Posts by chewitt

Have you tried using Tubed? .. it's a little less featured than the YouTube add-on, but sometime simplicity is a benefit.

Please put Kodi in debug mode then update to https://chewitt.libreelec.tv/testing/LibreE…h64-11.80.0.tar and share the URL from "pastekodi" after playing something. I'm not seeing anything unexpected/wrong in the system log but let's see what more logging shows.

Have you read https://wiki.libreelec.tv/configuration/…ration-advanced ?

The BT device probably uses VID/PID identifiers that aren't recognised by the kernel driver. LE 9.0 is no longer maintained so there's not much we can do to add them.

Have you tried the upstream kernel AMLGX image on a spare SD card? - It's not as feature complete as the legacy kernel images but with simple media collections it's often quite usable. Have a read of the LE 11.0.4 release notes for more info.

dmladenov I was working on the same change but you beat me to the announcement. It's good to know it works

As per https://github.com/chewitt/linux/commits/amlogic-6.7.y I've added "meson-gxl-s905l-p261.dtb" to the "box" image in my testing share: https://chewitt.libreelec.tv/testing/ so please switch to that dtb then share the URL from "dmesg | paste" and we can what else is working or not. NB: WiFi will not work because there's no upstream support for the MT7668 chipset. You can also follow https://wiki.libreelec.tv/configuration/…ration-advanced to create a working keymap.

I've been using Tubed for a while but had to resurrect the main YouTube add-on last week to test something. Once I fixed OAUTH login issues with my personal keys the YouTube add-on was preferring VP9/AV1 media at 4K/59.94 which was a) too much for an RPi5, b) not how things were configured in the past. After some config review to limit things to 1080p again, all was good. That sounds rather similar to your experience. I'd hazard a guess that 10.x with Matrix uses an older version of the YouTube add-on and with the 11.x update to Nexus the add-on has bumped to current and revised defaults/options and changed something.

I'd start with investigating the deprecated option warning which is related to ciphers; if those aren't aligned it will probably explain the authentication failure. The other messages are warnings (not errors) but also point to the config being misaligned with newer versions of OpenVPN that we're using. You should probably direct Q's to the VPN provider as it's their config which needs changes not our distro image.

I did reach out to HK but got their standard-ish "oh this is no longer sold.." response which basically means they no longer care for support (outside of their legacy kernels) and as usual support is entirely up to the community.

According to past Googling on the topic, S905L is the same as S905X except for no VP9 support. I did create a device-tree for a "Venz V10" S905L box before but the user disappeared without providing feedback so I've dropped that from my kernels.

The only odd thing in dmesg (other than references to missing SYSTEM file) is there's no sign of the GPU driver (lima) loading, but how that might factor into anything is anyone's guess. I don't see anything particularly odd from the vendor logs. I'm not much of an expert on them though and they're so full of verbose messaging it's hard to see much.

If you can't get the box to boot with Legacy LE or CE images then there might be something hooey going on at a low level (u-boot) which then upsets or interferes with Linux. It's hard to comment further from the info available.

In short..

Kodi reads the EDID data to determine resolutions and audio capabilities once at startup and never checks again. One of these days that might change, but that's how the current implementation works. The forced EDID at kernel DRM level means everything on the Linux side (all the way up the code stack) is blissfully unaware that anything on the HDMI connection changes/changed.

I suggest you read LE 11.0.4 release notes first. If that doesn't deter you, read https://wiki.libreelec.tv/hardware/amlogic

"Is there a secret to allowing pasting to work in this forum?

Or perhaps the forum software is broken because I keep seeing ..."

^ seems to work here copy/pasting a screenshot and raw text (macOS 14.1.2 and latest Firefox with a ton of privacy extensions)

Cache fiddling can sometimes smooth out the drops/glitches in WiFi, and other times it can't, but if it can it's free. I've also used an old router in bridge mode to traverse longer distances than the weak-as-hell onboard WiFi that lots of boards (not only RPi flavoured ones) have these days. Even old routers usually have better antennae and more receiving power.

Both logs show that playback starts in 2.0 pass-through then TrueHD/DTS-MA are detected and AESinkALSA renegotiates to output with 7.1 output. Kodi appears to be doing the right thing here. What spec is the HDMI cable?

Please (re)test with an LE12 nightly image.

I'm running the bare board inside a closed space (cupboard fronted with speaker cloth) in a room with an ambient (AC controlled) temp around 24ºC. There's no case (so no fan) and it's out of sight and out of harms way .. until the flirc cases start shipping. It's never 40ºC cool but also never that hot, so temps and throttling haven't been an issue.

Copy a 'problem' test file to the local SD card. If it plays fine (which it probably will) the finger points at the nework being unable to sustain the required data rate. If you bump to an LE12 nightly it's possible to fiddle with cache settings in the GUI (in LE11 you can do the same though advancedsettings.xml) but cache fiddling is a double edged sword and causes as many problems as it solves. If you increase the cache size the RPi5 may be able to cope better with temp glitches in connectivity and data rates, but you'll also need to read more data over the flaky connection before playback starts. The read-factor may be the better tool to adjust, and reducing the cache or read-factor can sometimes also be the solution, not increasing. It's all about what works in YOUR network so it's all about testing and experimentation not reading forum posts on what worked for someone else.

If the file doesn't play well from SD card .. then it's something else, but my money's on the evil that is WiFi connectivity. I'm playing a wide assortment of very large filesize media from a wired NAS to a wired RPi5 with zero issues.

Explain "nothing is happening" in more detail.