On Fri, Jun 22, 2012 at 08:30:30PM +0900, Itaru Kitayama wrote: > Hi Dann: > > Your Makefile in the make-highbank-ami package fails to execute flash-kernel: > > Cannot determine root device. Assuming /dev/hda1 > This error is probably caused by an invalid /etc/fstab > Searching for default file ... found: /boot/grub/default > Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst > Searching for splash image ... none found, skipping ... > Ignoring non-Xen Kernel on Xen domU host: vmlinuz-3.2.0-25-highbank > Updating /boot/grub/menu.lst ... done > > run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel > 3.2.0-25-highbank /boot/vmlinuz-3.2.0-25-highbank > Generating kernel u-boot image... done. > Creating new /boot/uImage. > Generating initrd u-boot image... done. > Creating new /boot/uInitrd. > run-parts: /etc/kernel/postinst.d/zz-flash-kernel exited with return code 1 > Failed to process /etc/kernel/postinst.d at > /var/lib/dpkg/info/linux-image-3.2.0-25-highbank.postinst line 1010. > dpkg: error processing linux-image-3.2.0-25-highbank (--configure): > subprocess installed post-installation script returned error exit status 2 > No apport report written because MaxReports is reached already > dpkg: dependency problems prevent configuration of linux-image-highbank: > linux-image-highbank depends on linux-image-3.2.0-25-highbank; however: > Package linux-image-3.2.0-25-highbank is not configured yet. > dpkg: error processing linux-image-highbank (--configure): > dependency problems - leaving unconfigured > No apport report written because MaxReports is reached already > Errors were encountered while processing: > linux-image-3.2.0-25-highbank > linux-image-highbank > E: Sub-process /usr/bin/dpkg returned an error code (1) > make: *** [u-boot.bin] Error 100
I don't know what causes this specific issue - but that's because I haven't (yet) switched to using the official Ubuntu bits... see below... > Any ideas why this happens? In the Makefile above, I am skipping using > the private PPA as I don't know how to > access. Apologies for the late reply. I was hoping to have good news for you when I did reply (i.e., an easy-to-follow-recipe), but I don't have that yet - been working on some other things. I can say that make-highbank-ami works fine w/ the bits in the PPA - the PPA is private, but there's nothing s3kr1t about the bits I use from there - so I've posted them here: http://people.canonical.com/~dannf/highbank-qemu/ I know of a couple architectural differences between these bits and what went into the distro: The qemu-highbank package here is based on Calxeda's QEMU tree. Since then the highbank support has gone upstream. That means, the official Ubuntu QEMU packages *should* be usable with one caveat. My understanding is that the upstream QEMU will require the kernel to be loaded from the host system, whereas my AMI build system expects to load it from a QEMU disk image (nicer for my use case because then users can upgrade the kernel & reboot). Also, my kernel image installs a device tree file, which we load into memory before booting the kernel in QEMU. I don't think the Ubuntu highbank images include this file, as that data is embedded on real hardware. I don't know if upstream-highbank-QEMU has device tree data pre-loaded into memory or not. I plan to switch make-highbank-ami over to use official Ubuntu bits - once I get that working I'll post a recipe somewhere. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
