The officially official Devuan Forum!

You are not logged in.

#1 Devuan » Docker images » 2021-01-31 22:49:17

vazhnov
Replies: 1

Hi all!

I created another one public repository with Devuan docker images and a small documentation: https://hub.docker.com/r/vazhnov/devuan
Images are tiny, about 30 MB compressed.

Also I see another unofficial Devuan images repositories: https://hub.docker.com/search?q=devuan&type=image

Any ideas how to create official one?

#3 Re: Installation » AWS EC2 AMI by FAI: grub-probe: error: failed to get canonical path » 2020-11-08 00:09:55

Checked the same steps with Devuan 4 Chimaera and fresh content of "debian-cloud-images" repository — image created successfully:

 % ls -l /tmp/image*                 
-rw-r--r-- 1 root  root       37004 Nov  8 03:01 /tmp/image_buster_ec2_amd64.build-fai.json
-rw-r--r-- 1 lenin lenin      37806 Nov  8 03:02 /tmp/image_buster_ec2_amd64.build.json
-rw-r--r-- 1 root  root       15460 Nov  8 03:01 /tmp/image_buster_ec2_amd64.build.junit.xml
-rw-r--r-- 1 root  root       42430 Nov  8 03:01 /tmp/image_buster_ec2_amd64.info
-rw-r--r-- 1 root  root  8589934592 Nov  8 03:01 /tmp/image_buster_ec2_amd64.raw
-rw-r--r-- 1 lenin lenin  775700480 Nov  8 03:01 /tmp/image_buster_ec2_amd64.tar
 % file /tmp/image_buster_ec2_amd64.raw
/tmp/image_buster_ec2_amd64.raw: DOS/MBR boot sector, extended partition table (last)

#4 Re: Installation » AWS EC2 AMI by FAI: grub-probe: error: failed to get canonical path » 2020-07-05 18:23:55

Devuan 3:

root@devuan3-01:~# for i in proc sys dev;do findmnt /$i;done
TARGET SOURCE FSTYPE OPTIONS
/proc  proc   proc   rw,nosuid,nodev,noexec,relatime
TARGET SOURCE FSTYPE OPTIONS
/sys   sysfs  sysfs  rw,nosuid,nodev,noexec,relatime
TARGET SOURCE FSTYPE   OPTIONS
/dev   udev   devtmpfs rw,nosuid,relatime,size=1005164k,nr_inodes=251291,mode=755

Debian 10:

root@debian10-01:~# for i in proc sys dev;do findmnt /$i;done
TARGET SOURCE FSTYPE OPTIONS
/proc  proc   proc   rw,nosuid,nodev,noexec,relatime
TARGET SOURCE FSTYPE OPTIONS
/sys   sysfs  sysfs  rw,nosuid,nodev,noexec,relatime
TARGET SOURCE FSTYPE   OPTIONS
/dev   udev   devtmpfs rw,nosuid,relatime,size=1006728k,nr_inodes=251682,mode=755

No difference except size and nr_inodes.

#5 Installation » AWS EC2 AMI by FAI: grub-probe: error: failed to get canonical path » 2020-07-05 17:21:35

vazhnov
Replies: 3

I'm trying to create clean minimal Devuan image for AWS.

As I know, Debian uses Fully automatic installation (FAI) to create AWS AMIs: https://wiki.debian.org/Cloud/SystemsComparison, https://wiki.debian.org/Cloud/AmazonEC2Image.

So first I tried to repeat process of Debian image creation by FAI. Next step will be: change FAI configuration to build Devuan image.

System: I use KVM virtual machine (Proxmox 6/Debian 10 buster) with Devuan guest:

lenin@devuan3-01 ~ % cat /etc/os-release
PRETTY_NAME="Devuan GNU/Linux 3 (beowulf)"
NAME="Devuan GNU/Linux"
VERSION_ID="3"
VERSION="3 (beowulf)"
VERSION_CODENAME=beowulf
ID=debian
ID_LIKE=debian
HOME_URL="https://www.devuan.org/"
SUPPORT_URL="https://devuan.org/os/community"
BUG_REPORT_URL="https://bugs.devuan.org/"

Commands I used:

sudo apt-get -V install fai-server fai-setup-storage qemu-utils
sudo apt-get -V --no-install-recommends install ca-certificates debsums dosfstools fai-server fai-setup-storage make python3 python3-libcloud python3-marshmallow python3-pytest python3-yaml qemu-utils udev
git clone "git@salsa.debian.org:cloud-team/debian-cloud-images.git"
cd debian-cloud-images
make DESTDIR=/tmp/ image_buster_ec2_amd64

(also I changed apt_cdn=http://192.168.1.1:3142/deb.debian.org and security_cdn=http://192.168.1.1:3142/security.debian.org URLs to use apt-cacher-ng).

Result:

…
Setting up grub-cloud-amd64 (0.0.4) ...
grub-probe: error: failed to get canonical path of `/dev/loop0p1'.
Installing for i386-pc platform.
grub-install: error: failed to get canonical path of `/dev/loop0p1'.
dpkg: error processing package grub-cloud-amd64 (--configure):
 installed grub-cloud-amd64 package post-installation script subprocess returned error exit status 1
…

Errors were encountered while processing:
 grub-cloud-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
ERROR: 25600 25600
ERROR: chroot /tmp/fai-diskimage.M61Y2t apt-get -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confnew --fix-missing install --no-install-recommends openssh-server cloud-initramfs-growroot sudo libpam-systemd unattended-upgrades chrony apt-utils ifupdown init iptables iputils-ping isc-dhcp-client less logrotate nano netbase rsyslog vim-tiny whiptail python-boto bsdmainutils awscli python3-boto cloud-init cloud-guest-utils linux-image-cloud-amd64 apparmor grub-cloud-amd64 return code 100
install_packages: executing chroot /tmp/fai-diskimage.M61Y2t apt-get clean
install_packages: executing chroot /tmp/fai-diskimage.M61Y2t dpkg --configure --pending
Setting up grub-cloud-amd64 (0.0.4) ...
grub-probe: error: failed to get canonical path of `/dev/loop0p1'.
Installing for i386-pc platform.
grub-install: error: failed to get canonical path of `/dev/loop0p1'.
dpkg: error processing package grub-cloud-amd64 (--configure):
 installed grub-cloud-amd64 package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 grub-cloud-amd64
ERROR: 256 256
ERROR: chroot /tmp/fai-diskimage.M61Y2t dpkg --configure --pending return code 1
install_packages: executing chroot /tmp/fai-diskimage.M61Y2t dpkg -C
The following packages are only half configured, probably due to problems
configuring them the first time.  The configuration should be retried using
dpkg --configure <package> or the configure menu option in dselect:
 grub-cloud-amd64     GRand Unified Bootloader (cloud setup)

install_packages: executing chroot /tmp/fai-diskimage.M61Y2t apt-get clean
2 errors during executing of install_packages
Error in task instsoft. Code: 471
Traceback: task_error task_instsoft task task_install task task_action task main
FATAL ERROR. Installation stopped.
Size of disk image and filename: 800M	/tmp/image_buster_ec2_amd64.raw
Image created by: /usr/sbin/fai-diskimage --verbose --hostname debian --class DEBIAN,CLOUD,TYPE_DEV,BUSTER,EXTRAS,EC2,IPV6_DHCP,AMD64,GRUB_CLOUD_AMD64,LOCALDEBS,LINUX_IMAGE_CLOUD,LAST --size 8G --cspace /home/lenin/debian-cloud-images/src/debian_cloud_images/build/fai_config /tmp/image_buster_ec2_amd64.raw
Traceback (most recent call last):
  File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/lenin/debian-cloud-images/src/debian_cloud_images/cli/__main__.py", line 38, in <module>
    main()
  File "/home/lenin/debian-cloud-images/src/debian_cloud_images/cli/__main__.py", line 34, in main
    args.cls(argparser=parser, **vars(args))()
  File "/home/lenin/debian-cloud-images/src/debian_cloud_images/cli/build.py", line 417, in __call__
    self.fai(not self.noop)
  File "/home/lenin/debian-cloud-images/src/debian_cloud_images/build/fai.py", line 47, in __call__
    raise subprocess.CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '('sudo', 'env', 'PYTHONPATH=/home/lenin/debian-cloud-images/src/debian_cloud_images/build/../..', 'CLOUD_BUILD_DATA=/home/lenin/debian-cloud-images/src/debian_cloud_images/data', 'CLOUD_BUILD_INFO={"type": "dev", "release": "buster", "release_id": "10", "release_baseid": "10", "vendor": "ec2", "arch": "amd64", "build_id": "manual", "version": "202007051951"}', 'CLOUD_BUILD_NAME=image_buster_ec2_amd64', 'CLOUD_BUILD_OUTPUT_DIR=/tmp', 'CLOUD_RELEASE_ID=ec2', 'CLOUD_RELEASE_VERSION=202007051951', 'fai-diskimage', '--verbose', '--hostname', 'debian', '--class', 'DEBIAN,CLOUD,TYPE_DEV,BUSTER,EXTRAS,EC2,IPV6_DHCP,AMD64,GRUB_CLOUD_AMD64,LOCALDEBS,LINUX_IMAGE_CLOUD,LAST', '--size', '8G', '--cspace', '/home/lenin/debian-cloud-images/src/debian_cloud_images/build/fai_config', '/tmp/image_buster_ec2_amd64.raw')' returned non-zero exit status 1.
make: *** [Makefile:14: image_buster_ec2_amd64] Error 1

Before the error, disks are:

lenin@devuan3-01 ~ % sudo lsblk
NAME       MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop0        7:0    0    8G  0 loop 
├─loop0p1  259:0    0  7.9G  0 part /tmp/fai-diskimage.M61Y2t
├─loop0p14 259:1    0    3M  0 part 
└─loop0p15 259:2    0  124M  0 part /tmp/fai-diskimage.M61Y2t/boot/efi
sr0         11:0    1  620M  0 rom  
vda        254:0    0   32G  0 disk 
├─vda1     254:1    0   30G  0 part /
├─vda2     254:2    0    1K  0 part 
└─vda5     254:5    0    2G  0 part [SWAP]
lenin@devuan3-01 ~ % sudo blkid|grep loop| sort
/dev/loop0p14: PARTUUID="f298765a-20f9-2543-8fe7-2749d86cdd61"
/dev/loop0p15: SEC_TYPE="msdos" UUID="4FCA-6200" TYPE="vfat" PARTUUID="5afa65b1-da1b-3648-b04c-c16bc2da197e"
/dev/loop0p1: UUID="f69236e0-7497-40a3-9e78-79d095a33e20" TYPE="ext4" PARTUUID="87e7358e-67ec-ba46-8dc5-91ecdd661c0e"
/dev/loop0: PTUUID="7553b010-f107-3449-9c99-5db320211b37" PTTYPE="gpt"
lenin@devuan3-01 ~ % ls -lAF /tmp/fai-diskimage.M61Y2t
total 88
drwxr-xr-x   2 root  root   4096 Jul  5 19:54 bin/
drwxr-xr-x   3 root  root   4096 Jul  5 19:54 boot/
drwxr-xr-x   4 root  root   4096 Jul  5 19:52 dev/
drwxr-xr-x  71 root  root   4096 Jul  5 19:55 etc/
drwxr-xr-x   2 root  root   4096 May  2 19:39 home/
drwxr-xr-x  12 root  root   4096 Jul  5 19:54 lib/
drwxr-xr-x   2 root  root   4096 Jul  5 19:52 lib64/
drwxr-xr-x   2 lenin lenin  4096 Jun 20 15:40 localdebs/
drwx------   2 root  root  16384 Jul  5 19:51 lost+found/
drwxr-xr-x   2 root  root   4096 Jul  5 19:52 media/
drwxr-xr-x   2 root  root   4096 Jul  5 19:52 mnt/
drwxr-xr-x   2 root  root   4096 Jul  5 19:52 opt/
dr-xr-xr-x 106 root  root      0 Jul  1 00:29 proc/
drwx------   2 root  root   4096 Jul  5 19:52 root/
drwxr-xr-x   5 root  root   4096 Jul  5 19:53 run/
drwxr-xr-x   2 root  root   4096 Jul  5 19:54 sbin/
drwxr-xr-x   2 root  root   4096 Jul  5 19:52 srv/
dr-xr-xr-x  13 root  root      0 Jul  1 00:29 sys/
drwxrwxrwt   2 root  root   4096 Jul  5 19:54 tmp/
drwxr-xr-x  10 root  root   4096 Jul  5 19:52 usr/
drwxr-xr-x  11 root  root   4096 Jul  5 19:52 var/

I tried to repeat the same steps on the same Debian KVM virtual machine, it finished without error.

Any idea how to prevent this error, "grub-probe: error: failed to get canonical path of `/dev/loop0p1'"?

#6 Re: ARM Builds » Installer images for armel, armhf and ppc64 need testing » 2020-05-31 13:12:32

fsmithred wrote:

We built beowulf installer images for armel, armhf and ppc64el. If you have appropriate hardware, please test and report.

My try with Devuan installer for armhf described here: https://dev1galaxy.org/viewtopic.php?id=3551

#7 Re: ARM Builds » Devuan installer can't start on MX53 Loco (i.MX53 Quick Start board) » 2020-05-31 13:08:53

Problem 2: ISO image

What have I do here?

[            (1*installer)  2 shell  3 shell  4- log           ][ Jan 01  0:02 ]
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
   ┌─────────┤ [!!] Scan hard drives for an installer ISO image ├──────────┐    
   │                                                                       │    
   │                 Failed to find an installer ISO image                 │    
   │ No installer ISO images were found. If you downloaded the ISO image,  │    
   │ it may have a bad filename (not ending in ".iso"), or it may be on a  │    
   │ file system that could not be mounted.                                │    
   │                                                                       │    
   │ You'll have to use an alternative installation method, select another │    
   │ device to look for ISO image, or try again after you've fixed it.     │    
   │                                                                       │    
   │     <Go Back>                                          <Continue>     │    
   │                                                                       │    
   └───────────────────────────────────────────────────────────────────────┘    
                                                                                
                                                                                
                                                                                
                                                                                
<Tab> moves; <Space> selects; <Enter> activates buttons                         

Which ISO image to use? I tried https://pkgmaster.devuan.org/devuan/dis … t/mini.iso — it is too small, only 33MB, and error is the same.

#8 Re: ARM Builds » Devuan installer can't start on MX53 Loco (i.MX53 Quick Start board) » 2020-05-31 11:22:13

Installer started after some manipulations (I'm not sure about addresses, especially kernel_addr_r=0x70008000):

=> setenv distro_bootpart ${mmcpart}
=> printenv distro_bootpart         
distro_bootpart=1
=> setenv boot_targets mmc
=> printenv boot_targets
boot_targets=mmc
=> setenv fdtfile ${fdt_file}
=> printenv fdtfile
fdtfile=imx53-qsrb.dtb
=> setenv bootpart ${mmcpart}
=> printenv bootpart
bootpart=1
=> setenv devnum ${mmcdev}
=> printenv devnum
devnum=0
=> setenv console ttymxc0
=> printenv console
=> setenv devtype mmc
=> printenv devtype  
devtype=mmc
=> setenv fdt_addr_r ${fdt_addr}
=> printenv fdt_addr_r                                    
fdt_addr_r=0x71000000
=> setenv ramdisk_addr_r ${loadaddr}
=> printenv ramdisk_addr_r          
ramdisk_addr_r=0x72000000
=> setenv kernel_addr_r 0x70008000
=> printenv kernel_addr_r
kernel_addr_r=0x70008000
=> boot

#9 ARM Builds » Devuan installer can't start on MX53 Loco (i.MX53 Quick Start board) » 2020-05-31 10:15:46

vazhnov
Replies: 3
Intro

I have a "i.MX53 Quick Start board", which named "MCIMX53-START-R" (a new one, with PMIC MC34708 and Device tree file "imx53-qsrb.dtb", not old board with PMIC Dialog DA9053).

I repeated steps from http://deb.devuan.org/devuan/dists/beow … ble_images:

 % wget "http://deb.devuan.org/devuan/dists/beowulf/main/installer-armhf/current/images/hd-media/SD-card-images/firmware.MX53LOCO.img.gz
 % wget "http://deb.devuan.org/devuan/dists/beowulf/main/installer-armhf/current/images/hd-media/SD-card-images/partition.img.gz"
 % zcat firmware.MX53LOCO.img.gz partition.img.gz > complete_image.img

Here are sha256sum(s):

fdb1096a90394878f0f5e23e146cc89ecd55d867b4b9327b791112041d8c9f51  complete_image.img
69376dc6f680a9d7273e36f39cb0d8d2f9d2fccd0756a13cff63b588e1b2ca24  firmware.MX53LOCO.img.gz
f3cf86ab65a1ca2469ca9fe9fe7ac1e9267d3c69bc5f12c7131503bb5e5764ca  partition.img.gz

And some other info:

 % file firmware.MX53LOCO.img partition.img complete_image.img
firmware.MX53LOCO.img: DOS/MBR boot sector; partition 1 : ID=0xc, active, start-CHS (0x0,32,33), end-CHS (0xc,114,38), startsector 2048, 197952 sectors
partition.img:         DOS/MBR boot sector, code offset 0x58+2, OEM-ID "mkfs.fat", Media descriptor 0xf8, sectors/track 32, heads 64, sectors 197952 (volumes > 32 MB), FAT (32 bit), sectors/FAT 1523, reserved 0x1, serial number 0x3498c0b4, unlabeled
complete_image.img:    DOS/MBR boot sector; partition 1 : ID=0xc, active, start-CHS (0x0,32,33), end-CHS (0xc,114,38), startsector 2048, 197952 sectors

Some useful information from U-Boot console, when I loaded board with this image:

=> printenv 
baudrate=115200
boot_fdt=try
bootcmd=mmc dev ${mmcdev}; if mmc rescan; then if run loadbootscript; then run bootscript; else if run loadimage; then run mmcboot; else run netboot; fi; fi; else run netboot; fi
bootdelay=2
bootscript=echo Running bootscript from mmc ...; source
ethact=FEC
ethaddr=00:04:9f:02:3e:73
ethprime=FEC0
fdt_addr=0x71000000
fdt_file=imx53-qsrb.dtb
fileaddr=72000000
filesize=627
image=zImage
ip_dyn=yes
loadaddr=0x72000000
loadbootscript=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${script};
loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}
loadimage=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image}
mmcargs=setenv bootargs console=ttymxc0,${baudrate} root=${mmcroot}
mmcboot=echo Booting from mmc ...; run mmcargs; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then bootz ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;
mmcdev=0
mmcpart=1
mmcroot=/dev/mmcblk0p2 rw rootwait
netargs=setenv bootargs console=ttymxc0,${baudrate} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
netboot=echo Booting from net ...; run netargs; if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; ${get_cmd} ${image}; if test ${boot_fdt} = yes ||  test ${boot_fdt} = try; then if ${get_cmd} ${fdt_addr} ${fdt_file}; then bootz ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then bootz; else echo ERROR: Cannot load the DT; exit; fi; fi; else bootz; fi;
script=boot.scr

Environment size: 1549/8188 bytes
=> ls mmc ${mmcdev}:${mmcpart} /
 17385125   initrd.gz
            dtbs/
     1575   boot.scr
  4260352   vmlinuz

3 file(s), 1 dir(s)
=> bdinfo
arch_number = 0x00000cc9
boot_params = 0x70000100
DRAM bank   = 0x00000000
-> start    = 0x70000000
-> size     = 0x20000000
DRAM bank   = 0x00000001
-> start    = 0xb0000000
-> size     = 0x20000000
eth0name    = FEC
ethaddr     = 00:04:9f:02:3e:73
current eth = FEC
ip_addr     = <NULL>
baudrate    = 115200 bps
TLB addr    = 0x8fff0000
relocaddr   = 0x8ff6c000
reloc off   = 0x1876c000
irq_sp      = 0x8f569eb0
sp start    = 0x8f569ea0
FB base     = 0x8f56c900

Also I mounted "partition.img" on my computer:

 % sudo losetup --show --find --partscan partition.img
 % sudo mount /dev/loop0 /mnt/imx53 
 % file /mnt/imx53/*       
/mnt/imx53/boot.scr:  u-boot legacy uImage, , Linux/ARM, Script File (gzip), 1511 bytes, Mon May 11 17:46:03 2020, Load Address: 0x00000000, Entry Point: 0x00000000, Header CRC: 0x79006BD0, Data CRC: 0x8734369F
/mnt/imx53/dtbs:      directory
/mnt/imx53/initrd.gz: gzip compressed data, max compression, from Unix, original size modulo 2^32 46077952
/mnt/imx53/vmlinuz:   Linux kernel ARM boot executable zImage (little-endian)
 % file /mnt/imx53/dtbs/imx53-qsrb.dtb
/mnt/imx53/dtbs/imx53-qsrb.dtb: Device Tree Blob version 17, size=21932, boot CPU=0, string block size=1236, DT structure block size=20640
 % strings /mnt/imx53/boot.scr
# Bootscript using the new unified bootcmd handling
# introduced with u-boot v2014.10
if test -n "${boot_targets}"; then
  echo "Mainline u-boot / new-style environment detected."
else
  echo "Non-mainline u-boot or old-style mainline u-boot detected."
  echo "This boot script uses the unified bootcmd handling of mainline"
  echo "u-boot >=v2014.10, which is not available on your system."
  echo "Please boot the installer manually."
  exit 0
if test -z "${fdtfile}"; then
  echo 'fdtfile environment variable not set. Aborting boot process.'
  exit 0
if test -n "${distro_bootpart}"; then
  setenv partition "${distro_bootpart}"
else
  setenv partition "${bootpart}"
if test ! -e ${devtype} ${devnum}:${partition} dtbs/${fdtfile}; then
  echo "This installer medium does not contain a suitable device-tree file for"
  echo "this system (${fdtfile}). Aborting boot process."
  exit 0
# Some i.MX6-based systems do not encode the baudrate in the console variable
if test "${console}" = "ttymxc0" && test -n "${baudrate}"; then
  setenv console "${console},${baudrate}"
if test -n "${console}"; then
  setenv bootargs "${bootargs} console=${console}"
load ${devtype} ${devnum}:${partition} ${kernel_addr_r} vmlinuz \
&& load ${devtype} ${devnum}:${partition} ${fdt_addr_r} dtbs/${fdtfile} \
&& load ${devtype} ${devnum}:${partition} ${ramdisk_addr_r} initrd.gz \
&& echo "Booting the Devuan installer..." \
&& bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}

I wrote image to SD card:

 % sudo dd of=/dev/sdb if=complete_image.img bs=4M status=progress 
71303168 bytes (71 MB, 68 MiB) copied, 1 s, 66,8 MB/s
24+1 records in
24+1 records out
102400000 bytes (102 MB, 98 MiB) copied, 18,5083 s, 5,5 MB/s
The problem

I powered on my "i.MX53 Quick Start board" with SD card with Devuan installer:

U-Boot 2019.01+dfsg-7 (May 14 2019 - 02:07:44 +0000)

CPU:   Freescale i.MX53 rev2.1 at 800 MHz
Reset cause: POR
Board: MX53 LOCO
I2C:   ready
DRAM:  1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   FEC
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
1575 bytes read in 21 ms (73.2 KiB/s)
Running bootscript from mmc ...
## Executing script at 72000000
Non-mainline u-boot or old-style mainline u-boot detected.
This boot script uses the unified bootcmd handling of mainline
u-boot >=v2014.10, which is not available on your system.
Please boot the installer manually.
=>

As I understand, "Warning - bad CRC, using default environment" is OK.

U-Boot not installed inside board, it run from SD-card, from Devuan file "firmware.MX53LOCO.img".
The file "boot.scr" also came with Devuan image, "partition.img".
But they don't want to work together.

Any ideas how to fix error "Please boot the installer manually"?

Board footer

Forum Software