fahd Posted July 16, 2003 Report Share Posted July 16, 2003 Really is it needed to mkinitrd? I have reconfigured the already used kernel-2.4.21-0.13mdk. I just changed the proccesor type(P4). Then I gave the followings: make dep clean bzImage. After that : make modules modules_install. Igave these commands: cp /usr/src/linux/../bzImage /boot/vmlinuz-new cp /usr/src/linux/System.map /boot/System.map-new rm /boot/vmlinuz #remove the soft link rm /boot/System.map #remove the soft link ln -s /boot/vmlinuz-new /boot/vmlinuz ln -s /boot/System.map-new /boot/System.map And made this in LILO, and run lilo -v . The system did not run. I think the initrd is the responsible. Please help me. Where Should I Have Given the command mkinitrd with the appropriate arguments. Thank You. Quote Link to comment Share on other sites More sharing options...
tyme Posted July 16, 2003 Report Share Posted July 16, 2003 you could just remove the initrd line from lilo. but, i think "mkinitrd" in the /usr/src/linux directory and then copying it from...what, /usr/src/linux/boot maybe? Quote Link to comment Share on other sites More sharing options...
Glitz Posted July 16, 2003 Report Share Posted July 16, 2003 Now issue: mkinitrd /boot/initrd-2.4.21-0.13mdk.img 2.4.21-0.13mdk and you should be all set. Make sure lilo is using this initrd image. Glitz. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.