Networking :: rt73 usb network card driver



Hi,

   I installed a dlink DWL-G122 (c1) usb wireless network card on my laptop. I found a lot of information about using ralink rt73 driver. I followed the instruction to download, compile and install the driver. I have one problem yet. When i do iwconfig, i see the rausb0 device but when i do ifconfig i didn't see it.

  If i do "ifconfig rausb0 up?. I receive a "Segmentation fault" and the session freeze. The only way to be able to send other command to the device (ex iwconfig) is to reboot.

Does somebody got this problem?

Thanks

Here's some info...
http://ndiswrapper.sourceforge.net/mediawiki/index.php/List

There's some alternatives there, but don't know about your problem.

Thanks for the answer. I will try with ndiswrapper. With the linux driver (rt73) the usb key freeze when i use "ifconfig rausb 0 up". Same thing when i use the mydsl control panel.
Well there are updated closed and open source native drivers that you could try that's listed there, but ndiswrapper should work.

And I think you meant the DSL panel.

I don't know anything about the NDIS Wrapper, but I was able to get an RT2571W chip to run successfully on DSL without it, using the RT73 driver.  It wasn't easy.  My card is not DLink, but rather Level One WNC-0301USB, but that shouldn't matter.  Here was the process I followed:

* Download the source code for the RT73 driver direct from RAlink.
* Download the source code for the DSL kernel (in my case, this was version 2.4.26).
* Put all the source code on a machine that has a compiler.  
* Compile the kernel using all default options.
* Compile the driver using the "Makefile.4" makefile.  (This step depends on files produced by the kernel build process)
* Put the module on the DSL machine in /lib/modules/net/wireless, run depmod, ignore the error, and reboot.  (you could run insmod to test the module first if you want).
* Run ifconfig rausb0 inet <IP addy> up
* Run route add default gateway <your gateway IP>

My guess is that the segmentation fault may have occured if you downloaded a binary driver, which may have been compiled for a different kernel version.  

I could post my binary driver module if you want, and you have kernel version 2.4.26.

Next Page...
original here.