> I must have messed up when editing menu.lst. Anyway, the ability to boot
> went away (GRUB complains about a 'file missing', and I've put myself
> down that rabbit hole once already). It took Ubuntu's Alternate Install
> CD to make a command line fix possible. Maybe I'll try again, later.
You can enter the grub shell and type everything in manually. It even
support tab complete to find the files you need to boot.
I don't remember the option at the grub menu (s?) to get the shell,
but once in you do
root (hd1,0) #You can hit tab after type (h it will auto-complete like bash
kernel /boot/vmlinuz-2.6.17-11-generic root=/dev/sda1 ro #same auto
complete here after the first forward slash. Then you have to type
the stuff starting at root= manually
initrd /boot/initrd.img-2.6.17-11-generic
boot
> I'm about ready to junk this 64-bit system and go back to 32. 8-(
Other than to say you did it, I don't see any reason to run a 64-bit system.
Received on Wed Apr 18 18:31:06 2007
This archive was generated by hypermail 2.1.8 : Wed Apr 18 2007 - 18:31:13 CST