Hello Anton,
Sunday, January 5, 2003, 2:04:39 PM, you wrote:
AP> what does your grub.conf look like?
# 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,0)
# kernel /boot/vmlinuz-version ro root=/dev/md6
# initrd /boot/initrd-version.img
#boot=/dev/sda
default=2
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title Red Hat Linux (2.4.19-ac4)
root (hd0,0)
kernel /boot/vmlinuz-2.4.19-ac4 ro root=LABEL=/ vga=791
initrd /boot/initrd-2.4.19-ac4.img
title Red Hat Linux (2.4.18-14)
root (hd0,0)
kernel /boot/vmlinuz-2.4.18-14 ro root=LABEL=/ vga=791
initrd /boot/initrd-2.4.18-14.img
title Red Hat Linux (2.4.18-14smp)
root (hd0,0)
kernel /boot/vmlinuz-2.4.18-14smp ro root=LABEL=/ vga=791
initrd /boot/initrd-2.4.18-14smp.img
AP> thats probably where the problem is...
I had thought that it might be a grub.conf problem, but it looks
normal to me and hasn't been changed (by me) since the last kernel
upgrade (2.4.18-14) on Dec 23.
AP> does it get to the point where grub allows you to pass options to it?
AP> (should have a splash screen, with boot images to load, probably only
AP> one option) but you can edit it by pressing 'e' and trying other
AP> options.
Unfortunately, it doesn't get that far. Once the routine system
startup checks and initializations are performed, the screen shows
"GRUB", as it normally does before presenting the GRUB GUI, but
freezes at that point.
--
Best regards,
Brian Curtis
--
Psyche-list mailing list
Psyche-list@redhat.com
https://listman.redhat.com/mailman/listinfo/psyche-list
