Re: tulip driver BROKEN in 2.4.5-pre4

2001-05-23 Thread Johan Kullstam

Studierende der Universitaet des Saarlandes  <[EMAIL PROTECTED]> writes:

> Could you post the output of
> 
> #tulip-diag -mm -aa -f
> 
> with the broken driver?
> Some code that's required for Linksys Tulip clones was moved from pnic
> specific part into the generic part, perhaps that causes problems.

i have a 21041 dec tulip which has failed to work with
linux-2.4.5-pre[3-5] kernel drivers.  (it also fails with the
sourceforge devel version tulip-1.1.7)

it appears that the card gets lodged in full duplex mode.  however,
this could just be a superficial syndrome.

anyhow, here is the output of tulip-diag -mm -aa -f from the *broken*
driver

tulip-diag.c:v2.06 1/8/2001 Donald Becker ([EMAIL PROTECTED])
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21140 Tulip adapter at 0xfc00.
Digital DS21140 Tulip chip registers at 0xfc00:
 0x00: fff88000   03421000 03421200 fc000102 e384 fffe
 0x40: fffe dff0  fffe ff59  1c09fdc0 fec8
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
 Transmit stopped, Receive stopped, half-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  The transmit threshold is 128.
   No MII transceivers found!
Index #2: Found a Digital DC21041 Tulip adapter at 0xf080.
Digital DC21041 Tulip chip registers at 0xf080:
 0x00: ffe08000   0ee4e000 0ee4e200 fc000112 fffe0200 fffe
 0x40: fffe 4bf8  fffe 50c8 ef01  0008
 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 50c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Negotiation complete'.



and here is one working dump for comparison (driver 0.9.14 from
sourceforge)

tulip-diag.c:v2.06 1/8/2001 Donald Becker ([EMAIL PROTECTED])
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21140 Tulip adapter at 0xfc00.
Digital DS21140 Tulip chip registers at 0xfc00:
 0x00: fff88000   03421000 03421200 fc000102 e384 fffe
 0x40: fffe fff597ff  fffe ff59  1c09fdc0 fec8
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
 Transmit stopped, Receive stopped, half-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  The transmit threshold is 128.
   No MII transceivers found!
Index #2: Found a Digital DC21041 Tulip adapter at 0xf080.
Digital DC21041 Tulip chip registers at 0xf080:
 0x00: ffe08000   0ee4e000 0ee4e200 fc66 fffe2002 ebef
 0x40: fffe 03ff  fffe 01c8 ef05 ff3f 0008
 Port selection is half-duplex.
 Transmit started, Receive started, half-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit unit is set to store-and-forward.
  The NWay status register is 01c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Autonegotiation disabled'.


-- 
J o h a n  K u l l s t a m
[[EMAIL PROTECTED]]
Don't Fear the Penguin!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: tulip driver BROKEN in 2.4.5-pre4

2001-05-23 Thread Lukasz Trabinski

In article <[EMAIL PROTECTED]> you wrote:
> Okay, so Jeff Garzik already knows about this - I told him last week -
> but seeing as how the code has made it to a Linus pre-release without
> a fix I thought I'd better post the breakage description to l-k!


Try drivers from http://sourceforge.net/projects/tulip/
1.1.6 drivers + 2.4.5-pre1 works OK on high load router ( one four-ports
card and one two-ports carts).
Tulip drivers from 2.4.5-pre1 are realy borken. :(

-- 
*[ ukasz Trbiski ]*
SysAdmin @wsisiz.edu.pl
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: tulip driver BROKEN in 2.4.5-pre4

2001-05-23 Thread Lukasz Trabinski

In article [EMAIL PROTECTED] you wrote:
 Okay, so Jeff Garzik already knows about this - I told him last week -
 but seeing as how the code has made it to a Linus pre-release without
 a fix I thought I'd better post the breakage description to l-k!


Try drivers from http://sourceforge.net/projects/tulip/
1.1.6 drivers + 2.4.5-pre1 works OK on high load router ( one four-ports
card and one two-ports carts).
Tulip drivers from 2.4.5-pre1 are realy borken. :(

-- 
*[ ukasz Trbiski ]*
SysAdmin @wsisiz.edu.pl
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: tulip driver BROKEN in 2.4.5-pre4

2001-05-23 Thread Johan Kullstam

Studierende der Universitaet des Saarlandes  [EMAIL PROTECTED] writes:

 Could you post the output of
 
 #tulip-diag -mm -aa -f
 
 with the broken driver?
 Some code that's required for Linksys Tulip clones was moved from pnic
 specific part into the generic part, perhaps that causes problems.

i have a 21041 dec tulip which has failed to work with
linux-2.4.5-pre[3-5] kernel drivers.  (it also fails with the
sourceforge devel version tulip-1.1.7)

it appears that the card gets lodged in full duplex mode.  however,
this could just be a superficial syndrome.

anyhow, here is the output of tulip-diag -mm -aa -f from the *broken*
driver

tulip-diag.c:v2.06 1/8/2001 Donald Becker ([EMAIL PROTECTED])
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21140 Tulip adapter at 0xfc00.
Digital DS21140 Tulip chip registers at 0xfc00:
 0x00: fff88000   03421000 03421200 fc000102 e384 fffe
 0x40: fffe dff0  fffe ff59  1c09fdc0 fec8
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
 Transmit stopped, Receive stopped, half-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  The transmit threshold is 128.
   No MII transceivers found!
Index #2: Found a Digital DC21041 Tulip adapter at 0xf080.
Digital DC21041 Tulip chip registers at 0xf080:
 0x00: ffe08000   0ee4e000 0ee4e200 fc000112 fffe0200 fffe
 0x40: fffe 4bf8  fffe 50c8 ef01  0008
 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 50c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Negotiation complete'.



and here is one working dump for comparison (driver 0.9.14 from
sourceforge)

tulip-diag.c:v2.06 1/8/2001 Donald Becker ([EMAIL PROTECTED])
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21140 Tulip adapter at 0xfc00.
Digital DS21140 Tulip chip registers at 0xfc00:
 0x00: fff88000   03421000 03421200 fc000102 e384 fffe
 0x40: fffe fff597ff  fffe ff59  1c09fdc0 fec8
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
 Transmit stopped, Receive stopped, half-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  The transmit threshold is 128.
   No MII transceivers found!
Index #2: Found a Digital DC21041 Tulip adapter at 0xf080.
Digital DC21041 Tulip chip registers at 0xf080:
 0x00: ffe08000   0ee4e000 0ee4e200 fc66 fffe2002 ebef
 0x40: fffe 03ff  fffe 01c8 ef05 ff3f 0008
 Port selection is half-duplex.
 Transmit started, Receive started, half-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit unit is set to store-and-forward.
  The NWay status register is 01c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Autonegotiation disabled'.


-- 
J o h a n  K u l l s t a m
[[EMAIL PROTECTED]]
Don't Fear the Penguin!
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: tulip driver BROKEN in 2.4.5-pre4

2001-05-21 Thread J Brook

> Could you post the output of
> 
> #tulip-diag -mm -aa -f
> 
> with the broken driver?
> Some code that's required for Linksys Tulip clones was moved
> from pnic specific part into the generic part, perhaps that
> causes problems.

Here is the output from the kernels I've tested to try to get the
driver working:

2.4.4-ac6, this kernel works!

tulip-diag.c:v2.06 1/8/2001 Donald Becker ([EMAIL PROTECTED])
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DC21041 Tulip adapter at 0xd800.
Digital DC21041 Tulip chip registers at 0xd800:
 0x00: ffe08000   0129f000 0129f200 fc66 fffe2002
ebef
 0x40: fffe 03ff  fffe 01c8 ef05 ff3f
0008
 Port selection is half-duplex.
 Transmit started, Receive started, half-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit unit is set to store-and-forward.
  The NWay status register is 01c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Autonegotiation disabled'.

--

2.4.5-pre4 this kernel doesn't work

tulip-diag.c:v2.06 1/8/2001 Donald Becker ([EMAIL PROTECTED])
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DC21041 Tulip adapter at 0xd800.
Digital DC21041 Tulip chip registers at 0xd800:
 0x00: ffe08000   0129e000 0129e200 fc66 fffe2202
ebef
 0x40: fffe 03ff  fffe 50c8 ef01 
0008
 Port selection is full-duplex.
 Transmit started, Receive started, full-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit unit is set to store-and-forward.
  The NWay status register is 50c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Negotiation complete'.

--

2.4.4-ac9 with tulip 1.1.7 driver (from sf.net/projects/tulip)

tulip-diag.c:v2.06 1/8/2001 Donald Becker ([EMAIL PROTECTED])
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DC21041 Tulip adapter at 0xd800.
Digital DC21041 Tulip chip registers at 0xd800:
 0x00: ffe08000   0129f000 0129f200 fc66 fffe2202
ebef
 0x40: fffe 03ff  fffe 50c8 ef01 
0008
 Port selection is full-duplex.
 Transmit started, Receive started, full-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit unit is set to store-and-forward.
  The NWay status register is 50c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Negotiation complete'.


 Let me know if I can provide any more useful information about the
driver problem.

John

[EMAIL PROTECTED]

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: tulip driver BROKEN in 2.4.5-pre4

2001-05-21 Thread Studierende der Universitaet des Saarlandes

Could you post the output of

#tulip-diag -mm -aa -f

with the broken driver?
Some code that's required for Linksys Tulip clones was moved from pnic
specific part into the generic part, perhaps that causes problems.

--
Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: tulip driver BROKEN in 2.4.5-pre4

2001-05-21 Thread Studierende der Universitaet des Saarlandes

Could you post the output of

#tulip-diag -mm -aa -f

with the broken driver?
Some code that's required for Linksys Tulip clones was moved from pnic
specific part into the generic part, perhaps that causes problems.

--
Manfred
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: tulip driver BROKEN in 2.4.5-pre4

2001-05-21 Thread J Brook

 Could you post the output of
 
 #tulip-diag -mm -aa -f
 
 with the broken driver?
 Some code that's required for Linksys Tulip clones was moved
 from pnic specific part into the generic part, perhaps that
 causes problems.

Here is the output from the kernels I've tested to try to get the
driver working:

2.4.4-ac6, this kernel works!

tulip-diag.c:v2.06 1/8/2001 Donald Becker ([EMAIL PROTECTED])
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DC21041 Tulip adapter at 0xd800.
Digital DC21041 Tulip chip registers at 0xd800:
 0x00: ffe08000   0129f000 0129f200 fc66 fffe2002
ebef
 0x40: fffe 03ff  fffe 01c8 ef05 ff3f
0008
 Port selection is half-duplex.
 Transmit started, Receive started, half-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit unit is set to store-and-forward.
  The NWay status register is 01c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Autonegotiation disabled'.

--

2.4.5-pre4 this kernel doesn't work

tulip-diag.c:v2.06 1/8/2001 Donald Becker ([EMAIL PROTECTED])
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DC21041 Tulip adapter at 0xd800.
Digital DC21041 Tulip chip registers at 0xd800:
 0x00: ffe08000   0129e000 0129e200 fc66 fffe2202
ebef
 0x40: fffe 03ff  fffe 50c8 ef01 
0008
 Port selection is full-duplex.
 Transmit started, Receive started, full-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit unit is set to store-and-forward.
  The NWay status register is 50c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Negotiation complete'.

--

2.4.4-ac9 with tulip 1.1.7 driver (from sf.net/projects/tulip)

tulip-diag.c:v2.06 1/8/2001 Donald Becker ([EMAIL PROTECTED])
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DC21041 Tulip adapter at 0xd800.
Digital DC21041 Tulip chip registers at 0xd800:
 0x00: ffe08000   0129f000 0129f200 fc66 fffe2202
ebef
 0x40: fffe 03ff  fffe 50c8 ef01 
0008
 Port selection is full-duplex.
 Transmit started, Receive started, full-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit unit is set to store-and-forward.
  The NWay status register is 50c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Negotiation complete'.


 Let me know if I can provide any more useful information about the
driver problem.

John

[EMAIL PROTECTED]

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/