Making custom kernel..but drivers and modules wont load on boot
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Making custom kernel..but drivers and modules wont load on boot
Hello
I tried several times to make a custom kernal. Every single time after I do all the required steps, none of my modules and drivers get moved to /lib/modules/'custom kernal name'/kernel/
Is there something I am missing? Oh yeah..these are the commandes i have used.
make dep
make clean
make bzImage
make modules_install
make install
And I am using redhat 7.2 with grub. The kernal will boot but no drivers or modules will load up.
I have seen this before. I would suggest first checking your message log. Look for anything about not being able to find modules,dependecies, etc. It could be that the path is wrong or the system is just looking in the wrong directory for the new modules. That's what the problem usually seemed to be for me.
ok... make sure that the kernel sources are either in /usr/src/linux, or that there is a symlink from /usr/src/linux-2.4.? to the linux dir (which is the way it SHOULD be...) if the compile can't find the sources, you're going to have problems with the modules.
also... go through the config option again and make sure that you've correctly selected the modules as modules, and not as having been compiled directly into the kernel, or mistakenly unselected. 'make xconfig' is the easiest way to configure the kernel.
I thank you for the help and will attempt to recompile again when I have some time to invest in it. But anyone have any idea why something like this would happen? It seems very odd since I just installed the system fresh, and have not tinkered with it at all. Its with the kernel 2.4.7-10 on a red hat 7.2 distribution from unixcd.com. Very odd indeed.
Building a new kernel is a quite substantial bit of tinkering to do to a linux install.
Don't be put off by the fact that your first attempt didn't work as intended, I think most of the regulars here will agree with me when I say that it takes a few goes at it before you get one that works.
Just keep compiling and asking questions and when your first custom kernel boots you'll feel the same thrill we all did at a difficult job well done.
Originally posted by Aussie
Just keep compiling and asking questions and when your first custom kernel boots you'll feel the same thrill we all did at a difficult job well done.
...actually, i was too scared to do anything more substantial than an ls when i built my first kernel... i kept expecting it to crash or start smoking or somthing.
...actually, i was too scared to do anything more substantial than an ls when i built my first kernel... i kept expecting it to crash or start smoking or somthing.
Heh...I remember my first time, I was bouncing around in my chair with anticipation when I did the three finger salute and waited for the machine to boot so I could view the fruits of my labour, and then....kernel panic?!?....What the?!?
Needles to say thank gnu for lilo and back up kernel images
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.