Create a .libreelec/options file either in your home directory or in the root of the LE git directory and set ADDITIONAL_PACKAGES there. See LibreELEC.tv/options at master · LibreELEC/LibreELEC.tv · GitHub
Note that some projects set ADDITIONAL_PACKAGES so it's best to append to that variable. eg
ADDITIONAL_PACKAGES="$ADDITIONAL_PACKAGES kmscube"so long,
Hias
Just buy a 2GB or 4GB RPi4 (8GB is overkill for LE), exact rev doesn't matter.
so long,
Hias
on 9.2.4 (RPi4) the picture disappeared, while there is sound and hdmi cec works fine, I hear how the system reacts to pressing the remote control key, but I see nothing. The TV itself thinks that it is being given a signal, writes that it is there and writes the resolution, but the picture is just black. Changing the hdmi port doesn't help. This also happens when upgrading from 9.2.3 and during a clean install.
Can you please try if this build works LibreELEC-RPi4.arm-9.2-devel-20200817130411-96056bf.tar ?
Just copy it to the Update Windows share and then reboot.
See also this github issue for more info about the bug [BUG] · Issue #4523 · LibreELEC/LibreELEC.tv · GitHub
so long,
Hias
Screen tearing on LE9.2/RPi4 is a known issue. It will be fixed in LE10 with the switch to the full KMS driver.
so long,
Hias
You seem to have overclock settings in config.txt, can you test if that happens with stock config.txt, too?
mount -o remount,rw /flash
cp /flash/config.txt /flash/config.txt.bak
cp /usr/share/bootloader/config.txt /flash/config.txtso long,
Hias
Please someone with the issue post logs as cvh already requested multiple times in the github issue.
ssh into LE with black screen, then run pastekodi and post the URL you got on the console.
We have not seen this issue in local testing and without logs and details about your setup (which are included in the pastekodi log) we won't be able to do anything or give hints.
so long,
Hias
There are 2 issues with your config.txt:
dtoverlay=gpio-ir,gpio_in_pin=18you are still using "gpio_in_pin" instead of "gpio_pin" and also you can't use GPIO 18 - this is required by the I2S interface - dmesg/journal therefore prints this:
Apr 11 18:28:51 LE923zero kernel: pinctrl-bcm2835 20200000.gpio: pin gpio18 already requested by ir-receiver@12; cannot claim for 20203000.i2sYou have to connect the IR receiver to a GPIO that's not used by the DAC card, GPIO 17 should be fine, and then properly specify that in the dtoverlay line - eg gpio_pin=17
so long,
Hias
Please post your full config.txt and journal
pastebinit /flash/config.txt
journalctl -a | pastebinitso long,
Hias
dtoverlay=gpio-ir,gpio_in_pin=17
gpio_in_pin is wrong, you have to use gpio_pin.
so long,
Hias
Channel swaps with multi-channel PCM output is a well known issue on RPi4. It'll be fixed in 9.2.4.
so long,
Hias
Analog audio output is working fine here on RPi3B+ with LE 9.2.3 and current 9.2.4 development builds.
so long,
Hias
Optimizing for cortex-a72 resulted in odd issues, see eg my comment here add support for Raspberry Pi 4 by HiassofT · Pull Request #3597 · LibreELEC/LibreELEC.tv · GitHub
Could be (or have been) some compiler/optimizer bug.
Other LE deveopers noticed similar issues on other devices as well so we stuck to cortex-a53 which works fine.
It's hard to tell if optimizing for cortex-a72 would give any real-world performance improvements and as digging into possible compiler bugs isn't fun we haven't investigated that further.
so long,
Hias
Thanks a lot to all who tested (also LE staff and kodi forum users)!
The RPi4 HD audio passthrough code has now been merged into the LibreELEC master branch so our latest (and future) nightly testbuilds on Index of / have this feature built in.
I can't really comment on scraper / kodi label things (that's not my area of expertise), I mainly tested with various sample files in "Files" mode (not library) and that flagged both Dolby TrueHD and Atmos samples as "DOLBY-HD" (same for the DTS HD variants, that were flagged "DTS-HD").
so long,
Hias
Your dmesg is spammed with "Not enough bandwidth for new device state.". This indicates you're probably running into a limitation of the USB controller, see eg this thread here: Not enough bandwidth for new device state. - Raspberry Pi Forums
There's a beta USB firmware available here Raspberry Pi 4 VL805 firmware release 0138a1 - Raspberry Pi Forums which could help (it increases the maximum allowed size of isochronous endpoints).
First make sure that your bootloader and USB firmwares are up-to-date (in Settings->LibreELEC->Update). If they are up-to-date but you still have the issue you can try to update to the beta USB firmware. You can do this from LE as well - copy the vl805-000138a1.bin over, run rpi-eeprom-update -u vl805-000138a1.bin and then reboot.
so long,
Hias
LibreELEC 10 is still in pre-alpha development stage and although we have nightly testbuilds these are not recommended for general use. You have to be patient, I don't expect any official release to be out before the end of the year.
so long,
Hias
Screen tearing / update problems are known issues on LE 9.x/RPi4 and are resolved with the new video driver in LE10. Disabling sliding animations in the settings should help somewhat, but there are no plans to address these issues in LE9.2.
so long,
Hias
When tracking latest RPi firmware versions - which were very important for RPi4 - we totally missed that Raspbian had frozen the RPi0-3 firmwares at the April 15 version and only shipped updated RPi4 firmwares.
So LE 9.2.3 shipped with a newer RPi0-3 firmware than Raspbian (and OSMC which is based on that) that's causing issues on about one out of a couple thousand RPi3s.
so long,
Hias
