From: Larry Finger <Larry.Finger@lwfinger.net>
To: Chiefdome <chiefdome@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Alfa AWUS036NHR with RTL8188RU chipset
Date: Wed, 26 Oct 2011 16:31:17 -0500 [thread overview]
Message-ID: <4EA87C25.1070403@lwfinger.net> (raw)
In-Reply-To: <4EA861F5.4020200@googlemail.com>
On 10/26/2011 02:39 PM, Chiefdome wrote:
>
> Did you tested the commands you posted to me? Anyway here they do nothing. I
> cant see any changes in iwconfig nor in in iw.
>
> iw reg get
> country 00:
> (2400 - 2494 @ 40), (N/A, 33)
> (4910 - 5895 @ 40), (N/A, 33)
>
> so after my regulatory domain I should be able to change the adapter settings.
I now have tested. My device is limited to 27 dBm, thus the limit in the txpower
command is 2700, but one can reduce the power.
finger@larrylap:~/linux-2.6> iwconfig wlan25
wlan25 IEEE 802.11bg ESSID:"lwfdjf-n"
Mode:Managed Frequency:2.422 GHz Access Point: C0:3F:0E:BE:2B:44
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=66/70 Signal level=-44 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:93 Invalid misc:270 Missed beacon:0
finger@larrylap:~/linux-2.6> sudo iw dev wlan25 set txpower limit 2200
finger@larrylap:~/linux-2.6> iwconfig wlan25
wlan25 IEEE 802.11bg ESSID:"lwfdjf-n"
Mode:Managed Frequency:2.422 GHz Access Point: C0:3F:0E:BE:2B:44
Bit Rate=54 Mb/s Tx-Power=22 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=68/70 Signal level=-42 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:93 Invalid misc:270 Missed beacon:0
With your regulatory info, you should be able to get 3300, unless the rtl8192cu
firmware has a limit to keep you from destroying the chip.
Perhaps you should ask Alfa about this issue.
Larry
prev parent reply other threads:[~2011-10-26 21:31 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 2:10 Alfa AWUS036NHR with RTL8188RU chipset Chiefdome
2011-09-20 2:27 ` Chiefdome
2011-09-20 3:05 ` Larry Finger
2011-09-20 9:32 ` Chiefdome
2011-09-20 21:38 ` Chiefdome
2011-09-20 22:32 ` Larry Finger
2011-09-21 0:02 ` Larry Finger
2011-09-21 9:43 ` Chiefdome
2011-09-21 14:45 ` Larry Finger
2011-09-21 19:19 ` Chiefdome
2011-09-21 20:03 ` Larry Finger
2011-09-21 20:28 ` Chiefdome
2011-09-21 20:37 ` Larry Finger
2011-09-21 20:39 ` Chiefdome
2011-09-21 20:41 ` Chiefdome
2011-09-21 21:09 ` Larry Finger
2011-09-30 14:20 ` v4mp
2011-09-30 15:18 ` Larry Finger
2011-09-30 18:14 ` v4mp
2011-10-06 16:25 ` Toddy
2011-10-06 22:06 ` Larry Finger
2011-10-08 16:24 ` Toddy
2011-10-08 16:52 ` Larry Finger
2011-10-08 23:29 ` Gábor Stefanik
2011-10-09 14:21 ` v4mp
2011-10-09 14:47 ` Larry Finger
2011-10-15 14:22 ` v4mp
2011-10-16 2:49 ` Larry Finger
2011-10-17 10:07 ` v4mp
2011-10-17 14:59 ` Larry Finger
2011-10-17 17:09 ` v4mp
2011-10-17 18:38 ` Larry Finger
2011-10-18 3:23 ` Larry Finger
2011-10-18 12:44 ` v4mp
2011-10-18 13:07 ` v4mp
2011-10-18 15:20 ` Larry Finger
2011-10-18 21:50 ` v4mp
2011-10-18 23:01 ` Larry Finger
2011-10-19 8:17 ` v4mp
2011-10-19 12:08 ` Larry Finger
2011-10-19 14:37 ` v4mp
2011-10-20 3:38 ` Larry Finger
2011-10-20 9:47 ` v4mp
2011-10-20 13:35 ` Larry Finger
2011-10-26 15:49 ` Chiefdome
2011-10-26 16:12 ` Larry Finger
2011-10-26 19:39 ` Chiefdome
2011-10-26 21:20 ` Larry Finger
2011-10-26 21:31 ` Larry Finger [this message]
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=4EA87C25.1070403@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chiefdome@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
/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).