fraz0815

JFYI, collabora started building mesa packages - see https://gitlab.collabora.com/hardware-enablement/rockchip-3588/pkg/mesa That should be very convenient and easy to install in the near future.

Basic tool to change screen orientation and its touch input on gnome wayland desktops. Built for Gnome Wayland and displays without automatic touch input rotation after orientation change. Sadly xrandr and xinput are things of the past in times of wayland. And since I mounted a FHD touchscreen to my rock-5b which can be rotated, this caused some trouble for me. Mabye useful fur other people mounting displays with touch support on their SBC's in crazy spots 😛 Basically it's just a combination of gnome-randr.py and creating a udev rule with calibration matrix. Fun project to test out chatGPT 😀 https://github.com/fraz0815/gptouch

Just stumbled over another chromium fork: https://github.com/Alex313031/Thorium Forum search did not show any entries, so I thought I might share. The arm64 builds (for raspberry though) works great, it even has googly sync, widevine etc, check describtion for more info. It works out-of-the-box on legacy rock-5b jammy gnome images with liujianfeng1994 ppa enabled. For installation/updates one could also use: wget https://dl.thorium.rocks/debian/dists/stable/thorium.list sudo mv thorium.list /etc/apt/sources.list.d/ sudo apt update sudo apt install thorium-browser I usually like to test https://paveldogreat.github.io/WebGL-Fluid-Simulation/ which also runs smooth with webgl on the rock-5b. This might be a good choice, till upstream support makes it easier to find a up2date browser with gpu support.

Are AI generated (stable-diff) pictures allowed? Copyright is quite unclear afaik. This post can be deleted and the answer maybe put in first post for better overview.

imho android gpu drivers are often more mature for gaming/emulation.

Rock Pi-4B - Armbian_23.05.1_Rockpi-4b_jammy_current_6.1.30_gnome_desktop.img installed to emmc: logs wlan, hdmi, nvme working Rock-5B - Armbian_23.05.1_Rock-5b_jammy_legacy_5.10.160_gnome_desktop.img Took me a while to boot from SD, was using an older 23.05-trunk version. Even 'sudo dd if=zero.img of=/dev/mtdblock0' with radxa zero.img would continue to boot happily from nvme instead of sd, changed armbianEnv.txt to sd root, updated bootloaderon mtd -> worked. besides mtd being a mystical thing for me, almost anything worked: installed to mtd+nvme: logs using btrfs on nvme + mtd did not work (don't know if supported, but installer lets you pick it). performance with panfrost ppa's enabled is absolutely stunning. Btw, this time for testing I used my 45W PD PSU (+ PD C<->C Cable 60W) instead of fixed 5V@4A w/o errors and activated the max 12V PD option in armbian-config just for fun. Sensors report ed in0: 12.00 V (min = +12.00 V, max = +12.00 V) curr1: 1.50 A (max = +1.50 A) and had no reboots or whatsoever.

Okay, somehow i got lost between the repos, next-gen and 150balbes (. Thanks, let's find out out where I went wrong and what else I might pulled 🙂

Currently we get 'sduuid' in form of [[ -z $sdblkid ]] && sdblkid=$(blkid -o full /dev/mmcblk*p1) # 3 - Extract the UUID from $sdblkid via regex: sduuid=$(echo "$sdblkid" | sed -nE 's/^.*[[:space:]]UUID="([0-9a-zA-Z-]*)".*/\1/p') which outputs only UUID 78cdc7b8-0f2e-4444-ba7c-38aa26198de1 This is fine, as long as we use it correctly afterwards, but everytime we modifify fstab, echo "${sduuid} /media/mmcboot ext4 ${mountopts[ext4]}" >> "${TempDir}"/rootfs/etc/fstab echo "/media/mmcboot/boot /boot none bind 0 0" >> "${TempDir}"/rootfs/etc/fstab which results in # <file system> <mount point> <type> <options> <dump> <pass> tmpfs /tmp tmpfs defaults,nosuid 0 0 78cdc7b8-0f2e-4444-ba7c-38aa26198de1 /media/mmcboot ext4 defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 /media/mmcboot/boot /boot none bind 0 0 UUID=52f9b8a6-b6ab-4e81-a362-5c4ca041d539 / ext4 defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 Missing "UUID=" and prevents booting correctly. But we cannot simply change sduuid, because on other steps it is used correctly. Maybe make clear which variable has the form of "UUID=XXXXX-XXX-XXXX" in their name, for better understanding, like sduuid for only UUID ("blabla-bla") and sdwuuid für "UUID=blabla-bla". Or use the lazy mode with a check before we modify fstab and add "UUID" as simple string. Example log

Well, this isn't quite the recommendation (afaik, did something change from the 5V / 4A Type C?). Power Supply is absolutely critical during boot times, and even 5V/3A was not enough when running a desktop, mentioned many many times. I also had to learn this the hard lesson 😉 Try to get 5V/4A Type C to be sure. What happened to me one time after installation was a faulty line in /etc/fstab was XXXX_EXAMPLE_UUID / ext4 defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 instead of UUID=XXXX_EXAMPLE_UUID / ext4 defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 which you could check. @balbes150 Did you compile mesa from here for kernel 6.2 builds: https://gitlab.freedesktop.org/panfrost/mesa/-/tree/panfrost/v10-wip , I guess this was https://gitlab.com/panfork/mesa (branch csf) used for legacy kernel?

pipi, I think you should get a correct PSU without PD with 5V and 4A, like in the picture. Then start from scratch with erasing mtd/nvme with dd. Without this sort of PSU you will always run in possible conflicts which are hard to debug.

Some news about the rock5b + usb2 + uboot. https://www.collabora.com/news-and-blog/blog/2023/04/27/radxa-rock-5b-usb20-host-in-u-boot/ One of the patches seems nice:

Thanks for your long and detailed answer, I suspected something devastating like that 😀 glmark output was just for comparison, dmesg has a lot of errors, so never thougt it would win a price (even thoug Gnome runs smooth). I am willing to write a FAQ/wiki regarding Rock5B + PSU + MTD + NVME after switch to armbian-next/main is done.

@balbes150 Have you seen the rebornOS (arch based) image for rock5b? It's using radxa's SPI (and erasing MTD before with zero.img) detailed here, and then simply flashing the OS img file to nvme. This gets even grub installed, no clue if grub is really usable. Maybe there is something useful for your work to explore there. gl2mark2-es2-wayland on gnome: Just wondering, can your new version "20230219 with direct support for launching from USB" launch theoretically totally different images, like rebornos? What requirements would those other images have to include?

" extlinux.conf" Thats the only thing missing now for official armbian builds (with SPI support) for the rock-5b I think: https://github.com/armbian/build/blob/master/config/boards/rock-5b.wip

At the moment, SPI boot is only working with builds from here: Butt will sure be ported to armbian in future.

Of course it's far from perfect, but can be used. I remember the start of rk3399 boards, that was pretty bad in comparison to today. ARM64 and panfrost really made some serious progress. JFYI, wayland progress on gnome was always more advanced than KDE's (and only choice if you wanted working wayland DE besides sway etc)

When adding the ppa's for 3D accleration, there a more steps involved, which are printed out once and can be missed. So far desktop and chromium are running great, even wayland.

Power Supply with PD: "ALLNET USB Ladegerät Quick Charge® PD Power Supply 45 Watt 1x Typ C**EU PLUG**" with these outputs USB-C 5V/3A, 9V/3A, 12V/3A, 15V/3A, 20V/2,25A (45W) bought here. Description is wrong in the shop. Didn't work with old random Type C <-> Type C Cable, ordered this cable which should support up to 60W and worked. lars@rock-5b:~$ sensors tcpm_source_psy_4_0022-i2c-4-22 Adapter: rk3x-i2c in0: 20.00 V (min = +20.00 V, max = +20.00 V) curr1: 2.25 A (max = +2.25 A) I have the 8GB Ram Board, tools like free oder htop show 7.5 GB. I haven't done very much testing yet, but seems to work: Installed Armbian_23.02.0-trunk_Rock-5b_jammy_legacy_5.10.110_xfce_desktop from SD to SPI and nvme partition 1 (2 partitions in total on drive). Removed SD -> everything good. Just used Armbian_23.02.0-trunk_Rock-5b_sid_legacy_5.10.110 for testing on SD, and it booted 🙂 Took a while and led was flashing and turning on/off wildly, thought it bootloops (running my boards mostly headless). but after a while it was ready and ssh'ing worked as usual. Minor issues: Kernel reports Linux 5.10.110-station-m4 motd-news.service and speech-dispatcherd.service are failing on jammy xfce. :edit In total i tested about 5 power supplys which I had laying around, only one booted (5V/3A) but had lots of stability issues.

Installed with armbian-install to SPI+NVME and works perfectly. Thanks!

Sounds great! Am I missing the download link for 20221210? I can build myself, branch media-20221210 correct?

@whitefox I ran into same problems. When 'sensors' reports only in0: 5.00 V (min = +5.00 V, max = +5.00 V) curr1: 0.00 A (max = +0.00 A) emmc + nvme stopped working reliable together. I solved most of my problems with buying an new PSU AND a certified 60W USB Type C to Type C Cable. Random old Type C to Type C cable was unreliable. Some old non-Type C 5V/2A PSU did work, but only as long as i did not use emmc, sd + nvme at the same time, sensors reported same values Here is a incomplete list about PSU's and their possible boot options: https://wiki.radxa.com/Rock5/5b/power_supply I bought a PSU from ALLNET with: USB-C 5V/3A, 9V/3A, 12V/3A, 15V/3A, 20V/2,25A (45W) https://shop.maker-store.de/single-board-computer/zubehoer/weiteres-zubehoer/3763/rock-pi-4-zbh.-power-adapter-pd-netzteil-45-watt-eu-plug + + 60W cable https://www.amazon.de/gp/product/B09YHHNNCG/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1&language=en_GB in0: 20.00 V (min = +20.00 V, max = +20.00 V) curr1: 2.25 A (max = +2.25 A) So far I am very impressed about performance vs rk3399, this is a beast 🙂 And would also consider the legacy kernel in a better state than expected.

Maybe next time something is wrong i should be able to provide UART (and learn some new stuff anyway to keep the T4 up and running) 😉

Version 20220926 works! Tested Armbian_22.11.0-trunk_Nanopct4_jammy_edge_6.0.0.img and Armbian_22.11.0-trunk_Nanopct4_jammy_current_5.19.11: Both boot, show no dmesg errors and emmc install (boot+system) is fine. I will receive my UART device tomorrow for future debugging.

Okay, thank you so far. I will report back when i have UART access

Same problem, uboot show no usb error on these images but also fails to boot. edit: could a connected nvme drive cause this? I did not open the case und dismount it physically