I flagged it to one of the kernel maintainers (Neil) who supports LibreComputer.
Posts by chewitt
-
-
1. Yes, Chorus contains a web-based "remote" which can be used to navigate the GUI to access the LE settings add-on. You'll need to be on the network first for that to work of course.
2. Run this command and reboot: echo "options cfg80211 ieee80211_regdom=FR” > /storage/.config/modprobe.d/cfg80211.conf .. this will change the wireless regulatory domain to French specs which should better match the radio properties of the router, which may help. Wireless radio properties are not as simple as "n vs. ac" but that's the limits of configuration. LE10 in the future will move the config of regulatory domain to the GUI. Bonne chance!
-
Does it work if you change "python" to "/usr/bin/python" ?
-
If your (unknown) LE device supports WOL packet wake-up then you can use that option. If the (unknown) device does not .. there is no magic feature for turning boxes on. ESP would be cool, but we've been trying that for years while drunk and still can't get it to work
-
Two important points:
a) LE add-ons are compiled and packaged for LE - so I wouldn't expect them to run anywhere else. We do not publish a repo installer (the files are embeded into LE images) and even if you managed to get past that; when it doesn't work we have no interest in trying to fix anything.
b) The Chrome browser only exists for x86_64 hardware so there is no Chrome add-on in the Pi add-on repo anyway.
-
The WH dtb is preconfigured for the WH remote, but can be changed same as any other device Infrared Remotes [LibreELEC.wiki]
-
The mainline kernel handles RAM size dynamically so there are no 1G/2G/3G variants of devices trees. You should be able to boot the p200 device-tree. The WeTek Hub dtb is also for a 1G S905 device. NB: You cannot use legacy kernel dtb's on mainline. You can also try the AMLGX-box image from official nightlies, the boot arrangements are slightly different to Oleg's images in this thread. See: Index of /
-
I guess you're building on Arch? .. it might be easiest to build in a Docker container. Look in tools/docker in our build-system.
-
RPi4 is probably going to be the better supported device in the long-term, there will be millions more of tthem than S922X boxes, but I would always advocate seeing what's around in the future when you reach the point of wanting/needing to upgrade because it's a fast-moving world. In the next year S908X will probably take over from S922X as the high-end chip in boxes, although Linux support will lag a little behind if there's major changes to the SoC architecture (likely not, but until we see them it's unknown).
Glad you got it sorted out.
-
-
I suggest upstream translators don't do a half-arsed job with their translations. It's the correct and darn sight easier approach
-
-
flirc_util is packaged for more conventional distros. I'm far from being an expert package creator, but I'll have a look into what's required to repackage it into a binary add-on for LE use. This will take me "some time" though (lots of other priorities at the minute) so it's probably easiest if you find a Windows, macOS or other Linux box to reprogram the USB dongle from.
-
If we remove the word from our anti-spam list we get lots of nice chinese/korean people advertising their solution for preventing the mail loss of filament structures that come out of your head. The occasional user inconvenience is easier to live with than regular spam deleting.
-
I tried to search a folder "update" to paste the .tar but the folder not exist.
The folder is /storage/.update not /storage/update .. the . hides the folder unless you view hidden files.
-
-
From ConnMan devs:
"ConnMan resolves the FQDN on start of the VPN service and hands over the IP address to the WireGuard device. The WireGuard kernel code doesn't do any resolving. I am going to post a patch which reresolves the Endpoint address. If the address changes ConnMan will 'update' the WireGuard device. I've stollen this idea from reresolve-dns.sh « reresolve-dns « contrib - wireguard-tools - Required tools for WireGuard, such as wg(8) and wg-quick(8)"
There's also a second patch to remove "WireGuard.domain" from the config as "Domain" isn't really needed. NB: After this patch is included the internal service identifier will change needing you to correct any systemd files.
Patches => [PATCH 0/2] WireGuard/VPN small tweaks. - connman - Ml01.01.Org
If some of you are self-building images .. it would be good if you can test these patches. Please provide feedback to this thread and if there are positive reports on the DDNS improvement I will ack the changes on the list so things get merged upstream (and then added to the LE codebase).
-
linux-amlogic/gxbb_p200_1G_wetek_hub.dts at amlogic-3.14.y · LibreELEC/linux-amlogic · GitHub
^ dropping that from the device tree should/might do the trick. LE moved all development away from the legacy kernels to mainline so you won't find anything from us. Hopefully everyone being locked up at home for a while stimulates the ffmpeg work to be finished off..