Re: problems upgrading from 2.4.19-2.4.20

On Mon, 16 Dec 2002, Ed Schaller wrote:

> I have a HP B180 (parisc) that I have been using as a firewall/router for
> some time now. Along with the built in tulip ethernet card, I also have
> a Adaptec quad ethernet card that is also tulip based. This has worked
> fine in 2.4.17-2.4.19 but no longer works in 2.4.20-pa13. Although I
> can ifconfig up the interfaces, no traffic goes through and mii-tool
> reports that the interfaces do not exist (except for the built in one).

> After reporting this to the parisc list, Grant Grundler
> ([email protected]), said that he was having same problem on
> a HP A500 (also parisc) but with a single port HP tulip card. He thought
> that it was probably a tulip driver bug and not a parisc specific bug,
> so I thought I would also post it here.

Grant has a specific built-in NIC with an unusual transceiver reset
timing requirement that cannot be specified with the media table.
His problem is not a general one, and it's certainly related to your
problem.

> 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				[email protected]
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Scyld Beowulf cluster system
Annapolis MD 21403			410-990-9993

_______________________________________________
tulip-bug mailing list, [email protected]
To change to digest mode or unsubscribe visit
http://www.scyld.com/mailman/listinfo/tulip-bug