Posts by chewitt

rgmii (10/100/1000) and rmii (10/100) are different realtek PHY drivers .. the PHY is responsible for the physical connection to the network and Amlogic chips support "internal" rmii for free (it's part of the core SoC). Cost-engineered devices often skip the optional "external" PHY chip (usually rgmii but there are other options) to shave cents on the manufacturing costs. I'm not sure rmii is a good designation so the dts name might change, i've asked the kernel maintainers for their suggestions and preference.

project: add cpumac package · chewitt/LibreELEC.tv@e01aba3 · GitHub

^ this is an (incomplete) experiment in solving the problem on mainline Amlogic kernels. It won't work exactly the same as the CPU serial number is not exposed the same way on legacy kernels, as but you should be able to tweak the cpumac-config script and change the system.d service to ExecStart the modified script from a /storage/ location to make something work. Once you stop the MAC address changing on each boot by overwriting with a known value, the IP address you set via static config (via connman, or DHCP reservation in the router) won't change.

An OVA for vmware (workstation, player, vSphere) exists to support development work, but we have never formally supported it and have zero plans to change that or delve further into virtual hardware usage (KVM etc.) as it's very niche. YMMV.

Images are built and being tested.. it will come soon.

Kodi v17 and v18 are different with different features. Settings that exist in both will "migrate" to the newer version. Settings that never existed before the new version will need to be set. This has been true of all Kodi releases since I've run in the last decade. In most cases add-ons should self-update on first run of the newer version, but there may be reasons why that didn't happen and resulted in things being disabled. The main reasons are that you have old versions of Kodi binary add-ons are installed that are no longer API compatible and nothing newer is available. If all the add-ons were disabled you had a corrupted add-on DB leading to migration failure. In this case the problem add-on DB is cleared and automatically regenerated, but all the add-ons are disabled to prevent issues.

This thread is for balbes150 testing LE releases which are now focussed on the mainline kernel. If you want to run CE releases and discuss CE topics please take the chatter to their forum. If you want to experiment with mainline kernel images and LE things feel free to hang around here.

You will need to include user/password details as mount options because Win10 requires authenticated connections.

I've boot tested a C2 running the AMLGX (mainline kernel) image and from tonight or whenever the next balbes150 image gets pushed the HK remote works OOTB including power on/off (i've added device-tree keymap configuration and a kernel driver for the HK remote this morning). I have no idea about Harmony compatibility but it's a standard NEC protocol device so it probably isn't a big challenge for a learning remote.

I'm not implying anything, and I don't know what your MX3 variant is .. you were talking about C2 before.

It's been broken for a long time. I'm honestly not sure why it's still not marked as such in the Kodi repo.

What is hosting/providing the SMB server?

KyleS at this point there is no technical solution for S905X2 wifi on the mainline kernel. If that changes, then we can negotiate the project decision on how ugly the patch is and what to support.

LE has a browser which is semi-production ready. It works, but starting it requires Kodi to be stopped before it runs, and restarted after it closes. As Google frequently changes things that impact GPU hardware acceleration it has a history of only supporting software decoding at times (until someone fixes things). So it may or may not fulfil your needs for a browser. SteamLink is technically possible but requires a large number of hoops to be leapt through and is fragile at best. If those are major requirements a conventional distro (or Windows) would be better for you.

I haven't tested on WP2 for aeons but will dig one out and have a look over the next couple of days. WH (which has the same WeTek boot firmware) is working but you will need to use the "reset" process to reloads the boot instructions from SD card. If this is not done it will definitely not boot.

N2 is nice hardware although like most HK devices it has some quirks. It'll be even nicer when it doesn't run an obsolete franken-kernel, but mainline support is progressing swiftly. So far the G12A/B devices i've been playing with are noticeably quicker than GX devices. If you're not sold on the N2 there will be some other S922X devices in the market soon.

The USB/SD Creator app will write to any removable device. Some USB > IDE/SATA adaptors might not show up as removable, but the majority do and you should be able to write the image direct to the drive. The "USB" (or drive) should boot into installer mode by default, but it you hit any key at the syslinux prompt it will stop boot and you can type "run" to "USB boot with persistent storage" but it's not USB specific, it just creates a persistent /storage partition and changes the boot config from "installer" to "run" permanently. You might need to fiddle with boot settings to enable/disable UEFI or legacy boot support and in rare cases the BIOS/firmware might object to syslinux in which case you can always install grub as an alternative. The grub boot config is slightly different but extlinux.conf has all the details you need to set something up. As a general rule systems with problem firmware tend to be a bit too old and since (as a distro) we don't focus on old hardware at all, you may find drivers are missing.

.img or .img.gz files are used for install (but can also be used as updates) while .tar files are used only for updates

You can use "textmode" to prevent Kodi from starting and access a local on-screen console to poke around. Check the Ethernet port is full-duplex and share the URL generated by "dmesg | paste" so we can see the boot log (Kodi log isn't useful).