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.
I've been working on trying to get 2.6.4 installed on my RedHat 9 (Athlon XP) system for a while now, and have had NO luck. DrOzz's tutorial helped out a LOT, but I'm still having one problem (at least, I think it's only one)
All the modules seem to compile fine, everything seems to work perfectly, until I try mkinitrd. I always come up with the same error.
code:
[root@beecee boot]# /sbin/mkinitrd /boot/initrd-2.6.4.img 2.6.4
No module /bin/true found for kernel 2.6.4
I can't seem to figure out how to include /bin/true, there doesn't seem to be an option in the configuration tool (I'm using xconfig).
I am getting the same thing on RH9 when trying to upgrade to kernel 2.6.5.
this is pissing me off!
my workaround was to use the 2.4 initrd that comes with RH9, but use the 2.6.5 bzImage that I compiled. When I boot, the screen takes a dump. but once X starts up, all is well. it's a half baked solution, but is all i've got for now.
does anyone know how to solve this problem? i've seen nobody anywhere on the net that has offered an answer
What I suggest (which is what I did) was create a script with all the "insmod" or "modprobe" statements necessary to load the modules for your system when it boots and then completely remove the modules with "/bin/true" statements from modprobe.conf.
I then took that script and put it in a script called rc.modules, I believe..........or you can put it directly into the init scripts that already exist in /etc
Last edited by DarkBeethoven; 05-28-2004 at 10:42 AM.
ok, i looked in /etc and there is no "modprobe.conf" file. is there any way to restore it?
PS - i've successfully installed module-init-tools 3.0 following the instructions in the README file:
tar -xzf module-init-tools-3.0.tar.gz
cd module-init-tools-3.0
./configure --prefix=/
make moveold
make
make install
/generate-modprobe.conf /etc/modprobe.conf
ok, thanks. i went to modules.conf and got rid of all the /bin/true statements and mkinitrd worked after that. i can successfully boot into the 2.6.5 kernel now. thanks
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.