Posts by chewitt

The GUI shows Hardware/Revision/Serial here. It's a custom image I make for myself and not the official beta, but I'm not patching anything that would affect this. The info in /proc/cpuinfo is not the same on 64-bit kernels as 32-bit, but that's a general Linux thing.

I was thinking you were wanting to add tuners to the install. If you already did that and the tuners work fine under LE10 (not sure what kernel but it's upstream) I would expect them to continue working fine under LE11.

If you boot to Kodi (and let it hang for a bit) then boot again to textmode and "cat /storage/.kodi/temp/kodi.old.log | paste" and share the URL that's generated, this will pastebin the previous Kodi log and might give some hint on why Kodi is failing to start. If the log doesn't exist there might be a kodi.log file in the same dir. I don't see anything in the screenshots so I doubt the video will be useful.

It's most odd. User numbers are continuing to climb since the LE11b1 release so I know the box image is good. And there are other users with the same device ..

Quote from sugatam

Is the U9-H running LE11 capable of 1080p VC1 playback? I have a bunch of these old blu-rays that haven't been reissued in AVC, and a Pi2/3 with the VC1 hw codec enabled has been my only option so far to play them without stutter.

There's no hardware decoder for VC1 (was on the to-do list but never reached..) but S912 has a reasonably decent CPU so it might be enough to software decode. I don't have any VC1 test media so you'll have to experiment and let us know.

It's quite common to find weights in boxes. Without them they're so light an HDMI or Ethernet cable will twist the box all over the place.

The last Amlogic legacy kernel image we released was LE 9.0.2. Your box is currently running an unofficial fork of our OS that was created by Eminent so it would be their responsibility to provide updates. Presumably they did at some point since the version number is higher.

There is no official LE 9.2.x image (with Kodi v18) but dtech released an unofficial image that might work on the device (not sure if the image supports S905X though). There are no official or unofficial LE10 images as we discontinued Amlogic support for that release. The Eminent website currently links to the CoreELEC fork who released a Kodi v19 image (although that release is also discontinued now).

The latest LE11 beta (with Kodi v20) resumes basic Amlogic support and should run on the device; but please read the LE11b1 release notes on the website (and the link to the wiki) before you decide to update as the release, while usable, is not as feature complete as the legacy images and won't suit everyone's media needs. If you choose to use the AMLGX image, the "meson-gxl-s905x-p212.dtb" file should work, although a custom device-tree is probably needed to get WiFi/BT working as IIRC the box has a Realtek module (not Broadcom). It's not hard to make the device-tree if you can share "pastekodi" boot logs once the image is installed.

No need. I'll keep the RTL driver in my private branch for as long as it compiles (and drop it when it breaks). I won't be sending it upstream to main repo.

USB tuners should work, but there are never guarantees since DVB remains one of the more difficult and challenging parts of the kernel to work with. If possible run tuners on something separate so you can leave TVH on whatever combination of OS/drivers/firmware works best for you, while the playback device is on something that can just run the latest LE release.

The LE11 beta image should run better on WP2 than an older LE10 image. There's also the option to install/run from eMMC these days.

https://flirc.tv/products/flirc-usb-receiver <= works on anything with USB ports and any IR remote

https://rpilocator.com/?cat=PI4 <= can help with finding stocks, but supply remains a problem.

Small PC boxes generally work well with LE too, but look for something fanless (not sure what the box you linked is like).

Ye olde 'wl' was added for AppleTV support aeons ago and was noticed again recently. It will survive LE11 (bit late to drop it) but I suspect will be gone and replaced by b43 (which doesn't cover exactly the same cards) for LE12.

Quote from fr0sty

From version 10.0.2 and up, also nightlies. TV detects HDR but displaying striped, green/purple toned image.

I must have been Zzz .. the issue here (in all releases that have ever claimed to support HDR) is that you're playing files with DolbyVision HDR encoding which is not supported under Linux. You'll need to use Kodi on a DV licensed Android box to play them.

LE supports the static (and open) HDR and HDR10 formats, not the dynamic (and proprietary) HDR10+ and DV formats.

The core OS will downgrade without problems, but Kodi does not support downgrades so you'll end up with a bunch of add-ons at a higher and incompatible version and that can often have crashy consequences. Things like DB content will be fine as Kodi simply uses the older DB files that still on disk (or tables in MariaDB) and ignores the newer ones that correspond to new Kodi version.

Crossgrades between release and nightly versions are generally okay as long as Kodi API versions haven't changed. At this stage of the cycle things are stable on that front so it won't be an issue. If we're still in the pre-Alpha stages there are API bumps and that will cause issues from time to time.

Quote

bootargs=boot=UUID=2604-0049 disk=UUID=f660cd3d-904b-452a-ae8e-3584aab3e106 quiet ssh systemd.debug_shell=ttyAML0 console=ttyAML0,115200n8 console=tty0

Create a clean SD card from the same image. Set the DTB name in uEnv.ini and add "ssh" in the boot params ^ (beware the forum is wrapping lines - it should all be one line). This forces SSH to start, even if the GUI doesn't come up etc.

Then login over SSH and run "pastekodi" and share the URL so I can see the boot log (and what's going on with the mount/unmount).

cd /storage/.update
wget https://chewitt.libreelec.tv/testing/LibreELEC-AMLGX.arm-10.95.1.tar
reboot

jim_p run that ^ and then run "pastekodi" from SSH and share the URL

If the issue was firmware I would expect to see errors when the hardware probes and fails to find/load the right firmware. However I don't see any mention of anything related to WiFi/BT at all which suggests the hardware isn't probed/detected at all. I'd go (re)check the card is seated correctly - is it detected/shown anywhere in the BIOS (if the BIOS is sophisticated, often they are dumb). Or perhaps the card is bad? / can you test it in anything else?

Wacko37 to test if the issue is caused by Kodi starting before audio drivers have probed/loaded in the kernel you can simply stop/restart Kodi after boot with "systemctl restart kodi" over SSH. There is no 'exit' option in Kodi (in LE) as there is no Desktop to exit to.

Settting "meson-gxl-s905x-p212.dtb" in uEnv.ini should work with the box (except for WiFi/BT perhaps) although the ability to boot does still require the vendor bootloader to support looking for boot.scr or s905_autoscript on startup. Most do, but not unless you invoke the recovery boot process (holding the reset button during power-on and releasing at the right time, which might take some attempts to get right). If the recovery boot flow is not triggered the box will continue booting into Android or existing Linux OS. Sadly a) it's not as simple as just inserting the SD card, and b) the only real way to understand what is/isn't happening if it's not working is to attach a serial console. That generally needs the user to open the box and solder header pins to the board (as box manufacturers omit them to save pennies) before connecting the USB->UART device (which 99/100 users don't have). When it works it's great. When it doesn't it can be a hoop-jumping exercise

find /path/to/share -type d -name '.@__thumb' | while read ITEM; do rm -rf "${ITEM}"; done

From a quick read it's the DLNA photo sharing features on the QNAP that creates them, so this needs to be disabled for the content/media folders you share to Kodi. Then you can run ^ that (on the QNAP) to exorcise the existing thumbs. Then you can either clean the current Kodi DB or start over and scrape again.