[tulip-bug] cnet, linksys, and tulip

[Balazs Sallay]

I have a CNet Pro 200 card, which worked just fine with the
dmfe.o module under Suse 7.0 and 2.2.16. I recently put there a
Linksys LNE100TXv4 card as eth1 and tried to use it with the
tulip driver, but the two driver didn't work at the same time. I
suspect that the tulip driver tries to manage the CNet card on
eth0, but it can't. Same problems with kernel 2.4.5, though once
in many times it looked like the tulip driver (with the absence
of dmfe) managed the CNet card correctly. Is there a way to tell
the tulip driver to leave the CNet card alone? 

Here is why I think that. Lines beginning with > are a root
shell, the rest come from kern.log:

> modprobe -r dmfe
> modprobe -r tulip
> modprobe tulip
Jun 13 13:30:33 cinober kernel: tulip.c:v0.92 4/17/2000  Written
by Donald Becker <becker@scyld.com>
Jun 13 13:30:33 cinober kernel:  
http://www.scyld.com/network/tulip.html
Jun 13 13:30:33 cinober kernel:   The PCI BIOS has not enabled
the device at 0/80!  Updating PCI command 0005->0007.
Jun 13 13:30:33 cinober kernel: eth0: Digital DS21140 Tulip rev
49 at 0xcc82b000, 00:00:AD:75:AE:F9, IRQ 12.
Jun 13 13:30:33 cinober kernel: eth0:  EEPROM default media type
Autosense.
Jun 13 13:30:33 cinober kernel: eth0:  Index #0 - Media MII
(#11) described by a 21140 MII PHY (1) block.
Jun 13 13:30:33 cinober kernel: eth0:  Index #1 - Media
100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
Jun 13 13:30:33 cinober kernel: eth0:  Index #2 - Media 10baseT
(#0) described by a 21140 non-MII (0) block.
Jun 13 13:30:33 cinober kernel: eth0:  Index #3 - Media 10baseT
(#0) described by a 21140 non-MII (0) block.
Jun 13 13:30:33 cinober kernel: eth0:  Index #4 - Media
100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
Jun 13 13:30:33 cinober kernel: eth0:  Index #5 - Media
100baseFx (#7) described by a 21140 non-MII (0) block.
Jun 13 13:30:33 cinober kernel: eth0:  MII transceiver #1 config
1000 status 7829 advertising 01e1.
Jun 13 13:30:33 cinober kernel: eth1: ADMtek Comet rev 17 at
0xcc86b000, 00:04:5A:44:BA:77, IRQ 9.

> modprobe -r dmfe
> modprobe -r tulip
> modprobe dmfe
...
> modprobe tulip
Jun 13 13:32:57 cinober kernel: tulip.c:v0.92 4/17/2000  Written
by Donald Becker <becker@scyld.com>
Jun 13 13:32:57 cinober kernel:  
http://www.scyld.com/network/tulip.html
Jun 13 13:32:57 cinober kernel:   The PCI BIOS has not enabled
the device at 0/80!  Updating PCI command 0005->0007.
Jun 13 13:32:57 cinober kernel: eth1: Digital DS21140 Tulip rev
49 at 0xcc86d000, 00:00:AD:75:AE:F9, IRQ 12.
Jun 13 13:32:57 cinober kernel: eth1:  EEPROM default media type
Autosense.
Jun 13 13:32:57 cinober kernel: eth1:  Index #0 - Media MII
(#11) described by a 21140 MII PHY (1) block.
Jun 13 13:32:57 cinober kernel: eth1:  Index #1 - Media
100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
Jun 13 13:32:57 cinober kernel: eth1:  Index #2 - Media 10baseT
(#0) described by a 21140 non-MII (0) block.
Jun 13 13:32:57 cinober kernel: eth1:  Index #3 - Media 10baseT
(#0) described by a 21140 non-MII (0) block.
Jun 13 13:32:57 cinober kernel: eth1:  Index #4 - Media
100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
Jun 13 13:32:57 cinober kernel: eth1:  Index #5 - Media
100baseFx (#7) described by a 21140 non-MII (0) block.
Jun 13 13:32:57 cinober kernel: eth1:  MII transceiver #1 config
1000 status 782d advertising 01e1.
Jun 13 13:32:57 cinober kernel: eth2: ADMtek Comet rev 17 at
0xcc87a000, 00:04:5A:44:BA:77, IRQ 9.





__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/