Posts by chewitt

Quote from DoktorX

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.

Quote from cdu13a

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..

"it depends" on when the OE install was made .. if the /flash (boot) partition is 512MB, yes LE fits, but if 230MB (older sizing) LE will not fit.

See Updating - LibreELEC.wiki

Since the file is clearly something you've pirated .. thread closed.

Running "df -h" will show the size of the disk, and "ls -l /storage/.kodi/userdata/Database/Addons27.db" will show size of the DB file (which has no limits on size) so either this is a new install where for reasons unknown the default 32Kb /storage partition failed to resize to 100% of the available space during install (if yes, recreate the SD card and start over, or connect it to a Linux desktop to resize the partition with Gparted) or perhaps there's an isssue where the DB file is zero bytes (if yes, just delete it and reboot).

Changing regdomain only works if you don't have an active wifi connection (so after reboot). Also, if you connect to a wifi network that has a regdomain announced on the router/AP (some do, some don't) and the driver supports this (most do, some don't) this will override the LE regdomain setting.

There are no plans to remove the current limited number of realtek modules (or to add more). If we do remove a module it will be because we can switch to an in-kernel module. Some of the older Realtek cards are supported in-kenrel now, but the drivers still aren't great and Pi Foundation feels there are too many older Pi users with the official adapter for us to switch. Realtek are more actively engaged in upstreaming support for latest/next chips now so in the future the situation will improve for new devices, but I suspect there will always be a gap for recent-past and older cards.

LE does not support pre-boot configuration of wireless details, it's not a requirement for our userbase (the other 99.999999% of it) so your options are to connect via Ethernet (direct cable between two devices with 169.x.x.x addresses is fine, it doesn't need to be a proper network) or use Raspberry Pi OS via NOOBS which can support pre-boot WiFI configuration.

LE uses 5.10+ kernel and Allwinner will be using a BSP kernel (usually 4.9, 4.19 or at best 5.4) so any modules you compile will not be compatible.

documentation/cm-emmc-flashing.md at master · raspberrypi/documentation · GitHub

^ this is the procedure for mounting the emmc storage. In my experience the Slice box is a bit tempremental about connecting to the host so don't be too surprised if it doesn't work first time. Once the emmc is mounted as a local disk you can flash the LE image using any USB/SD image writing tool (ours, Etcher, Win32DiskImager, etc.).

I thought wireguard: Regular reresolve endpoint address · igaw/connman@90592f7 · GitHub should have solved this issue? If not I might need you to explain the problem properly so I can replicate it and nag the ConnMan devs.

marantz using the settings add-on to set the regdom?