[tulip-bug] Problems with 21041 in 2.4.9, worked in 2.2.19

[Edwin Chiu]

I did somemore testing, it's broken between 2.4.3 and 2.4.5

Just incase, here is the PCI entry...

00:0d.0 Ethernet controller: Digital Equipment Corporation DECchip 21140
[FasterNet] (rev 22)
        Subsystem: Acer Incorporated [ALI]: Unknown device 0310
        Flags: bus master, medium devsel, latency 64, IRQ 10
        I/O ports at ec00 [size=128]
        Memory at ea002000 (32-bit, non-prefetchable) [size=128]
        Expansion ROM at e9000000 [disabled] [size=256K]

Edwin Chiu wrote:
> 
> Hi,
> 
> I downloaded the tulip 0.9.14 driver and that seems to work.
> Kernel 2.4.9 comes with 0.9.15-pre6
> 
> The DE4x5 driver works as well, but I get carrier errors for
> every packet sent...
> 
> Regards,
> Edwin
> 
> Edwin Chiu wrote:
> >
> > Hi,
> >
> > Here is ths situation:
> >
> > I have a 21041, I think it's an Acer or D-link fast ethernet card that
> > worked with 2.2.10 thru 2.2.19.
> >
> > The new driver in 2.4.9 doesn't seem to work with the card... I can
> > see it sending packets on the switch, but it's definitely not receiving
> > anything, b/c the arp tables are empty.
> >
> > Tried the stock 2.4.9 driver and the one that Jeff maintains on
> > sourceforge (tulip-1.1.8)
> >
> > Here is some tulip-diag output:
> >
> > tulip-diag.c:v2.08 5/15/2001 Donald Becker (becker@scyld.com)
> >  http://www.scyld.com/diag/index.html
> > Index #1: Found a Digital DC21041 Tulip adapter at 0xe400.
> > Digital DC21041 Tulip chip registers at 0xe400:
> >  0x00: ffe08000 ffffffff ffffffff 0ec50000 0ec50200 fc000112 fffe0200 fffe0000
> >  0x40: fffe0000 ffff4bf0 ffffffff fffe0000 41e1d5c8 ffffef01 ffffffff ffff0008
> >  Port selection is full-duplex.
> >  Transmit stopped, Receive stopped, full-duplex.
> >   The Rx process state is 'Stopped'.
> >   The Tx process state is 'Stopped'.
> >   The transmit unit is set to store-and-forward.
> >   The NWay status register is 41e1d5c8.
> >   Internal autonegotiation state is 'Negotiation complete'.
> > Index #2: Found a Digital DS21140 Tulip adapter at 0xec00.
> >  * A potential Tulip chip has been found, but it appears to be active.
> >  * Either shutdown the network, or use the '-f' flag to see all values.
> > Digital DS21140 Tulip chip registers at 0xec00:
> >  0x00: ffa08000 ffffffff ffffffff 0fab5000 0fab5200 fc660000 32042202 ffffebef
> >  Port selection is MII, full-duplex.
> >  Transmit started, Receive started, full-duplex.
> >   The Rx process state is 'Waiting for packets'.
> >   The Tx process state is 'Idle'.
> >   The transmit threshold is 128.
> >
> > --
> >  (tulip-diag -a -f)
> >
> > tulip-diag.c:v2.08 5/15/2001 Donald Becker (becker@scyld.com)
> >  http://www.scyld.com/diag/index.html
> > Index #1: Found a Digital DC21041 Tulip adapter at 0xe400.
> > Digital DC21041 Tulip chip registers at 0xe400:
> >  0x00: ffe08000 ffffffff ffffffff 0ec50000 0ec50200 fc000112 fffe0200 fffe0000
> >  0x40: fffe0000 ffff4bf0 ffffffff fffe0000 41e1d5c8 ffffef01 ffffffff ffff0008
> >  Port selection is full-duplex.
> >  Transmit stopped, Receive stopped, full-duplex.
> >   The Rx process state is 'Stopped'.
> >   The Tx process state is 'Stopped'.
> >   The transmit unit is set to store-and-forward.
> >   The NWay status register is 41e1d5c8.
> >   Internal autonegotiation state is 'Negotiation complete'.
> > Index #2: Found a Digital DS21140 Tulip adapter at 0xec00.
> > Digital DS21140 Tulip chip registers at 0xec00:
> >  0x00: ffa08000 ffffffff ffffffff 0fab5000 0fab5200 fc660000 32042202 ffffebef
> >  0x40: e0000000 fff583ff ffffffff fffe0000 ffffff40 ffffffff 1c09fdc0 fffffec8
> >  Port selection is MII, full-duplex.
> >  Transmit started, Receive started, full-duplex.
> >   The Rx process state is 'Waiting for packets'.
> >   The Tx process state is 'Idle'.
> >   The transmit threshold is 128.