I have a Cubietruck SBC. I can properly create netboot sd card images. If I use cubietruck firmware, usb keyboard won't work at all. Installer loads and runs, but I cannot use it. If I use olinuxino-lime2 firmware, usb keyboard works and I can install

FYI.Thanks

b9AcE

Just thought I'd share that Debian Image Builder now builds for the "Orange Pi 5 Plus"-device.
I tested it with Devuan Daedalus.

Thanks!

Haha, i need to edit this message

Its way to complicated for me to build it my own :-)

I'm looking for an Orange Pi 5 version

BTW, my goal is for these to a small K8 cluster - trying hard to keep them Devuan-based in the process - 1 K8 Master and 4 K8 Nodes. Was noticing I needed to add some modules per the K8 configuration and noticed I didn't include them in my build. Would be great to get on an official provided image so it gets updated with `apt-get` instead of having to do custom builds; but I get it if that's not functional given the state of ARM SoC support.

Maybe try images at https://arm-files.devuan.org/?

FYI, I've encountered an error with the devuan_chimaera_4.0.0_arm64_rpi4.img where the Raspberry Pi freezes when the CPU cores are maxed out for a few seconds. Turning off the second monitor by commenting out max_framebuffers=2 prevented the Pi from freezing. Downgrading the kernel to 5.4.42 fixed the issue for me although I haven't had time to identify which kernel version the issue was introduced in.

Image : https://arm-files.devuan.org/devuan_chi … i4.img.zip (SHA256 239e7dbfe0f27eaa2305fefcfca2f9838c65d90828892cdd96aed8bd76c743b)

The installation was based on instructions by Andreas Hug: https://andreashug.medium.com/raspberry … 7e680fc8d5. The most significant changes were omitting the logical volume manager, using a second SD card with NOOBS instead of shuffling partitions on the primary SD card, and encrypting with Adiantum+Argon2i instead of AES+SHA256.

Overall a success except for the small issues below:

• When starting the system for the first time, the framebuffer resolution was too high. Only a small part of the console output was visible and the setup seemed to be hung. There was a visible restart counter ("restart: 6/-1" before pulling the plug) and the lower bottom part of a QR code was visible in the upper right corner of the screen. The fix was to manually set the framebuffer resolution in `/boot/config.txt` (`framebuffer_width`, `frambuffer_height`).

• The SD card could not be mounted after this. The SD card is brand new and after copying the Devuan image a second time on the SD card, there were no further mounting problems. `dd conv=fsync` was used both times.

• The second partition with the root file system was not aligned to a 4096 byte boundary.

• Making Wi-Fi work was annoying. The rfkill was obvious to fix but afterwards both connman (error message `Error /net/connman/technology/wifi: No carrier`) and network-manager (no visible access points when iwlist saw them) did not work. Removing connman and adding the Wi-Fi name and password in `/etc/wpa_supplicant/wpa_supplicant.conf` lead to Wi-Fi access.

• The country in `wpa_supplicant.conf` was wrong, even after setting up locales.

the kernel is very modular it will only load the drivers for your SBC, the netboot installer was working very well except it stopped at the error message with a no matching kernel (version 5.10.70-1 used by the current installer image might have been removed for chimaera repositories?). How to build a netboot image for an unsupported SBC in devuan  is described at the end of the README file, it might work if there is a specific device tree for your SBC, see e.g. https://pkgmaster.devuan.org/devuan/dis … vice-tree/, so the problem reduces to build and configure u-boot which is far easier than making a custom kernel and to build a custom image for the whole distribution for every SBC

Not gonna disagree. Would be easier.

As for kernels than sure... Someone could make a super bloated kernel for just about all the SoCs and have them run some what OK. But even that depending on the SoC would not be a great idea.

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

actually I didn't change anything it runs out of the box with kernel 5.10 (I've only compiled u-boot which is well documented) although I haven't tested it much only text mode, IMO it might be better to fix the installer, the fix might be to update the installation image, or maybe I didn't use the right parameters for the initrd image, ..., the installer can be used then with any of the supported SBCs in the kernel, instead of building an image for each SBC...