Posts by HiassofT

FYI: There are now also MAME and ScummVM addons available in our repo.

so long,

Hias

Take the bootcode.bin, start.elf and fixup.dat files from the FAT partition of the working LE12 installation and copy it over the files on the FAT partition of LE9.2

so long,

Hias

kurai Today's nightly (20260507) added support for Generic
https://test.libreelec.tv/13.0/Generic/Generic/LibreELEC-Generic.x86_64-13.0-nightly-20260507-6030451.img.gz

so long,

Hias

I'm happy to announce that I managed to create a few browser and game addons for LE13.

The 64bit ARM versions (aarch64, eg for RPi4 and RPi5) have just been uploaded to the LibreELEC addon repo, you'll now find them in the "Progams" section. Generic/x86_64 will follow at a later point.

Under the hood these addons use the flatpak versions in a minimal wayland session with kodi stopped.

You can configure the display resolution for these addons in the new "Exteral programs helper" addon - I recommend using 1920x1080 if you are a couple of meters away from your 4k TV, otherwise the browser GUI will be really tiny.

In the new "Flatpak" addon you see a list of all installed flatpaks and can update them via the context menu ("Check for updates").

The new "Terminal (Foot)" addon is also available for 32bit ARM from our repo, this is a native program, not a flatpak. You can configure the font size via it's settings.

Note: browsers have become real monsters today, you need at least 2GB of RAM to run them and you also need several GBs of space on your /storage partition (I recommend at least 8GB).

Also note that retroarch currently doesn't the cores buildbot URL configured by default on aarch64, you need to manually configure it to http://buildbot.libretro.com/nightly/linux/aarch64/latest/ in the Updater settings to download cores.

And: make sure you are running the latest LE13 nightly build, compatibility with older nightlies has not been tested.

so long,

Hias

Set ARCH=aarch64, not ARCH=arm

so long,

Hias

Running "create-edid-cpio" is necessary each time you manually change the .config/firmware/edid/ file(s).

"getedid create" automatically calls that to create the initrd after retrieviing the edid from the TV. In addition to that it modifies config.txt and cmdline.txt to enable the edid override.

Since you already ran "getedid create" before you only need to run "create-edid-cpio".

so long,

Hias

MRudolph the EDID contains the physical HDMI port address so if you switch to a different TV or even to another HDMI port on your TV that'll easily break CEC if you ran "getedid create" before.

But since your RPi4 seems to detect the old TV fine you could use that to grab the EDID of your old TV and then use it on your RPi5:

Start LE12 on your RPi4 with HDMI-A-1 connected to the HDMI port of your TV which you'll then use for your RPi5.

First make sure you have no edid override in place, if in doubt run "getedid delete" and reboot so the RPi will actually read the EDID from the TV.

Now ssh in and run "getedid create" to grab the edid, you'll then have a edid-HDMI-A-1.bin file in /storage/.config/firmware/edid/ which you need to copy over to your RPi5.

On the RPi5 make sure you have an edid override (from getedid create) in place, the one from your new TV will do fine, then overwrite the /storage/.config/firmware/edid/edid-HDMI-A-1.bin file with the one from your RPi4 and run "create-edid-cpio" to also update the initrd (which contains the edid firmware override for early stage boot).

Now the RPi5 will have the correct edid of your old TV and hopefully CEC might work better - you may need to wipe CEC settings in kodi, it could also still have physical address overrides and then things go south.

But CEC is a bit of a mess, every TV vendor seems to implement it differently, so it could also be that you'll still need to switch TV inputs to get it working.

so long,

Hias

Then better go to the RPi forums. If only the second HDMI port shows HDMI/EDID in the bootloader but not the first one then this could also be a hardware fault of the RPi (in that case you should return it to the seller for a replacement) - but double-check with the RPi folks, they might have another clue or advice for you.

so long,

Hias

Quote from MRudolph

Do you have a source for me on how to do that?

Try creating an autostart.sh file with these two lines (see https://wiki.libreelec.tv/configuration/…wn#autostart.sh), then reboot:

rm -f /dev/cec0
ln -s /dev/cec1 /dev/cec0

Note that I haven't tested this. If it doesn't work then remove the autostart.sh file.

so long,

Hias

Still nothing kodi related in your paste, but I noticed you are running piracy crap. You are in violation of our forum rules so support ends here.

so long,

Hias

We've got a fix for the RPi crash https://github.com/LibreELEC/LibreELEC.tv/pull/11147, it should land in nightlies soon.

so long,

Hias

After enabling debug logging you need to reboot, then reproduce the issue, then upload the crash log - the journal in your log didn't show any signs of a kodi crash.

Verify the uploaded crash log and be sure it contains the kodi log at the beginning - sometimes creating a crash log can fail if it gets too large.

so long,

Hias

There's no kodi log/crash info in the log. Please try again.

so long,

Hias

Please post a debug log instead of AI-slop, the latter doesn't help us much.

My guess is that could be caused by the recent addition of EAC3 transcoding in kodi https://github.com/xbmc/xbmc/pull/28001 which got included in LE build 20260329-14b0c24. In that case best open a kodi issue https://github.com/xbmc/xbmc/issues

I'll let your AI figure out if it's EAC3 related or not and if you should open an issue on kodi's repo

so long,

Hias

Quote from MRudolph

For me, the simplest solution would be if CEC were re-enabled for HDMI 1.

That's unfortunately not easily possible - libcec hardcoded /dev/cec0 as the device and the first attempt to support /dev/cec1 as well failed miserably.

The best workaround IIRC is to remove /dev/cec0 and symlink /dev/cec1 to /dev/cec0 (eg in autostart.sh).

so long,

Hias

As the bootloader has issues detecting the TV it could be some hardware issue/difference between RPi4/5 or some difference in the closed-source bootloaders.

It's best to either ask on the RPi forums https://forums.raspberrypi.com/ or open an issue on the rpi-eeprom bootloader repo https://github.com/raspberrypi/rpi-eeprom

so long,

Hias

The RPi crash in current nightlies is related to hardware deinterlacing.

If you disable that in "Settings"->"Player"->"Allow hardware deinterlacing with DRM PRIME" (you need to enable expert mode to see that) playback works fine and interlaced videos will use the bwdif deinterlacer (which gives better quality than the HW deinterlacer).

Still, we're trying to figure out what exactly causes the crash and fix that to get HW deinterlacing back (RPi2/3 don't have the CPU power to deinterlace HD videos in software).

so long,

Hias

Thanks a lot for the debug backtrace, we're already investigating the RPi issue

so long,

Hias