Posts by chewitt

AFAICT the only difference between AM6 and AM6+ is the plus using a DV licensed SoC chip (S922X-J) which is irrelevant for upstream kernel using devices. If it makes you feel better, rename "meson-g12b-ugoos-am6.dtb" to "meson-g12b-ugoos-am6-plus.dtb" and pretend that you have a special dtb for your board.

Quote from sh33p0mat

What I am after is a few lines of code that will make the add-on wait for the VPN tunnel to be up.

You cannot delay the add-on inside Kodi, but you can use a systemd service to schedule the VPN to start after the network is up and before Kodi, so the tunnel is established before Kodi autostarts the PM4K addon.

Have a look at /storage/.config/system.d/wireguard.service.sample and tweak that to suit whatever VPN technology you're using, e.g. if using OpenVPN not WireGuard, substitue an openvpn command instead of the connmanctl connect command. NB: If using OpenVPN you should really investigate using WireGuard instead as it'll significantly increase tunnel throughput on the same point-to-point connection.

The RPi5 works fine when directly connected to the TV, but once you add the AVR in the chain things don't work. That firmly points fingers at the AVR, but the usual methods of negating that or forcing output also appear to disagree with the AVR.

Please delete /storage/.config/firmware/edid/edid-HDMI-A-1.bin and then run "getedid create" again with the AVR inline between RPi5 and TV. It won't solve anything but I'd like you to upload/share the .bin file that's created here so we can have one of the RPi developers have a look at it - they collect problem files for testing.

popcornmix any ideas?

The non-trivial suggestion is to self-build an image that uses wpa_supplicant instead of iwd to see if that's the issue. The switch to iwd has overall been successful, but over time there's been a few users whose setups are tripping over edge cases and/or borderline reception and iwd doesn't seem to perform as well in those situations as older wpa_supplicant. We aren't going to be moving back to wpa but we've intentionally left support in the build system for a while to support people doing some a/b testing.

Use "pastekodi" and then we see the corresponding system log at the same time.

Remove the edid override with "getedid delete" and add "video=HDMI-A-1:1920x1080M@60" to boot params in cmdline.txt; this forces the HDMI-A-1 output to 1080p@60 which sometimes helps if the kernel can't quite decide on what to use.

You need to use an LE12 nightly which contains some updates specicially for RPi5 2GB which was realeased annoyingly shortly after LE 12.0.1 was made available. Update and it should work fine.

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.