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

  • почему wayland?

    с ним нормально работает графика, и плюс он лучше поддерживается в основном ядре


    Playing around a little more. I noticed that the monitor refresh rate only had one option, 30mhz and I was unable to connect to to either the Kodi or Libreelec repositories to install addons. I just get a timeout error.

    Here are screenshots showing that the network turnips are working on the supported models (the installation is going well) and the frequency is available at 60 Hz.

    screen
    Посмотреть и скачать с Яндекс Диска
    disk.yandex.ru
  • 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?

    Edited once, last by deleonkikko: Merged a post created by deleonkikko into this post. (June 8, 2025 at 10:52 PM).

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

    If wyland hadn't been able to do this, no one would have started translating all modern distributions to wyland with gnome and kde. I admit that there are no such tools in LE yet (perhaps they just weren't needed yet).

    I launched armbian with a 6.15 core on Rock 5b with gnome and wyland - in the settings I can change the screen frequency (60 59.5 50 etc) and any resolution formats. And this is taking into account that there is not all support for 3588 yet.


    Alpha version 20250610-wayland . This is a universal version for all supported devices RK3399 RK356X RK3588 RK3576. SW decoding works on all devices by default. To enable HW decoding (including on 3588), need to enable drm_prem_hw in the settings (see the screenshots for details on how to do this). But on 3588, when HW decoding is turned on, there is a bug - on 4K video it does not work and the video freezes, all videos =< 1920 x 1080 work with HW decoding without any problems.


    screen_drm_hw
    Посмотреть и скачать с Яндекс Диска
    disk.yandex.ru
  • 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.

    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?

    Edited 2 times, last by deleonkikko: Merged a post created by deleonkikko into this post. (June 10, 2025 at 10:08 PM).

  • 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.

  • Wrote test-image to sdcard and changed FTD to NanoPi-r6c

    rk3588-roc-pc.img.gz

    When writing to the SD card, the u-boot for RK3588-ROC-PC is used, which is not compatible with your model. You will have to manually replace the u-boot on the SD card with one that supports your model and (importantly) knows how to run the system using extlinux.conf.

    Or you need to use a USB flash drive, but you need a u-boot for your model that works with USB (as it is implemented for supported models of this theme).

    starting USB...
    Bus usb@fc800000: USB EHCI 1.00
    Bus usb@fc840000: USB OHCI 1.0
    Bus usb@fc880000: USB EHCI 1.00
    Bus usb@fc8c0000: USB OHCI 1.0
    Bus usb@fcd00000: usb maximum-speed not found
    Register 2000140 NbrPorts 2
    Starting the controller
    USB XHCI 1.10
    scanning bus usb@fc800000 for devices... WARN: interface 0 has 2 endpoint descriptor, different from the interface descriptor's value: 1
    4 USB Device(s) found
    scanning bus usb@fc840000 for devices... 1 USB Device(s) found
    scanning bus usb@fc880000 for devices... 1 USB Device(s) found
    scanning bus usb@fc8c0000 for devices... 1 USB Device(s) found
    scanning bus usb@fcd00000 for devices... 1 USB Device(s) found
    scanning usb for storage devices... 0 Storage Device(s) found

    Device 0: unknown device
    switch to partitions #0, OK
    mmc1 is current device
    Scanning mmc 1:1...
    Found /extlinux/extlinux.conf
    Retrieving file: /extlinux/extlinux.conf
    reading /extlinux/extlinux.conf
    225 bytes read in 6 ms (36.1 KiB/s)
    1: LibreELEC
    Retrieving file: /KERNEL
    reading /KERNEL
    86051328 bytes read in 13673 ms (6 MiB/s)
    !!! env helper try: /uEnv.txt
    Retrieving file: /uEnv.txt
    ** Unable to read file /uEnv.txt **
    append: boot=LABEL=LIBREELEC disk=LABEL=STORAGE quiet console=ttyS2,1500000 console=tty0 systemd.debug_shell=ttyS2 coherent_pool=2M cec.debounce_ms=5000
    Retrieving file: /dtb/rockchip/rk3588-rock-5b.dtb
    reading /dtb/rockchip/rk3588-rock-5b.dtb
    178470 bytes read in 41 ms (4.2 MiB/s)
    Fdt Ramdisk skip relocation
    No misc partition
    ## Flattened Device Tree blob at 0x0a100000
    Booting using the fdt blob at 0x0a100000
    'reserved-memory' shmem@10f000: addr=10f000 size=100
    Using Device Tree in place at 000000000a100000, end 000000000a12e925
    can't found rockchip,drm-logo, use rockchip,fb-logo
    WARNING: could not set reg FDT_ERR_BADOFFSET.
    failed to reserve fb-loader-logo memory
    Adding bank: 0x00200000 - 0x08400000 (size: 0x08200000)
    Adding bank: 0x09400000 - 0xf0000000 (size: 0xe6c00000)
    Adding bank: 0x100000000 - 0x3fc000000 (size: 0x2fc000000)
    Adding bank: 0x3fc500000 - 0x3fff00000 (size: 0x03a00000)
    Adding bank: 0x4f0000000 - 0x500000000 (size: 0x10000000)
    Total: 20528.512 ms

    Starting kernel ...

  • 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.

    This is a BSP core for which you need to use rk-mpp (for HW decoding), which greatly reduces its benefits. Back in 2023, I released LE builds with BSP 6.1 kernels, you can find them on the website. Yes, this core has better support for rk3588 hardware, but it's not the main core with a lot of hacks.