Bug 812500 - Can't connect to wireless AP (ath9k)
Summary: Can't connect to wireless AP (ath9k)
Keywords:
Status: CLOSED DUPLICATE of bug 810796
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-14 03:45 UTC by Jeremy Newton
Modified: 2012-04-16 15:01 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-16 15:01:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jeremy Newton 2012-04-14 03:45:05 UTC
Description of problem:
If I attempt to connect to a wireless AP with my laptop and it fails to connect. This seems to happen over and over, and rarely manages to connect to the wireless AP. I'm using a laptop with an ath9k wireless card.

Version-Release number of selected component (if applicable):
This is not a problem in kernel 3.3.0-8 and I can confirm this as becoming a problem as of kernel 3.3.1-1. Due to the circumstances, one could assume this is a bug in 3.3.1 itself.

As well, I can confirm this with the following Fedora kernel versions:
3.3.1-1.fc16, 3.3.1-2.fc16, 3.3.1-3.fc16

How reproducible:
Very reproducible

Steps to Reproduce:
1. Start into Fedora 16 with one of the confirmed kernel listed above.
2. Try to connect to a wireless AP
  
Actual results:
Mostly consistently failed connections.

Expected results:
Mostly consistently successful connections.

Additional info:
I'm using an EeePC 1015PX with an Atheros AR9285 wireless card.
Note this seems to be specifically a regression in ath9k, though may include others.

Please let me know if I can provide any more information that would help.

Comment 1 John W. Linville 2012-04-16 14:55:36 UTC
A 3.3.2-based kernel should resolve this issue when it becomes available through the update system.

Comment 2 Josh Boyer 2012-04-16 15:01:16 UTC

*** This bug has been marked as a duplicate of bug 810796 ***


Note You need to log in before you can comment on or make changes to this bug.