Red Hat Bugzilla – Bug 494341
kernels newer than 2.6.29-0.258.2.3.rc8.git2.fc11.i586 stall at udev
Last modified: 2018-04-11 08:05:14 EDT
Description of problem:
Kernel released with F11 beta boots fine. Updates, including the latest on koji (188.8.131.52-52.fc11.i586), start booting but never get through the starting udev display. Have to power-cycle to reboot. All updates have been applied.
Version-Release number of selected component (if applicable):
kernel.i586 184.108.40.206-46.fc11 and newer
Steps to Reproduce:
udev message displayed with blinking cursor for a couple of seconds, cursor disappears, no response to anything other than power button.
Toshiba Satellite A105
Looks like the video device is Radeon Xpress 200M.
Can you try adding 'nomodeset' to the boot options?
Video is Intel Mobile 915GM. Using nomodeset works regardless - I'm adding this note from a successful boot.
Installed latest kernel (220.127.116.11-54.fc11.i586) and Intel X11 driver from rawhide with no help - still need to use "nomodeset".
Discovered that the use of a vga= kernel option negates the need for nomodeset, at least with the latest rawhide kernel (18.104.22.168-126.fc11.i686.PAE). I added vga=864 to my kernel line in grub.conf and, while I get a blank screen during boot and shutdown, all works properly.
*** Bug 498072 has been marked as a duplicate of this bug. ***
Argh, mixed up the dup direction. Fixing assignee/component/blocks.
This sounds similar to bug 493526, which concerns boot hangs with kernel-PAE and systems with intel video and 4GB (or more) RAM.
How much RAM is in your system? Have you tried using a x86_64 Live image instead?
The system is maxed out at 2GB of RAM. This is not a 64 bit CPU AFAIK - Intel Pentium® M Processor 740. If the 64 bit Live image would work, let me know and I'll try it.
You're correct, it's not 64-bit capable, so ignore that suggestion. And since you don't have 4GB ram it's probably not the same bug.
Can you try this test kernel:
and let us know if it works?
Same old same old. Use of a vga= option still gives a blank screen but booting works properly.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command
yum upgrade --enablerepo='*-updates-testing'
Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
I happen to be running F12 Beta (plus all updates) and no longer need to use the "nomodeset" kernel option. It was only the install of F12 that allowed this so unless F11 changed in the past two weeks, nothing has changed. Since I no longer have F11 installed and since F12 seems to have cured the issue, I guess we can close this. It would have been nice to have been able to actually fix F11, though, rather than having to resort to F12.
Thank you for letting us know.