From: Plamen Dimitrov <plamen.dimitrov@pevogam.com>
To: Ping-Ke Shih <pkshih@realtek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Problems with RTL8852BE PCIe 802.11ax Wireless Network Controller and Linux kernel 6.7.7-100.fc38.x86_64
Date: Tue, 23 Apr 2024 10:30:55 +0800 [thread overview]
Message-ID: <94f3355c-b247-4215-a046-a39293c8d03e@pevogam.com> (raw)
In-Reply-To: <efc3e8306e1b417cbb779109a4a5ff54@realtek.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1332 bytes --]
On 4/16/24 10:31, Ping-Ke Shih wrote:
> Plamen Dimitrov<plamen.dimitrov@pevogam.com> wrote:
>
>> Indeed, I had tried this before but did not include it in my report. Now I decided to redo everything
>> just in case and the WiFi still disappears within a few minutes with logs like
> Did you mean it works initially but WiFi got lost after a while?
Exactly. Sometimes it may even work for hours before I hit the issue, right now I tried with kernel
6.7.11-100.fc38.x86_64
and the issue happens after a few minutes.
> Please attach your full log from boot (via private mail if you have concern).
>
> Another try is to disable power save by 'iw' command right after booting, like
> sudo iw wlan0 set power_save off
I had to take a while to make sure that this indeed worked and so far it took some days without any failure
which makes me guess that this has actually helped. I even tried rebooting again and the problem is still
likely fixed. I will monitor the situation but for the sake of sustainable solution, I guess the above
does set a setting that we could not set in any other way? It seems to work and that's great, I just wonder
if running `sudo iw wlan0 set power_save off` upon each reboot or kernel update can be replaced with something
more long lasting.
Best,
Plamen Dimitrov
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3211 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2024-04-23 2:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 8:04 Problems with RTL8852BE PCIe 802.11ax Wireless Network Controller and Linux kernel 6.7.7-100.fc38.x86_64 Plamen Dimitrov
2024-04-16 0:31 ` Ping-Ke Shih
2024-04-16 2:23 ` Plamen Dimitrov
2024-04-16 2:31 ` Ping-Ke Shih
2024-04-23 2:30 ` Plamen Dimitrov [this message]
2024-04-23 2:49 ` Ping-Ke Shih
2024-04-25 3:30 ` Plamen Dimitrov
2024-04-25 5:41 ` Ping-Ke Shih
[not found] ` <c26272e9-069a-44b0-aee5-49530c084365@pevogam.com>
[not found] ` <d69ab1ccd3fd456a82ae954d25d056ba@realtek.com>
2024-05-13 3:34 ` Plamen Dimitrov
2024-05-14 3:26 ` Plamen Dimitrov
2024-05-15 3:47 ` Ping-Ke Shih
2024-05-15 5:40 ` Kalle Valo
2024-05-17 3:01 ` Plamen Dimitrov
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=94f3355c-b247-4215-a046-a39293c8d03e@pevogam.com \
--to=plamen.dimitrov@pevogam.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).