lilo.conf ---> how do i dual boot between kernels?

nenyo · 08-18-2005, 05:35 PM

i have an OLD laptop and i just put vectorlinux 3.2 on it. i want to upgrade the kernel to 2.4.31 or 2.6(not sure if it would run it though). since im a total novice with the whole kernel thing i want to be able to boot back into the old kernel to retry WHEN i screw it up. if i set up the old one as vmlinuz.old and boot from that it would be perfect.

i know how to do this with grub but is there a way with lilo? if so how.

:::::::: justification (my predicament) ::::::::
i will probably put grub on it later but for now im using lilo. i need to get network support to start downloading stuff for setup. in order to do this i need ndiswrapper for my wireless card because the computer has no networking capabilities other than a pc card slot. ndiswrapper require that i upgrade to 2.4.20 first.

Bruce Hill · 08-18-2005, 06:11 PM

Having an old computer shouldn't be a problem for the kernel. It's detecting hardware, and unless they've dropped support for your older hardware, a 2.6.x.x should work fine.

Kwan Lowe's Kernel Build Guide should take care of that part. He has LiLO and GrUB instructions.

Also use the instructions in Jesper Juhl's super fast 2.6 guide for getting it installed. Here's an example of my /etc/lilo.conf for two different boxen. One is a Slackware only box with two kernels, the other has a Windoze boot and several Slackware kernels.

Code:

mingdao@slackbox:~$ cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact        # faster, but won't work on all systems.
prompt
timeout = 50
# VESA framebuffer console @ 1024x768x256
vga = 773
# ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.12.5
  root = /dev/hda2   
  label = Slack-2.6.12.5
  read-only
image = /boot/vmlinuz
  root = /dev/hda2   
  label = Slack-2.4.31  
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

Code:

mingdao@james:~$ cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/hda
# Bitmap in BMP format: 640x480x4
  bitmap = /boot/slack.bmp
# Colors fg,bg,sh,h-fg,h-bg,h-sh
  bmp-colors = 9,0,9,0,9,0
# Location of the option table: x,y,column,lines,space
  bmp-table = 61,15,1,8
# Timer x,y,fg,bg,sh
  bmp-timer = 73,29,0,9
#append="elevator=cfq"
#compact # faster, but won't work on all systems.
prompt
timeout = 50
# VESA framebuffer console @ 1024x768x256
vga = 773
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.12.5
root = /dev/sda2
label = 2.6.12.5
read-only
image = /boot/vmlinuz-2.6.12.4
root = /dev/sda2
label = 2.6.12.4
read-only
image = /boot/vmlinuz-2.6.12.3
root = /dev/sda2
label = 2.6.12.3
read-only
image = /boot/vmlinuz-2.6.12.2
root = /dev/sda2
label = 2.6.12.2
read-only
image = /boot/vmlinuz-2.6.12.1
root = /dev/sda2
label = 2.6.12.1
read-only
image = /boot/vmlinuz-2.6.12
root = /dev/sda2
label = 2.6.12
read-only
image = /boot/vmlinuz-2.6.11.11 
root = /dev/sda2
label = 2.6.11.11
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
label = WinXP
table = /dev/hda
# Windows bootable partition config ends

nenyo · 08-18-2005, 07:20 PM

thanks but i already did that. i guessed thats how one is supposed to do it and gave it a try. i then coppied yours and changed the info to fit my comp. that didn't work either. when i boot up it still shows only one option in the list.

do i have to export to mbr somehow?

Bruce Hill · 08-18-2005, 07:32 PM

After you edit the file "/etc/lilo.conf" you must run "/sbin/lilo" as root.

nenyo · 08-18-2005, 09:26 PM

thank you. worked perfectly

Bruce Hill · 08-18-2005, 09:46 PM

Quote:

Originally posted by nenyo
thank you. worked perfectly

You're welcome. It was in both kernel guides I gave you, btw:

Quote:

Install the new kernel by running the lilo program.

$ /sbin/lilo
~ Kwan Lowe

Quote:

when you are done, save the file and run /sbin/lilo to reinstall the lilo bootloader
~ Jesper Juhl

:{)>