Posts by chewitt

I have a hunch the AMLGX image is missing the firmware for the card. Please update to this (LE12) image and test again:

https://chewitt.libreelec.tv/testing/LibreELEC-AMLGX.aarch64-11.80.0.tar

Feb 16 18:11:03.067888 LibreELEC kernel: r8188eu: module is from the staging directory, the quality is unknown, you have been warned.
Feb 16 18:11:03.212474 LibreELEC connmand[513]: wlan0 {create} index 3 type 1 <ETHER>
Feb 16 18:11:03.212608 LibreELEC connmand[513]: wlan0 {update} flags 4098 <DOWN>
Feb 16 18:11:03.212657 LibreELEC connmand[513]: wlan0 {newlink} index 3 address 14:EB:B6:A9:5E:BF mtu 1500
Feb 16 18:11:03.212695 LibreELEC connmand[513]: wlan0 {newlink} index 3 operstate 2 <DOWN>
Feb 16 18:11:03.214879 LibreELEC connmand[513]: Adding interface wlan0 [ wifi ]
Feb 16 18:11:03.223865 LibreELEC kernel: usbcore: registered new interface driver r8188eu

It looks working from a driver perspective but the interface is in a <down> state. What happens if you do "ifconfig wlan0 up" ?

Quote from sergiodbx

Dune Hd Magic 4K on Amlogic S905X3

It is possible, but with limitations (read the release notes on the main website). Install instructions for AMLGX image are in the wiki.

The OS and Kodi itself downgrade fine, but add-ons do not auto-revert to earlier versions and this may/will cause issues, so I would stop Kodi, copy the contents of /storage/.kodi to /storage/.kodi-backup then update. Then if you later choose to go back, stop Kodi, delete /storage/.kodi, rename the backup folder to /storage/.kodi and restart .. and you're back to where you started. If you choose to stick with LE12 (which is nearing an official beta..) just delete the backup folder. I've been running nightlies (albeit my own builds not official ones) since last summer with no problems.

HEVC is software decoded on G12A/B and SM1 and there's no 10-bit decoding path. If you play 1080p 8-bit media it should work.

H264 should play, but the 'VDEC' driver was written for GXBB/GXL/GXM boards and is technically the wrong driver so you might see artefacts at playback start, but things should sort themselves out normally (depends on what the problem is though). G12A should be using the (confusingly named) 'HEVC' driver which doesn't currently exist.

There's more info on current status in release notes on the main website.

Update to https://chewitt.libreelec.tv/testing/LibreE…h64-11.80.0.tar and enable debug logging.. repeat the test and if the issue persists, run "pastekodi" and share the log URL generated.

I assume you've read the comments about status of things on G12A/B hardware in the LE 11.x release notes?

PROJECT=Generic DEVICE=wayland ARCH=x86_64 make release

That ^ will result in a Wayland image. In theory the same can be done on ARM targets if device "options" files are adjusted.

The Kodi repo is the most appropriate place for discussion and you already found that ticket.

Please update to a current LE12 nightly to see if newer kernel, drivers, firmware, etc. helps?

LE will use DHCP by default so the IP address the RPi4 receives from the router will change over time. The easiest way to solve that is creating a static address reservation in the router. You're still using DHCP but the IP that's dynamically received will remain the same so any links you make will remain the same.

The UK is listed as "Britain (UK)" not United Kingdom. The timezone country list is populated from OS timezone content which is pulled from some international standard so it's not a Kodi internal list that can be changed or patched.

See https://kodi.wiki/view/Movie_artwork

The Kodi wiki probably has the answer to any other questions you have (on Kodi).

See what happens with "ifconfig eth1 up" .. it might take a while to get an address via DHCP

Please update to the latest LE12 nightly and retest: https://test.libreelec.tv

The latest LE12 nightly (since https://github.com/LibreELEC/LibreELEC.tv/pull/8616) would be interesting to test as it contains some changes to correct some EDID issues seen. No ideas if this is one of them, but would be good to rule in or out.

It sounds like the repo wasn't available (or refreshed) before; now that's fixed there is content to get-more from, so it shows.

I tweaked the thread title.

areq1987 You need to set the full name of the filename.dtb to use in extlinux/extlinux.conf. If you rename files to dtb.img boot does not work. This is probably why you end up in the Android recovery app.