Hi folks,
First post so be kind

I've been trying to get a wireless networking card working under debian testing. I'm using a Toshiba A60 laptop, which uses a Texas Instruments PCI1410 PC card Cardbus Controller.

My problem is this: the computer will not recognise that there is a card in the slot when doing lspci or cardctl (output listed below). The card i'm trying to use is a Linksys WPC54G Cardbus 802.11g. I'm not sure if this is a problem with the TI cardbus bridge or the wireless card, and if it's the card, tell me off and i'll take it to the networking forum

Card works under windows (dualboot) so i assume the hardware works in some fashon.

I've tried mindlessly installing the ndiswrapper driver for the card out of desparation, but that obviously didn't work .

Anywho various outputs are below that might help, let me know if there's something i've missed, and i'll provide it

Thanks


uname -a
---
Linux client04 2.6.8-20050202 #1 Wed Feb 2 11:48:46 GMT 2005 i686 GNU/Linux


lspci
---
0000:00:00.0 Host bridge: ATI Technologies Inc: Unknown device cab3 (rev 05)
0000:00:01.0 PCI bridge: ATI Technologies Inc PCI Bridge [IGP 340M]
0000:00:13.0 USB Controller: ATI Technologies Inc: Unknown device 4347 (rev 01)
0000:00:13.1 USB Controller: ATI Technologies Inc: Unknown device 4348 (rev 01)
0000:00:13.2 USB Controller: ATI Technologies Inc: Unknown device 4345 (rev 01)
0000:00:14.0 SMBus: ATI Technologies Inc ATI SMBus (rev 18)
0000:00:14.1 IDE interface: ATI Technologies Inc: Unknown device 4349
0000:00:14.3 ISA bridge: ATI Technologies Inc: Unknown device 434c
0000:00:14.4 PCI bridge: ATI Technologies Inc: Unknown device 4342
0000:00:14.5 Multimedia audio controller: ATI Technologies Inc IXP150 AC'97 Audio Controller
0000:00:14.6 Modem: ATI Technologies Inc: Unknown device 434d (rev 01)
0000:01:05.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4437
0000:02:06.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 02)
0000:02:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
0000:02:0a.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)


lspci -vvv (cardbus bridge section)
---
0000:02:06.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 02)
Subsystem: Toshiba America Info Systems: Unknown device ff10
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 168, Cache Line Size: 0x20 (128 bytes)
Interrupt: pin A routed to IRQ 19
Region 0: Memory at 10001000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=02, secondary=03, subordinate=06, sec-latency=176
Memory window 0: 10400000-107ff000 (prefetchable)
Memory window 1: 10800000-10bff000
I/O window 0: 00004400-000044ff
I/O window 1: 00004800-000048ff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt- PostWrite+
16-bit legacy interface ports at 0001


cardctl ident
---
Socket 0:
no product info available

I just got a Linksys WPC54GS working under Debian with 2.8.6-2 the other day (on a Toshiba Tecra). So... maybe I can help.

First, I don't think the device will show up in lspci (my cardbus cards don't). They should, I think, show up in cardctl, though. Unfortunately, I never checked cardctl to see what the output was before I installed everything... and right now I can't put the wireless card in to test.

Second, I did have to use the ndiswrapper to get my card working. My card was a GS, though... maybe a WPC54G doesn't need ndiswrapper. It was sort of a pain (particularly since the debian package of the source code was incomplete... I tried building it three times before I realized that I would have to download the tarball).

My suspicion is that ndiswrapper is the way you'll need to go.

EDIT: And after starting up with my Linksys card in the PCMCIA slot, but without modprobing the drivers, I get the same thing as you for 'cardctl ident'. In other words, the fact that cardctl ident isn't showing any information does not indicated a hardware problem.