PDA

View Full Version : [ubuntu] Ubuntu 9.10/Windows dual boot problem



outerspaceguy
January 19th, 2010, 03:15 AM
I tried to set up a dual boot system on two separate hard drives. I installed Windows XP first (because doing so in past experience has made it easier) on the PATA 20 GB hard drive configured as slave on the first IDE channel. Then I installed Ubuntu 9.10 on the PATA 80 GB hard drive configured as master on the first IDE channel along with an NTFS partition on this drive:



sudo fdisk -l
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x494ccaeb

Device Boot Start End Blocks Id System
/dev/sda1 * 1 3404 27342598+ 83 Linux
/dev/sda2 3405 3653 2000092+ 5 Extended
/dev/sda3 3654 9729 48805470 7 HPFS/NTFS
/dev/sda5 3405 3653 2000061 82 Linux swap / Solaris

Disk /dev/sdb: 20.0 GB, 20020396032 bytes
255 heads, 63 sectors/track, 2434 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x14dffdcf

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 2433 19543041 7 HPFS/NTFS


Grub seems to be set up properly with an entry in the menu on boot-up for Windows XP, however this message appears when I try to start Windows and I'm unable to start it:


Windows NT has found only 510k of low memory. 512k of low memory is required to run Windows NT. You may need to upgrade your computer or run a configuration program provided by the manufacturer.

I tried running update-grub2 again however the problem persists. If I switch my BIOS to boot the slave drive instead, Windows will boot normally without any issues without Grub coming up, as expected. I have to switch my BIOS back again to get to the Grub menu and start Ubuntu. Is there a problem with the way Grub is configured? My /boot/grub/grub.cfg looks like this (did not modify, this is what was automatically generated):



cat /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
saved_entry=${prev_saved_entry}
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 7d414b48-3c0f-4670-8921-783e02778e1c
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-17-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 7d414b48-3c0f-4670-8921-783e02778e1c
linux /boot/vmlinuz-2.6.31-17-generic root=UUID=7d414b48-3c0f-4670-8921-783e02778e1c ro quiet splash
initrd /boot/initrd.img-2.6.31-17-generic
}
menuentry "Ubuntu, Linux 2.6.31-17-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 7d414b48-3c0f-4670-8921-783e02778e1c
linux /boot/vmlinuz-2.6.31-17-generic root=UUID=7d414b48-3c0f-4670-8921-783e02778e1c ro single
initrd /boot/initrd.img-2.6.31-17-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 7d414b48-3c0f-4670-8921-783e02778e1c
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=7d414b48-3c0f-4670-8921-783e02778e1c ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 7d414b48-3c0f-4670-8921-783e02778e1c
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=7d414b48-3c0f-4670-8921-783e02778e1c ro single
initrd /boot/initrd.img-2.6.31-14-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Microsoft Windows XP Professional (on /dev/sdb1)" {
insmod ntfs
set root=(hd1,1)
search --no-floppy --fs-uuid --set be882d55882d0e09
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###


Thanks for any help!

lidex
January 19th, 2010, 04:05 AM
I think windows wants to be sda1.

outerspaceguy
January 20th, 2010, 12:32 AM
I think windows wants to be sda1.

I tried that but same effect.


sudo fdisk -l

Disk /dev/sda: 20.0 GB, 20020396032 bytes
255 heads, 63 sectors/track, 2434 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x14dffdcf

Device Boot Start End Blocks Id System
/dev/sda1 * 1 2433 19543041 7 HPFS/NTFS

Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x494ccaeb

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 3404 27342598+ 83 Linux
/dev/sdb2 3405 3653 2000092+ 5 Extended
/dev/sdb3 3654 9729 48805470 7 HPFS/NTFS
/dev/sdb5 3405 3653 2000061 82 Linux swap / Solaris

darkod
January 20th, 2010, 12:15 PM
The message you are getting is about memory. What has that got to do with your hdds and their order?

It's complaining about not enough memory to run windows.

outerspaceguy
January 20th, 2010, 01:42 PM
The message you are getting is about memory. What has that got to do with your hdds and their order?

It's complaining about not enough memory to run windows.

Like I noted in my first post, Windows runs boots fine if I switch my BIOS to boot from that hard drive. The problem only exists when Grub attempts to chainload it. Perhaps Grub is taking up too much low memory or not freeing some? Note the distinction "low memory". The system has 1.5 GB installed. Or do I need to change some configuration to increase it?

I swapped the positions of the hard drives to try lidex's suggestion which was to make Windows on /dev/sda1.