A native driver is usually preferable, if you can get it installed. The instructions on the Debian wiki that I linked to should work on Ubuntu as well, with a few modifications: skip steps 1 and 2,...
Type: Posts; User: pytheas22; Keyword(s):
A native driver is usually preferable, if you can get it installed. The instructions on the Debian wiki that I linked to should work on Ubuntu as well, with a few modifications: skip steps 1 and 2,...
gnueliafnak: what is the output of:
uname -a
ndiswrapper -l
Also, I gather from some quick googling that there is also a native Linux driver for your card called ar5523. If ndiswrapper...
mastergunner: sorry, I don't check the forums too often anymore. I am willing to help you if you post more information. In particular, it would be good to see the output of:
uname -a
lspci...
Laize: you should not need to use ndiswrapper for your device, as it is supported by the Broadcom STA driver. To install that driver, type these commands in a terminal (you will need an Internet...
blahtrash: first of all, I would check whether changing any settings on your router makes a difference. Try using a different channel or changing the mode (e.g., if it is now in 11g and 11n mode,...
fblud: this thread is very old and the solution here no longer applies on modern versions of Ubuntu. Please instead try installing the firmware-b43-installer package, which you can do by typing:
...
mojo risin: it must have built the module when you installed the ndiswrapper-dkms package, so it wasn't necessary to build it yourself as I had suggested. In any case, I'm glad it works now, and...
mojo risin: if you install the ndiswrapper-common and ndiswrapper-utils-1.9 packages they should install the ndiswrapper module on your system for all kernels. But apparently that is not happening...
mojo risin: you don't have any ndiswrapper module installed for the 3.2 kernel. I'm not sure why that is, but hopefully reinstalling the ndiswrapper packages would fix the problem. Please try:
...
mojo risin: what is the output of:
locate ndiswrapper.ko
uname -a
mojo risin: the Ubuntu 12.04 repositories contain packages for ndiswrapper which should presumably work with the 3.2 kernel, since that is the one Ubuntu 12.04 uses. Have you tried simply installing...
Drumclem: glad it worked. wildmanne39's explanation of what those commands do is pretty thorough.
Je suis content que quelqu'un ait enfin apprecié le nom du domaine :)
haha, here I am! Thanks for the suggestion above, wildmanne39, which would have been my first try as well.
Since modifying /etc/modules doesn't seem to do the trick, why don't you try writing a...
pedrok1664: copying the files into /usr/src/ndiswrapper will not do anything -- that is just a location to store source code. Did you also install the Windows driver into ndiswrapper by typing:
...
pedrok1664: have you tried using the Windows driver referenced here? If not I would remove the driver you currently have loaded by typing:
sudo ndiswrapper -r wlanuzg
and then install the...
Yes, that line looks like the culprit, but unfortunately it's pretty vague.
Other thoughts would be to try changing the settings on your router, if possible. Try changing the wireless channel, or...
Master_Ne0: I would first try connecting using wicd, which you can install via the Ubuntu Software Center. It might handle the encrypted network better than NetworkManager.
If that doesn't help,...
hannah187: unfortunately it looks like ndiswrapper doesn't like that driver for strange reasons. You could try compiling ndiswrapper from source to see whether using the latest version might help,...
smith123946: please try following the instructions for configuring Ndiswrapper at https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper. We can help you if you run into trouble after putting...
By all indications in the output you posted, your wireless driver is installed and functioning correctly, and your connection should work. My first guess as to why it's not is that your network is...
pivotraze: from the output you posted it looks like ndiswrapper just doesn't want to work with the particular Windows driver you loaded. Unfortunately there's not much information on why. You might...
Did you check to see if dmesg, etc. says anything about why the driver might not be bringing up the device?
Also, your card should be supported by the native Linux driver ath9k. Does it not work...
Glad that did it. You just needed to get the b43 driver loaded. As bkratz pointed out, though, those changes won't persist through a reboot, but you can make the solution permanent easily enough by...
MikeLitt: thanks for the information. That helps make things a little clearer, although I'm afraid I'm still not positive what's wrong.
When you're able, please post the output of these commands,...
Update: I was wrong. The b43 driver will support this device. I thought it didn't because I'd forgotten that the PCI ID matches for the b43 driver are actually built into the "ssb" module, not b43...