RE: Bizarre Linksys PCMPC200 problem

>> I'm having some trouble getting a Linksys PCMPC200 (v2 I think) to 
>> work in a Toshiba Satellite Pro 490CDT. The kernel picks up the card 
>> during boot, and lspci says it's definitely there:
>
>What driver version are you using?
>What is the detection message?
>
>> 12:00.0 Ethernet controller: Linksys: Unknown device ab08 (rev 11)
>> 	Subsystem: Linksys: Unknown device ab08
>...
>> The tulip driver won't pick it, claiming the usual 'no such device'. 
>> Here's what tulip-diag says:
>
>This is an ADMtek Centaur-C.  The modifications in tulip driver
distributed with most 2.4 kernel versions are
>flawed, and that driver will not work with this chip.  You will need
the unmodified driver from Scyld.
>
>> tulip-diag.c:v2.16 12/17/2002 Donald Becker ([email protected])  
>> http://www.scyld.com/diag/index.html
>> Assuming a ADMtek AL985 Centaur (Linksys CardBus v2) adapter at 
>> 0x4000. ADMtek AL985 Centaur (Linksys CardBus v2) chip registers at 
>> 0x4000:

I'm running kernel 2.4.21-rc1-ac4 on a slackware 9.0 base system, here
is some relevant dmesg output:

Linux Kernel Card Services 3.1.22
  options:  [pci] [cardbus] [pm]
Intel PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.
Yenta IRQ list 0000, PCI irq11
Socket status: 30000020
Yenta IRQ list 0000, PCI irq11
Socket status: 30000006
Yenta IRQ list 0498, PCI irq11
Socket status: 30000011
Yenta IRQ list 0498, PCI irq11
Socket status: 30000007

...

cs: cb_alloc(bus 18): vendor 0x1737, device 0xab08
PCI: Enabling device 12:00.0 (0000 -> 0003)

...

Starting PCMCIA Services:
cardmgr[49]: Watching 4 sockets
cardmgr[50]: starting, version is 3.2.4
cardmgr[50]: socket 0: CardBus hotplug device

thats it - no modules are loaded.

As you mentioned, the stock 0.9.15-pre12 tulip driver fails to detect
anything. I downloaded netdrivers-3.4.tgz from Scyld, and did a "make &&
make install" (I noticed that the old tulip.o sat in its own dir
/lib/modules/2.4.21-rc1-ac4/kernel/drivers/net/tulip/ so I deleted it
manually.) upon insmod, the new 0.96 tulip driver also fails to detect
the linksys. However, cb_shim.o has unresolved symbols when depmod does
its thing, so "insmod cb_shim.o" gives:

cb_shim.o: unresolved symbol unregister_driver
cb_shim.o: unresolved symbol register_driver

Is this maybe why tulip.o is not detecting the linksys? do I need to I
need to fix this?

Kind Regards,

Matthijs Vrolijk

_______________________________________________
tulip mailing list, [email protected]
To change to digest mode or unsubscribe visit
http://www.scyld.com/mailman/listinfo/tulip