eth0 not staying configured

[Jim Herrmann]

Some messages from the log at boot up time:

May 14 01:34:42 lou kernel: Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)
May 14 01:34:42 lou insmod: /lib/modules/2.4.21-0.13mdk/kernel/drivers/net/tulip/tulip.o.gz: 
init_module: No such device
May 14 01:34:42 lou insmod: Hint: insmod errors can be caused by incorrect module parameters, 
including invalid IO or IRQ parameters. You may find more information in syslog or the output from 
dmesg
May 14 01:34:42 lou modprobe: modprobe: insmod eth0 failed

So, it appears that it is trying to bring up the network, but failing. 
The tulip driver appears to be a driver for a lot of things, and it 
works fine when it is run later by the network setup.

And the info about the network card:

Vendor: ?Silicon Integrated Systems [SiS]
Bus: ?PCI
Bus identification: ?1039:900
Location on the bus: ?0:1:1
Description: ?SiS900 10/100 Ethernet
Module: ?sis900
Media class: ?NETWORK_ETHERNET

file:/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
NETMASK=255.255.255.0
ONBOOT=yes
MII_NOT_SUPPORTED=yes
NEEDHOSTNAME=yes

Which is exactly the same as the one on my machine.

Still looking,
Jim

Jim Herrmann wrote:

> I bought my wife a new motherboard for Mother's Day (get it? ;-) ), 
> and upgraded her from Mandrake 9.0 to 9.1. I have everything working 
> fine, except that the network doesn't remain configured. I can 
> configure it with the Mandrake tools once it's booted, and everything 
> works great. Upon reboot, which my wife does daily as she like to 
> shutdown at night, the network configuration is lost again, and I have 
> to go through network setup again.
> Suggestions on what I should look at and what configuration files 
> might be involved that Mandrake is not writing out properly. Any help 
> would be appreciated. And yes, I know, I'm too damned dependent on 
> those GUI tools. :-)
>
> Thanks,
> Jim
>
>
>
>
>