beyondthegrave RAM size is intentionally capped as some Rockchip drivers assume 32-bit memory ranges and behave badly with ranges above 4GB. HDR is not implemented yet, and I don't expect that to change for a while yet.
LE13 Testing for RK3288, RK3328, RK3399, RK3566, RK3568, RK3576, RK3588
-
chewitt -
August 28, 2025 at 8:08 AM -
Thread is Unresolved
-
-
On the Pine64 Rock64 (RK3328) the slide show does not work, but just displays a black screen. Not sure if that is a kodi issue or if it has something to do with libreelec.
kodi.log contains an error as last entry:
-
rdorsch slideshows are probably using shaders which might have a connection to e.g. the mesa version, but in general it sounds like something that needs to be investigated from the Kodi side; especially with Piers technically still in a pre-alpha state. It's worth seeing if the feature works on another distro or platform.
-
Let me also add the debug log:
Code2025-12-08 09:44:38.631 T:1056 debug <general>: Keyboard: scancode: 0x1c, sym: 0x0d (enter), unicode: 0x0d, modifier: 0x0 2025-12-08 09:44:38.632 T:1056 debug <general>: bool CInputManager::HandleKey(const CKey&): return (0xf00d) pressed, window 10002, action is Select 2025-12-08 09:44:38.653 T:1056 debug <general>: Activating window ID: 12007 2025-12-08 09:44:38.653 T:1056 debug <general>: ------ Window Init (SlideShow.xml) ------ 2025-12-08 09:44:38.653 T:1056 info <general>: Loading skin file: SlideShow.xml, load type: KEEP_IN_MEMORY 2025-12-08 09:44:38.659 T:1301 debug <general>: Thread BgPicLoader start, auto delete: false 2025-12-08 09:44:38.659 T:1056 debug <general>: Loading the current image 7: /storage/fs/pictures/BCN/2025-09-11-20-14-53-729.jpg 2025-12-08 09:44:39.061 T:1080 error <general>: EXCEPTION: Kodi is not playing any file 2025-12-08 09:44:39.062 T:1080 debug <general>: [plugin.video.youtube] Clear property |plugin_sleeping| 2025-12-08 09:44:39.063 T:1080 debug <general>: [plugin.video.youtube] Set property |plugin_sleeping|: 'true'What might be also interesting to add: The preview for the images works well. Even it is used as background with overlays when navigating through the image works well.
Probably a different issue:: during scanning of the images a popup window with a progress bar is shown. During the scan the entire screen is flickering from time to time. I could not identify a pattern though.
I don't have easy access to another platform with Piers, but the slide show does not work at all, so it should be easy to check.
-
-
Good afternoon, is it possible to use this adapter for TVBOX? rk3576
LE has no support for RK3576 set-top box devices (because the upstream kernel has no support) so: a) no idea, b) even if it does work there is no LE image for you to test with.
-
Nanopc-t6, black screen when booting from microSD; it used to boot fine in early September 2025. The manufacturer's spyloader is dated 2024, no newer version.
Rendering works fine, the choice between eth1 and eth2 jumps around, and eth0 is random. The driver for the new 8822ce module works.
I have to fix U-boot by re-flashing from an old (September 1st) libreelec image.
What do you recommend?
Thank you for your work, happy holidays! -
rkman Saying "black screen" and then "rendering works fine" sounds contradictory so I'm guessing the Kodi home screen shows up eventually? so the screen is only blank during early boot?. If yes, this is prob. due to the kernel now supporting 4K output and in early boot a 4K mode the TV doesn't quite agree with is used. The workaround is to append video=HDMI-A-1:1920x1080M@60D to the kernel boot params in extlinux.conf so initial output is forced to 1080p instead. As a general rule you want to run Kodi at 1080p and only switch to 4K for playback anyway (see https://wiki.libreelec.tv/configuration/4k-hdr).
NB: If the board is booting from downstream Rockchip u-boot on SPI flash you can probably expect random behaviours. It's best to wipe SPI and allow mainline u-boot (2025.10) on the SD card or eMMC module (wherever LE is flashed) to be used instead.
-
Images in my test share are bumped to Linux 6.19-rc2. No functional changes are expected although I suspect some of the in-flight 4K60 patches have matured as test files in [email protected] and 4K@60 seem to be more stable. I'm hoping the new year brings upstream merges so the number of patches required reduces and become less of a juggling act.
-
Thanks for the update!! I was using the firmware rtw8821a for my wifi dongle and after updating to the latest test update, the dongle no longer works. I think it was probably the linux upgrade.
Would it be possible to add the firmware to LibreElec? I don't know if that could help with this issue. I was using the /storage/.config/firmware/rtw88 directory to manually add the firmware, but that no longer seems to be working. Also, I got the one I am using from this link
-
swever the images include the latest rtw88/rtw8821a_fw.bin firmware from the upstream linux-firmware repo and nothing has changed with that in the last few months. If you have files in /storage/.config/firmware/rtw88 these override the lastest upstream files so I would suggest removing them and using upstream firmware. If that doesn't fix something; clean boot then "journalctl | paste" and share the log URL so we can look for error messages etc.
-
Hi all,
Love the project. Have a Rock 5B and appreciate the work done by countless volunteers to make this device usable.
I'm able to boot my device but wifi and bluetooth are not working.
Code[ 15.633717] iwlwifi 0002:21:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x80000000 [ 15.633734] iwlwifi 0002:21:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000 [ 15.633739] iwlwifi 0002:21:00.0: Detected Intel(R) Wi-Fi 6E AX210 160MHz [ 15.633803] iwlwifi 0002:21:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-89.ucode failed with error -2 [ 15.633809] iwlwifi 0002:21:00.0: no suitable firmware found! [ 15.633812] iwlwifi 0002:21:00.0: iwlwifi-ty-a0-gf-a0-89 is required [ 15.633814] iwlwifi 0002:21:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.gitHere's the full log from my device: https://paste.libreelec.tv/expert-coyote.log
-