this post was submitted on 15 Sep 2023
16 points (100.0% liked)
techsupport
2497 readers
6 users here now
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This has been happening for 2 years, with the previous debian version too, so I doubt this would do anything?
Have you been updating or reinstalling ?
Parce que si c'est update sur update ça pourrait venir de là. Dans ce cas réinstalle peut etre ?
Updating. I'm willing to try your solution but I am a little bit worried about not being able to reinstall anything after I
sudo apt remove network-manager. Why would a package reinstallation help? Wouldn't resetting the config files be more efficient btw?EDIT: Ce n'est pas update sur update, y a juste eu bullseye (d'abord testing, puis stable), puis récemment je suis passé à bookworm. Mais le soucis est là depuis le début. Il est pas trop chiant parce que c'est rare, mais quand même ça m'enquiquine.
Thing is, I really haven't used debian based distros for the better part of the last two years so I'm not sure how to reinstall it if something goes south. With arch you just have to do a pacstrap with a liveUSB.
So... it seems kinda dangerous if you don't have a backup .deb. I'm not sure I would advise you to go this way.
I looked at your journalctl. The error might come from your wireless card. If that is the case, and since you don't use it at all there is a simple trick :
sudo systemctl disable wpa_supplicantthen reboot.It won't have any incidence on the ethernet but will somewhat disable your wifi card. (Not exactly but you get the gist of it).
If I'm right it should make all of your problems go away. It might be worth a try. And if it doesn't work a simple
sudo systemctl enable wpa_supplicantwill reverse it back to the way it was.Ça demeure chiant, même si c'est pas quotidien.
If its been happening for multiple years and os's, maybe your network card is dead/dying? Buy a new network card and see if that helps?
Everything is 2 yo, so this would mean the mobo (well, the onboard ethernet thing) was malfunctioning from the start. Maybe!
I might try disabling and using the onboard wifi chip temporarily instead, just to see if I notice a new freeze. The issue is, I've never understood what triggers it, and it's quite rare (less than once a week), so it's really annoying to debug…