Project Description

Create openSUSE images (or test generic EFI images) for Arm and RISC-V boards that are not yet supported.

Goal for Hackweek

Create bootable images of Tumbleweed for SBCs that currently have no images available or are untested.

Consider generic EFI images where possible, as some boards can hold a bootloader.

Document in the openSUSE Wiki how to flash and use the image for a given board.

Hack Week 25

Hack Week 24

Hack Week 23

Hack Week 22

Hack Week 21

Resources

Looking for hackers with the skills:

arm64 risc-v sbc opensuse aarch64

This project is part of:

Hack Week 22 Hack Week 21 Hack Week 24 Hack Week 25 Hack Week 23

Activity

  • about 8 hours ago: baldarn liked this project.
  • about 8 hours ago: baldarn disliked this project.
  • 4 days ago: jmodak liked this project.
  • 7 days ago: flonnegren joined this project.
  • 14 days ago: barendartchuk liked this project.
  • 20 days ago: drdavis joined this project.
  • 20 days ago: drdavis liked this project.
  • 21 days ago: avicenzi added keyword "aarch64" to this project.
  • 25 days ago: ph03nix joined this project.
  • about 1 month ago: pvorel liked this project.
  • about 2 months ago: manoknapulamod0934 liked this project.
  • about 1 year ago: a_faerber liked this project.
  • about 1 year ago: gpathak liked this project.
  • about 1 year ago: abergmann liked this project.
  • about 1 year ago: keichwa liked this project.
  • about 1 year ago: ph03nix liked this project.
  • about 1 year ago: avicenzi added keyword "opensuse" to this project.
  • about 1 year ago: ldevulder liked this project.
  • about 1 year ago: mbrugger liked this project.
  • about 1 year ago: flonnegren liked this project.
  • about 1 year ago: mfriedrich liked this project.
  • about 1 year ago: FruityWelsh liked this project.
  • about 1 year ago: pwerneck liked this project.
  • about 1 year ago: baldarn liked this project.
  • almost 3 years ago: clin liked this project.
  • All Activity

    Comments

    • michals
      almost 3 years ago by michals | Reply

      FTR some boards have an onboard flash memory that can be used to store a bootloader such as u-boot or EDK2 which can then load a standard, universal EFI image. I think where possible this way of booting the board should be promoted over building board-specific images.

      • avicenzi
        almost 3 years ago by avicenzi | Reply

        Yes, I agree, but not all have SPI or other memory on board.

    • mfriedrich
      about 1 year ago by mfriedrich | Reply

      I have a few boards which could work with the EFI images: - Radxa Rock 5B - Milk-V Mars, Meles - LicheePi 4A

    • socon
      about 1 year ago by socon | Reply

      Raspberry pi 5?

      • avicenzi
        about 1 year ago by avicenzi | Reply

        The HW enablement team at SUSE is working on the Pi 5, there are a few missing patches upstream that prevent having full support yet in openSUSE AFAIK.

    • gpathak
      about 1 year ago by gpathak | Reply

      Can we get a list of supported and unsupported boards?
      Which all boards are we planning to build the images?
      Is there any official documentation or link to any Wiki etc?
      I have couple of ARM board such as BananaPi-R64, Odroid-C2 (outdated but can still be used for testing)

      • gpathak
        about 1 year ago by gpathak | Reply

        Got it add-emoji https://en.opensuse.org/Portal:Arm https://en.opensuse.org/Portal:RISC-V

        • avicenzi
          about 1 year ago by avicenzi | Reply

          If the board is not on the above pages, it is not supported usually. Boards that support UEFI boot might not be on the list, and might work, but if the board is not on the list and it does work, it would be nice to add to the list.

          There's no list of boards that we plan to support, you are free to work on any boards you have.

    • ph03nix
      25 days ago by ph03nix | Reply

      I'll join this project and will continue to work on my Mars-V CM. Also related: https://hackweek.opensuse.org/25/projects/tumbleweed-on-mars-cm-risc-v-board

      • avicenzi
        21 days ago by avicenzi | Reply

        I also have a few RISC-V boards to test, but not the Mars-V.

    • JCayouette
      21 days ago by JCayouette | Reply

      I have several RPi 5's, and Orange Pi 5 Plus (Rockchip RK3588) and some older models. Happy to test or help out in any way I can. Been hoping for such a port for a long time!

      • avicenzi
        21 days ago by avicenzi | Reply

        The RPi 5 has an openSUSE image that you can test.

    • flonnegren
      3 days ago by flonnegren | Reply

      I created a project in OBS for building a tumbleweed image for the Milk-V Jupiter board. Right now it does not even build, but I will see how far I can get with u-boot, opensbi and the kernel.

    • drdavis
      2 days ago by drdavis | Reply

      I just started assembly of my SiFive Premier P550 System and will see how far I can get on getting TW working on it. I also have a SiFive HiFive Unmatched that I assembled some time ago. I have a replacement Rev B board that I need to replace the older motherboard, and get a current TW image for.

      Also, updated the Hack Week project page with this round of systems.

    • ph03nix
      2 days ago by ph03nix | Reply

      I spent the last two days trying to get the Mars CM working. The kernel is stuck when setting up the CPU - I also tried the Fedora images. Looks like the upstream support was never that good, and I think this is beyond what is reasonable to do.

      I give up on the Mars CM enablement.

    • drdavis
      2 days ago by drdavis | Reply

      Sad to hear about the Mars CM situation.

    Similar Projects

    Reassess HiFive Premier P550 board (for RISC-V virtualization) by a_faerber

    Description

    With growing interest in the RISC-V instruction set architecture, we need to re-evaluate ways of building packages for it:

    Currently openSUSE OBS is using x86_64 build workers, using QEMU userspace-level (syscall) emulation inside KVM VMs. Occasionally this setup causes build failures, due to timing differences or incomplete emulation. Andreas Schwab and others have collected workarounds in projects like openSUSE:Factory:RISCV to deal with some of those issues.

    Ideally we would be using native riscv64 KVM VMs instead. This requires CPUs with the H extension. Two generally available development boards feature the ESWIN 7700X System-on-Chip with SiFive P550 CPUs, HiFive Premier P550 and Milk-V Megrez. We've had access to the HiFive Premier P550 for some time now, but the early version (based on Yocto) had issues with the bootloader, and reportedly later boards were booting to a dracut emergency shell for lack of block device drivers.

    Goals

    • Update the boot firmware
    • Test whether and how far openSUSE Tumbleweed boots

    Results

    • Boot firmware image 2025.11.00 successfully flashed onto board
      • Enables UEFI boot in U-Boot by default
      • U-Boot's embedded Flat Device Tree is lacking a timebase-frequency, required for recent (6.16.3) mainline kernels (panic leading to reset, visible via earlycon=sbi)
    • Tested eswin/eic7700-hifive-premier-p550.dtb from Ubuntu 2025.11.00 image
      • Allows to boot past the above panic, but times out in JeOS image while waiting for block device, dropping to dracut emergency shell
      • No devices shown in lsblk -- 6.16 appears to be lacking device drivers still

    Resources


    pudc - A PID 1 process that barks to the internet by mssola

    Description

    As a fun exercise in order to dig deeper into the Linux kernel, its interfaces, the RISC-V architecture, and all the dragons in between; I'm building a blog site cooked like this:

    • The backend is written in a mixture of C and RISC-V assembly.
    • The backend is actually PID1 (for real, not within a container).
    • We poll and parse incoming HTTP requests ourselves.
    • The frontend is a mere HTML page with htmx.

    The project is meant to be Linux-specific, so I'm going to use io_uring, pidfs, namespaces, and Linux-specific features in order to drive all of this.

    I'm open for suggestions and so on, but this is meant to be a solo project, as this is more of a learning exercise for me than anything else.

    Goals

    • Have a better understanding of different Linux features from user space down to the kernel internals.
    • Most importantly: have fun.

    Resources


    Tumbleweed on Mars-CM (RISC-V board) by ph03nix

    RISC-V is awesome, Tumbleweed is awesome, chocolate cake is awesome. I'm planning to combine all of them in one project.

    Project Description

    I recently purchased a MILK-V Mars CM and managed to setup it up already using Debian Linux. My project for this Hackweek is to see how far I can get to run Tumbleweed on this compute module board.

    Goal for this Hackweek

    • Run Tumbleweed on the Compute Module

    Resources

    • http://milkv.io/mars-cm
    • https://en.opensuse.org/HCL:VisionFive2


    Add Qualcomm Snapdragon 765G (SM7250) basic device tree to mainline linux kernel by pvorel

    Qualcomm Snapdragon 765G (SM7250) (smartphone SoC) has no support in the linux kernel, nor in u-boot. Try to add basic device tree support. The hardest part will be to create boot.img which will be accepted by phone.

    UART is available for smartphone :).