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.
I made the commented out changed in below lilo.conf file ( option to
boot to 2.6.7 or old kernel)
After blowing the process and not being able to boot. I took a closer
look at the /boot directory before and after running mkinitrd. In my
infinite wisdom I didn't save file that had the changes after I ran
mkinitrd. Below is the before listing and what it is currently.
What you can't see it that after running mkinitrd it changed the link of
System.map to System.map-generic-2.6.7, config to config-generic-2.6.7,
and vmlinuz to vmlinuz-generic-2.6.7. Afraid for my system, again, I
decided to change the links to the original configuration. Knowing I
will be pointing to them anyway in the lilo.conf file.
Also, I have one disk hda1 with reiserfs and only one mount point /. ( I
know, I know, I wasn't paying attention and didn't partition it up)
after making the changes to lilo.conf I ran the lilo command and I get
this error:
------------------------------------------------------------------------------------------------
Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite boot
loader
------------------------------------------------------------------------------------------------
I get this error with and without then new changed in the file.
Any ideas on what to try? I have been unable to find any real help online.
-------------------------------------------------------------------------------------
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 800x600x64k
vga = 773
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1
label = Linux
read-only
The real problem is the changes in lilo don't show during boot. My understanding is that after you make changes to the lilo.conf file you run "lilo" to comment the changes. This is when I get the error. I am used to using GRUB.
My drive is set up with only one partition "/" and it is reiserfs.
i agree with suslik. unless you have a specific need for initrd that you haven't mentioned, just get rid of it. it's definitely not needed for reiserfs. cut everything after "# Linux bootable partition config ends" (and those commented lines if you don't think you'll need them) and run lilo again.
Originally posted by elegin The real problem is the changes in lilo don't show during boot. My understanding is that after you make changes to the lilo.conf file you run "lilo" to comment the changes. This is when I get the error. I am used to using GRUB.
It seems running "lilo" craps out with a Fatal error and never actually writes the changes to mbr. You need to clean up your lilo.conf and possibly get rid of the initrd thing.
Unless I don't know something about making reiserfs on / work with Lilo, I don't see a reason why
No, I never unistalled lilo. I did this right after installing Slackware 10 (not upgraded). The only thing I installed was KDE 3.3 which involved unistalling KDE 3.2.
For everyone telling him to dump the initrd business:
Per Pat V.'s instructions that comes with the kernel
4. Now that I've built an initrd, how do I use it?
Now that you've got an initrd (/boot/initrd.gz), you'll want to load
it along with the kernel at boot time. If you use LILO for your boot
loader you'll need to edit /etc/lilo.conf and add a line to load the
initrd. Here's an example section of lilo.conf showing how this is
done:
The initrd is loaded by the "initrd = /boot/initrd.gz" line.
Just add the line right below the line for the kernel image you use.
Save the file, and then run LILO again ('lilo' at the command line).
You'll need to run lilo every time you edit lilo.conf or rebuild the
initrd.
An initrd image is needed for loading your SCSI module at boot time or if you are compiling the kernel with ext3 support as a module. If you do not need an initrd image, do not make one and do not edit lilo.conf or grub.conf to include this image.
so according to that, if you don't have a SCSI drive and you haven't built your filesystem as a module, you don't need initrd to boot. and you should not make one or have it in lilo.conf in that case.
so the question for elegin is: do you have a SCSI hard drive or have you built your filesystem as a module? if the answer to both of those is no, then you don't need initrd and you shouldn't use it.
in that case, strip down your lilo.conf to this (edit: changing the vmlinuz kernel name and partitions if necessary, of course):
Code:
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 800x600x64k
vga = 773
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1
label = Linux
read-only
run lilo, and tell us what happens.
Last edited by synaptical; 08-24-2004 at 05:56 PM.
the only thing i can think of is that your boot partition is past the 1024 mark, which i'm not sure even matters anymore, and which it doesn't sound like it would be from your configuration. you could try adding the lba32 line to lilo.conf, though.
also, i think running lilo -U as aeNeo suggested might be a good idea. otherwise, i would get a win98 boot CD from the net, boot to that, fix the MBR, reboot to linux with your boot disk, and try again. if that doesn't work, maybe there's something wrong with your kernel image somehow. also could you post:
ls -l /boot
Last edited by synaptical; 08-24-2004 at 06:21 PM.
Try commenting out or removing the change-rules and reset lines. You are telling lilo that you want the defaults removed that you are going to make your own rules, but then you don't make any.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.