Control: notfound -1 yaboot-installer/1.1.26 On 07/21/2013 04:55 PM, Ben Hutchings wrote:
Control: reassign -1 yaboot-installer 1.1.26 On Mon, 2013-07-22 at 00:38 +0400, Pavel Fedin wrote: [...]So, it's not kernel's fault. It seems to be installer fault which does not generate correct vmlinuz image when not using separate /boot partition. vmlinux, i know, is another thing. It's a "plain" image meant to be ran from GRUB or yaboot. It cannot be run from OFW. So, we can close this, probably with a notification to Installer guys.There is no need to close it. I'm reassigning to the relevant part of the installer.
The particular partition/file-system layout reported in this bug report cannot work.
This platform does not have a boot loader at all. Firmware knows how to load kernel directly from affs1, ext2 or older implementations of ext3 file systems. It is possible to tweak options while creating ext3 with current tools to make it work, but it is not worth the trouble.
In practice this means you have to have ext2 boot partition, to place the kernel onto, for this machine to boot.
Installer correctly creates ext2 boot partition and ext4 root partition. The identical mkinitramfs and mkvmlinuz commands are issued during installation as those during kernel upgrades. The generated vmlinuz loads and kernel works fine.
Closing this bug report. This is not a bug. Milan