Next-in-Thread Next Message

Warning FYI Linksys PCMPC200 V2 card; different from older versions 

Forum: PCMCIA Network Adapter Issues
Date: 2000, Aug 06
From: Nik Conwell nikc

FYI - Be aware that the Linksys EtherFast 10/100 CardBus PCMPC200 has changed and is now V2 which apparently isn't supported yet. The box has blue edges and says something like new V2 in the upper left corner.


I'm runing RH 6.2, kernel-pcmcia-cs-2.2.16-3.

kernel: Linux PCMCIA Card Services 3.1.8
kernel:   kernel build: 2.2.16-3 #1 Mon Jun 19 18:10:14 EDT 2000
kernel: Intel PCIC probe:
kernel:   Toshiba ToPIC97 PCI-to-CardBus at bus 0 slot 19, mem 0x68000000, 2 sockets
kernel:     host opts [0]: [slot 0xf0] [ccr 0x10] [cdr 0x86] [rcr 0x02] [no pci irq] [l at 168/176] [bus 20/20]
kernel:     host opts [1]: [slot 0xf0] [ccr 0x20] [cdr 0x86] [rcr 0x02] [no pci irq] [l at 168/176] [bus 21/21]
kernel:     ISA irqs (default) = 3,4,5,7,9,10,12 polling interval = 1000 ms
pcmcia: cardmgr. cardmgr[488]: starting, version is 3.1.8 rc: Starting pcmcia succeeded cardmgr[488]: watching 2 sockets
kernel: cs: IO port probe 0x1000-0x17ff: clean.
kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x480-0x48f 0x4d0-0x4d7
kernel: cs: IO port probe 0x0a00-0x0aff: clean.
inet: inetd startup succeeded kernel: cs: cb_alloc(bus 20): vendor 0x13d1, device 0xab02 cardmgr[488]: initializing socket 0 cardmgr[488]: unsupported card in socket 0 cardmgr[488]: product info: "CardBus", "Fast Ethernet", "V1.0", "" cardmgr[488]: manfid: 0x13d1, 0xab02 function: 6 (network)

The manfid is different from the pcmcia config for the EtherFast 10/100. Being a tricky guy, I tried adding an entry for the new manfid, using the tulip_cb driver, and was rewarded with:

kernel: cs: cb_config(bus 20)
kernel:   fn 0 bar 1: io 0xa00-0xaff
kernel:   fn 0 bar 2: mem 0x60060000-0x600603ff
kernel:   fn 0 rom: mem 0x60040000-0x6005ffff
kernel: tulip_attach(bus 20, function 0)
kernel: tulip.c:v0.91 4/14/99 (modified by for XIRCOM CBE, fixed by Doug Ledford)
kernel: eth0: Digital DS21143 Tulip rev 17 at 0xa00, 10:80:00:80:00:80, IRQ 3.
kernel: eth0:  EEPROM default media type 10baseT.
kernel: eth0:  MII transceiver #1 config 3000 status 7849 advertising 01e1.
cardmgr[1210]: executing: './network start eth0' pumpd[1242]: starting at (uptime 0 days, 0:18:06) Sat Aug 5 17:59:54 2000
kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
kernel: current->tss.cr3 = 02721000, %cr3 = 02721000
kernel: *pde = 00000000
kernel: Oops: 0000
kernel: CPU:    0
kernel: EIP:    0010:[lockd:__insmod_lockd_S.bss_L444+161553/21737519]
kernel: EFLAGS: 00010246
kernel: eax: fffffff8   ebx: ffffffff   ecx: 00000000   edx: c3ffab58
kernel: esi: 00000000   edi: c593ada0   ebp: c2723e4c   esp: c2723e00
kernel: ds: 0018   es: 0018   ss: 0018
kernel: Process pump (pid: 1242, process nr: 48, stackpage=c2723000)
kernel: Stack: c593ada0 00000008 00000286 c26e1000 00000246 00000003 00000008 00000000
kernel:        00000000 00000282 c593ada0 c3ffab58 00000a00 c3ffab50 c0383800 00000a00
kernel:        c593ada0 c01ded87 00000214 c2723ea0 c6857c04 c593ada0 00000001 c593ada0
kernel: Call Trace: [__delay+19/40] [lockd:__insmod_lockd_S.bss_L444+160452/21738620] [lockd:__insmod_lockd_S.bss_L444+161399/21737673] [dev_open+32/128] [dev_change_flags+84/264] [devinet_ioctl+635/1536] [sock_ioctl+0/32]
kernel:        [sk_alloc+17/60] [inet_ioctl+402/524] [sock_ioctl+26/32] [sys_ioctl+414/452] [system_call+52/56]
kernel: Code: 8a 06 8b 55 08 88 42 3c 83 7d 0c 00 74 15 8b 45 e8 0f b6 48
cardmgr[1210]: + Determining IP information for eth0... done.

The card wasn't accessible after that...

I took the card back to CompUSA and exchanged it for a not V2 PCMPC200 (which they had tried to unload on me first, but I was too smart for them...). The older PCMPC200 works just fine in my system.

I've sent a copy to the Linksys tech support as well(

Keep up the good work. I'm eternally grateful. -nik

Next-in-Thread Next Message

Select this message: FYI Linksys PCMPC200 V2 card; different from older versions

Message Administration

This form allows you to delete, move, or copy one or more messages. You can move messages by copying and deleting the original. The action will be applied to the messages you select above and all replies to those selected messages.

If you want to copy or move messages, specify the HyperNews path of a destination forum or message that all messages will be copied or moved to. The destination must already exist, so maybe create it first.

Path of Destination (a Forum or Message): (e.g. "test")

Notify Subscribers at destination

If you want to delete messages (the default), specify that here. If you want to move messages, you need to delete the original messages; placeholders will be left pointing to where they were moved.

Delete Messages

Caution: After deleteing messages (the default), if you have not copied them (i.e. no destination above), then the selected messages are not be recoverable.

Members Subscribe No Admin Mode Show Frames Help for HyperNews at 1.10
[ Edit This Forum ]