Timeline for lsusb is taking forever
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 16, 2021 at 12:23 | vote | accept | Tsidia | ||
| Mar 3, 2021 at 16:09 | answer | added | Tsidia | timeline score: 0 | |
| Mar 3, 2021 at 15:43 | comment | added | Tsidia | This command produces a similar issue to the one in question. However, this one does not respond to CTRL-C or CTRL-Z. I don't know how to remove the broken driver | |
| Mar 3, 2021 at 15:34 | comment | added | user1091774 |
You had mentioned that this started after trying to install a network driver. Can you uninstall the driver? What does sudo lshw -C network reveal? If the network device is on the USB bus, it could be interfering with the rest of the system.
|
|
| Mar 3, 2021 at 15:25 | comment | added | Tsidia | I tried to run the command again and checked the syslog file. It doesn't display anything after opening the terminal. I also checked other logfiles in the directory, but I couldn't spot anything meaningful | |
| Mar 3, 2021 at 15:09 | comment | added | user1091774 | Cool. So you've narrowed it down to an internal device. This is progress. Does any log file show what might be causing the issue? | |
| Mar 3, 2021 at 15:09 | comment | added | Tsidia | Disconnecting devices didn't help, it appears to be a problem with an internal device | |
| Mar 3, 2021 at 15:02 | comment | added | user1091774 |
This can sometimes happen if a USB device is refusing to be queried for whatever reason. The first thing to do would be to disconnect all external USB devices from the machine and try lsusb again. If it continues to hang, then a driver for an internal device (such as a keyboard or touchpad) may be corrupted and in need of repair. System logs in /var/log/syslog may contain information relating to the issue.
|
|
| Mar 3, 2021 at 14:49 | history | asked | Tsidia | CC BY-SA 4.0 |