[Bug 262584] Re: Intrepid LiveCD installer didn't set up boot files correctly

[Launchpad Bug Tracker]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ubiquity (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/262584

Title:
  Intrepid LiveCD installer didn't set up boot files correctly

Status in “ubiquity” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: ubiquity

  I have Ubuntu Hardy, Win-Vista and Gentoo all on a multi-boot system
  using Grub. /boot is a separate small ext2 partition.

  When I installed Intrepid Kubuntu Alpha 4 from LiveCD on a separate
  (ext3) partition, it completed successfully. But the system wouldn't
  boot. The former menu.lst had been wiped out without saving any backup
  copy that I could see (but I'm used to Ubuntu installs doing that).
  The new entries pointed to initrd.img-2.6.26-5-generic and to
  vmlinuz-2.6.24-19-generic. (There are also symbolic links to these two
  files in the root folder.) vmlinuz-2.6.26-5-generic does not exist on
  the /boot partition (nor could I find it anywhere else). However,
  there is a file vmcoreinfo-2.6.26-5-generic on /boot.

  Surely it's not correct to try to boot from vmlinuz and initrd files
  mixed from different Ubuntu versions? I tried reinstalling from the
  LiveCD again but the same problem. This seems weird. (I could fix up
  menu.lst if I could work out where to find a copy of vmlinuz-2.6.26-5
  to copy onto my /boot partition.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/262584/+subscriptions