Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

There's no /etc/X11/xorg.conf anymore and /var/log/dmesg will obviously not help because I cannot provide the version of it when using KMS (as I get zero screen output).

I will try to get a meaningful Xorg.log as soon as I get access to the system again.

Trying to reset to needinfo

Created attachment 349701 [details]
Xorg.0.log

So I just instructed my GF to remove the nomodeset kernel option and boot. Surprisingly everything seems to work fine now. Maybe some post-release update already fixed the problem?

Anyway here's Xorg.0.log, please have a look and see if everything is fine. There are a few (EE)s inside but KMS, UXA and DRI2 seem to be working fine. Thanks!

Yeah, these are probably harmless:

(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0xffffffff: DRI memory manager (0 kB)
(II) intel(0): 0x00000000:            end of aperture
(II) intel(0): BO memory allocation layout:
(II) intel(0): 0x00000000:            start of memory manager
(II) intel(0): 0x02418000-0x027fffff: front buffer (4000 kB) X tiled
(II) intel(0): 0x02408000-0x02411fff: HW cursors (40 kB)
(II) intel(0): 0x00000000:            end of memory manager
(EE) intel(0): max_gtt_map_size: 55272kb.

Thanks. Should I file the (EE)s separately (maybe on freedektop bugzilla) anyway?

(In reply to comment #6)
> Thanks. Should I file the (EE)s separately (maybe on freedektop bugzilla)
> anyway?  

We think that these (EE)s are harmless. Don't bother.

Thank you offer though, of course.