From: J Brook <jbk@postmark.net>
To: linux-kernel@vger.kernel.org
Cc: manfred@colorfullife.com
Subject: Re: tulip driver BROKEN in 2.4.5-pre4
Date: Mon, 21 May 2001 11:50:16 +0000 [thread overview]
Message-ID: <20010521115016.5262.qmail@venus.postmark.net> (raw)
> 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 (becker@scyld.com)
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 ffffffff ffffffff 0129f000 0129f200 fc660000 fffe2002
ffffebef
0x40: fffe0000 ffff03ff ffffffff fffe0000 000001c8 ffffef05 ffffff3f
ffff0008
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 000001c8.
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 (becker@scyld.com)
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 ffffffff ffffffff 0129e000 0129e200 fc660000 fffe2202
ffffebef
0x40: fffe0000 ffff03ff ffffffff fffe0000 000050c8 ffffef01 ffffffff
ffff0008
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 000050c8.
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 (becker@scyld.com)
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 ffffffff ffffffff 0129f000 0129f200 fc660000 fffe2202
ffffebef
0x40: fffe0000 ffff03ff ffffffff fffe0000 000050c8 ffffef01 ffffffff
ffff0008
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 000050c8.
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
----------------
jbk@postmark.net
next reply other threads:[~2001-05-21 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 11:50 J Brook [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-21 9:54 tulip driver BROKEN in 2.4.5-pre4 Studierende der Universitaet des Saarlandes
2001-05-24 2:24 ` Johan Kullstam
2001-05-21 1:37 J Brook
2001-05-23 21:39 ` Lukasz Trabinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010521115016.5262.qmail@venus.postmark.net \
--to=jbk@postmark.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox