Bug#788221: flash-kernel: Cubietruck failed to boot with flash-kernel 3.41

[Karsten Merker <merker@debian.org>]

On Tue, Jun 09, 2015 at 10:12:13PM +0800, Zhang Jingqiang wrote:

> Package: flash-kernel
> Version: 3.41
> Severity: important
> 
> Dear Maintainers:
>     My cubietruck failed to boot with flash-kernel 3.41.
>     I didn't connect to its serial port to find the error message as it is not convenience, but if
> you really need that, I will find some time to unpack the box and check that.
>     I can not connect to bugs.debian.org for now, so sorry if this is a duplicate bug report.

The source of the problem appears to be the recent kvers ->
fk_kvers change in the boot scripts.  The actual load commands
have been changed to use fk_kvers instead of kvers, but in the
sunxi boot script the check for the availability of a kernel
image in the current pathprefix still references kvers.  This
causes the check to fail, so the script does not actually try to
execute the load commands.

Excerpt from the sunxi boot script:

for pathprefix in ${image_locations}
do
  if test -e ${device} ${partition} ${pathprefix}vmlinuz-${kvers}
                                                           ^^^^^^
  then
    load ${device} ${partition} ${kernel_addr_r} ${pathprefix}vmlinuz-${fk_kvers} \
    && load ${device} ${partition} ${fdt_addr_r} ${pathprefix}dtbs/${fk_kvers}/${fdtfile} \
    || load ${device} ${partition} ${fdt_addr_r} ${pathprefix}dtb-${fk_kvers} \
    && load ${device} ${partition} ${ramdisk_addr_r} ${pathprefix}initrd.img-${fk_kvers} \
    && echo "Booting Debian ${fk_kvers} from ${device} ${partition}..." \
    && bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}
  fi
done

I'll commit a fix tomorrow after some further testing.

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.