Description of problem: My systems boots very slow. The cause seems to be dracut waiting for something. I don't know what exactly. I find this information in /var/log/messages: ... Feb 6 10:38:14 galadriel kernel: dracut: dracut-004-4.fc12 ... Feb 6 10:38:14 galadriel kernel: dracut: Feb 6 10:38:14 galadriel kernel: dracut: udevadm settle - timeout of 30 seconds reached, the event queue contains: Feb 6 10:38:14 galadriel kernel: dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0 (709) Feb 6 10:38:14 galadriel kernel: dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/controlD64 (793) Feb 6 10:38:14 galadriel kernel: dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (794) Feb 6 10:38:14 galadriel kernel: dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1 (800) Feb 6 10:38:14 galadriel kernel: dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (801) Feb 6 10:38:14 galadriel kernel: dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-SVIDEO-1 (802) Feb 6 10:38:14 galadriel kernel: dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (803) Feb 6 10:38:14 galadriel kernel: dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-DVI-I-1 (805) Feb 6 10:38:14 galadriel kernel: dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (806) Feb 6 10:38:14 galadriel kernel: dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-VGA-1 (808) Feb 6 10:38:14 galadriel kernel: dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (809) Feb 6 10:38:14 galadriel kernel: dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/graphics/fb0 (812) Feb 6 10:38:14 galadriel kernel: dracut: Starting plymouth daemon The delay does happen around here during boot. My laptop is a Macbook Pro of a couple of years back. Here's the smolt profile to give you more details on the hardware: http://www.smolts.org/show?uuid=pub_9f283477-35bb-407a-a913-8e5061dcf670 If you need any more information just let me know. I'm also available to perform additional tests on this laptop.
Does your video card need a special module / firmware?
The card is an ATI Technologies Inc M56P [Radeon Mobility X1600]. How do I know if it needs a special module/firmware ? If it does, I didn't install any. The installation is F12 upgraded from a clean rawhide install around the first or second beta release of F12.
hmm, you could add "rdudevinfo" to the kernel command line to get more info
I tried that, but then the system won't boot anymore. When the rdudevinfo parameter is added, the console starts printing lots of udev related debugmessages. But at some point, it just hangs. With each reboot it hangs at another message. There's no crash, it just hangs. I have waited several minutes but nothing changes anymore. From trying several times, I gather this is when kernel mode setting kicks in. This seems to be incompatible with the rdudevinfo parameter. So I tried to disable kms and suddenly all is well. The boot delay is gone with or without the rdudevinfo option. Does this mean there's something wrong with the kms code in the radeon driver for my particular graphics card ? Let me know if I can provide you with more information.
seems like the kms code of the radeon driver makes the trouble.. reassigning to component "kernel"
Meanwhile I have updated from kernel 2.6.31.x to 2.6.32.x. I can no longer reproduce this delay with this new kernel series. I tried 2.6.32.9, 2.6.32.10 and 2.6.32.11. As far as I'm concerned this bug is fixed and this ticket can be closed.
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
This is no longer a problem in Fedora 13. I'll close.