Ok, so i just got an Orinoco 11 b/g WiFi card (silver) and i am at a loss as how to get it to work. I am running Red Hat 9.0 on my laptop and tried running the wizard, but the only 3 drivers for Orinoco don't allow me to acticate the card. The KDE control center does not reconise the card all it says is that theslot is empty.......help......please

When Proxim bought up Orinoco, they change the chipset and not the name. Should be used to that one by now... Dlink, Linksys, etc... they all go in for this evil.

Let's find out what's actually under the hood:

/sbin/cardctl ident

and..

What's the EXACT model name of the card?

Cheers,

Finegan

When i run that comand from the terminal all i get is
Socket 0:
no product info available
and the exact model of the card is 8471-WD
thaks,
Mike

No Product info... oh I'm an idiot, its a G card so its cardbus not pcmcia straight, try this one:

/sbin/lspci

Its Cardbus, so instead of pcmcia-cs having to bind a module to it, its part of the normal old pci subsystem, you modprobe modules to it just like it was a regular pci device. I'll look around with the exact model #, but the lspci is going to be exact info.

Cheers,

Finegan

Ahhh.... I found a report of it working with the www.linuxant.com driverloader, which I hate with a passion, but at least it works there. I'm still looking.

Cheers,

Finegan

I'm fairly certain that your card uses the Atheros chipset and will require the MadWiFi drivers.
SourceForge Page
MadWiFi Wiki

does anyone know what chipset proxim's 802.11 a/b GOLD combo uses?

Also Atheros, I believe.

Yeah, now that the big bloody link over at linux-wlan works again:

http://www.linux-wlan.org/docs/wlan_adapters.html.gz

Its should also have atheros stamped on its name under /sbin/lspci too.

Cheers,

Finegan

Is there a place to get the proper madwifi drivers besides "cvs -z3 -dserver:anonymous@cvs.sourceforge.net:/cvsroot/madwifi co madwifi" as I don't have a linux system connected to the net yet? I need to download via HTTP.

I guess I should further clarify my intent.. I've already downloded a version from http://madwifiwiki.thewebhost.de/wiki/FrontPage that is giving me a bunch of "unresolved symbols" when I go to install the modules for the driver. I'm guessing this is because the driver I downloaded was compiled for another kernal. I'm using 2.4.20-8.

The download on the Wiki is a source tarball. It compiled fine for me on Slackware with 2.4.24. Unfortunately, I don't have a card to test with madwifi, so I can't go much further. You have the kernel source, headers and compiler loaded, right?

It looks as though the Sourceforge page is pretty broken for the project right now. I don't know of an alternate source for the driver.

bm3780,
I don't have PM permissions on this board or an email for you, so I grabbed the CVS, tarred it up and put it here: http://members.cox.net/general.speci...fi_cvs.tar.bz2
It's dated 1/13/2004.
I'll leave it up for a bit. Hope it helps.

I got an error on the make. About one-third of the way down it says:

uudecode < ../hal/linux/i386-elf.hal.o.uu
uudecode: stdin: No 'end' line
make[1]: ***[hal.o] Error 1

Did you see anything like this? I didn't encounter this error when I was using the old version from wiki. When I try to modprobe ath_pci, I get this:
------------------------------------------------
Module ath_hal loaded, with warnings
/lib/modules/2.4.20-8/net/wlan.o: unresolved symbol eth_type_trans
/lib/modules/2.4.20-8/net/wlan.o: unresolved symbol __kfree_skb
/lib/modules/2.4.20-8/net/wlan.o: unresolved symbol alloc_skb
...
/lib/modules/2.4.20-8/net/wlan.o: insmod /lib/modules/2.4.20-8/net/wlan.o failed
/lib/modules/2.4.20-8/net/wlan.o: insmod ath_pci failed


Looking at dmesg, I see this:
-------------------------------------
Linux Kernal Card Services 3.2.11
options: [pci] [cardbus] [pm]
PCI: Found IRQ 9 for device 00:0b.0
Yenta IRQ list 0000, PCI irq9
Socket status: 10000061
cs: cb_alloc(bus 2): vendor 0x168c, device 0x0012
PCI: Enabling device 02:00.0 (0000 -> 00002)
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x0a00-ox0aff: clean
ath_hal: 0.9.5.3 BETA (Sam Leffler <sam@errno.com> )
ath_hal: driver unloaded

There's no point trying to insmod anything if you get errors during the make. Those need to be fixed first.

I did not get any errors compiling the drivers with either the CVS or the Wiki linked versions. My suspicion is that you're missing a package or two needed to build the drivers, although I cannot tell from the error. Maybe someone a little smarter can contribute on that point.

edit: stdin is in the kernel headers. Again, do you have the development packages, kernel source and headers installed?