Bug 12943 - ath9k doesn't report (correct) link speed (802.11n, 2.4GHz)
Summary: ath9k doesn't report (correct) link speed (802.11n, 2.4GHz)
Status: CLOSED DOCUMENTED
Alias: None
Product: Networking
Classification: Unclassified
Component: Wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: networking_wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-25 23:06 UTC by Patrick Bregman
Modified: 2009-06-01 17:08 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.29
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Patrick Bregman 2009-03-25 23:06:10 UTC 
I noticed that ath9k doesn't report the correct link speed. I noticed this when I got a 802.11n AP. "iwconfig" gives a speed of 0kBit/s:

patrick@EeePC901:~$ iwconfig ath0
ath0      IEEE 802.11abgn  ESSID:"Disconnected-N"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:24:36:9C:EC:11   
          Bit Rate=0 kb/s   Tx-Power=23 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Power Management:off
          Link Quality=100/100  Signal level:-25 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

This is while connected to my Airport Express running at 2.4GHz N. The hardware is:
01:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)

On a 802.11b/g network the speed is reported correctly.

If you need more information, I´ll be happy to provide it.
Comment 1 John W. Linville 2009-03-31 19:19:12 UTC 
I think this is a limitation in the wireless extensions API.  Copying Luis just in case there is a real problem here...
Comment 2 Sujith 2009-04-10 07:04:58 UTC 
That's correct, it is a limitation in WE. To see the correct TX rate,
'iw dev wlan# station dump' should show MCS rates - but ath9k doesn't report 11n rates properly to mac80211 now. So that would be bogus too. :-)
Comment 3 Luis Chamberlain 2009-05-28 22:08:49 UTC 
Can this please be closed? Its marked as resolved already.
Note You need to log in before you can comment on or make changes to this bug.