From: Ed Schaller <schallee@darkmist.net>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] quad tulip now not functional in 2.4.20
Date: Sun, 15 Dec 2002 23:45:12 -0700 [thread overview]
Message-ID: <20021216064512.GA1983@darkmist.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 3412 bytes --]
I have a B180 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).
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.
Linux version 2.4.20-pa13 (root@landmine) (gcc version 3.0.4) #3 Tue Dec 10 01:35:34 MST 2002
...
Linux Tulip driver version 0.9.15-pre12 (Aug 9, 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 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
eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
Linux version 2.4.19-32 (root@j5k) (gcc version 3.0.4) #1 Fri Nov 22 23:27:00 MST 2002
...
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.
tulip2: EEPROM default media type Autosense.
tulip2: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
tulip2: MII transceiver #1 config 3100 status 7849 advertising 01e1.
eth2: Digital DS21140 Tulip rev 34 at 0xed00, 00:00:D1:1B:C8:B5, IRQ 99.
tulip3: EEPROM default media type Autosense.
tulip3: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
tulip3: MII transceiver #1 config 3100 status 7849 advertising 01e1.
eth3: Digital DS21140 Tulip rev 34 at 0xee00, 00:00:D1:1B:C8:95, IRQ 96.
tulip4: EEPROM default media type Autosense.
tulip4: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
tulip4: MII transceiver #1 config 3100 status 7849 advertising 01e1.
eth4: Digital DS21140 Tulip rev 34 at 0xef00, 00:00:D1:1B:70:33, IRQ 97.
...until ifconfig eth0-eth4
eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth3: Setting full-duplex based on MII#1 link partner capability of 41e1.
eth4: Setting full-duplex based on MII#1 link partner capability of 41e1.
>>>------>
--
+-------------+-----------------------+---------------+
| Ed Schaller | Dark Mist Networking | psuedoshroom |
+-------------+-----------------------+---------------+
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2002-12-16 6:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 6:45 Ed Schaller [this message]
2002-12-16 23:11 ` [parisc-linux] quad tulip now not functional in 2.4.20 Grant Grundler
2002-12-17 7:12 ` jsoe0708
2002-12-18 16:58 ` Grant Grundler
2002-12-18 20:27 ` Ed Schaller
2002-12-19 17:37 ` jsoe0708
2002-12-17 10:43 ` jsoe0708
2002-12-17 15:14 ` jsoe0708
2002-12-17 17:42 ` jsoe0708
2002-12-17 18:19 ` Grant Grundler
2002-12-18 6:30 ` jsoe0708
2002-12-18 17:01 ` Grant Grundler
2002-12-19 14:27 ` Ryan Bradetich
-- strict thread matches above, loose matches on Subject: below --
2003-01-30 10:59 "Beerse, Corné"
2003-01-30 14:45 ` Michael S.Zick
2003-01-30 15:02 ` Randolph Chung
2003-01-30 15:34 ` Michael S.Zick
2003-01-30 15:38 ` Thibaut VARENE
2003-01-30 15:36 ` Michael S.Zick
2003-01-30 19:23 ` Grant Grundler
2003-02-03 9:40 ` Peter Lavender
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=20021216064512.GA1983@darkmist.net \
--to=schallee@darkmist.net \
--cc=parisc-linux@lists.parisc-linux.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.