i have an inspiron 1100 w/ rh9.0

loading of pcmcia results in [ok] at boot up, but when i examine dmesg i see that under Linux Kernel Card Services 3.1.22
Intel PCIC probe not found is shown. after that it says
PCI: Found IRQ 10 for device 02:04.0 and so on.
Yenta IRQ list 0000 PCI irq10
Socket status: 30000020
cs: cb_alloc(bus 3): vendor 0x1317, device 0x8201

when i do a cardctl ident my pcmcia wireless card is not listed.

i have tried to remove pcmcia from my kernel, recompiling it then installing pcmcia_cs. that got cardctl ident to find 0x1317 0x8201 as my manuf addresses, but then the orinoco_cs driver still wouldnt load.

so how can i get my PCMCIA working?

EDIT: Ok, I just checked the pci id of your card and you do indeed have a version 2 DWL-650, I have the same card and it works just fine check out this page for how to get it working. I put this page up because so many people are confused between version 1 and 2 of this card.

A question: did you buy this card because it was listed as working with linux in the "supported cards list"? I'm sort of assuming that's where you got the orinoco_cs info from.

Also, if you do have this card and my howto works for you on redhat, pls let me know so I can update it with a credit to you for the redhat testing, as well as if it doesn't.

akabeavis, thx for your help. heres a little progress report

pcmcia now works (i removed the pcmcia from the kernel, recompiled, then installed pcmcia_cs) . got my broadcom 4400 ethernet working too finally.
however my wireless card does not work. its manufacturer id is detected

[root@localhost pcmcia]# /sbin/cardctl ident
Socket 0:
no product info available
PCI id: 0x1317, 0x8201


ive installed wireless tools 25. ive compiled the 8211.o, the directory i used is
/lib/modules/2.4.20-8custom/pcmcia/

but upon depmod -a i get the following
[root@localhost pcmcia]# depmod -a
depmod: *** Unresolved symbols in /lib/modules/2.4.20-8custom/pcmcia/8211.o

again im in redhat 9.0, using dell inspiron 1100. generic wireless card with fcc id: mq4wb2k. i will try to search fcc.gov tomorrow, right now it seems to be down for me.

it's not over....yet ...

I'm sorry, and obviously I'll have to add this info to my little "howto", I too got/get unresolved symbols when doing a depmod -a, in fact I get that response for both 8211.o and pcmf502rd.o, and yet both are entirely functional. I apologize for that omission, I should have realized that any experienced linux-er would probably stop at that point.

now that you've done the depmod, first, do an ifconfig -a, then modprobe the 8211, then ifconfig -a again, hopefully you'll see another device registered on the second ifconfig.

ps: here's the relevant section after doing an lspci -vv on my box with the card plugged in:
I'd be curious what yours says, be aware that the "D-Link Air Wireless Network Card model DWL-650v2" string is simply a regurgitation of what I placed in my /usr/share/pci.ids. The second string referencing D-Link: "D-Link System Inc:", is coming from the card, not me.

01:00.0 Network controller: Linksys D-Link Air Wireless Network Card model DWL-650v2 (rev 11)
Subsystem: D-Link System Inc: Unknown device 3502
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: 64 (16000ns min, 32000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 4000 [size=256]
Region 1: Memory at 10400000 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at 10000000 [size=128K]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=100mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

here's an lspci -n:
01:00.0 Class 0280: 1317:8201 (rev 11), notice the "1317:8201", this is where your numbers (and mine) are coming from, however from the fccid you posted your mfgr appears to be abicom, not dlink.

Addendum:
Since you seem to have had a problem with the FCC site, (it is unresponsive at times, I suppose I should have mentioned that also.) anyway, here's a pic of your card's internals. This is a screencap of a portion of a pdf file returned when I input the FCCID you posted.

Sadly, it's not a real close-up, but you can still make out "ADMtek" on the large chip, perhaps you can zoom/sharpen and be able to read the rest.

ok so i tried to modprobe the 8211

[root@localhost /]# modprobe 8211
Warning: loading /lib/modules/2.4.20-8custom/pcmcia/8211.o will taint the kernel: no license
See http://www.tux.org/lkml/#export-tainted for information about tainted modules
/lib/modules/2.4.20-8custom/pcmcia/8211.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-8custom/pcmcia/8211.o: insmod /lib/modules/2.4.20-8custom/pcmcia/8211.o failed
/lib/modules/2.4.20-8custom/pcmcia/8211.o: insmod 8211 failed


i believe the problem is actually not with thte 8211, since when i do a lspci -vv with the card plugged in i get the following:

[root@localhost /]# lspci -vv
pcilib: Cannot open /proc/bus/pci/03/00.0
lspci: Unable to read 64 bytes of configuration space.

if i unplug the wireless card the lspci works fine. thanks for the info on my card, maybe i will try looking for other drivers. but my guess is that the problem lies elsewhere.. what is this /usr/share/pci.ids file? maybe i need to edit it? (mine is actually in /usr/share/hwdata/pci.ids)

p.s. if someone is reading this to fix the INTEL PCIC error, the way i fixed that is by doing the following:

http://groups.google.com/groups?hl=e...01%40127.0.0.1

except i substituted make menuconfig for make xconfig since redhat9 didnt install tk for some reason initially. i skipped the loading of the i586 config file also, and just went into the general setup and disabled the pcmcia there.

after that, the new pcmcia_cs package seems to work fine with my inspiron 1100. but my generic wireless card still needs some work.

It's probably not going to help you all that much, as far as I can tell it simply for lookups of the numbers returned from a lspci -n and assigns text strings to them, thus the reason why my D-Link is labelled a Linksys. I edited because I got tired of seeing my card listed as an "unknown Linksys".

Sorry about the paths thing, as you can tell I'm not on redhat, I'm glad you were able to find the file anyway.

One thing you may want to check and it depends on your machine's bios, and perhaps whether your dual booting. You may want to look there for settings related to PCIC, APIC, and PnP (ain't that a silly string of acronyms, ). I've read things here and there that end up pointing to those bios settings as fixing pcmcia issues. (although you've got a 32bit CardBus card there).

the dell bios has no such options, its very limited in terms of what you can actually change. pretty much the boot up sequence and thats it.

well that's not exactly good news. It sounds to me like the 32bit part (ie CardBus) of the whole pcmcia thing is broken, it's been my own sad experience that when compiling a kernel it usually takes me several tries to get everything right, I seem to invariably miss some critical setting. Do you have any other cards you can use to test your setup?