Posts by chewitt

NB: Without the workaround in https://github.com/LibreELEC/LibreELEC.tv/pull/8970 Kodi makes a large number of connections to the MariaDB server (making repeated connections trying to connect) and this may cause MariaDB to stop responding. Even if you update to an LE image with the workaround included, MariaDB may need to be restarted before it will accept connections again.

I've asked one of the ffmpegdirect maintainers if he can decipher the request; because the Tidal2 repo you've linked to only shows how to compile the add-on. It contains no mention of what technical change is required somewhere.

Quote from Da Flex

Maybe a different modifier is in use on DRM Prime:

HDR probably doesn't work without DRMPRIME, which is why I keep trying to stop people disabling it.

Quote from Dutch87

I did the command but still I can not see the /flash/syslinux.cfg or /flash/extlinux.conf files...

because RPi boards use cmdline.txt .. as written (twice) already.

I normally associate that error with bad credentials (or lack thereof). At some point Kodi swapped from simple sources.xml to needing a combo of sources.xml and passwords.xml to work, but that was some time ago. You can map device hostnames to IP's using /storage/.config/hosts.conf.

Quote from Da Flex

Maybe DRM Prime has an HDR bug on RPi5

Nope .. at least not one affecting the 40K+ RPi5 users we have (else there'd be more folks showing up with issues).

All the error messages flagged above are normal/harmless, and show it setting an HDR colourspace and 12-bit output. The RPi side appears to be doing everything correctly. I think the solution lies in AVR and/or TV settings, or port combinations.

Typo .. "getedid" not "getedit" .. the wiki article is still correct, and cmdline.txt is present (or the board won't boot).

mount -o remount,rw /flash

Or just run "getedid create" as previously instructed and it'll do everything for you.

LEIoT:~ # docker version
Client:
 Version:           26.1.3
 API version:       1.45
 Go version:        go1.22.3
 Git commit:        b72abbb6f0351eb22e5c7bdbba9112fef6b41429
 Built:             Fri Jun  7 14:43:10 UTC 2024
 OS/Arch:           linux/amd64
 Context:           default

Server:
 Engine:
  Version:          library-import
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.22.3
  Git commit:       library-import
  Built:            library-import
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.17
  GitCommit:        3a4de459a68952ffb703bbe7f2290861a75b6b67
 runc:
  Version:          1.1.12
  GitCommit:        51d5e94601ceffbbd85688df1c928ecccbfa4685
 docker-init:
  Version:          0.19.0
  GitCommit:

Odd .. this is what I see ^ albeit this is with a custom image where Docker is embedded (not installed as an add-on as there's no Kodi in the image) but I'd expect the results to be the same (as same build system).

Nothing changed and "getedid create" still works the same as the last 5+ years. RPi boards store boot params in /flash/cmdline.txt.

I've been able to replicate the issue with my C2 board. It boots KERNEL but then fails to load SYSTEM with the famous "Error in mount_flash: mount_common: Could not mount LABEL=LIBREELEC" and eventually the UART console fails to the initramfs shell where I've been able to get some logs which show an error with the ddr-50 mode:

Combining the tf_io GPIO_OPEN_DRAIN patch and removing sd-uhs-ddr50, the card I'm using now installs/boots/reboots fine.

Please retest with: https://chewitt.libreelec.tv/testing/LibreE…droid-c2.img.gz

Maybe some info in here: https://github.com/LibreELEC/documentation/pull/18/files

Feedback on the content appreciated. If it 'works' I'll merge it and clean-up the wording a little. I've never network booted any of my devices (and not a trick I need to learn) and nobody else has ever confirmed the text.

Just compress the log in a zip file and upload it somewhere

Feb 27 18:26:11.509638 INTSVC-STREAMPI connmand[575]: Skipping server 172.21.21.254 KoD code RATE
..
Feb 27 18:26:25.768188 INTSVC-STREAMPI connmand[575]: Skipping server 172.21.21.254 KoD code RATE
..
Feb 27 18:26:39.762246 INTSVC-STREAMPI connmand[575]: Skipping server 172.21.21.254 KoD code RATE
..
Feb 27 18:27:01.976455 INTSVC-STREAMPI connmand[575]: ntp: adjust (jump): +8815445.461668 sec
Jun 08 20:11:07.439421 INTSVC-STREAMPI connmand[575]: eth0 {add} route 82.165.8.211 gw 172.21.21.254 scope 0 <UNIVERSE>
..
Jun 08 20:11:07.499950 INTSVC-STREAMPI connmand[575]: Skipping server 172.21.21.254 KoD code RATE
..
Jun 08 20:11:22.227952 INTSVC-STREAMPI connmand[575]: Skipping server 172.21.21.254 KoD code RATE
Jun 08 20:11:36.227660 INTSVC-STREAMPI connmand[575]: Skipping server 172.21.21.254 KoD code RATE
Jun 08 20:12:05.538565 INTSVC-STREAMPI crond[438]: time disparity of 146925 minutes detected

(re)configure your NTP server to stop sending Kiss of Death (KoD) responses when we attempt to sync against it and we'll manage to reset the time much earlier in the boot sequence. Or just leave NTP unconfigured and we'll default to pool.ntp.org servers which normally work fine for people.

As nice as those cases are, we've seen a lot of silly problems with them. YMMV.

It was located in /storage/.config/hwdb.d but I did some searching on the internet among other distros and consolidated all the ok button hwdb entries I could find into a single file; including the OSMC remote changes. Once that was merged the 99-osmcef.hwdb file wasn't needed anymore. You can still create your own files there.

Official:Forum rules/Banned add-ons - Official Kodi Wiki

No support for you in this forum.

HDMI was submitted last week. That opens up the option for LE to create an image that software decodes all media, which will be quite usable as RK3588 has a strong CPU. Otherwise we now need to wait for codecs. That's always the tricky bit that takes ages for developers to get done (and get right). Meanwhile .. time passes.