eth0 not staying configured

[Jim Herrmann]

So, even though it identifies itself as Sis being the vendor, the bus 
identifier says Realtek?  OK.  This is an itegrated NIC on a MoBo that 
has everything integrated, sound, network, video, and 256 M RAM, believe 
it or not.  It has one slot to add memory, and two PCI slots. 

So is the "tulip" driver bleeding edge?  I'd never heard of it before.  
Are you suggesting that I can choose Realtek 1039 for my driver, and it 
just might work?  I'll give it a try.

Peace,
Jim

Brian Kelsay wrote:

>Does the tulip driver work for Realtek chipsets?   This ( Bus
>identification: ?1039:900) tells me that you have a Realtek 1039 network
>chipset on the mobo or on a NIC.   Yes, it is probably sad that I can tell
>this by looking at four numbers, but ya gotta have a hobby.
>Have you tried to get a more up to date driver or one that is not a
>prerelease?   Maybe it is too bleeding edge.
>Brian
>----- Original Message -----
>From: "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
>>
>>    
>>
>
>
>
>
>
>  
>