Posts by chewitt

    passphrase = password .. although <space> is a valid character so you can have multiple words; hence "pass phrase" is a more accurate description of what's involved. It's also hard to guess what the problem is from your description. You will need to be more specific about what "logging on to my network" means (where in the GUI, etc.)

    Anything under /etc is not writeable in LE (as it's part of a read-only squashfs file) but you don't need to touch wpa_supplicant anyway as this is driven by connman which has an easy to use console configuration tool (connmanctl) which writes the service/settings files. Manual configuration to those files will fail unless connman is stopped as connman will overwrite them at any time.

    Code
    connmanctl
    agent on
    scan wifi
    services
    connect wpa_your_network_psk
    <enter password>

    ^ if you insist on configuring from the console that sequence of commands will work. connmanctl is also scriptable but configuration from the GUI is also available. I can't explain why you saw an error, but the GUI is the normal and recommneded way to configure network things.

    I have a SFTP server (SSH access) which is for me the easiest way to configure it as it's simple to configure for macOS or Linux

    I'm not sure which end you think is simple .. because from here is sounds like you made the whole thing wildly complicated. SMB is perfectly fine for domestic media use. SMB sources take ~30 seconds to setup.

    No wiki, only kernel sources. If/when at some future point it makes sense the Pi Foundation will switch over .. but I wouldn't expect that to be a high priority for them. Making perfect software is somewhere on the list, but helping kids learn stuff comes first, and the current assorment of 32-bit code does that job just fine.

    The /storage/folders are hard-coded and will be recreated on boot if removed. To stop that behaviour you'd need to compile a custom image with modifications to packages/mediacenter/kodi/tmpfiles.d/kodi-userdirs.conf .. just ignore them, they're harmless.

    Rename /storage/.config/samba.conf.sample to /storage/.config/samba.conf and edit the file; there's a section that needs to be uncommented to make one of the devices the local browse master. You don't change the behaviour of the less important devices; you change the most important. The thing to remember is that the browse master should be something that's always on (or almost always) else you're forever forcing elections.

    I have LE booting on a Khadas VIM3L with 5.4 kernel which is the same S905X3 (SM1) chipset, but the changes needed for that aren't in LE master branch nightly builds yet and due to rework on video decode and my real-world job schedule the master branch won't be usable for a while. I'll send an email to Beelink for the Android dts file and schematics. The dts won't be usable with LE but S905X3 and S922X are pin-compatible and comparing against the GT-King/Pro dts will reveal any changes. I have the GT-King/Pro devices booting the same (not quite functional) LE image. I need to find time to finish checking the schematics before sending the device-tree file upstream to the kernel. The Beelink u-boot is a sh1t to work with though. It's simple to trip into update mode but it doesn't allow enough time to detect alternative media so 9/10 times it won't boot into LE for install. Once it does it's fine, but getting to first boot is unreliable.

    No plans, and I doubt that will change until one of the core team swaps to an ISP that forces them to use IPv6 .. or until a user with an IPv6 connection and some dev skills starts to poke around and sort things out and sends us some PRs. Until then IPv6 support "is what it is" .. which is largely untested and thus likely to be not implemented correctly or complete.

    Hub and WP2 can boot mainline Linux kernels and there is active development to re-add support in a future LE release. It was going to be LE10/Kodi v19 but since Kodi brought forwards the release date to push the python3 changes public we probably won't make that schedule.

    Amlogic "USB Burn Tool" allows you to connect the device via USB ports to a Windows laptop and flash an image (in a proprietary Amlogic format, not the same format we've ever used) directly to the internal NAND/eMMC storage. It's for flashing factory images onto a device. Most images will be Android, but it restores the factory u-boot, which negates any changes that other boot scripts have done to the boot environment.