Timeline for USB ports stop working after a week, needs restart
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 25, 2020 at 20:53 | history | edited | Edward | CC BY-SA 4.0 |
deleted 42 characters in body
|
| Jan 18, 2019 at 17:54 | vote | accept | varesa | ||
| Jan 3, 2018 at 19:50 | history | edited | Edward | CC BY-SA 3.0 |
After testing the application on my model B+ RPi (see comment) it didn't work so I've added two other ideas to try.
|
| Jan 3, 2018 at 19:17 | comment | added | Edward |
I tested this on a model B+ (rev 1.2, Linux kernel 4.4, Debian wheezy/7.11) Raspberry Pi and it didn't work using either the hub and port numbers (0 2 for built-in hub, all 4 ports) or device and bus id numbers (bus 001, device 004 for my USB-2.0 4-port hub with a wireless LAN adapter). I think the built-in USB hub 0 was more likely to work. Another idea I have for waking up a USB WiFi device is to restart the connection or switch the network interface back on with something like ifup.
|
|
| Jan 1, 2018 at 16:38 | comment | added | Edward | Okay, I don't know much about the subject or that other project. Thanks for stating that the 3+ ports on built-in hub 0 probably don't work on newer RPi models. Also, there's a note that the port numbering from that forum post could be less accurate so use a command to check it. | |
| Dec 31, 2017 at 23:40 | comment | added | SlySven |
I've investigated this for another project looking at USB Hub power control uhubctl Issue 35 and the port 2 control switches the power for all the USB ports as they are all ganged on that line, the remaining power controls from 3 upwards can be set in software but they are not connected to anything and are ineffective. This is on RPi models 1B+ and later, and the port 1 control does have an effect on the Wired Ethernet port but that can be awkward if you are sshing into the RPi on that connection when you switch it off!
|
|
| Dec 31, 2017 at 20:30 | comment | added | Edward | @varesa useful to know, thanks. I think this method could probably be used to restart the bus as well as individual ports but if you've found another way, that's good. | |
| Dec 31, 2017 at 20:25 | comment | added | varesa | In my case I don't think the issue is with a single port. The whole bus goes dead. The part about the P2553W6 USB power fault seems interesting. In the meantime I've "solved" this issue by automatically restarting the devices nightly during a quiet time | |
| Dec 31, 2017 at 16:09 | review | First posts | |||
| Dec 31, 2017 at 19:36 | |||||
| Dec 31, 2017 at 16:05 | history | answered | Edward | CC BY-SA 3.0 |