[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: lilo not "accepting" a new kernel

Ron Johnson wrote:

On Sat, 2006-04-08 at 10:12 -0700, Mike Bird wrote:

On Sat, 2006-04-08 at 12:07 -0500, Ron Johnson wrote:

When I run lilo to integrate a new kernel, it is rejected.
Anyone have a clue why?
# lilo -v LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger 
  Development beyond version 21 Copyright (C) 1999-2004 John Coffman
  Released 17-Nov-2004, and compiled at 10:36:02 on Nov 29 2005
  Debian GNU/Linux
Warning: LBA32 addressing assumed 
  Reading boot sector from /dev/hda
  Using MENU secondary loader
  Calling map_insert_data
Boot image: /boot/vmlinuz-2.6.12-1-386 
  Mapping RAM disk /boot/initrd.img-2.6.12-1-386
  Added Linux-2.6.12 *
Skipping /boot/vmlinuz-2.6.14-1-386 <<<<<<<<<<<<<<<< 
  Writing boot sector.
  /boot/boot.0300 exists - no boot sector backup copy made.


Here is the commentless version of my /etc
  boot=/dev/hda
  root=/dev/hda2
  map=/boot/map
  delay=20
  prompt
  image=/boot/vmlinuz-2.6.12-1-386
          label=Linux-2.6.12
          read-only
          optional
          initrd=/boot/initrd.img-2.6.12-1-386
  image=/boot/vmlinuz-2.6.14-1-386

                                   ^

          label=Linux-2.6.14
          read-only
          optional
          initrd=/boot/initrd.img-2.6.14-1-386

                                               ^

I'd first check that the initrd and image are present
in /boot with exactly those filenames.


Gah!  Staring and assuming are a dangerous combination...

Some time between 2.6.13 & 2.6.14, the Debian people changed the
name of the pre-built kernel from -386 to -686, and I didn't notice
that 1 character change... :(

Thanks.

I'll see if it boots now.




Not the debian folks, but you did chose to install a 686 kernel.
That's it
Reply to: