From: Ping-Ke Shih <pkshih@realtek.com>
To: Plamen Dimitrov <plamen.dimitrov@pevogam.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: Thu, 25 Apr 2024 05:41:30 +0000 [thread overview]
Message-ID: <4e6da84a3a274fcebaae86c42f80458f@realtek.com> (raw)
In-Reply-To: <89fccaa8-af18-4192-8186-f76577694b97@pevogam.com>
Plamen Dimitrov <plamen.dimitrov@pevogam.com> wrote:
> On 4/23/24 10:49, Ping-Ke Shih wrote:
> > Plamen Dimitrov<plamen.dimitrov@pevogam.com> wrote:
> >>> 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.
> >>
> > If you use network manager as WiFi controller, set 'wifi.powersave = 2' in config file [1].
> >
> > [1]https://gist.github.com/jcberthon/ea8cfe278998968ba7c5a95344bc8b55
>
> So I applied this with the wifi card failing again with the above errors. Then I tried the same NetworkManager
> config
> but with a full reboot and the wifi crashed again. I reissued the previous `iw` comment to set this but
> then the wifi
> crashed again before and after additional cold reboot. I am really not sure what is going on here. Should
> I look for
> more logs once this happens again despite the powersave mode?
Using 'sudo iw wlan0 get power_save' to check power save status expected.
next prev parent reply other threads:[~2024-04-25 5:41 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
2024-04-23 2:49 ` Ping-Ke Shih
2024-04-25 3:30 ` Plamen Dimitrov
2024-04-25 5:41 ` Ping-Ke Shih [this message]
[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=4e6da84a3a274fcebaae86c42f80458f@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=plamen.dimitrov@pevogam.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).