Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
For literally several grueling days I've been attempting to compile and boot the latest Linux Kernel release. This is my first time, and after several errors, most caused by my own ignorance I seemed to have comeup with a winning kernel configuration except for one heartbreaking fact.....
.....the boot insists on stalling on: Checking for new hardware..... Just to test that it was not my own impatience, I've left it over night once, and stil next morning, it was still checking for new hardware.
Or boot with nothing (I think its lilo:single or something...I just saw it on another thread)...that way you can get all the way into your system, disable kudzu (I think that's the hardware checker thingy) and then boot normally so you can look at logs and figure out what's wrong (finding a specific error message would be a great start)
However, the closest thing to these I see in the compile confiugrations are under USB Support, and they are:
USB HIDBP Keyboard (basic support)
USB HIDBP Mouse (basic support)
Now the only way I can access these options is if I set the "USB Human Interface Device (full HID) support" to m (module) or n (no). This however cuases me to get a third error on boot, that it can't locate the module for hid.
How can I aquire the misisng modules?
Well, it's very neat if you try to compile your own kernel, you'll gain a lot of knowledge and the kernel runs better if you leave out the options you don't need.
But there's no need!
The message "Checking for new hardware....." is caused by Kudzu. It has nothing to do with the kernel, except that everyting on a GNU/Linux system is correlated to the kernel. Kudzu is just a RedHat tool to check for hardware changes. I highly recommend you disable Kudzu if you reboot a lot but do not change any hardware.
# chkconfig --level 12345 kudzu off
The messages: "
Can't locate module keybdev
Can't locate module mousedev"
indicate that the kernel can't find these modules. These modules are needed if you do HID - needed for USB mouses and USB keyboards. But if you plan to use only PS/2 mouse and keyboard, ignore these messages.
If you want to use in the end HID you have to compile your kernel ofcourse.