Posts by lrusak

Please post a crashlog. /storage/.kodi/temp/kodi_crash.log

Quote from tony013

Pi does not have a reset button ...

I read about booting support from usb and network - usb needs lot of plug changes too, so may be network may be the way to go?

How do you get rid of all that weakness?

This may be obvious but I tend to unplug/plug the USB power cord at the wall side rather than the RPi side to help wear.

Quote from reljaz

I was also in need to have VNC server on rPi4 with latest LibreELEC 10 beta.

Thanks for the info @Irusak.

Do you have some alternative how to have GUI remote desktop interaction with rPi4 on LibreELEC?

Thanks

It's not possible at this time

There is currently a known issue with USB hard drives on RPi4 RPi 4B, external HDD randomly freezes · Issue #3981 · raspberrypi/linux · GitHub

looks like it crashed because it was waiting for something from the jellyfin add-on

Quote from slappy

RPI4 development is a big deception. No 3D mvc support and no HDR after over one year. We will have it running at the same time everything will move to 8k or other newest tech. In the 2000 years the RPI development was able to catch up but not anymore. Better to go Vero 4k or stick with PC with madvr for 3D and 4K hdr.

RPi4 HDR video and HBR audio are WIP but they do work on current betas

Add the following to config.txt

dtoverlay=gpio-ir,gpio_pin=23

Then download the lircd file and put it into place

wget -O /storage/.config/lircd.conf https://raw.githubusercontent.com/Argon40Tech/kodiaddon_service_argonforty-device/matrix.script.service.argonforty-device/script.service.argonforty-device/resources/data/argon.lircd.conf

Though you may have to make your own remote config

then reboot.

Some info: Need help understanding Argon One IR control

/storage/.kodi/addons

well, you can just call make install in makeinstall_target() if that's what you need

I'm not really sure which misconfiguration you are talking about?

The libva driver shouldn't crash when initializing on old hardware and should gracefully fallback to the older libva intel driver.

A bug report should probably be made to the media-driver github repo about that.

Quote from harun-cuk17

When is it possible to set the webui interface of the rpi4 to 2160p with 60hz ?

I assume you mean the Kodi GUI, but the answer is when it's ready

some folders are installed automatically if present as part of the normal build, "system.d" is one of them, see LibreELEC.tv/install at master · LibreELEC/LibreELEC.tv · GitHub

As for your other question I'm not really sure what you are asking. Python packages typically require manual setup to use. Please see this package as a reference. LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub

Note that Pillow requires compiling some c modules and that's why it has a separate build step.

There is no point in doing that as libva maintains it's own mapping for drm drivers and libva drivers. see: libva/va_drm_utils.c at master · intel/libva · GitHub

Quote from tony013

Thanks a lot for that hint. Very helpful!

Good to know the background for package usage in image creation!

Actually pigpio was just the first package to add. Others will follow.

How do I create a package, that consists of just a few files, that need to be copied unchanged to given location?

Is the root-filesystem assembled at runtime (and so I have to copy the files to different filesystems at build time), or can I specify whatever path I want as copy destination?

see here for some hints: LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub

You just need to use

PROJECT=Rockchip ARCH=arm DEVICE=RK3399 scripts/build pigpio (you don't need the package folder)

And to get it in your image you need to make sure it's actually referenced somewhere

you can either hard code it somewhere like LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub

or you can use the custom options file at ~/.libreelec/options and add ADDITIONAL_PACKAGES+="pigpio"

Quote from smp

So there is no way to keep both methods? E.g. EGL as the default one and direct to plane for the hardware that can support YUV planes?

There is no reason to support both. The EGL method will be universal and the direct-to-plane method doesn't offer any benefits. With the direct to plane method you also can't do things like tonemapping, brightness/contrast adjustment, etc.

Quote from Deathcrow

Just tried it out. Yeah, looks fine as well. Same subtitle problems though:

Please post a debug log, it's likely that it's falling back to EGL

Quote from smp

Both using direct to plane. When EGL is selected HDR does not work.

I don't believe so. Direct to plane even works on an old Apollo Lake SoCs, not to mention the new Tiger Lake (already confirmed working), Rocket Lake, Elkhart/Jasper Lake.

I don't think that's really possible. Using direct-to-plane requires YUV planes which aren't provided when using LSPCON. So unless intel has updated there driver to expose this it won't work.

If you think it does work please post the output of the "modetest" utility.

I'm not sure which branch your are using of mine at this point but as I said the direct-to-plane method won't be merged for intel. So really this branch is the only way forward (but likely has a lot of bugs and quirks) Commits · lrusak/xbmc · GitHub