You are not logged in.
i checked my journalctl -b and i could see constant errors like this
Jan 11 14:27:36 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-58 noise=9999 txrate=108000
Jan 11 14:27:39 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=135000
Jan 11 14:27:42 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=135000
Jan 11 14:27:45 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=135000
Jan 11 14:27:48 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=108000
Jan 11 14:27:51 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=162000
Jan 11 14:27:54 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=162000
Jan 11 14:27:57 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=108000
Jan 11 14:28:00 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=108000
Jan 11 14:28:03 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=54000
Jan 11 14:28:06 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=54000
Jan 11 14:28:09 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-53 noise=9999 txrate=108000
Jan 11 14:28:12 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-54 noise=9999 txrate=108000
Jan 11 14:28:15 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-53 noise=9999 txrate=108000
Jan 11 14:28:18 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-53 noise=9999 txrate=108000
Jan 11 14:28:21 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-51 noise=9999 txrate=162000
Jan 11 14:28:24 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-53 noise=9999 txrate=162000
Jan 11 14:28:27 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=162000
Jan 11 14:28:30 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-52 noise=9999 txrate=162000
Jan 11 14:28:33 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-52 noise=9999 txrate=162000
Jan 11 14:28:36 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-52 noise=9999 txrate=108000
Jan 11 14:28:39 akai wpa_supplicant[736]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-53 noise=9999 txrate=108000
The wifi module
output of lspci :
01:00.0 Network controller: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz
Last edited by akai (2026-01-11 14:26:27)
Offline
That's not a error - wpa logs signal quality changes (the signal quality is ok)
This is kinda normal because NM enabled wpa_supplicant's debug output, but the 3s frequency there is excessive.
The trigger might be some power saving or roaming or whatever causing frequent reconnects.
Please don't grep for random strings, post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.stOffline
Offline
read the note
Offline
Which one? This has nothing to do w/ resolved.
Disable systemd-networkd, but I doubt that to be the cause either.
cat /proc/$(pidof wpa_supplicant)/cmdlineIt would seem either you or NM have risen the debug level, there's nothing else to explain the excessive signal logging.
Offline
https://gitlab.archlinux.org/archlinux/ … e3da12128e
https://archlinux.org/packages/core-tes … upplicant/
Which one
the first bullet point
Offline
cat /proc/$(pidof wpa_supplicant)/cmdline
shell:
/usr/bin/wpa_supplicant-u-s-O/run/wpa_supplicant%
Offline
https://gitlab.archlinux.org/archlinux/ … e3da12128e
https://archlinux.org/packages/core-tes … upplicant/seth wrote:Which one
the first bullet point
so was there a problem within the wpa_suplicant from core. and should i change it to one from core testing brach.
Offline
and should i change it to one from core testing brach.
No, see https://wiki.archlinux.org/title/Offici … positories
In doubt wait.
Unlike the wiki note the merge request is relevant but it was opened 7 months ago and I haven't seen this excessive signal reports during that time (or ever) - but it might be chip dependent.
Upstream patch is https://git.w1.fi/cgit/hostap/commit/wp … 2d9c69166a
Offline
and should i change it to one from core testing brach.
No, see https://wiki.archlinux.org/title/Offici … positories
In doubt wait.Unlike the wiki note the merge request is relevant but it was opened 7 months ago and I haven't seen this excessive signal reports during that time (or ever) - but it might be chip dependent.
Upstream patch is https://git.w1.fi/cgit/hostap/commit/wp … 2d9c69166a
i think the core-testing did the work for now
this is the log now : http://0x0.st/PXeb.txt
Offline
For clarification: Do not cherry pick stuff out of the testing repos!
You can switch to ALL packages from ALL testing repos or none at all.
Picking isolated packages *can* work at times but also *can* (more often than never) result in major issues and is generally a terrible idea.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
For clarification: Do not cherry pick stuff out of the testing repos!
You can switch to ALL packages from ALL testing repos or none at all.Picking isolated packages *can* work at times but also *can* (more often than never) result in major issues and is generally a terrible idea.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
So should i stick with the core and build only the wpa_suppliacnt from the testing.
Last edited by akai (2026-01-11 14:14:43)
Offline
That's exactly the opposite of what seth said.
Offline
That's exactly the opposite of what seth said.
eeeee... sry and thx sytem72, seth and Scimmia for the help.
Last edited by akai (2026-01-11 14:33:29)
Offline
To add some context, also for future readers:
In this particular case, looking at the build history and dependencies of wpa_supplicant:
Using the binary from the testing repo is unlikely to cause any further problems - and after all it's your system and you can do whatever you want.
What you need to understand is that this isn't a reasonable general strategy and the rule of thumb is that
if you've to ask, you better do not dive into the testing repos
(let alone cherry picking it) because you're unlikely prepared to deal with things going wrong (which will more typically be the result)
More experienced users (and certainly the developers/packagers) might very much habitually break these guidelines, but they will also then not show up on the forum because their system no longer boots.
They know what they're doing, understand what the potential consequences are, how to safeguard that and in doubt get out of the mess they created.
Offline
mm. OK
Offline
should i change it to one from core testing brach.
wait till the package hits the main core repo unless your competent enough to mix and match testing packages with non testing packages, theres always a chance you can run into dependency issues down the road, there are a few example threads on the forums showcasing this e.g. https://bbs.archlinux.org/viewtopic.php … 7#p2282077
but really, if the testing package is working fine for you then i don't see a reason why you can't use it, as long as you disable the testing repos and move back to the package in the core repository after that version moves there it's fine
on a side note i wonder why wpa supplicant is in core when alternatives like iwd are in extra lol
Last edited by system72 (2026-01-11 15:15:36)
Offline
I was gonna say because iwd depends on other pacakges from extra, but wpa_supplicant depends on https://archlinux.org/packages/extra/x86_64/pcsclite/
So … for traditional reasons and cultural heritage ![]()
Offline
I was gonna say because iwd depends on other pacakges from extra, but wpa_supplicant depends on https://archlinux.org/packages/extra/x86_64/pcsclite/
So … for traditional reasons and cultural heritage
Ok so i changed from wpa_supplicant to iwd as Network manager backend. And removed wpa_supplicant.
Last edited by akai (2026-01-11 15:32:05)
Offline
Ok so i changed from wpa_supplicant to iwd as Network manager backend. And removed wpa_supplicant.
well thats one way to fix it, for correct configuration with networkmanager see:
Offline