gyptazy.ch is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
I’ve been bullish on RISC-V for quite some time for a variety of reasons.
One issue that I also expected is unfolding in real time. The West wants to control Chinese access to technology, but how do you restrict access to open source hardware?
Need to update Gunther at some point.
#VisionFive2 #RISCV #riscv64 #riscvsbc #raspberrypi #raspberrypi3 #raspberrypi5 #opensourcehardware #sbc #singleboardcomputer
#QEMU 9.0 Released with #RaspberryPi 4 Support, LoongArch #KVM Acceleration Support, and New #RISCV Features https://9to5linux.com/qemu-9-0-released-with-raspberry-pi-4-support-loongarch-kvm-acceleration
@phoronix This was the impetus I need to try out the #RISCV port of #NetBSD (https://wiki.netbsd.org/ports/qemu_riscv/) It was hands-down the easiest OS to bring up. Download and decompress to images and run one command. Lovely.
Never worked with #ansible before and I need it for an upcoming project... so I'm using my #VisionFive2 to manage all other #SBC in my home. Even reinstalled my old #raspberrypi 3 with #openSUSE to have a different OS and system in the network xD
The way things look right now I'll have a lot of time on my hands to figure this out...
#RISCV #riscv64 #riscvsbc #ARM #Linux
FreeBSD OpenJDK Contract
Various contracts, full- and part-time:
— bhyve hypervisor kernel improvements
— desktop usability
— developer tools such as LLD
— hardware support on new ARM and RISC-V devices
— installer
— jails – usability/orchestration/OCI-compatibility
— networking
— packaging – including package base (pkgbase)
— …
<https://freebsdfoundation.org/open-positions/>
#FreeBSD #OCI #JDK #OpenJDK #ARM #RISCV #bhyve #LLD #pkgbase #orchestration #Java
🦾 SiFive HiFive Premiere P550 high-performance RISC-V dev board coming this summer | Liliputing
「 The upcoming SiFive HiFive Premiere P550 is powered by an Eswin EIC7700 processor that combines four SiFive P550 CPU cores with a GPU, NPU, and support for PCIe Gen 3, among other things. The board should be available to purchase from Arrow Electronics in July, 2024 」
Current set of RISC-V boards ... From left to right - the first three are 32-bit, the others 64-bit. Most of these aren't used as much as they should be!
- SiFive HiFive1-A01 (Freedom E310)
- Base board for Doctor Who HiFive inventor kit (FE310-G002)
- Espressif ESP32-C3 microcontroller+LCD
- MangoPi D1 (Alibaba XuanTie C906) - The clear case it's in was for a Pi Zero
- HiFive Unleashed (Quad core Freedom U540)
- Beagle-V prototype (Dual core JH7100)
- VisionFive 2 (Quad core JH7110)
#riscv
Apparently I accidentally removed my post about the #RISCV build of #OpenJDK #Adoptium Eclipse #Temurin 21.0.1+12 from a few weeks back so I'm reposting:
This is an early access build - not intended for production use:
wget -q -O - https://api.adoptium.net/v3/binary/version/jdk-21.0.1+12.1-ea-beta/linux/riscv64/jdk/hotspot/normal/adoptium | tar xfz -
It needs libatomic1 (Debian/Ubuntu) or libatomic (Fedora) to avoid a runtime error
In a docker container you may get: "RISCV_FLUSH_ICACHE not available". To fix, start the container with "--security-opt seccomp=unconfined"
No-one would have believed it if we posted this yesterday, so today we are announcing that Eclipse #Temurin 21 and 22 are available as a GA headless release on #RISCV! #openjdk #java
https://adoptium.net/en-GB/blog/2024/04/eclipse-temurin-21-and-22-available-on-riscv/
Thanks to @ludovic_dev and others at RISE for getting us here 🙂
You can also install it via the @jbangdev tool. Set JBANG_DEFAULT_JAVA_VERSION=21 first to get the GA version
See also: "Lessons from porting" and the "managed runtimes" talks from #FOSDEM #FOSDEM2024 at https://video.fosdem.org/2024/aw1126/
ohhhh gosh… more RISC-V for FreeBSD!
💘 more cores 💘 more ram 💘 more ports 💘 more more more 💘
going to validate whether this SO-DIMM format will work in my TuringPi2, but generally underlying all technical plans, a vast majority of my home-lab acquisitions are solely because I want it and it's fun!
💖👩🏼💻💁🏼♀️🤩😌
#riscv #embedded #freebsd #lichee #engineering #homelab #happiness #hardware #oss #womeninstem #toomanyhashtags
🔐 Linux 6.9 Adds New RISC-V Vector-Accelerated Crypto Routines - Phoronix
「 RISC-V with Linux 6.9 implements support for more vector-accelerated crypto routines. Among the work is RISC-V vector accelerated AES-{ECB,CBC,CTR,XTS}, ChaCha20, GHASH, SHA-256, SHA-384, SHA-512, SM3, and SM4 algorithms 」
Is there *any* physical RISC-V hardware at all that actually implements the Svpbmt / page-based memory types? It seems like all the cores I can find with MMUs don't do this, maybe because most of the cores have their original prior to that extension being approved? But there's code for it in Linux, so somebody must have hardware, right?
#riscv
Check this out, a #RISCV CPU made of just simple components, no FPGAs or ASICs.
I just played snake on it. 🥳
It implements RV32I.
#amd64 offers the best support and is fast.
#arm64 is very efficient and also very fast.
#riscv is amazing & exciting (but slow with my current hw, but I can deal with it)
While amd64 & ARM64 work perfectly fine with #FreeBSD, the #RISCV hardware support (beside #qemu stuff) is still very limited. Currently, #Ubuntu and #OpenBSD work very well there.
#amd64 offers the best support and is fast.
#arm64 is very efficient and also very fast.
#riscv is amazing & exciting (but slow with my current hw, but I can deal with it)
While amd64 & ARM64 work perfectly fine with #FreeBSD, the #RISCV hardware support (beside #qemu stuff) is still very limited. Currently, #Ubuntu and #OpenBSD work very well there.
Currently performing a huge update on my #VisionFive2 for good measure. Lets see if it boots up again once everything is done xD
#RISCV #riscv64 #riscvsbc #crux #irradium #linux #opensourcehardware
Just to give you a sense of scale, that's this board next to a fully equipped #esp32 D1 Mini, an #esp32s2 dev board and the #VisionFive2 🥹
#esp32c3 #RISCV #riscv32 #microcontroller
This little thing literally has it's own github repository. I was already wondering where to get documentation for it but here we are:
https://github.com/01Space/ESP32-C3-0.42LCD
#esp32c3 #esp32 #riscv #riscv32 #microcontroller #makerspace
So there is small, there is tiny and then there is smol 🥹🥺
#esp32c3 #esp32 #RISCV #riscv32 #makerscene #microcontroller
Played around with the MILK-V Duo this morning. It certainly feels snappier than the Mango Pi, although that might be because it's running a buildroot image and not a full distro. Idle it uses about 75mA, running `while true; do echo Hello; done` over an ssh connection it pulls 100mA. #milkv #riscv #linux
Looks like #scaleway has a #riscv offering now - the first known cloud provider with them as far as I know - and a decent choice by using TH1520-based systems (until good boards with vector 1.0 support appear)
- https://bret.dk/scaleway-risc-v-testing/#Benchmarking-the-RISC-V-TH1520
- https://labs.scaleway.com/en/em-rv1/
@gyptazy
kannst jetzt auch auf #RISCV hosten ;-)
The world's first RISC-V servers available in the cloud.
https://labs.scaleway.com/en/em-rv1/
"The PolarFire SoC Discovery Kit is centered around a quad-core, 64-bit RISC-V processor, optimized for Linux and real-time applications, and a PolarFire MPFS095T SoC FPGA with 95K Logic Elements. The kit also includes 1 GB of DDR4 memory and a microSD connector, ensuring solid performance and flexible storage options for various applications."
🧲 Milk-V Duo S: Dual-Core RISC-V SBC Open for Pre-Order Starting at $11.00
— linuxgizmos.com
"This dual-core design offers flexibility and performance for embedded computing. Scheduled to ship in March 2024, this board has improved specifications and features compared to the Duo Classic, and it supports both Linux and FreeRTOS operating systems."
https://linuxgizmos.com/milk-v-duo-s-dual-core-risc-v-sbc-open-for-pre-order-starting-at-11-00/
Heh never knew #RISCV #assembly was such a relaxing thing to do before a #halfmarathon xD
Looking for a RISC-V single board computer with Open Source RISC-V implementation
https://github.com/suryakantamangaraj/AwesomeRISC-VResources?tab=readme-ov-file#cores
Discussions: https://discu.eu/q/https://github.com/suryakantamangaraj/AwesomeRISC-VResources?tab=readme-ov-file%23cores
So put my #VisionFive2 where it belongs xD
Now the actual work can start 🧐 😆
#RISCV #riscv64 #sbc #opensourcehardware #linux #StarFive #riscvsbc
So looks like this could be the final incarnation of my #VisionFive2
Put an active cooler on top using blu tack which also makes this really silent 😶🔕
Currently trying to update the system which failed the past two days simply because it took too long, but now since it doesn't thermal throttle anymore it should go through.
Stays nice and cool at 43°C under 100% load on all cores
#RISCV #riscv64 #riscvsbc #sbc #OpenSOC #OpenSourceHardware #makerdon
Since a friend of mine has access to a free of charge 3D printer, courtesy of the German tax payer (us), I got myself a nice case printed for the #VisionFive2 .
Have to add some active cooling on top which will make it look less cool, but otherwise it's running at around 58°C with just the passive cooler and over 65 when under load.
#RISCV #riscv64 #sbc #starfive #OpenSourceHardware
https://gyptazy.ch/misc/starfive-visionfive2-riscv64-board-perfect-ubuntu-support-review/
- Primary Auth NS & NTP
- Secondary NS & NTP
- Webserver (#manpageblog)
- #snac (#Fediverse server) & #synapse (#Matrix chat server)
- #Tor relay node
gcc: internal compiler error: Segmentation fault signal terminated program cc1
Do I have encountered a hardware issue?
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
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
@lattera It's not a kernel config, but release config which you should seek for. GERERICSD for RISC-V uses GENERIC kernel.😉
https://cgit.freebsd.org/src/commit/release?id=a0b9e2e854027e6ff61fb075a1309dbc71c42b54
#FreeBSD #RISCV
@lattera It's not a kernel config, but release config which you should seek for. GERERICSD for RISC-V uses GENERIC kernel.😉
https://cgit.freebsd.org/src/commit/release?id=a0b9e2e854027e6ff61fb075a1309dbc71c42b54
#FreeBSD #RISCV
The Firmware update on my #VisionFive2 worked really well actually. I didn't adjust the version strings though so the openSBI now shows the board and build date instead of 1.4 or w/e the latest but it's fine.
Now let's hope Amazon delivers the new SD cards and if they work I can finally continue to dabble around with other systems but the standard #debian image 😅🙏🏻
#RISCV #riscv64 #sbc #OpenSourceHardware #starfive
In case anyone was wondering I'm still working on my #VisionFive2
Currently building a new firmware image and waiting for a new SD card since one of my issues apparently is that the second SD card I have here simply doesn't work with the device... or my laptop for that matter
#riscv #riscv64 #StarFive #opensourcehardware #opensource #debian #slackware #singleboardcomputer
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
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
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
@gyptazy Good to see it running different distros, is Debian well supported? Have not really even looked at what level of support for #riscv is there from the well known distros...
What I really want to see is #HaikuOS neofetch output for this board. This might not be perfectly accurate since I am no Haiku historian but I think it might well be the first SBC and even non-x86 computer ever that has a full install of Haiku up and running in a usable state.
Shall post a screenshot myself when I get my #visionfive2 if nobody else does :)
Isn't that the prettiest thing you've ever seen? 😆
So the developer of the build released a new patch with a newer kernel version and from the sound of it that one should fix most of the issues I'm still facing so... lets see how that works out tomorrow.
#RISCV #riscv64 #VisionFive2 #StarVision #slackware #slarm64 #singleboardcomputer
I've also blacklisted the repository kernel and I'll keep working on figuring out how to make this work in a more mainstream way.
Thing with these #RISCV boards is that they can't just run on a general distro... I believe they always need a specific distro tailored to each specific board considering how many issues you get with uboot and openSBI loading the actual image
So I've reimaged my SD card and... managed to brick it again with a custom kernel update. HOWEVER I managed to fix it again by pointing to the right image file for the board... this is quite a learning experience xD
#slackware #slarm64 #RISCV #riscv64 #StarFive #VisionFive2
Since the #VisionFive2 is currently located in my bedroom running updates (for 3 hours now and counting) I thought I could just connect to it from my Windows PC and see how things are going xD
#Slackware #RISCV #riscv64 #singleboardcomputer #linux #LinuxOnRISCV
So this went... Pretty smooth, thought the beginning would cause a heck of a lot more issues. Now onwards to the actual issues 😅🤣
(Please ignore the dirty USB-C cable 😵💫)
#RISCV #riscv64 #VisionFive2 #starfive #slackware #singleboardcomputer #OpenSource
So that worked... better than I expected. ^^'
WIFI still doesn't work though which might be a driver thing? This one came with an external wifi card ^^'
#riscv #riscv64 #visionfive2 #starfive #slackware
Let's get this party started 🥹🤞🏻
#RISCV #riscv64 #VisionFive2 #starfive #singleboardcomputer
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
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
Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:14:riscv64/quarterly, please wait...
pkg: Error fetching http://pkg.FreeBSD.org/FreeBSD:14:riscv64/quarterly/Latest/pkg.txz: Not Found
A pre-built version of pkg could not be found for your system.
FINALLY!
We just *fully* booted into #Linux on the #VisionFive2 #RISCV board using #oreboot as #firmware and a u-root rootfs. 🧑💻
This took quite a while again and I had needed some breaks here and there. Go 1.21RC2 has the necessary alignment checks for this to work without too much performance penalty otherwise caused if Linux or (even worse!) oreboot handled this.
In other news, this is a vast improvement to what OpenSBI offers. Less hacks, a cleaner architecture, and IT WORKS! 🥳
https://gyptazy.ch/misc/collection-of-images-and-information-for-risc64-board-visionfive2/
Attached you can find the #Grafana metrics and the system wasn't bothered in any way... But I also need to say, that everything is running in a very optimized way with a really low footprint in all ways. Thank you all (it were more than 20 people over the whole day) for testing, stress testing and your feedback I got during the day. The next steps will result in replacing ns[01,02] and ntp[01,02] (low performance) with #RISCV (#RISC #RISC64) boards. ns[03,04] and ntp[03,04] will remain on ARM architecture until everything is running stable. Guess, you will see some more RISC64 related content soon - stay tuned!
Board: #StarFive #VisionFive2 with 8GB RAM
@gyptazy @frankenmichl wobei...die Sourcen für RISCV Prozessoren bzw Evalboards sind doch nicht zwangsläufig verfügbar oder? Glaube nicht dass #RISCV nur unter der GPL verfügbar ist 😉
@gyptazy @frankenmichl wieso eigentlich n #RISCV?
My last two orders never arrived, so maybe someone can recommend something? Thanks!
Ed Maste, Senior Director of Technology at The FreeBSD Foundation, discusses the rapidly-evolving interplay between hardware, cybersecurity, open source, and instruction set architectures.
<https://hackernoon.com/the-cybersecurity-battle-has-come-to-hardware>
#RISCV #Arm #Morello #CHERI #CheriBSD #hardware #ISA #security #cybersecurity #University #Cambridge #SRI #FreeBSD