Internet dies, then plasma freezes for around 15 seconds.
Sometimes my internet will just stop working. When my system is in this state, enabling or disabling internet will freeze plasma for around 15 seconds. I will also be unable to power off or reboot my system without removing power from it or holding the power button down, as it will hang on the black loading screen.
This log starts at where the internet died and goes through where this video takes place to where i pressed the "restart" button and then the system hanged and i held the power button down.
https://paste.centos.org/view/64bcb502
28 Replies
This has been an on-and-off issue for around 6 months for me but it is inconsistent and I can't find a way to reproduce it on-command
When my mouse is moving in that video is me spamming right-click and dragging on the desktop
Interestingly, once the system seems to recognize that internet is dead and switches to the "no availavilable connections", plasma only freezes when enabling internet
instead of enabling or disabling it
the journalctl log would need to be from boot
and what wifi chipset are you using?
0d:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
ah
mediatek
try the full log
maybe we can find a feature that is causing it
but the real reason is that the wifi drivers suck
ideally you want intel
realtek is getting better but still isn't perfect
From journalctl
From the start of the boot
that is 14 hours and full of irrelevancies
but sure
https://paste.centos.org/view/153e732e
ignore the pipewire error spam
that is not related
and this
WARNING: discarding _NET_WM_PID 3 as invalid for X11 window - use specialized XCB_X11_TO_PID function!Jul 23 04:02:35 kernel: mt7921e 0000:0d:00.0: Timeout for driver own
Boom is was cutting a line
Yep that looks like bad drivers
Is the WiFi card removable on your motherboard?
uh
probably not
wait
maybe?
but would be hard-ish to get to
one image of the motherboard does have "M.2(wifi)" listed on it
and i don't think the top left area is really meant to be removeds
but that's where it would be
Your other option is creating a bug report, I would probably start with the bazzite GitHub, so you can have someone actually responsible for the distro, maybe there is a way to solve it
Ot a PCI-E wi-fi card if you don't want to dig through your motherboard
You'll be looking for an intel ax210 chipset
i've considered it but the issue seems to come in groups then disappear for a while
and also only really happen if the system's been on for a long time
Yeah, that's probably why the bug hasn't been fixed
I would post an issue with the full journalctl log linked
(and maybe specify the fact that it starts towards the end lol)
i'd rather one without the steam spam and pipewire spam
tbh
If you're willing to try go for it
Bit save the current one to a file
could try just turning my computer on during the weekend and letting it sit for 10 hours and see if it happens
It's interesting that it only pops up after so long
Mediatek drivers even suck on windows so what do you expect I suppose
idk maybe something is accumulating then just causes a catastrophic failure
could be a hardware fault
Next time you buy a motherboard, either just rely on a pcie card, or find one with WiFi you feel comfortable changing to intel
They generally ship you ewaste
this wasn't my first choice
Probably not
this was a "my first choice is broken and doesn't work and i need a computer functioning tomorrow"
I had a relatively similar issue on a realtek chip
It was 100% drivers, they're rolling out a fix in 6.16 or 6.17
it does show that it tries to reset the chip
Jul 23 03:51:59 kernel: mt7921e 0000:0d:00.0: chip reset failed
but failsYeah that looks like catastrophic failure to me
If I even had an ounce of trust in the drivers I would tell you it's hardware
then rfkill comes in eventually
idk what it's doing
But I can practical guarantee the chipset is fine
Well at that point it's just in panic mode
and not sure why it hangs on reboot or power off
seems to unmount home then stop
or whatever it was trying to do didn't make it into the log from being forced off
Turns out this also happens on my arch install with the exact same errors in journalctl
USB Network adapter and try networking on that?