Hi guys,

This is my first attempt at Linux, so bare with me.

I tried installing Ferora Core 1, but the software hung at "running /sbin/loader". so I gave up and tried Red Hat 9 (which I had an old copy of).

I selected server option and then selected all options. On reboot, it is now hanging at "Finding module dependencies".

What should I do? I have tried rebooting loads of times and am beginning to dispair. I can't bring myself to reinstall all over again,

Your help will be gratefully received,

Thanks,

James

p.s. my computer hardware is:
Asus A7N266 - 160Gig Maxtor Diamond 9 - Duron 1100 and black case with penguin on front!

You said you selected all options... it may mean that there is so much packages to load that it takes a long time to load. How long have you tried waiting?

Maybe you just have to wait a little longer.

I am also facing the same problem can't any one in this community help in gettng through this
Error Message : Hanging during finding module dependencies
Hardware : AMD Athlon XP, Asus MB
Same Problem with : RedHat/Mandrake
Type of Installations : Minimal, Custom,Everything,Personal Desktop
Please HELP.................. URGENT

Hi,

I actually found that my hard drive was not working properly/totally buggered and it didn't have anything to do with linux. Although, as the post above yours suggests you try installing with only a few components selected. Have you tried this?

jim

Always good advice. Try dealing with as few variables as possible. If the system isn't cooperating, give it fewer things to do. In this case, a minimal install might be in order. If it boots okay, then you can install more packages on top of this working system. But since your system isn't even getting far enough along to be dealing with layered applications, I'd wait on doing the minimal install (or reinstall).

Not sure if this is what's affecting you but, some years ago, I had a very similar problem with the system hanging when it reached that part in the startup scripts. (This was with RH7.) I think the problem had something to do with a mismatch between the modules and the running kernel. But it was one that I'd recompiled; the stock kernel from the installation never hung.

Have you recompiled the kernel lately?

Do you have lilo or grub setup with a failsafe/generic kernel that you could boot from?

What about booting into single user mode? Does that work? If so, at least you have a way to get into the system. When I got burned by this, I recall booting to single user and editing the startup scripts to insert a "set -x" just before where I thought the problem was occuring so I could see all the commands that were being executed. If I saw nothing then I didn't place the "set -x" early enough in the script. It'll take some trial and error before you can find the exact line (probably "depmod -A"). Especially if you're not certain just what script is running when it hangs. (probably something like "/etc/rc.d/rc.sysinit")

Dunno if I'll be able to help out if the problem is inherent to Fedora. I still have a Red Hat (8.0) system up and running. My guess is that the startup scripts haven't changed that much.

BTW, once you know what line it's stuck on, can you post that section -- plus a little context on either side of the section -- of the startup script? It'd be a help. Assuming, of course, you can get into the system to do some debugging.

Good luck...