Thanks. Is all your firmware up-to-date (especially HDMI)? You probably need Windows for this.
Posts by Da Flex
-
-
Seems like LE is still trying to use the laptop display (eDP1):
Code2024-05-25 17:41:16.176 T:18747 warning <general>: CXRandR::Query - output eDP1 has no current mode, assuming disconnected ... 2024-05-25 17:41:30.582 T:18747 warning <general>: CXRandR::Query - output eDP1 has no current mode, assuming disconnected ... 2024-05-25 17:41:34.177 T:18747 warning <general>: CXRandR::Query - output eDP1 has no current mode, assuming disconnectedAdd this to the boot options:
-
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 -
-
xmlcom Yes, these patches are known to the dev. He has mentioned this thread earlier:
-
-
Try latest nightly build. Post a log from it, in case it doesn't work.
This is the most relevant thread about the problem:
PostRE: [RPi5] Problem with HiFiBerry DAC
[…]
RPi folks recommend to store the name of the overlay in the eeprom, not the actual overlay itself, to avoid kernel version issues.
Unfortunately Hifiberry did the latter (and OFC the overlays became incompatible with RPi5) but fortunately this could be fixed up with hat_map entries (see commit https://github.com/raspberrypi/li…fdda902104650b3) so the hifiberry cards should work fine now without any config.txt trickery.
so long,
HiasHiassofTApril 25, 2024 at 2:30 PM -
No further support due to banned add-ons. Open a new thread, and provide a clean log on it.
Closed.
-
Code
2024-05-20 16:27:42.819 T:3339 debug <general>: NFS: Context for 192.168.1.100/export/Musica not open - get a new context. 2024-05-20 16:27:42.820 T:3339 debug <general>: NFS: version: 3 2024-05-20 16:27:42.826 T:3339 debug <general>: NFS: Connected to server 192.168.1.100 and export /export/Musica 2024-05-20 16:27:42.826 T:3339 debug <general>: NFS Server max read chunksize (1048576) is bigger than client setting - Using client value 131072 2024-05-20 16:27:42.826 T:3339 debug <general>: NFS Server max write chunksize (1048576) is bigger than client setting - Using client value 131072 2024-05-20 16:27:42.826 T:3339 debug <general>: NFS: chunks: r/w 131072/131072 2024-05-20 16:27:42.828 T:3339 error <general>: NFS: Failed to stat(export/Musica/I/I Mother Earth/Dig/folder.jpg) stat call failed with "NFS: Lookup of /I/I Mother Earth/Dig/folder.jpg failed with NFS3ERR_NOENT(-2)"Try without NFS. If you have the option to update to NFSv4 on your server, please do.
-
Thanks. Please post a link to a log now.
-
I don't think so because the soundcard does not appear anymore in the audio devices listed by kodi.
So you get HiFiBerry sound without having a HiFiBerry card in the audio output device list?
-
Tried but nothing changed.
Does that mean you still have audio without the config.txt driver entry?
I heard that HiFiBerry cards are now auto-detected.
-
Code
2024-05-20 15:41:02.962 T:7382 info <general>: Disabled debug logging due to GUI setting. Level 0.Not helpful.
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 -
This maybe sounds like magic, but try without any HiFiBerry driver activated at config.txt (and of course reboot).
-
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 -
The OutputPicture - timeout waiting for buffer warning is normal (I've just learned that myself).
Try again with the default skin.
-
xmlcom If you start a new thread at Development sub-forum, then LE admins could invite other 3D users. So please do some research, and let us know if you see a chance. It's definitely not an easy project.
We have an Amlogic pro in our LE support team. Here is what he said:
QuoteI wouldn’t implement it on AMlogic
We spent serious time and money getting it to work to find out there are VLSI level bugs that cause macro blocking on some titles. Only solution is remux or live with it. These are straight BD rips. AML acquired the 3D IP block without any understanding of it and this is visible in their code.
I just about broke even on it, but fortunately got two goods devs in the process.
So I would suggest RPi as target platform.
-
You will run into dependency problems on add-ons. Most add-ons need Python.