2.6.xx kernel much slower for USB transfers than 2.4.32
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.
2.6.xx kernel much slower for USB transfers than 2.4.32
Every time I try to download and compile a 2.6.xx kernel for Slackware 10.2, I use the configuration of the stock 2.4.31 kernel, as it works really well. Now I know that 2.6.16 for example is much newer, but why is it that USB transfers are always dreadfully slow? Same configuration, same everything, just with the new modules and stuff..
Every time I try to download and compile a 2.6.xx kernel for Slackware 10.2, I use the configuration of the stock 2.4.31 kernel, as it works really well. Now I know that 2.6.16 for example is much newer, but why is it that USB transfers are always dreadfully slow? Same configuration, same everything, just with the new modules and stuff..
Anyone know why it's like this? Thanks
-A
I dont know why your transfers are slow but you should really been using the config for your 2.6.XX from slackware-current testing, grab the config from a mirror ftp site and give that a try it may solve your problem.
Cheers, will try it and tell you how it went.. I only have the 2.6.16 source at the moment, it shouldn't be a problem to put the config file in there and execute make oldconfig (and add the new modules), right?
I am also compiling my kernel to 2.6.15.6 with the corresponding config file from Slackware website.Unfortunately,my USB couldn't be detected after using new kernel.I have compiled in UHCI,OHCI and other related modules.I have no problem when using 2.4.31 with SATA before.
Please drop me a line if you have any suggestions.
You need to check what USB controller you're using.
check the output of lspci, there should be some reference to your controller which is most probably a USB2, have you included EHCI in your USB config for the kernel?
The problem was fixed last night.I did not turn on the hotplug so no usb device was detected.After I enabled it,all usb devices were detected successfully.
since you are using 2.6.15.x above, you can use udev to replace hotplug. I don't know whether if it work on default package of Slackware-current, but i update some packages using Piter Punk's packages (new sysinit, module-init-tools, udev, pcmiautils, sysfsutils)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.