SlackwareThis Forum is for the discussion of Slackware Linux.
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.
1) I made sure i had all the tools needed (e.g. the correct version of gcc, binutils, ...)
2) I successfully compiled the kernel
3) I moved it in /boot and linked /boot/vmlinuz to it
4) The kernel size is of about 1.8MB
5) I'm now using a 2.4.26 kernel wich image size is of 2.2MB
6) When re-installing lilo it says: Fatal: Kernel /boot/vmlinuz is too big
another thing: LiLo can use kernels bigger than the MBR because it can access kernels on other part of the disk... so, can it be a filesystem-related matter? the fs where the kernels reside is reiserfs.. BUT it has ever worked (and still now work with 2.4.6 k) with reiserfs... dunno^2
Distribution: Xubuntu, Mythbuntu, Lubuntu, Picuntu, Mint 18.1, Debian Jessie
Posts: 1,207
Rep:
2.6 kernels usually need an initrd.img file or initrd.gz file to boot. This will appear as /boot/initrd.gz or /boot/initrd.img if you have it. If not there is a mkinitrd script in Slack. Do a man mkinitrd for specifics (there are module options for your file system).
you don't need an initrd and it's not caused by the file being to big.
you could try to leave out all those symlinks, and use the real filenames in your lilo.conf.
it won't hurt to also delete any symlink in the /boot dir and use the 'normal' naming scheme.
(vmlinuz-2.6.11 ; System.map-2.6.11 ; config-2.6.11 )
want to know how? just using bzImage instead of vmlinuz ... arch/i386/boot/bzImage has the same size og arch/i386/boot/compressed/vmlinux i used before but LiLo seems to love it!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.