Bug 12288 - txpower off doesn't work for ath5k driver
Summary: txpower off doesn't work for ath5k driver
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-24 19:53 UTC by shen cathy
Modified: 2010-06-07 19:42 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.28.rc7
Subsystem:
Regression: No
Bisected commit-id:

Attachments
txpower off (127.64 KB, image/jpeg)
2009-10-30 13:09 UTC, Daniel Folkers 		Details
txpower 10dBm (127.57 KB, image/jpeg)
2009-10-30 13:09 UTC, Daniel Folkers 		Details
txpower 20dBm (129.28 KB, image/jpeg)
2009-10-30 13:10 UTC, Daniel Folkers 		Details
Add an attachment (proposed patch, testcase, etc.)

Description shen cathy 2008-12-24 19:53:36 UTC 
Latest working kernel version: N/A
Earliest failing kernel version:N/A
Distribution:N/A
Hardware Environment: AspireOne
Software Environment: 2.6.28.rc7
Problem Description: when use "iwconfig wlan0 txpower off" still can associate with other AP or wireless machine.

Steps to reproduce:
1. associate with one AP in managed mode and g band without WEP
2. use "iwconfig wlan0 txpower off" to disable radio
3. still can ping AP
Comment 1 John W. Linville 2009-01-14 12:36:37 UTC 
Looks like the ath5k hw_config mac80211 op needs to account for conf->radio_enabled, similar to what b43/main.c does in b43_op_config.
Comment 2 Bob Copeland 2009-01-21 13:08:28 UTC 
Exactly right - some rfkill support is forthcoming and this will be part of it.
Comment 3 Bob Copeland 2009-10-25 19:49:44 UTC 
Can you retest latest kernel?  Rfkill and txpower support was added for 2.6.31.
Comment 4 Daniel Folkers 2009-10-30 13:08:07 UTC 
I have very recently done some testing with the 2.6.30 kernel and a R52H mini PCI card (RouterBoard), with a Atheros AR5414 chipset in it. 

I connected the antenna output to a spectrum analyser and did a multicast ping with a duty cycle of 80% (using MGen).

wlan1 IEEE 802.11abg ESSID:"HENK"
      Mode:Ad-Hoc  Frequency:2.462 GHz Cell: Not-Associated
      Tx-Power=20 dBm
      Retry min limit:7   RTS thr:off  Fragment thr:off
      Encryption key:off
      Power Management:off
      Link Quality:0  Signal level:0  Noise level:0
      Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
      Tx excessive retries:0  Invalid misc:0 Missed beacon:0

Not just putting txpower on and off does not work, also setting the txpower does not work. See attachments (screenshots of my spectrum analyser).
Comment 5 Daniel Folkers 2009-10-30 13:09:10 UTC 
Created attachment 23595 [details]
txpower off
Comment 6 Daniel Folkers 2009-10-30 13:09:52 UTC 
Created attachment 23596 [details]
txpower 10dBm
Comment 7 Daniel Folkers 2009-10-30 13:10:17 UTC 
Created attachment 23597 [details]
txpower 20dBm
Comment 8 Bob Copeland 2010-02-09 15:18:48 UTC 
(In reply to comment #7)
> Created an attachment (id=23597) [details]
> txpower 20dBm

Hi Daniel,

I think this older bug is the same as

http://bugzilla.kernel.org/show_bug.cgi?id=14567 

which we fixed by 2eb2fa67e5462a36e98172fb92c78bc405b3035f
"ath5k: allow setting txpower to 0".  Do you agree it's fixed
and this bug can be closed?
Comment 9 John W. Linville 2010-03-05 18:36:09 UTC 
Daniel, please respond to comment 8?
Comment 10 John W. Linville 2010-06-07 19:41:49 UTC 
Closed due to lack of response...
Note You need to log in before you can comment on or make changes to this bug.