[SOLVED] LILO Problem

klee12 · 05-26-2013, 11:35 PM

Hello,

I want to upgrade from Slackware 13.37 to Slackware 14.0. Usually I run dual boot ... one that can dual boot the current system (e.g. 13.37 kernel) and the new new system (e.g. 14.0 kernel). The root of the new system is mounted on /Sda1 and I have the OS install on /dev/sda1. I want to lilo to a memory stick on /dev/sdd. My lilo.conf with comments removed is

<<

lba32
boot=/dev/sdd
append=" vt.default_utft=0"
timeout=300
delay=100
vga=788

image=/boot/vmlinuz
root=/dev/sda6
label=Slack13.37:32
read-only

image=/Sda1/boot/vmlinuz
root=/dev/sda1
label=Slack:32_14.0
read-only

>>

I run lilo. There are two warnings (sdd not on first disk an boot sector and map file are on different disks) and then

<<
Added Slack13.37:32 *
Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite boot loader
>>

What did I do wrong. I have used this same config file with minor changes and it worked before.

If I go run the new version (with 14.0 kernel), enter setup, then config lilo, will I be able to generate a lilo.conf file without actually running lilo (i.e. leave MBR alone)?

Thanks in advance for any help

Didier Spaier · 05-27-2013, 12:58 AM

To avoid "Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite boot loader", you need to upgrade lilo, the version shipped in 13.37 is not able to install 14.0. Just do this:

Code:

lftp -c 'open http://mirrors.slackware.com/slackware/slackware-14.0/source/a; mirror lilo"
cd lilo
su
chmod +x lilo.Slackbuild
./lilo.SlackBuild
upgradepkg /tmp/lilo-23.2-i486-3.txz

klee12 · 05-28-2013, 06:40 PM

Thanks Didier. That did the trick.

Before I checked here, I looked at the SlackBuild site to see if it had anything for Lilo. I couldn't find anything. Is there any reason why?

klee12

astrogeek · 05-28-2013, 06:57 PM

Quote:

Originally Posted by klee12

Before I checked here, I looked at the SlackBuild site to see if it had anything for Lilo. I couldn't find anything. Is there any reason why?
klee12

If you and Didier will pardon me answering out of turn, that is because SlackBuilds.org does not include anything that is part of the Slackware distro itself, which of course lilo is.

kfanyo · 12-27-2014, 11:27 PM

My system was using symbolic links in boot. The lengths of the names of the system, config, kernel files are well over 63 characters combined. Dropped the links and renamed the actual system files "System.map", "config", "vmlinuz" (23 characters) instead of linking to their more descriptive names and problem solved.