I am running SuSE. 9.0 professional on a Dell Inspiron 8100 laptop. I have a d-link AirPlus card (DWL-G650). I have been trying for days to get this to work. I have tried to compile and install the acx-100 drivers and while reading through the readme I found that this card wasn't supported. I have been searching through the forums and no luck with any of it. I have also tried messing with the madwifi project, but also with that I have had no luck. Any help on this would be appreciated


-Nowhere

Moved: This thread is more suitable in Wireless Networking and has been moved accordingly to help your thread/question get the exposure it deserves.

Somebody in the HCL list here said the madwifi drivers worked. But they don't seem to for you so this link might help.

http://prism54.org/supported_cards.php

I have the same type of card. There are 3 different versions of it also: A, B, and C
I have the C. you might have that one also

When I installed the madwifi drivers it installed the iw commands and stuff but it doesn't detect the card. When I do an lsmod I don't see anything in there. Can you tell me the exact steps you took to get your card working with the madwifi drivers? I would appreciate it.

try using lspci to detect the card
If you look on the back of the card you can find out which type it is. The lettering is usually in or near the S/N number
What I did was install madwifi, then configured the card like it said in the write up, but it didnt work. I had taken the card out and rebooted then reinserted the card after liunux was fully booted and logged in. Then I noticed the light on the card was on. So I tried a ifconfig ath0 up and I got both lights blinking together. Then I did a dhcpcd ath0 to get an IP address
You will have to download dhcpcd from freashmeat.net

Tried following the directions exactly and loading the modules in the order they were listed.

This is what happens when I use lspci
05:00.0 Ethernet controller: Unknown device 168c:0013 (rev 01)

and the first two modules load just fine, until I get to the third one.
insmod ath_pci.o
ath_pci.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

Any ideas what would be preventing that module from loading up?