rtw88_8821c Unhandled Firmware Interrupts

[JusGellin]

On one of my laptops (HP Pavillion x360 convertible 11m-ap0xxx) it seems that no matter which distro I use
(I've tried BookwormPup64_10.0.6 through 10.0.9, BookwormPup64_10.0.9_nkbv2, KLV-vmHost-rc4, Alpine Linux )
I get annoying continuous errors in dmesg like:
[Tue Jan 21 14:03:40 2025] rtw_8821ce 0000:02:00.0: unhandled firmware c2h interrupt
occurring every 1 to 15 seconds.

It seems that everything is working properly including wifi.

Is there something that can be done to resolve these these errors from cluttering up dmesg, or just preventing them from occurring in dmesg?

My other laptops don't have this problem, but they are using different wifi drivers.

Thanks

[Trapster]

It seems that message is from the different levels of kernel logging

Try this.
Create a file /etc/sysctl.d/local.conf

inside /etc/sysctl.d/local.conf write:
kernel.printk=1

Reboot and see if it works.

[JusGellin]

I made the file /etc/sysctl.d/local.conf with kernel.printk=1
using BookwormPup64_10.0.9.

It still shows the unhandled interrupt errors.

Thanks

[ozsouth]

@JusGellin - rtw-8821ce has caused me issues in the past (hanging the pc that had that wifi adaptor), so much so that I made my 6.6 & 6.1 kernels with it disabled (have 'nr' in kernel name), & instead made an out-of-tree driver pet.

[JusGellin]

@JusGellin - rtw-8821ce has caused me issues in the past (hanging the pc that had that wifi adaptor), so much so that I made my 6.6 & 6.1 kernels with it disabled (have 'nr' in kernel name), & instead made an out-of-tree driver pet. 6.6.67 (usrmerge option) should work.

I would need specific direction to try this. But I would like to try to do it.
Can you show me how even to the trying the different kernels?

Also, I saw a place on the internet to check if wifi power management is available.
I used iwconfig to see that it is and it is on.
Then it suggested shutting just that off.
How could I shut the wifi power management off?

Thanks

[ozsouth]

@JusGellin - turning power management off is easy in a terminal. At own risk:

1. run: iwconfig (this will tell you what interface is active, i.e. wlan0)

2. (assuming wlan0) run: iwconfig wlan0 power off

See if that fixes it first.

[JusGellin]

@JusGellin - turning power management off is easy in a terminal. At own risk:

1. run: iwconfig (this will tell you what interface is active, i.e. wlan0)

2. (assuming wlan0) run: iwconfig wlan0 power off

See if that fixes it first.

Setting wlan0 to power off looks like it did the trick.
It's run over an hour with no dmesg entries at all. Before it gave the error messages almost right away.

I'll run it for a few more hours to make sure.

Now how can I make this permanent? I notice it loses the setting on a reboot.

Thanks

[JusGellin]

It worked ok overnight.

I saw that I should be able to commit the change:
iwconfig wlan0 commit

But it gives error:

Code: Select all

Error for wireless request "Commit changes" (8000) :
SET failed on device wlan0 ; Operation not supported.

If I reboot, it looses the change and right away gives the unhandled firmware interrupts again

[ozsouth]

@JusGellin - if you have a savefile/folder, you can put an executable script in /root/Startup , which will run every time X starts.
I'd call it zwlanoffpower , containing something like this:

Code: Select all

#!/bin/sh
sleep 3
iwconfig wlan0 power off

Once it is in /root/Startup , in a terminal, to make it executable, run:
chmod 755 /root/Startup/zwlanoffpower

The reason it starts with z is so it runs last (or near last), before X starts.

[JusGellin]

@ozsouth
That works great

Thanks for your help

[JusGellin]

@JusGellin - if you have a savefile/folder, you can put an executable script in /root/Startup , which will run every time X starts.
I'd call it zwlanoffpower , containing something like this:

Code: Select all

#!/bin/sh
sleep 3
iwconfig wlan0 power off

Once it is in /root/Startup , in a terminal, to make it executable, run:
chmod 755 /root/Startup/zwlanoffpower

The reason it starts with z is so it runs last (or near last), before X starts.

So this works with BookwormPup64.

How can I fix KLV-vmHost which is doing the same thing but it doesn't use iwconfig for shutting the wlan0 power management off?

Thanks

[JusGellin]

I found how to do the same thing for KLV-vmHost.
It uses a different command for the wifi called iw.

I had to install iw
1. Update
xbps-install -S iw
2. Install iw
xbps-install iw
3. Make new file:
/root/Startup/zwlandoffpower
4. For zwlandoffpower:
#!/bin/sh
sleep 3
iw dev wlo1 set power_save off
5. Make executable
chmod 755 /root/Startup/zwlanoffpower
6. Reboot should see this prevent the errors. (Use dmesg to see if these errors show up continuously)