Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It appears that my linux will not boot at all due to my laptop having one of its two USB ports destroyed, however MS Windows on this same laptop manages things correctly. In Windows, the offending USB port shows as 'unrecognized device', while still allowing unfettered use of the remaining working USB port.
Is there a way to mimic this behavior in linux? In my case, I must use a wireless USB nic on my laptop. I post here because I am assuming this is a kernel flaw rather than a flaw of any particular linux variant.
'usb x-x: device not accepting address x, error -62'
Linux would not care if a usb is bad. It may be that a boot order deal. Try boot options maybe. I think some distros are linux=nousb or something like that maybe no hotplug.
[linux-bzImage...]
[linux-initrd...]
usb 2-1: device descriptor read/64, error -62
usb 2-1: device descriptor read/64, error -62
Booting Linux Kernel 2.6.34
Starting udev daemon for hotplug support...
usb 2-1: device descriptor read/64, error -62
usb 2-1: device descriptor read/64, error -62
Done.
Checking boot options...Done.
Scanning hard disk partitions to create /etc/fstab
Setting Language to C Done.
Setting Timezone to UTC Done.
hclock: can't open '/dev/misc/rtc': No such file or directory
usb 2-1: device not accepting address 4, error -62
usb 2-1: device not accepting address 4, error -62
hub 2-0:1.0 unable to enumerate USB device on port 1
Network device eth0 detected, DHCP broadcasting for IP.
xauth: creating new authority file /home/tc/.Xauthority
xauth: creating new authority file /home/tc/.Xauthority
and there it stops never to continue, I am only assuming because of the USB trouble. The identical linux boot image on my desktop performs perfectly.
I did look into simply bypassing the fuse on that dead port but alas I am unable to identify it as of yet. Thems small parts.
For my purposes, simply disabling all USB support is not an option, I will need at least one working port.
There is nothing actually plugged into any port yet. Not unlike Windows, Linux is interpretting the dead port as a working port with a mystery device on it.
Any ideas?
Sorry for the double post, but I wanted to increase the chance of Jefro reading this, I guess that's two strikes now as far as my forum netiquette, I like walking the thin line!
@Jefro, ahh you sir are correct, its all been a blur, yes I have tried a new linux flavour and it happily ignores the dead usb port as if it wasn't even there. Thanks for your sledgehammer confidence because it inspired me to take a look around.
So yea now to fuss around with the original linux version. Cheers all!
On the original try some boot options like failsafe or default or nousb or nohotplug options. May have to edit grub line at boot. Dunno your distro, may have been installed in such a way to need usb. Try to disable usb in bios maybe then fix distro issue.
The distro that is failing me is TinyCore, I have now tried Puppy and everything works just fine. So now I am to decide to I try to rebuild everything that I need from TinyCore into Puppy, or continue to fight with TinyCore, aw hell I'm gonna do both!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.