Chances to boot are better with a legacy image.
There are big differences in the kernels and userspace of Generic and Generic-Legacy but in respects to initial boot code they're both exactly the same. If the kernel cannot see the target device to install-to; you'll hit the same issue in both images.
RPi4 is excelently supported, but DVB is an icky topic regardless of hardware. The general recommendation is to separate tuners from the playback device so you can run whatever OS and hacked version of drivers and firmware that works reliably .. with playback on something simple that you can OS bump whenever LE puts out a new release. The moment you put both functions on the same device you can have a reliable player or DVB that works; they are generally mutually exclusive and you have to chose one.
That means you could revert to a legacy image, e.g. CE or dtech's LE 9.2.8 one for the TVH side. RPi4 is a nice playback device if you can get your hands on one.
You have to use LEs generic-legacy variant, because you have an Nvidia graphics card.
That's the next problem (once installed). It doesn't sound like the user got that far yet.
There is no hardware deinterlace in any codec, forcing software deinterlace which is limited (else you hit the CPU limits). I've disabled support for MPEG2/MPEG4 hardware decoding in the latest images (as the hardware decoder is broken) which is why those 'work' now. However, ff those codecs and interlacing are important for your media; you aren't in the narrow band of users who should be using the AMLGX image. I have low expectations on progress because it's basically me solo supporting Amlogic these days, and I don't write driver code.
touch /storage/.cache/services/sshd.conf
systemctl start sshd
connmanctl
agent on
services
connect <service_string>
(enter pw when prompted)Running ^ that sequence of commands form the textmode console should enable SSH, start it, then connect you to a WiFi network instead of Ethernet, although from logs it appears SSH is running (as it was forced) and the Ethernet NIC is up/active and assigned 192.2168.1.76. Make sure that you're using a current version of PuTTY as support for ciphers does change over time.
Then, to have more info on why Kodi isn't working, create /storage/.kodi/userdata/advancedsettings.xml with the following content (to put Kodi into debug mode) then reboot and run "pastekodi" and share the URL:
<?xml version="1.0" encoding="utf-8" ?>
<advancedsettings version="1.0">
<!-- enable debug logging -->
<loglevel hide="false">1</loglevel>
</advancedsettings>Then maybe we get some insights on the problem..
NB: You can also experiment with other device-tree files. How about the 201 dtb? .. there are some other GXBB box devices too.
If you add "textmode" to boot params in uEnv.ini the box boots to a text console instead of Kodi and you can attach/use a USB keyboard to run commands. To retrieve the logs, make the SD card read-write with "mount -o remount,fw /flash" and then dump the boot log content to /flash with "journalctl > /flash/journal.log" .. then connect the SD back to something you can retrieve and pastebin the log file from.
AFAIK all the atheros USB chips are enabled in the kernel but we are probably missing the firmware, which should be obvious if you look in dmesg for the chip being probed. This might get it working: "mkdir -p /storage/.config/firmware && cd /storage/.config/firmware && wget https://git.kernel.org/pub/scm/linux/…plain/ar9271.fw && reboot"
There is no driver code in-common between the Legacy image and AMLGX image so there is no value in making comparisons. It's like pointing at a Nissan car and a Ford car and saying .. "they're different" .. because they are.
I'll add the investigation to my list, but these days Amlogic support is largely a one-man team (and I don't write driver code) so these things take time.
Nice, but I have no plan to install Arch Linux to test a single package. If you created it, you need to test it 
To release official LE binaries we need to build Qt6 "static" to avoid depending on sizeable Qt packages. Since the codebase was bumped to Qt6 I've not stumbled upon a working Qt6 static build recipe for Linux.
I've enabled/added some kernel drivers which may be required for different Ethernet PHYs to this image:
https://chewitt.libreelec.tv/testing/LibreELEC-AMLGX.arm-10.95.1-box.img.gz
Or update using:
https://chewitt.libreelec.tv/testing/LibreE…arm-10.95.1.tar once installed with the official image.
Does that get Ethernet working? (WiFi/BT is something seperate, we need logs for).
Allwinner H618 (and related H616) are not currently supported and there are no images. H6 is supported.
Perhaps rename /storage/.kodi to /storage/.kodi-old and reboot to see if moving all old config out of the way helps. You can drop the current http://sources.xml/passwords.xml back into userdata and rescrape to see what happens. Plan B .. share debug logs so we can see what's happening.
p.s. thread title changed because you have done clean install from SD card and are not technically updating from CE; which is something I have no interest in trying to support with users as too much has changed and too much stuff breaks.
The "reboot update" triggers recovery boot mode causing the SoC to search for boot scripts in the first partition on the SD card. The LE boot scripts are then found, which sets params in the vendor u-boot environment to use LE boot files and if you reach Kodi then everything has worked. To revert to CE you will need to trigger recovery boot mode again. In most cases that's done with the toothpick method, which (with SD card removed) will find their boot scripts and set boot params to use CE boot files. On most boxes (but it depends on what customisation was done in vendor u-boot) both OS are tweaking the same boot params to suit themselves which prevents a simple swap between OS(es) by removing the SD card.
The ethmactool-config service creates a unique MAC address based on the CPU serial to avoid issues where vendor code sets the same MAC for all boxes (and users have more than one of the same box causing conflicts) or where the MAC was not set in the factory and changes on each boot. As long as you have a static MAC address "systemctl mask ethmactool-config" will disable the service on future boots and stop the message from showing up.
Not sure about the blue tint, but as long as it doesn't happen on the TV it's not something I'll be interested in chasing. Vendor u-boot does a few weird things.
NB: If the S805 image is AMLMX .. it is pre-Alpha state and is not even remotely supported.
root preexec = /bin/bash -c "mkdir -p /storage/test"^ Just a guess. See if that ^ works?
2023-02-05 01:29:18.397 T:1533 ERROR <general>: failed to initialize egl
2023-02-05 01:29:18.397 T:1533 WARNING <general>: Visual 0x21 of the window is not suitable, looking for another one...
2023-02-05 01:29:18.403 T:1533 ERROR <general>: GLX Error: vInfo is NULL!No idea what the cause of the problem is, but basically it fails to find an OpenGL surface to render the GUI onto and fails. As LE10 will receive no further fixes/changes now I'd start with a bump to LE11 beta 1 and see if that resolves things?