Results 11 to 14 of 14
Enjoy an ad free experience by logging in. Not a member yet? Register.
Press ALT+F2 and type gksudo gedit /etc/modprobe.d/blacklist
Add this to the end of the file and save.
blacklist ath_hal blacklist ath_pci blacklist ndiswrapper
Now make sure the right driver is loading.
Press ALT+F2 and type gksudo gedit /etc/modules
This should make it load the right driver on reboot.
Without rebooting, you can also do
sudo modprobe -r ndiswrapper sudo modprobe ath5k sudo ifconfig wlan0 up
- Join Date
- May 2009
I think I know the problem already. When you installed ndiswrapper did you follow online instructions that told you to blacklist your native driver? If so, did you remember to unblacklist it when I told you to get rid of ndiswrapper or did you just remove ndis and forget to go into your modprobe.d/blacklist file?Bodhi 1.3 & Bodhi 1.4 using E17
Dell Studio 17, Intel Graphics card, 4 gigs of RAM, E17
"The beauty in life can only be found by moving past the materialism which defines human nature and into the higher realm of thought and knowledge"
- Join Date
- Jul 2004
i just installed Ubuntu 9.04 on my Eee PC 900, and it has the same wireless. I then updated it.
The wireless worked out-of -the box. But after installing a program to enable the Function (Fn) keys, and then testing the wireless on/off keys, I had to reboot. When i checked the output of lsmod, I found that it was loading both the ath5k and ath_pci modules! I never enabled the madwifi (ath_pci) driver, so maybe it was the Funtion keys program that did this.
This may not apply here, but it may be something to keep an eye out for.Please do not send Private Messages to me with requests for help. I will not reply.