Just to verify and make sure I have this right,
If I installed 11.2 (32bit) via iso image burned to dvd, my linux kernel is v 2.6.31.5 correct?
uname -a
post result
yea its a little more difficult than that, I’m stuck in Grub stage 1.5 on that computer and need to load the kernel
?? anyone else have any insight? or even advice on how to get past Grub stage 1.5?
I think your disk or interface may be hosed, but nonetheless if you want to give it a try. <TAB> means tab key then use file completion to pick the correct candidate file.
grub> root (hd0,0) # assuming / and /boot on sda1, otherwise try (hd0,1) and so forth
grub> kernel /boot/<TAB> # pick the latest vmlinuz image, and type it in
grub> initrd /boot/<TAB> # pick the latest initrd, ditto
grub> boot
Good luck.
PS: If you actually get it to boot, you probably need to add root=/dev/sda1 after the kernel name. Or sda2 or whichever is the / partition.
This worked 100% smoothly the first time I tried. Thank you very much, very very much.
Please understand that I am new. I am about two months into the linux world. Would it be possible for for help on how to do that
ken_yap wrote :
PS: If you actually get it to boot, you probably need to add root=/dev/sda1 after the kernel name. Or sda2 or whichever is the / partition.
I have tried to find literature, but nothing has proven to be fruitful.
??
In the file
/boot/grub/menu.lst
For eg, my default boot is
###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.2 - 2.6.31.12-0.2
root (hd0,4)
kernel /boot/vmlinuz-2.6.31.12-0.2-default root=/dev/disk/by-id/ata-FUJITSU_MJA2250BH_G2_K95CT9A2D4UF-part5 resume=/dev/disk/by-id/ata-FUJITSU_MJA2250BH_G2_K95CT9A2D4UF-part2 splash=silent quiet showopts vga=0x314
initrd /boot/initrd-2.6.31.12-0.2-default
That was originally created by the installer.
A brief device ID eg might be
title openSUSE 11.2
root (hd0,4)
kernel /boot/vmlinuz root=/dev/sda5
intrid /boot/intrid
/dev/sda5
Is what Ken was talking about, but your root partition may be different.
Perhaps you can post your menu.lst
su terminal
cat /boot/grub/menu.lst
su in terminal
and than typing…
cat /boot/grub/menu.lst
…will give me this…
linux-l0yt:/home/pleh # cat /boot/grub/menu.lst
Modified by YaST2. Last modification on Tue Apr 13 00:34:05 EDT 2010
THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
gfxmenu (hd0,1)/boot/message
##YaST - activate
If that’s from a installed and running system. It looks like it’s empty.
Have a look in the /boot/grub/
directory to see if there is a old version, may look like: menu.lst.old
yes there is
menu.lst.old
su -
terminal
cat /boot/grub/menu.lst.old
post result
Modified by YaST2. Last modification on Fri Apr 16 02:19:17 EDT 2010
THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
##YaST - activate
##YaST - generic_mbr
So you have no menu.
Your easiest option is to re-install the OS. Because even if the kernel is in place, I doubt it’s in good order and to try and explain to you how to write a menu is tricky.
Have you tried the repair option with the DVD?
You proceed as if for a New Install and then at this part:
http://public.bay.livefilestore.com/y1p7nWQFcnkLGnuRBtvbC282ZWovoRJrstb6bn1jwkb1FeJzPIzOaaqksBx8zRVNIqs5S_md8raABzz2x-jnokv4w/pic5-select%20New%20Install.png
Select the repair. And probably let it automatically repair.
I don’t suppose there would be a way to access repair from the gUI would there. Currently can’t boot from CD
-cheers
Are you saying you have this system booted?
If that’s the case and it’s just the menu that’s messed up. Use Yast - Bootloader to propose a new configuration.
But obviously, if this system has a working kernel, then you could write your own menu. Something like I described earlier in post #7
Solved…
What I had to do was go in, install PloP, for USB Booting w/out BIOS support, go into my menu.lst and have it load that installed instead of the kernel. it installed it. At that point i rebooted, installed and figured I might as weel try to boot from the CD-Rom. It worked, I didn’t even have to use the extra step of booting from USB.
So, it obviously wasn’t my hardware, at some point I destroye my option in the bootsplash, (but I was able to fix that before the new clean install…
I’m thinking the cause of this madness was maybe it was booting from MBR, not giving the chance for BIOS, or even the toshiba settings to kick in? this was a several week battle and was really hoping to lern from it… thanks guys…
-cheers
Not how it works. When you power on the BIOS is the first thing that is given control. The bare hardware does not know anything about I/O that is what the BIOS is for (Basic Input Output System). So without running a BIOS the machine can not read anything from the disk.
yes, seems though that grub was over riding any settings I configured in the BIOS menu. and once I installed PloP, everything was in perfect working order…
…just kinda weird