tags 834974 + confirmed thanks Martin Michlmayr dijo [Mon, Aug 29, 2016 at 07:49:48PM -0700]: > The log suggests that flash-kernel was installed successfully, i.e. > that a u-boot boot script was generated correctly. > > I don't know anything about this device so unfortunately I cannot help > you. Maybe Vagrant Cascadian knows something?
I own a Cubox-i4pro as well, and can assert I Rainer's experience is reproducible: The installer finishes doing its work and reports having installed the boot loader, but after it attempts to reboot, nothing happens (the computer just hangs idly). My Cubox-i was originally installed via a chroot and manual boot fiddling, as I reported on my blog back in the day¹. In order to check whether this was a regression, I tried installing Jessie, and also ended up with a seemingly successful install that didn't boot. ¹ http://gwolf.org/content/cubox-i4pro I might have botched something while preparing my Jessie install: Having all the files at the same directory, it is possible I booted it with the Stretch kernel — and I fear that because my syslog starts with: Jan 1 00:00:03 syslogd started: BusyBox v1.22.1 Jan 1 00:00:03 kernel: klogd started: BusyBox v1.22.1 (Debian 1:1.22.0-19) Jan 1 00:00:03 kernel: [ 0.000000] Booting Linux on physical CPU 0x0 Jan 1 00:00:03 kernel: [ 0.000000] Linux version 4.6.0-1-armmp (debian-ker...@lists.debian.org) (gcc version 5.4.0 20160609 (Debian 5.4.0-4) ) #1 SMP Debian 4.6.2-2 (2016-06-25) and of course, the installer started by telling me of a kernel version conflict :) I cannot dig deeper into this today, but I'll come back to this topic on Monday. Can somebody confirm whether the Jessie installer actually works reliably on this machine? (that is, whether it's always been broken or we have a regression)