- activate log level 1 by creating an advancedsettings.xml file
- reboot
- when the error appears, upload the log (by GUI, or by pastekodi command on SSH), and post the resulting URL
Posts by Da Flex
-
-
Yes I dont use default skin
Can you try the default skin? Maybe you'll see NFS entries afterwards.
-
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 -
-
OK, if power-on by IR works for you on RPi5, post that solution.
-
Nekromantik If you want to give something back to the forum, post that solution on Showcase section.
-
StarLite Update to LE 11.0.6. If the issue remains, post a log (see post #23).
-
vanfroda Try the latest LE 12 nightly.
-
Try the latest LE 12 nightly.
-
-
Ask this guy:
ThreadNot booting without Keyboard attached
New to this, love how easy this setup was, even for a novice like myself. I have an older Intel NUC "DC3217IYE" that I have configured to run an autoexec auto play loop script for a media unit I am using at my shop TV on a wall. It works perfectly that way!
However, I would LOVE if it did not require a keyboard hooked up on first boot up. I tested my setup if there was a power failure and was hoping it would fire right back up. It didn't, and hung forever right before the LibreELEC splash…WraithJanuary 30, 2024 at 4:43 AM -
-
-
There is miscommunication between RPi4 and TV. So please double-check whether your HDMI cable is conform to HDMI 2.0 or 2.1 standard:
Code2024-01-31 20:55:33.814 T:878 error <general>: [display-info] Error parsing EDID: 2024-01-31 20:55:33.814 T:878 error <general>: [display-info] ---------------------------------------------- 2024-01-31 20:55:33.814 T:878 error <general>: [display-info] Block 1, CTA-861 Extension Block: 2024-01-31 20:55:33.814 T:878 error <general>: [display-info] Video Capability Data Block: IT video formats are always underscanned, but bit 7 of Byte 3 of the CTA-861 Extension header is set to overscanned. 2024-01-31 20:55:33.814 T:878 error <general>: [display-info] 2024-01-31 20:55:33.814 T:878 error <general>: [display-info] ----------------------------------------------
You have network timeouts. Please try to play the same video from USB stick:
Code2024-01-31 20:58:03.716 T:885 debug <general>: ActiveAE::SyncStream - average error of 35.362936, start adjusting 2024-01-31 20:58:03.716 T:885 debug <general>: ActiveAE::SyncStream - average error 0.362936 below threshold of 30.000000 2024-01-31 20:58:03.719 T:878 debug <general>: CDRMUtils::DrmFbDestroyCallback - removing framebuffer: 342 2024-01-31 20:58:03.732 T:878 debug <general>: CDRMUtils::DrmFbDestroyCallback - removing framebuffer: 343 2024-01-31 20:58:08.774 T:1068 warning <general>: OutputPicture - timeout waiting for buffer 2024-01-31 20:58:16.440 T:1069 info <general>: Skipped 144 duplicate messages..
-
Thx. Wait for chewitt . The NFS scan in the log looks weird, so it could be a bug.
-
Can you remove / rename the .cache folder for another test?
-
those could impact the nfs browsing?
I'm not sure, NFS scan in the log is erratic to me. Just try, and go back to the original, if it doesn't work.
Another thing is this:
Code2024-01-31 17:55:50.418 T:1039 debug <general>: NFS: Connected to server 192.168.1.200 and export /mnt/user/Stuff 2024-01-31 17:55:50.418 T:1039 debug <general>: NFS Server max read chunksize (1048576) is bigger than client setting - Using client value 131072 2024-01-31 17:55:50.418 T:1039 debug <general>: NFS Server max write chunksize (1048576) is bigger than client setting - Using client value 131072 2024-01-31 17:55:50.418 T:1039 debug <general>: NFS: chunks: r/w 131072/131072
So play with <chunksize> at advancedsettings.xml.
-