eth0 not staying configured

[Brian Kelsay]

http://www.tux.org/hypermail/linux-tulip-bug/2002-Dec/0005.html

Quote from Donald Becker, who wrote the tulip driver, in response to email
about that driver :

> In the following dmesg out takes for 2.4.20-pa13 and 2.4.19-32 (debian),
> it seems that the older kernel is finding the transceiver and
> successfully auto-negotiating the link while the newer is not.
>
> Any ideas how to solve this? Any help would be greatly appreciated.

Use a different driver version.

> Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)

That driver is based on mine (despite removing the copyright information
from the output and binary), but it's derivative code. I can't help you
with the specific problem, but can confirm that it is broken...

> tulip0: no phy info, aborting mtable build
> tulip0: MII transceiver #1 config 1000 status 782d advertising 01e1.
> eth0: Digital DS21143 Tulip rev 48 at 0xf0fff000, 00:60:B0:C4:5E:7B, IRQ
96.
> eth1: Digital DS21140 Tulip rev 34 at 0xf0efc000, 00:00:D1:1B:C8:90, IRQ
98.
> eth2: Digital DS21140 Tulip rev 34 at 0xf0efd000, 00:00:D1:1B:C8:B5, IRQ
99.
> eth3: Digital DS21140 Tulip rev 34 at 0xf0efe000, 00:00:D1:1B:C8:95, IRQ
96.
> eth4: Digital DS21140 Tulip rev 34 at 0xf0eff000, 00:00:D1:1B:70:33, IRQ
97.
> ...until ifconfig eth0-eth4

Hmmm, no media information. I don't know if the output has been
removed, or if this version isn't reading the EEPROM correctly.

> Linux Tulip driver version 0.9.15-pre11 (May 11, 2002)
> tulip0: no phy info, aborting mtable build
> tulip0: MII transceiver #1 config 1000 status 782d advertising 01e1.
> eth0: Digital DS21143 Tulip rev 48 at 0xff00, 00:60:B0:C4:5E:7B, IRQ 96.
> tulip1: EEPROM default media type Autosense.
> tulip1: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
> tulip1: MII transceiver #1 config 3100 status 7849 advertising 01e1.
> eth1: Digital DS21140 Tulip rev 34 at 0xec00, 00:00:D1:1B:C8:90, IRQ 98.

This is better.

--
Donald Becker				becker at scyld.com
Scyld Computing Corporation

----- Original Message -----
From: "Jim Herrmann" <kclug at ItDepends.com>
To: "KCLUG" <kclug at kclug.org>
Sent: Thursday, May 15, 2003 4:17 AM
Subject: Re: eth0 not staying configured

> 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