Posts by HiassofT

There's nothing obvious in the logs except you are running a rather old LE version, 9.2.8, which is EOL now (latest release is 10.0.3) and you are playing a bluray image over nfs (which may or may not be problematic - never tried that myself).

Another thing worth looking into is your TV settings. Best to turn off all picture/video "enhancement" stuff, they usually just make things worse (especially Samsung TVs still seem to come with terrible defaults). Search eg on rtings.com for your TV model to find some info about recommended TV settings.

so long,

Hias

If you haven't setup whitelist and enabled refresh rate switching then the GUI mode will be used for playback - and if you try playing eg an SD or HD 50fps file at 4kp30 things will go south.

If it still doesn't work then post a debug log.

so long,

Hias

Most likely you are running at 4kp30.

Configure kodi as described in the wiki https://wiki.libreelec.tv/configuration/4k-hdr and optionally add hdmi_enable_4kp60=1 to config.txt to get 4kp50/60 modes as well.

so long,

Hias

Quote from Jocke.Sve

Yes, the "Power" seems to ignore the disable setting!

See here: https://github.com/raspberrypi/fi…ment-1225910618

Quote

The safest way to turn off the PWR LED on all Pis with either old or new firmware is to use the default-on method but declare the output as being active-high:

Code

dtparam=pwr_led_trigger=default-on # The default
dtparam=pwr_led_activelow=off

so long,

Hias

RPi0-3 don't have H265 hardware decoders but older LE (more specifically: ffmpeg) versions contained some clever code to offload some of the heavy lifting to the GPU. So H265 up to HD, with not too high bitrate, was playable on RPi 3.

Unfortunately this code could only work with the legacy proprietary graphics drivers so it's no longer available since LE10 (and has now been removed in latest ffmpeg versions).

so long,

Hias

Just use the RPi imager on a PC to create an eeprom/bootloader recovery SD card and then put it into your RPi

Raspberry Pi OS – Raspberry Pi

From industries large and small, to the kitchen table tinkerer, to the classroom coder, we make computing accessible and affordable for everybody.

www.raspberrypi.com

so long,

Hias

I think you may be out of luck, the soundbar only seems to have an HDMI eARC input and no standard HDMI inputs where you could connect the RPi to.

You have to connect the soundbar's eARC input to an (e)ARC output of your TV.

so long,

Hias

It might be worth to contact suntdek support and ask for open source drivers with source code - with their closed source binary drivers it's impossible to debug any issue.

In the (likely) case they won't do that it's up to sundtek to debug the issue - so again, ask sundtek support about that.

so long,

Hias

You have to name the keymap custom_remote.toml if you use the new toml format - keymaps without the .toml extensions are considered to be in the legacy format.

so long,

Hias

Quote from noggin

Is this the case with all versions of the Argon One cases do you know? They switched from Micro-HDMI to Fullsize-HDMI on their Pi 4B cases - do both have issues with lack of Hotplug, SDA and SCL pass-through on their extenders?

Ah, didn't know they now have fullsize HDMI, so there's some hope the situation improved.

So far I only know about issues with their old micro HDMI versions. They had quite some QA / production issues with the board (can't say how high the actual failure rate was, though):

- pin 19 (HPD) shorted to the GND/shield pad next to it, so hotplug detect didn't work

- cold joints / no connection on some HDMI pins/pads

So basically issues in their (reflow?) soldering process which OFC is more critical with the small pitch of micro HDMI connectors, compared to full size ones.

Issues with soldering are quite common, it's very rare to hit 100% yield rate, but usually QA (automatic optical and electrical inspection systems) should have caught those.

so long,

Hias

Quote from MatteN

Last tested was LibreELEC-RPi4.arm-11.0-nightly-20221006-f15e1de, same behaviour.

No log means no problem

Please test with the latest nightly build.

We've now updated to linux kernel 6.0 and won't be looking into issues anymore that once happened with kernel 5.15.

And please post full debug logs created with the "pastekodi" command or the log uploader function in LibreELEC settings.

Cut down logs or "me too" posts with no info don't help us.

https://wiki.libreelec.tv/support/log-files

so long,

Hias

Thanks a lot for the logs and also your edid!

I could reproduce the issue here, it comes from the speaker allocation block in your edid - it reports left, right and LFE (which is not totally wrong but a bit weird as your soundbar only support 2 channel PCM) - and then the hdmi audio driver and kodi trip over that.

The easiest workaround is to simply remove the offending speaker allocation block from the edid (you don't need it, it's only needed for multi-channel PCM output which your soundbar doesn't support)

You can do this eg with AW EDID Editor (there are other programs available but I found that to be the most reliable and easy to use one and it also runs fine under Wine)

AW EDID Editor | Analog Way

Powerful solution to create and edit EDID files for an optimal compatibility between your sources and displays.

www.analogway.com

First ssh in and run getedid create. This will dump your current edid, save it to /storage/.config/firmware/edid/edid-HDMI-A-1.bin

Then copy this file over to your PC, open it in AW EDID Editor, change to the "CEA Extension" tab and remove the "Speaker Allocation" entry in "Instantiated Blocks", and save the changed edid.

You can also use the modified edid in the attached zip (I used the edid you posted) but keep in mind that if you change the TV, HDMI ports etc it might not match anymore and you could run into CEC issues etc - in that case you have to do the steps above.

Now copy the modified edid back to your RPi, overwriting the existing /storage/.config/firmware/edid/edid-HDMI-A-1.bin file.

Then run create-edid-cpio on your RPi - this will update /flash/edid.cpio so the edid is available early during boot as well.

Now reboot and HD passthrough should work fine.

Note: if you switch to a different TV / soundbar / AVR / ... you have to remove the edid changes first - simply run getedid delete on your RPi and reboot to do that.

so long,

Hias

eLr0n can you please test with the latest LE10 nightly build from here:

https://test.libreelec.tv/10.0/RPi/RPi4/ - just copy the latest img.gz (currently 20221005) to the update share/folder and reboot.

If this doesn't help add "drm.debug=0x04" to the end of /flash/cmdline.txt (it must all be on a single line, immediately after "quiet", just separated by a blank), then reboot, reproduce the problem and upload a full log (either with the upload log file option in LibreELEC settings or via ssh with the "pastekodi" command) - just post the URL here.

The log should give more hints why it fails.

so long,

Hias

Did you maybe run "getedit create" at some point in time?

If yes, then RPi will still be using the old edid of your HD TV.

In this case simply run "getedid delete" and reboot.

so long,

Hias

Had a look at github issues, it's a known problem (Netflix changed APIs), new netflix plugin version with a fix should be released this weekend

TypeError: __init__() missing 2 required keyword-only arguments: 'request' and 'response' · Issue #1425 · CastagnaIT/plugin.video.netflix

Netflix add-on version 1.18.10 Operative systems used Windows Kodi version used Kodi 19 (Matrix) Description of the bug I open Netflix addon and when i press…

github.com

so long,

Hias

This looks like a netflix or netflix plugin issue - report it on the netflix plugin repo

GitHub - CastagnaIT/plugin.video.netflix: InputStream based Netflix plugin for Kodi

InputStream based Netflix plugin for Kodi. Contribute to CastagnaIT/plugin.video.netflix development by creating an account on GitHub.

github.com

so long,

Hias

LE has no knowledge about the used kodi in an update and which addons might get disabled then by kodi. So there's no way we could tell you upfront what kodi will do.

If something goes wrong with a nightly then restore your backup - or stick to official release builds.

so long,

Hias