Are you making sure to select "2.4.22" from the Lilo boot menu when your system boots up?

Joshua

Dana Schoonover wrote:

I already ran "lilo -v" before I did the reboot, and
it still seems to be running the old version of the
kernel. Is there anything else I can do?





Err, yeah, I guess we are running lilo now :) Anyway, you probably
need to run "lilo -v" as root in order to re-write
your boot record.


Caleb

On Sun, 2003-10-26 at 22:00, Dana Schoonover wrote:


the contents of lilo.conf are:

prompt
timeout=100
default=linux
lba32
boot=/dev/hda
compact
image=/boot/vmlinuz-2.4.22
       append = "ro root=LABEL=/"
       initrd = /boot/initrd-2.4.22.img
       label = 2.4.22
image=/boot/vmlinuz-2.4.20-8
       append = "ro root=LABEL=/"
       initrd = /boot/initrd-2.4.20-8.img
       label = linux
other=/dev/hda1
       label = Windows_2000
       table = /dev/hda
lilo.conf (END)


the contents of grub.conf are:


# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after


making


changes to this file
# NOTICE: You do not have a /boot partition.


This


means that
# all kernel and initrd paths are


relative to


/, eg.
# root (hd0,1)
# kernel /boot/vmlinuz-version ro
root=/dev/hde2
# initrd /boot/initrd-version.img
#boot=/dev/hde
default=1
timeout=10
splashimage=(hd0,1)/boot/grub/splash.xpm.gz
title Red Hat Linux (2.4.22)
root (hd0,1)
kernel /boot/vmlinuz-2.4.22 ro


root=LABEL=/


hdg=ide-scsi
initrd /boot/initrd-2.4.22.img
title Red Hat Linux (2.4.20-8)
root (hd0,1)
kernel /boot/vmlinuz-2.4.20-8 ro


root=LABEL=/


hdg=ide-scsi
       initrd /boot/initrd-2.4.20-8.img
title Windows2000
       rootnoverify (hd0,0)
       chainloader +1
grub.conf (END)



I think I'm using Lilo now because something or


other


was weird with grub when I switched over to my new
hardware... but in either case, here are the


files.

I don't know what they're supposed to look like..


but


they both have 2.4.22 stuff in them, so... I


don't


know. If anyone knows what I need to do lemme


know


:-) Thanks :-)

Dana




The problem lies somewhere with your boot loader


not


booting the kernel you want it to. Could you tell us something about


it? Is


it grub or lilo? The contents of your /etc/lilo.conf or
/boot/grub/grub.conf (or /boot/grub/menu.lst)?


On Sunday 26 October 2003 18:36, Dana Schoonover
wrote:


[EMAIL PROTECTED] r0b0tg1rl]$ uname -a
Linux localhost.localdomain 2.4.20-8 #1 Thu


Mar 13


17:54:28 EST 2003 i686 athlon i386 GNU/Linux



Does that mean I didn't really update my


kernel?

(If


yes, I really need help.. *laugh*)

(I was trying to go from 2.4.20-8 to 2.4.22,


btw)


=====
"God is bigger than the boogey-man." --Jr. Asparagus


__________________________________
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
http://launch.yahoo.com/promos/britneyspears/




-----------------------------------------------------------------


To get off this list, send email to


[EMAIL PROTECTED]


with Subject: unsubscribe



-----------------------------------------------------------------





-----------------------------------------------------------------


To get off this list, send email to
[EMAIL PROTECTED]
with Subject: unsubscribe



-----------------------------------------------------------------




=====
"God is bigger than the boogey-man." --Jr. Asparagus


__________________________________
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
http://launch.yahoo.com/promos/britneyspears/

-----------------------------------------------------------------
To get off this list, send email to [EMAIL PROTECTED]
with Subject: unsubscribe
-----------------------------------------------------------------







----------------------------------------------------------------- To get off this list, send email to [EMAIL PROTECTED] with Subject: unsubscribe -----------------------------------------------------------------



Reply via email to