Another Vista-Windows 7-Ubuntu can't boot to Ubuntu

IMNemo

New Member
#1
I have read all of the WIKI EasyBCD literature, search these forums, but so far I have been unable to multi-Boot to Ubuntu.

Please help
:tongueout:
======================

I have an HP Pavilion 9020 Laptop with 2 SATA drives.
I am using EasyBCD 2.0.0.60 Beta.

I have Windows Vista Ultimate on (SATA Drive 0, Partition 1) drive C
I have Windows 7 Ultimate BETA on (SATA Drive 0, Partition 2) drive D

I have installed Ubuntu 9.04 Beta on SATA Drive 1,
Partition 1 (Linux - 292 GB)
Partition 2 (Swap - 6 GB)
GRUB was installed to Partition 1 (Linux - 292GB)

=================================

ALL OF THIS IS DONE IN Windows Vista Ultimate

In EasyBCD I added a Linux entry:
Type: Grub
Name: Ubuntu 9.04 Beta
Device: Partition 1 (Linux - 292 GB)

GRUB isn't installed to MBR/bootsector <is checked>

I saved it and goto the next step;

OK, when you select "EasyBCD > View Settings" you see below what it says.



There are a total of 3 entries listed in the bootloader.

Default: Windows Vista Ultimate
Timeout: 30 seconds.
Boot Drive: C:\

Entry #1
Name: Windows Vista Ultimate
BCD ID: {current}
Drive: C:\
Bootloader Path: \Windows\system32\winload.exe

Entry #2
Name: Windows 7 Ultimate
BCD ID: {a1e65204-c47e-11dc-8f20-001b2400ba27}
Drive: D:\
Bootloader Path: \Windows\system32\winload.exe

Entry #3
Name: Ubuntu 9.04 Beta
BCD ID: {a1e6521b-c47e-11dc-8f20-001b2400ba27}
Drive: C:\
Bootloader Path: \NST\NeoGrub.mbr

=================================

Now, if you go to C:/NST/menu.lst this is what you will see.

# NeoSmart NeoGrub Bootloader Configuration File
#
# This is the NeoGrub configuration file, and should be located at C:\NST\menu.lst
# Please see the EasyBCD Documentation for information on how to create/modify entries:
# EasyBCD Documentation Home - NeoSmart Technologies Wiki


find --set-root --ignore-floppies /boot/grub/menu.lst
configfile /boot/grub/menu.lst

# All your boot are belong to NeoSmart!

=================================

ALL OF THIS IS DONE IN Ubuntu 9.04 Beta

I opened a terminal window, I did the command "sudo fdisk -l"

Here are the results:


To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x360a8e83

Device Boot Start End Blocks Id System
/dev/sda1 * 1 19462 156328416+ 7 HPFS/NTFS
/dev/sda2 19463 38914 156241350 7 HPFS/NTFS

Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x808ca26a

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 38162 306536233+ 83 Linux
/dev/sdb2 38163 38913 6032407+ 5 Extended
/dev/sdb5 38163 38913 6032376 82 Linux swap / Solaris

Disk /dev/sdc: 16.0 GB, 16010838016 bytes
112 heads, 48 sectors/track, 5816 cylinders
Units = cylinders of 5376 * 512 = 2752512 bytes
Disk identifier: 0xd6b0d667

Device Boot Start End Blocks Id System
/dev/sdc1 2 5817 15631552 c W95 FAT32 (LBA)

Disk /dev/sdd: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x06525480

Device Boot Start End Blocks Id System
/dev/sdd1 1 38913 312568641 7 HPFS/NTFS

Disk /dev/sde: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x229651ed

Device Boot Start End Blocks Id System
/dev/sde1 1 38913 312568641 7 HPFS/NTFS
ubuntu@ubuntu:~$

=================================

I opened /Boot/Grub/menu.lst

Here are the results:

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=93b0238a-2bae-44f9-87d7-3129ed2ffe3d ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=93b0238a-2bae-44f9-87d7-3129ed2ffe3d

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
## indomU=true
## indomU=false
# indomU=detect

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title Ubuntu jaunty (development branch), kernel 2.6.28-11-generic
uuid 93b0238a-2bae-44f9-87d7-3129ed2ffe3d
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=93b0238a-2bae-44f9-87d7-3129ed2ffe3d ro quiet splash
initrd /boot/initrd.img-2.6.28-11-generic
quiet

title Ubuntu jaunty (development branch), kernel 2.6.28-11-generic (recovery mode)
uuid 93b0238a-2bae-44f9-87d7-3129ed2ffe3d
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=93b0238a-2bae-44f9-87d7-3129ed2ffe3d ro single
initrd /boot/initrd.img-2.6.28-11-generic

title Ubuntu jaunty (development branch), memtest86+
uuid 93b0238a-2bae-44f9-87d7-3129ed2ffe3d
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Windows Vista (loader)
rootnoverify (hd0,0)
savedefault
chainloader +1

=================================

Ok, when I re-boot I do get a menu showing 3 items (not the exact wording, but you get the idea)
(1) Windows Vista
(2) Windows 7
(3) Ubuntu 9.04 Beta

Select either Vista or 7 ands both boot OK.

Select Ubuntu and here is what the final window says (can't get the first window as it is just to fast)

GRUN4DOS 0.4.4 2009-01-27
Memory: 638K/2045M
Menu End: 0x465CA

[Minimal BASH-Like line editing is supported. For the first word, TAB lists possible commands]

grub>

It just stops there and I don't know how to go further.

Can you help? I'm at the end of my rope.
 
#2
Hi imnemo, welcome to NST.
It is unclear at this time whether our software works with 9.04 (Jaunty) beta release of Ubuntu. Though it may, we have no one here who has personally tested it as of yet, to see if it works with EasyBCD.
No doubt we will keep you posted of any further developments in that regard, though, or confirmation that it indeed works once (and if) someone here tests it successfully. :wink:

Regards,

Jake
 
Last edited:

IMNemo

New Member
#3
Ok, but what I didn't put in the original info was that it does this (exactly the same behavior) with Ubuntu 8.10. It acts exactly the same.

I didn't include this cause I didn't realize that you might not support Ubuntu 9.04, sorry
 

JustinW

Super Moderator
Staff member
#4
IANemo, replace the uuid lines with "root (hdx,y)" where x is disk and y is partition. Are you using the latest build of EasyBCD 2.0 Beta? If not, get it from [thread=642]here[/thread].
 
#5
He said in the first post, Justin, that he's using Build 60 of EasyBCD beta, which supports UUID lines.

EDIT: Of course if there was a problem with the UUID code, then it may be better to use "root (hdx,y)" lines instead, indeed...

Addendum:

Everything looks ok from a technical standpoint alone, imnemo. As far as I can tell from all the posted info, you did everything correct, but its still not working for some reason. Now, it seems to me the problem must be either NeoGrub is not reading (at least correctly) the menu.lst on the Ubuntu partition, or there is something in your Ubuntu menu.lst that is not working with NeoGrub (wrong UUID code, for instance...). Seeing as you didn't get any errors per se when attempting to boot into Ubuntu from the Vista boot menu, but just got to that Grub prompt, the problem seems to me to be with NeoGrub, and the Ubuntu menu.lst. For some reason, they are not playing together very nicely. :wink: Have you tried removing, and then installing again, NeoGrub (under the NeoGrub tab in EasyBCD's Add/Remove Entries section)? Perhaps re-adding the Linux entry after doing that will help.
 
Last edited:

IMNemo

New Member
#6
I have tried to do as you suggested (replace UUID with root (hdx,y)) but unbuntu says I don't have the rights. I'm just a novicew with Linux, main reason I want to multi-boot. So I really don't know where to go from here. I hate to be a pest, but could you help?

Addendum:

Oh, I forgot in my previous message. I did delete NeoGrub, and reinstall the Linux to the Linux partition. No effect, still goes to Grub.
 
Last edited:

Terry60

Knows where his towel is.
Staff member
#7
First time I tried to edit menu.lst in Ubuntu, it said I didn't have rights, and I thought "I'm the only bl**dy user, who else has got them ? "
Later on in the session, I did something which asked me for my user password for authorization (can't remember what now), and having given it for that purpose, I wen't back to menu.lst on a hunch, and sure enough it let me do the edit which it previously vetoed.
So try it again and see if you can complete the edit.
 
#8
I have tried to do as you suggested (replace UUID with root (hdx,y)) but unbuntu says I don't have the rights. I'm just a novicew with Linux, main reason I want to multi-boot. So I really don't know where to go from here. I hate to be a pest, but could you help?
You will need to be a "root" user before you will be able to save the changes you make to your menu.lst. :wink: Open up the Terminal (Applications>Accessories>Terminal), and run the following command:

Code:
gksu nautilus
That will open up a file browser as root, and then you just simply browse to the menu.lst, open it up, make your changes, and then save it, which it will now allow you to do. :smile:

Cheers,

Jake
 

IMNemo

New Member
#9
I opened the terminal you told me about. I typed in the command and below is the results

==================================

ubuntu@ubuntu:~$ gksu natilus

/usr/share/themes/Human/gtk-2.0/gtkrc:82: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/usr/share/themes/Human/gtk-2.0/gtkrc:83: Murrine configuration option "lightborder_ratio" will be deprecated in future releases. Please use "lightborder_shade" instead.
/usr/share/themes/Human/gtk-2.0/gtkrc:194: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.

>>>>>> at this point the cursor is just sitting there for 3 - 4 seconds, then it gives the below responce.

ubuntu@ubuntu:~$


==================================
I have tried this several times, always the same responce. No file browser opens up, nothing happens. I opened up a file browser and checked to make sure it was Natilus and it was. I think my PC is possessed.

What now? I really do appreciate all the help you are giving me.
 
#10
Code:
gksu [B]nautilus[/B]
not

Code:
gksu [B]natilus[/B]
 
#12
OK, I finally got it to work. I copied the menu.lst that I modified and replaced the original in /boot/grub/menu.lst.

I rebooted, selected Ubuntu from the menu, and it still went to grub>
=================================
I'm including the menu.lst I used so you can tell me if I did it right.

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=93b0238a-2bae-44f9-87d7-3129ed2ffe3d ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=93b0238a-2bae-44f9-87d7-3129ed2ffe3d

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
## indomU=true
## indomU=false
# indomU=detect

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

## 06:02 Sunday, 2009/03/29
## replaced UUID with "root (hdb, 1) as suggested in NeoTech forum responce

title Ubuntu jaunty (development branch), kernel 2.6.28-11-generic
root (hdb,1)
# uuid 93b0238a-2bae-44f9-87d7-3129ed2ffe3d
kernel /boot/vmlinuz-2.6.28-11-generic root=root (hdb,1) ro quiet splash
# kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=93b0238a-2bae-44f9-87d7-3129ed2ffe3d ro quiet splash
initrd /boot/initrd.img-2.6.28-11-generic
quiet

title Ubuntu jaunty (development branch), kernel 2.6.28-11-generic (recovery mode)
root (hdb,1)
# uuid 93b0238a-2bae-44f9-87d7-3129ed2ffe3d
kernel /boot/vmlinuz-2.6.28-11-generic root=root (hdb,1) ro single
# kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=93b0238a-2bae-44f9-87d7-3129ed2ffe3d ro single
initrd /boot/initrd.img-2.6.28-11-generic

title Ubuntu jaunty (development branch), memtest86+
root (hdb,1)
# uuid 93b0238a-2bae-44f9-87d7-3129ed2ffe3d
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST
root (hdb,1)
# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Windows Vista (loader)
rootnoverify (hd0,0)
savedefault
chainloader +1

=====================================================

Thanks again for your help
 
#13
## ## End Default Options ##

## 06:02 Sunday, 2009/03/29
## replaced UUID with "root (hdb, 1) as suggested in NeoTech forum responce

title Ubuntu jaunty (development branch), kernel 2.6.28-11-generic
root (hdb,1)
# uuid 93b0238a-2bae-44f9-87d7-3129ed2ffe3d
kernel /boot/vmlinuz-2.6.28-11-generic root=root (hdb,1) ro quiet splash
# kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=93b0238a-2bae-44f9-87d7-3129ed2ffe3d ro quiet splash
initrd /boot/initrd.img-2.6.28-11-generic
quiet

title Ubuntu jaunty (development branch), kernel 2.6.28-11-generic (recovery mode)
root (hdb,1)
# uuid 93b0238a-2bae-44f9-87d7-3129ed2ffe3d
kernel /boot/vmlinuz-2.6.28-11-generic root=root (hdb,1) ro single
# kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=93b0238a-2bae-44f9-87d7-3129ed2ffe3d ro single
initrd /boot/initrd.img-2.6.28-11-generic

title Ubuntu jaunty (development branch), memtest86+
root (hdb,1)
# uuid 93b0238a-2bae-44f9-87d7-3129ed2ffe3d
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST
Not "hdb,1". You need to use "(hd1,0)" in the "root" lines of your menu.lst if that's where your Ubuntu partition is located (which according to the fdisk info you posted, it is). :wink: You also need to remove the kernel lines that you added, and uncomment the ones that were previously used. Its ok having the UUID code in the kernel lines.
 
Last edited:
#14
Ok, first let me say OOps on the typo's. An Thanks for your patience with me and your help.

I have cut and pasted the NEW /boot/grub/menu.lst

Unfortunately when I reboot and go to the menu,, select Ubuntu, it still goes to grub>

What now, hopefully I have edited menu.lst as you suggested.

Thanks
========================
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=93b0238a-2bae-44f9-87d7-3129ed2ffe3d ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=93b0238a-2bae-44f9-87d7-3129ed2ffe3d

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
## indomU=true
## indomU=false
# indomU=detect

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title Ubuntu jaunty (development branch), kernel 2.6.28-11-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=93b0238a-2bae-44f9-87d7-3129ed2ffe3d ro quiet splash
initrd /boot/initrd.img-2.6.28-11-generic
quiet

title Ubuntu jaunty (development branch), kernel 2.6.28-11-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=93b0238a-2bae-44f9-87d7-3129ed2ffe3d ro single
initrd /boot/initrd.img-2.6.28-11-generic

title Ubuntu jaunty (development branch), memtest86+
root (hd1,0)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Windows Vista (loader)
rootnoverify (hd0,0)
savedefault
chainloader +1
 
#15
Oh, I forgot in my previous message. I did delete NeoGrub, and reinstall the Linux to the Linux partition. No effect, still goes to Grub.
When you said you "reinstalled Linux", did you mean you did just that?!! That is not what I was suggesting in my other post. :wink: I meant to uninstall, and then reinstall, NeoGrub...not Linux. Ok, so when you reinstalled Linux, did you make sure you reinstalled it to the same partition, i.e. sdb1? And did you select the "Advanced" option, and make sure to type in the location of "/dev/sda1" as where to install Grub to?

Try adding a new entry to boot Linux under the Linux tab in EasyBCD, with the "Grub is not installed..." box checked again, and the correct drive and partition selected in the Devices menu (should be shown as Drive 1, Partition 1). And if that doesn't work, try adding a new entry with that box unchecked, and see if you get any better results.

BTW, your Ubuntu menu.lst is now configured correctly (at least for your previous install of Linux anyway...if you installed Linux somewhere else the second time, then obviously, it would not be correct).

Jake
 
#16
I did not re-install "Ubuntu Linux" program, just the EasyBCD portion.. The "Ubuntu Linux" program installation is just as it was.

What I meant was in EasyBCD, I un-installed "NeoGrub" under the Add/Remove Entries "NeoGrub" tab, and then added a new "Linux" entry under the "Linux" tab. When I re-installed the Linux entry in EasyBCD I did check the "GRUB isn't installed .." box.

Sorry I didn't make it clear. After re-reading my post to you I see how it would confuse.

I will re-boot now and see the results. If it doesn't work, I'll try the option of not checking the "GRUB isn't installed" box.

Hopefully this will be the fix.
 
#17
Ok, thanks for the clarification. Now, I have another question...:wink: In the first post, you said you installed Grub to partition 1. I'm assuming by that you mean you selected the "Advanced" option when installing Ubuntu, and typed in the location of "/dev/sdb1" without the quotes?
 
Last edited:
#18
Under the "Advanced" option (during the Ubuntu Linux install), it would have been the "sdb" Linux drive, the first partition (If I am understanding how Linux does the numbering. That should be drive "1" partition "0" I think)

In EasyBCD it is listed as Drive 1, Partition 1 (Linux 292GB) under the "Linux" tab.

By the way these are the results of your previous suggestion.

(1) with the "GRUB isn't installed ..." box checked. Re-Boot, Select Ubuntu, and it goes to the same screen:
====================================================================
GRUN4DOS 0.4.4 2009-01-27 Memory: 638K/2045M Menu End: 0x465CA
[Minimal BASH-Like line editing is supported. For the first word, TAB lists possible commands]

grub>
====================================================================

(2) with the "GRUB isn't installed ..." box NOT checked. Re-Boot, Select Ubuntu, and it goes to a different screen
====================================================================
GRUB


====================================================================
It goes straight to this black screen with "GRUB" at the top of the screen with the cursor line just blinking and the PC is locked up, the keyboard does not respond, I had to hit the power on/off button and to then re-boot.

It's different, but no cigar.
 
#19
Under the "Advanced" option (during the Ubuntu Linux install), it would have been the "sdb" Linux drive, the first partition (If I am understanding how Linux does the numbering. That should be drive "1" partition "0" I think)
Oops. You're right, my bad. :wink: Edited last post. It was a typo. It is indeed "sdb" that is the drive you have needed to install Grub to, but the partition value would have "1" though because the count for that notation begins at "1" not "0". :smile: So if you typed in the location of "/dev/sdb0", that would have of course been wrong, and most likely Grub would have either been not installed at all, or would have defaulted to installing to the MBR instead.

Well, like I mentioned in my first post, no one here has personally tested Jaunty with EasyBCD yet, and so we don't know yet if it works or not. You would also do good to keep in mind the version is still in beta build, so its quite possible there are quite a few bugs still remaining. :wink: Meaning you would do better to use the bootloader they recommend (i.e. Grub) for controlling the boot this time around, instead of using the Vista bootloader to chain to Grub. No doubt you will probably have less trouble and more peace of mind doing that then to struggle getting it to work with EasyBCD. Our software was not intended to work with OSes still in beta build, and so we can't be held responsible if they fail to.

Cheers,

Jake
 
Last edited: