![]() |
Ubuntu 9.04 - Atheros AR242x wireless
I've been using a budget-line Compaq laptop which has an AR242x wireless controller from Atheros. It was running out of the box when I first put 8.10 on the system, but future kernel upgrades stopped the drivers from working - so I'd just been booting into an old kernel. After upgrading to 9.04, however, it was working out of the box again - until I rebooted, and presto! the wireless card was no longer detected by the system, even though there was supposedly an active proprietary driver.
I went to the compat-wireless site, downloaded and made the package, and after typing "make load," it appeared to work. Here's what I got. Code:
ath5k loaded successfullyCode:
wlan0 Interface doesn't support scanning : Device or resource busyiwconfig results: Code:
lo no wireless extensions. |
Your problem seems to depend on some volatile and undocumented bug in the ath5k driver.
I have experienced about the same appearance of "perhaps-functionality" of that new driver when upgrading from 8.04 to 9.04, and decided to revert to the madwifi driver -- which has been removed from the jaunty repositories! Well I dowloaded the .deb from Debian instead, and the madwifi's driver (ath_pci) does function reliably. Note: Remember to blacklist ath5k since it is told that they don't like each other! I can tell more details if relevant, keep in touch! P.S. Your problem may/may not be related to http://www.linuxquestions.org/questi...oot-up-744756/ (just a note). |
Update: I did a clean install, and the wireless worked out of box - until I had used it for a couple of hours, then the connection failed and when I disabled and reenabled wireless, it was back to how it was.
I tried installing the ndiswrapper Windows driver, but that gives the same net result. What is wrong here? |
Did you check that the ndiswrapper driver does "take the command"? Maybe the default ath5k is still loaded in the kernel and acting just like before?
You may check using sudo lsmod or e.g. sudo lsmod | grep ath to verify loaded driver modules. In order to prevent ath5k being loaded you may need to blacklist it in the /etc/modprobe.d/ directory. In my case, after blacklist, lspci -k still shows that ath5k is an available module, but it doesn't come up in lsmod | grep ath since it isn't loaded (but the madwifi driver ath_pci comes up). |
| All times are GMT -5. The time now is 09:56 PM. |