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

2015-06-10 Thread Ian Campbell
On Tue, 2015-06-09 at 23:35 +0200, Karsten Merker wrote:
   if test -e ${device} ${partition} ${pathprefix}vmlinuz-${kvers}
^^


Ah yes, well spotted, thanks.

I'd switched my system to use the generic script as an experiment (it
worked) and then forgotten to switch it back.

I tried the obvious change though and it doesn't seem to have helped :-(

Ian.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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

2015-06-10 Thread Ian Campbell
On Wed, 2015-06-10 at 09:07 +0100, Ian Campbell wrote:
 I'll cook something up.

I pushed to git which WFM with bootscr.sunxi on Cubietruck as well as
bootscr.uboot-generic both with and without fdtfile being set on Jetson.

Please take a look, I'll upload tonight unless one of you spots an
issue.

Ian.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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

2015-06-10 Thread Ian Campbell
On Wed, 2015-06-10 at 08:41 +0100, Ian Campbell wrote:
 I tried the obvious change though and it doesn't seem to have helped :-(

It looks like the  || construct from #78307 used to handle fallback
for the DTB on platforms without ${fdtfile} doesn't work as expected.
The chain stops after loading the first dtb, I think because || turns
out to be higher precedence that . i.e. it is
   ( load kernel  load fdtfile ) || (load dtb  load ramdisk  boot )
and not
   load kernel  ( load fdtfile || load dtb )  load ramdisk  boot
as required.

My Jetson (my other test system) doesn't set ${fdtfile}, so it falls
back ok to loading the second one and then continues.

_But_ if I set fdtfile on Jetson then it works, but I think it is
falling back to the non-versioned case which the generic version tries
if the versioned one fails.

u-boot's scripting language doesn't seem to understand () nor {}. I
think something using test to see if fdtfile is set might be required
here.

I'll cook something up.

Ian.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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

2015-06-09 Thread Zhang Jingqiang
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.

Thanks

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), 
(1, 'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.0.0-2-armmp-lpae (SMP w/2 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages flash-kernel depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  devio  1.2-1
ii  initramfs-tools0.120
ii  linux-base 3.5
ii  ucf3.0030

Versions of packages flash-kernel recommends:
ii  u-boot-tools  2015.04+dfsg1-2

flash-kernel suggests no packages.

-- Configuration Files:
/etc/flash-kernel/db changed:
Boot-Device: /dev/mmcblk0p1
Machine: Cubietech Cubietruck
Kernel-Flavors: armmp-lpae
Boot-Script-Path: /boot/boot.scr
DTB-Id: sun7i-a20-cubietruck.dtb
U-Boot-Script-Name: bootscr.sunxi
Required-Packages: u-boot-tools


-- debconf information:
* flash-kernel/linux_cmdline: console=ttyS0,115200 hdmi.audio=EDID:0 
disp.screen0_output_mode=EDID:1280x1024p60 root=/dev/mmcblk0p1 rootwait 
panic=10 ${extra}


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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

2015-06-09 Thread Ian Campbell
Control: tag -1 +moreinfo

On Tue, 2015-06-09 at 22:12 +0800, Zhang Jingqiang wrote:
 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'm afraid that since this works for me on Cubietruck that will be
necessary.

As well as the boot log it would be interesting to see the logs from
running flash-kernel too.

[...]
 -- Configuration Files:
 /etc/flash-kernel/db changed:
 Boot-Device: /dev/mmcblk0p1
 Machine: Cubietech Cubietruck
 Kernel-Flavors: armmp-lpae
 Boot-Script-Path: /boot/boot.scr
 DTB-Id: sun7i-a20-cubietruck.dtb
 U-Boot-Script-Name: bootscr.sunxi
 Required-Packages: u-boot-tools

Why have you modified this from the default?

In particular setting Boot-Device is not normally necessary when the
device can boot from /boot (as a CT can), and since it is the same
device as your root appears to be (judging from the below) it is likely
to cause strangeness (e.g. mounting the device twice).

Have you customised anything else, e.g. the u-boot boot environment
perhaps?

Ian.

 
 
 -- debconf information:
 * flash-kernel/linux_cmdline: console=ttyS0,115200 hdmi.audio=EDID:0 
 disp.screen0_output_mode=EDID:1280x1024p60 root=/dev/mmcblk0p1 rootwait 
 panic=10 ${extra}
 
 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org