Re: GRUB configuration to dual boot Windows XP w/FC3
From: Kill Bill (xbill_at_msn.com)
Date: 05/09/05
- Previous message: Alfred Z. Newmane: "Upgrading GLIBC, recompiling progs ok, but cant find GLIBC"
- In reply to: Andrew Falanga: "GRUB configuration to dual boot Windows XP w/FC3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 09 May 2005 13:20:45 +0100
Andrew Falanga wrote:
> Hi,
>
> I really hope this time this message gets to the group. Anyway, I'm
> having difficult getting the right commands in my grub.conf file to
> chainload Windoze. I'll provide, below, my grub.conf file. Basically,
> the way I have it now results in the boot process simply stopping after
> grub dumps the Windows XP section to stdout (or stderr). As you'll see,
> I've commented the lines that remap my hard drives. I have my BIOS
> setup to use my SATA drive (with Linux) to be drive 1 and my EIDE drive
> to be drive 2 (after reading the grub manual, I thought I'd need them).
> However, with the map commands, the boot process still hangs and in
> addition to dumping the Windows XP section, I see "GRUB" on the screen.
> So, what gives? What am I missing? Below is my grub.conf.
>
> Andy
Are you able to boot to linux? Or you are not able to boot to any of the
OSes?
>
> # grub.conf generated by anaconda
> #
> # Note that you do not have to rerun grub after making changes to this file
> # NOTICE: You have a /boot partition. This means that
> # all kernel and initrd paths are relative to /boot/, eg.
> # root (hd0,0)
> # kernel /vmlinuz-version ro root=/dev/sda3
> # initrd /initrd-version.img
> #boot=/dev/sda1
> default=0
> timeout=5
> splashimage=(hd0,0)/grub/splash.xpm.gz
> hiddenmenu
> title Fedora Core (2.6.9-1.667)
> root (hd0,0)
> kernel /vmlinuz-2.6.9-1.667 ro root=LABEL=/1 rhgb quiet
> initrd /initrd-2.6.9-1.667.img
>
> title Windows XP (Home Edition)
> # map (hd0) (hd1)
> # map (hd1) (hd0)
> rootnoverify (hd1,0)
> chainloader +1
> boot
>
I am not sure if this will help or not but I experienced that the SATA
driver messes up the disk notation. I remember I had to name them as
(E)IDE drives (i.e., /dev/hdaX, etc) in grub.conf but name it as SCSI
disks (i.e., /dev/sdaX) in /etc/fstab. In my case, I didn't have windoze
though. I guess that the SATA drive is recognised as an IDE device by
BIOS and its actual driver is an SCSI one (after initrd is loaded?). By
all means it helps using disk labels. Just that map, root and
rootnoverify commands don't support disk labels.
I also remembering that you may have to modify the file device.map
(change IDE-stype naming to SCSI-stype). For example, change "(hd1)
/dev/hda" to "(hd1) /dev/sda". Not sure if this is relevant since I
don't know if you are able to boot to linux.
Good luck,
KB
> ----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet
> News==----
> http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+
> Newsgroups
> ----= East and West-Coast Server Farms - Total Privacy via Encryption =----
-- NT stands for New Technology. Windowds NT(NT4.x)/2K(NT5.0)/XP(NT5.1) was built on NT Technology. Anyone understands what "new" means, so everyone knows M$ Windows NT/2K/XP/Whatever is a *real* innovation.
- Previous message: Alfred Z. Newmane: "Upgrading GLIBC, recompiling progs ok, but cant find GLIBC"
- In reply to: Andrew Falanga: "GRUB configuration to dual boot Windows XP w/FC3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|