Why not dracut?
One is always free to implement a initrd of oneās choice.
Iā m working on a much more functional, more tailor suited, initrd, with many possibilities For now it is running on R3, but when all functional I will add R4.
Just a few things working on:
Uboot Distro-boot sd/emmc - nvme - nand. Scanning for extlinux.conf on the devices in that order. Where on nand there is also a resque initrd.
This initrd can make connection through dhcp-client. Run my installscript or debootstrap, to install any linux on the R3 directly from initrd.
Anyway, still in development, partly functional. Maybe in a month or so it is usable.
It is all tested and looks good, setting up a usefull NAND image, from where it is quite easy to install any linux distro on nvme (or emmc), or use some linux tools to fix the reason the board is not booting correctly.
In case the R3-Mini (or any other board) is bricked, this is how to get linux running and fix whatever is needed:
with your nand distro-boot + recovery i made a ubuntu image and installed it on emmc. No i am having troubles getting ipv6 working from the router itself. its no prob from the lan side but using wan times out. when checking if all modules have been loaded i noticed the absence of nf_conntrack_ipv6 module, so this seems kinda important ;). when building a new kernel did you somewhere outlined the procedure on how to get the new kernel and modules on the emmc afterwords? I would be greatful for some hints :). Also i would like to thank you for your great work. When im done i will post my config (systemd-networkd, nftables, suricata etc ) on this board in case anyone might wanna use it. i will include a setup script for the most important stuff.So far your builds are working fine ipv4 and ipv6 wise when not on the router itself. Thanks again for all the great work you and Frank W. are making. Appreciate it alot.
Something else i missed mentioning entirelyā¦When using bpir-build -F from the nand-rescue one has to change the https links in the bpir-build script since the nand is missing correct time and the ssl certificates needed to do the build. One can ignore the failing of verification by using curl -k in the script.
The time should get set when using `bpir-dhcpcā command, see line 224
Have you used this command or setup manually?
1 Like
In my images the kernel is build as archlinux package.
Altering the PKGBUILD or defconfig and rebuilding on x86 or aarch64. When not running archlinux, then you can use (arch-)chroot.
https://github.com/ericwoud/archlinuxarm-repo/tree/linux-bpir-git
Thanks will have a look tomorrow. Yeah it works perfectly fine with bpir-dhcpc but Environment was static in that Case. So had to do it manually. nice way of obtaining timeā¦reminds me of kicksecures sdwdate. I have used the Ubuntu Image build that you provide in bpir-build.Alarm doesnt support suricata/hyperscan in Aur yet. So took the easy way. After editing the SSL Errors Out it worked Like a Charm and Image started fine from emmc.