[tulip-bug] Problem with 2.2.18
Hidvegi
hzoli@austin.ibm.com
Wed, 13 Dec 2000 02:22:55 -0600 (CST)
I've just installed 2.2.18 and recompiled and installed tulip.c on my
Thinkpaf 600E. This worked fine with 2.2.18, but now I get the
messages below when I insert a LinkSys PCM200. Note that if reports
two interfaces, eth0 and eth1, but eth0 cannot be used (resource
temporarily unavailable). But eth1 works fine. eth0 and eth1 has
different hw address, the address of eth1 is the correct one. When I
use the driver under 2.2.17 there is only eth0. I tried the standard
driver in ncftp ftp://ftp.scyld.com/pub/network/ and also the one in
ncftp ftp://ftp.scyld.com/pub/network/test/, both has this problem.
Zoli
cs: cb_alloc(bus 2): vendor 0x13d1, device 0xab03
cb_shim.c:v1.00 4/15/2000 Donald Becker <becker@scyld.com>
http://www.scyld.com/linux/drivers.html
cs: cb_free(bus 2)
cs: cb_alloc(bus 2): vendor 0x13d1, device 0xab03
cb_shim.c:v1.00 4/15/2000 Donald Becker <becker@scyld.com>
http://www.scyld.com/linux/drivers.html
tulip.c:v0.92p 11/28/2000 Written by Donald Becker <becker@scyld.com>
http://www.scyld.com/network/tulip.html
The PCI BIOS has not enabled the device at 2/0! Updating PCI command 0002->00
06.
eth0: ADMtek Centaur-C (Linksys) rev 17 at 0xca067000, 02:F9:00:F0:02:F9, IRQ 0.
PCI: Increasing latency timer of device 02:00 to 64
cs: cb_config(bus 2)
fn 0 bar 1: io 0xa00-0xaff
fn 0 bar 2: mem 0x60060000-0x600603ff
fn 0 rom: mem 0x60040000-0x6005ffff
irq 11
cs: cb_enable(bus 2)
bridge io map 0 (flags 0x21): 0xa00-0xaff
bridge mem map 0 (flags 0x1): 0x60040000-0x60060fff
Found a ADMtek Centaur-C (Linksys) at 2/0 address 0x60060000->0xca069000 IRQ 11.
ADMtek Centaur-C (Linksys) at 2/0 command 0x7.
eth1: ADMtek Centaur-C (Linksys) rev 17 at 0xca069000, 00:E0:98:75:C7:6F, IRQ 11
.
eth1: MII transceiver #1 config 3000 status 7849 advertising 01e1.
eth1: Setting full-duplex based on MII #1 link partner capability of 45e1.