From: Ben Greear <greearb@candelatech.com>
To: sedat.dilek@gmail.com
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Setting txpower fails?
Date: Fri, 28 Mar 2014 07:18:39 -0700 [thread overview]
Message-ID: <533584BF.70604@candelatech.com> (raw)
In-Reply-To: <CA+icZUVe7Mwf2P=Jk3rHvqZEDf3otOP7DwM=y7_LVHd4t_koQA@mail.gmail.com>
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
>> [root@ct523-9292 lanforge]# echo $?
>> 0
>> [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]#
>>
>
> Which version of wireless-tools?
> Why don't you use modern iw?
Do you know the right incantation for 'iw'? From it's help, it seems
this should work, but it throws an error. I haven't dug into the
code to figure out why...
[root@ct523-9292 lanforge]# iw dev wlan0 set txpower 10
Invalid parameter: 10
[root@ct523-9292 lanforge]# iwconfig --version
iwconfig Wireless-Tools version 29
Compatible with Wireless Extension v11 to v22.
Kernel Currently compiled with Wireless Extension v22.
sta211 Recommend Wireless Extension v21 or later,
Currently compiled with Wireless Extension v22.
...
Thanks,
Ben
>
> - Sedat -
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-03-28 14:18 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 [this message]
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
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=533584BF.70604@candelatech.com \
--to=greearb@candelatech.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).