Grub 2 in Jaunty/Karmic can break double boot configuration

[NoOp]

On 10/04/2009 09:11 PM, Lucio M Nicolosi wrote:
> On Mon, Oct 5, 2009 at 12:14 AM, Goh Lip <snip> wrote:
...
>>
>> But, yes, I think it's better to change all instances to grub2.
>>
...
> 
> Thanks for your notes.
> 
> As reported, my Karmic installs went berserk and there was no grub2
> installed. So I had to install grub2 on jaunty to get things working.
> 
> Everything seems fine now, but I can't reproduce the problem because I
> do not have grub legacy installed anymore.
> 


The jaunty upgrade using:

To upgrade from Ubuntu 9.04 on a desktop system, press Alt+F2 and type
in "update-manager -d" (without the quotes) into the command box. Update
Manager should open up and tell you: New distribution release '9.10' is
available. Click Upgrade and follow the on-screen instructions.

went well, albeit slow:

 26 packages are going to be removed. 268 new packages are going to be
installed. 949 packages are going to be upgraded.
  You have to download a total of 659M. This download will take about 1
hour 40 minutes with your connection.

Overall took about 3 hours. grub 1 (0.97-29ubuntu56) is still installed,
but grub-common is now grub 2 (1.97~beta3-1ubuntu7). So, menu.lst is
still available & the drive is still ext3. Other OS (Ubuntu hardy 8.04)
on the second drive still boots without issues.

Not Grub 2 related:
Getting 'address space collision on of device [0xfc9c0000-0xfc9dffff]'
at startup w/kernel 2.6.31-11-generic.
https://bugs.launchpad.net/ubuntu/+bug/424142
[Address Collision]
But so far can't tell if that is actually affecting anything.