Are there remote controls such as tvbox to connect to the Raspberry?
You can use the TV remote control for the RPi. The technology is called CEC, and uses HDMI to send remote calls to RPi.
Posts by Da Flex
-
-
I can do putty. Is there a text editor built into LE.?
Yes, nano.
-
I can't actually get into the installed version to turn logging on. When I SSH into it the /logfiles directory is empty.
Nobody was talking about that folder before.
Activate log level 1 at advancedsettings.xml, and reboot. Then run pastekodi from SSH, and post the resulting URL.
-
If you don't get any log files, then we already found the cause of the issue. Kodi has no write access on your SATA drive.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Use LE 13 Generic Legacy Nightly for NVidia GPU. Upgrade your current installation on SSH:
Code
Codecd /storage/.update wget https://test.libreelec.tv/13.0/Generic/Generic-legacy/LibreELEC-Generic-legacy.x86_64-13.0-nightly-20250529-8c39f0c.img.gz reboot -
technics Most add-on developers are at Kodi forum. I suggest to ask over there.
-
I think this was the cause:
-
Known issue. We have something similar on RPi3 and x86-64:
RE: [RPi] FTPS Broken in LE12
There is a comparison table that indicates which versions of curl, along with their libraries, are used in the different LibreELEC versions. It is evident that under LibreELEC 12.0.1, 12.0.2, and the current nightly-20250415-e25b5e0 (v12.x), ftps does not function.
LibreELEC Generic.x86_64 and RPi2.arm curl comparison table:
With the current LibreELEC nightly-20250424-067110d (v13.x), ftps is operational again; however, various elements (folders/files) are constantly being omitted. This renders…
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Here you go: crashlog
I guess it crashes due to an unknown audio codec:
Code2025-05-25 19:04:59.025 T:733 warning <general>: CreateLoader - unsupported protocol(sources) in sources://music.tbn ... Feb 27 18:26:07.867553 kodi6 kernel: snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. -
That's for Apple devices?
What's your hardware?
-
Is it helpful to create a log when we know it's a Nividia driver issue? Serious question...
Seems like our devs can't test that Nvidia driver. If chewitt knowns how to revert to the working driver, then it's not necessary.
-
i am currently using the nightly from 12.04.2025 generic leagcy, it is the last working version.
I guess it would be cool to compare working and non-working logs. What do you think?
-
Where is the part about HID remotes?
Since 9.2.0 we use the native Linux kernel driver for the IR sensor, which sends normal HID events.
-
Is there an help page on how to set-up an HID based remote?
-
Chrome only runs on LE Generic-legacy. Do you have that?
-
Sorry, the default instructions don't work for you. Enable log level 1 by creating an advancedsettings.xml. Then reboot, login again, and use pastekodi to get the URL of the log.
-
If you still have SSH access in black screen mode, login, and grab a log.
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link
