Posts by HiassofT

Can you please post some detailed log where kodi didn't like the addon version? We've been using that scheme for ages and haven't seen any issues so far.

so long,

Hias

The .1/.3/... at the end is nothing you need to worry about, it's simply the PKG_REV added to the original addon version - see eg here https://github.com/LibreELEC/Libr…o/package.mk#L7

Most of the time PKG_REV will be .1, sometimes when we need to roll out new versions of the addons (eg when important underlying dependencies have changed) we increment PKG_REV so kodi sees it as a new addon version.

so long,

Hias

Quote from niels

thanks, but why is the procedure distinct for rpi3 and rpi4 ? is it risky to upgrade on rpi3 ?

No, it's exactly the same. If you run LE 9.2 it's strongly advised you make a complete clean install of LE 10, as mentioned in the release note (see first post)

LibreELEC (Matrix) 10.0.2 - LibreELEC

Quote

Users of LibreELEC 10 Beta or RC1 get an automatic update to the final version. LibreELEC 9.2 setups will not be automatically updated, you will need to manually update.

Quote

So unless you are already running an image with Kodi 19 inside, a clean install is preferred. We apologize for the inconvenience, but we expect a much higher than normal support effort with in-place upgrades so it’s sensible advice.

so long,

Hias

Thanks for the info, this seems to be a widevine issue - see eg here https://github.com/xbmc/inputstream.adaptive/issues/877 - reverting back to older widevine version seems to help in this case

so long,

Hias

busfahrer303 thanks for the info! Can you please do a test with this build:

https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi4.arm-10.0-devel-20220319153448-7f96b91.tar

I've added a bit of additional debug logging which will show if and when scrambling is used. Please reproduce the issue and post a log from that build.

BTW: I strongly recommend setting kodi gui resolution to 1920x1080 60Hz, not 3840x2160 30Hz. Kodi will keep using GUI resolution as a fallback when none of the whitelist entries match and 30Hz is a very bad choice eg for 50/60fps video playback.

so long,

Hias

Just tested your sample and got the same "no signal" issue here. Not quite sure what's going wrong, I've informed RPi devs about it.

so long,

Hias

I'm still puzzled about your first log. Did you also have no picture after TV power off/on at 3840x2160 30Hz? Does it also happen at 1920x1080 (60 and 30 Hz)?

so long,

Hias

Try a different, HDMI Premium certified ,HDMI cable. RPi4 will now output 10/12bit video which means you'll see issues like that with cables that don't meet the specs.

See also here: RE: RPi Deinterlacer testbuild

so long,

Hias

busfahrer303 I just checked your log again and you don't seem to be using 4kp50/60 output - log shows kodi GUI runs in 4kp30 and the 720p video playback switches to 4kp25 - so scratch my comments about scrambling.

INFO <general>: GUI format 1920x1080, Display 3840x2160 @ 30.000000 Hz
INFO <general>: Display resolution ADJUST : 3840x2160 @ 25.000000 Hz (29)

BTW: I highly recommend configuring your display settings and whitelist as described in the wiki: https://wiki.libreelec.tv/configuration/4k-hdr

so long,

Hias

See here RE: Raspberry Pi Official Display does not work properly by default, so how can I make this fix stick with updates?

so long,

Hias

Running top in threads mode - just press "H" to toggle that - might also provide some clues.

Usual suspects are addons freaking out and background tasks like addon / library updates.

so long,

Hias

Flipping the screen upside down should work by setting the "panel_orientation=upside_down" video option in cmdline.txt but IIRC kodi still ignores it. Read more about it here:

Post

RE: CM3+ with LT070ME0500 DSI display

Display rotation should be possible by using the rotate and/or panel_orientation options of the video kernel command line parameter.

eg add something like video=DSI-1:1920x1080@60,panel_orientation=left_side_up

See the kernel documentation for infos about the video parameter: modedb default video mode support — The Linux Kernel documentation

The RPi forums might be a better place to ask about DSI/DPI panels and KMS details (I never used DSI/DPI displays myself), I found eg this post there rotate…

HiassofT

July 8, 2021 at 8:44 PM

so long,

Hias

Quote from chewitt

HiassofT are RPi2/3 are still using patchram to load BT firmware? .. these days everything else (AWL/AML/RK) is driven from device-tree. If RPi did the same we wouldn't see that error, no?

I just checked current RPi OS, it still uses the old hciattach method.

I guess switching to DT / kernel config might work somehow (latest RPiOS bt-uart script checks for that case) but I'm not sure if it'd catch all cases - like when using the miniuart-bt dtoverlay etc so I didn't dare to touch that area yet.

so long,

Hias

Keep distroconfig.txt as it is, just add dtoverlay=vc4-kms-dsi-7inch to the end of config.txt.

so long,

Hias

Add dtoverlay=vc4-kms-dsi-7inch to the end of /flash/config.txt.

so long,

Hias

Just post here in the forum - but please don't edit your posts if you add test results, always create a separate post with that info.

We don't get any notification when you later change your older posts (only on new posts) so no one saw the line you added about one day later that the test build didn't work either...

so long,

Hias

Quote from popcornmix

The hdmi pixel clock is actually the same.

12-bit YCC422 is 24-bits per pixel. Which is the same as 8-bit RGB444.

For 4kp50/60 yes, but 4kp30 and below will use 12bit RGB 4:4:4 if supported by the TV.

So lots of 10-bit videos (eg 4kp24 or 1080p) now can have 50% higher clocks than before.

so long,

Hias

Drop imageres and fanartres from your advancedsettings.xml, the GPU is running out of (CMA) memory.

You could also try increasing CMA memory a bit, add eg "dtoverlay=cma,cma-320" or "dtoverlay=cma,cma-384" to config.txt to get 320 or 384 MB instead of the default 256MB - but be careful, better keep image resolution at sane levels.

You can safely ignore the messages on the screen (and in journal), first two are because Silce/CM3 doesn't have a bluetooth chip, and the other two are normal (and harmless), too.

so long,

Hias