Not much chance of it being supported under the legacy kernel as AFAICT it was never supported and we've abandoned all work on the 3.14 codebase after LE 9.0 and diverted our attention to modern (5.10+) kernels which while promsing, are still a bit work in progress.
If you can point me to some more recent Linux 5.4-ish (or newer) device tree (overlay) snippets needed to make the shield work, I'd be happy to see if we can get it working on a newer kernel.
tavoc enable SSH and see if you can login to run "dmesg | paste" .. often when users describe "hung" systems it's simply that Kodi doesn't start and thus nothing overwrites the boot splash, but the OS is otherwise running and accessible in the background.
The IP address seems to be on the wrong subnet. My router is set up on 192.168.0.1 and the IP of the Pi is 192.168.0.2.
When I connect to the AP i get an address of 192.168.1.2 and the gateway is 192.168.1.1. So this is wrong for a start.
This is correct because the tether creates a NAT routed (not bridged) connection between the interfaces, so two different subnets will be used. There is no need to set iptables rules or enable forwarding as these are either handled within connman or already enabled in default config.
It would be useful to see "route | paste" before/after the tether is enabled, and "journalctl | paste" after a clean boot, enabling the tether, and connecting a client device. Just share the URLs generated.
Raspberry Pi Imager tool gets the image info direct from LE servers so it used an official release, but we have never embedded cache setting changes in the default images. See:
The default appliance.xml LibreELEC.tv/advancedsettings.xml at libreelec-9.2 · LibreELEC/LibreELEC.tv · GitHub
The extra config applied for RPi LibreELEC.tv/advancedsettings.xml at libreelec-9.2 · LibreELEC/LibreELEC.tv · GitHub
It's not impossible for add-ons to make "helpful" changes that mess up users installs.
tavoc using the box image or the emmc image? (i.e. are you using vendor or mainline u-boot). If you can find the serial cables and capture the boot log it might (or might not) be useful.
I think this happens after the installation of which I think is the most popular piracy addon (not sure if it is allowed to mention which one), which is working just fine too, but I am not really sure about it.
As long as you have pirate add-on crapware installed, your problem is not our problem.
I do most partitioning work on remote servers via CLI so it's maybe 2.5 years since I last used gparted and I couldn't give you steps without installing a distro to describe it from .. and I'm not interested in that level of spoon-feeding. Just make the SD card again and let the installer expand things on first-boot. I'd guess you can't have installed or done much before running out of space so it's not hard to start over.
I'd say there's huge progress in the drivers all over, but then I find the current GUI performance on RPI4 perfectly fine so I don't know what you see that I don't see etc. .. I'm normally a fairly astute tester (been doing it for a while etc.)
You can instal the Chrome add-on from our repo. Most of the time it works, but sometimes it doesn't .. due to the fun of supporting a constantly iterating moving target piece of software. One of these days Kodi might gain an in-GUI browser, but that's subject to the same issues and is a long-term and slow moving project.
Community created images might have changed something, but LE default images do not contain any embedded advancedsettings changes to cache settings, because if your network is functioning correctly there is no need to ever fiddle with these settings.
I'm sure much was added since, but for reference on FDTDIR [U-Boot] [PATCH] pxe: implement fdtdir extlinux.conf tag
Is s912 supported?
Yes. All devices from S905 thru to A311D should be able to boot subject to using a working device tree. GXM = S912.
I believe you need to boot the device with the box img(or any other linux img that you can boot via USB or uSD), then download the kvim1 img to the device and then dd the kvim1 img to the emmc, instead of using the crap AML tools, since the the img is a raw disk img.
90% correct. Boot from the box image (so you are running from SD card) then transfer the -khadas-vim.img.gz file to /storage. For the last bit you can use "emmctool w /storage/LibreELEC-AMLGX.arm-9.80.8-khadas-vim.img.gz" and the emmctool helper script will handle the uncompress, dd to emmc, then resize and rename partitions so they are ready for use and don't conflict with the partition names used on an SD card.
NB: As a general comment for users: emmctool works on specific devices that have a -suffix image available. It is not a direct replacement for the older "installtoemmc" scripts and I have no interest in supporting "internal" installs on box devices that we don't have propper boot firmware for. It's not hard to circumvent the restriction but if you do and mess up your box, your should expect no sympathy and no help with recovering the box.
Nope. Because:
a) It's RPi only and wouldn't be usable on other SoC platforms
b) It's dependent on the Broadcom OpenMAX libs which we no longer support in K19
c) It's dependent upon gstreamer and while that's not impossible to solve, Kodi uses ffmpeg so this adds lots of MB
d) It should be handled in Kodi, and Team Kodi will refuse to implement something that's not cross-platform (can't work from an Android device)
As much as I like the simplicity and conformity of the extlinux arrangement vs. older "bootscript" approaches I am slso super keen on things that drive simplicity in the installation user experience, it's something that has always been a hallmark of LE/OE etc. and shipping 3x images or even 1x image instead of the current 6-8 rather weirdly named images could be a solid improvement.
I don't have any iMX6 hardware so I won't be able to test anything, but (speaking for myself) I'd like to see the PR.
Config.txt - LibreELEC.wiki <= really tough 5 second search to find it
RPi4 2GB model and up are fine for LE(10) .. in our testing the 1GB model is fine for 1080p media but has issues with 4K.
SD cards 4GB sized and up, but more than 16GB is probably a waste of money as big cards are sill prices so you're better off with a small(er) boot card and media on a USB drive. The smallest cheap cards I can find in the shops these days are 16GB class 10 cards.
There have been significant changes in the last week or so to catch up on several years of missed updates throughout the build-system, so likely we broke something the driver depends upon. It's been noted..
