Father, Hacker (Information Security Professional), Open Source Software Developer, Inventor, and 3D printing enthusiast

  • 0 Posts
  • 12 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2023

help-circle
  • The same thing can happen in Windows. Only difference, really, is that Linux tells you that there’s a problem and the Event Viewer doesn’t. You just end up with a hung Windows PC or a screwed up USB port that won’t work anymore after it happens enough times.

    Oftentimes what causes it is undocumented firmware “features” that need to be turned on via a proprietary driver (for your USB device). The vendor “supports” Windows but not Linux so they never bothered to submit any patches to fix issues like that. It’s that Linux fault? Not really. It’s the fault of the shitty vendor.

    It’s always some bargain basement piece of shit Chinese-made USB device that causes these sorts of problems. The type of thing that can happen when even the vendor of the product didn’t know a counterfeit chip ended up in their device.





  • I had this same thing happen a while back. You know what it was? A bad USB device!

    I had a little USB debug probe that went bad (somehow) and it totally screwed up my USB hub’s ability to… Stay stable? Haha, that’s the best way to put it.

    Anyway, the fix was to remove the device and disconnect the USB hub (and its power) for a few seconds. If I ever reconnected the probe, the problem would recur within an hour or two.

    Here’s how you can check for something similar: Run dmesg and look for regular messages like, “unable to enumerate device”. It’ll tell you which bus and port it’s on but that’s not easy to figure out so just keep unplugging things until you get the one matching the device that’s regularly throwing errors in dmesg. Keep it disconnected, power everything off (PC, USB hub’s, etc) for a few seconds and then try running without that device for a while. It might be the culprit!