I see nothing in the log beyond the wlan0 interface being created. There's no connection attempt.
I also see no reason to generate a Kodi debug log (as requested). It won't show anything related to connman/iwd/rtw89.
I see nothing in the log beyond the wlan0 interface being created. There's no connection attempt.
I also see no reason to generate a Kodi debug log (as requested). It won't show anything related to connman/iwd/rtw89.
Urgh.. thread merge doesn't work nicely (sorry) but we'd prefer to continue with a single thread on the same topic.
Thanks for confirming. I'll work up enthusiasm to push an update to LE12 to enable that kernel module. I'll avoid the tempatation to bump the kernel as I haven't tested/booted LE12 for some time now.
In attempting the long list of Qs:
* I've not seen reboot issues for a while, although I use an eMMC module for testing not SD cards. I'll add a card check to a to-do list of things, but I caution that I'm often rather slow at ticking items off the list.
* Known issue with subtitles. I'm told it's a problem with lima/Utgard and needs something fixing in mesa, which is taking time.
* No idea but probably a Kodi issue not a LibreELEC issue.
* System Info page clearly shows K22 and the build details (bottom of the page) using the default Estuary skin.
* No idea about NTP issues, I've never needed to change the defaults.
* LE settings changes the OS keyboard (console etc.) not the Kodi UI keyboard in Settings > Regional > Virtual Keyboard Layouts.
* If you want name resolution to work without DNS, configure /storage/.config/hosts.conf as you would /etc/hosts.
* Yes, putting .tar or .img.gz in /storage/.update will work.
* The .img is a standard USB/SD card image. Most Windows tools don't understand Linux partitioning schemes well so I'd guess VCD is just another one to add to th elist.
Is there anyone out there using LibreELEC on a Zero 2W?
Stats show 33 active installs on a Zero 2W board. 1x on 12.0.2, 1x on 11.0.6, 24x on 10.0.4, and the rest on old nightlies. Installs do not prove it's viable, I'd expect half/most of them are just using LE to run something like Tvheadend in the background. Playback will not be great and there's no cure for that. If you're still keen to have a poor experience, the instructions are probably in this thread.
I've no idea about the issue, but before doing anything more I'd update the flirc firmware to current to see if the cures anything?
In short, no, because in LE there is effectively only a root user in the OS. I wouldn't expect that to be an issue though. You might see some warnings in logs, but warnings are informational, not errors which are fatal.
As a general rule RAM size and I/O performance don't make a difference for video decoding performance or cause stuttering. RPi5 has the CPU grunt to software-decode most formats to 4K30 (only HEVC is hardware decoded and supported above that) so media format can be important. Kodi config also needs to be right, see: https://wiki.libreelec.tv/configuration/4k-hdr
Please test the C2 image from my test share again. I'm guessing at the issue, but the image reverts an upstream kernel change that might be responsible for USB issues. Let me know.
EDIT: it may simply be CONFIG_USB_ONBOARD_HUB being dropped in the switch to CONFIG_USB_ONBOARD_DEV when we've rebased against Linux 6.10 and the kernel defconfig being missed since then.
I've updated the images in the test share to (re)enable that. Please see if it works?
The lack of subtitles is a known issue in K22 caused by shader optimisations in Kodi, it's been flagged to @sarbes who is the Kodi dev responsible for that. To downgrade to K21, download the 12.0.2 .tar file to /storage/.update, stop Kodi, remove /storage/.kodi, then reboot to perform the update.
Merged. The updated add-on should be in the repo in the next 24-36 hours.
LE is minimalist and the Generic image probably needs CONFIG_SENSORS_APPLESMC enabling in defconfig.
See: https://github.com/LibreELEC/Libr…6_64.conf#L3509
There's no problem to include the module, but we need to prove that's the fix first. As you seem to be the tinkering type, can you self-build an image to test? See: https://wiki.libreelec.tv/development/build-basics .. it's just a case of cloning our sources and then editing the .conf file before running the build command.
alexiedb Clone the RPi kernel (as we use their downstream fork not true upstream for RPi boards) then cherry-pick the patches smp has linked onto the RPi kernel 6.12.y codebase and solve the Kconfig and Makefile issues (simple sort order changes in the files probably) before generating a clean patch to use in the LE buildsystem. Also don't forget to add the related CONFIG_XXXXXX entries and enable the relevant modules in packages/RPi/devices/RPi/linux.arm.conf else the modules will not be built.
Ahh, he normally links a thread which discusses building with a patch. All you need to do is add .patch to the URL and you have the patch that's needed for the kernel in the LE buildsystem: https://github.com/tbsdtv/linux_m…4187cc616.patch
Is it enough to do the steps to build a customer LE image and the drivers for TBS5530 will be automatically included?
No, you need to add the kernel patch when compiling the image. Go read the thread smp linked.
The LE buildsystem still supports creating an RPi(1) image, but even if you patch the kernel to support the TBS card it's not going to run well as the board has only 512MB RAM and modern Kodi needs more. That's the reason we dropped support for all boards with under 1GB RAM. If you want to run the board as an e.g. Tvheadend server-only LE device, that should be fine, but server running in the background and Kodi doing playback will be too much.
NB: Although it's not hard to compile a custom LE image, it requires a certain skillset, so it's probably easier to run a server-only setup from a RaspiOS image as this will have a ton of HOWTO guides for the task.
2025-03-09 06:19:04.211 T:13590 debug <general>: ADDON: Dll Initializing - Sidplay Audio Decoder
2025-03-09 06:19:04.211 T:13590 debug <general>: SECTION:LoadDLL(/storage/.kodi/addons/audiodecoder.sidplay/audiodecoder.sidplay.so.20.2.0)
2025-03-09 06:19:04.211 T:13590 debug <general>: Loading: /storage/.kodi/addons/audiodecoder.sidplay/audiodecoder.sidplay.so.20.2.0
2025-03-09 06:19:04.211 T:13590 error <general>: Unable to load /storage/.kodi/addons/audiodecoder.sidplay/audiodecoder.sidplay.so.20.2.0, reason: /storage/.kodi/addons/audiodecoder.sidplay/audiodecoder.sidplay.so.20.2.0: undefined symbol: _ZTI7SidTune
It's so much more helpful when you post a log file with the actual error. You need to report it in Kodi forums to the add-on maintainers.
I forget the exact command, but you can change mixer config with "amixer sset" commands. On boot the soundconfig script is run by udev (which provides the card device as the $0 variable), see:
You cannot overwrite the soundconfig script as it's embedded in the read-only part of the OS, but you can create an autostart.sh script to run a command to change the mixer controls on boot, or (better, as it supports more precise scheduling) a systemd service that runs the command before Kodi starts.