Try the latest nightly (not stable) as some fixes for AMD GPUs were merged a couple of days ago.
If you add "textmode" to kernel boot params in syslinux.cfg the box will boot to a local text console (not Kodi) allowing you to poke around with a USB keyboard attached to investigate the WiFi problem. To diagnose anything we'll need to know what the WiFi chipset is, and see the system boot log (dmesg).
Layer 8 networking issues are the hardest to solve 
There's only one upstream developer working on Meson8 support (Martin B) and he has a busy day job so output comes and goes depending on when he has some free time (and enthusiasm). I rebased the pre-pre-Alpha AMLMX image on LE master and Martin's latest kernel branch one month ago and built this image:
https://chewitt.libreelec.tv/testing/LibreELEC-AMLMX.arm-10.88.0-box.img.gz
It's been boot tested by a couple of people but might need some manual finessing of the u-boot environment to get it booting - I one have one Meson8 box (and one board) and vendor u-boot from 2013 is an archaeology experience, so the scripts used to hook and boot into LE aren't finalised.
You are welcome to report bugs (there will be some) but this is completely unsupported 
Where is this Key-Only Auth setting you speak of??
In the LE settings add-on, next to the SSH enable on/off .. and users occasionally get enthusiastic and flick everything on, which means they enabled key-only authentication (after which, passwords are unsurprisingly no longer accepted).
dtb_name=/dtb/meson-gxl-s905d-sml5442tw.dtb
bootargs=boot=LABEL=LIBREELEC disk=LABEL=STORAGE quiet systemd.debug_shell=ttyAML0 console=ttyAML0,115200n8 console=tty0^ Modify the bootargs line in uEnv.ini to look like ^ this with everything on one line (beware, the forum wraps lines). Working?
Kodi only detects output config at startup so if you connect to the TV after boot it didn't receive necessary info. You can run "getedid create" to cache/force the EDID data from the HDMI connection, then the box will never see HDMI state changes that might be upsetting things.
There's not much we can do locally if suspend/wake doesn't work; it's all about the upstream kernel and what that inherently supports on your device. The challenge with mac mini's has always been that there's no BIOS that power states can be tweaked from, and no upstream kernel developers are using decade-old Apple hardware to validate Linux support so regressions can creep in over time (or things never worked in the first place). Your best bet is generall Googling .. if there's a patch we can add or a missing kernel module to enable; we can probably do that, but nobody on the team has old mac kit for testing so we're shooting blind on the problem. You can also report the issue to upstream kernel maintainers and see what they suggest. If you do, feel free to cc me (chewitt@ the LE domain). The power-management and ACPI mailing lists are probably the ones to target for Qs:
You need to replace /path/to/share with the path to your media share or maybe even just / (the root of the filesystem) and then it will crawl the entire box. The find command will run recurrsively so it's the easier one to use.
I'm happily connecting from Win11 (using the native support not PuTTY) and macOS to a range of LE devices using SSH, and if it didn't work for everyone there'd be a wave of forum posts complaining about it. So whatever the issue is, I'm confident it's local to your environment.
Make sure you didn't enable key-only auth. It doesn't stop SSH prompting for passwords. It does stop passwords from being accepted.
In the Rock Pi 4 A/B+ (the plus is important) there is a change on the boad that requires different u-boot. I'm not sure if the C follows the same change. There will be a new image for Rock Pi A/B+ added to the next beta so perhaps try that when it ships (soon).
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 ..
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).
