FC5 on Acer Laptop - won't boot past udev...

[thejeremy]

Hello forum,

I just went out and bought an Acer Aspire 5100 laptop last night. Here are the specs:

AMD Turion 64 bit CPU
1 GB of RAM
ATI Radeon Express 1100, 128MB
80GB PATA HD

I think that's everything that's relevant.

So I downloaded the 5 FC5 CD iso files (the x86_64 ones), burned them, and started installing. Everything installed just fine. GRUB came up, I chose Linux. However, it won't boot completely. Here's what happens.

Decompressing Linux...done.
Booting the kernel.
PCI: Cannot allocate resource region 7 of bridge 0000:00:04.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:04.0
PCI: Cannot allocate resource region 9 of bridge 0000:00:04.0
PCI: Cannot allocate resource region 7 of bridge 0000:00:05.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:05.0
...
(more stuff...)
...
Setting clock ... [ OK ]
Starting udev: ... [ FAILED ]

...and things just hang there. Does anyone know what type of issue this even is and how I can go about troubleshooting it?

Any help is appreciated.

[markjensen]

From a few googles[1] [2], it seems that "udev failed" is not typically/necessarily a fatal type of problem. However, there was one link that I stumbled across that might be of interest.
http://chandanthewhiz.wordpress.com/...starting-udev/
They recommend booting with acpi=off option to boot (then fix the problem). I don't know if that will work for you, but here are my reference googles, in case they prove helpful.


[1] http://www.google.com/search?q=starting+udev+failed
[2] http://www.google.com/linux?q=Cannot...00%3A00%3A04.0

[thejeremy]

Thanks for the reply

So far, nothing that I've tried has worked. The case where udev fails to start may not be fatal, but in my case, nothing proceeds beyond that point so I consider it fatal in a stability sense. I've tried different boot-time arguments (i.e. acpi=off, acpi=noirq...), and I tried the solution suggested here:

http://www.fedoraforum.org/forum/sho...highlight=udev

which basically renames pcmcia-socket-startup to pcmcia-socket-startup.bak. This causes an error to be printed to the screen when udev is loading, and udev still times out. I'll check out those other google links though.

Any other ideas??