SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: Slint64-14.2beta3 on Lenovo Thinkpad W520
Sorry, no clue. I just saw that the 'huge" kernel of Slackware 14.1 has the ehci_hcd driver configured as a module, that is not the case in Slackware 14.0 in which this driver is built in the kernel.
But I don't know if that can cause a problem when building the initrd. Still, I hardly understand why "lspci -k" doesn't list this driver. Would you be kind enough to plug in some USB device under Slackware, then type
lsmod > lsmod.txt
and attach that file to your next post?
In any case, I'd suggest you stay with the huge kernel till someone finds a more helpful answer, this usually doesn't hurt (unless in some special cases like conflicting drivers loaded, for instance).
Just one more question: does your USB devices work properly when using the huge Slackware kernel ?
Last edited by Didier Spaier; 01-03-2014 at 02:55 PM.
ls: cannot access /sys/module/*_hcd/drivers/*: No such file or directory
when running mkinitrd_command_generator.sh on a 3.12.7 kernel on Slackware -current, built using testing/source/config-testing-3.12/config-generic-smp-3.12-smp. I only made sure that CONFIG_X86_PAE, CONFIG_PREEMPT, CONFIG_SCHED_AUTOGROUP and Processor type are enabled/correct (I also disabled CONFIG_DEBUG_KERNEL, as I use the nvidia driver). Otherwise I didn't change anything.
When running the same command on a 3.10.17 kernel (huge or generic), I don't get this message. The 3.12.8-generic-smp kernel boots, though. I am able to use USB devices etc. Is this something I should worry about? Or can I ignore this?