You are not logged in.
Well, that is my problem, because, on the officially supported Ubuntu image, these overlays do exist, and I have them in my "config.ini" file, and they work neatly ; but Ubuntu is booting terribly slow. Any recommendations of what, exactly, to do to get these overlays working in Devuan?
Offline
Well, that is my problem, because, on the officially supported Ubuntu image, these overlays do exist, and I have them in my "config.ini" file, and they work neatly ; but Ubuntu is booting terribly slow. Any recommendations of what, exactly, to do to get these overlays working in Devuan?
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
Offline
We built beowulf installer images for armel, armhf and ppc64el. If you have appropriate hardware, please test and report.
armel (no mini.iso for these. I hope you know what to do.)
https://pkgmaster.devuan.org/devuan/dis … nt/images/
kirkwood/netboot/marvell/{dreamplug,guruplug,sheevaplug,sheevaplug-esata}
kirkwood/netboot/seagate/dockstar
orion/netboot/buffaloarmhf
https://pkgmaster.devuan.org/devuan/dis … t/mini.isoppc64el (not arm, but it's on my list.)
https://pkgmaster.devuan.org/devuan/dis … t/mini.isoThanks,
fsmithred
How exactly should I be flashing this to an SD Card? Can I just DD it or use balena etcher? Or is there some other method I should be using?
Offline
For the mini.iso images just use
# cp mini.iso /dev/mmcblkX ; sync
Replace X with the correct identifier for the SD card. It should be copied to the entire card rather than a partition.
I think the armel versions need the various components copied to specific locations on the card using dd and the seek option but I've never actually tried it so I'll have to leave that to somebody who knows better.
Last edited by Head_on_a_Stick (2022-02-26 10:19:15)
Brianna Ghey — Rest In Power
Offline
Highly appreciated!
I tried it on arm64 using firmware-none.img together with partition.img and a self-built u-boot to install beowulf on an Xunlong OrangePi Zero plus. In the installation process I selected openrc as init. After fixing dtbs and extlinux (only required as the board has official kernel support but is not officially supported in Debian and lacks a packaged bootloader), installation worked like a charm - at least I didn't observe any regressions when compared to doing the same with Debian 10.
One of the few things I noticed was the following message on shutdown:
* ERROR: apparmor failed to stop
Not sure whether this is arm-specific, though.
I would like to install devuan on a orange pi PC which is not officially supported but it is by armbian. I have found a howto on the Internet: How to install Devuan or almost anything Debian based on Orange Pi PC/One/Lite/Whatever but I would prefer not to mix repositories (devuan and armbian), e.g. doing the same as kuleszdl did using only devuan repositories, since he has successfully installed on a orange pi zero plus, but it is not clear to me the steps of "fixing dtbs and extlinux", could you or someone else clarify those steps in more detail, thanks a lot!
Offline
solved! I found the answer in a different topic http://dev1galaxy.org/viewtopic.php?id=3147
Offline
Unfortunately the chimaera installation did not conclude (No kernel modules found). I downloaded the images from:
https://pkgmaster.devuan.org/devuan/dis … rd-images/
concatenated firmware.none.img.gz and partition.img.gz, built an u-boot image for my board (Orangepi PC) following the instructions of https://linux-sunxi.org/U-Boot and flashed it to the sdcard:
# dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 bs=1024 seek=8
the u-boot image refused to load the initrd.gz image so I converted to uInitrd with
$ mkimage -A arm -O linux -T ramdisk -C gzip -n "netboot image" -a 0x0 -e 0x0 -d initrd.gz uInitrd
and then booted with the following commands to start the installer
setenv bootargs console=ttyS0,115200
fatload mmc 0:1 0x43000000 dtbs/sun8i-h3-orangepi-pc.dtb
fatload mmc 0:1 0x41000000 vmlinuz
fatload mmc 0:1 0x45000000 uInitrd
bootz 0x41000000 0x45000000 0x43000000
after booting the installer started but stopped at this step (No kernel modules found):
lqqqqqqqqqqqqqqqqu [!!] Download installer components tqqqqqqqqqqqqqqqqqk
x x
x No kernel modules found x
x No kernel modules were found. This probably is due to a mismatch x
x between the kernel used by this version of the installer and the x
x kernel version available in the archive. x
x x
x You should make sure that your installation image is up-to-date, or - x
x if that's the case - try a different mirror, preferably x
x deb.devuan.org. x
x x
x <Go Back> <Continue> x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
I used the current image and changed the devuan mirror but it didn't work, the installer kernel version gives
Linux devuan 5.10.0-9-armmp #1 SMP Debian 5.10.70-1 (2021-09-30) armv7l GNU/Linux
could this be fixed somehow? thank you in advance
Offline
Maybe try images at https://arm-files.devuan.org/?
Online
Maybe try images at https://arm-files.devuan.org/?
unfortunately those images won't work because the board is not officially supported but apparently kuleszdl made it work with a similar board (OrangePi Zero plus) https://dev1galaxy.org/viewtopic.php?pid=21185#p21185
Offline
it works making a rootfs with debootstrap:
Linux orangepi 5.10.0-13-armmp #1 SMP Debian 5.10.106-1 (2022-03-17) armv7l
The programs included with the Devuan GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Devuan GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@orangepi:~# uname -a
Linux orangepi 5.10.0-13-armmp #1 SMP Debian 5.10.106-1 (2022-03-17) armv7l GNU/Linux
the reason the installer does not work might be that installation image is not up-to-date as the error message says
Offline
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
Offline
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...
Offline
U-Boot is diff for every board, so I'm not sure how that's really doable, but if it works for you, have at it.
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.
Last edited by c0rnelius (2022-04-24 00:19:50)
Offline
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
Offline
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.
Last edited by c0rnelius (2022-04-24 15:29:35)
Offline
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.
Last edited by christoph (2022-05-08 18:52:51)
Offline
I installed the latest RPi4 build at the end of last week. Works great so far (headless as a server, anyway). It is very impressive to have it using 71MB of RAM sitting at a bash prompt.
I'm working on getting the Argon1 fan/power button scripts to work right now.
Offline
And here is the way to go if you need/want Argon1 case support: https://dev1galaxy.org/viewtopic.php?id=4159
Offline
The https://arm-files.devuan.org link seems to be taking me to the regular non-ARM downloads now. It was working a week or two ago.
Offline
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.
Offline
Thanks for https://github.com/pyavitz/debian-image-builder
I managed to build a rockpro daedalus devuan image from a chimaera host
It did need a bit of modification, the scripts
The rk3399 cpu got up to 70C building kernel, and not that speedy
-----
Is there any plan to make gtk4 libs? I want to make iwgtk, maybe gtk4 is too new?
Offline
Just thought I'd share that Debian Image Builder now builds for the "Orange Pi 5 Plus"-device.
I tested it with Devuan Daedalus.
Offline
I installed Devuan on a set of RPi 4B's a while ago (Beowolf IIRC) and have updated them to Daedalus. They work great; however, I haven't updated the Kernel since - installed with 4.16.18-v7+/armv7l. Is there an official image yet? Or do I need to do another custom build?
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.
Last edited by TemporalBeing (2024-03-30 16:59:24)
Offline
Seagate Personal Cloud (1-BAY version) works pretty well on devuan. I'd say extremely faster than debian too. Because when I SSH to that box while on debian, it'd take around 2 seconds to respond. Now it's instant. Thank you guys.
Offline