Posts by HiassofT

This is a known issue with Kodi Matrix/gbm. The milestone for fixing this has recently been moved to the next kodi version (20). See [GBM] add ability to screenshot with video plane by lrusak · Pull Request #18741 · xbmc/xbmc · GitHub

so long,

Hias

Correct. FKMS was basically a stop-gap to transition to standard linux drivers, all development is now focussed on KMS. 10-bit output, 4k etc will be added at some point but we don't have any ETA.

so long,

Hias

This is normal, 4k isn't supported by the RPi4 KMS driver yet, this still needs to be implemented.

so long,

Hias

Most devices use the kernel default of 128k (CONFIG_LOG_BUF_SHIFT=17), not sure why Generic is set to 64k. Would be best if you created a PR and change it to 17, too

hias@delle:~/private/libreelec/libreelec-git$ git grep CONFIG_LOG_BUF_SHIFT
projects/Allwinner/linux/linux.aarch64.conf:CONFIG_LOG_BUF_SHIFT=17
projects/Allwinner/linux/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=17
projects/Amlogic/linux/linux.aarch64.conf:CONFIG_LOG_BUF_SHIFT=18
projects/Generic/linux/linux.x86_64.conf:CONFIG_LOG_BUF_SHIFT=16
projects/NXP/devices/iMX6/linux/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=18
projects/Qualcomm/devices/Dragonboard/linux/linux.aarch64.conf:CONFIG_LOG_BUF_SHIFT=14
projects/RPi/devices/RPi/linux/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=17
projects/RPi/devices/RPi2/linux/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=17
projects/RPi/devices/RPi4/linux/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=17
projects/Rockchip/devices/RK3288/linux/default/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=17
projects/Rockchip/devices/RK3328/linux/default/linux.aarch64.conf:CONFIG_LOG_BUF_SHIFT=17
projects/Rockchip/devices/RK3399/linux/default/linux.aarch64.conf:CONFIG_LOG_BUF_SHIFT=17
projects/Samsung/linux/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=17

so long,

Hias

Yes, that should work fine. An MCE USB receiver (the HP branded ones you can find cheaply on ebay work very well) or switching to an RPi4 (which uses a "real" USB controller) are other alternatives to the ones mentioned on the wiki.

so long,

Hias

This is a well known issue, see here Infra-Red Remotes - LibreELEC.wiki

so long,

Hias

No problem at all, this isn't too obvious.

As a rule of thumb: it's best to forget everything you learned about or find on search engines on the legacy style of video configuration/setup on RPi (i.e. hdmi... settings in config.txt)

With the switch to the KMS video driver we now use the same methods to configure video as eg Intel/AMD or all other ARM/... platforms use.

so long,

Hias

This is normal - tvservice uses the legacy functions which aren't relevant for master builds anymore (we still kept the legacy programs for testing ATM).

Use eg modetest to find out what displays are connected and what resolutions are supported.

so long,

Hias

This is a question only the developer of the VPN manager addon can answer - it's not an official LibreELEC addon.

so long,

Hias

kill, killall and pidof are all available in LibreELEC, no need to install anything

LibreELEC (official): 9.2.6 (RPi4.arm)
xbmc:~ # which kill killall pidof
/usr/bin/kill
/usr/bin/killall
/usr/bin/pidof

so long,

Hias

Don't worry about automatic updates, we only enable that for minor version updates (eg 9.2.5->9.2.6). Major version upgrades (eg 9.2.x->10) need to be done manually.

You haven't mentioned which platform you are using, but if you are using an RPi then, yes, hyperion won't work on LE10 as hyperion(ng) doesn't have a working grabber for that yet.

On Generic//x86 the hyperion addon with the X11 grabber should work as before.

so long,

Hias

There's a PR to add hyperion ng BROKEN: Hyperion-NG by CvH · Pull Request #4673 · LibreELEC/LibreELEC.tv · GitHub but currently there are major issues in building it and it doesn't work.

As neither hyperion nor hyperion ng support GBM yet Raspberry Pi 4 with Libreelec v19 / Kodi Matrix, no grabber is working · Issue #983 · hyperion-project/hyperion.ng · GitHub it's quite useless for anything other than X11 on Generic/x86 platforms or external video grabbers in LibreELEC 10. As we'll be using GBM on all platforms except Generic/x86 in LE 10 it's quite low on our priority list ATM.

Any help (PRs, fixes, etc) would be highly appreciated though, if the issues are resolved then hyperion ng will be included in LE.

so long,

Hias

Quote from Anke

Question: is a SD moved from RPi3b it supposed to boot on RPi4 ?

No, not without quite a lot of hassle.

In the end, it will be a lot easier and safer if you just start from scratch with a fresh RPi4 installation.

so long,

Hias

Interesting, kodi-autostart.service seems to be pulled in by kodi.service, not kodi.target (which is a bit unusual...).

To get it back with kodi.service mask the following command should to the trick:

systemctl add-wants kodi.target kodi-autostart.service

For filesystem mounts it's better though to use mount units, see eg the nfs/cifs mount samples in .config/system.d and the mount unit documentation systemd.mount

If this filesystem is used for tvheadend recordings I strongly recommend ordering the mount unit before service.tvheadend42.service so the filesystem will be mounted before tvheadend is started.

so long,

Hias

Quote from MegaVectra

Format/Info : Advanced Video Codec

Format profile : High [email protected]

Like most other devices RPi doesn't support hardware acceleration for 10bit H264, so it has to be decoded in software.

so long,

Hias

Ah, sorry, I totally missed that you are not using an original Hifiberry card. In that case you'll have to contact the respective manufacturer of course, he's probably the only one who knows the implementation details about the card.

so long,

Hias

As I already wrote here RE: Should I change to Rpi 4B? contact the Hifiberry folks. Something is off either with your RPi4 or the soundcard.

I just tested with a plain LibreELEC 9.2.6 installation on a RPi4, plugged in my Hifiberry Digi Pro and it was detected fine.

so long,

Hias

Quote from og13

[ 5.242057] wm8804 1-003b: Failed to read device ID: -121

[ 5.242252] wm8804: probe of 1-003b failed with error -121

Remove the changes to config.txt and double-check if the card is plugged in correctly. The Hifiberry Digi Pro should be auto-detected and work out-of-the box.

If the error persists contact Hifiberry. The dmesg lines indicate there's a communication error with the wm8804 chip which could indicate a hardware fault.

so long,

Hias