| Summary: | Cannot boot Fedora 16 without nomodeset kernel parameter | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mark Lambert <lambertm> | ||||||
| Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 16 | CC: | ekanter, fedora, iarlyy, jonathan, lambertm, notting, plautrba, rhttrindade, rstrode, ulrich.hobelmann | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | 684898 | Environment: | |||||||
| Last Closed: | 2013-02-13 22:01:13 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Mark Lambert
2012-02-05 16:49:09 UTC
Cloned to a new bug as not only related to USB booting - this is an installed system that worked fine as F15, F16 for a few days after initial upgrade F15->F16 and THEN stopped booting properly. Attached the :0.gdm.1.log (when not using nomodeset). Noticed NO Xorg.?.log created in this case - so the boot process seem to fail before X becomes involved. Scanning rest of logs and will hopefully find something further useful to attach. I completed viewing system logs - oddly, /var/log/messages has no entries from the boot attempt (replaced nomodeset with video=i915). Only the successful boots (because of nomodeset) show. Nothing else of interest in any log. So...is this a driver issue? Kernel issue? DRM issue? X11 issue? Plymouth? I have more questions now than when I began trying to figure this out. The worst part is...FC16 worked *fine* before. Only thing I cannot downgrade is the kernel at this point. I am stuck with 3.2.2-1 until an update comes down. Hoping one does, and cures this - I will update this bug either way with results after next kernel update. Probably my last input for today...however interesting results whether very useful or not - remains to be seen. Booted from DVD again...same result. (nomodeset will allow boot) Created LiveUSB and booted...same result. (nomodeset will allow boot). On both media...screen turns to white background...then a message (as much as I could read in the short time displayed)..."Unable to fully initialize daemon ... no such file or directory" then straight to blank screen. Not just blank actually - if power indicators didn't show machine powered on it would look powered-down. Mark, since you are not on the CC List for bug 684898 I will post this here also. There is a difference between the F16 USB and the DVD installation. I found this out when I tried to reinstall F16 with the DVD and the system did not detect it. At the time I probably removed the boot dir completely to get the DVD going. When I got to the login screen I could see that it looked different. Update to 3.2.3-2 kernel released and problem still occurs. Since I upgraded using pre-upgrade tool...then had this issue start I have tested with both DVD and USB-stick media from an installation DVD image. I am now downloading "Live" images (Gnome and KDE) and will post my results later on today. I am thinking this is much like an issue around FC10 I believe it was where the intel_drv.ko module couldn't load properly because the framebuffer driver (fbcon back then wasn't it?) hadn't been loaded first. Now I think it is supposed to be inteldrmfb (which is created by fbcon) .... I now somewhere in old logs I saw /dev/fb0 : no such device or something like that. Before the screen blanks I see something about Plymouth...then [drm]<something..something...> - goes blank too quickly to catch and at this point the system is not yet logging. Will d/l both these images, try one by one on usb stick and see what happens. Somehow I think this is the fault of the framebuffer driver not being loaded when it should. I am also attaching the output of lsinitrd on my current kernel initramfs file. Created attachment 559637 [details]
Output of lsinitrd /boot/initramfs-3.2.3-2.fc16.x86_64.img
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. |