• We did not send an email asking for donations - please read this post.

USB devices not working, error 110

Monkeylord2390

New Member
Joined
Feb 15, 2022
Messages
3
Reaction score
1
Credits
38
I decided to move to Linux recently, and installed Linux Mint as a place to start. While installing everything was working fine, all devices detected and functioning as expected. This carried onto into the first launch of the distro, where I set up all my applications, updates, etc. Then I restarted after switching my video driver, and now before every boot "usb 1-9: device descriptor read/64, error -110." I did research and found error 110 seems to signify the connection gets timed out, most often attributed to the usb not receiving enough power. It doesn't seem to be a case of not getting power through though, as the lights indicating my devices are detected shine up until the splash screen with the error.

I'm currently using a live cd version of Linux Mint, where everything seems to work perfectly fine, I have reinstalled the distro as well as trying Ubuntu to see if it would help to no avail. I'm sorry to bother anyone, and thank you ahead of time for any help or advice offered.
 


kc1di

Well-Known Member
Joined
May 14, 2021
Messages
1,295
Reaction score
1,085
Credits
9,301
I decided to move to Linux recently, and installed Linux Mint as a place to start. While installing everything was working fine, all devices detected and functioning as expected. This carried onto into the first launch of the distro, where I set up all my applications, updates, etc. Then I restarted after switching my video driver, and now before every boot "usb 1-9: device descriptor read/64, error -110." I did research and found error 110 seems to signify the connection gets timed out, most often attributed to the usb not receiving enough power. It doesn't seem to be a case of not getting power through though, as the lights indicating my devices are detected shine up until the splash screen with the error.

I'm currently using a live cd version of Linux Mint, where everything seems to work perfectly fine, I have reinstalled the distro as well as trying Ubuntu to see if it would help to no avail. I'm sorry to bother anyone, and thank you ahead of time for any help or advice offered.
Can you give us the output of the following terminal command.
Code:
inxi -Fxxxz
thanks.
 
OP
M

Monkeylord2390

New Member
Joined
Feb 15, 2022
Messages
3
Reaction score
1
Credits
38
Can you give us the output of the following terminal command.
Code:
inxi -Fxxxz
thanks.
CPU:
Topology: 6-Core model: Intel Core i5-10400F bits: 64 type: MT MCP
arch: N/A L2 cache: 12.0 MiB bogomips: 69597
Speed: 2899 MHz min/max: N/A Core speeds (MHz): 1: 2899 2: 2906 3: 2900
4: 2903 5: 2903 6: 2900 7: 2909 8: 2908 9: 2908 10: 2901 11: 2900 12: 2900
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
dtherm dts ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
fsgsbase fxsr ht ibpb ibrs ibrs_enhanced ida intel_pt invpcid
invpcid_single lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr mtrr
nonstop_tsc nopl nx ospke pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge
pku pln pni popcnt pse pse36 pts rdrand rdseed rdtscp rep_good sdbg sep
smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr

This is what came out while on the live cd instance
 

Brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
3,175
Reaction score
2,062
Credits
23,638
Welcome to the forums
now, I know this is Linux and not windows, but this silly trick often works.
  1. In a terminal run, shutdown -h now (turn off the computer)
  2. Unplug USB device from computer.
  3. Unplug power cord to back of the computer.
  4. Unplug power from mains socket.
  5. Wait for the light to go out on the charger
  6. Plugged everything back in and booted up.
 
OP
M

Monkeylord2390

New Member
Joined
Feb 15, 2022
Messages
3
Reaction score
1
Credits
38
Welcome to the forums
now, I know this is Linux and not windows, but this silly trick often works.
  1. In a terminal run, shutdown -h now (turn off the computer)
  2. Unplug USB device from computer.
  3. Unplug power cord to back of the computer.
  4. Unplug power from mains socket.
  5. Wait for the light to go out on the charger
  6. Plugged everything back in and booted up.
I didn't think to power cycle it for some reason. This seems to have worked, at least for the time being. I hope that was all that was wrong.

Thank you for your help!
 

Brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
3,175
Reaction score
2,062
Credits
23,638
This seems to have worked, at least for the time being
I said it was silly ;), Give it a few days, If it has stabilised come back and edit your first post to include "solved"
 

kc1di

Well-Known Member
Joined
May 14, 2021
Messages
1,295
Reaction score
1,085
Credits
9,301
The Inxi report certainately was not definitive :(
Good luck.
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Linux.org Hosting Donations
Consider making a donation


Top