Posts by chewitt

Banned add-ons are present, no support.

Official:Forum rules/Banned add-ons - Official Kodi Wiki

Use full path to the binary, e.g. /usr/bin/connmanctl not just connmanctl as the bash script doesn't have knowledge of $PATH from the bash interpreter, unlike the console which does.

The gold standard for support is currently still an RPi5 board; not the fanciest specification but definitely the most reliable. Rockchip is making strong progress though and is now ahead on media codec support. Some audio issues need to be resolved for RK3588 to steal the crown from RPi5, and support for the trickle-down derivatives and slightly older RK hardware that share capabilities with the RK3588 chipset also need some attention.

LE10+ uses a completly different (ground up rewrite) display pipeline to LE9.2, so yes there is a HUGE software difference. The main way this manifests for users is that almost all config.txt tweaks for forcing video and audio output used in the older display pipeline are no longer supported using config.txt, and are now achieved using standard Linux DRM methods/properties.

It would be helpful if you described how everything is physically cabled/connected, and please share the "pastekodi" URL taken from the LE9.2 and a clean-install LE12.2 (or LE13 nightly) image so we can see kodi/kernel and various bits of config from the systems; the kodi.log on its own isn't giving us the full picture. If the RPi4 is connected to the projector using the HDMI socket nearest the power connector, please also run edid-decode /sys/devices/platform/axi/axi:gpu/drm/card1/card1-HDMI-A-1/edid | paste and share that URL too.

Make sure you set/configure the wireless regulatory domain for your country in LE settings, it can make a large difference to the radio spectrum that's usable.

This is a long running known issue without resolution impacting a small number of users. The issue correlates with poor WiFi signal and is seen with all common manufacturers of WiFi chipsets so the root cause likely resides in common ConnMan or IWD code not device drivers. The only known workaround is reinstating wpa_supplicant support (we removed the wpa_supplicant package from our buildsystem in 2023) then self-building an image using wpa_supplicant instead of iwd.

This patch looks promising https://patchwork.kernel.org/project/connma…[email protected]/ but the author submitted no detail on the problem and we've also seen reports from people self-building images saying it did not resolve their issue, so there's no guarantee that it's the same issue or the correct fix.

This LE13 test image has the patch applied: https://chewitt.libreelec.tv/testing/LibreE…1-tinker.img.gz

Go test and see if it changes anything?

There are no known HDMI audio problems in recent images (and we have a large RPi4/RPi5 userbase) but HDMI audio depends on the EDID data on the HDMI connection. No EDID or bad EDID or connecting to a monitor with no speakers or using HDMI adapters or bad HDMI cables or bad config.txt/cmdline.txt are the cause of most audio problems.

• Ensure the board is running updated RPi firmware (done via LE settings)
• Ensure the HDMI cable is a proper micro-HDMI to HDMI one (adapters frequently cause issues)
• Ensure the cable is connected to HDMI-A-1 (socket nearest the power connector)
• Connect the RPi directly to the TV (no AVR in the chain) then remove the SD card and power on. The board will boot to a status screen and you should see 'EDID = okay' against the active HDMI connection
• Create a new/clean SD card using LE12.2 or a current LE13 nightly to ensure no old/existing config causes issues

If still seeing a problem, put Kodi into debug mode, reboot to get a clean and complete debug log, then run "pastekodi" and share the log URL so we can see the output.

Most USB dongle WiFi devices normally trump on-board WiFi as the antenna is larger (albeit still small) and separated from other chips and RPi5 may or may-not be an improvement on earlier models, it's hard to tell. If you are in a poor/difficult signal area USB dongles also allow you to choose a device that can be hooked up to a proper external antenna. As a rule we avoid making wireless hardware recommendations due to the ephemeral nature of success; what works amazing for one person often sucks for someone else. This page from a linux-wireless maintainer is worth reading: https://github.com/morrownr/USB-WiFi/

Revert of the PR will restore the previous driver to the buildsystem, but you'll probably need to update the driver source version or add some source patches to compile the driver against newer kernels that we are using now; Realtek downstream drivers often break when we bump the kernel major version (hence we dumped them in-favour of in-kernel ones).

The RK3588, RK3567, RK356X images in my test share have been updated to use Linux 6.19.0 and HDR is now working on RK3588 and hopefully RK3576 too (limited tested on RK3588, no testing on RK3576 yet). I'm finding the output a little dark compared to the family daily-driver RPi5 board, but different hardware will always give different results, and most users won't have multiple devices wired up to the TV for comparisons; meaning you can tweak TV settings/profiles to get things as you like.

LE was created using https://www.linuxfromscratch.org principles. It is not a derivative of any other distro. It should boot and run on any type of x86_64 hardware but LE is not a general purpose OS and it intentionally targets HTPC/SBC hardware and will be lacking drivers useful on non-target devices like tablets and laptops. In some cases you can enable drivers in the kernel when building an image. In others not, it depends on the specific hardware you're trying to use and what drivers exist for that device. As a rule we avoid trying to curate lists of "what works best" because the lists are never maintained for long and are outdated; and you won't find lists of tablets in our forum because people rarely use them and we don't have experience with them. There's not much need for touch-screens among our userbase so support for them is a bit of a grey area and our experience is limited/non-existent.

Our 'Generic' image runs Kodi under GBM, while Generic-Legacy (not something that I'd guarantee is around for much longer) runs under Xorg. It can also run under Wayland which exists in our buildsystem to support the Lakka retro-gaming fork that leverages our codebase; but we don't release LE images that use Wayland (as no need to) and our buildsystem is missing lots of things you would need to create a desktop environment.

Kodi implements its own rendering engine so you'd need to learn their UI and skinning process to do something. Kodi plays media well, but it is not a kiosk systema and does not support ebooks, email, or much in the way of communications. It could of course do more, but that's down to you and your development skills. IMHO you'll get further faster using a conventional distro or perhaps Yocto/OpenEmbedded which has a much broader hardware audience and more packages in its ecosystem.

Please test a current LE13 nightly image without the EDID hardcoding. Same result?

There is no such thing as an audio-only HDMI connection, so the AVR is advertising video on HDMI-A-2, hence the 4K mode seen in the modetest output. The AVR on HDMI-A-2 passes through the EDID capabilities of the non-existent upstream device; ergo that connector has no HDR support. So if Kodi were using the output of HDMI-A-2 for decision making it would explain why HDR is not seen as possible, but the log shows it selected HDMI-A-1 for DRM output. At that point I have no clue

What, like this one? https://kodi.wiki/view/File_manager .. or the Web File Browser add-on in the LE repo?

Images in my test share are updated to Linux 6.19.y and with a change to the uImage.lzo kernel entry point that's currently needed to get the kernel booting on S4 boards; so I'm interested in reports of boot failures after updating. As part of that work I've added support for the Khadas VIM1S board, although this is not real-world usable at the moment (and thus won't be in official nightlies for a while) due to issues with the S4 DRM driver that result in a flickering screen when Kodi is running, and new alsa incantations being needed for audio routing/mixer settings. Khadas shipped a bunch of VIM1S (S905Y4) samples so there's common hardware among those needing (or wanting) to test the new stateless video codecs and dependencies (DRM, audio, etc.) Amlogic are working on.

In Kodi debug logs there is normally a section after debug <general>: CDRMAtomic::InitDrm - initialized atomic DRM and before the debug <general>: CWinSystemGbm::InitWindowSystem - initialized DRM line that displays info on the EDID data presented on the active HDMI connector Kodi is using. This data is missing from the log. However, in addition to colourspace data, the EDID data contains info on audio capabilities and in the audio section of the log names of the TV and AVR are visible so this appears to be read from the HDMI connctor okay. Most odd..

popcornmix there's been a couple of similar reports in LE12.2, any ideas?

ConnMan will show show a valid service as long as the config file is complete; doesn't mean the config is correct. The main item that you might need to figure out is the host IP of the server. ConnMan cannot currently resolve an FQDN to an IP so you need to replace any hostnames in the Mullvad config with an valid IP. Most VPN providers use hostnames because they are frequently changing the IP's that their nodes resolve to, and most hostnames resolve to multiple A records.

Extracting the dtb from an Android image is guaranteed to result in boot failure. Even if you rename dtb.img and configure uEnv.ini to use it correctly, the Android vendor kernel you pulled the dtb from has no code in-common with the mainline kernels that LE uses in the AMLGX image and kernel and dtb need to be version aligned.

If the box has an S905W chip the only device-tree files that might work are meson-gxl-s905w-p281.dtb or the similar Tanix TX3 mini device. It's a cost-engineered box with a CPU that runs/clocks slower than other GXL designs so p212 or similar may attempt to run the CPU faster than it can boot or reliably operate at. I would only use LE12.2 or perhaps an LE13 nightly image to attempt boot. LE9 images predate the existance of S905W (so don't support the chipset) and we no longer support those images.

If the device isn't booting to the LE splash screen or Kodi the only way for us to provide any support is to see the early boot log. This is obtained by connecting a USB serial UART cable to TX/RX/GND pins on the board; assuming they exist, and if not they need to be soldered in-place. The log will show what Amlogic u-boot attempts (or not). In the absence of the log we are blind to the issue and it's not worth the time/effort to guess at things.

NB: read https://wiki.libreelec.tv/hardware/amlogic to understand a little more about LE differences

Most providers simply generate all the keys needed for a client node to be configured to work with their server. This is technically less secure (as they generated and thus could know/store the private key of the remote device) but that doesn't seem to bother most users who only care about a connection that hides their presumably dodgy activity. I've never seen the Mullvad device generator tool but if they allow you to provide a public key and optional preshared key, which they store to authenticate your client node, this is more secure, but not really more complicated; the tool will still generate a conf with the content you require.