I can confirm this problem. I just got thru running a “stretch” install on my test Cuboxi4Pro with ingredients from:
> wget > http://ftp.us.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/partition.img.gz > wget > http://ftp.us.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/firmware.MX6_Cubox-i.img.gz > wget > http://ftp.us.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images To be absolutely clear which components: > -rw-r--r-- 1 rbthomas rbthomas 871 Jun 29 15:56 > README.concatenateable_images > -rw-r--r-- 1 rbthomas rbthomas 187261 Jun 29 15:56 > firmware.MX6_Cubox-i.img.gz > -rw-r--r-- 1 rbthomas rbthomas 24210806 Jun 29 15:56 partition.img.gz I got the same results as Rainer. System would not boot after installation. There was nothing at all on serial-port the console. I also tried power-cycling the device. Nothing on the serial-port console. Can somebody tell me how to find out if there is a bootable u-boot on the SD card? Maybe the u-boot is getting clobbered by something in the installation process? Let me know if you want log files, etc... Rick > On Aug 21, 2016, at 10:44 AM, Martin Michlmayr <t...@cyrius.com> wrote: > > * Rainer Dorsch <m...@bokomoko.de> [2016-08-21 10:41]: >> The boot loader installation did not show an error, but the device did not >> boot. >> >> The last "words" of the installer: >> >> lqqqqqqqqqqqqqqqqqqqqqu Finishing the installation tqqqqqqqqqqqqqqqqqqqqqqk >> x x >> x 95% x >> x x >> The system is going down NOW!ystem... x >> Sent SIGKILL to all processes x >> Requesting system rebootqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj >> [ 2730.956106] reboot: Restarting system > > Can you 1) attach /var/log/installer/syslog from the SD card and b) > show the boot log (after the installer). > > -- > Martin Michlmayr > http://www.cyrius.com/ >