Posts by chewitt

Quote from mega-samu

Have you implemented the latest changes for panfrost for the s912? Experimental Panfrost GLES 3.0 support has landed in Mesa

Unlikely in Oleg's images because LE master is using Mesa v20.x and the changes have gone into Mesa master for v21.x. The GLES 3.0 changes are not particularly relevant for Kodi support as Kodi runs under GLES 2.0. If you're enquiring about overall Panfrost support ..it runs great on S912 now (has been passing all dEQP tests for some time) and there are some Khadas VIM2 boards installed in the Mesa CI lab now so that all Midgard changes are run against T820.

NB: In the last week I organised a bunch of Bifrost using board samples for the Panfrost devs and Bifrost work has now kicked off! It will be a while before there's usable code, but once that happens, a single LE image that supports GXBB thru SM1 hardware is within our sights

The majority of 4K media is under 4K30 (the only 4K60 content I have is test media) and the Pi hardware performs better in terms of overall power use and thermal output (both of which impact stability) without 4K60 support enabled. LE defaults the GUI to 1080p and almost all 4K capable TVs will do a better job of upscaling the Kodi 1080p output to 4K than Kodi does upscaling 720p Estuary to 4K. RPi4 is a nice bump in performance over RPi3 but at the end of the day it's still a low-spec ARM board. Unless you really do need to run something at 4K60, it's best to leave the default config as-is.

I think original ION will be in the too-old bucket now .. and the 304.xx driver is not ABI compatible with the versions of X11 that we ship in the 9.2 release so anyone seeking older driver support will need to downgrade a few things before building an image. In older LE versions it used to be possible to do a simple tweak to the nVidia driver version and rebuild, but that is no longer the case.

Custom EDID [LibreELEC.wiki]

^ connect direct to the TV, dump the EDID to file and configure tthis permanently, then reconnect to the AVR.

If you want an image for RPi4 build from the libreelec-9.2 branch; master should build (no idea why you're seeing the error) but the resulting image is not going to be so usable as master is in the middle of a transition to GBM/V4L2 (no more MMAL decoding).

Nope.

I'll add it to the list of things to think about.

Run a disk check from Windows. It's likely there is an issue with the filesystem and Linux mounts the drive read-only to prevent writing new data to a damaged filesystem.

[Unit]
Description=TimeCapsule Mount Script
Requires=network-online.service
After=network-online.service
Before=kodi.service

[Mount]
What=//192.168.1.10/data
Where=/storage/data
Options=username=plez,password=crash,sec=ntlm,vers=1.0
Type=cifs

[Install]
WantedBy=multi-user.target

^ You are missing the [install] section .. so a copy/paste error as predicted

The same solution still works so it sounds like you made a copy/paste error somewhere. The easiest thing will be to scp the systemd .mount file from the old Pi directly to the new Pi.

It's best to ask the people who sell the CPU cooler then .. it's not our product or script.

Leia add-ons will be bumped to current in the next couple of days.

LE 9.2 does not and is unlikely to ever support HDR with RPi4 as it's based upon Linux 4.19 which pre-dates all the initial HDR support being merged into the Linux kernel, and because Kodi will move to a modern GBM/V4L2 architecture for most things running Linux as part of LE10 and Kodi v19. There is a considerable amount of ongoing activity to port RPi hardware away from the legacy MMAL decoder to the new GBM/V4L2 pipeline and once this is working people will start poking 10-bit video and HDR. So.. we're not there yet, but it will come.

I'm sure PINN has a forum somewhere where you can ask their developers why it doesn't work. I'm not aware of any LE staff members contributing to PINN so you're asking the wrong audience.

It's not a Kodi debug log, and there is no attempt to play anything. Fix those details and use "cat /storage/.kodi/temp/kodi.log | paste" and share the URL (less effort than copy/pasting to pastebin).

RPi4 software is not quite as mature as RPi3, but I've been using one as the family daily driver since before the public launch and I don't see any real-world issues with any media apart from HDR which plays with washed out colours due to the current lack of HDR support (but is otherwise fine).

In the absence of a debug log file which would allow us to spot the config errors and such, we have to guess. I'm guessing you've enabled 4K60 modes and set the GUI to 4K60 (or if not enabled, it's running at 4K30) and you haven't done refresh/resolution whitelisting, so 23.976 media is being forced to run at the desktop resolution (30 or 60 Hz) which requries resampling .. and RPi4 is still a low-power ARM device so that will suck and cause a nice stuttery experience.

Keep the desktop at 1080p60, set "adjust refresh" to start/stop and configure the whitelist for 1080p/4k 23.976/24/50/59.97/60 only, and don't force 4k60 in config.txt unless you actually intend to watch 4k60 media (there is none in use apart from test files).

There are lots of shitty Amlogic builds .. but I haven't heard of a "shitty" image before.

delete autostart.sh and run the commands from the SSH console