Intrepid LiveCD installer didn't set up boot files correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
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.
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.)
Gave the same problem on Alpha 5 (except with 2.6.27-2. I still haven't been able to install Intrepid (64-bit). It only puts the initrd on /boot plus a vmcoreinfo file, but not the vmlinuz file.
When I changed menu.lst to boot from the Hardy kernel (2.6.24-19), I can boot Kubuntu. But if I try to mount /boot, I get "unknown ext2 filesystem". If I try to mount the CD, I get "unknown ISo9660 filesystem". So I haven't found a way to manual get the Intrepid kernel onto my /boot partition yet.