[SOLVED] USB ports stop working after LILO boos kernel (14.4)
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.
USB ports stop working after LILO boos kernel (14.4)
Hi all
I'm running SalixOS (a slackware based distro) on a Zotac Zbox. After upgrading to a new version with a more recent kernel, 2 USB ports and the card reader stopped working. I upgraded the kernel further to 4.4.19 in the hopes that it would fix the problem, but no joy. As the thread title suggests, the ports work fine until the kernel gets booted by lilo.
These commands get the desired result of having autosuspend and autosuspend_delay_ms as negative values which I understand to mean the USB devices should not be suspended. However, no changes to the operation of the ports, excepting what appeared to be a brief flash on the optical mouse when I was testing one port after adding the autosuspend_delay_ms command (set to -1 as above).
Running a live version with kernel 2.6.33 plays fine with all ports as seen by lsusb below.
Code:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 13fd:1640 Initio Corporation
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 003 Device 003: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 045e:0750 Microsoft Corp.
Bus 004 Device 003: ID 192f:0416 Avago Technologies, Pte.
lsusb with 4.4.19 yields
Code:
Bus 001 Device 002: ID 13fd:1640 Initio Corporation INIC-1610L SATA Bridge
Bus 002 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
Bus 002 Device 004: ID 192f:0416 Avago Technologies, Pte. ADNS-5700 Optical Mouse Controller (3-button)
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I msybe got your same problem, my 3.0 USB ports sometimes when I boot up return a error then no longer work. I have discovered that if I just do not plug my external drives in before booting they will not get this problem.
if that is your case then it is called a work around. happy days ~ is still in reruns somewhere.
I'll need to run lsusb with some additional commands under an older kernel. Running it under a recent kernel doesn't appear to give me much more information.
Code:
lsusb -v | grep -A 6 bcdUSB
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x13fd Initio Corporation
idProduct 0x1640 INIC-1610L SATA Bridge
--
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x045e Microsoft Corp.
idProduct 0x0750 Wired Keyboard 600
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
--
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x192f Avago Technologies, Pte.
idProduct 0x0416 ADNS-5700 Optical Mouse Controller (3-button)
--
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
Couldn't open device, some information will be missing
--
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
Last edited by cavit8; 11-01-2016 at 07:47 PM.
Reason: Non-contributory
After much updating of new release kernels and browsing of forums, I've gone to a distro that uses 3.16 kernel and all is well. All ports are operational. I've yet to discover what it is about the architecture of the Zotac that newer kernels dislike, but it's a moot point now.
Thanks to all who contributed. I've marked the thread as solved although strictly speaking it hasn't been.
After much updating of new release kernels and browsing of forums, I've gone to a distro that uses 3.16 kernel and all is well. All ports are operational. I've yet to discover what it is about the architecture of the Zotac that newer kernels dislike, but it's a moot point now.
Thanks to all who contributed. I've marked the thread as solved although strictly speaking it hasn't been.
Extract configs from both kernels (3.16 and 4.4) and compare them for USB-related difference.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.