The officially official Devuan Forum!

You are not logged in.

#1 2024-10-24 15:38:36

EchedeyLR
Member
From: Canary Islands, Spain
Registered: 2021-08-18
Posts: 3  

RISCV support

I wanted to ask if there is thought or plan to provide support for RISCV-based computers (now an official arch in Debian starting by 13/Trixie).

Currently, I am playing a bit with a VisionFive2 which is gaining support bit by bit and was looking for a way to get Devuan (because I like the style which differs from Debian).

Offline

#2 2024-10-24 16:24:32

Camtaf
Member
Registered: 2019-11-19
Posts: 527  

Re: RISCV support

Well, there's no official support for ARM, so I would guess not....

Offline

#3 2024-10-24 21:32:16

ralph.ronnquist
Administrator
From: Battery Point, Tasmania, AUS
Registered: 2016-11-30
Posts: 1,606  

Re: RISCV support

It may depend on what you mean by "Devuan" and "support for".

Technically "Devuan" (as organisation) is merely this small group of people that publish the collection of packages that includes all debian packages except some. Those that require systemd have been forked where possible and they are maintained (by these people) towards providing relevant functionality without systemd; most are forked but a few end up just being excluded from the devuan repositories. Currently supported (i.e. maintained, built and published) architectures are amd64, arm64, armel, armhf, i386, riscv64 and ppc64el (all using debian's architecture labelling).

Though "Devuan" (as organisation) might also be understood to include the people that compose and publish filesystems and disk images that are installations of various kinds using devuan packages. Those works span a more limited range of architectures and they provide support (or not) individually for their published works. I'm aware of people having riscv64 installations of devuan packages but not of anyone publishing such for replication.

Offline

#4 2025-09-15 07:42:17

stargate-sg1-cheyenne-mtn
Member
Registered: 2023-11-27
Posts: 479  

Re: RISCV support

@EchedeyLR, how is your VisionFive2 experimentation progressing?


Be Excellent to each other and Party On!
https://www.youtube.com/watch?v=rph_1DODXDU
https://en.wikipedia.org/wiki/Bill_%26_Ted%27s_Excellent_Adventure
Do unto others as you would have them do instantaneously back to you!

Offline

#5 2026-02-11 08:17:07

tripole
Member
Registered: 2023-08-20
Posts: 4  
Website

Re: RISCV support

@EchedeyLR

Devuan runs well on the VisionFive 2, at least Excalibur, and it can be installed using the standard bootstrap procedure. The only caveat is that serial console has to be enabled in /etc/inittab. There is a script called debuntu_dbstrap_riscv64.bash at my Gitlab page https://gitlab.com/tripole-inc/bootdisk which you can use to build an image, or you can just rip out the parts you need (the script also builds images for Debian and Ubuntu). There is also a download link to a Devuan Excalibur image for the VF2 on the Gitlab page.

Last edited by tripole (2026-02-11 08:17:36)

Offline

#6 2026-02-11 14:15:34

fsmithred
Administrator
Registered: 2016-11-25
Posts: 2,824  

Re: RISCV support

Offline

#7 2026-02-11 20:01:09

tripole
Member
Registered: 2023-08-20
Posts: 4  
Website

Re: RISCV support

@fsmithred
Yes, it is definitely useful. I just tried installing to SD using the mini.iso found from the link you provided and it works well. However, it requires some "massage", see below. One of the problems is how to boot the installer on VF2. Therefore, I personally think debootstrapping is better for now (even though also that requires some chroot work etc.)

Example installation to SD (on bare metal VF2): In order to boot the iso I copied it to a USB and booted it on the VF2 via Petitboot that I have on EMMC. (I have u-boot on SPI-flash.)  As install target I used an SD which had the partition scheme that VF2's u-boot expects. The installation went fine except that the Devuan installer does not accept to have a boot partition with vfat so I chose ext2 and later ("offline") converted it to vfat. (I booted into another distro on the VF2 and from there updated the UUIDs in fstab and regenerated the initramfs in a chroot). Finally I added an extlinux.conf on the boot partition on the SD. It booted fine (using u-boot on SPI-flash) and seems to run as intended (except for time; I had to install ntpsec).

SInce the Devuan installer works I expect that installation to SD using the installer files ("linux","initrd.gz") in QEMU would also work.

Edit: I was wrong about the difficulty of booting the installer; indeed the installer iso can be booted using u-boot (on SPI-flash), at least if it is mainline u-boot >= 2025.01 since these u-boot versions can do an EFI boot of Grub on the iso, which will bring up the installer. So, copy the the iso to a USB and start the VF2, and interrupt u-boot at the point "Hit any key to interrupt..". Then, at the u-boot prompt, do

# usb start
# usb storage # (useful but not necessary)
# setenv devnum 0
# run usb_boot

and proceed with the install.

Last edited by tripole (Yesterday 19:05:21)

Offline

#8 Today 12:03:52

tripole
Member
Registered: 2023-08-20
Posts: 4  
Website

Re: RISCV support

I have now done also an EFI based Excalibur installation for VF2 on an SD, using the installer mini.iso on a USB. The image on SD can be booted with u-boot (SPI-flash), provided u-boot is a newer version (see post #7 above). There is only one caveat (see further below).

The installer does not seem to provide (easily) to set up an EFI install so I prepared an SD with a standard layout

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         1026047   500.0 MiB   EF00  EFI system partition
   2         1026048         5220351   2.0 GiB     8200  Linux swap
   3         5220352        62332927   27.2 GiB    8300  Linux filesystem

I then formatted the EFI partition to FAT32 by 'mkfs.fat -F32 /dev/sdX' (but the Devuan installer will still think this is FAT16, oh well).

Next I started the installer on the VF2 (see e.g. post #7).

I installed as usual (EFI partition mounted on /boot/efi, the ext4 partition on /, and added swap), but just before leaving the installer (where you are asked to reboot) I switched to a terminal (e.g. ctrl-a 2) and there did a 'chroot /target/ bash' (the root / on the SD is mounted under /target/).
At the bash prompt in the chroot jail I did

# apt install ntpsec
# apt install grub-efi-riscv64
# grub-install --efi-directory=/boot/efi
# mkdir /boot/efi/EFI/BOOT
# cp /boot/efi/EFI/debian/grubriscv64.efi /boot/efi/EFI/BOOT/BOOTRISCV64.EFI
# update-grub
# exit # (exit chroot and get back to installer menu)

I rebooted and then stopped u-boot at "Hit any key..." to get to the u-boot prompt.
At the u-boot prompt, I did

# mmc dev 1 # (my SD is on dev 1, eMMC is on dev 0)
# mmc part # (useful but not necessary)
# run mmc_boot

This will bring up the usual Grub menu etc, boot will proceed normally and Bob will be your uncle.

Several things above are from memory so some details may be off.

Caveat: If I boot the installer using u-boot (as described in #7) then I can't move the cursor with the up/down arrows in the main Grub menu (in serial console) so I can't select Advanded (options). If I anyway just go ahead and hit Enter then the default installation method proceeds but it seems to have serious difficulties with mirrors, package files etc (I tried it several times). However, when I boot the installer using Petitboot (thus bypassing Grub) I always choose the second "install" option that appears but I don't know exactly that that is since Petitboot doesn't properly render anything except simple Grub-isms. I think, however, that what I do then (when I select the second "install" option) is that I select some form of "expert install" (but it looks like the normal installer flow). Anyway, that works like a charm.

This reference is helpful: https://wiki.debian.org/InstallingDebia … sionFiveV2

I hope someone else will help straighten out the quirks here so that a smooth installation procedure for the VF2 emerges. (Perhaps it already exists and I'm just being ignorant.)

Edit: Some clarifications.

Last edited by tripole (Today 15:06:05)

Offline

Board footer