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, 14 May 2024 11:26:57 +0800 [thread overview]
Message-ID: <23d3e142-125a-4b3f-99f6-1f85d47541f7@pevogam.com> (raw)
In-Reply-To: <25c629d5-f356-4eeb-a2e2-e184f024fad0@pevogam.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 19292 bytes --]
With the newest Fedora kernel and firmware version I see different errors:
┌May 14 10:20:28 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin │
│May 14 10:20:28 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: enabling device (0000 -> 0003) │
│May 14 10:20:28 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: Firmware version 0.29.29.5 (da87cccd), cmd version 0, type 5 │
│May 14 10:20:28 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: Firmware version 0.29.29.5 (da87cccd), cmd version 0, type 3 │
│May 14 10:20:28 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: chip rfe_type is 1 │
│May 14 10:20:28 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0 wlp2s0: renamed from wlan0 │
│May 14 10:22:42 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: failed to pre-release fwcmd │
│May 14 10:22:42 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: timed out to flush pci txch: 0 │
│May 14 10:22:42 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: timed out to flush pci txch: 1 │
│May 14 10:22:42 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: timed out to flush pci txch: 2 │
│May 14 10:22:42 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: timed out to flush pci txch: 3 │
│May 14 10:22:42 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: timed out to flush pci txch: 8 │
│May 14 10:22:42 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: timed out to flush pci txch: 9 │
│May 14 10:22:43 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: FW does not process h2c registers │
│May 14 10:22:43 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: FW does not process h2c registers │
│May 14 10:22:43 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: timed out to flush pci txch: 0 │
│May 14 10:22:43 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: timed out to flush pci txch: 1 │
│May 14 10:22:43 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: timed out to flush pci txch: 2 │
│May 14 10:22:43 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: timed out to flush pci txch: 3 │
│May 14 10:22:43 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: timed out to flush pci txch: 8 │
│May 14 10:22:43 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: timed out to flush pci txch: 9 │
│May 14 10:22:43 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: failed to pre-release fwcmd │
│May 14 10:22:43 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: Update probe request failed │
│May 14 10:22:43 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: FW does not process h2c registers │
│May 14 10:22:43 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: FW does not process h2c registers │
│May 14 10:22:43 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: HW scan failed with status: -110 │
│May 14 10:22:44 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: Update probe request failed │
│May 14 10:22:45 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: FW does not process h2c registers │
│May 14 10:22:45 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: FW does not process h2c registers │
│May 14 10:22:45 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: HW scan failed with status: -110 │
│May 14 10:22:46 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: Update probe request failed
...
│May 14 10:22:56 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: HW scan failed with status: -110 │
│May 14 10:22:57 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: Update probe request failed │
│May 14 10:22:57 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: FW does not process h2c registers │
│May 14 10:22:57 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: FW does not process h2c registers │
│May 14 10:22:57 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: HW scan failed with status: -110 │
│May 14 10:22:58 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 10:22:59 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 10:22:59 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 10:22:59 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 10:22:59 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 10:23:00 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 10:23:00 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 10:23:00 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 10:23:00 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 10:23:01 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110
While with the older kernel and firmware version I get the errors
┌May 14 11:11:21 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 11:14:05 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: Direct firmware load for rtw89/rtw8852b_fw.bin failed with error -2 │
│May 14 11:14:05 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: failed to early request firmware: -2 │
│May 14 11:14:05 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: enabling device (0000 -> 0003) │
│May 14 11:14:05 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: Firmware version 0.27.32.1, cmd version 0, type 1 │
│May 14 11:14:05 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: Firmware version 0.27.32.1, cmd version 0, type 3 │
│May 14 11:14:05 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: MAC has already powered on │
│May 14 11:14:05 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: chip rfe_type is 1 │
│May 14 11:14:05 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0 wlp2s0: renamed from wlan0 │
│May 14 11:14:07 vagrant.whitetree NetworkManager[5099]: <info> [1715656447.3977] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/ieee80211/phy0/rfkill1) (driver rtw89_8852be) │
│May 14 11:15:23 vagrant.whitetree NetworkManager[9615]: <info> [1715656523.5805] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/ieee80211/phy0/rfkill1) (driver rtw89_8852be) │
│May 14 11:15:36 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: failed to pre-release fwcmd │
│May 14 11:15:36 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 11:15:36 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 11:15:37 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 11:15:37 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 11:15:37 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 11:15:38 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 11:15:38 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 11:15:38 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 11:15:38 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 11:15:39 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 11:15:39 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110 │
│May 14 11:15:39 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110
Any idea what could go wrong here? I have tried disabling via all before-mentioned methods and the network card crashes on both older
and newer kernels despite all my efforts.
On 5/13/24 11:34 AM, Plamen Dimitrov wrote:
> Hi,
>
> On 4/30/24 11:36 AM, Ping-Ke Shih wrote:
>> Plamen Dimitrov <plamen.dimitrov@pevogam.com> wrote:
>>>
>>> On 4/25/24 13:41, Ping-Ke Shih wrote:
>>>> sudo iw wlan0 get power_save
>>>
>>> [pevogam@vagrant ~]$ sudo iw wlp2s0 set power_save off
>>> [pevogam@vagrant ~]$ sudo iw wlp2s0 get power_save
>>> Power save: off
>>>
>>> Then it still failed and I have attached a grepped syslog to this email.
>>>
>>
>> The log said hardware has gotten abnormal, and you cannot recover the state
>> even you set power_save to off.
>>
>> I suggest you disable power_save via network manager conf file again, and
>> check power_save state via 'iw' command right after booting.
>>
>> Another try is to disable WiFi when you turn off your computer, because WiFi
>> will not enable immediately right after booting.
>>
>
> I have set this:
>
> ```
> $ cat /etc/NetworkManager/conf.d/wifi-powersave-off.conf
> # File to be place under /etc/NetworkManager/conf.d
> [connection]
> # Values are 0 (use default), 1 (ignore/don't touch), 2 (disable) or 3 (enable).
> wifi.powersave = 2
> ```
>
> then also did `sudo iw wlp2s0 set power_save off` and turned off my wifi entirely
> before rebooting. After reboot (and with wifi still completely off), I checked the
> "sudo iw wlp2s0 set power_save off" and unfortunately it was
>
> ```
> $ sudo iw wlp2s0 get power_save
> Power save: on
> ```
>
> I then disabled it manually again `sudo iw wlp2s0 set power_save off` and finally
> enabled the wifi. After a few minutes the error happened again and all wifi crashed.
>
> I am attaching the new log here but some highlights of what I see are:
>
> ```
> │May 13 10:52:45 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: failed to pre-release fwcmd
> │May 13 10:52:45 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
> │May 13 10:52:45 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
> │May 13 10:52:45 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110
> │May 13 10:52:45 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: failed to leave idle state
> ```
>
> It seems that the problem is different with this "failed to pre-release fwcmd" but I am not really sure.
>
--
Kind regards,
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-05-14 3:27 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
[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 [this message]
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=23d3e142-125a-4b3f-99f6-1f85d47541f7@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.