Created attachment 406039 [details] /var/log/messages Description of problem: after upgrading to 2.6.32.11-99.fc12.i686.PAE the screen reamins completely dark during and after boot. I can blindly type the dm-crypt pashphrase, the system boots, gdm is started but nothing ever appears on screen. Grub entry: title Fedora (2.6.32.11-99.fc12.i686.PAE) root (hd0,1) kernel /vmlinuz-2.6.32.11-99.fc12.i686.PAE ro root=/dev/mapper/vg_netbook-lv_root LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=de-mobii initrd /initramfs-2.6.32.11-99.fc12.i686.PAE.img This is a typical 1st gen Atom based netbook with Intel Graphic, never had any problems with it. For HW details please see attached /var/log/messages and http://www.smolts.org/client/show/pub_60ee46a0-1f44-40bf-b7ce-b9c82789c940 Last version that worked for me was a selfcompiled kernel.org 2.6.32.8
What's the last kernel build that works, for you? Can you provide the log from a boot on that kernel, for comparison? If you take 'rhgb quiet' out of the kernel parameter list, does the behaviour change? What happens if you add the parameter 'nomodeset'? Thanks. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
- can you please point me at a list of older kernel builds to try? - removing rhgb quiet did not change anything (when tried with the F13-2.6.33.1 build I could see the messages till well after ramdisk took over but went black before asking for dm-crypt password - latest msg that flashed by was not surprisingly something DRM related) - will try nomodeset and the other things in a few hours
Richard, for older kernel look at http://koji.fedoraproject.org/koji/packageinfo?packageID=8
tried a few kernels, last one that worked "out of the box" was 2.6.31.12-174.2.19.fc12.i686.PAE, will add dmesg in a while. Perhaps more interesting is the behavior of 2.6.32-0.48.rc7.git1.fc13.i686. Booted with default options it recorded an oops in the Intel drm code. It did continue booting, kdm started but nothing was visible on screen. Console switching worked though so I was able to login into it. Also tested all kernels again with nomodeset and they booted without problems, kdm started and I was able to login.
Created attachment 407932 [details] boot messages 2.6.32-0.48.rc7.git1.fc13.i686, showing ooops did boot, kdm started but screen black, could switch to different VT and login
Created attachment 407934 [details] messages from 2.6.31.12-174.2.19.fc12.i686.PAE last known version that booted with default parameters, graphical boot and modesetting
It sounds like I am having the same problem. Kernel 2.6.31.5-127.fc12.i686 runs on a Dell E6410 with an intel chip set. Upon updating to 2.6.32 I get a blank screen at boot. If I add nomodeset to grub then I see the scrolling bar at the bottom of the screen, but then it goes blank where I would expect a login screen. Anyway, I am very interested in solving this. Can I offer some data? Thanks, Sean Lawton
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.