Networking :: wifi card not listed in iwconfig



I did try to install the .inf file, and after I did ndiswrapper -l, all i got was:

Code Sample
neta3ab invalid driver!


I don't get the "hardware present, software present" messages like I am used to seeing.  I know this for a fact: the only network interfaces that are present are eth0 (which is my onboard 10/100 wired connection), and lo (loopback).  Nothing else is showing!

Quote
Alternatively, your Atheros chipset is supported by the MADWiFi drivers already in DSL (although it's possible that your adapter requires a newer version of MADWiFi) so you could try "sudo modprobe ath_pci".
In fact, you should possibly run "lsmod" because DSL may have automatically loaded this module (ath_pci) already.


I have not yet tried this approach, I didn't realize MADwifi drivers were in DSL.  How would I update the MADwifi drivers?  I assume by downloading them from the website and compiling them from source?

Yes, obtain the driver source by CVS from http://madwifi.sourceforge.net
I compiled this myself a few months ago, you can email me if you want the package ... but try the DSL module first, it might work.

ath_pci was not listed on lsmod, nor after I modprobed it.  

I was able to find the madwifi drivers for download, after some furious googling, however I have been running into some problems with compiling.  I installed gcc, gnu-utils, and kernelsource from the mydsl control panel, yet after I untar a package (such as the madwifi drivers), then enter "./configure" it says command not found.  Am I supposed to symb link in /bin from another location to the ./configure script?

Also, a bigger problem I had was with the drivers I downloaded from Dlink.  I saved the .zip file to my home folder, and proceeded to unzip it from the command line.  I get an error everytime of:

Code Sample
unsupported compression method 0


So, what I did was download and unzip the file on my powerbook, and uploaded the .inf file to my ftp space, then downloaded just the .inf file on my DSL PC.  In retrospect, that probably caused my problem with ndiswrapper, but it was the only workaround I could think of, since finding drivers elsewhere on the net for the DWL-G510 rev b is an arduous task.

thanks for all the replies :)

I found the problem, I had a bad installation on my HD.  I reinstalled and things are going smoothly.

ndiswrapper now recognizes the driver, and now it is just a matter of getting it properly connected to my network.

Glad to hear you got if figured out. Now you can properly enjoy dsl.
Next Page...
original here.