From: Ben Greear <greearb@candelatech.com>
To: Bruno Antunes <baantunes@gmail.com>
Cc: linux-wireless@vger.kernel.org, sedat.dilek@gmail.com
Subject: Re: Setting txpower fails?
Date: Fri, 28 Mar 2014 08:25:41 -0700 [thread overview]
Message-ID: <53359475.60904@candelatech.com> (raw)
In-Reply-To: <E322ACF2-B0A6-45D9-93C8-85F68176DCB2@gmail.com>
On 03/28/2014 08:15 AM, Bruno Antunes wrote:
>
> On 28 Mar, 2014, at 15:02 , Ben Greear <greearb@candelatech.com> wrote:
>
>> On 03/28/2014 07:49 AM, Bruno Antunes wrote:
>>>
>>> On 28 Mar, 2014, at 14:37 , Ben Greear <greearb@candelatech.com> wrote:
>>>
>>>> On 03/28/2014 07:29 AM, Bruno Antunes wrote:
>>>>> Hi Ben,
>>>>> I think you are missing some parameters
>>>>>
>>>>> On 28 Mar, 2014, at 14:18 , Ben Greear <greearb@candelatech.com> wrote:
>>>>>
>>>>>> On 03/28/2014 12:27 AM, Sedat Dilek wrote:
>>>>>>> On Fri, Mar 28, 2014 at 5:21 AM, Ben Greear <greearb@candelatech.com> wrote:
>>>>>>>> Any idea why this isn't working?
>>>>>>>>
>>>>>>>> Kernel is 3.9.11+, driver is ath9k.
>>>>>>>>
>>>>>>>> [root@ct523-9292 lanforge]# iwconfig wlan0
>>>>>>>> wlan0 IEEE 802.11abgn ESSID:off/any
>>>>>>>> Mode:Managed Access Point: Not-Associated Tx-Power=16 dBm
>>>>>>>> Retry short limit:7 RTS thr:off Fragment thr:off
>>>>>>>> Encryption key:off
>>>>>>>> Power Management:off
>>>>>>>>
>>>>>>>> [root@ct523-9292 lanforge]# iwconfig wlan0 txpower 10
>>>>>
>>>>> iw dev <devname> set txpower <auto|fixed|limit> [<tx power in mBm>]
>>>>>
>>>>> It should be something like:
>>>>>
>>>>> iw dev wlan0 set txpower fixed 1000
>>>>
>>>> Ok, that doesn't give an error, but 'iwconfig' still shows 16 dBm,
>>>> and I don't see any way to get 'iw' to print out the power itself?
>>>>
>>>> So, not sure if it is really working or not.
>>> It works , at least on iw 3.10.
>>>
>>> If you have debug enabled you can see the value changing.
>>
>> Just for posterity's sake, it seems you should really be looking
>> at user_power_level:
>>
>> [root@ct523-9292 lanforge]# iw dev wlan0 set txpower fixed 1000
>> [root@ct523-9292 lanforge]# cat /debug/ieee80211/wiphy0/netdev\:wlan0/txpower
>> 0
>> [root@ct523-9292 lanforge]#
>>
>> [root@ct523-9292 lanforge]# cat /debug/ieee80211/wiphy0/netdev\:wlan0/user_power_level
>> 10
>>
> Not on all systems...
I suspect the difference is that my wlan0 is not actually connected,
and it will probably show correct 'txpower' when it is connected.
Thanks,
Ben
>
> root@RSPro2:/etc/config# iw dev adhoc0 set txpower fixed 700
> root@RSPro2:/etc/config# cat /sys/kernel/debug/ieee80211/phy0/netdev\:adhoc0/txpower
> 7
> root@RSPro2:/etc/config# cat /sys/kernel/debug/ieee80211/phy0/netdev\:adhoc0/user_power_level
> 7
>
> Bruno
>
>> Thanks,
>> Ben
>>
>>>
>>> On a openwrt system
>>>
>>> root@RSPro2:/lib/wifi# iw dev adhoc0 set txpower fixed 900
>>> root@RSPro2:/lib/wifi# cat /sys/kernel/debug/ieee80211/phy0/netdev:adhoc0/txpower
>>> 9
>>> root@RSPro2:/lib/wifi# iw dev adhoc0 set txpower fixed 1500
>>> root@RSPro2:/lib/wifi# cat /sys/kernel/debug/ieee80211/phy0/netdev:adhoc0/txpower
>>> 15
>>>
>>> And the received power changes on the station confirming that is making effect.
>>>
>>> Bruno
>>>
>>>>
>>>> Thanks,
>>>> Ben
>>>>
>>>>
>>>> --
>>>> Ben Greear <greearb@candelatech.com>
>>>> Candela Technologies Inc http://www.candelatech.com
>>>>
>>
>>
>> --
>> Ben Greear <greearb@candelatech.com>
>> Candela Technologies Inc http://www.candelatech.com
>>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-03-28 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 4:21 Setting txpower fails? Ben Greear
2014-03-28 7:27 ` Sedat Dilek
2014-03-28 14:18 ` Ben Greear
2014-03-28 14:39 ` Sedat Dilek
[not found] ` <4CC49FDB-1767-4A3F-9C1D-8F8DCF612233@gmail.com>
[not found] ` <53358920.6030304@candelatech.com>
2014-03-28 14:49 ` Bruno Antunes
2014-03-28 15:02 ` Ben Greear
2014-03-28 15:15 ` Bruno Antunes
2014-03-28 15:25 ` Ben Greear [this message]
2014-03-29 5:02 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53359475.60904@candelatech.com \
--to=greearb@candelatech.com \
--cc=baantunes@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).