It is just a script that creates a copy of the initramfs that is generated, so there is a static name for the config.txt to use.

/etc/initramfs/post-update.d/99-initrd

@vortex Technically new ARM64 images generated by the builder for the pi4 "bcm2711" can be used to boot the pi3, pi4 and pi5 and any other variant using the same SoC. If you make pi5 "bcm2712" specific images, they can only be used on the pi5.

The kernel can be updated if you build it ur self using the github repo. There is also a deb-eeprom script on the pi4 images that can be used to update the eeprom package. Warning: I no longer have a Pi4, so I have no idea how well it works anymore and honestly I'm sure the script needs to be updated and made easier to use.

As for pi-bluetooth and sys-mods. There isn't much to do there, as they are basically just debs that install scripts and udev rules and such.

The Zero2W is basically a PI3 in a Zero form factor, so use a Pi3 img.

That's a pretty old image, so i'm not going to pretend to know whats going on with it. You could try messing with some of these rpi specific options: https://www.raspberrypi.com/documentati … figuration

I just spun this and tested it (worked fine for me): https://github.com/pyavitz/rpi-img-buil … -16.img.xz
First boot and general usage: https://github.com/pyavitz/rpi-img-builder#usage

I also included a default passwd for root: toor

Not gonna disagree. Would be easier.

if you feel like putting in the effort you can build an OrangePi PC img for Devuan here: -> https://github.com/pyavitz/debian-image-builder

Well if you were using systemd you could just add net.ifnames=0 to the cmdline. But as this isn't an option on Devuan, you would need to play around with the udev rules.

sudo tee /etc/udev/rules.d/80-net-setup-link.rules <<EOF

SUBSYSTEM!="net", GOTO="net_setup_link_end"

IMPORT{builtin}="path_id"

ACTION!="add", GOTO="net_setup_link_end"

# IMPORT{builtin}="net_setup_link"

NAME=="", ENV{ID_NET_NAME}!="", NAME="wlan0"

LABEL="net_setup_link_end"
EOF

I use a rule like this to insure the ethernet interface comes up as eth0 on Pi3's.

I'm not sure why eth0 would be interfering with it, considering it doesn't have an ethernet port, but I'm happy you got it working.

As for the builder, because of the different versions of GCC and compilers it currently supports and will support in the future, I ended up moving it over to Ubuntu as the Host. Debian and Devuan stable for example only support GCC-9/10. The builder currently supports GCC-8/9/10 and by the start of next year will also support GCC-11 and CLang-13. Basically, Ubuntu unfortunately provides more options.

If need be docker is an option?

You can also install depends manually on Debian and Devuan, but just know certain options won't be available to you. Such as Clang and anything gcc-8 related if building on Bullseye or Chimaera.

My suggestion would be to ask tobetter if he could please include the said overlays. I've only chit-chatted with him a few times concerning problems in the linux source, but he has always been really kind and receptive. He does include them for the Odroid N2/+ so i don't see why it would be that much of a stretch?

tobetter --> https://github.com/tobetter/linux

The image you are using was made with the following builder: https://github.com/pyavitz/rpi-img-builder

I've made lots of changes to the builder since that img was created, one of those changes is in relation to firmware, how its installed and where its located. I don't use the firmware provided by Debian, Devuan or Ubuntu as its usually outdated and incomplete.

The firmware used --> https://github.com/pyavitz/firmware
The firmware function --> https://github.com/pyavitz/rpi-img-buil … ersal#L291
The line now added to the /boot/cmdline.txt --> firmware_class.path=/lib/firmware/updates/brcm

The script used to update kernels, firmware and userland: fetch -h

The gist of it in my opinion is that the imgs on the site need to be updated. I have no access and did not make those imgs myself, so there isn't anything I can do except point out the problem.

The reason the deb install is failing is because the firmware wasn't installed using apt, so you would need to remove the firmware by hand and then run the apt install.

Assuming you have a Pi4 and an extra SDCARD you can produce them yourself without much effort.

Go here, download the pre-made Hirsute IMG and write it to said SD. From there follow the instructions on the README.

When creating an IMG you have 3 options, but only two will probably be of interest. That being make config and make admin, depending on which you choose, fill in the information of choice and create the userdata file.

You can speed up the process by pulling a pre-made kernel, using make helper.

So for example, if you wanted a quick rpi4 img... Create the userdata file and run: make 2711; make rootfs; make image

I'm not in the know of when there will be an official release, plus I'm still waiting to find out what the official sources.list file will look like.