debian kernel recompile

Doug Sampson dougs at dawnsign.com
Wed Jun 23 18:18:43 PDT 2004


Ok, looks like I trashed the LILO during my recompilation efforts. The box
won't boot up. Instead it gives me a message "MBR F3A:" and promptly drops
dead.

Luckily, I made a floppy boot disk so am able to get back into it.

The next question is: How do I get myself out of this hole?

The way I've set up my partitions is as follows:

sda1    /boot      16 MB
sda2    <swap>    254 MB
sda3    /        8825 MB

sdb1    /usr     9000 MB

sdc1    /home    9000 MB

sdd1    /var    18000 MB

All of these are ext3 partitions.

During the recompilation (dpkg -i
kernel-image-2.4.26.040623_123.Custom_i386.deb), I believe I did the
following:

Said "no" when script asks if I wanted to install boot block using the
existing /etc/lilo.conf.

Said "yes" to do I want to wipe out the old LILO configuration and make a
new one.

Said "yes" to do I want to set up Linux to boot from the hard disk.

It then said it couldn't find a bootloader and asked if I wanted to install
a partition boot record to /dev/sda3 which contains the root partition. I
said "yes". It went on to install the partition boot record, the master boot
record, and made the root partition the active partition.

It hung while making the root partition the active partition as far as I
could tell. I did a cold reset.

I believe, in retrospect, I should have tried to redirect the installation
of the partition boot record to /dev/sda1 instead. Correct?

contents of /boot:
orion:/boot# ls
total 3999
drwxr-xr-x    3 root     root         1024 Jun 23 17:31 .
drwxr-xr-x   22 root     root         4096 Jun 23 17:16 ..
-rw-r--r--    1 root     root       559088 May  7 03:59
System.map-2.4.18-bf2.4
-rw-r--r--    1 root     root       704682 Jun 23 17:09
System.map-2.4.26.040623
-rw-r--r--    1 root     root          512 May  7 04:12 boot.0801
lrwxrwxrwx    1 root     root           11 May  7 04:10 boot.b ->
boot-menu.b
-rw-r--r--    1 root     root        16984 May  7 03:59 config-2.4.18-bf2.4
-rw-r--r--    1 root     root        35384 Jun 23 15:42 config-2.4.26.040623
lrwxrwxrwx    1 root     root           38 May 13 16:16 debianlilo.bmp ->
/usr/share/lilo/contrib/debianlilo.bmp
drwx------    2 root     root        12288 May  7 03:49 lost+found
-rw-------    1 root     root        17408 May  7 04:13 map
lrwxrwxrwx    1 root     root           33 May 13 16:16 sarge.bmp ->
/usr/share/lilo/contrib/sarge.bmp
lrwxrwxrwx    1 root     root           31 May 13 16:16 sid.bmp ->
/usr/share/lilo/contrib/sid.bmp
-rw-r--r--    1 root     root      1263339 May  7 03:59 vmlinuz-2.4.18-bf2.4
-rw-r--r--    1 root     root      1452900 Jun 23 17:09
vmlinuz-2.4.26.040623

contents of existing lilo.conf:
boot=/dev/sda3
root=/dev/sda3
compact
install=/boot/boot.b
map=/boot/map
vga=normal
delay=20

image=/vmlinuz
  label = Linux
  read-only

content of ls /etc | grep lilo:
orion:/etc# ls | grep lilo
-rw-r--r--    1 root     root          132 Jun 23 17:31 lilo.conf
-rw-r--r--    1 root     root          132 Jun 23 17:22 lilo.conf.0
-rw-r-----    1 root     root         4106 May  7 04:12 lilo.conf.1

Looks like the lilo.conf.1 is the original lilo.conf that was created when I
installed Debian that day. The boot parameter points to /dev/sda1.

Now, how do I dig myself out of here? I could try recreating a new lilo.conf
as follows:

boot=/dev/sda1
root=/dev/sda3
install=/boot/boot.b
map=/boot/map
vga=normal
delay=20

image=/boot/vmlinuz
   label=Linux
   read-only

Then try moving the old image (what is the name of the old image?) into
/boot/vmlinuz.

Am I heading in the right direction? Anything else I left out?

~Doug



More information about the KPLUG-List mailing list