mglae I've seen that one. It's mostly discussing problems where the adapter can't be used correctly whereas in our case it simply doesn't probe and load the driver (so not getting that far). The cbc_mbim stuff looks related to a USB-C dock.
rkershenbaum Are these ASIX adapters a simple Ethernet adapter or are they the Ethernet portion of a USB-C dock?
If media has been scraped into the database the watched status for an episode in the Movies database view should be updated on completion of the episode. If you enable debug logging you should see the DB query being made?
The "Trakt" add-on will push status to the Trakt website. The original purpose is to sync status between multiple hosts, but it might do the same with a single one too.
Kodi audio settings depend on the EDID data read from HDMI only during Kodi startup; hence the restart after the AVR is turned on results on 5.1 being detected. Unless someone implements HDMI hotplug support in Kodi so audio properties are updated when the HDMI sink changes, the workaround that you've done is the right solution.
Simple. Install 11.0.6 and disable auto-update, then perform a manual 'update' to 11.0.4.
You'll probably find that the addon uses inputstream.adaptive and the stream is 'adapting' and serving the optimum quality stream for current conditions. Note that 'optimum' doesn't only mean what's best for you, it also covers what's best for the upstream CDN infrastructure and under conditions where resources are constrained and actively managed you might be served 720p streams and not the normal/expected 1080p. Or the add-on needs reworking to accomodate some upstream change.
The USB-SD Creator app is unsigned, downloads unreadable compressed files from the internet, then writes data to the boot sector of a removable media device. Some forms of malware does similar things but ShitDefender isn't capable of spotting the difference.
To be fair, most AV apps are equally rubbish so ShitDefender isn't anything special here.
RPi4 can run Android and RPi4 can support the RPi TV HAT so something could be possible; but exactly what and how is way beyond the Linux + Kodi scope of the LE forums so I'd suggest you take the questions to the Pi forum.
Update the RPi5 to https://chewitt.libreelec.tv/testing/LibreE…h64-11.80.0.tar with the ASIX adapter connected and share the log URL from "journalctl | paste" please. I've made the drivers built-in to the kernel (=y) instead of using loadable modules (=m). That's not necessarily the right fix, but takes udev (which I think is the issue) out of the equation temporarily.
Dies ist ein englischsprachiges Forum
It's not a Kodi debug log so it's missing info on codecs and format, and by snipping out the bits you thought were relevant you've removed all the useful environment info that we'd like to see.
I'd suggest testing an LE12 nightly as LE9.2 is no longer maintained. Even if we confirm a problem, it's not going to be fixed.
No idea what the issue is, but you already found the solution (out first move would be to try a curretn LE12 nightly)
Commit device-tree changes for the different audio setup to an upstream kernel git source (Linux 6.6 for RK boards) then use "git format-patch" to create a diff patch that can be imported to "projects/Rockchip/patches/linux" in the buildsystem. When you build the patch is applied and the resulting dtb file has the changes built in, so no need to mess around with true overlays.
This wiki article describes how to self-build: https://wiki.libreelec.tv/development/build-basics
This describes workflow to enable a different kernel module: https://wiki.libreelec.tv/development/git-tutorial
LE12 is stable and firmly on the "sooner than later" horizon.
nVidia drivers now support MESA/GBM which can do HDR, but only through Wayland; which official LE doesn't use, and even if it's made to (with a self-built image) Wayland doesn't support dynamic refresh rate switching so the desktop refresh rate is fixed, e.g. 60Hz so you may find media playback has glitches and such as 23.976Hz or 25Hz content is adapted to that rate. Or you can use Xorg, but that doesn't support HDR at all. Oh, and Kodi only supports VDPAU not NVDEC.
I haven't used x86_64 hardware for a decade so I'm not going to recommend alternate GPUs (in part because vendors breed new stuff faster than I can keep up with it) but the general advice is: Intel = #1 choice, AMD = #2 choice, nVidia .. distant #3 choice.
Please retest with a current LE12 nightly. Thanks.
Add "video=HDMI-A-1:1920x1080M@50" and "ssh" to kernel boot params in cmdline.txt and it will force initial HDMI output to that resolution/refresh and force the SSH daemon to start so you can access the device to investigate.
update 1st to a sky42 release with a device that official LE knows
The "error" message on-screen is telilng you exactly what to do: create /storage/.update/.nocompat and put the update file there again and reboot to update.
