search for: uhubctl

...h-linux it seems not possible to programmatically truly power-cycle USB port/hub, as 5V pins are "always on"; and per https://stackoverflow.com/a/16316401/4715872 - at least not on MoBo ports (some hubs may have invested into being fully up to spec and control power fully). The referenced uhubctl <https://github.com/mvp/uhubctl> on my PC said "No compatible devices detected!" so I guess that's it. * Whatever I could find with (suggestions welcome) `grep -r . `find /sys/devices/pci0000\:00 -name '*usb*port*'` /sys/bus/usb/devices/` did not expose any differences...

...possible to programmatically truly power-cycle USB port/hub, > as 5V pins are "always on"; and per > https://stackoverflow.com/a/16316401/4715872 - at least not on MoBo ports > (some hubs may have invested into being fully up to spec and control power > fully). The referenced uhubctl <https://github.com/mvp/uhubctl> on my PC > said "No compatible devices detected!" so I guess that's it. > > * Whatever I could find with (suggestions welcome) `grep -r . `find > /sys/devices/pci0000\:00 -name '*usb*port*'` /sys/bus/usb/devices/` did > no...

...grammatically truly power-cycle USB port/hub, >> as 5V pins are "always on"; and per >> https://stackoverflow.com/a/16316401/4715872 - at least not on MoBo ports >> (some hubs may have invested into being fully up to spec and control power >> fully). The referenced uhubctl <https://github.com/mvp/uhubctl> on my PC >> said "No compatible devices detected!" so I guess that's it. >> >> * Whatever I could find with (suggestions welcome) `grep -r . `find >> /sys/devices/pci0000\:00 -name '*usb*port*'` /sys/bus/usb/devic...

FWIW, a few lessons learned: * Different USB-A sized ports (even if marked USB-3.2) did not prove a stable source, with Pi5 occasionally turning off or rebooting. Sort of behaved well for days, but as soon as I added load like package installs or NUT builds, it did not survive 5 minutes... * Might be the MoBo turning off or cycling the port due to "overload"?.. * Tried the