Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
# Which listing to boot at default. 0 is first, 1 the second etc.
default 0
# How many seconds to wait before booting the default listing
timeout 5
# Nice, fat splash-image to spice things up
splashimage=(hd0,0)/grub/splash.xpm.gz
title=Gentoo Linux 2.6.5
root (hd0,0)
kernel /kernel-2.6.5 root=/dev/hdb3 video=vesafb:ywrap,mtrr vga=0x31A splash=silent
initrd=/boot/initrd-Emergance
this set is working 100%. what i dont understand are these parts:
i thought at first it was supposed to be (hd1,0) instead of (hd0,0). gentoo does not boot at all with (hd0,0). why is grub assigning my harddrives like that?
so i thought ok whatever, if thats how my set up is, then i guess my windows xp drive must be (hd1,0). so i tried adding this to the end of my grub.conf
Code:
title=Windows XP Professional
rootnoverify (hd1,0)
chainloader +1
that doesnt work, it just sits there doing nothing. im currently dual booting by changing the boot order in BIOS and its really annoying. how would i get my XP to work in grub?
Distribution: LFS 5.0, building 6.3, win98se, multiboot
Posts: 288
Rep:
Umm, this probably isn't what you want to hear, but I think you may have an 80mbyte /boot where your xp used to be. Something looks very wrong. You appear to be accessing the grub files (the splash img, the kernel, the stage files) on hda. Try fdisk -l in linux to display existing partions on all hd's.
Have you tried:
title=winxp
rootnoverify hd(0,0)
chainloader +1
That should work if xp isn't toast and the grub install went correctly.
Distribution: LFS 5.0, building 6.3, win98se, multiboot
Posts: 288
Rep:
Odd. The
root hd(n,m)
statement is supposed to set the partition where grub can find menu.lst, the stage files, and the like. The
rootnoverify hd(n,m)
chainloader +1
statement is different. It's more of a direct pointer to a saved copy of another os's boot sector.
Not sure what's going on. It's like grub's hd(n) assignments are changing but I've only seen that with pci udma cards that support drive swapping.
With xp I believe it's possibly to install grub to the boot partition and chainload it via xp's multiboot capability. That might be one solution but I haven't used xp so I can't help you there.
One other approach would be something like this:
grub
root hd(1,0)
setup hd(0)
That should put the grub binary in the mbr and set for menu.lst etc in hdb1. I avoid grub-install. It tends to mess up. With the grub shell you force it to install the way you want.
Distribution: LFS 5.0, building 6.3, win98se, multiboot
Posts: 288
Rep:
Ok, I see now. You are using xp's boot menu to chainload the grub boot menu. IIRC, when you do that you can't use a section in menu.lst to load xp later. Or maybe you could.
rootnoverify hd(0,0)
chainloader +0
?
That should point back to xp's bootloader. (The MBR)
IIRC, Windows doesn't like to boot unless it finds the MBR on the first sector of the first drive. Your grub may be setup so that windows doesn't see things this way which makes it not boot. Try the following for WinXP
Code:
title Windows XP
map (hd1) (hd0)
map (hd0) (hd1)
rootnoverify (hd0,0)
makeactive <-- may/may not be needed
chainloader +1
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.