VisionFive 2 official OpenSUSE image

OpenSUSE has updated their JeOS image on VisionFive 2. Thanks for OpenSUSE team!

Wiki page: https://en.opensuse.org/HCL:VisionFive2
Image page: https://build.opensuse.org/project/show/devel:RISCV:Factory:Contrib:StarFive:VisionFive2

6 Likes

I would like to try this out, but the server download speed is ~40 KiloBytes/Second.
Any chance of getting a flashable .img file in my lifetime?
[Sorry, not yet a SUSE user].
Thanks for any help.

https://mirrorcache-us.opensuse.org/repositories/devel:/RISCV:/Factory:/Contrib:/StarFive:/VisionFive2/images/openSUSE-Tumbleweed-RISC-V-JeOS-starfivevisionfive2.riscv64.raw.xz

Manually changing the mirror address may help

https://en.opensuse.org/openSUSE:Mirrors

If you would like to use a different mirror or want to see a complete list of all mirrors which you could download a file from, go to mirrors.opensuse.org.

Thanks you! I am getting ~725 KB/Sec on
https://mirrorcache-eu.opensuse.org

OK. Next speed bump.
flashed raw image to SD & booted
stopped boot and did
fdt addr ${fdtcontroladdr}; fdt rsvmem add 0x40000000 0x00001000
typed boot


Loading Linux 6.2.0-rc8-14-default …
Loading initial ramdisk …
EFI stub: Booting Linux Kernel…
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services…
clk u5_dw_i2c_clk_core already disabled
clk u5_dw_i2c_clk_apb already disabled
sbi_trap_error: hart0: trap handler failed (error -2)
sbi_trap_error: hart0: mcause=0x0000000000000005 mtval=0x0000000040059060
sbi_trap_error: hart0: mepc=0x00000000400047fc mstatus=0x0000000200001800
sbi_trap_error: hart0: ra=0x0000000040009972 sp=0x0000000040058f10
sbi_trap_error: hart0: gp=0x0000000000000000 tp=0x0000000040059000
sbi_trap_error: hart0: s0=0x0000000040058f20 s1=0x0000000040059000
sbi_trap_error: hart0: a0=0x0000000040059060 a1=0x0000000000000002
sbi_trap_error: hart0: a2=0x0000000000000000 a3=0x0000000000000000
sbi_trap_error: hart0: a4=0x0000000000000001 a5=0x0000000040059060
sbi_trap_error: hart0: a6=0x00000000400590a8 a7=0x0000000000000000
sbi_trap_error: hart0: s2=0x0000000040023188 s3=0x0000000000000000
sbi_trap_error: hart0: s4=0x0000000000000000 s5=0x0000000040027000
sbi_trap_error: hart0: s6=0x0000000040027020 s7=0x0000000000000000
sbi_trap_error: hart0: s8=0x000000000000001c s9=0x00000000400476a8
sbi_trap_error: hart0: s10=0x0000000000000000 s11=0x0000000000000000
sbi_trap_error: hart0: t0=0x0000000000000000 t1=0x0000000000000000
sbi_trap_error: hart0: t2=0x0000000000000000 t3=0x0000000000002000
sbi_trap_error: hart0: t4=0x0000000000000000 t5=0x0000000000000000
sbi_trap_error: hart0: t6=0x0000000000000000

The u-boot-spl.bin.normal.out and visionfive2_fw_payload.img firmware for openSUSE is different from official, the first one is available in https://download.opensuse.org/repositories/devel:/RISCV:/Factory:/Contrib:/StarFive:/VisionFive2/standard/noarch/visionfive2-firmware-2023.01-5.1.noarch.rpm , but I can’t find the visionfive2_fw_payload.img, so probably need to compile it following the instruction on the Wiki page.

Seems they are using upstream uboot+patches under review

3 Likes

I’m having the same problem, also searched for fw payload but didn’t find it.
The workaround I found was comment 3 and 4 in this thread, both work.
https://bugzilla.opensuse.org/show_bug.cgi?id=1208173#c4

2 Likes

Verify this works for me to boot into CLI. Many thanks! [name:password=root:linux]

load mmc 1:3 ${fdt_addr_r} /boot/dtb/jh7110-starfive-visionfive-2-va.dtb

fdt addr ${fdt_addr_r}; fdt rsvmem add 0x40000000 0x00001000

boot

yes, that also works.
now to the next question, where’s the network devices ?

Finally received the V5-2, and will be putting Fedora on it, but needed the Uboot/GRUB capability from OpenSUSE…
The latest images still have the ‘sbi_trap_error’ fault, and to avoid having to manually type the fix (see above) I managed to cobble together a uEnv.txt that works:

setupfdt=load mmc 1:3 ${fdt_addr_r} /boot/dtb/jh7110-starfive-visionfive-2-v1.3b.dtb; fdt addr ${fdt_addr_r}; fdt rsvmem add 0x40000000 0x00001000;
uenvcmd=run setupfdt


This should go in /boot , as usual…

With the latest release ‘openSUSE-Tumbleweed-RISC-V-JeOS-starfivevisionfive2
.riscv64-2023.03.20-Build11.61’ networking seems to work OK:

[ 19.206204] starfive-dwmac 16040000.ethernet end1: Register MEM_TYPE_PAGE_POOL RxQ-0
[ 19.207323] starfive-dwmac 16040000.ethernet end1: PHY [stmmac-1:00] driver [YT8531 Gigabit Ethernet] (irq=POLL)
[ 19.207370] starfive-dwmac 16040000.ethernet end1: No Safety Features support found
[ 19.207393] starfive-dwmac 16040000.ethernet end1: IEEE 1588-2008 Advanced Timestamp supported
[ 19.207691] starfive-dwmac 16040000.ethernet end1: registered PTP clock
[ 19.208214] starfive-dwmac 16040000.ethernet end1: configuring for phy/rgmii-id link mode
[ 23.255124] starfive-dwmac 16040000.ethernet end1: Link is Up - 1Gbps/Full - flow control rx/tx

1 Like

Tried this with a 64GB eMMC card, but the ‘fix’ failed:
StarFive # load mmc 0:3 ${fdt_addr_r} /boot/dtb/jh7110-starfive-visionfive-2-v1.3b.dtb
ERROR: reserving fdt memory region failed (addr=40000000 size=80000 flags=4)