I had yum install kde-develop for me however during that download, due to a freak accident the system was turned off. When the system restarted, it gave the message eth0 failed to start. i checked log and it seemed that the kernel module failed to load. Along with that Kudzu also had problem loading.
I tried to manually load the module but it says that it can't find the module. Let me repeat that the same ethernet was working well and truly well before this accident occured. Now i am in a fix because i can't access the network. Also other modules like ntfs fails to load.

When i ifconfig eth0 it says device eth0 not found.

Can any one give me a walkthrough that how am i going to load the module which existed before the accident.

Oh and by the way my distro is FC 5.

regards.

Install the missing module off the install disk. Then update when you get a connection.

Lazlow

The Missing module that is 8139too.ko is there in the /lib/modules/2.6.15-1_FC5/kernel/drivers/net/8139too.ko.

However when i do modprobe 8139too.ko it tells me that it couldn't find the module.

when i insmod /lib/modules/2.6.15-1_FC5/kernel/drivers/net/8139too.ko
It gives me the following error
insmod error inserting /lib/modules/2.6.15-1_FC5/kernel/drivers/net/8139too.ko
-1 Unknown Symbol in Module

Any Suggestions

IMHO it is worth the time to re-install the Distro. I would if it were me trying to correct a module<s> situation. It is YOUR system,...YOU know which is the quicker fix to be up-n-running. Another reason for suggesting the re-install is that it gives <us> the opportunity to make more acceptable choices during the Distro installation. Observation: Reading previous posts here in this Forum,...there a more than one module/driver for the Realtek Device. Try a "search", and YOU'll find the different drivers and their corrections. Good luck my friend.

Don't include the ".ko" extension. Just type:

modprobe 8139too

8139too also needs crc32 and mii modules. One of those isn't being loaded. Check dmesg to see which one it is.

You should make a habit of using modprobe instead of insmod. Insmod is dumber than modprobe. Modprobe handles module dependencies and loads them automagically; insmod doesn't.

Check your /etc/modprobe.conf file to see if you have the following line in it:

alias eth0 8139too