Description of problem: With the update to the newest kernel version (3.2.3-2 fc16.i686), I am unable to connect with my wireless router. Unlike the issue with the previous release whereby the wireless card isn't recognized by the system, my wireless card can see my wireless network (and those in the surrounding area). However, when I enter the WEP key, the system attempts to connect but is unable to do so. I have removed/deleted the existing connection and attempted to start from scratch, however that did not correct the issue. Version-Release number of selected component (if applicable):Fedora 16 3.2.3-2 fc16.i686 How reproducible: It happens every time I log on with kernel 3.2.3. If I revert to 3.1.9-1 there is no problem connecting to my wireless network. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
What kind of wireless card? Does the new kernel in f16-updates-testing improve things? There are a number of wireless fixes in there.
Sounds like bug 785409, which should be fixed in kernel-3.2.5-3.fc16.
As far as I can tell, the wireless card is an "Atheros AR5B91", which shipped with the laptop - a Gateway MD2614u. Josh Boyer: As this is my only computer and I'm still a relative novice when it comes to compiling and testing the kernel itself, I'm a little reluctant to explore that course of action. John Linville: I've checked out Bug 785409 and I concur: it does sound like the same issue. I haven't tried applying any patches yet - as I've said, I'm a little reluctant in case I foul up my only working computer. However, if you want to close this bugreport and refer to 785409, I'm fine with that.
(In reply to comment #3) > As far as I can tell, the wireless card is an "Atheros AR5B91", which shipped > with the laptop - a Gateway MD2614u. > > Josh Boyer: As this is my only computer and I'm still a relative novice when it > comes to compiling and testing the kernel itself, I'm a little reluctant to > explore that course of action. You don't need to compile the kernel at all. Just install the one in updates-testing (which is moving to stable updates today most likely so you might as well wait).
*** This bug has been marked as a duplicate of bug 785409 ***