Regular log, nothing specific.
Posts by Da Flex
-
-
It's there, but it's hidden, because .cache starts with a point. Your solution at post #4 is better, because you don't delete the complete cache. I guess it's possible to write an update script that only deletes the specific DB file from that cache folder.
-
Just in case you haven't done it yet, reboot is necessary to activate the content of advancedsettings.xml.
-
Maybe deleting /storage/.cache helps.
-
rosenkrf Please update to LE 11.0.5, and post another log. The link at post #15 is dead, and we have our own log server now.
-
This part looks fishy to me. I'll ping a dev...
CodeJan 24 11:55:33.273919 media kernel: iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver Jan 24 11:55:33.274057 media kernel: iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36 Jan 24 11:55:33.274119 media kernel: iwlwifi 0000:00:14.3: loaded firmware version 72.daa05125.0 so-a0-gf-a0-72.ucode op_mode iwlmvm -
Background: We need more info due to problems with newer Intel WiFi drivers:
ThreadNewer intel wireless chip not supported
I have a newer n100-based miniPC that has the following intel wifi/BT adapter:
00:14.3 Network controller: Intel Corporation Device 54f0
It looks like this is a problematic piece of hardware (or at least a "too-new" piece of hardware):
https://community.intel.com/t5/Wireless/AX…er/td-p/1468063
While I wait for intel to add some better support, is there a 'tried-and-true' USB bluetooth adapter I can pick up in the meantime?
isamudaisonApril 29, 2023 at 12:31 AM -
mmh i cannot find the directory \Kodi\userdata
/storage/.kodi/userdata/advancedsettings.xml is the right location.
-
Regular log at log level 1 please...
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 -
Adding a power button to your RPi is the easiest solution:
ThreadRPi4 GPIO using in LibreELEC
Dear All,
Is it possible use GPIO pins with LibreELEC on RPi4? My idea is use some GPIO pin for LED in the power button for signaling that system is running. Now I´m using only standard shut down funtion in Kodi and RPi4 weak-up function with button on GPIO pins 5 and 6 made by this manual:
How to Add a Power Button to Your Raspberry Pi - howchoo
All manuals I found for this is for NOOBS but not for LibreELEC
Thanks
RadekFoxbikerAugust 16, 2019 at 10:23 PM -
Better ask HiFiBerry. RPi5 is pretty new, so it could be a HiFiBerry driver issue.
-
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 -
sky42 had good progress with his N100 during the last weeks (see link at post #5). Maybe ask him for 4k HDR 4.4.4.
-
Yes, very likely an LSPCON chip issue. You should avoid any DP->HDMI converter (internal or external):
PostRE: Time to upgrade my NUC. What's hot today?
[…]
As you can see on this block diagram, NUC11PAxxx does not have a native HDMI port. It is using a DP->HDMI protocol converter (PCON) chip. It is more than likely the source of your audio passthrough issues. So this is not a gen11 issue but an issue specific to that NUC model. There is nothing to fix from LE/Kodi side.smpJanuary 15, 2024 at 2:36 AM -
Incomplete log at log level 0.

Activate log level 1 by creating an advancedsettings.xml file.
Reboot, replicate the issue, and post the resulting URL of pastekodi.
-
Activate log level 1 by creating an advancedsettings.xml file, and reboot.
Code2024-01-22 20:51:40.366 T:985 info <general>: Disabled debug logging due to GUI setting. Level 0.
-
Not sure whether it's CEC-related at all.

-
It could be something else, too. Provide the log when the error appears again.
PS: Activate log level 1 by creating an advancedsettings.xml file, and reboot. When the error appears, login by SSH, and post the result of pastekodi.