Posts by chewitt

Kodi only supports upgrades not downgrades and I've never seen tools/scripts for downgrading. The sole option* is to update the LE12 DB so it finds new media and manually mark a few things read to align statuses. I'd also drop the newer DB version tables from the DB (if using a shared SQL DB) or delete the newer local DB files (if using local DB files) so that in the future when you update to LE13 again, Kodi migrates the current LE12 files instead of using outdated LE13 files.

* unless you're a database wizzard, but those people don't normally post here for help.

Just find the dtech thread which has links to his 9.2.8 image, download it to /storage/.update, and reboot. The only option newer is AMLGX (LE 12.0.1) which will boot from SD card but requires you to invoke recovery boot (toothpick boot method) to force u-boot into reading boot scripts and loading the right files. You can revert back to Android by removing the SD card. You can revert back to SD booting older LE images if you repeat the toothpick boot method.

Quote from primuspaul

So basically if I want to watch YouTube, I must download it with a regular computer and save to my NAS to watch on LibreELEC?

The Kodi repo has two YouTube add-ons (YouTube and Tubed). These days both require some "jumping through hoops" to register for personal Google API keys, but it's a one-time hassle. I said 'no' to SmartTube because there's no add-on blocking in either of them - what you see depends on your geo.

Connect the RPi5 direct to the TV and then run "getedid create" to capture the EDID data on the HDMI connection to file and then (re)configure boot files to use this and ignore the EDID data from the AVR. Then power down and reconnect to the AVR. Now if you power up .. things are working?

Nope.

S905 devices have a video output plane that supports 4K resolutions, but the OSD plane used for the Kodi desktop supports 1080p max. As Kodi skins are 1080p max and the S905 chips is too weak for 4K desktop with graphics; use 1080p and be happy. NB: The original Android image has been hacked to show a 4K option to stop users moaning about the lack of one, but when you configure this you get 1080p (the same silicon limitation of 1080p on the OSD plane applies).

If you don't see 4K resolutions in the whitelist for video playback (on the video plane) it's an EDID issue from the TV and there's a workaround in the EDID article in the wiki.

NB: dtech has an LE 9.2.8 image for WP2 if you want something marginally newer and with updated TLS certs.

Interesting. I started work on a tailscale add-on about 18-months ago, but didn't get that far down the path of a working install to really make anything work. I might have to redo things as I use Tailscale more than plain WireGuard these days. Although, I'm so time-poor at the moment that I wouldn't hold breath on anything progressing

echo "options em28xx card=92" > /storage/.config/modprobe.d/dvb.conf

That ^ would test the suggestion from one of the GitHub issues.

I wouldn't advise a direct update from LE 9.2 to LE 12 as the Python2 to Python3 change often causes crashing and issues that some users find challenging to self-recover from. Instead I would download the update .tar to /storage/.update and then stop Kodi and rename the /storage/.kodi folder to /storage/.kodi-old and then reboot to start the update. This will give you a clean LE12 install. Then it's a simple case of stopping Kodi and copying the essential bits of userdata config back (sources, addon preferences, passwords, DB files, thumbnails) before restarting Kodi.

reading s905_autoscript
reading KERNEL
reading uEnv.ini
reading /amlogic/meson-gxl-s905d-sml5442tw.dtb
load dtb from 0x1000000 ......
      Amlogic multi-dtb tool
      Single dtb detected
find 1 dtbos
dtbos to be applied: 0
Apply dtbo 0
   Uncompressing Kernel Image ... OK
   kernel loaded at 0x01080000, end = 0x02958a00
   Loading Device Tree to 000000001fff2000, end 000000001ffff01f ... OK
Starting kernel ...

I stripped the noise out to show the essentials. It looks good to that point, and there's nothing more recorded except

bl31 reboot reason: 0xd
bl31 reboot reason: 0x0
system cmd  1

It's rather nice to see one of these boxes "in the wild" .. I only have a couple of pre-release samples shared by an O2.cz product manager we met during the Embedded Linux Conference in Prague back in 2017

Can you share the UART/boot output from Armbian? .. I'll see if I can spot any differences.

S905-H is an S905 chip with DTS license, and rev C is the same silicon revision as WeTek Play2 (and many other boxes). If you have been using older LE/CE images on the box you MUST force recovery boot so the device reads the u-boot boot scripts from the SD card, else u-boot is looking for the wrong filenames. It should boot using meson-gxbb-p200.dtb.

LE is almost certainly not "freezing at the splash screen" .. but something prevents it from being able to correctly setup an output display device and thus the boot splash is never overwritten by the Kodi desktop appearing. I have a hunch this is related to EDID data on the HDMI connection (or lack thereof) but a debug log from the RPi will normally allow us to see if that's the issue.

I'd guess the BIOS is preconfigured for Windows and you'll need to disable EFI secure boot or allow legacy boot modes.

I'd guess the Windows drivers understand how to route audio signals to the DVI interface, and the Linux display drivers do not have the same capabilities; which is somewhat understandable as DVI hardware is not normally carrying audio signals.

Please provide the debug log previously asked for. Also run "amixer contents | paste" and share the URL generated so we can see the audio mixer control options and settings.

Quote from Frimelbear

is there a way to work with the toolkit and scriptset which creates Libreelec to create my own version?

You'd have to add python modules and whatever scripts are required. It's possible, but there are no instructions, although the buildsystem contains a large amount of prior art.

Quote from ararTP

Also, I can't install the certificate from the chrome settings, when trying to choose the file, chrome crashes.

Chrome is probably trying to access an internally hardcoded path that either doesn't exist in LE, or perhaps expects rw access and the path is inside the ro filesystem. As we don't compile Chrome for LE that can't really be changed.

No idea why it doesn't use the system cert chain either .. just commenting on that ^

The Terramaster box doesn't support hardware RAID so I think you created a "Spanned Volume" over the two drives. This uses the Logical Disk Manager (LDM) capabilities which are not natively supported on Linux, although there is a tool called "ldmtool" which can be used to create device-mapper entries and mount volumes. However, LE does not bundle ldmtool into our images, we do not support package management, and we are intentionally missing all the software RAID and device-mapper bits (so we don't have to support it).

This community image from sky42 has the LVM bits you need LE 12.0 added lvm2, luks (dm-crypt, veracrypt), mdraid, ext4 encryption .. but not ldmtool AFAICT. You can try copying the ldmtool binary direct from an Ubuntu image; if you're lucky it's an independent binary that's not linked against a bunch of libraries. If you're not, it is, and it needs to be compiled properly for LE use. That image also has the bits needed to make a Linux compatible software RAID (JBOD) setup; though that will require you to move data off the disks to create a new JBOD array before copying data back.

Of course, even if you make something work, it's not supported by staff.