SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
doesn't /sbin/lilo -v just show the version?
I did run lilo after and it gave the same error .. kernel too large.
I thought the error could be just as you said, only for a floppy is it too large.
However when I ran lilo after changing lilo.conf to append the new kernel .. it gives that error.
I'm just a little hesititant doing it again because it's running so nice now. =)
Cedrik - I checked out the /usr/src/linux/arch/i386/boot/ and there was a bzImage which was just a bit smaller than my current kernel .. which would make sense.
I then copied it to /boot as vmlinuz.old and then ran lilo .. no problem. (my lilo.conf still has an entry for another kernel) Rebooted and I get a good ole Kernel Panic, VFS Unable to mount root fs on 08:05.
I'll post my lilo.conf
root@cerveza:/etc# cat lilo.conf
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
append="nousb mem=exactmap mem=640K@0 mem=511M@1M"
boot = /dev/sda
message = /boot/boot_message.txt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# VESA framebuffer console @ 1024x768x32k
# VESA framebuffer console @ 1024x768x256
# VESA framebuffer console @ 800x600x64k
# VESA framebuffer console @ 800x600x32k
# VESA framebuffer console @ 800x600x256
# VESA framebuffer console @ 640x480x64k
# VESA framebuffer console @ 640x480x32k
# VESA framebuffer console @ 640x480x256
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda5
label = Linux
image = /boot/vmlinuz.old
root = /dev/sda5
label = Linux-SMP
# Linux bootable partition config ends
I only made one change in make menuconfig so I know I didnt disable any built in support.
assuming your top post means
if you have 4 G of ram
2) The reason I asked the size of your new kernel is that grub can boot kernels up to 1440Kb in size
3) you may also consider the following to assist (=yes)
CONFIG_PREEMPT=y for speed
CONFIG_MODULE_FORCE_UNLOAD=y under loaded mod support so you can compile more drivers than you think you need but won't be forced to reboot
(according to LinuxUser & Developer magazine)
4) you can of course make most things modules but then you are forced to have a bigger initrd image to get your hardware recognised.
it probably sounds like boasting but heres my updated tutorial look for the emergency boot of large kernels on how to use 2 or 3 floppies .
as one floppy is devoted to the kernel its theoretical size is 1440 Kb