bug-grub
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [grub #2] Win2K unable to be booted by installed GRUB


From: Herbert Szumovski
Subject: Re: [grub #2] Win2K unable to be booted by installed GRUB
Date: Sun, 1 Dec 2002 12:42:26 +0100
User-agent: KMail/1.4.3

Hmm,
I have a nearly equal setup on my laptop, and it works fine (grub 0.92).
The only thing I see is that you tried booting windows with root(hd0,0). 
I don't know why it worked (as you said), but actually that should 
be rootnoverify(hd0,0) (see explanation in the docs).
See below my config file for comparison (RH8.0 and Win2000):

default=2
timeout=5
splashimage=(hd0,6)/grub/herbiesBoot.xpm.gz
password --md5 something
title Boot my test 2.5 kernel (2.5.47)
        root (hd0,6)
        kernel /vmlinuz-2.5.47 ro root=LABEL=/ hdc=ide-scsi vga=0x315
        initrd /initrd-2.5.47.img
title Boot original RedHat kernel (2.4.18-14)
        root (hd0,6)
        kernel /vmlinuz-2.4.18-14 ro root=LABEL=/ hdc=ide-scsi
        initrd /initrd-2.4.18-14.img
title Boot my production kernel (2.4.18-17.8.0herbie2)
        root (hd0,6)
        kernel /vmlinuz-2.4.18-17.8.0herbie2 ro root=LABEL=/ hdc=ide-scsi 
vga=0x315
        initrd /initrd-2.4.18-17.8.0herbie2.img
title Boot my legacy systems
        rootnoverify (hd0,0)
        chainloader +1

Cheers, Herbert


On Sunday 01 December 2002 12:09, you wrote:
> >Reporter: address@hidden
> >Summary: Win2K unable to be booted by installed GRUB
> >Version: 0.91
> >Type: software bug
> >
> >Message:
> >I have got a disk partitioned as follows:
> >Disk /dev/hda: 255 heads, 63 sectors, 9729 cylinders
> >Units = cylinders of 16065 * 512 bytes
> >
> >   Device Boot    Start       End    Blocks   Id  System
> >/dev/hda1   *         1      2550  20482843+   7  HPFS/NTFS
> >/dev/hda2          2551      2556     48195   83  Linux
> >/dev/hda3          2557      7653  40941652+  83  Linux
> >/dev/hda4          7654      9729  16675470    f  Win95 Ext'd (LBA)
> >/dev/hda5          7654      7702    393561   83  Linux
> >/dev/hda6          7703      9566  14972548+  83  Linux
> >/dev/hda7          9567      9696   1044193+  82  Linux swap
> >/dev/hda8          9697      9729    265041   83  Linux
> >
> >The first 20GB partition contains a Win2K installation, and the rest is a
> > default Redhat 7.3 installation, with the mount list as follows:
> > /dev/hda5 on / type ext3 (rw)
> >none on /proc type proc (rw)
> >usbdevfs on /proc/bus/usb type usbdevfs (rw)
> >/dev/hda2 on /boot type ext3 (rw)
> >none on /dev/pts type devpts (rw,gid=5,mode=620)
> >/dev/hda6 on /home type ext3 (rw)
> >none on /dev/shm type tmpfs (rw)
> >/dev/hda3 on /usr type ext3 (rw)
> >/dev/hda8 on /var type ext3 (rw)
> >
> >While building this box I first installed Windows, and then I installed
> > Redhat.  During the redhat installation I directed the installer to set
> > grub up on the boot sector, not the MBR.  Thus, the MBR still contained
> > Windows' default boot loader.
> >
> >After the installation I verified that Windows would still boot from the
> > MBR.  I also verified that it would boot from a copy of GRUB on a floppy
> > disk, with the following commands: root (hd0,0)
> >chainloader +1
> >boot
> >
> >I then verified that Linux would boot from a floppy disk containing grub -
> > I checked it by chain-loading the copy of GRUB on the boot partition from
> > the instance on the floppy.  All worked fine.
> >
> >I then installed GRUB on to the MBR.  Now, Linux will boot perfectly both
> > directly from the copy of GRUB on the MBR and by chain-loading the copy
> > of GRUB on the boot sector.  Windows, however, hangs while displaying the
> > initial, text-mode progress bar during the hardware detection phase of
> > its boot.  Windows is still bootable by using the copy of GRUB on the
> > floppy disk, but it will not boot from either the copy of GRUB on the MBR
> > or on the Linux boot sector, using exactly the same commands.
> >
> >My GRUB config file is:
> ># 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,1)
> >#          kernel /vmlinuz-version ro root=/dev/hda5
> >#          initrd /initrd-version.img
> >#boot=/dev/hda2
> >default=0
> >timeout=10
> >splashimage=(hd0,1)/grub/splash.xpm.gz
> >title Red Hat Linux (2.4.18-3)
> >        root (hd0,1)
> >        kernel /vmlinuz-2.4.18-3 ro root=/dev/hda5
> >        initrd /initrd-2.4.18-3.img
> >
> >And my device.map file is:
> ># this device map was generated by anaconda
> >(fd0)     /dev/fd0
> >(hd0)     /dev/hda
> >
> >If you need any more information, please inform me.
> >
> >Simon
> >
> >
> >_______________________________________________
> >Bug-grub mailing list
> >address@hidden
> >http://mail.gnu.org/mailman/listinfo/bug-grub





reply via email to

[Prev in Thread] Current Thread [Next in Thread]