Networking :: Dynex DX-WGNBC WiFi Cardbus PCMCIA - How To

This card works out of the box with the ath modules. I'm not sure it's possible to use the ath modules with WPA. Also, the ath modules taint the kernel (not sure what this means).

The following describes how to set it things up to use WPA with ndiswrapper. WEP installation information can be found here.

First, unload the ath modules in this order:

Code Sample

rmmod ath_pci
rmmod ath_rate_sample
rmmod ath_hal

Next, install ndiswrapper (only needs to be done once):

Code Sample

ndiswrapper -i net5211.inf

Probe ndiswrapper:

Code Sample

modprobe ndiswrapper

Check status (not necessary for functionality, but for your piece of mind):

Code Sample

iwconfig
dmesg

Build your WPA config file, using this trimmed down configuration file (ellipses replaced by your settings). I named my config file wpa_supplicant_short.conf:

Code Sample

network={
ssid="..."
psk="..."
}

Start WPA:

Code Sample

wpa_supplicant -B dd -c wpa_supplicant_short.conf -i wlan0 -D ndiswrapper

Run the GUI netcardconfig from the DSL Control Panel once and assign static IP. Gateway and DNS servers get set automatically. Click Apply and have the "Save configuration in the system" option ticked, the utility will create /opt/wlan0.sh for you.

Now, your connection your network should be active.

To persist this and have it fire up every time you boot, add the following to /opt/bootlocal.sh as follows. Make a copy of the wlan0.sh if you want to maintain it manually:

Code Sample

# dynex cardbus wpa
rmmod ath_pci
rmmod ath_rate_sample
rmmod ath_hal
modprobe ndiswrapper
# driver loads up slowly on my hardware, so giving it time to finish
sleep 5
wpa_supplicant -B dd -c /home/dsl/config/wifi/wpa_supplicant_short.conf -i wlan0 -D ndiswrapper
/home/dsl/config/wifi/wlan0.sh &

Now searching for a boot code to disable the ath_ modules from loading up.

taint = using non-free (binary-only) modules

Thank you Curaga.

The steps that I've noted above work well in 4.1RC3.

I'm having trouble with the wpa_supplicant and wlan0.sh calls from bootlocal.sh in v4.1. I've tried many variations, but have found that I can only successfully execute wpa_supplicant with a sudo call from outside bootlocal.sh.

I've created a script file and a desktop symlink to launch it (sudo wpa_supplicant...) but would rather have it execute automatically at startup.

What I've tried, and whether it worked or not:

1) call wpa_supplicant from bootlocal.sh - NO
2) call sudo wpa_supplicant from bootlocal.sh - NO
3) call wpa_supplicant without sudo and not root - NO
4) call sudo wpa_supplicant in aterm - YES
5) call sudo wpa_supplicant from script file - YES

Any help would be appreciated.

Thank you

Maybe $PATH is different at that stage, try specifying the full path? (i.e. /usr/sbin/wpa_supplicant )
Note that you shouldn't require any use of sudo in bootlocal.sh as it is normally executed as root.
As for not loading the modules at start, it probably depends on how you are running DSL.

Next Page...
original here.