Trouble with lilosetup

[mimosa]

When I click on the button to edit configuration, nothing happens, and the list of boot options above greys out. It is still possible to install lilo, but installation fails if the order of itms is changed.

There is no /etc/lilo.conf.

It may be relevant that I have installed the new lilo - I installed it from source using the QuickInst script, but then I tried with the package from current. The lilo in the 13.37 repos has a bug that stops it working with some more recent kernels (including the Current kernel), and as this is likely to be increasingly problematic, I wonder if there is a case for upgrading lilo in 13.37 and earlier?

Here is the log when I revert to the old lilo;

Code: Select all

vanilla[log]$ cat lilosetup.log
LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 14:44:48 on Feb 16 2010

Reading boot sector from /dev/sda
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/salix.bmp -> slack.bmp
Calling map_insert_file

Boot image: /boot/vmlinuz-huge-smp-3.2.23-smp
Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite boot loader

Here is the log for when I try to change the order of entries (using those green arrows). If I leave everything as is, installation is succesful. This is with the new lilo:

Code: Select all

root[vanilla]# spkg -u lilo-23.2-i486-1.txz
root[vanilla]# lilosetup.py
root[vanilla]# cat /var/log/lilosetup.log 
LILO version 23.2 (released 09-Apr-2011)
  * Copyright (C) 1992-1998 Werner Almesberger  (until v20)
  * Copyright (C) 1999-2007 John Coffman  (until v22)
  * Copyright (C) 2009-2011 Joachim Wiedorn  (since v23)
This program comes with ABSOLUTELY NO WARRANTY. This is free software 
distributed under the BSD License (3-clause). Details can be found in 
the file COPYING, which is distributed with this software.
Compiled at 19:26:55 on Aug 11 2011

Reading boot sector from /dev/sda
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/salix.bmp
Fatal: open /boot/salix.bmp: No such file or directory

Now this looks like the problem with current that was solved by symlinking salix.bmp to slack.bmp. That symlink is still in place in my Current /boot directory.

[Akuna]

OK, tx for this info. I'll ensure LiloSetup is eventually working with current.

[Shador]

The problem seems to be that on current still the stock Slackware lilo package is used which doesn't provide the salix.bmp. If you symlink that file as suggested by laprjns on the maillist, I'm sure it'll work:

Code: Select all

ln -s /boot/slack.bmp /boot/salix.bmp

[mimosa]

Yes, it does (I've yet to check by rebooting) but clicking the option to edit config still greys out. So something is not right. That is also just a hack.

[djemos]

Upgrade lilo with this lilo package 32 or 64 bit and check if problem solved.
http://people.salixos.org/djemos/lilo/

[mimosa]

Thanks djemos. That solves the salix/slack .bmp problem (as does the symlink) so the setup works even changing the order; and now I have the Salix not Slack image!

However, the problem of greying out when clicking on "Edit config" remains.

I also tried it in Current, using the existing lilosetup. Some messages were produced, but everything still worked.

[Akuna]

I'll wait for the dust to settle a bit more on current before looking at it. Probably not a big thing. Again thanks for the info, it's on my ToDo list

[Andyun]

Thank you, djemos! I could not reinstall LiLo with LiloSetup (Lilo-22.8-i486-13tm.txz, /var/log/lilosetup.log):

Code: Select all

LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 14:44:48 on Feb 16 2010

Reading boot sector from /dev/sda
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/salix.bmp
Calling map_insert_file

Boot image: /boot/vmlinuz-linux
Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite boot loader

and your package Lilo-23.2-i486-13dj.txz helped me!:

Code: Select all

LILO version 23.2 (released 09-Apr-2011)
  * Copyright (C) 1992-1998 Werner Almesberger  (until v20)
  * Copyright (C) 1999-2007 John Coffman  (until v22)
  * Copyright (C) 2009-2011 Joachim Wiedorn  (since v23)
This program comes with ABSOLUTELY NO WARRANTY. This is free software 
distributed under the BSD License (3-clause). Details can be found in 
the file COPYING, which is distributed with this software.
Compiled at 19:26:55 on Aug 11 2011

Reading boot sector from /dev/sda
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/salix.bmp
Calling map_insert_file

Boot image: /boot/vmlinuz-linux
Mapping RAM disk /boot/initramfs-linux-fallback.img
The initial RAM disk will be loaded in the high memory above 16M.
Added Arch  +  *

Boot image: /tmp/lilosetup/mnt/sda4/boot/vmlinuz-huge-recent-smp-3.3.6-smp
Added Salix

Writing boot sector.
/boot/boot.0800 exists - no boot sector backup copy made.

Thank you, mimosa, for this topic!
Thank you, Akuna, for LiloSetup!