From rynosp at talk2eo.me.uk Wed Jun 3 21:22:45 2026 From: rynosp at talk2eo.me.uk (Ryan) Date: Wed, 3 Jun 2026 22:22:45 +0100 Subject: [Trisquel-devel] Ecne-Armv7h tarball issue Message-ID: Hi, So when aramo came out 2ish years ago, I was able, using the freesh repo kernels, was able to chroot in install the kernel and bootlader, which would build an initramfs about 50M which would then happily boot on sunxi and imx boards. Recently, thanks to help from Jason self, we where able to solve another issue of the later kernels not booting and all is well. However, in order to write a guide I decided to try out my existing guide with the new ecne tarball, exactly as before. On producing a usable image (u-boot etc) and attempting to boot the image on the target hardware, it would fail and drop into a busybox shell, with no input. After some troubleshooting and looking at the initrd images, I was able to work out that most modules needed for booting where not being included and its size was around or below 20M. So I added a list of modules into /etc/initramfs-tools/modules from my working ecne hosts (of which where previously upgraded from aramo), after regenerating the initrd images, then booting it would boot fine as before and a working ecne install from ecne tarball was possible. Looking at the verbose output of update-initramfs, I could see that it now uses dracut-install whereas this wasn't the case in aramo, where it wasn't included. Anyhow, does anybody have any ideas as to why the ecne initramfs now doesn't pull all/many modules by default? Rather than before, in which it seemed to pull all the modules for devices enabled in the kernel config. Also if anyone knows, is there a way to change this by default or will I have to add to the installation guide the modules to add to get devices working? Just seems strange that the default behaviour has changed. As usual, thanks in advance, Ryan