Hi all,
I had some problems with RTL8852BE and tried a commonly suggested fix
$ sudo cat /etc/modprobe.d/20-wifi.conf
options rtw89_pci disable_aspm_l1ss=y disable_aspm_l1=y disable_clkreq=y
options rtw89_core disable_ps_mode=y
as
$ lsmod | grep rtw
rtw89_8852be 12288 0
rtw89_8852b 364544 1 rtw89_8852be
rtw89_pci 81920 1 rtw89_8852be
rtw89_core 577536 2 rtw89_8852b,rtw89_pci
mac80211 1568768 2 rtw89_core,rtw89_pci
cfg80211 1335296 3 rtw89_8852b,rtw89_core,mac80211
but this doesn't fix my issue which looks like
[ 1794.542266] rtw89_8852be 0000:02:00.0: FW does not process h2c registers
[ 1794.542269] rtw89_8852be 0000:02:00.0: HW scan failed with status: -110
[ 1794.935328] rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
[ 1795.006323] rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
[ 1795.006330] rtw89_8852be 0000:02:00.0: mac init fail, ret:-110
I verified that the changes take effect via
$ sudo modprobe -r rtw89_8852be
$ sudo modprobe -r rtw89_core
$ sudo modprobe -v rtw89_8852be
which produces
insmod /lib/modules/6.7.4-100.fc38.x86_64/kernel/net/mac80211/mac80211.ko.xz
insmod /lib/modules/6.7.4-100.fc38.x86_64/kernel/drivers/net/wireless/realtek/rtw89/rtw89_core.ko.xz disable_ps_mode=y
insmod /lib/modules/6.7.4-100.fc38.x86_64/kernel/drivers/net/wireless/realtek/rtw89/rtw89_pci.ko.xz disable_aspm_l1ss=y disable_aspm_l1=y disable_clkreq=y
insmod /lib/modules/6.7.4-100.fc38.x86_64/kernel/drivers/net/wireless/realtek/rtw89/rtw89_8852b.ko.xz
insmod /lib/modules/6.7.4-100.fc38.x86_64/kernel/drivers/net/wireless/realtek/rtw89/rtw89_8852be.ko.xz
However, the `xtal is not ready` still appears after reloading and the device is likely in a bad state once the error is already encountered:
[12876.478139] rtw89_8852be 0000:02:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin
[12876.478249] rtw89_8852be 0000:02:00.0: Unable to change power state from D3cold to D0, device inaccessible
[12876.529327] rtw89_8852be 0000:02:00.0: xtal si not ready(R): offset=41
[12876.529336] rtw89_8852be 0000:02:00.0: no suitable firmware found
[12876.529339] rtw89_8852be 0000:02:00.0: failed to recognize firmware
[12876.529342] rtw89_8852be 0000:02:00.0: failed to setup chip information
[12876.530074] rtw89_8852be: probe of 0000:02:00.0 failed with error -2
Does anyone know what is going on here?
Regards,
Plamen Dimitrov
Plamen Dimitrov <[email protected]> wrote:
> Hi all,
>
> I had some problems with RTL8852BE and tried a commonly suggested fix
>
> $ sudo cat /etc/modprobe.d/20-wifi.conf
> options rtw89_pci disable_aspm_l1ss=y disable_aspm_l1=y disable_clkreq=y
> options rtw89_core disable_ps_mode=y
>
> as
>
> $ lsmod | grep rtw
> rtw89_8852be 12288 0
> rtw89_8852b 364544 1 rtw89_8852be
> rtw89_pci 81920 1 rtw89_8852be
> rtw89_core 577536 2 rtw89_8852b,rtw89_pci
> mac80211 1568768 2 rtw89_core,rtw89_pci
> cfg80211 1335296 3 rtw89_8852b,rtw89_core,mac80211
>
> but this doesn't fix my issue which looks like
>
> [ 1794.542266] rtw89_8852be 0000:02:00.0: FW does not process h2c registers
> [ 1794.542269] rtw89_8852be 0000:02:00.0: HW scan failed with status: -110
> [ 1794.935328] rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
> [ 1795.006323] rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
> [ 1795.006330] rtw89_8852be 0000:02:00.0: mac init fail, ret:-110
These logs said that it can download firmware successfully, but timed out to
ask firmware to do scan. I would try module parameters like you did, but
please do "cold reboot" to take effect the parameters, because hardware
has been gotten into abnormal state.
> However, the `xtal is not ready` still appears after reloading and the device is likely in a bad state once
> the error is already encountered:
>
> [12876.478139] rtw89_8852be 0000:02:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin
> [12876.478249] rtw89_8852be 0000:02:00.0: Unable to change power state from D3cold to D0, device
> inaccessible
> [12876.529327] rtw89_8852be 0000:02:00.0: xtal si not ready(R): offset=41
This is second IO driver does to read hardware revision, but inaccessible.
You should reboot to recover hardware state.
> [12876.529336] rtw89_8852be 0000:02:00.0: no suitable firmware found
> [12876.529339] rtw89_8852be 0000:02:00.0: failed to recognize firmware
> [12876.529342] rtw89_8852be 0000:02:00.0: failed to setup chip information
> [12876.530074] rtw89_8852be: probe of 0000:02:00.0 failed with error -2
Hi again,
On 4/16/24 08:31, Ping-Ke Shih wrote:
>>
>> [ 1794.542266] rtw89_8852be 0000:02:00.0: FW does not process h2c registers
>> [ 1794.542269] rtw89_8852be 0000:02:00.0: HW scan failed with status: -110
>> [ 1794.935328] rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
>> [ 1795.006323] rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
>> [ 1795.006330] rtw89_8852be 0000:02:00.0: mac init fail, ret:-110
>
> These logs said that it can download firmware successfully, but timed out to
> ask firmware to do scan. I would try module parameters like you did, but
> please do "cold reboot" to take effect the parameters, because hardware
> has been gotten into abnormal state.
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
```
Apr 16 10:14:22 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: read rf busy swsi
Apr 16 10:14:22 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: write rf busy swsi
Apr 16 10:14:22 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: write rf busy swsi
Apr 16 10:14:22 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: write rf busy swsi
Apr 16 10:14:22 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: write rf busy swsi
Apr 16 10:14:22 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: read rf busy swsi
Apr 16 10:14:22 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: write rf busy swsi
Apr 16 10:14:22 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: FW does not process h2c registers
Apr 16 10:14:22 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: HW scan failed with status: -110
...
Apr 16 10:14:23 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
Apr 16 10:14:23 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
Apr 16 10:14:23 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110
Apr 16 10:14:23 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
Apr 16 10:14:23 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
Apr 16 10:14:23 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110
Apr 16 10:14:23 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
Apr 16 10:14:23 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
Apr 16 10:14:23 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110
Apr 16 10:14:23 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
Apr 16 10:14:23 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
Apr 16 10:14:23 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110
Apr 16 10:14:24 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
Apr 16 10:14:24 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
Apr 16 10:14:24 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110
Apr 16 10:14:24 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
Apr 16 10:14:24 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: xtal si not ready(W): offset=90 val=10 mask=10
Apr 16 10:14:24 vagrant.whitetree kernel: rtw89_8852be 0000:02:00.0: mac init fail, ret:-110
```
This reconfirmed my previous conclusion that the settings did not help. Perhaps there is some other useful info
I could provide and should investigate?
Regards,
Plamen Dimitrov
Plamen Dimitrov <[email protected]> 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?
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
On 4/16/24 10:31, Ping-Ke Shih wrote:
> Plamen Dimitrov<[email protected]> 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
Plamen Dimitrov <[email protected]> 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
On 4/23/24 10:49, Ping-Ke Shih wrote:
> Plamen Dimitrov<[email protected]> 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?
--
Best,
Plamen Dimitrov
Plamen Dimitrov <[email protected]> wrote:
> On 4/23/24 10:49, Ping-Ke Shih wrote:
> > Plamen Dimitrov<[email protected]> 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.
Hi,
On 4/30/24 11:36 AM, Ping-Ke Shih wrote:
> Plamen Dimitrov <[email protected]> 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.
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 <[email protected]> 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
Plamen Dimitrov <[email protected]> wrote:
> 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
> │
>
> 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.
What is the kernel version of the newest Fedora? I can try it in my side.
It looks like firmware enters abnormal state, so my suggestion is to disable
all power save functions to clarify the problems, but it seems like you
have done all of them.
Is it possible to remove modules from /lib/modules/ ? Then insmod manually
with module parameters to disable power save functions one-by-one?
Ping-Ke
Ping-Ke Shih <[email protected]> writes:
> Plamen Dimitrov <[email protected]> wrote:
>
>> 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
>> │
>>
>> 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.
>
> What is the kernel version of the newest Fedora? I can try it in my side.
>
> It looks like firmware enters abnormal state, so my suggestion is to disable
> all power save functions to clarify the problems, but it seems like you
> have done all of them.
>
> Is it possible to remove modules from /lib/modules/ ? Then insmod manually
> with module parameters to disable power save functions one-by-one?
BTW it should be also possible to blacklist modules to avoid them being
loaded automatically. At least in Debian I do this:
$ cat /etc/modprobe.d/kvalo.conf
blacklist ath11k_pci
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
On 5/15/24 11:47 AM, Ping-Ke Shih wrote:
>> 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.
> What is the kernel version of the newest Fedora? I can try it in my side.
6.8.9-300.fc40.x86_64
> It looks like firmware enters abnormal state, so my suggestion is to disable
> all power save functions to clarify the problems, but it seems like you
> have done all of them.
>
> Is it possible to remove modules from/lib/modules/ ? Then insmod manually
> with module parameters to disable power save functions one-by-one?
Not sure, which modules in particular are you referring to so I can isolate this further:
$ ll /lib/modules/$(uname -r)/kernel/net
total 200
drwxr-xr-x. 2 root root 4096 May 13 15:05 6lowpan
drwxr-xr-x. 2 root root 4096 May 13 15:05 802
drwxr-xr-x. 2 root root 4096 May 13 15:05 8021q
drwxr-xr-x. 2 root root 4096 May 13 15:05 9p
drwxr-xr-x. 2 root root 4096 May 13 15:07 appletalk
drwxr-xr-x. 2 root root 4096 May 13 15:07 atm
drwxr-xr-x. 2 root root 4096 May 13 15:07 ax25
drwxr-xr-x. 2 root root 4096 May 13 15:07 batman-adv
drwxr-xr-x. 5 root root 4096 May 13 15:05 bluetooth
drwxr-xr-x. 3 root root 4096 May 13 15:05 bridge
drwxr-xr-x. 3 root root 4096 May 13 15:05 can
drwxr-xr-x. 2 root root 4096 May 13 15:05 ceph
drwxr-xr-x. 2 root root 4096 May 13 15:05 core
drwxr-xr-x. 2 root root 4096 May 13 15:05 dns_resolver
drwxr-xr-x. 2 root root 4096 May 13 15:05 dsa
drwxr-xr-x. 2 root root 4096 May 2 08:00 handshake
drwxr-xr-x. 2 root root 4096 May 13 15:05 hsr
drwxr-xr-x. 3 root root 4096 May 13 15:05 ieee802154
drwxr-xr-x. 2 root root 4096 May 13 15:05 ife
drwxr-xr-x. 3 root root 4096 May 13 15:07 ipv4
drwxr-xr-x. 4 root root 4096 May 13 15:05 ipv6
drwxr-xr-x. 2 root root 4096 May 13 15:05 kcm
drwxr-xr-x. 2 root root 4096 May 13 15:05 key
drwxr-xr-x. 2 root root 4096 May 13 15:07 l2tp
drwxr-xr-x. 2 root root 4096 May 13 15:05 llc
drwxr-xr-x. 3 root root 4096 May 13 15:05 mac80211
drwxr-xr-x. 2 root root 4096 May 13 15:05 mac802154
drwxr-xr-x. 2 root root 4096 May 13 15:05 mpls
drwxr-xr-x. 2 root root 4096 May 2 08:00 mptcp
drwxr-xr-x. 4 root root 4096 May 13 15:05 netfilter
drwxr-xr-x. 2 root root 4096 May 13 15:07 netrom
drwxr-xr-x. 4 root root 4096 May 13 15:05 nfc
drwxr-xr-x. 2 root root 4096 May 13 15:05 nsh
drwxr-xr-x. 2 root root 4096 May 13 15:05 openvswitch
drwxr-xr-x. 2 root root 4096 May 13 15:05 psample
drwxr-xr-x. 2 root root 4096 May 13 15:05 qrtr
drwxr-xr-x. 2 root root 4096 May 13 15:07 rds
drwxr-xr-x. 2 root root 4096 May 13 15:05 rfkill
drwxr-xr-x. 2 root root 4096 May 13 15:07 rose
drwxr-xr-x. 2 root root 4096 May 13 15:05 rxrpc
drwxr-xr-x. 2 root root 4096 May 13 15:07 sched
drwxr-xr-x. 2 root root 4096 May 13 15:05 sctp
drwxr-xr-x. 2 root root 4096 May 13 15:05 smc
drwxr-xr-x. 4 root root 4096 May 13 15:05 sunrpc
drwxr-xr-x. 2 root root 4096 May 13 15:05 tipc
drwxr-xr-x. 2 root root 4096 May 13 15:05 tls
drwxr-xr-x. 2 root root 4096 May 13 15:05 vmw_vsock
drwxr-xr-x. 3 root root 4096 May 13 15:05 wireless
drwxr-xr-x. 2 root root 4096 May 13 15:05 xdp
drwxr-xr-x. 2 root root 4096 May 13 15:05 xfrm
On 5/15/24 1:40 PM, Kalle Valo wrote:
>> Is it possible to remove modules from/lib/modules/ ? Then insmod manually
>> with module parameters to disable power save functions one-by-one?
> BTW it should be also possible to blacklist modules to avoid them being
> loaded automatically. At least in Debian I do this:
>
> $ cat /etc/modprobe.d/kvalo.conf
> blacklist ath11k_pci
Indeed, I guess maybe one way to remove modules on reboot, thanks for the hints!
Regards,
Plamen