Bug 576457
| Summary: | firstboot errors when loading modules | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Misty Stanley-Jones <misty> |
| Component: | firstboot | Assignee: | Martin Gracik <mgracik> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | awilliam, dmach, lcarlon, mhlavink, psatpute |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 530320 | Environment: | |
| Last Closed: | 2010-12-03 16:50:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Misty Stanley-Jones
2010-03-24 05:34:38 UTC
if you boot to initlevel 3 (just add '3' as a kernel parameter), can you get to a console? If you then create a user account with 'useradd', login as that user and do startx, does it work? Then try disabling the 'firstboot' service and rebooting to normal initlevel (5) again... just trying to help narrow down what the breakage is here. Seems odd that firstboot itself would get stuck like that... also, why is this set as an F13 blocker when it's filed against F12 and your initial report says you were testing F12? I did not mark it as an F13 blocker (though it may be, if it still exists in F13). I will do the tests you requested and get back with you. hmm, it was me who set it as a beta blocker. clearly i'm losing it. =) sorry. adjusting. Your workaround does work. What else works is setting /boot as ext3 instead of ext4. I am out of time to test this, but hopefully something helpful has come out of it. that should at least give the devs a fighting chance of figuring out what's wrong... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers 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. |