From: cybersnow_2001@tutamail.com
To: John Scott <jscott@posteo.net>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: Atheros AR9280 / AR7010 Initial low scaning signal range
Date: Mon, 6 Jul 2026 20:15:10 +0200 (CEST) [thread overview]
Message-ID: <OwscydZ--F-9@tutamail.com> (raw)
In-Reply-To: <c2163c6ee67e982fd95d1f965ecf0b853f687214.camel@posteo.net>
Thanks for looking at it. Here is what I could find on the Web about the same issue. Someone said Kernel 6.4 and earlier worked. You might try with Debian Live DVD Buster, Bullseye and others distro if you want. I tried to use an older firmware of Atheros v1.3 instead of 1.4, same problem. I wonder if there are older firmware... But I'm not sure if this is related to the firmware. It might be more about the kernel 80211 modules... Or it might be an electronic issue coming from the chip itself. I need to do a cold/freeze and very hot test to see if it solve the issue...
https://discussion.fedoraproject.org/t/need-help-with-weak-wifi-signal-on-fedora-with-qualcomm-atheros-card/87854
https://www.spinics.net/lists/linux-wireless/msg90423.html
https://forum.mikrotik.com/t/ar9280-low-speed/62030
https://forums.freebsd.org/threads/atheros-ar9280-wifi-not-working.68357/
https://forum.opnsense.org/index.php?topic=28266.0
https://forum.mikrotik.com/t/compex-wle200nx-atheros-ar9280/166217/3
https://forum.netgate.com/topic/83364/atheros-ar9280-testing-settings-craziness-success-ymmv/2
https://forums.tomshardware.com/threads/qualcomm-atheros-ar9287-terrible-range.2687938/
https://forum.netgate.com/topic/53616/atheros-ar9280-ath0-stuck-beacon-resetting-bmiss-count-4-hangs-later/2
https://forums.linuxmint.com/viewtopic.php?t=299646
Jul 4, 2026, 17:25 by jscott@posteo.net:
> On Wed, 2026-07-01 at 04:08 +0200, cybersnow_2001@tutamail.com wrote:
>
>> I've read in another forum that people experienced the same issue after a kernel update, maybe after 6.8. What do you think?
>>
>
> I think I can partially reproduce the problem. I have a Sony UWA-BR100 on Debian Trixie (kernel 6.12.94) and a wireless scan only shows very few access points, never more than -65 dBm or so. The access point for my home, being the closest one to me, actually has the *worst* signal strength value reported as -80 dBm consistently. A scan for access points does show 5GHz ones, but it chose to connect to my AP on 2.4GHz (which may or may not be legitimate; iwd normally joins the 5GHz ones when I'm using dual-band NICs). I did not observe any circumstance in which the reported signal became better, though.
>
> With a TP-Link TL-WN822N v2 (still AR7010, but the 2.4GHz-only AR9287 instead of dual-band AR9280), everything is excellent, so indeed it seems only the AR9280 devices are affected.
> Could you share that forum link? I'm not sure I'll get around to it but my next steps would be to bisect the kernel using a virtual machine and USB pass-through. This is strange indeed...
>
prev parent reply other threads:[~2026-07-06 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 2:08 Atheros AR9280 / AR7010 Initial low scaning signal range cybersnow_2001
2026-07-04 17:25 ` John Scott
2026-07-06 18:15 ` cybersnow_2001 [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=OwscydZ--F-9@tutamail.com \
--to=cybersnow_2001@tutamail.com \
--cc=jscott@posteo.net \
--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