Modify

Opened 6 years ago

Closed 6 years ago

Last modified 4 years ago

#11135 closed defect (invalid)

strange txpower behaviour (AR9381 here on WZR-HP-G450H)

Reported by: Halo2 Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: Cc:

Description

        option diversity '0'

--

        option txantenna '0'
        option rxantenna '0'

reboot

        option txpower '[1-19]'

wifi

wlan0     unknown transmit-power information.

          Current Tx-Power=19 dBm       (79 mW)
        option txpower '20'

wifi

wlan0     unknown transmit-power information.

          Current Tx-Power=20 dBm       (100 mW)

-

        option txantenna '1'
        option rxantenna '1'

reboot

        option txpower '[1-14]'

wifi

wlan0     unknown transmit-power information.

          Current Tx-Power=14 dBm       (25 mW)
        option txpower '15-20'

wifi

wlan0     unknown transmit-power information.

          Current Tx-Power=15 dBm       (31 mW)

---

Conclusion:

wrong tx/rx power behaviour and/or information

behaviour differs on first and second antenna (third antenna not selectable at all - see ticket #11134)

Attachments (0)

Change History (4)

comment:1 follow-up: Changed 6 years ago by jow

  • Resolution set to invalid
  • Status changed from new to closed

The wireless-utils family of tools (iwconfig, iwlist) is deprecated. It is also entirely normal for the driver to not expose txpower levels via wext, this api has been deprecated.

As for the power value -> power level mapping; the driver only supports certain levels which your value is rounded towards to. You can't seamlessly set values in 1dBm steps in many cases.

comment:2 in reply to: ↑ 1 Changed 6 years ago by anonymous

Replying to jow:

The wireless-utils family of tools (iwconfig, iwlist) is deprecated. It is also entirely normal for the driver to not expose txpower levels via wext, this api has been deprecated.

As for the power value -> power level mapping; the driver only supports certain levels which your value is rounded towards to. You can't seamlessly set values in 1dBm steps in many cases.

Just want to state that only 2 values were displayed:

19 or 20 on Antenna 0

14 or 15 on Antenna 1

Definitely to few.

So what would be a proper way to check this now?

Never seen it this bad on another device.

Unfortunately currently no spectrum analyzer in reach, but i think chances are high that it won't convince..

comment:3 Changed 6 years ago by Halo2

Solved now (tested on r31650)

comment:4 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.