#Wifi gets disconnected

50 messages · Page 1 of 1 (latest)

halcyon timber
#

In my LMDE 7 in asus laptop when it goes to sleep/suspend and when it wakes up the wifi becomes unavailable and systemctl restart NetworkManager doesn't work here. I have to reboot again to get it back.

What is the solution for this?
I have wifi card - rtw89_8852be

quick storm
#

Please show output of

inxi -Snxxxz

halcyon timber
quick storm
#

Ok, and what do you mean by "systemctl restart NetworkManager doesn't work here"?

halcyon timber
#

like after running the command the Wifi doesn't get enabled

#

basically nothing happens

quick storm
#

After suspend, does the wifi button disappears or it says connected when it's not, or something else?

halcyon timber
#

it shows wifi unavailable
and the wifi disconnected icon displays on panel

quick storm
#

See if

sudo modprobe -r rtw89_8852be
sudo modprobe rtw89_8852be

gets it back after suspend

halcyon timber
#

i have tried this before and it freezes the system and have to force reboot

quick storm
#

After the first or the second command?

halcyon timber
#

first command

quick storm
#

Have you tried pcie_aspm=off kernel parameter?

wary breach
#

some drivers suck at it

#

you can apply it temporarily with the iw utility

#

sudo apt install iw && sudo iw dev wlp1s0 set power_save off

#

then try suspending/resuming

halcyon timber
#

but right now if it is unavailable (after waking from suspend) then how to get it back?

halcyon timber
quick storm
halcyon timber
#

yes I did but did not work

faint spoke
quick storm
wary breach
#

and show the last few lines of dmesg after resuming from sleep

halcyon timber
# wary breach and show the last few lines of `dmesg` _after_ resuming from sleep

[ 1426.694908] rtw89_8852be 0000:01:00.0: xtal si not ready(W): offset=90 val=10 mask=10 [ 1426.715886] rtw89_8852be 0000:01:00.0: mac init fail, ret:-110 [ 1426.787120] rtw89_8852be 0000:01:00.0: xtal si not ready(W): offset=90 val=10 mask=10 [ 1426.807317] rtw89_8852be 0000:01:00.0: mac init fail, ret:-110 [ 1436.696064] rtw89_8852be 0000:01:00.0: xtal si not ready(W): offset=90 val=10 mask=10 [ 1436.716782] rtw89_8852be 0000:01:00.0: mac init fail, ret:-110 [ 1436.787745] rtw89_8852be 0000:01:00.0: xtal si not ready(W): offset=90 val=10 mask=10 [ 1436.808722] rtw89_8852be 0000:01:00.0: mac init fail, ret:-110

wary breach
#

-110? Seems to point to 'connection timed out'

halcyon timber
#

maybe?

#

sorry, I don't know much about this

wary breach
#

what about dmesg | grep rtw89_8852be?

quick storm
#

So the adapter can't wake up properly, if turning off wifi powersaving isn't enough, try pcie_aspm=off kernel parameter

halcyon timber
# wary breach what about `dmesg | grep rtw89_8852be`?

[ 33.489964] rtw89_8852be 0000:01:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin [ 33.490085] rtw89_8852be 0000:01:00.0: enabling device (0000 -> 0003) [ 33.495524] rtw89_8852be 0000:01:00.0: Firmware version 0.29.29.8 (39dbf50f), cmd version 0, type 5 [ 33.495527] rtw89_8852be 0000:01:00.0: Firmware version 0.29.29.8 (39dbf50f), cmd version 0, type 3 [ 33.807326] rtw89_8852be 0000:01:00.0: chip rfe_type is 1 [ 33.836688] rtw89_8852be 0000:01:00.0: rfkill hardware state changed to enable [ 33.859136] rtw89_8852be 0000:01:00.0 wlp1s0: renamed from wlan0 [ 1028.022353] rtw89_8852be 0000:01:00.0: failed to write DBI register, addr=0xB48 [ 1028.022570] rtw89_8852be 0000:01:00.0: failed to write DBI register, addr=0xB48 [ 1028.022780] rtw89_8852be 0000:01:00.0: failed to read DBI register, addr=0x719 [ 1028.022781] rtw89_8852be 0000:01:00.0: failed to read PCI cap, ret=134 [ 1028.468093] rtw89_8852be 0000:01:00.0: xtal si not ready(W): offset=90 val=10 mask=10 [ 1028.488425] rtw89_8852be 0000:01:00.0: mac init fail, ret:-110

wary breach
quick storm
#

I think mint 22.3 now offers system administration is the settings, so you can add it there

wary breach
#

is it in LMDE?

quick storm
#

Don't know, but easy enough to check at the bottom of the settings

halcyon timber
quick storm
halcyon timber
#

yes did all that and after that I am saying that it's not working

#

should I update the kernel via backports?

#

what should be careful about before doing that and after effect of doing this?

wary breach
#

can you? you're already on the latest debian kernel

halcyon timber
#

their backport site says kernel 6.18 while I am in 6.12

wary breach
#

debian 14?

#

well you can try i guess

#

there's little risk in upgrading the kernel

#

you can always grub load the previous image and delete the new kernel packages

halcyon timber
#

well with newer kernel 6.19 it still gives the exact problem

halcyon timber
#

well I got back original firmware and kernel