Subject: detecting a WaveLAN card
To: None <current-users@netbsd.org>
From: Brook Milligan <brook@biology.nmsu.edu>
List: current-users
Date: 02/20/2001 23:40:32
I am trying to get my kernel to detect a Lucent WaveLAN card in
Lucent's ISA-PCMCIA adapter. In one machine (old 486 with VLB/ISA
slots), detection works fine. In another (with different hardware:
AUSU P3B-F motherboard with 686, AGP/PCI/ISA slots) it doesn't. In
the machine that works, I get the following probe messages from a
kernel with option PCMCIADEBUG and with appropriate variables set to 1
in both pcmcia.c and pcmcia_cis.c:
pcic1 at isa0 port 0x3e2-0x3e3 iomem 0xe0000-0xe3fff
pcic1: controller 0 (Intel 82365SL Revision 1) has sockets A and B
pcic1: controller 1 (Intel 82365SL Revision 1) has no sockets
pcmcia0 at pcic1 controller 0 socket 0
pcmcia1 at pcic1 controller 0 socket 1
pcic1: controller 0 detecting irqs with mask 0xdeb8:..9..10..11
pcic1: using irq 9 for socket events
cis mem map c0614000
pcmcia0: CIS tuple chain:
CISTPL_DEVICE type=null speed=null
01 03 00 00 ff
CISTPL_DEVICE_A type=sram speed=ext
17 04 67 5a 08 ff
unhandled CISTPL 1d
1d 05 01 67 5a 08 ff
CISTPL_VERS_1
15 50 05 00 4c 75 63 65 6e 74 20 54 65 63 68 6e
6f 6c 6f 67 69 65 73 00 57 61 76 65 4c 41 4e 2f
49 45 45 45 00 56 65 72 73 69 6f 6e 20 30 31 2e
30 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 ff
CISTPL_MANFID
20 04 56 01 02 00
CISTPL_FUNCID
21 02 06 00
unhandled CISTPL 22
22 02 01 07
unhandled CISTPL 22
22 05 02 40 42 0f 00
unhandled CISTPL 22
22 05 02 80 84 1e 00
unhandled CISTPL 22
22 05 02 60 ec 53 00
unhandled CISTPL 22
22 05 02 c0 d8 a7 00
unhandled CISTPL 22
22 02 03 07
unhandled CISTPL 22
22 08 04 06 00 02 2d 04 dd 07
unhandled CISTPL 22
22 02 05 01
CISTPL_CONFIG
1a 07 03 01 e0 03 00 00 01
CISTPL_CFTABLE_ENTRY
1b 0f c1 01 19 76 c5 4b d5 19 36 36 05 46 7f ff
ff
CISTPL_END
ff
cis mem map c0614000
CISTPL_LINKTARGET expected, code 8f observed
pcmcia0: CIS version PC Card Standard 5.0
pcmcia0: CIS info: Lucent Technologies, WaveLAN/IEEE, Version 01.01,
pcmcia0: Manufacturer code 0x156, product 0x2
pcmcia0: function 0: network adapter, ccr addr 3e0 mask 1
pcmcia0: function 0, config table entry 1: I/O card; irq mask ffff; iomask 6, iospace 0-3f; io16 irqpulse irqlevel
wi0 at pcmcia0 function 0
pcmcia0: ++enabled_count = 1
pcmcia0: function 0 CCR at 0 offset 3e0: 41 80 22 ff, ff ff ff ff, ff
port 0x380-0x3bf
wi0: address 00:02:2d:04:dd:07
pcmcia0: --enabled_count = 0
From the machine that doesn't detect the card I get the following
probe messages (also from a similar kernel):
pcic1 at isa0 port 0x3e2-0x3e3 iomem 0xe0000-0xe3fff
pcic1: controller 0 (Intel 82365SL Revision 1) has sockets A and B
pcic1: controller 1 (Intel 82365SL Revision 1) has no sockets
pcmcia0 at pcic1 controller 0 socket 0
pcmcia1 at pcic1 controller 0 socket 1
biomask eb6d netmask ef6d ttymask ffef
pcic1: controller 0 detecting irqs with mask 0xdeb8:..3..9..11..15
pcic1: using irq 3 for socket events
cis mem map c02b7000
pcmcia0: CIS tuple chain:
CISTPL_END
ff
cis mem map c02b7000
CISTPL_LINKTARGET expected, code ff observed
Can anyone provide guidance in how to figure out why one system
detects a tuple chain and one does not? Or in how to get the second
system to recognize this card? Are there any interactions with other
devices that must be considered?
All suggestions on where to go from here are welcome. Thanks for your
help.
Cheers,
Brook