Are you into #RISCV64? #Ubuntu #Linux provides a really good hardware support for the #StarFive #VisionFive2 board including up-to-date packages and security updates in a long term view.

#risc #risc64 #riscv #rv64

https://gyptazy.ch/misc/starfive-visionfive2-riscv64-board-perfect-ubuntu-support-review/

Current state: 5x #StarFive #VisionFive2 boards on #RISCV in place for production usage:

- Primary Auth NS & NTP
- Secondary NS & NTP
- Webserver (#manpageblog)
- #snac (#Fediverse server) & #synapse (#Matrix chat server)
- #Tor relay node

#risc #riscv64 #risc64

You can find some newer packages for #Debian #Bookworm (which is used by the #VisionFive #VisionFive2 board) than the 2022 snapshot old ones for #RISCV on https://gyptazy.ch. But you can also grab my whole QEMU image to build it yourself or just spawn up a #chroot with #qemu static (qemu-riscv64-static) by running:

mmdebstrap --architectures=riscv64 --aptopt='Acquire::Check-Valid-Until "false"' --include="debian-ports-archive-keyring" sid /srv/riscv64-chroot "deb [trusted=yes] https://snapshot.debian.org/archive/debian-ports/20220616T194833Z unstable main"

cp /usr/bin/qemu-riscv64-static /srv/riscv64-chroot/usr/bin/

chroot /srv/riscv64-chroot/ qemu-riscv64-static /bin/bash

Tags:
#risc #riscv #risc64 #riscv64 #starfive #vision #packages #crosscompile #foss

Tomorrow at work...
"Hey gyptazy, how was your weekend, what did you do?"

I recompiled #Debian #Bookworm (non snapshot) packages for #RISCV. Currently, there're running 7 nodes with QEMU RISC-V images and one native board. Maybe I should simply switch to experimental but I guess in the current situation many new RISCV users will stay on the bookworm snapshot's which has been used as a default by #StarFive for the #VF2 board.

#risc #riscv #riscv64 #risc64 #risc-v #visionfive #visionfive2 #hardware

@lattera@bsd.network @tara@hachyderm.io @stefano@bsd.cafe thank you both for mentioning me and keeping my posts in mind :)

So, when it comes to the #StarFive VF2 board I tried to collect some information in general as well as VF2 specific ones. We also have a #RISCV (#risc #risc64 #riscv64) Matrix chat in the #BSDCafe which you can find here:
#RISCV64:bsd.cafe

You can find more to regarding my initial ideas, reasons and information here: https://gyptazy.ch/misc/switching-from-arm64-to-open-riscv-hardware-architecture/

Some #VisionFive (#VisionFive2) specific things like benchmarks, images (collection) or precompiled software like #snac2 (Fediverse instance server), matrix-synapse (Matrix server), #unixbench etc can be found here:
https://gyptazy.ch/misc/collection-of-images-and-information-for-risc64-board-visionfive2/

Keep in mind that not all OS images may work fully and may lack drivers. For my #FreeBSD one for example you can just boot into memory. Debian runs quite well but still needs a custom kernel (do not upgrade the kernel unless you know what you’re doing). Even RISCV is tier 2 level in FreeBSD many things are missing. Pkg completely, ports is a mess. However, you may find QEMU RISCV images to cross-build stuff from your amd64 or ARM64 machine right here: https://gyptazy.ch/misc/freebsd-14-riscv64-build-box-image-for-qemu/

Here you can find a real life test where the board served for a day my whole website (based on #manpageblog) and some other ones:
https://gyptazy.ch/snac/gyptazy/p/1706078460.746773

Btw, here’s a #neofetch output:
https://gyptazy.ch/snac/gyptazy/p/1707391057.757603

You asked for it!

Here's the #neofetch output on the #StarFive #VisionFive2 board based on #RISCV running #Debian #Linux. If you have any question, feel free to ask.

#risc #riscv64 #openhardware #opensource

Hm, I’m thinking about switching completely my personal servers to #RISCV64 based systems. Why?

Because I can! For real, it’s an awesome new platform, almost no one is using it for production (because of the limited support (especially currently from an OS perspective), knowledge and performance). However, I’m already running some boards in production, some tests I already shared with you (see also summary) and we saw that it’s easily running my workloads - so why not?

So when speaking about „why not“ my first issue is that it would force me to #Linux #Debian instead of #FreeBSD. It would be the first time since 2008 running personal Linux server instead of BSD based ones. It’s not a knowledge problem, I heavily even contribute to a Debian based distribution as a developer, it’s more an aspect of philosophy.

If you’re interested in #riscv (especially the #starfive #visionfive2 board), see also:

* Fediverse with snac: https://gyptazy.ch/snac/gyptazy/p/1706017043.921341
* Weberserver (testrun for a day): https://gyptazy.ch/snac/gyptazy/p/1706078460.746773
* More details: https://gyptazy.ch/misc/collection-of-images-and-information-for-risc64-board-visionfive2/
* Benchmarks: https://browser.geekbench.com/v6/cpu/4566123
* Docs: https://wiki.bsd.cafe/docs:riscv64
* Chat: We also have a chat for RISC related topics in the BSD cafe. Feel free to join us at: #riscv64:bsd.cafe

#risc #risc64 #riscv #riscv64 #bsdcafe

Some more insights behind the #StarFive #VisionFive2 board running on #RISCV64 architecture. Operating systems like #FreeBSD, #Debian & other #Linux distros, #benchmarks and precompiled stuff...

https://gyptazy.ch/misc/collection-of-images-and-information-for-risc64-board-visionfive2/

#risc #riscv #risc64

Alright, here we have my first new #RISCV (#RISC #RISC64) board running #Debian #Linux. I already prepared a #FreeBSD image which will be flashed after work. It’s playtime - thanks to the #Fediverse

Board: #StarFive #VisionFive2 with 8GB RAM

While lacking in available and functional operating systems, I’m already preparing a collection (like my #Vagrant collection) of flashable SD images of #risc-v (#riscv) for the #Starfive #VisionFive2:
#FreeBSD #OpenBSD #Debian #Ubuntu #Alpine #Arch #Gentoo