Posts by chewitt

WireGuard is a kernel module (currently out-of-tree) and a userspace config tool (wg) that are used to configure a wg0 network interface that presents in the OS much like a normal Ethernet interface. I'm still actively working on the userspace packaging so balbes150 images are usable with some caveats but also subject to change. I've also identified an interesting connman bug with NTP (reported upstream last night) that needs fixing before it'll be possible to use automatic WireGuard connections on boot. It's also untested on Generic/RPi so I need to spend some time on that too. I'm hoping to get it merged as an LE9.2 feature. Compared to OpenVPN the initial config process has more confusing terms (lots of things that sound the same) but it's actually rather simple and connections take a second to create.

Have a look at /storage/.config/wireguard.conf.sample .. rename to wireguard.conf and it will start the connection on reboot, but this will cause NTP to fail and if the system clock is wrong most SSL certificates will fail validation causing other issues. You need to stop, pause, restart wireguard.service to workaround that until the connman fix comes in.

project: add wireguard package · chewitt/LibreELEC.tv@d82a723 · GitHub

balbes150 images do not have the latest changes I pushed last night so "wg-quick" does not exist until his next rebase/release.

???

I've been experiencing the same "connman attempting to use IPv6 NTP servers" issue while poking WireGuard support. I finally managed to track down one of the connman developers, which led to this chat:

[22:28:39]  <wagi>    IIRC, we try resolve the nameservers and when we get an IPv6 we try it. Don't know if we have some logic in place which checks if IPv6 is up
[22:31:04]  <wagi>    Indeed, we try IPv6 without checking if IPv6 is setup
[22:31:20]  <wagi>    So that explains the 'Time request for server' message
[22:31:44]  <wagi>    We should check if IPv6 is up and running before trying to send IPv6 frames :D

Fingers crossed there will a patch to test in the near future

MikeKL my branch currently has some experimental code for WireGuard support and I modified /usr/bin/usercache-setup to create the WireGuard keys, so my guess is /usr/bin/wg is missing due to WireGuard support not being included in balbes150 images, and thus usercache-setup.service fails. If that's the case it's nothing serious and I'll tweak the script so it avoids the failure.

If you install default LE you get a 512MB boot partition which is approx 2x. the size needed for our normal image boot files. Nothing wrong with that.

RR needs considerably more space (about 700MB) which is why it's creator uses a 1024MB boot partition size in his install images.

So you all you need to do is install using the RR .img.gz that 5schatten provides.

NB: your KEYBOARD appears to have some caps lock PROBLEMS.

Gitlab is a bit more advanced in overall features than GitHub, but ultimately git (at the command-line, where all the real work gets done) is just git and unless you're needing to fiddle with CI pipelines I find them to be much the same; visual differences aside. My personal preference is GitHub due to more whitespace in the GUI and finger memory of how things work, but I'm still closer to n00b than power users so I wouldn't assign much gravitas to my opinion on the topic. Try both, whatever works for you and results in public shared code is a good thing.

c.2001 I used to heat the ground floor of my house in the UK with the thermal output of a NetApp filer cluster

Quote from relkai

btw.: Could we please stop calling this metal thingy a "radiator", but a heatsink instead?

To explain: balbes150 reads this forum (and replies) entirely via Google Translate, and while it does a reasonable job, it also makes some persistent mistakes including heatsink > radiator, compile > assembly, and banned > illegal. I've also noticed that Google frequently uses English words that are stronger in meaning than the original Russian text, so it's best to not read his words too literally. Once in a while Google also mangles his sentences into something unintelligible (even if you understand Russian it doesn't help) but that's all part of the fun contributing to a global project

Please keep the conversation civil or this and other threads will be locked and moved to the off-topic bin or be trashed. The N2 is a reasonable board and we (all) look forward to good open-source support for it and other next-gen Amlogic devices.

Yes, as it contains the contents of /storage/.cache .config and .kodi .. and autostart.sh lives in .config

kowalmisiek you need to provide a Kodi debug log so we understand what kind of device you are using .. and can see what the issue is

I can't speak for a few days ago, but right now 2.3.15.0 is present.

In short, no. If there's a reasonable use-case to extend the capabilities of the ffmpeg-tools add-on, a pull-request with changes is welcomed.

The x86_64 image has "boot" and "run" options in addition to the default "installer" mode. I forget which is which, but one is a persistent "Live USB" mode and the other is the same but non-persistent. Hit tab at the syslinux prompt (instruction text is on-screen, but not for long before the installer starts).

The 4.9 kernel is the same badly written Amlogic 3.14 codebase forward ported to a marginally newer (December 2016) kernel. I've even heard some rumours of a 4.19 version being worked on. I wish everyone the best of luck using them once amcodec is removed

Quote from Rover95

Hi Guys.. Was mentioned there was a sky go addon someone had working? Is this a UK version as assume the german one is only for those with German sky? If so where do I find it.

SkyGo is for German users only. There is currently no equivalent for UK users.

There are balbes150 test images available in this forum if you want to have a play with 5.0 kernel images. For 1080p/8-bit/2.0 video things are super stable but 4k/10-bit and multi-channel audio development is still work in progress.

To manually install LE .. create two EXT4 partitions on a disk; 1GB for "BOOT" and remaining space for "STORAGE" then install any bootloader that works on that hardware and configure it for boot=LABEL=BOOT and disk=LABEL=STORAGE .. and ensure KERNEL/SYSTEM live in the boot partition (and mark it active). That's all our installer does. We use syslinux but GRUB and others are fine. We don't touch boot ever after install.

NB: Team Kodi gave up on maintaining an entire distro (Kodibuntu) but the stable/unstable PPA's are still maintained for use with current Ubuntu.

See Kodi stable : “Kodi” team