Developer Forum

replaced Suse 10.2 with Ubuntu Intrepid on my secondary office box,
which I also use to run XP when necessary. while the Grub which Suse
installed did a good job setting up, Ubuntu not so much -- it could
boot all the available Ubuntu kernels, but when XP was selected, would
hang. I must have tried a dozen different combinations of drive
assignments without success.

finally, thanks to Super Grub Disk (a remarkable tool for getting
through just these sorts of problems, highly recommended) I got back
to XP's bootloader, and can use the SGD CD to boot Ubuntu.

I've asked on the SGD and Ubuntu forums, but am just curious if any
experts here would want to hazard suggestions how I should edit my
menu.lst to be able to boot XP, as well as Boot Manager.

by the way: I decided to try Intrepid after getting a little eeePC
1000 a month or so ago -- the same one, I think, that's shown in that
video running eCS. it's very nice, I must say -- apart from being
pleasing to my eye, Synaptic is head and shoulders above anything I
ever used in any of the Suse distros I tried. one of the nifty things
about this eee PC is its ability to boot from a little SD(HC) card.
one thing I would actually pay money for is one of these babies
formatted with eCS to suit the eee.

here is how SGD describes my disk layout. I have a feeling that
somehow the SCSI drive assignment and/or Boot Manager is what confused
Grub, but I have a hard enough time figuring out Unix drive
assignments much less understanding how Grub talks to the BIOS.
(incidentally, notice hda2, where eCS may someday live).

N IDE SCSI FGRUB HURD TYPE SIZE OS
1 hda1 sda1 (hd0,0) hd0s1 Uknown 7MB
2 hda2 sda2 (hd0,1) hd0s2 HPFS.NTFS 2GB WINDOWS
3 hda3 sda3 (hd0,2) hdos3 Uknown 1004 MB
5 hda5 sda5 (hd0,4) hdos5 HPFS/NTFS 7GB WINDOWS
6 hda6 sda6 (hd0,5) hdos6 HPFS/NTFS 9GB WINDOWS
7 hda7 sda7 (hd0,6) hdos7 HPFS/NTFS 14GB WINDOWS
8 hda8 sda8 (hd0,7) hdos8 SWAP 1GB
9 hda9 sda9 (hd0,8) hdos9 SWAP 2GB
10 hda10 sda10 (hd0,9) hdos10 ext2fs 11GB Ubuntu 8.10 \n \l
11 hda11 sda11 (hd0,10) hdos11 ext2fs 17GB

& here is menu.lst

title Ubuntu 8.10, kernel 2.6.27-11-generic
uuid 7b2666ae-c50a-4e66-89bf-7ee746b0d57b
kernel /boot/vmlinuz-2.6.27-11-generic root=UUID=7b2666ae-
c50a-4e66-89bf-7ee746b0d57b ro quiet splash
initrd /boot/initrd.img-2.6.27-11-generic
quiet

title Ubuntu 8.10, kernel 2.6.27-11-generic (recovery mode)
uuid 7b2666ae-c50a-4e66-89bf-7ee746b0d57b
kernel /boot/vmlinuz-2.6.27-11-generic root=UUID=7b2666ae-
c50a-4e66-89bf-7ee746b0d57b ro single
initrd /boot/initrd.img-2.6.27-11-generic

title Ubuntu 8.10, kernel 2.6.27-7-generic
uuid 7b2666ae-c50a-4e66-89bf-7ee746b0d57b
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=7b2666ae-
c50a-4e66-89bf-7ee746b0d57b ro quiet splash
initrd /boot/initrd.img-2.6.27-7-generic
quiet

title Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
uuid 7b2666ae-c50a-4e66-89bf-7ee746b0d57b
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=7b2666ae-
c50a-4e66-89bf-7ee746b0d57b ro single
initrd /boot/initrd.img-2.6.27-7-generic

title Ubuntu 8.10, memtest86+
uuid 7b2666ae-c50a-4e66-89bf-7ee746b0d57b
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below fr

It's been quite a while since I played with Linux, but GRUB should go
into /boot or / [root], not the MBR. This worked for me with SUSE 8.2
and RH 8 (each had it's own GRUB in / [root] as I recall), and GRUB gave
a second route to the same XP installation. Can't remember whether it
was necessary to add XP and/or OS/2 manually to each GRUB menu or not.
In any case, if you have BM (or AirBoot), GRUB shouldn't be allowed to
make any changes to the MBR nor BM partition. LILO isn't recommended for
this type of set-up.

HTH,
Pete

--

On Feb 10, 2:45 am, "Pete" <khadhargo@sbc...nospam.-.global.net>



well after three or four failed attempts in the past, I've finally
learned to put Grub in /. this time I think it's Grub's fault!

guess I could get another bootloader -- I used to use Veit
Kannegeiser's Vpart, and I suppose I might try it again -- but I can't
believe that this isn't soluble.

suspect what is going on here is Ubuntu was confused about Boot
Manager and/or the SCSI drive assignments. I think it's just a matter
of filling in the right partition assignments and maps.

n 02/10/09 07:23 am, rafe wrote:

The basic Ubuntu disk insists on putting grub in the MBR. I believe the
alternate install disk allows putting grub in root or /boot.
Also I've always had to add the bootmanager to grub with Ubuntu (even
filed a bug about it, they closed it as cosmetic, won't fix)
with chainloader +1.

> # This entry automatically added by the
> Debian installer for a non-
> linux OS
> # on /dev/sdd2
> title Windows XP Media Center Edition
> root (hd0,1)
> chainloader +1
> map (hd0) (hd1)
> map (hd1) (hd0)

Don't these two lines that start with map swapping your hard drives?
Perhaps that is the problem?
If you can get BootManager working you can always go there to boot XP
Dave

FYI my grub has (windows on drive C:)
root (hd0,1)
savedefault
makeactive
chainloader +1

and for BootManager
root (hd0, 0)
makeactive
chainloader +1

Dave

thanks, Dave, I'll see about playing around with this.

I should have noted the unsuccessful values I used, though I can
somewhat remember them. if I can't get Grub to work, odds are I'll
switch to Vpart or Airboot or something -- reworking Boot Manager was
my first thought at the time, and so when I was looking at the disk in
DFSEE, I added XP to the menu, but for some reason, when I got into
boot manager on the next boot, it wouldn't start XP. another problem
is, believe it or not, in all these years I've managed to avoid LVM,
so I suspect this would be an issue trying to start Grub from BM.

I wish there was a bit better response on the Ubuntu forums about
this, but maybe SCSI disks have become *** .

You can start GRUB from BM. The trick (and probably how you should do it
anyways) is to use OS/2 fdisk to do all partitioning, add it to BM. Then
when installing Linux just use the Linux fdisk to change the partition
type, not create a partition.
Dave

On 2002/08/2009 10:00 (GMT-0800) rafe composed:


If you have BM on the system, it's easiest to use it to boot everything. You
can use Grub to boot XP, BM & Linux, but BM is just too much simpler.

XP's NTLDR.EXE is a boot manager, and can boot Grub, and I suppose BM as
well: http://www.yqcomputer.com/
--
"Do not let any unwholesome talk come out of your
mouths, but only what is helpful for building
others up." Ephesians 4:29 NIV

Team OS/2 ** Reg. Linux User #211409

Felix Miata *** http://www.yqcomputer.com/