openwrt / openwrt/mt76

Alfa Network AWUS036AXML: TX power limited to 3 dBm (not sure if for real or just innacurate report), UL speed much worse than AWUS036ACM

Open
#783 56 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
888
Forks
436
PR merge metrics
No merged PRs in 30d

Description

I bought a new USB WiFi adapter, Alfa Network AWUS036AXML, and tried to use it on my desktop with Arch Linux. The kernel version is 6.3.3, the linux-firmware package version is 20230404.2e92a49f-1.

The adapter is recognized, but in the 5 GHz band, the TX power is limited to 3 dBm. I am in the Philippines, and the regulatory domain is set correctly. The bad received signal strength is also confirmed by my router.

As this is a USB card, there is no such thing as a "factory partition" from where the calibration data can be obtained.

# iw dev
phy#2
	Interface wlp0s20u4i3
		ifindex 34
		wdev 0x200000001
		addr 00:c0:ca:b3:c7:3c
		ssid Archer
		type managed
		channel 153 (5765 MHz), width: 80 MHz, center1: 5775 MHz
		txpower 3.00 dBm
		multicast TXQ:
			qsz-byt	qsz-pkt	flows	drops	marks	overlmt	hashcol	tx-bytes	tx-packets
			0	0	0	0	0	0	0	0		0
phy#0  <-- onboard WiFi, please ignore
	Interface wlp4s0
		ifindex 4
		wdev 0x1
		addr f2:b5:c2:8a:89:b9
		type managed
		txpower 20.00 dBm
		multicast TXQ:
			qsz-byt	qsz-pkt	flows	drops	marks	overlmt	hashcol	tx-bytes	tx-packets
			0	0	0	0	0	0	0	0		0

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no source file or test; begin by reproducing the AWUS036AXML behavior with the supplied iw dev output on kernel 6.3.3 and linux-firmware 20230404.2e92a49f-1. Compare the 5 GHz TX power and UL performance with the reported regulatory setup, then determine whether the issue is an inaccurate report or a driver or calibration problem and document the result.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.