Posts by Da Flex
-
-
It's special hardware you are trying to program.
-
-
-
No support due to proved piracy.
ThreadForum Rules
General Conduct- Be polite and respectful to forum staff and other users
- Be polite and respectful towards this project and other projects
- Be patient, user and staff are spread all over the world, an answer may take time
- One topic per thread
- Posts should be written in English (add text in your native language if needed)
- Be as descriptive and detailed as possible. We are not mind readers!
- If AI tools have been used to create your post or triage an issue, name the tool and version in the post
- Do not
newphreakMarch 15, 2016 at 1:02 AM -
-
OK, thread renamed again.
I think it's better to ask at Kodi forum, because those guys set the default values for cache.
-
I use Pi5 wired LAN interface, but it is running only on 100Mbit/sec, not Gigabit. The video source is on an SMB windows box.
This seems to be the normal speed for that hardware. The NIC specs don't mean you really get it in real life.
PostRE: Change 100MB to 1GB on LibreELEC-Generic-legacy.x86_64-12.0.1?
I see transfers around ~112MB/s from an RPi5 with nvme storage.
I see transfers around ~33MB/s on an elderly Amlogic S905 box with emmc storage.
I see transfers around ~12MB/s on another Amlogic board booted from USB storage.
All three have gigabit NICs, but all three internally wire them up differently and storage media can have a large impact too.
chewittSeptember 21, 2024 at 2:15 PM -
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 -
But the questions in my opening post still apply aboutv how exactly does caching work in LE / Kodi, and how to maximize usable cache size up to the free RAM available?
PostRE: [RPi5] Problem mount HardDisk
[…]
GPU memory is fixed at boot time and we already optimised consumption. Kernel caching has a simple rule: "if you understand the kernel documentation, do what you like, else leave alone" and since 99.99% of users will not understand kernel memory architecture it's best left alone. On the Kodi side users like to tweak cache/buffers settings thus undoing thousands of man-hours of effort to optimise the default settings with a ham-fisted bodge from a forum post where a user with a different…
chewittNovember 10, 2024 at 2:22 AM -
The problem disappeared as soon as I changed hdmi port on my TV. Initially I was using the (e)ARC port. Could be that the audio return capability triggers a bug?
No, but it might trigger a PSU issue. We have to see a log to be sure...
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 -
Remove all banned add-ons and repos, and post another log afterwards.
ThreadForum Rules
General Conduct- Be polite and respectful to forum staff and other users
- Be polite and respectful towards this project and other projects
- Be patient, user and staff are spread all over the world, an answer may take time
- One topic per thread
- Posts should be written in English (add text in your native language if needed)
- Be as descriptive and detailed as possible. We are not mind readers!
- If AI tools have been used to create your post or triage an issue, name the tool and version in the post
- Do not
newphreakMarch 15, 2016 at 1:02 AM -
Thread
Forum Rules
General Conduct- Be polite and respectful to forum staff and other users
- Be polite and respectful towards this project and other projects
- Be patient, user and staff are spread all over the world, an answer may take time
- One topic per thread
- Posts should be written in English (add text in your native language if needed)
- Be as descriptive and detailed as possible. We are not mind readers!
- If AI tools have been used to create your post or triage an issue, name the tool and version in the post
- Do not
newphreakMarch 15, 2016 at 1:02 AM -
Do you use HDMI-0? That's the HDMI output next to the power connector.
-
LE doesn't support simultaneous displays. Buy an HDMI splitter.
-
-
Congrats for solving the puzzle! You was lucky, and had premium support.

-
The initialization of the CEC adapter has a bug. On your working LE 12.0.1:
Code
Display More2024-02-27 18:26:18.011 T:916 debug <general>: InitialiseFeature - using libCEC v4.0.7 2024-02-27 18:26:18.012 T:899 info <general>: starting zeroconf publishing 2024-02-27 18:26:18.012 T:911 error <general>: CCurlFile::CReadState::FillBuffer - (0x7fff1401ca40) Failed: Couldn't resolve host name(6) 2024-02-27 18:26:18.012 T:927 debug <general>: Thread EventServer start, auto delete: false 2024-02-27 18:26:18.012 T:925 debug <general>: Thread CECAdapter start, auto delete: false 2024-02-27 18:26:18.012 T:925 debug <general>: OpenConnection - opening a connection to the CEC adapter: /dev/cec0 2024-02-27 18:26:18.012 T:912 error <general>: CCurlFile::CReadState::FillBuffer - (0x7fff080532d0) Failed: Couldn't resolve host name(6) 2024-02-27 18:26:18.012 T:912 error <general>: CCurlFile::Open - <https://mirrors.kodi.tv/addons/omega/addons.xml.gz?sha256> Failed with code 0: 2024-02-27 18:26:18.012 T:916 debug <general>: Initialise - initialised peripheral on '/dev/cec0' with 2 features and 0 sub devices 2024-02-27 18:26:18.012 T:916 info <general>: Register - new cec device registered on cec->/dev/cec0: CEC Adapter (0000:0000) 2024-02-27 18:26:18.012 T:916 debug <general>: GetMappingForDevice - device (0000:0000) mapped to CEC Adapter (type = cec) 2024-02-27 18:26:18.012 T:912 error <general>: CRepository: failed read 'https://mirrors.kodi.tv/addons/omega/addons.xml.gz?sha256' 2024-02-27 18:26:18.012 T:910 debug <general>: CAddonDatabase::GetAddons took 48 ms 2024-02-27 18:26:18.012 T:911 error <general>: CCurlFile::Open - <https://addons.libreelec.tv/12.0.0/ARMv8/aarch64/addons.xml.gz.sha256> Failed with code 0: 2024-02-27 18:26:18.012 T:911 error <general>: CRepository: failed read 'https://addons.libreelec.tv/12.0.0/ARMv8/aarch64/addons.xml.gz.sha256' 2024-02-27 18:26:18.012 T:916 debug <general>: InitialiseFeature - using libCEC v4.0.7 2024-02-27 18:26:18.013 T:930 debug <general>: Thread CECAdapter start, auto delete: false 2024-02-27 18:26:18.013 T:930 debug <general>: OpenConnection - opening a connection to the CEC adapter: /dev/cec1 2024-02-27 18:26:18.013 T:916 debug <general>: Initialise - initialised peripheral on '/dev/cec1' with 2 features and 0 sub devices 2024-02-27 18:26:18.013 T:916 info <general>: Register - new cec device registered on cec->/dev/cec1: CEC Adapter (0000:0000) 2024-02-27 18:26:18.013 T:916 debug <general>: Thread PeripBusCEC 140733637783296 terminatingOn your non-working LE 13 nightly (20241103-f662bea):
Code2024-11-05 16:49:04.830 T:1046 debug <general>: InitialiseFeature - using libCEC v4.0.7 2024-11-05 16:49:04.830 T:1057 debug <general>: Thread CECAdapter start, auto delete: false 2024-11-05 16:49:04.830 T:1057 debug <general>: OpenConnection - opening a connection to the CEC adapter: Linux 2024-11-05 16:49:04.832 T:1046 debug <general>: Initialise - initialised peripheral on 'Linux' with 2 features and 0 sub devices 2024-11-05 16:49:04.832 T:1046 info <general>: Register - new cec device registered on cec->Linux: CEC Adapter (0000:0000) 2024-11-05 16:49:04.832 T:1046 debug <general>: Thread PeripBusCEC 140732832476800 terminatingIn the working log, the CEC adapter is registered at /dev/cec1, in the non-working log at Linux.
I've already reported the bug to the devs. Stay tuned.