Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Usually my go-to for "Linux problems" is "tear down the VM and start a new one", but a few days ago my Manjaro rig at home lost power, and bluetooth wouldn't work upon restart. I wracked my brain, pored through forum threads, man pages, and LFS, but nothing really helped. It looked like several different problems at once, but none of the individual fixes worked, or only worked for minutes at a time. I stepped away from the problem for a while, as one does, while I mused about the way troubleshooting works, and how my early life with Windows and now modern containerization has predisposed me to certain types of solu-- wait, I've got it! rmmod the bluetooth modules, modprobe 'em back in. Everything worked flawlessly. I'm not sure what I learned.

*sigh*



>I'm not sure what I learned.

"Have you tried turning it off and on again?"


I've done this enough, but don't stop there as it's likely to happen again. When I resort to such a solution, I take a look at the syslogs. More often than not, something there will tell me why a simple restart of a service, module, whatever was the answer.

I had a similar problem as the article with a standard USB 3 enclosure. Two PCs, identical OS (oS Tumbleweed), same kernel version even. modprobe -r then modprobe usbstorage and it worked. An obscure error in the logs pointed to the uas module which for some reason failed to reload, enabling the enclosure to work.

Oddly, the other PC on which it worked was loading uas.


Exactly. My tendency is to jump in and try to root cause problems but nowadays the most productive solution is almost always some kind of a restart.


I always refer to this as Computer Science 101.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: