Bug#793157: flash-kernel: syslinux-style boot configuration on recent u-boot versions
On 2015-07-21, Thibaut Girka wrote: syslinux-style /boot/extlinux/extlinux.conf superseed boot.scr in recent u-boot versions and seems to be the way forward for u-boot configuration, but I couldn't find anything to automatically generate them in Debian. ... 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. menu title LIME2 boot menu timeout 10 ontimeout linux LABEL linux KERNEL /boot/vmlinuz-4.0.0-2-armmp INITRD /boot/initrd.img-4.0.0-2-armmp fdt /boot/dtb-4.0.0-2-armmp append root=/dev/mmcblk0p1 ro rootwait I think I'll take a stab at writing this. It's fairly safe, as only machines that support it will use it, as long as it also generates the boot script as a fallback. I think the main downside is that it doesn't inherrit the console boot arguments... not sure exactly how to handle that. It also has the advantage of being able to specify multiple boot options (e.g. old kernel versions if the new kernel doesn't boot, alternate boot options, alternate consoles console=tty1 vs. console=ttyS0,115200). This would also be good to add to debian-installer... live well, vagrant signature.asc Description: PGP signature
Bug#793157: flash-kernel: syslinux-style boot configuration on recent u-boot versions
On Tue, 2015-07-21 at 23:09 +0200, Thibaut Girka wrote: 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). It's hard to say without logs but I suspect you are missing the contents of /etc/default/flash-kernel which according to your working extlinux.conf in your case should should contain: LINUX_KERNEL_CMDLINE=root=/dev/mmcblk0p1 ro rootwait This would normally be setup by d-i. You can either edit that file directly or dpkg-reconfigure -plow flash-kernel in the chroot. You might also be able to add console=tty there to override the default serial console. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793157: flash-kernel: syslinux-style boot configuration on recent u-boot versions
On Wed, Jul 22, 2015 at 08:44:44AM +0100, Ian Campbell wrote: […] It's hard to say without logs but I suspect you are missing the contents of /etc/default/flash-kernel which according to your working extlinux.conf in your case should should contain: LINUX_KERNEL_CMDLINE=root=/dev/mmcblk0p1 ro rootwait It indeed cointained only “LINUX_KERNEL_CMDLINE=quiet”. This would normally be setup by d-i. You can either edit that file directly or dpkg-reconfigure -plow flash-kernel in the chroot. You might also be able to add console=tty there to override the default serial console. Done, and it now boots fine using the boot.scr, thanks! signature.asc Description: Digital signature
Bug#793157: flash-kernel: syslinux-style boot configuration on recent u-boot versions
On Tue, 2015-07-21 at 22:02 +0200, Thibaut Girka wrote: Package: flash-kernel Severity: normal syslinux-style /boot/extlinux/extlinux.conf superseed boot.scr in recent u-boot versions and seems to be the way forward for u-boot configuration, It's an alternative, but boot.scr remains a valid option and is what we support in Jessie. but I couldn't find anything to automatically generate them in Debian. Long story short, I manually manually == with debootstrap from a host system or some other way? 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. 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. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793157: flash-kernel: syslinux-style boot configuration on recent u-boot versions
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. signature.asc Description: Digital signature
Bug#793157: flash-kernel: syslinux-style boot configuration on recent u-boot versions
Package: flash-kernel Severity: normal syslinux-style /boot/extlinux/extlinux.conf superseed boot.scr in recent u-boot versions and seems to be the way forward for u-boot configuration, but I couldn't find anything to automatically generate them in Debian. Long story short, I manually 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. 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. menu title LIME2 boot menu timeout 10 ontimeout linux LABEL linux KERNEL /boot/vmlinuz-4.0.0-2-armmp INITRD /boot/initrd.img-4.0.0-2-armmp fdt /boot/dtb-4.0.0-2-armmp append root=/dev/mmcblk0p1 ro rootwait
