Posts by chewitt

Quote from Deezle

Very sad to hear.

The GBM/V4L2 pipeline has probably been actively used on about 10% of the overall range of x86_64 hardware that users probably have. Some of that percentage will be low-risk, but we're expecting a fair number of quirks to surface. So you might be in a rush to use an "official" image instead an otherwise working fine "community" image, but LE10 already impacts 85% of our userbase (RPi) so Generic is in the queue and will have its day (along with the likely end of nVidia support) but some more elapsed time is a good thing. We're not in a rush.

No logs, no accurate description of before/after changes to SMB settings, and not enough technical detail to do anything beyond guess at the issue:

a) Your hardware might have NICs that need odd drivers to work

b) Your SMB server needs different settings, or Kodi client isn't configured correctly

I'd guess it's the later .. but .. it's just a guess

btw, LE *never* auto updates between Kodi major versions, so it was your decision to manually upgrade.

Switching between LE10 nightlies and LE10 beta images doesn't require reinstallation. Just 'update' as needed.

Quote from AndreyB

Use CoreELEC-Amlogic-ng.arm-9.2-nightly_20210327-Generic.img.gz

Ask in the CE forums.

Quote from Nekromantik

If we want to use official

Until we switch from X11 there are no official images with HDR support. The earliest we might do something is LE10.2, but more likely LE11/K20.

Quote from Raven

Why won't it make it to the LE10 builds?

because LE10 still uses ye olde Xorg for the Generic image and all these patches are aimed at the GBM/V4L2 pipeline we are not (yet) using. Until we make the switch, community created images are the well-proven approach to testing things.

No, for the simple technical reason there is zero upstream kernel support for the hardware. An RPi Zero will outclass it by a mile.

Quote from synrgii

Does post that I just found help?

Nope. The entire video rendering and hardware decoding pipeline has changed. All previous articles are null and void.

Kodi assumes that you will define "sources" and then "Set content" for the source to e.g. "Movies" and then scan (scrape) the source, i.e. when it finds a movie it will lookup the movie in TVDB.com and download metadata and fanart etc. to create a rich library view. This fails since you are offline.

To prevent this and still use Libraries you will need to change the scraper for each source to "Use local content only" and provide the metadata via .info or .xml files and locally stored images (in the same folder as the movie normally). The Kodi wiki has lots of info on files/formats and how to arrange the media in folders etc. to do this.

To prevent this and not use Libraries at all .. define sources and browse them via the "Videos" menu item which is a non-Library raw view of the files in the source. Kodi will create thumbnails from the local media, but there's no online lookups.

It sounds like you're missing the step to change the scraper - for each source you've defined.

Poor WiFi signals? - RPi4 is better than RPi3 for WiFi but with no antenna the connection is never brilliant. Also check the reegulatory domain setting as the default "world" config may not be fully compatible with the radio transmission requirements in your country.

Worst case you can install LE 9.2.6, update to LE 10b1, then use the hard reset option in the LE settings add-on to nuke all traces of Kodi v18. Sounds a bit complex but with a fast NUC it's probably under 5 mins effort.

I answered several questions that you asked. I didn't claim to solve the problem.

Please share the URL from "journalctl | paste" and "mount | paste" about 20-30 seconds after boot so we can see how the drives are being mounted and if the kerrnel logs any error messages. Ignore lrusak message - it was late when he replied and his eyeballs didn't make it past the /dev/loop0 device to where the real issue is

If you're able to boot one of the mainline u-boot-using LE or Armbian images from SD card, installing them to eMMC is as simple as dd'ing the .img file to the eMMC /dev/mmcblkX device the same as you'd write an SD card under Linux. GXL and newer boards look for the Amlogic signed boot header in the same places on both SD and eMMC so the images will (or should) boot from either.

If you want Android on eMMC you'll need to track down either a more recent version of the Amlogic burning tool (or an older era-appropriate one that matches the image age) and a "ROM" image from somewhere like Freaktab. The ROM image format uses .img file extension but this is an Amlogic proprietary format so you cannot simply dd it to the eMMC device.

Kodi does not support downgrading so the best approach is to clean reinstall LE 9.2.6 and restore the backup you made before updating. If you do a direct downgrade you'll have the reverse issue with add-ons; the ones that auto-updated to new Python3 versions will not be compatible with older Python2 in LE 9.2.6.

Please try installing/running the LE10 beta release.

I'm wondering if it detects any network card. It is possible to add "textmode" to kernel boot params in syslinux.conf on the USB and then it will boot to a local console (not Kodi GUI) where you can attach a USB keyboard and run commands to see the output on screen. The output of "systemctl status connman.service" will probably reveal what the issue is.

GBM (V4L2) is the new video pipeline that all ARM based LE devices are using for LE10.0. Codec licenses are not availaable as they are not needed: the RPi4 has enough CPU grunt to software decode all the media formats that historically needed them.

LE 9.2.6 or LE 10b1 ?