From: Ping-Ke Shih <pkshih@realtek.com>
To: Philipp Matthias Hahn <pmhahn@pmhahn.de>,
"iwd@lists.linux.dev" <iwd@lists.linux.dev>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Kalle Valo <kvalo@kernel.org>
Subject: RE: rtw89_8852ce + iwd stuck in (dis-)connect/-auth loop
Date: Fri, 15 Nov 2024 01:43:06 +0000 [thread overview]
Message-ID: <eecdb8b482f947aaabd08a4a02913bfc@realtek.com> (raw)
In-Reply-To: <ZzW9IIrc-HYQuD6-@birdy.pmhahn.de>
Philipp Matthias Hahn <pmhahn@pmhahn.de> wrote:
> Hello,
>
> I finally switched from `wpa_supplicant` to `iwd` after having regular
> issues with connectivity issues, so the following problem is probably
> not related to `iwd` at all.
>
> APs:
> - FRITZ!Box 7490 one
> - 34:31:C4:27:99:ED (2.4 GHz)
> - 34:31:C4:27:99:EE (5 Ghz)
> - FRITZ!Box 7490 two
> - E8:DF:70:4A:46:AB (2.4 GHz)
> - E8:DF:70:4A:46:AC (5 GHz)
> - FRITZ!Powerline 1260E
> - F0:B0:14:88:AC:43 (2.4 GHz)
> - F0:B0:14:88:AC:47 (5 GHz)
> - FRITZ!Powerline 540E
> - 5C:49:79:E1:C5:94 (2.4 GHz)
I'm not familiar with these AP brands. Are they all the same brand?
Can you try another AP brand? Empirically some AP send beacon with larger
variant timing that WiFi adapter can't receive beacon at correct moment.
>
> Debian-12-Buster
> iwd original: 2.3, now: 3.1 self-compiled
> Linux 6.10.11
> 04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit
> Ethernet Controller [10ec:8168] (rev 15)
This is Ethernet not wireless adapter, but I can skip this information for now.
>
> [87572.028075] wlan0: authenticate with 34:31:c4:27:99:ee (local address=40:1a:58:f6:ca:6f)
> [87572.028079] wlan0: send auth to 34:31:c4:27:99:ee (try 1/3)
> [87572.031085] wlan0: authenticated
> [87572.036527] wlan0: associate with 34:31:c4:27:99:ee (try 1/3)
> [87572.039534] wlan0: RX AssocResp from 34:31:c4:27:99:ee (capab=0x1511 status=0 aid=2)
> [87572.158153] wlan0: associated
> [87572.158264] wlan0: Limiting TX power to 20 (23 - 3) dBm as advertised by 34:31:c4:27:99:ee
> [87581.686018] wlan0: Connection to AP 34:31:c4:27:99:ee lost
I feel the connection lost because of beacon lost causing by power save.
Please try
sudo iw wlan0 set power_save off
to see if it can get stable.
>
> I have seen that "Limiting TX power to …" before with `wpa_supplicant`,
> which also lead to a disconnect there, which triggered me to try `iwd`
> now.
I think the message is not related to this problem, because driver has its
own TX power management.
>
> Last time unloading `rtw89_8852ce` and re-loading it did get it, but
> only after switching Wifi off and on again in NetworkManager.
To be clear... is it work only after switching WiFi off/on? It doesn't work?
If so, seemingly some settings are still persistent when WiFi off.
prev parent reply other threads:[~2024-11-15 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 9:04 rtw89_8852ce + iwd stuck in (dis-)connect/-auth loop Philipp Matthias Hahn
2024-11-14 13:05 ` James Prestwood
2024-11-15 1:43 ` Ping-Ke Shih [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=eecdb8b482f947aaabd08a4a02913bfc@realtek.com \
--to=pkshih@realtek.com \
--cc=iwd@lists.linux.dev \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pmhahn@pmhahn.de \
/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