Yahoo Answers is shutting down on May 4th, 2021 (Eastern Time) and the Yahoo Answers website is now in read-only mode. There will be no changes to other Yahoo properties or services, or your Yahoo account. You can find more information about the Yahoo Answers shutdown and how to download your data on this help page.
Trending News
Wireless Ubuntu 11.10?
So I installed Ubuntu 11.04 a few weeks back and I really liked it. No hic ups, never crashed for me. Today I upgraded to the new Ubuntu 11.10. Now my wireless doesn't work at all. I can see my connection and when I click on it it asks me for my password. It then thinks for 2 minutes, and comes back again asking for my password. and on and on it goes in this cycle.
i heard maybe this is a driver issue. but i am not a hardware guy. i have no idea what my driver is, how to find out or what to do once i do find out.
sadly, this is what keeps people away from linux.with 11.04 i just clicked, entered a password and i was on my way. here i have spent 2 hours looking around on the net (with an ethernet connection) and all i find is long complex code which might as well be in Greek.
please help!!!
2 Answers
- Linux Mint 11Lv 710 years agoFavorite Answer
Here is the Official Ubuntu Wireless Documentation
Troubleshooting/Howto/General
https://help.ubuntu.com/community/WifiDocs/WiFiHow...
LUg.
- 10 years ago
This happens alot on realtek chips. The wrong driver module is loaded for the chipset.
To verity boot with your old kenel (from he grub menu, select previous versions and use one of those that say a 2.6.38* kernel version string)
Step one figure out what your chipset is. either be using "sudo lshw" or "sudo dmesg |grep -i net" in a terminal.
Step two figure out what network modules are loaded. run "lsmod" what modules were loaded for it. (should have a dependency on the generic wireless module (i think mac80211), have the same company name as the chipset name, or likely both. If this is different from what is loaded with the older kernel you can probably fix it.
Step 3. If it is the same kernel module, report it as a bug and keep using the prior kernel version.
If is is a different module, unload it with "rmmod <currently loaded module name>" and load the right one with "modprobe <name of previously working module> " To make the fix permanent, blacklist the bad module (google for details) This is still a bug if you want to report it, but a less serious one.
