SlackwareThis Forum is for the discussion of Slackware 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.
Previously I had slack 9.0 which used 2.4.22 kernel I believe. I was able to configure the USB on my motherboard as "Legacy/Hi-Speed" and all was fine...
But after upgrading to slack 10.1 with 2.4.29 kernel, if I leave the motherboard USB setting to "Legacy/Hi-Speed", then my flash drive is not even recognized at all. But if I set the motherboard setting to "Legacy/Full Speed", then once again, the flash drive is recognized... BUT, now it's alot slower.
So... anyone know what happend to "hi-speed" support between slack 9 and slack 10??
Ok, problem solved. I'm posting this because someone, sometime will run across this same problem...
When building the kernel via 'make menuconfig', the first menu item is "Code maturity level options", and inside that, "Prompt for development and/or incomplete code/drivers". Well it seems that somewhere along the way, I "excluded" that item, the result being that the "EHCI HCD (USB 2.0) support" did not show up under "USB support", and thus I could never select it. It took me a long time to figure out EHCI is needed for USB2.0, and then to realize that I didn't have that driver in my kernel, and then to realize why it didn't show up.
So, there it is - now my flash drive is back to normal...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.