Created attachment 107460 [details] Screenshot Description of problem: I tried to install Fedora 20 LXDE spin, but after livecd boot I got an unexpected behaviour as represented in the screenshot. I tried to boot the livecd in basic video mode and I managed to install Fedora, even using a basic resoluzione of 640x480. When I booted the just installed Fedora, I got again a similar behaviour like in the mentioned screenshot. Additional info: [*] 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01) [*]The package contains two xorg.0.log log files: one for the livecd session, one for the installed Fedora session [*]Fedora bugreport https://bugzilla.redhat.com/show_bug.cgi?id=1149242
Created attachment 107461 [details] xorg.0.log
Hmm. The postinstall logs contain nomodeset on the kernel commandline, disabling the intel driver (both ddx and kernel). Do you see the same behaviour if you then remove that and replace it with drm.debug=6 from the grub entry when booting? Could you attach the Xorg.0.log and dmesg after doing so?
Created attachment 108799 [details] dmesg with drm.debug=6 kernel flag # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.16.6-203.fc20.i686 root=UUID=**removed** ro vconsole.font=latarcyrheb-sun16 drm.debug=6 LANG=it_IT.UTF-8
Created attachment 108800 [details] Xorg.0.log with drm.debug=6 kernel flag
(In reply to Chris Wilson from comment #2) > Hmm. The postinstall logs contain nomodeset on the kernel commandline, > disabling the intel driver (both ddx and kernel). Do you see the same > behaviour if you then remove that and replace it with drm.debug=6 from the > grub entry when booting? Could you attach the Xorg.0.log and dmesg after > doing so? I get a black screen that shows only the mouse pointer.
I have no longer access to the affected machine, nor I had any feedback from component developers. I close the bugreport as wontfix
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.