Posts by Da Flex
-
-
Using a V3 case with an LE12 nightly and addon v0.0.7, the fan pulses every 20-30 seconds. Is this expected behavior?
If the on/off frequency of the fan is pretty constant, then I would say it's expected behavior. My power LED (always-on expected) had random on/off cycles without that fix.
-
The problem happens randomly, when I start Kodi with AV Receiver and TV off,
So you don't have picture when you switch the TV on.
From LE side it seems to be connected:
CodeConnector 0 (95) DP-1 (connected) Encoder 0 (94) TMDS Crtc 0 (51) [email protected] 65.000 1024/24/136/160/- 768/3/6/29/- 60 (60.00) Plane 0 (31) fb-id: 121 (crtcs: 0) 0,0 1024x768 -> 0,0 1024x768 (C8 RG16 XR24 XB24 AR24 AB24 XR30 XB30 XR4H XB4H YUYV YVYU UYVY VYUY NV12 XYUV) FB 121 1024x768 XR24Maybe your TV doesn't switch to the DisplayPort signal. Can you test with a computer monitor?
-
Da Flex Are you on LE12? RE: Raspberry Pi Tools - GPIOZERO - LE12 Issues
I'm on LE 11.0.6. Thx for that hint, sounds like my issue. I'll try LE 12.
-
jmi Try this autostart.sh:
autostart.sh starts before Kodi, so after sleeping some seconds in background, Kodi should run.
-
-
It's more like we are waiting for those Wayland features.

-
It's still the same issue that you had on your last thread. Same solution: Update your server to NFS4.
Code
Display More2024-02-13 18:38:46.635 T:674 debug <general>: CGUIMediaWindow::GetDirectory (nfs://192.168.178.42/home/kodi/fresh.m3u) 2024-02-13 18:38:46.636 T:674 debug <general>: ParentPath = [nfs://192.168.178.42/home/kodi/fresh.m3u] 2024-02-13 18:38:46.678 T:674 debug <general>: NFS: Context for 192.168.178.42/home/kodi not open - get a new context. 2024-02-13 18:38:46.679 T:674 debug <general>: NFS: version: 3 2024-02-13 18:38:46.748 T:674 debug <general>: NFS: Connected to server 192.168.178.42 and export /home/kodi 2024-02-13 18:38:46.748 T:674 debug <general>: NFS: chunks: r/w 65536/65536 2024-02-13 18:38:46.753 T:674 debug <general>: CNFSFile::Open - opened home/kodi/fresh.m3u 2024-02-13 18:38:46.785 T:681 info <general>: CActiveAESink::OpenSink - initialize sink 2024-02-13 18:38:46.787 T:674 debug <general>: CNFSFile::Close closing file home/kodi/fresh.m3u 2024-02-13 18:38:46.795 T:674 debug <general>: CNFSFile::Open - opened home/kodi/fresh.m3u 2024-02-13 18:38:46.826 T:674 debug <general>: CNFSFile::Close closing file home/kodi/fresh.m3u -
-
No, he clearly said "once the connection works".
-
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 -
Maybe a network issue. Try to play from a thumb drive.
-
I just connected the AVR to the electricity and with exactly the same connections than before... and it worked.
Congrats! Maybe the AVR has some type of an EDID buffer, which was cleaned now.
Make some more tests, and then mark this thread as solved. I don't think it's an LE issue.
The AVR probably had bad EDID data (containing a video mode) when connector detection failed. Dev talk:
Quoteexcept for the second HDMI / AVR (which looks like a broken EDID and all modes except 720x576i filtered out) the kernel log looks fine.
-
-
Pleaassee libreelec devs, get this released properly somewhere, it'll make this awesome project viable for a lot of builds, especially with things like the intel N100 gaining popularity.
Sure. sky42 is already in contact with Intel developers.
-
-
-