Unofficial LE for RK356x RK3328\RK3399 RK3588(s) RK3576

My motherboard won't boot with this image.
It's not sending a signal to the monitor. Is there a graphics issue?

What does Wayland mean?

I managed to get connection to the repositories. During the initial set-uo, only my local network was auto configured for ethernet.

I had to add the default gateway manually, which opened up access to the internet.

I still can't get past the 30mhz refresh rate but the Orange Pi 5 is not officially supported, so it is entirely reasonable that some functionality might not be there.

The vertical USB 2.0 port is not supported but then it is also problematic on most Linux distros.

Likewise, the USB-C data port is not detected, which is also the case with one or two other distros and full mainline support is, as I believe things, still to come.

Having some fun testing it though and it is worth other Orange Pi 5 users trying it.

Use the LibreELEC-ARMv8.aarch64-13.0-devel-20250607193042-e5590fa-rk3588-roc-pc.img image and change the config file to reflect use of the correct DTB image.

balbes150 is building the image with the Wayland windowing environment, and this restricts you to a single refresh rate because Wayland does not support dynamic refresh rate changes. This is why LE does not use Wayland in official images (only GBM, and Xorg for nVidia). The LE build system supports Wayland because it's used with the Lakka retrogaming fork.

Quote from chewitt

balbes150 is building the image with the Wayland windowing environment, and this restricts you to a single refresh rate because Wayland does not support dynamic refresh rate changes. This is why LE does not use Wayland in official images (only GBM, and Xorg for nVidia). The LE build system supports Wayland because it's used with the Lakka retrogaming fork.

That does explain what is happening then.

Researching this more seems to suggest that right now, manual adjustments using tools such as wlr-randr, which I am not familiar with can sometimes be required.

I dare say that as Wayland development matures, solutions will be created.

Quote from ozarks

I dare say that as Wayland development matures, solutions will be created.

The issue is known about in the Wayland ecosystem for many years already so I woulnd't hold breath or hope of a solution. NB: It's generally not an issue as Kodi GBM works well, although on new hardware where the DRM layer is still maturing there might be some glitches to resolve.

Quote from chewitt

The issue is known about in the Wayland ecosystem for many years already so I woulnd't hold breath or hope of a solution. NB: It's generally not an issue as Kodi GBM works well, although on new hardware where the DRM layer is still maturing there might be some glitches to resolve.

Yes, further research does indeed stop me from holding my breath.

I did manage to get Kodi GBM working on one or two Linux distros a few months back and for the most part, Kodi could run rather well overall.

Steps forward in one way or another I guess.

Quote from deleonkikko

My motherboard won't boot with this image.
It's not sending a signal to the monitor. Is there a graphics issue?

---

What does Wayland mean?

Quote from balbes150

Did you not specify the exact model of the equipment, did not provide logs, and do you want someone to respond to you? There are no psychics here to guess what's not working for you.

Thread

ORANGE PI 3B

Good afternoon.

Could someone create an image for this board for me? I've been using it for a while, just in case something comes out for it.

I know no developer has it, but I'm sure someone is waiting to buy it. It's a good, very affordable board that could be put to good use with LibreElec.

On the Internet, from the page http://www.orangepi.org/html/hardWare/…ange-Pi-3B.html you can see all its features.

If someone helps me create it, I promise to perform any tests they need.

Greetings

deleonkikko

May 21, 2025 at 4:35 PM

Sorry, but I don't speak English and I have to use a translator.

I also don't know anything about viewing logs because the topic is beyond me. I'll just post the exact model of my computer with all its components and pictures where you can see them.

I finally managed to get it to boot with this new version, Wayland, using the DTB from the second version, although mine is from the first.

With this version, hardware acceleration DOES work and it runs much better. What still doesn't work is Wi-Fi, Ethernet, and Bluetooth.

How can I see the log where the errors are specified, what command should I use?

Reading through an old thread on the Armbian forum from 2023, titled, [GUIDE] Kodi on Orange Pi 5 with GPU Hardware Acceleration and HDMI Audio, one of the additional options, when enabling enable drm_prem_hw running Kodi under GBM, there was a third option that really opened up the HW decoding performance, called PRIME Render Method where the option "Direct To Plane" enabled a wider array of hardware accelerated video, including 8K.

Within the instructions there was this section

Step 4 (Enable PPAs and install other elements required for GPU hardware acceleration)

At the command line, enter the following commands (highlighted in Blue):

sudo add-apt-repository ppa:liujianfeng1994/panfork-mesa

sudo add-apt-repository ppa:liujianfeng1994/rockchip-multimedia

sudo apt update

sudo apt full-upgrade

sudo apt install ubuntu-desktop kodi

When prompted on-screen if you wish to use gdm or lightdm, select gdm.

Now this was all relevant to a fairly specific Armbian build using the old 5.1 kernel and unfortunately, the liujianfeng1994 repositories don't work with newer builds.

I don't know whether any of this information could be used to enhance Libreelec builds to allow the selection of the Prime Render Method Direct To Plane.

NanoPi-r6c won't boot

Steps I took:

1. Booted OpenWRT (link) to test if debug-console was working and it was.

screen /dev/ttyUSB0 1500000

2. Verified checksum successfully:

2186b184bb88272b2522841679b3bc99a7a7ae9aa376cc3d4b375b12381c4919

 LibreELEC-ARMv8.aarch64-13.0-devel-20250607193042-e5590fa-rk3588-roc-pc.img.gz

3. Wrote test-image to sdcard and changed FTD to NanoPi-r6c

$ diff extlinux.conf extlinux.conf.bak 
3c3
<   FDT /dtb/rockchip/rk3588s-nanopi-r6c.dtb
---
>   FDT /dtb/rockchip/rk3588s-roc-pc.dtb

4. Inserted sdcard into NanoP, no output on debug-console, unfortunately it does not boot.

Thanks for all the hard work.

ozarks Panfork was a fork of panfrost (hence the name) hacked/adapted for ARM Mali Valhal hardware while "panthor" was still in the earlier stages of development. As panthor is now developed and upstream it's been superseded. In theory Direct-to-Plane with DRMPRIME decoding should be the default used; although until I have some RK3588 hardware to test with (some is allegedly being sent to me) i'm unable to do anything beyond theorize what's missing or required.

balbes150 please push changes to your GitHub repo, thanks.