How I got the BlueNEXT BN-WD54G wireless USB adapter to work in Debian (testing) Lenny.

The BlueNext BN-WD54G requires the rt73 driver.


I am continuing to play with this device and will update this page with any improvements I make.
Page created on the 25th November 2008

Incase it is of interest my setup is...
CPU =
Intel Core 2 Duo E7300 2.66GHz Socket 775 (1066FSB) 3MB L2 Cache
Mother Board =
ECS G33T-M2 V1.0 Socket 775 Intel G33 Chipset PCI-E
RAM =
Corsair 4GB Kit (2x2GB) DDR2 800MHz/PC2-6400 XMS2 Memory Non-ECC Unbuffered
Linux Kernel is 2.6.26-1-Bigmem

I needed this wifi stick to use WPAPSK TKIP and a static IP.

If you follow the way I installed everything then I guess in a perfect world it should work because mine does.
Things don't always quite work out this way but hopefully this page will help, good luck.


Install this package from synaptic, it has iwconfig and iwpriv in it, these tools are required.
wireless-tools

Download the rt73 driver from...
http://rt2x00.serialmonkey.com/rt73-cvs-daily.tar.gz
Save the file to your /usr/src directory, or in reality save it anywhere but then copy it to your /usr/src directory like this...
sudo cp rt73-cvs-daily.tar.gz /usr/src/

Then change to the /usr/src directory with...
cd /usr/src
and enter..

tar -xvzf rt73-cvs-daily.tar.gz
This will untar the file and create the necessary directories.
Enter the directory created with this... (obviously changing the YYYYMMDD to the date of your version)...
cd rt73-cvs-YYYYMMDDHH/Module
become root by typing this...
sudo bash
Now compile with...
make
followed by...
make install

Now we must bring the network down so we can remove some driver modules not wanted because of conflicts.
sudo ifconfig wlan0 down

Now we remove the following modules...
sudo modprobe -r rt73usb
sudo modprobe -r rt2570
sudo modprobe -r rt2500usb
sudo modprobe -r rt2x00lib
Ignore any messages about modules not existing, if they dont exist all the better.

Now we need to blacklist those modules so that our USB stick will only use the one we want rt73.
sudo gedit /etc/modprobe.d/blacklist
Add the following lines to the bottom of the blacklist file.
blacklist rt73usb
blacklist rt2570
blacklist rt2500usb
blacklist rt2x00lib
Now we need to insert our module with...
sudo modprobe -v rt73
Check if your USB stick is being detected with...
ifconfig -a
This should show you a list of all your network interfaces including your new USB wifi one.

Create a new file called wlanstart.sh and put the following into it...
(obviously changing all the ENTER_YOUR.... parts to suit your system)

#! /bin/bash
# wlanstart file
/sbin/ifconfig wlan0 up
/sbin/iwconfig wlan0 mode managed
/sbin/iwconfig wlan0 essid ENTER_YOUR_ESSID_HERE
/sbin/iwconfig wlan0 ap ENTER_YOUR_ACCESS_POINT_MAC_CODE_HERE
/sbin/iwconfig wlan0 rate 54M
/sbin/iwpriv wlan0 set AuthMode=WPAPSK
/sbin/iwpriv wlan0 set WPAPSK="ENTER_YOUR_PASSPHRASE_HERE"
/sbin/iwpriv wlan0 set EncrypType=TKIP
route add default gw ENTER_YOUR_GATEWAY_IP_HERE

You need to make this file executable and place it in your /usr/local/bin directory.

Now add the following line to your /etc/rc.local file.

/usr/local/bin/wlanstart.sh

Be sure to put the line just above the exit 0 line!!!


Now you need to edit your /etc/network/interfaces file.
Add the following to the file.

iface wlan0 inet static
address 192.168.1.133
netmask 255.255.255.0
gateway 192.168.1.200
dns-nameservers 192.168.1.200
auto wlan0

Obviously change any parts that are different in your setup like maybe the IP, gateway and wlan0 etc.

On a reboot your network should come up working okay.
Mine takes a few seconds or so to come up correctly, but it seems to work flawlessly!

Update 27th November 2008
This does not seem to work as flawlessly as I thought, sometimes the wireless does not come up, I am looking into this and will report more as I find out more.
End of Update

NOTE:-
When booting you may notice a delay on the MTA line, just wait it will only take 10 to 20 seconds.
MTA is the Mail Transfer Agent and I believe it is looking for something on the network, the network is not operational during this part of the boot so it causes this delay. I am looking into solving this.

If anyone has any information to improve upon this please email me at

Disclaimer: I have tried to make this page as accurate as possible but even so mistakes can be made. If you use the information on this page you do so completely at your own risk.
Created by C Cooper.




myspace web counter
web counter code