Art Fore wrote: > Think I am getting a better understanding of this whole process, but > have a few questions still. I am at work now, so I only have my laptop > to look at, also Suse 10.2 but 32-bit. > > Yast bootloader shows root device as /dev/sda2. > OK > Yast Sysconfig Editor Loader_location shows blank, but also has note > that default is mbr. /etc/sysconfig/bootloader shows LOADER_LOCATION="". > /boot/grub/device.map shows (hd0) /dev/sda. > OK, the variable is not set, meaning though the note says mbr is default (used to be) but this was changed for some reason in 10.2. See the Release Notes for more details. > /boot/grub/menu.lst shows root (hd0,1) for the linux partition. (First > partition is Windows). > That is correct. > /boot/grub/menu.lst also has a line gfxmenu (hd0,1)/boot/message. What > does this mean? > That the graphical menu file message is located on sda2 in /boot > >From the above, it looks like hd0,1 equates to /dev/sda2. Is that right? > Yes > Does the /boot/grub/device.map (hd0) /dev/sda Indicate the mbr is > located on /dev/sda? > No. It means your BIOS is telling Grub your first boot HD is sda. Though I'm sure the generic bootloader must work for some, I prefer to have Grub in the mbr. You should change the variable in bootloader to mbr via Yast and perhaps it will automatically write is to the mbr on sda. If it doesn't work, you can always go to the grub command, i.e. grub grub>root (hd0,1) grub>setup (hd0) grub>quit
That will give you feedback and will work regardless of the variable, but for future updates I would recommend changing that variable in Yast. HTH -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
