Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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.
Trying to build a new kernel but all the stuff I need is built in, no modules after make menuconfig I run make rpm.. I forgot how to make an RPM out of it actually but when I do a make rpm it goes thru the entire process but at the end it errors
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.67514
+ umask 022
+ cd /usr/src/redhat/BUILD
+ cd kernel-2.6.17.5
+ mkdir -p /var/tmp/kernel-2.6.17.5-root/boot /var/tmp/kernel-2.6.17.5-root/lib /var/tmp/kernel-2.6.17.5-root/lib/modules
+ INSTALL_MOD_PATH=/var/tmp/kernel-2.6.17.5-root
+ make modules_install
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
make[2]: *** [modules_install] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.67514 (%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.67514 (%install)
make[1]: *** [rpm] Error 1
make: *** [rpm] Error 2
Distribution: Xubuntu 9.10, Gentoo 2.6.27 (AMD64), Darwin 9.0.0 (arm)
Posts: 1,151
Rep:
Why would you disable loadable modules support? I don't like modules either, but even with everything compiled into the kernel you should have this on. Now I don't know anything about about making an .rpm, but to me it looks like it is calling make modules_install and this fails because your kernel doesn't have support for modules. go back to make menuconfig and under 'Loadable module support' I would a least enable these 3:
Code:
[*] Enable loadable module support
[*] Module unloading
[*] Forced module unloading
[ ] Module versioning support
[ ] Source checksum for all modules
[ ] Automatic kernel module loading
Some things you just can't do without modules; like the nvidia driver for example or my wifi driver: it's unstable and causes the kernel to crash so I load the module to go online then unload it when I'm done for stability. If you have loadable module support it just means the kernel can load a module. If you compile everything into the kernel 'make modules_install' won't even install any modules.
Last edited by johnson_steve; 07-19-2006 at 12:09 PM.
I run servers, not desktops thats why I build my kernels statically... less attempts at exploits, all my hardware is the same so I can interchange drives and chassis around without hiccups and I know exactly what needs to be built into kernels when I load the previous config file.
Yes if I was running a desktop enviroment I would have a modulated kernel but statically built I know what I need, and takes less time to boot
Quote:
Originally Posted by Thetargos
Check the .spec, disable the make modules or modules_install steps, and rebuild.
I figured as much, the spec file is above I cat the output of the spec file I guess all I need to do is just remove the lines and run make rpm again but I think ill just have the same problem again. The spec file only shows up after I make rpm, not before... i'll find out
This is a intel based config, with some scsi/smp support mostly generic.
If I have to edit the macro file every time that could be a headache
I use the rpmbuild system, and actually have the spec under my SPECS directory of my defined rpmbuild environment (which in my case is not /usr/src/redhat, but ~/rpmbuild). You can define your build environment in the .rpmmacros file and set your path and what not, just you will have to replicate the /usr/src/redhat tree, then manage all through .specs, build with rpmbuild $RPMBUILD/SPECS/<your_kernel>.spec and make sure you have all you need in $RPMBUILD/SOURCES, including .configs and what not. That should work well for you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.