On Tue, Jul 21, 2015 at 09:48:32PM +0100, Ian Campbell wrote: > > […] > > Long story short, I manually > > "manually" == with debootstrap from a host system or some other way? Yes, debootstrap from my amd64 laptop (second stage in a chroot with qemu-static). I also installed the kernel and flash-kernel in the chroot. I just deleted the /boot/extlinux directory and ran flash-kernel again in the booted system, but it still doesn't work. > > installed Debian Jessie (as well as linux-image-4.0.0-2-armmp and u > > -boot from u-boot-sunxi=2015.04+dfsg1-2) on an > > A20-OLinuXino-LIME2 from Olimex but couldn't get it to boot (even with the > > boot.scr created by flash-kernel when invoked in a chroot with > > “FK_MACHINE="Olimex A20-OLinuXino-LIME2" flash-kernel”) until I created the > > simple /boot/extlinux/extlinux.conf file attached. > > This is a bug, the boot.scr method is expected to work and should be > supported for this system, since there is a db entry. If it is broken > we'd like to know the details of how please, including full logs if > possible. It appears to load the kernel, and then nothing happens anymore, the screen is black and everything appears dead. I have not tried accessing it through the serial console as I don't have the required hardware (that is the reason why I haven't used d-i in the first place, as it lacks display support). > > I'm not sure whether flash-kernel is the correct package to implement this > > feature, but there should be a way to automaticaly generate such files. > > The extlinux packages support generating these files, that support just > needs to be split out and made non-x86 specific I think. > > That support shouldn't be duplicated in flash-kernel. Ok, seems sensible. The dtb file is currently selected by flash-kernel, though.
Attachment:
signature.asc
Description: Digital signature