A couple of weeks back perhaps I noticed a weird thing happening to my main laptop with Atheros wireless chip: I can no longer connect to the wireless network at home! Of course I made sure the network was up and running (all other devices connect without issue), just the F16 x86_64 machine does not: it insists in requesting the password (which is correct, and was working before). I didn't care much back then because the laptop has a network cable anyway.
The "offending" device is:
product: AR928X Wireless Network Adapter (PCI-Express)
vendor: Atheros Communications Inc.
The system is fully up-to-date, and just to be sure of the problem I checked that:
- The same machine can connect under F16 booting from the liveUSB.
- It can not connect to protected wireless networks at work.
- Can use unprotected wireless networks just fine.
So I may rule out hardware malfunction and point fingers solely to the software, perhaps a recent upgrade?
I read several threads dealing with similar problems but they are mostly about Broadcom or Intel chips, and their solutions involve tweaking hardware-specific files which do not apply; the only useful suggestion I tried was that from a fellow who introduced the passwords as root (they are already there).
Several years ago the Atheros drivers were embedded into the kernel itself, right? I'll try booting from the previous kernel and see if it helps.
EDIT: OK, I just checked and the problem starts with kernel 3.2.x (the problem is absent in kernel 3.1.9, which is at the end of the list and I am gonna find out how to preserve from disappearing in further upgrades).
So here I am at a loss about what to do to regain this basic laptop functionality (I won't always have a network cable or open network at hand). What can I do/tweak? Where am I supposed to look for a fix?
Am I supposed just to wait patiently for a new kernel to fix the problem or what should I change of the current one?
---------- Post added at 12:36 PM ---------- Previous post was at 12:11 PM ----------
Found the bugger:
I guess the suggested solution will have to wait until I clear up my schedule, unless a kernel upgrade comes first.