lilo fatal error after upgrade to kernel 26 2.6.38.2-1

badmad · 2011-04-01 11:37:33

Hello, when I try to execute 'sudo lilo' after installation of newest kernel from testing it shows me an error:

Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite boot loader

But with kernel 2.6.38.1 it's all ok.

Any suggestions?

Here are my lilo and mkinitcpio configs:

#
# /etc/lilo.conf
#

boot=/dev/sdb
# This line often fixes L40 errors on bootup
# disk=/dev/hda bios=0x80

default=Arch-Linux
timeout=100
lba32
prompt
compact

image=/boot/vmlinuz26
label=Arch-Linux
root=/dev/sdb2
initrd=/boot/kernel26.img
read-only
vga=869
other=/dev/sda1
label=Windows-XP
boot-as=0x80

mknintcpio.conf:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""

# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
#
# This is identical to the above, except the old ide subsystem is
# used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
#
# This setup assembles an pata raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev pata raid encrypt filesystems"
#
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata filesystems"

# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
# compression.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

graysky · 2011-04-01 11:45:52

Retro Have you considered grub or grub2? LILO has been depreciated for years now.

skodabenz · 2011-04-01 11:57:55

graysky wrote:

Retro Have you considered grub or grub2? LILO has been depreciated for years now.

Lilo is still in development https://alioth.debian.org/plugins/scmgi … o/lilo.git . Its grub-legacy which has been deprecated. I would recommend syslinux over grub2 (but grub-legacy is dead).

badmad · 2011-04-01 13:44:47

Well both grub and grub2 gave me a lot of issues, lilo has never failed me... until now

Last edited by badmad (2011-04-01 13:45:18)

pyther · 2011-04-04 19:25:56

badmad wrote:

Well both grub and grub2 gave me a lot of issues, lilo has never failed me... until now

Give syslinux a try: https://wiki.archlinux.org/index.php/Syslinux

Arch Linux

#1 2011-04-01 11:37:33

lilo fatal error after upgrade to kernel 26 2.6.38.2-1

#2 2011-04-01 11:45:52

Re: lilo fatal error after upgrade to kernel 26 2.6.38.2-1

#3 2011-04-01 11:57:55

Re: lilo fatal error after upgrade to kernel 26 2.6.38.2-1

#4 2011-04-01 13:44:47

Re: lilo fatal error after upgrade to kernel 26 2.6.38.2-1

#5 2011-04-04 19:25:56

Re: lilo fatal error after upgrade to kernel 26 2.6.38.2-1

Board footer