The internal id changed from 32 to 33 (the IDs are not guaranteed to be stable).
Either adjust the modetest line or use kmstest instead where you can specify the connector by name:
kmstest -c HDMI-A-1 -P "Broadcast RGB=1" < /dev/nullso long,
Hias
You need to use the FLIRC software on a PC to configure the dongle.
To linux/LibreELEC the dongle looks like a keyboard, not an IR receiver, and there's nothing you can configure.
so long,
Hias
FYI: the fixed inputstream.adaptive addon (version 22.1.10.2) is now available in the LE addon repo.
so long,
Hias
The "undefined symbol" error is caused by a recent change in inputstream.adaptive and affects widevine on all aarch64 platforms
I've PR'ed fixes to inputstream.adaptive and LE repos so this should work soon again without needing to fiddle around with the widevine library.
so long,
Hias
use "ARCH=aarch64" - arm is 32bit but RPi5 only supports 64bit
PROJECT=RPi DEVICE=RPi5 ARCH=aarch64 make image so long,
Hias
Use the other HDMI port. CEC is only supported on the first HDMI port (HDMI-A-1, the one next to the power connector).
LE 12.0.1 contained a change to support CEC on both ports, but kodi didn't cope with this well so this had to be dropped again.
so long,
Hias
Try adding vc4.force_hotplug=1 to /flash/cmdline.txt, see also this thread TV/AVR turns back on right after turning them off
so long,
Hias
It seems you are using a RPi4 with only 1GB of RAM and according to the logs it's running out of memory.
Try adding the following line to the end of /flash/config.txt
dtoverlay=cma,cma-384so long,
Hias
Even if you install the python modules for getting the netflix key this won't help much in LibreELEC as they'll spawn a chrome browser - which only exists for Generic Legacy and resides in a rather non-standard location so likely you'd have to modify the scripts.
Just run the script on a Windows/Linux PC or Mac.
so long,
Hias
In LibreELEC everything is running under / owned by root.
So, as a normal user you can't simply write to eg videos on the ext4 storage partition if you mount it on your PC.
You can copy files as root, or by using sudo, when the card is mounted on your PC or use scp or smb:// in your file manager when the RPi is running (smb will be a bit faster than scp).
so long,
Hias
It took some time but finally this feature was added to kodi and I've also backported it to LE12 and it's now in the latest LE12 nightly builds:
RPi2/3: https://test.libreelec.tv/12.0/RPi/RPi2/…-bd771c9.img.gz
RPi4: https://test.libreelec.tv/12.0/RPi/RPi4/…-bd771c9.img.gz
RPi5: https://test.libreelec.tv/12.0/RPi/RPi5/…-bd771c9.img.gz
so long,
Hias
The fix is now included in latest LE12 nightly builds
RPi4: https://test.libreelec.tv/12.0/RPi/RPi4/…-bd771c9.img.gz
RPi5: https://test.libreelec.tv/12.0/RPi/RPi5/…-bd771c9.img.gz
so long,
Hias
ffmpeg from the ffmpeg-tools-addon is built from plain upstream source without any RPi patches, so you won't get hardware acceleration on RPi with it.
Getting rid of the separate ffmpeg build and shipping a ffmpeg binary in the image (which will then have all patches, like in kodi) is on my TODO list but I didn't find the time to dig into this yet.
so long,
Hias
You may be able to get LE12 to boot by reducing cma memory in config.txt - see here
But don't get too excited, kodi really needs quite a lot of RAM (esp for all the artwork/cover/... images) and it'll likely often crash, therefore we don't officially support devices with less than 1GB RAM.
so long,
Hias
Do a clean LE build (i.e. remove all build.LibreELEC... folders) then it should work fine.
so long,
Hias
hmm, you seem to have both an NVME drive and a SD card inserted. Please run "blkid" and verify that you don't have identical filesystem UUIDs on those (that will happen if you do a raw copy of SD card to NVME and will create a mess).
Or just remove the SD card if you boot from NVME
so long,
Hias
Something is utterly wrong with your installation, first of all it should report kernel 6.6.45 on RPi and 6.6.46 on Generic - not kernel 6.6.28 (that was used on LE 12.0.0).
Try re-installing LE12.0.1 again. Just put the img.gz into the update share or /storage/.update folder and reboot.
so long,
Hias
and LE by default tries to force the highest resolution? If this was the case, then maybe it would be better to have LE start at a lower res by default on the first boot.
By default the Linux kernel uses the resolution that is flagged as the preferred one in the EDID (which it read from the connected AVR/TV) - so basically it's just following the wishes of the HDMI device which in general is a good thing.
Forcing some other resolution is quite tricky, there'd be some chance it's either too low or too high for some TV and thus that would again lead to "no signal" issues for other users.
The easiest solution is if you do that manually and choose the resolution you'd like - you can eg just append video=HDMI-A-1:1920x1080p60 to the end of cmdline.txt and the Linux kernel / LE will than use that instead of whatever the TV/AVR flagged as the preferred mode.
so long,
Hias
