/sbin/installkernel doesn't work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debianutils (Ubuntu) |
Invalid
|
Medium
|
Andy Whitcroft | ||
Lucid |
Won't Fix
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Invalid
|
Undecided
|
Unassigned | ||
Utopic |
Invalid
|
Undecided
|
Unassigned | ||
Vivid |
Invalid
|
Medium
|
Andy Whitcroft |
Bug Description
If I build a kernel (from kernel.org) and do a 'make install'
it runs /sbin/installkernel which doesn't work right on my system (fresh install
from CD).
Because of a couple of problems. First, the script expects that /boot/vmlinuz is
a symlink to the existing kernel (ditto for initrd), this is not how Ubuntu with
GRUB
is installed. Making the symlink made the script run, but there was no entry in
/boot/grub/menu.lst for the new kernel.
Second problem is that installkernel doesn't make and install initrd, as it does
on other distro's (Suse, Redhat). Since the default config depends on ext3 and other
drivers being in initrd, this prevents the new kernel from booting.
The whole process of installing a new kernel does work out of the box on Suse,
and Fedora.
Suse uses one entry in grub/menu.lst but makes new symlinks.
Fedora adds new entries in grub/menu.lst for each kernel built.
Changed in debianutils (Ubuntu): | |
assignee: | Charles Majola (chmj) → nobody |
assignee: | nobody → Andy Whitcroft (apw) |
Changed in debianutils (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | added: patch |
This has been fix as far as I know. If it still persists, please feel free to reopen the bug.