Posts by Da Flex

Quote from Tom7320

Like this?

Yes, it's active after reboot, and results in more log details.

Use advancedsettings.xml to increase the log level. Post another log when it happens again.

Maybe this procedure helps:

Post

RE: [x86-84] No sound via HDMI

solution (90%)

chatGPT told me to power it all off then turn tv on and wait for it to boot 100% and then wait 10 sek and then turn the computer on

in the audio devices there was my tv now selected that and i fliped some more things back and forth but now it is working

latest log here https://paste.libreelec.tv/charmed-herring.log

menace_dk

May 1, 2026 at 4:37 PM

There is something wrong with your advancedsettings.xml file, so you're still at log level 0:

2026-04-28 21:49:46.726 T:823     error <general>: Error loading special://profile/advancedsettings.xml, no <advancedsettings> node
2026-04-28 21:49:46.726 T:823      info <general>: Default Video Player: VideoPlayer
2026-04-28 21:49:46.726 T:823      info <general>: Default Audio Player: paplayer
2026-04-28 21:49:46.726 T:823      info <general>: Disabled debug logging due to GUI setting. Level 0.

PS: Also have a look at this thread:

Thread

[x86-64] NFS kernel mounting NO WORKIE

I am attempting to update my trusty old x86 HTPC from an ancient version of OpenELEC that I've been running forever because it just worked and it was sufficient for my needs. Now however I'm trying to move to the latest LibreELEC (legacy PC edition) and I'm just not able to get NFS mounts to work following the instructions on this LibreELEC Wiki page:

Mount Network Share

I have noted that (in the case of NFS, at least) these are still the identical old instructions that I used on OpenELEC, years…

ronbaby

April 27, 2026 at 5:28 AM

Quote from Quiffy

Shall I try to reproduce for a log with the following settings?

<loglevel>3</loglevel>
      <setting id="debug.extralogging">true</setting>
<setting id="debug.setextraloglevel">131072</setting>

Reproduce the issue with log level 1. Anything else is overkill.

Quote from BokitoNL

After further testing, and hooking the Raspberry Pi straight into my beamer, audio works perfect. (through the beamer speaker)

Please check the LE audio settings in expert mode. The 44.1kHz sampling rate is common, but could be too low for some hi-res audio codecs. So your beamer seems to handle that sampling rate, but the Meridian AVR could have a problem with it.

2026-04-18 13:59:22.897 T:1906250624   DEBUG: CActiveAESink::OpenSink - SinkPi Initialized:
2026-04-18 13:59:22.897 T:1906250624   DEBUG:   Output Device : HDMI
2026-04-18 13:59:22.898 T:1906250624   DEBUG:   Sample Rate   : 44100
2026-04-18 13:59:22.898 T:1906250624   DEBUG:   Sample Format : AE_FMT_FLOAT
2026-04-18 13:59:22.898 T:1906250624   DEBUG:   Channel Count : 2
2026-04-18 13:59:22.898 T:1906250624   DEBUG:   Channel Layout: FL, FR
2026-04-18 13:59:22.898 T:1906250624   DEBUG:   Frames        : 2205
2026-04-18 13:59:22.898 T:1906250624   DEBUG:   Frame Size    : 8

chewitt : Thx for explaining.

Thanks for the log. If it's a legal ISO, then it looks like an FFmpeg bug to me:

2026-04-18 13:59:21.868 T:1523102592   DEBUG: ffmpeg[5AC8B380]: [mpegts] PES packet size mismatch
2026-04-18 13:59:22.060 T:1523102592   DEBUG: Previous line repeats 3 times.
2026-04-18 13:59:22.060 T:1523102592   ERROR: ffmpeg[5AC8B380]: [mp3float] Header missing
2026-04-18 13:59:22.518 T:1523102592    INFO: ffmpeg[5AC8B380]: [mpegts] decoding for stream 12 failed
2026-04-18 13:59:22.518 T:1523102592   DEBUG: ffmpeg[5AC8B380]: [mpegts] Could not find codec parameters for stream 5 (Subtitle: hdmv_pgs_subtitle (pgssub) ([144][0][0][0] / 0x0090)): unspecified size

You can try to compile your own LE with latest FFmpeg, but you need skills for that.

We don't support 3D on newer LE versions, sorry.

Quote from BokitoNL

Seems like this version should be the best for use with 3D MVC video's on a raspberry pi ?

Yes.

Quote from BokitoNL

Anyone knows how to fix my problem ?

No, but you can try to overclock the RPi(s). To me the issue sounds like a lack of processing power.

Incomplete hardware info. Open the housing, make a hi-res photo, and post it, so users could read the chip labels.

Try the latest LE 13 nightly. It has some fixes for the WiFi driver.

https://test.libreelec.tv/13.0/RPi/RPi4/

Update procedure:

Login by SSH, go to /storage/.update, download the nightly image by wget <image URL>, and reboot.

Quote from chewitt

Are you using tea leaves or a crystal ball to derive this knowledge?

Doesn't the kernel detect devices at boot time?

The audio devices seem to be detected correctly. There must be an audio routing error on LE side.

Do this from SSH terminal:

1. getedid delete
2. reboot

Also check different HDMI ports on TV. They often don't have the same capabilities.

Quote from SoloUnRandom

1. Downloading a bunch of movies and dont use internet at all.

2. Putting a ethernet cable from my bedroom (2nd floor) ALL THE WAY to the living room (1st floor).

3. Buying an Ethernet-to-WiFi adapter.

Quote from goofy84

i use a triple boot system, which files do i have to copy to the partion in order to install from scratch. I remember that i had to extract 2 files from the image-file, to get it working...

We have two threads about multi-boot at Showcase section.

Install LE from scratch, and then just test with Waipu. Use our log server to provide logs.

Quote from goofy84

Thanks but it had nothing to do with the dns service, i use a vpn which i disable when i am testing new builds.

Hmm, I'm still reading VPN messages in your latest log:

2025-12-20 09:35:08.570 T:1572    error <general>: VPN Mgr : (service.py) VPN monitor service detected VPN connection  is not running when it should be
...
2025-12-20 09:35:12.416 T:1572     info <general>: VPN Mgr : (service.py) VPN connected to de-fra.prod.surfshark.comsurfshark_openvpn_udp
...
2025-12-20 09:43:16.922 T:1572    debug <CAddonSettings[[email protected]]>: trying to load setting definitions from old format...

I would uninstall all VPN-related stuff to test Waipu, just to get clean logs. chewitt knows more about VPN...

The developer of the Waipu add-on is your target person, but most add-on devs are at Kodi forum. They aren't here.

Try a different DNS service:

2025-12-20 09:35:06.904 T:1581    error <general>: CCurlFile::CReadState::FillBuffer - (0x7f176c003fc0) Failed: Could not resolve hostname(6)
2025-12-20 09:35:06.904 T:1581    error <general>: CCurlFile::Open - <https://auth.waipu.tv/oauth/token> Failed with code 0:
                                                   
2025-12-20 09:35:06.904 T:1581    error <pvr.waipu>: [Http-GET-Request] error. status: -1, body: 
2025-12-20 09:35:06.904 T:1581    error <pvr.waipu>: [OAuthRequest] no network connection
2025-12-20 09:35:07.104 T:1581    error <general>: CCurlFile::CReadState::FillBuffer - (0x18002600) Failed: Could not resolve hostname(6)
2025-12-20 09:35:07.104 T:1581    error <general>: CCurlFile::Open - <https://auth.waipu.tv/oauth/token> Failed with code 0:
                                                   
2025-12-20 09:35:07.104 T:1581    error <pvr.waipu>: [Http-GET-Request] error. status: -1, body: 
2025-12-20 09:35:07.104 T:1581    error <pvr.waipu>: [OAuthRequest] no network connection