Posts by HiassofT

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

I can't comment on the C5 (no idea what that should be) but it's more likely that's standard network traffic in your LAN, coming from other devices (or your router) that reaches your device.

Lots of network protocols (ARP/ND, MDNS, ...) rely on small broadcast or multicast messages that are transmitted to all devices in a LAN segment - and those cause the network LEDs to blink.

You'll see the same blinking on PCs, switches etc, too - if they have LEDs.

so long,

Hias

OK, weird.

You could test if it makes a difference if the DAC is plugged in before you power up the RPi vs if you plug it in after you powered up the RPi.

If it never shows up it could also be some hardware fault.

so long,

Hias

There are no signs of a USB device in the log, not even an error during enumeration.

Please give the LE13 nightly a try (ideally on a separate SD card), if this doesn't work either then it's best to test with the Raspberry Pi OS and move testing over to the RPi forums - it all looks like a compatibility issue between the USB DAC and the RPi's USB controller.

so long,

Hias

If the DAC doesn't show up with lsusb it points to a general USB (compatibility) issue. Please run "pastekodi" with the DAC connected so we can see the full dmesg output and system logs.

It would be worth testing with the latest LE13 nightly, it ships with a newer kernel that might help.

so long,

Hias

Hello, seriously, just complaining without any info or logs?

Hint: if you only get 1024x768 and no HDMI audio this usually means the RPi couldn't detect the TV/receiver and was unable to read the EDID - and is running with some fail-safe defaults.

So check the cabling (especially avoid micro<->full-size HDMI adapters and keep in mind that cases with built-in HDMI adapters are rather prone to this sort of issue).

Time will be set correctly once you configured your timezone and are connected to the network/internet so time can be retrieved from NTP servers.

so long,

Hias

Quote from VLouis

For LE installation in that case enough 1-2GB space...

That's very tight, my .kodi folder is about 2GB (thumbnails take quite a bit of space) and I don't have a large music/video library.

Calculate at least 8-16GB of space for the storage partition, remember you also need quite a bit of scratch space - eg Widevine updates need to download and store large image files, kodi updates need space for database migrations (which results in separate, new database files) etc.

No big deal with current SD cards which are 32GB and up.

so long,

Hias

Is this on a RPi5? If yes, just use it's netinstall feature.

Make sure the bootloader EEPROM is up-to-date, power it up with keyboard , mouse and ethernet cable connected and press "shift" to start the installer / RPi Imager.

so long,

Hias

Power up your RPi4 without the SD card and any other devices connected (i.e. only connect power and HDMI) and post the output of the "display:" line shown on screen.

so long,

Hias

We use kodi upstream sources with a couple of patches applied on top, the common patches are in https://github.com/LibreELEC/Libr…er/kodi/patches and the RPi specific ones are in https://github.com/LibreELEC/Libr…Pi/patches/kodi

Kodi version/githash and cmake/configure options are in the package.mk file https://github.com/LibreELEC/Libr…kodi/package.mk

Our RPi ffmpeg patches are in https://github.com/LibreELEC/Libr…g-001-rpi.patch and are sourced from jc's ffmpeg tree (the same that's used for RPiOS), the commit message of the patch file will tell you the exact version used, currently that's https://github.com/jc-kynesim/rpi…4d573df97223cd9 from the test/8.0.1/main branch - might be easiest for you to use ffmpeg sources directly from there.

Also see the package.mk for configure options https://github.com/LibreELEC/Libr…mpeg/package.mk

so long,

Hias

The instructions in the wiki are outdated and wrong, /usr/lib/firmware should be added to the cpio, not /lib/firmware (the latter breaks the lib->usr/lib symlink and then everything goes south).

Just use the "create-edid-cpio" script which is included in the image, it'll create a working /flash/edid.cpio with all files from /storage/.config/firmware/edid

so long,

Hias

Looks like you added vc4.force_hotplug... as a second line - this doesn't work, everything in cmdline.txt needs to be in a single line.

Move that up right after console=tty0, separated with a space, and try again.

so long,

Hias

Are you running Generic-Legacy?

If yes I strongly recommend you resize the 512MB boot partition to 1GB or create a backup, do a fresh install and restore the backup. 1GB is the default for Generic in LE12.2 and newer.

The Generic-Legacy image got really fat, mainly due to the Nvidia driver which is huge, and likely you'll soon run into issues on updates.

so long,

Hias