Posts by chewitt

Raspberry Pi has some closed-source broadcom boot firmware which some folk get upset or uptight about, but unlike Rockchip who pay lip-service to upstream support and still have closed-source blobs and NXP who hide their entire ecosystem behind an NDA/paywall they openly provide A1+ support for their boards and the software ecosystem around them (both the open and closed-source bits). Pi devs have also been funding a lot of upstream development for their hardware too; because their own resources are limited and time-to-market counts so major things like mesa have been subcontracted to people with the knowledge and expertise.

NB: LE has fairly terrible software support for all the (now dated) Amlogic boards you mentioned. Rockchip support is reasonable. Allwinner is the best of the three. RPi4 still wins the best supported board medal though.

Quote from andymarc

Can anyone assist?

This is the LE forum. The folks who create CE hang out somewhere else.

Where are the symlinks pointing to?

If the NAS supports WOL and some form of scriptable sleep/shutdown command it might be possible to create a startup script that sends the magic packet to wake the NAS and delay Kodi/Emby start until SMB shares are online, and to then send a shutdown command when the HTPC device is turned off. Neither app supports "If NAS source is online use config A, if NAS source is offline use config B" logic; they both expect a single configuration and for that config to be valid. The systemd suggestion simply allows scheduling logic (and scripts) to be used that ensure sources are available before Kodi or Emby container start. I'm not sure if you'll find any howto or prior art for WOL in the forum; it's not a thing that comes up often and most folks ultimately accept that NAS devices are designed to be used in an always-on state.

I would investigate using systemd to locally mount the remote SMB shares so they become part of the local filesystem; instead of using the SMB clients in Kodi/Emby. The advantage of this approach is you can configure startup/shutdown dependencies; i.e. the systemd service for the Emby container (or Docker as a whole) can be tweaked to depend on the SMB mount being active first.

Probably. Grab a spare SD card and see for yourself.

I never heard of mediasources.xml before, but sources.xml (where you define sources) and passwords.xml (password mappings to sources) are definitely valid. In the past I had creds in sources.xml but at some point that stopped working and the mapping (as posted above) was needed.

The release notes refer to kernel overlays that provide(d) support for additional kernel modules to support DVB cards that are not upstream (lots of them). I'm not aware of any changes to the Kodi PVR clients.

NFSMOUNT

-- MOVIES

-- Movie1 (2012)

-- Movie2 (2018)

-- TVSHOWS

-- Show

-- Show.s01.e01.mkv

-- Show.s01.e02.mkv

-- AnotherShow

-- AndAnotherShow

^ I'd use a single NFS mount with separate folders underneath it for content. Edit /storage/.kodi/userdata/sources.xml to change the paths to align with that. Delete existing DB files, restart Kodi to start over clean, then set the content types and scrapers to use for each source and then rescrape. Don't obsess over trying to reuse existing library data. As long as you named everything correctly in the first place it will all (re)scrape easily.

http://ftp.sunet.se/mirror/archive…media/openelec/ <= OE v4-v6

https://mirror.math.princeton.edu/pub/openelec/ <= OE v7-8

^ 10 seconds of Google searching found some old OE mirrors that still have files for download. You can probably get something to install and show the Kodi home-screen, but when it refuses to access anything on the internet due to expired TLS certs and other issues that impact on old software, there will be zero support in this forum. We forked from OE in 2016 and anything before LE is not our problem.

NB: The OE v8 release is after we forked LE and it has a ton of problems due to a large number of changes being added without any prior testing (one of the several reasons we forked) .. so best to skip that one.

This is the CPU opp-table: https://github.com/torvalds/linux…3399-t-opp.dtsi

It looks like support for the 4SE board has been submitted and merged upstream: https://patchwork.kernel.org/project/linux-…@collabora.com/ .. although I don't see that in torvalds/master (will become Linux 6.6) yet, bu you should be able to pick/backport those patches onto the Linux 6.5 kernel we use in LE master easily.

https://wiki.libreelec.tv/development/build-basics

https://wiki.libreelec.tv/development/git-tutorial

I moved all my devices to LE12 for testing so can't test LE11, but in LE12: Settings > Display > Calibration > Video Calibration exists. You may need to have the GUI in advanced or expert mode to see the option.

Kodi is not a heavy-CPU application unless you're software decoding lots of media, but using the non-T device-tree means you are over-clocking the board, so you need to ensure it's properly cooled via fan or case.

Kodi feature requests should be made to Kodi developers via the Kodi forums: https://forum.kodi.tv/forumdisplay.php?fid=9

Kodi feature requests should be made here: https://forum.kodi.tv/forumdisplay.php?fid=9

I suggest reading the link I already posted.

It's a while since I played with an RPi3 but something around 10s is normal for most of ARM boards we support.

You figured out that you need to replace <service> with the actual service name, right?