It seems that rc.sysinit finds out which module to load using kmodule
commands output. But it that NETWORK e1000 doesn't get loaded as module:
Maybe defining e1000 explicitly (network="e1000" in rc.sysinit) solves the
problem which I can't risk since it is a remote system:
Below is a snippet from rc.sysinit
echo -n $"Initializing hardware... "
ide=""
scsi=""
network=""
audio=""
other=""
eval `kmodule | while read devtype mod ; do
case "$devtype" in
"IDE") ide="$ide $mod"
echo "ide=\"$ide"\";;
"SCSI") scsi="$scsi $mod"
echo "scsi=\"$scsi"\";;
"NETWORK") network="$network $mod"
echo "network=\"$network"\";;
"AUDIO") audio="$audio $mod"
echo "audio=\"$audio"\";;
*) other="$other $mod"
echo "other=\"$other"\";;
esac
done`
> I think on power outage one of the files deleted by the fsck. I want to
> ask which file or startup script loads ethernet and other networking
> modules (such as iptables). I have manually edited
> /etc/rc.d/init.d/network to load e1000 driver from
> /lib/modules/KERNEL-VERS/kernel/drivers/net/e1000/e1000.ko which is
> obviously not a good thing to do but solved my problem for a while. At
> least until I debug the problem.
>
> Your situation I think all different than mine. But thanks .
>> On Sat, 31 Dec 2005, Omer Faruk Sen wrote:
>>
>>> Hi,
>>>
>>> I have a peculiar problem that I can't solve by my own. I have a server
>>> installed rhes es4.2. After a power problem machine got rebooted. After
>>> that e1000 eth module can't get loaded automaticly which was getting
>>> loaded perfectly before without any problem. I have no idea why that
>>> happens and want to ask why that might be. And will be glad if you show
>>> help me about this problem.
>>
>> I noticed if you need a driver disk to load a module for something else,
>> my e1000 would not recognize either. Once I used the correct driver
>> disk,
>> all other modules loaded flawlessly. I don't know if this applies to
>> you
>> or not.
>>
>>
>
>
> --
> Omer Faruk Sen
> http://www.faruk.net
>
--
Omer Faruk Sen
http://www.faruk.net
