Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Am using gentoo kernel 2.6.17-gentoo-r4,during the system boot process the comp scans for more than 20 drivers ," eg:scanning for ehci-hcd in ..../module.dep....file or directory not found".i think most of the drivers it scans are related to usb(ehc-hcd,usb-storage,uhci-hcd,sl811-hcd...etc),ieee 1394..then a lot of drivers related to sata(sata_via,sata_promise,sata_sis..etc)..and ends the scanning session with the modules like dm_mod,dm-mirror.No problem for me to boot in gentoo.i got USB ports in my computer,i compiled the kernel both by disabling and enabling my USB ports,but still got the same scan message at boot.i didnt have any sata support or firewire either in my hardware hence not in the kernel too,also hotplug is disabled.Help me on this.
nothing unusual at modules.autoload.yes i compiled the module myself but i given support for those usb modules in my previously built kernel..but again showing the same "scanning for ...",at the boot time.These scanning happens just after the hardware detection.The initrd image am using is still the old one,is that causing the problem?
First, configure your kernel for your hardware. It takes some time because you have to step thru all submenus, disable everything you do not need. Compile everything in what you do need, leave ALSA as modules (and some other things not always in use as floppy, etc.). There is no point using initrd with self-compiled kernel.
Second, since you already have same version of kernel installed - clean up /lib/modules/<your_kernel_version> before running 'make modules_install'.
i already done all those things mentioned above..i even deleted the modules folder before the compilation of my new kernel,again it is ended with same problem,if any one nevemind ,please go through this link http://forums.gentoo.org/viewtopic.php?t=466962
If any one can say a good solution to this problem is really helpful
OK, there is a common mistake even seasoned Gentoo users do sometimes - they forget to mount /boot before copying the kernel image there. This means your new kernel ends up in /boot directory of root partition and is not used at all. Make sure you have your /boot mounted before installing kernel.
Thats a good guess but i dont have any seperate boot partition,so that possibility rules out.i think this is the problem with modules,first i got the kernel that comes with the fresh installation of gentoo,then i changed it to the current one,but one thing i noticed is that,when booting from gentoo 2006 live cd,it scans for these modules at the boot,and the scan is a success there,the error produced is that"on scanning the corresponding modules are not found in module.dep",if anything interesting strikes to any one please keep posting.
yes thats it.i noticed your comment about the initrd in your previous post as initrd has got nothing to do with newly compiled kernel,but it didnt striked me that the same thing causing the problem for me,actually initrd was really un-noticable.Now i removed the line of initrd in grub.conf and now my gentoo boots without any scanning.
And my experience with this problem was very funny,i compiled the kernel for about dozen times,played with modules..any way it was a very learning experience for me.thanks really to Emerson,sabot,sabot for responding.