Armbian images are now available for Rock 5b!

Hi, I just downloaded the newest release of Armbian and flashed into the SD card, it boots up fine from the SD Card.
But I wanna install the system into the Samsung PM9A1 SSD,
So I followed the instruction on the armbian page,
partioned the drive and made a ext4 filesystem.
but I got stuck when I tried to boot up from SSD.
I hooked up a serial cable and got this information


Any idea?

see if it helps
More info (Spi to NVME boot from SD Card):
http://www.fieldday.io/armbian-rock5b/

THX for your help, what I did after flash the armbian system image into the sd card is immediately execute the armbian-install command, not upgraded the system, I will try it later :slight_smile:

BTW, the release I am using is Armbian 23

1 Like

Hi, I think that I got the reason why it randomly cannot boot up.
I checked the armbianEnv.txt and found no errors:

verbosity=1
bootlogo=true
overlay_prefix=rockchip-rk3588
fdtfile=rockchip/rk3588-rock-5b.dtb
rootdev=UUID=48f493da-c648-4986-a041-4aeea77c5e01
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

The UUID is set correctly, and it points to the SSD.
but the boot.cmd shows below:

# DO NOT EDIT THIS FILE
#
# Please edit /boot/armbianEnv.txt to set supported parameters
#

setenv load_addr "0x9000000"
setenv overlay_error "false"
# default values
setenv rootdev "/dev/mmcblk0p1"
setenv verbosity "1"
setenv console "both"
setenv bootlogo "false"
setenv rootfstype "ext4"
setenv docker_optimizations "on"
setenv earlycon "off"

We can see that the rootdev is still mmcblk0p1, but it should be nvme0n1p1

After I edited and recompiled it, It finally boot up :slight_smile:

But I still don’t know why I can boot up at first boot after I write the system into the SSD,
boot failed after two reboot operation.

1 Like

I am no longer understanding anything: with the official radxa distros everything works, with the custom ones it doesn’t: for example with armbian there is no video signal, I discovered that the system does not go into a loop, in fact I can connect via ssh, even the ping it is stable. I can’t figure out why it doesn’t start the GUI, it’s incomprehensible.

Hello everyone, I have a clear problem with PD after updating the bootloader on eMMC in February. Before that, I updated it in December 2022 and the power supplies on both boards with PD worked.
Now in apt-cache show linux-u-boot-rock-5b-legacy I don’t see versions from linux-u-boot-legacy-rock-5b_22.11.0-trunk.0126_arm64 when everything worked

I am the only one that have no video post with Armbian images? The system is up and running but no video (I use emmc card). I tried three different PD: official (that bzzz), ugreen 65W, samsung 45W.
Any ideas?
PS: ubuntu 20.04 works fine, ko if I update kernel or s.o. version.

Test image.

2 Likes

Looks great! Thanks for the hard work. I look forward to it being ready for release.

Whom are you thanking? @Googulator or @igorp?

You know where ‘the hard work’ happened, right? Hint: it was not over at Armbian but here

1 Like

How about everyone working on project! It takes a team of effort from multiple walks of SBC life with multiple skills and inputs, as well as public facing people/intities to build and keep project motivation.
Don’t poopoo someone else because they are not doing what you think is the “real” hard work. We NEED ALL the pegs.

2 Likes

To be credible you need to be involved. Testing, measuring and hunting bugs is important too, but its something entirely different. Its mainly done by automation. Once you build it, hard work becomes maintaining it.

Armbian developers are involved into this and as it should be clear, nobody claimed anything - its just a picture of test run and a link to the image that was put together after many many unsuccessful attempts. Thank you for helping educating users. Less disrespectful way would cost you more?

You must have mixed us with people who actually claims board bring up and even removing © from other peoples work on doing no / cosmetic changes to the code. Armbian developers don’t do that.

Hardest and most boring work is anyway keeping this operational and dealing with endless bugs and complains users will come up with years to come. In most cases in exchange for nothing, not even compliment as “developers duty is to keep devices functional, however they can”.

1 Like

Candidly this absolutely shouldn’t have a formal release and only as a user-beware experimental image.

The @Googulator midstream kernel is called midstream for a reason. One should view it as carrying the similar security/performance/stability risks/uncertainties as the BSP kernel, but it’s just much closer to mainline in its heritage.

hello. what brand of nvme disk are you using?

Hi there,
I’m testing “https://github.com/armbian/os/releases/download/23.05.0.0070/Armbian_23.05.0.0070_Rock-5b_lunar_midstream_6.2.0-rc1_minimal.img.xz”.
I like this image. For example KDE with Wayland is working fine. But 2 points are missing a) no sound via headphone barrel b) no WLAN is working
root@rock-5b:~# dmesg | grep -i firmware
[ 0.000000] psci: PSCIv1.1 detected in firmware.
[ 0.130900] arm-scmi firmware:scmi: Enabled polling mode TX channel - prot_id:16
[ 0.130962] arm-scmi firmware:scmi: SCMI Notifications - Core Enabled.
[ 0.130990] arm-scmi firmware:scmi: SCMI Protocol v2.0 ‘rockchip:’ Firmware version 0x0
[ 1.394173] arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active.
[ 1.394868] optee: probe of firmware:optee failed with error -22
[ 4.429816] rtw89_8852be 0002:21:00.0: no suitable firmware found
[ 4.429826] rtw89_8852be 0002:21:00.0: failed to recognize firmware
root@rock-5b:~# lspci
0000:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01)
0000:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963
0002:20:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01)
0002:21:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b852
0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01)
0004:41:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
root@rock-5b:~# ls -l /lib/firmware/rtw89/
total 4056
-rw-r–r-- 1 root root 1423232 Mär 2 14:02 rtw8852a_fw.bin
-rw-r–r-- 1 root root 1188488 Mär 2 14:02 rtw8852b_fw.bin
-rw-r–r-- 1 root root 1532656 Mär 2 14:02 rtw8852c_fw.bin
root@rock-5b:~#
Any hint to solve this? I know this image is in early stages …
Thanks
Andreas

Next one:
software for fan-control isn’t working:
journal -f
Mär 14 20:12:09 rock-5b systemd[1]: Starting fan-control.service - fan control for rock5b…
Mär 14 20:12:09 rock-5b systemd[1]: Started fan-control.service - fan control for rock5b.
Mär 14 20:12:09 rock-5b systemd[1]: fan-control.service: Deactivated successfully.
Mär 14 20:12:12 rock-5b systemd[1]: fan-control.service: Scheduled restart job, restart counter is at 1108.
Mär 14 20:12:12 rock-5b systemd[1]: Stopped fan-control.service - fan control for rock5b.
Mär 14 20:12:12 rock-5b systemd[1]: Starting fan-control.service - fan control for rock5b…
Mär 14 20:12:12 rock-5b systemd[1]: Started fan-control.service - fan control for rock5b.
Mär 14 20:12:12 rock-5b systemd[1]: fan-control.service: Deactivated successfully.
Mär 14 20:12:14 rock-5b systemd[1]: fan-control.service: Scheduled restart job, restart counter is at 1109.
Mär 14 20:12:14 rock-5b systemd[1]: Stopped fan-control.service - fan control for rock5b.
Mär 14 20:12:14 rock-5b systemd[1]: Starting fan-control.service - fan control for rock5b…
Mär 14 20:12:14 rock-5b systemd[1]: Started fan-control.service - fan control for rock5b.
Mär 14 20:12:14 rock-5b systemd[1]: fan-control.service: Deactivated successfully.

@lanefu maybe you’ve more luck explaining to Igor why he should give credit to @Googulator (and to Rockchip and Collabora folks if we want to be fair) when you guys rely completely on someone else’s work. But I know this would be to no avail since Igor always tries to create the impression work would only happen over at Armbian so he can ask for more cash…

Anyway in case any of these famous ‘Armbian developers’ want to help please take at look here: https://github.com/Googulator/linux-rk3588-midstream/issues/3

In case it’s over your head then please simply run sbc-bench -r with Sebastian Reichelt’s settings and then with my tweaked https://transfer.sh/bt4FdB/rk3588-rock-5b-BSP-OPP-tables.dts replacing /boot/dtb/rockchip/rk3588-rock-5b.dtb:

cp -p /boot/dtb/rockchip/rk3588-rock-5b.dtb /boot/dtb/rockchip/rk3588-rock-5b.dtb.bak
dtc -I dts -O dtb -o /boot/dtb/rockchip/rk3588-rock-5b.dtb /path/to/rk3588-rock-5b-BSP-OPP-tables.dts

BTW: sbc-bench can be updated in place with -u.

Ofc. Their work function perfectly since start, its well maintained and it has no bugs. Grow up.

Dear “customer”, thank you for your input. This year probably not, perhaps next. Problems you have kindly complained about 4,3,2 … years ago hasn’t been resolved yet. You always forget about something.

@GinKage now you maybe know what the real problem is. I guess at the same time he started to babble about ‘leadership’ few years ago it really started to get difficult being part of his moronic project any longer… and by ‘his project’ I’m not talking about Armbian and the contributors but the way Igor’s doing all those moronic Igor things.