[SOLVED] Adjusting my wireless card Txpower

saw_mj · 2017-07-22 05:05:39

I have an External wireless card : Alfa awus036h

and when i try change the txpower with the command

iwconfig wlp**** txpower "whatever number i put in here"

nothing seems to change when i try iwconfig to see the change Txpower seems stuck at 20dBm even if i decrease it below 20 or increase it up 20dBm

and my Chipset is rtl8187l

and the output of lspci -k

09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
	Subsystem: Lenovo Device 3831
	Kernel driver in use: r8169
	Kernel modules: r8169

and the interesting part here is when i try to change the Txpower into my integreted wifi chipset it works. it doesn't increase than 22dBm yes, but i can change it lower than 20dBm and verifying the change with iwconfig.

Last edited by saw_mj (2017-07-24 07:05:28)

Docbroke · 2017-07-22 05:53:04

Try "iw dev set txpower <power>", iwconfig is too old.

saw_mj · 2017-07-22 06:57:02

Docbroke wrote:

Try "iw dev set txpower <power>", iwconfig is too old.

I already tried it and still the same... doesn't change a thing.

ugjka · 2017-07-22 07:30:31

probably the driver doesn't support it for that chip

seth · 2017-07-22 08:11:28

At least the lspci output is for an ethernet chip. No txpower, because it uses a cable :-P

Fwwi, the "Alfa awus036h" is promoted w/ 1W power, ie. you should be able to get 30 dBm, but you probably need to adjust the regularory domain first (what may be illegal and punishable at your location, google on details)
It may very well be that the device only supports some fixed txpower values.

saw_mj · 2017-07-22 09:01:39

ugjka wrote:

probably the driver doesn't support it for that chip

you saying that i'm using the wrong driver ?
I remember i checked it and that was the prober driver for the device

saw_mj · 2017-07-22 09:03:13

seth wrote:

At least the lspci output is for an ethernet chip. No txpower, because it uses a cable :-P
Fwwi, the "Alfa awus036h" is promoted w/ 1W power, ie. you should be able to get 30 dBm, but you probably need to adjust the regularory domain first (what may be illegal and punishable at your location, google on details)
It may very well be that the device only supports some fixed txpower values.

yep that's why i tried to lower the Txpower and doesn't help and also try it to change my reg domain the same nothing happens

ugjka · 2017-07-22 10:12:43

saw_mj wrote:

ugjka wrote:
probably the driver doesn't support it for that chip
you saying that i'm using the wrong driver ?
I remember i checked it and that was the prober driver for the device

No I mean it simply not supported, the txpower value is probably hardcoded. Or maybe the chip itself doesn't have any capability to change the txpower

seth · 2017-07-22 12:39:49

Well, the thing explicitly claims 1W power...

Google indicates it's important to bring the device down before setting the txpower (and "adjusting" the reg domain)
Also check "dmesg -w" for errors on attempts to change the txpower.

---
Google also indicates that the reg domain for this device may be hardcoded, requiring to "mend" and recompile the regdb (which though should only impact upper limits)
You may find suggestions to raise the txpower even beyond 1W this way, but I'd suggest to do not. More power means more heat - what could easily kill the device.

cc. trying the above may be illegal for you.

ewaller · 2017-07-22 16:08:56

Out of curiosity, why are you trying to increase your output power? It may not help as much as you imagine. Direct sequencing spread spectrum plays by different rules than narrow band communications. "Yelling Louder" will not provide any benefit as long as your receiver can hear you in the first place. More importantly, the performance you you achieve, no matter how loud you yell, will be a function of how many other foreign networks either your client or server can see. If either the receiver or transmitter stations can detect other networks, they will back off on their data rates to allow the networks to exist in harmony. In general, increasing power will not provide an increase the performance of your network, but it will f**k with other peoples network and (and more of them) by causing them to reduce their data rates-- all without providing any utility to you.

Believe it or not, the best solution is to pick a band that has less range and pick a moderate power output so that devices at your site can see your AP, while not seeing AP points outside your site.

Besides, increasing your Tx power does not improve your Rx sensitivity. What about the other end of the link?

Last argument. Wireless radios enjoy relatively few regulatory hurdles at present. Screw with it and we will prod governmental regulatory agencies to do something about it. This is never good as politicians tend to be idiots when it comes to regulation of technologies they do not understand. We have already seen efforts to lock down routers so that people cannot mess with them; including changing the firmware. Keep it up, and will will see "anti tamper" provisions, fines for altering these radios in the name of preventing RF pollution, and, almost certainly, a tax levied on every AP to provide funds to enforce these regulations.

seth · 2017-07-22 16:17:28

It's not clear that he wants to do that at all - we're just trying to figure whether he can adjust txpower in any way.
The device also comes with a 5dBi antenna, so he might indeed want to lower the power in urban contexts.

The actual (and only) justification for increased txpower is btw "far range".

ewaller · 2017-07-22 16:20:07

Fair enough. And I tried to stop short of accusations.

Just one of my favorite soapboxes

saw_mj · 2017-07-23 03:29:11

No I mean it simply not supported, the txpower value is probably hardcoded. Or maybe the chip itself doesn't have any capability to change the txpower

The thing i'm positive about that i remember back when i was using Debian distro. i could change the Txpower with so much flexibilty.

Well, the thing explicitly claims 1W power...
Google indicates it's important to bring the device down before setting the txpower (and "adjusting" the reg domain)
Also check "dmesg -w" for errors on attempts to change the txpower.
---
Google also indicates that the reg domain for this device may be hardcoded, requiring to "mend" and recompile the regdb (which though should only impact upper limits)
You may find suggestions to raise the txpower even beyond 1W this way, but I'd suggest to do not. More power means more heat - what could easily kill the device.
cc. trying the above may be illegal for you.

Yes i tried to brought the device down before adjusting the Tx power but it didn't help and when i try to change the txpower it doesn't give me any error but it gives me this output when i bring the device up

[ 1423.081842] iwlwifi 0000:08:00.0: Microcode SW error detected.  Restarting 0x2000000.
[ 1423.081851] iwlwifi 0000:08:00.0: CSR values:
[ 1423.081855] iwlwifi 0000:08:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
[ 1423.081874] iwlwifi 0000:08:00.0:        CSR_HW_IF_CONFIG_REG: 0X00c89200
[ 1423.081890] iwlwifi 0000:08:00.0:          CSR_INT_COALESCING: 0X00000040
[ 1423.081905] iwlwifi 0000:08:00.0:                     CSR_INT: 0X00000000
[ 1423.081919] iwlwifi 0000:08:00.0:                CSR_INT_MASK: 0X00000000
[ 1423.081934] iwlwifi 0000:08:00.0:           CSR_FH_INT_STATUS: 0X00000000
[ 1423.081948] iwlwifi 0000:08:00.0:                 CSR_GPIO_IN: 0X00000000
[ 1423.081963] iwlwifi 0000:08:00.0:                   CSR_RESET: 0X00000000
[ 1423.081978] iwlwifi 0000:08:00.0:                CSR_GP_CNTRL: 0X080403c5
[ 1423.081992] iwlwifi 0000:08:00.0:                  CSR_HW_REV: 0X00000210
[ 1423.082007] iwlwifi 0000:08:00.0:              CSR_EEPROM_REG: 0Xd55555d5
[ 1423.082022] iwlwifi 0000:08:00.0:               CSR_EEPROM_GP: 0X00000000
[ 1423.082036] iwlwifi 0000:08:00.0:              CSR_OTP_GP_REG: 0Xd55555d5
[ 1423.082051] iwlwifi 0000:08:00.0:                 CSR_GIO_REG: 0X001f0042
[ 1423.082065] iwlwifi 0000:08:00.0:            CSR_GP_UCODE_REG: 0X00000000
[ 1423.082080] iwlwifi 0000:08:00.0:           CSR_GP_DRIVER_REG: 0X00000000
[ 1423.082095] iwlwifi 0000:08:00.0:           CSR_UCODE_DRV_GP1: 0X00000000
[ 1423.082109] iwlwifi 0000:08:00.0:           CSR_UCODE_DRV_GP2: 0X00000000
[ 1423.082124] iwlwifi 0000:08:00.0:                 CSR_LED_REG: 0X00000060
[ 1423.082139] iwlwifi 0000:08:00.0:        CSR_DRAM_INT_TBL_REG: 0X8846cad9
[ 1423.082154] iwlwifi 0000:08:00.0:        CSR_GIO_CHICKEN_BITS: 0X27800200
[ 1423.082168] iwlwifi 0000:08:00.0:             CSR_ANA_PLL_CFG: 0Xd55555d5
[ 1423.082183] iwlwifi 0000:08:00.0:      CSR_MONITOR_STATUS_REG: 0Xd3b7f757
[ 1423.082198] iwlwifi 0000:08:00.0:           CSR_HW_REV_WA_REG: 0X0001001a
[ 1423.082212] iwlwifi 0000:08:00.0:        CSR_DBG_HPET_MEM_REG: 0Xffff0010
[ 1423.082216] iwlwifi 0000:08:00.0: FH register values:
[ 1423.082241] iwlwifi 0000:08:00.0:         FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X46376600
[ 1423.082266] iwlwifi 0000:08:00.0:        FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X04637110
[ 1423.082291] iwlwifi 0000:08:00.0:                  FH_RSCSR_CHNL0_WPTR: 0X00000038
[ 1423.082316] iwlwifi 0000:08:00.0:         FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114
[ 1423.082341] iwlwifi 0000:08:00.0:          FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
[ 1423.082365] iwlwifi 0000:08:00.0:            FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
[ 1423.082420] iwlwifi 0000:08:00.0:    FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
[ 1423.082445] iwlwifi 0000:08:00.0:                FH_TSSR_TX_STATUS_REG: 0X07ff0001
[ 1423.082470] iwlwifi 0000:08:00.0:                 FH_TSSR_TX_ERROR_REG: 0X00000000
[ 1423.082602] iwlwifi 0000:08:00.0: Start IWL Error Log Dump:
[ 1423.082607] iwlwifi 0000:08:00.0: Status: 0x00000000, count: 6
[ 1423.082614] iwlwifi 0000:08:00.0: Loaded firmware version: 27.455470.0
[ 1423.082618] iwlwifi 0000:08:00.0: 0x000014FC | ADVANCED_SYSASSERT          
[ 1423.082622] iwlwifi 0000:08:00.0: 0x000002F0 | trm_hw_status0
[ 1423.082626] iwlwifi 0000:08:00.0: 0x00000000 | trm_hw_status1
[ 1423.082632] iwlwifi 0000:08:00.0: 0x00043CF8 | branchlink2
[ 1423.082635] iwlwifi 0000:08:00.0: 0x0004AEF2 | interruptlink1
[ 1423.082638] iwlwifi 0000:08:00.0: 0x00000000 | interruptlink2
[ 1423.082643] iwlwifi 0000:08:00.0: 0x01022400 | data1
[ 1423.082647] iwlwifi 0000:08:00.0: 0x000003E1 | data2
[ 1423.082650] iwlwifi 0000:08:00.0: 0x05010000 | data3
[ 1423.082657] iwlwifi 0000:08:00.0: 0x2C817BDE | beacon time
[ 1423.082661] iwlwifi 0000:08:00.0: 0x798A5420 | tsf low
[ 1423.082665] iwlwifi 0000:08:00.0: 0x0000002F | tsf hi
[ 1423.082668] iwlwifi 0000:08:00.0: 0x00000000 | time gp1
[ 1423.082672] iwlwifi 0000:08:00.0: 0x143C662B | time gp2
[ 1423.082676] iwlwifi 0000:08:00.0: 0x00000001 | uCode revision type
[ 1423.082679] iwlwifi 0000:08:00.0: 0x0000001B | uCode version major
[ 1423.082683] iwlwifi 0000:08:00.0: 0x0006F32E | uCode version minor
[ 1423.082690] iwlwifi 0000:08:00.0: 0x00000210 | hw version
[ 1423.082714] iwlwifi 0000:08:00.0: 0x00C89200 | board version
[ 1423.082717] iwlwifi 0000:08:00.0: 0x009C0151 | hcmd
[ 1423.082720] iwlwifi 0000:08:00.0: 0x00022000 | isr0
[ 1423.082724] iwlwifi 0000:08:00.0: 0x00000000 | isr1
[ 1423.082727] iwlwifi 0000:08:00.0: 0x00000002 | isr2
[ 1423.082730] iwlwifi 0000:08:00.0: 0x404140C0 | isr3
[ 1423.082736] iwlwifi 0000:08:00.0: 0x00000000 | isr4
[ 1423.082740] iwlwifi 0000:08:00.0: 0x009C0151 | last cmd Id
[ 1423.082743] iwlwifi 0000:08:00.0: 0x00000000 | wait_event
[ 1423.082746] iwlwifi 0000:08:00.0: 0x00000000 | l2p_control
[ 1423.082750] iwlwifi 0000:08:00.0: 0x00000000 | l2p_duration
[ 1423.082753] iwlwifi 0000:08:00.0: 0x0000003F | l2p_mhvalid
[ 1423.082756] iwlwifi 0000:08:00.0: 0x00000000 | l2p_addr_match
[ 1423.082762] iwlwifi 0000:08:00.0: 0x00000005 | lmpm_pmg_sel
[ 1423.082765] iwlwifi 0000:08:00.0: 0x04012314 | timestamp
[ 1423.082768] iwlwifi 0000:08:00.0: 0x00003848 | flow_handler
[ 1423.082779] ieee80211 phy0: Hardware restart was requested
[ 1423.195902] iwlwifi 0000:08:00.0: L1 Enabled - LTR Enabled
[ 1423.196466] iwlwifi 0000:08:00.0: L1 Enabled - LTR Enabled
[ 1423.264303] iwlwifi 0000:08:00.0: L1 Enabled - LTR Enabled
[ 1423.264858] iwlwifi 0000:08:00.0: L1 Enabled - LTR Enabled
[ 1427.903711] IPv6: ADDRCONF(NETDEV_UP): wlp0s20f0u1: link is not ready
[ 1443.475907] iwlwifi 0000:08:00.0: regular scan timed out
[ 1443.476488] iwlwifi 0000:08:00.0: Microcode SW error detected.  Restarting 0x2000000.
[ 1443.476493] iwlwifi 0000:08:00.0: CSR values:
[ 1443.476497] iwlwifi 0000:08:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
[ 1443.476606] iwlwifi 0000:08:00.0:        CSR_HW_IF_CONFIG_REG: 0X00c89200
[ 1443.476660] iwlwifi 0000:08:00.0:          CSR_INT_COALESCING: 0X00000040
[ 1443.476715] iwlwifi 0000:08:00.0:                     CSR_INT: 0X00000000
[ 1443.476770] iwlwifi 0000:08:00.0:                CSR_INT_MASK: 0X00000000
[ 1443.476825] iwlwifi 0000:08:00.0:           CSR_FH_INT_STATUS: 0X00000000
[ 1443.476877] iwlwifi 0000:08:00.0:                 CSR_GPIO_IN: 0X00000000
[ 1443.476931] iwlwifi 0000:08:00.0:                   CSR_RESET: 0X00000000
[ 1443.476984] iwlwifi 0000:08:00.0:                CSR_GP_CNTRL: 0X080403c5
[ 1443.477037] iwlwifi 0000:08:00.0:                  CSR_HW_REV: 0X00000210
[ 1443.477090] iwlwifi 0000:08:00.0:              CSR_EEPROM_REG: 0Xd55555d5
[ 1443.477143] iwlwifi 0000:08:00.0:               CSR_EEPROM_GP: 0X00000000
[ 1443.477196] iwlwifi 0000:08:00.0:              CSR_OTP_GP_REG: 0Xd55555d5
[ 1443.477249] iwlwifi 0000:08:00.0:                 CSR_GIO_REG: 0X001f0042
[ 1443.477302] iwlwifi 0000:08:00.0:            CSR_GP_UCODE_REG: 0X00000000
[ 1443.477357] iwlwifi 0000:08:00.0:           CSR_GP_DRIVER_REG: 0X00000000
[ 1443.477413] iwlwifi 0000:08:00.0:           CSR_UCODE_DRV_GP1: 0X00000000
[ 1443.477468] iwlwifi 0000:08:00.0:           CSR_UCODE_DRV_GP2: 0X00000000
[ 1443.477523] iwlwifi 0000:08:00.0:                 CSR_LED_REG: 0X00000060
[ 1443.477578] iwlwifi 0000:08:00.0:        CSR_DRAM_INT_TBL_REG: 0X8846cad9
[ 1443.477632] iwlwifi 0000:08:00.0:        CSR_GIO_CHICKEN_BITS: 0X27800200
[ 1443.477684] iwlwifi 0000:08:00.0:             CSR_ANA_PLL_CFG: 0Xd55555d5
[ 1443.477738] iwlwifi 0000:08:00.0:      CSR_MONITOR_STATUS_REG: 0Xd3b7f777
[ 1443.477791] iwlwifi 0000:08:00.0:           CSR_HW_REV_WA_REG: 0X0001001a
[ 1443.477844] iwlwifi 0000:08:00.0:        CSR_DBG_HPET_MEM_REG: 0Xffff0010
[ 1443.477847] iwlwifi 0000:08:00.0: FH register values:
[ 1443.477909] iwlwifi 0000:08:00.0:         FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X46376600
[ 1443.477972] iwlwifi 0000:08:00.0:        FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X04637110
[ 1443.478032] iwlwifi 0000:08:00.0:                  FH_RSCSR_CHNL0_WPTR: 0X00000078
[ 1443.478091] iwlwifi 0000:08:00.0:         FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00801114
[ 1443.478150] iwlwifi 0000:08:00.0:          FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
[ 1443.478372] iwlwifi 0000:08:00.0:            FH_MEM_RSSR_RX_STATUS_REG: 0X03030000
[ 1443.478432] iwlwifi 0000:08:00.0:    FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
[ 1443.478496] iwlwifi 0000:08:00.0:                FH_TSSR_TX_STATUS_REG: 0X07ff0001
[ 1443.478560] iwlwifi 0000:08:00.0:                 FH_TSSR_TX_ERROR_REG: 0X00000000
[ 1443.478725] iwlwifi 0000:08:00.0: Start IWL Error Log Dump:
[ 1443.478729] iwlwifi 0000:08:00.0: Status: 0x00000000, count: 6
[ 1443.478733] iwlwifi 0000:08:00.0: Loaded firmware version: 27.455470.0
[ 1443.478737] iwlwifi 0000:08:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[ 1443.478740] iwlwifi 0000:08:00.0: 0x000002F0 | trm_hw_status0
[ 1443.478743] iwlwifi 0000:08:00.0: 0x00000000 | trm_hw_status1
[ 1443.478746] iwlwifi 0000:08:00.0: 0x00043CF8 | branchlink2
[ 1443.478749] iwlwifi 0000:08:00.0: 0x0004AEF2 | interruptlink1
[ 1443.478752] iwlwifi 0000:08:00.0: 0x000001E4 | interruptlink2
[ 1443.478755] iwlwifi 0000:08:00.0: 0x00000000 | data1
[ 1443.478758] iwlwifi 0000:08:00.0: 0x00000080 | data2
[ 1443.478761] iwlwifi 0000:08:00.0: 0x07030000 | data3
[ 1443.478764] iwlwifi 0000:08:00.0: 0x20C1392F | beacon time
[ 1443.478767] iwlwifi 0000:08:00.0: 0x7AC186CF | tsf low
[ 1443.478770] iwlwifi 0000:08:00.0: 0x0000002F | tsf hi
[ 1443.478773] iwlwifi 0000:08:00.0: 0x00000000 | time gp1
[ 1443.478776] iwlwifi 0000:08:00.0: 0x013447F2 | time gp2
[ 1443.478779] iwlwifi 0000:08:00.0: 0x00000001 | uCode revision type
[ 1443.478782] iwlwifi 0000:08:00.0: 0x0000001B | uCode version major
[ 1443.478785] iwlwifi 0000:08:00.0: 0x0006F32E | uCode version minor
[ 1443.478788] iwlwifi 0000:08:00.0: 0x00000210 | hw version
[ 1443.478791] iwlwifi 0000:08:00.0: 0x00C89200 | board version
[ 1443.478794] iwlwifi 0000:08:00.0: 0x0000001C | hcmd
[ 1443.478797] iwlwifi 0000:08:00.0: 0x00022000 | isr0
[ 1443.478800] iwlwifi 0000:08:00.0: 0x00000000 | isr1
[ 1443.478803] iwlwifi 0000:08:00.0: 0x00000002 | isr2
[ 1443.478806] iwlwifi 0000:08:00.0: 0x40400082 | isr3
[ 1443.478808] iwlwifi 0000:08:00.0: 0x00000000 | isr4
[ 1443.478812] iwlwifi 0000:08:00.0: 0x004B014E | last cmd Id
[ 1443.478814] iwlwifi 0000:08:00.0: 0x00000000 | wait_event
[ 1443.478817] iwlwifi 0000:08:00.0: 0x00000000 | l2p_control
[ 1443.478820] iwlwifi 0000:08:00.0: 0x00000020 | l2p_duration
[ 1443.478823] iwlwifi 0000:08:00.0: 0x0000003F | l2p_mhvalid
[ 1443.478826] iwlwifi 0000:08:00.0: 0x000000CE | l2p_addr_match
[ 1443.478830] iwlwifi 0000:08:00.0: 0x00000005 | lmpm_pmg_sel
[ 1443.478832] iwlwifi 0000:08:00.0: 0x04012314 | timestamp
[ 1443.478835] iwlwifi 0000:08:00.0: 0x00347888 | flow_handler
[ 1443.478841] ieee80211 phy0: Hardware restart was requested
[ 1443.627778] iwlwifi 0000:08:00.0: L1 Enabled - LTR Enabled
[ 1443.628226] iwlwifi 0000:08:00.0: L1 Enabled - LTR Enabled
[ 1443.695648] iwlwifi 0000:08:00.0: L1 Enabled - LTR Enabled
[ 1443.696240] iwlwifi 0000:08:00.0: L1 Enabled - LTR Enabled

Out of curiosity, why are you trying to increase your output power? It may not help as much as you imagine. Direct sequencing spread spectrum plays by different rules than narrow band communications. "Yelling Louder" will not provide any benefit as long as your receiver can hear you in the first place. More importantly, the performance you you achieve, no matter how loud you yell, will be a function of how many other foreign networks either your client or server can see. If either the receiver or transmitter stations can detect other networks, they will back off on their data rates to allow the networks to exist in harmony. In general, increasing power will not provide an increase the performance of your network, but it will f**k with other peoples network and (and more of them) by causing them to reduce their data rates-- all without providing any utility to you.
Believe it or not, the best solution is to pick a band that has less range and pick a moderate power output so that devices at your site can see your AP, while not seeing AP points outside your site.
Besides, increasing your Tx power does not improve your Rx sensitivity. What about the other end of the link?
Last argument. Wireless radios enjoy relatively few regulatory hurdles at present. Screw with it and we will prod governmental regulatory agencies to do something about it. This is never good as politicians tend to be idiots when it comes to regulation of technologies they do not understand. We have already seen efforts to lock down routers so that people cannot mess with them; including changing the firmware. Keep it up, and will will see "anti tamper" provisions, fines for altering these radios in the name of preventing RF pollution, and, almost certainly, a tax levied on every AP to provide funds to enforce these regulations.

ahaa you see i don't only want to increase txpower but also decrease it sometimes it depens on my usage for the device sometime all i need is just a wifi device to connect to a very near AP, and sometimes i need to connect it thru an AP is far from my building.
so actually i need it to be flexibile for my usage and about

and about wether it's legal or not. it's legal for me where i live.

seth · 2017-07-23 07:54:15

Errr... iwlwifi is for an intel chip (likely the integrated device?)

n37 · 2017-07-23 08:59:18

https://wiki.archlinux.org/index.php/Wi … ory_domain

All that you need is in there. In a nutshell, you need to have crda installed in order to change the regdom. If the selected regdom allows it, then you could set the txpower to 1W. The Alfa hardware (if genuine), supports 1W.

saw_mj · 2017-07-23 10:29:34

Errr... iwlwifi is for an intel chip (likely the integrated device?)

hmmm then it doesn't give me any error about the Alfa card

https://wiki.archlinux.org/index.php/Wi … ory_domain
All that you need is in there. In a nutshell, you need to have crda installed in order to change the regdom. If the selected regdom allows it, then you could set the txpower to 1W. The Alfa hardware (if genuine), supports 1W.

i already installed the crda and successfully could change my regdom and i also mentioned that i can adjust my integrated intel device but can't with the alfa card .

n37 · 2017-07-23 14:15:52

I had to dig out my Alfa. Here it is at 1W.

# lsusb
Bus 001 Device 010: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter

# iw dev wlp0s20f0u1 info
Interface wlp0s20f0u1
        ...
	txpower 30.00 dBm

If I were you, I would double check whether your regdom really allows 30dBm at 2.4GHz.

# iw reg get
global
country ...
	(2402 - 2472 @ 40), (N/A, 30), (N/A)
        ...

Last edited by n37 (2017-07-23 15:20:13)

seth · 2017-07-23 14:20:16

Don't get this wrong, but "it gives me this output when i bring the device up" sounds like you're operating on the wrong device? Otoh, the output covers 20 seconds, so that may be a red herring.

Just to be sure: when trying to bring the device down and adjust txpower, there's no service (networkmanager, wpa_supplicant, systemd-netword, netctl, wicd, connman, ....) running on the device? (And then i'm running out of ideas)

Ultimately, let's get into details ;-)

iw list
iw reg get

n37 · 2017-07-23 15:18:58

In all likelihood, it is the regdom. The one that is used in virtually all of the online "tutorials" is no longer specified at up to 30dBm at 2.4GHz. In the current ARCH release of wireless-regdb (2016.06.10-1) it is capped at 20 dBm. I had not used my Alfa for some time and this gave me a surprise at first. Still there are other domains which would allow 1W.

The Alfa is a USB device, so there is no need to bring it down. It is enough to disconnect and reconnect after setting the new domain and it will take the max txpower of the new domain.

seth · 2017-07-23 15:40:30

That doesn't explain the inability to lower the txpower, though.
Good to know though, that <undisclosed south-american country> altered its rules ;-)

saw_mj · 2017-07-24 07:04:18

Ok guys, Finally i knew what was the problem.

First of all it was the Regdomain most of reg-domain you only can use its maximum txpower dunno why but for an example

	(2402 - 2482 @ 40), (N/A, 30), (N/A)
	(5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW
	(5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
	(5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)

this regdomain only support 30dBm at 2.4GHz band and the lowest power you can get is specified as N/A

I don't know why but the only txpower adjustment you can get is 30dBm not 29, not 20, not 31. nothing BUT 30dBm

and most of regdomains has the same issue the only adjustment you can get is with its maximum field so that's was the problem i couldn't lower the Txpower

and the other thing after you adjust the txpower with the only supported change it doesn't give any sign of success of the changing until some times, so i should wait for 2~3 min i dunno maybe more.

And now i gotta search for a regdomain the max field with it around 15dBm or something.

And Thank you guys for your help

Last edited by saw_mj (2017-07-24 07:08:40)

Arch Linux

#1 2017-07-22 05:05:39

[SOLVED] Adjusting my wireless card Txpower

#2 2017-07-22 05:53:04

Re: [SOLVED] Adjusting my wireless card Txpower

#3 2017-07-22 06:57:02

Re: [SOLVED] Adjusting my wireless card Txpower

#4 2017-07-22 07:30:31

Re: [SOLVED] Adjusting my wireless card Txpower

#5 2017-07-22 08:11:28

Re: [SOLVED] Adjusting my wireless card Txpower

#6 2017-07-22 09:01:39

Re: [SOLVED] Adjusting my wireless card Txpower

#7 2017-07-22 09:03:13

Re: [SOLVED] Adjusting my wireless card Txpower

#8 2017-07-22 10:12:43

Re: [SOLVED] Adjusting my wireless card Txpower

#9 2017-07-22 12:39:49

Re: [SOLVED] Adjusting my wireless card Txpower

#10 2017-07-22 16:08:56

Re: [SOLVED] Adjusting my wireless card Txpower

#11 2017-07-22 16:17:28

Re: [SOLVED] Adjusting my wireless card Txpower

#12 2017-07-22 16:20:07

Re: [SOLVED] Adjusting my wireless card Txpower

#13 2017-07-23 03:29:11

Re: [SOLVED] Adjusting my wireless card Txpower

#14 2017-07-23 07:54:15

Re: [SOLVED] Adjusting my wireless card Txpower

#15 2017-07-23 08:59:18

Re: [SOLVED] Adjusting my wireless card Txpower

#16 2017-07-23 10:29:34

Re: [SOLVED] Adjusting my wireless card Txpower

#17 2017-07-23 14:15:52

Re: [SOLVED] Adjusting my wireless card Txpower

#18 2017-07-23 14:20:16

Re: [SOLVED] Adjusting my wireless card Txpower

#19 2017-07-23 15:18:58

Re: [SOLVED] Adjusting my wireless card Txpower

#20 2017-07-23 15:40:30

Re: [SOLVED] Adjusting my wireless card Txpower

#21 2017-07-24 07:04:18

Re: [SOLVED] Adjusting my wireless card Txpower

Board footer