#Wifi breaks when waking from sleep

125 messages · Page 1 of 1 (latest)

cursive vessel
#

today my wifi started breaking when i exit from sleep.
if i ping a url it will error with "network is unreachable", then if i either restart my router or make mint forget the network and reconnect everything starts working again.
i know the problem isn't my router because mint is the only place where this happens.

#

wifi power saving is 2, so that shouldn't be a problem

sullen iris
#

what wireless chip is it

cursive vessel
#

don't know exactly what to look for so here's the output of lspci, which the internet tells me is how you'd find out chipset info

nicknonya@LinuxMintPC:~$ lspci
00:00.0 Host bridge: Intel Corporation Device a740 (rev 01)
00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog and Telemetry (rev 01)
00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation
00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 Gb/s) XHCI Host Controller (rev 11)
00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi (rev 11)
00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C Host Controller #0 (rev 11)
00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C Host Controller #1 (rev 11)
00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C Host Controller #2 (rev 11)
00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 (rev 11)
00:17.0 SATA controller: Intel Corporation Raptor Lake SATA AHCI Controller (rev 11)
00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 (rev 11)
00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 (rev 11)
#
00:1c.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #1 (rev 11)
00:1c.3 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #4 (rev 11)
00:1c.4 PCI bridge: Intel Corporation Device 7a3c (rev 11)
00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Raptor Lake LPC/eSPI Controller (rev 11)
00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio Controller (rev 11)
00:1f.4 SMBus: Intel Corporation Raptor Lake-S PCH SMBus Controller (rev 11)
00:1f.5 Serial bus controller: Intel Corporation Raptor Lake SPI (flash) Controller (rev 11)
01:00.0 VGA compatible controller: NVIDIA Corporation AD106 [GeForce RTX 4060 Ti] (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 22bd (rev a1)
04:00.0 Ethernet controller: Aquantia Corp. AQtion AQC113CS NBase-T/IEEE 802.3an Ethernet Controller [Antigua 10G] (rev 03)
05:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 06)
06:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Maple Ridge 4C 2020] (rev 02)
07:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Maple Ridge 4C 2020] (rev 02)
07:01.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Maple Ridge 4C 2020] (rev 02)
07:02.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Maple Ridge 4C 2020] (rev 02)
07:03.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Maple Ridge 4C 2020] (rev 02)
08:00.0 USB controller: Intel Corporation Thunderbolt 4 NHI [Maple Ridge 4C 2020]
3c:00.0 USB controller: Intel Corporation Thunderbolt 4 USB Controller [Maple Ridge 4C 2020]
sullen iris
#

Chipset is from Intel

#

Weird since iwlwifi is a surprisingly decent wireless driver

#

I suspect some ACPI fuckery to be the issue, is this a laptop?

cursive vessel
#

norp

sullen iris
#

Hm

cursive vessel
#

i haven't had this problem before, and it's not like i've updated and then had this. last update i did was weeks ago

sullen iris
#

Provide the last few lines of dmesg after waking from sleep

cursive vessel
# sullen iris Provide the last few lines of `dmesg` after waking from sleep

ok so, i'm currently connected with my phones hotspot, which doesn't have this problem, the result of the command after waking is this:

[ 9423.976661] Bluetooth: hci0: Device revision is 0
[ 9423.976669] Bluetooth: hci0: Secure boot is enabled
[ 9423.976672] Bluetooth: hci0: OTP lock is enabled
[ 9423.976676] Bluetooth: hci0: API lock is enabled
[ 9423.976679] Bluetooth: hci0: Debug lock is disabled
[ 9423.976683] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 9423.976689] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[ 9423.977690] Bluetooth: hci0: DSM reset method type: 0x00
[ 9423.979964] done.
[ 9423.979988] random: crng reseeded on system resumption
[ 9423.980065] PM: suspend exit
[ 9423.982127] Bluetooth: hci0: Found device firmware: intel/ibt-1040-0041.sfi
[ 9423.982139] Bluetooth: hci0: Boot Address: 0x100800
#
[ 9425.295979] Bluetooth: hci0: Waiting for firmware download to complete
[ 9425.296577] Bluetooth: hci0: Firmware loaded in 1283640 usecs
[ 9425.296606] Bluetooth: hci0: Waiting for device to boot
[ 9425.312578] Bluetooth: hci0: Device booted in 15616 usecs
[ 9425.314688] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-1040-0041.ddc
[ 9425.316623] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 9425.319644] Bluetooth: hci0: Firmware timestamp 2023.48 buildtype 1 build 75324
[ 9425.319647] Bluetooth: hci0: Firmware SHA1: 0x23bac558
[ 9425.323575] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[ 9425.323579] Bluetooth: hci0: Fseq status: Success (0x00)
[ 9425.323580] Bluetooth: hci0: Fseq executed: 00.00.02.41
[ 9425.323581] Bluetooth: hci0: Fseq BT Top: 00.00.02.41
[ 9425.323584] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 9425.323616] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[ 9425.323624] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[ 9425.324808] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 5
[ 9425.393687] Bluetooth: MGMT ver 1.23
[ 9428.949483] wlp0s20f3: authenticate with 76:0f:74:21:f8:2e (local address=d4:f3:2d:35:62:18)
[ 9428.950301] wlp0s20f3: send auth to 76:0f:74:21:f8:2e (try 1/3)
[ 9428.993878] wlp0s20f3: authenticated
[ 9428.994562] wlp0s20f3: associate with 76:0f:74:21:f8:2e (try 1/3)
[ 9429.042330] wlp0s20f3: RX AssocResp from 76:0f:74:21:f8:2e (capab=0x1431 status=0 aid=4)
[ 9429.050111] wlp0s20f3: associated
[ 9429.100695] wlp0s20f3: Limiting TX power to 20 (20 - 0) dBm as advertised by 76:0f:74:21:f8:2e
#

imma go and connect to my router and post the command again

sullen iris
#

Bluetooth: hci0: Secure boot is enabled

#

try disabling it

cursive vessel
#
 9429.050111] wlp0s20f3: associated
[ 9429.100695] wlp0s20f3: Limiting TX power to 20 (20 - 0) dBm as advertised by 76:0f:74:21:f8:2e
[ 9594.836892] wlp0s20f3: deauthenticating from 76:0f:74:21:f8:2e by local choice (Reason: 3=DEAUTH_LEAVING)
[ 9611.893606] wlp0s20f3: authenticate with d6:35:1d:71:64:ae (local address=d4:f3:2d:35:62:18)
[ 9611.894408] wlp0s20f3: send auth to d6:35:1d:71:64:ae (try 1/3)
[ 9611.897198] wlp0s20f3: authenticated
[ 9611.899046] wlp0s20f3: associate with d6:35:1d:71:64:ae (try 1/3)
[ 9611.905167] wlp0s20f3: RX AssocResp from d6:35:1d:71:64:ae (capab=0x1411 status=0 aid=23)
[ 9611.908716] wlp0s20f3: associated
[ 9611.959729] wlp0s20f3: Limiting TX power to 20 (20 - 0) dBm as advertised by d6:35:1d:71:64:ae
[ 9612.200904] wlp0s20f3: deauthenticating from d6:35:1d:71:64:ae by local choice (Reason: 3=DEAUTH_LEAVING)
[ 9612.264806] wlp0s20f3: authenticate with d6:35:1d:71:64:ae (local address=d4:f3:2d:35:62:18)
[ 9612.265634] wlp0s20f3: send auth to d6:35:1d:71:64:ae (try 1/3)
[ 9612.268422] wlp0s20f3: authenticated
[ 9612.268959] wlp0s20f3: associate with d6:35:1d:71:64:ae (try 1/3)```
this is when i'm connected to my router. everything is still fine ^
#
[ 9612.275016] wlp0s20f3: RX AssocResp from d6:35:1d:71:64:ae (capab=0x1411 status=0 aid=24)
[ 9612.278393] wlp0s20f3: associated
[ 9612.373159] wlp0s20f3: Limiting TX power to 20 (20 - 0) dBm as advertised by d6:35:1d:71:64:ae
[ 9612.431772] wlp0s20f3: deauthenticating from d6:35:1d:71:64:ae by local choice (Reason: 3=DEAUTH_LEAVING)
[ 9612.461257] wlp0s20f3: authenticate with d6:35:1d:71:64:ae (local address=d4:f3:2d:35:62:18)
[ 9612.462063] wlp0s20f3: send auth to d6:35:1d:71:64:ae (try 1/3)
[ 9612.464856] wlp0s20f3: authenticated
[ 9612.465960] wlp0s20f3: associate with d6:35:1d:71:64:ae (try 1/3)
[ 9612.475448] wlp0s20f3: RX AssocResp from d6:35:1d:71:64:ae (capab=0x1411 status=0 aid=25)
[ 9612.478597] wlp0s20f3: associated
[ 9612.571519] wlp0s20f3: Limiting TX power to 20 (20 - 0) dBm as advertised by d6:35:1d:71:64:ae
[ 9614.512216] wlp0s20f3: disconnect from AP d6:35:1d:71:64:ae for new auth to d6:35:1d:71:64:b6
[ 9614.539945] wlp0s20f3: authenticate with d6:35:1d:71:64:b6 (local address=d4:f3:2d:35:62:18)
[ 9614.540747] wlp0s20f3: send auth to d6:35:1d:71:64:b6 (try 1/3)
[ 9614.581897] wlp0s20f3: authenticated
[ 9614.583044] wlp0s20f3: associate with d6:35:1d:71:64:b6 (try 1/3)
[ 9614.585304] wlp0s20f3: RX ReassocResp from d6:35:1d:71:64:b6 (capab=0x1011 status=0 aid=30)
[ 9614.592373] wlp0s20f3: associated
[ 9614.678983] wlp0s20f3: Limiting TX power to 23 (23 - 0) dBm as advertised by d6:35:1d:71:64:b6
#

this is after i wake when connected to my router, wifi no longer works

#

if you see anything about switching networks thats cos i switched to my hotspot accidentally and then switched back to the broken router connection before running the command

cursive vessel
cursive vessel
cursive vessel
#

which is the only other option in the dropdown

cursive vessel
#

ok i have something

#

ofc discord wittle servers cannot possibly handle this as a message so i'll attach it as a file

sullen iris
#

looks perfectly good

sullen iris
#

6.14 is EOL

cursive vessel
sullen iris
#

what

cursive vessel
#

in the bios dropdown

#

there's only on or "custom"

sullen iris
#

does custom unlock any other options?

cursive vessel
#

not that i can tell

#

in the same section there's also an "os type" which is set to "other os"

#

only other option is windows uefi or something

sullen iris
#

cursed BIOS

#

anyways

#

upgrade the kernel

cursive vessel
#

will do

cursive vessel
sullen iris
#

6.14 is your default image

#

Go to the grub menu (press esc once after you see the manufacturer's logo after POST) and select the 6.17 image in advanced options

#

If it's not a troubling kernel, go to the update manager and delete all 6.14 kernel packages, which will set the default image to the one you're currently running

cursive vessel
#

aight imma try

#

tho it'd be weird if it was the kernel cos this wasn't happening up until a few days ago

sullen iris
#

perhaps your router got a firmware upgrade that breaks some connections?

#

Or you're far from the AP, making it difficult for the wireless chip to connect after resuming from sleep

cursive vessel
cursive vessel
#

how convenient

#

i'll try the new kernel and if that doesn't fix it ig i'll just make do with not putting my pc to sleep for the forseeable future

cursive vessel
sullen iris
#

huh

#

this.. is bad

#

you don't have the standard kernel either

#

huh

#

install it with sudo apt install linux-generic

cursive vessel
#

dunno if it's relevant but my gpu's drivers are weird and the whole os refuses to boot if i use anything other than my current ones

sullen iris
#

nvidia?

cursive vessel
#

yep

sullen iris
#

590?

#

(verison)

cursive vessel
#

580

sullen iris
#

alright

#

so let's install the standard kernel first

cursive vessel
#

uugh

sullen iris
#

you'd ideally always want that to exist

cursive vessel
sullen iris
#

virtualbox goddamnit

#

virtualbox's kernel driver doesn't work with 6.17

#

so your nvidia modules also don't get built

cursive vessel
#

i've been having trouble with virtualbox's updates now that you mention it

sullen iris
#

are you open to remove it?

cursive vessel
#

every time i go to update anything it errors about failing to update virtualbox, the rest of the updates seem to go through

cursive vessel
#

i can just reinstall no?

sullen iris
#

i've learned that virtualbox is not ideal on linux

sullen iris
#

which is the kernel the driver was tested on apparently

cursive vessel
#

that's way older than what i have

#

is virtualbox really that shit

sullen iris
#

mostly

cursive vessel
#

cringe

sullen iris
#

we can look into alternatives that use Linux's native virtualization

cursive vessel
#

i tried out qemu but i know diddly squat about virtualization so i gave up after i needed to run two daemons just for the thing to crash anyways

#

whatever, problem for later

#

wifi is more important

sullen iris
#

so sudo apt purge virtualbox virtualbox-dkms && sudo apt autoremove

cursive vessel
#

oof autoremove scares me

#

i really don't want to get into another situation where i can't boot the os

sullen iris
#

you can omit it

cursive vessel
#

a friend of mine has a similar gpu and every time he runs autoremove it uninstalls his drivers

sullen iris
#

then you can just do the purge

cursive vessel
#

ig i'll try

sullen iris
#

then 6.17 should automatically install

cursive vessel
#

never thought virtualbox could be the cause

sullen iris
#

third party untested drivers ¯_(ツ)_/¯

cursive vessel
#

okaaay so apt list | grep nvidia returns 17223 lines

#

that doesn't seem right

#

how do i determine what i need?

sullen iris
#

does 6.17 install first?

cursive vessel
#

oh i haven't uninstalled vbox yet

sullen iris
cursive vessel
cursive vessel
#

alright everything seems to have worked

#

now to see if the wifi still dies

#

yep! still fucked

sullen iris
#

are you on the newest kernel?

cursive vessel
#

6.17 right?

sullen iris
#

yes

cursive vessel
#

then yes i'm on the new one

#

and vbox is no longer installed

sullen iris
#

hm

cursive vessel
#

the problem appears to have fixed itself.
i am scared

sullen iris
#

i think your AP was at fault then

cursive vessel
#

yeag

#

most likely