Posts by chewitt

mglae some early testing is positive. I've enabled systemd-time-wait-sync and added time-sync.target to "After" in wireguard.service. If we see a few more positive reports I'll push some changes.

genidy.m please do not cross-post the same information to multiple threads. If you make one post it will be seen by the developers and mods. Multi-posting is annoying and will normally decrease (not increase) the chances of someone taking an interest in your problem.

One of the challenges with RPi boards is there is no power-off button. So 99.9999% of the time you get away with a hard power pull, and once in a while you don't. It's imposssible to diagnose the problem from that screenshot, so you probably need to nuke LE using the noobs boot manager and reinstall.

It would be nice to do this but Kodi doesn't currently have API methods that would allow it to be done, and it's programatticaly complicated as Kodi supported languages has a different list of things to Kodi input settings which is different to OS locales which is different to Wireless RegDom options so there's no neat/tidy 1:1 mapping of things. It's not impossible to improve, but so far nobody on staff (which includes plenty of Germans) has ever volunteered to tackle the task

Having done a bit more reading I have a suspicion we need to start using systemd to handle NTP as this adds a new systemd .target for when the initial NTP sync has completed, which would be useful in this scenario. That's something for the master branch though, I wouldn't risk that kind of change being backported to 9.2 at this stage in the release lifecycle.

Have you enabled "disable password auth" in LE settings for the SSH service?

The upstream vdec supports H264 and VP9 currently. HEVC is still work in progress so it will be software decoded. Other (older) codecs like MPEG4 and MPEG2 are a low priority for hardware support as even lowly S905 can software decode everything fine. You S912 nox should be able to handle 1080p media in the current state, but not 4K (as most 4K media is HEVC). The kernel stateful API changed in the semi-recent past and this broke seeking .. we're still trying to figure out what and where things need to be changed to make it work again.

I didn't ask you to edit an existing file. I suggested you run a command that creates the file.

/etc/fstab is not editable (or overwriteable) as it is not used or required in LE - it exists solely as a dummy file because some packages expect it to be present and fail to start if it is not. In LE locally attached drives that recognised (and not corrupted or unclean) filesystems will be auto-mounted by udevil, and network drives can be handled through systemd .mount files (see /storage/.config/system.d).

From what I've read WireGuard requires monotonic time, i.e. time can change but must always move forwards, so it shouldn't be affected by the time-jump seen when NTP kicks in (unlike TLS certs which are invalid until current time is greater than cert start dateTime) as time starts from libc compile time (some date in April?) but I'm not an expert in these things. I suspect the timing/sequencing for WireGuard in the .service file could be improved as I'm a novice with systemd things.

It should be impossible to update from older LE (3.14 kernel) to nightly (mainline kernel) images .. I added an explicit check to detect this and abort:

LibreELEC.tv/canupdate.sh at master · LibreELEC/LibreELEC.tv · GitHub

I haven't been adding the realtek vendor-binary drivers to the LE master branch for Amlogic as I'm typically working on an rc kernel and these things break all the time, but I have enable most of the in-kernel drivers and rtl8188ee should support that device. Can you run "dmesg | paste" when using Ethernet (but with the WiFi device connected) and share the URL, it might me something simple like missing firmware.

No ideas why it fails, but we have cron in the OS so the ugly workaround is to schedule a reboot at 2am every night.

No, WP2 is S905 (GXBB) and VP9 support didn't appear in hardware until S905X (GXL) so it's software decoding.

lumpi I can't say much about Tartiflette until LibreComputer publish more themselves, but it's packaged for industrial use-cases and will also ship as an S905D device so it probably won't appeal to LE users. It's relevance will be that it's a device LibreComputer will want broad "out of box" upstream Linux and distro support for, and since they're one of the few entities that supports (funds) upstream work, that's ultimately good for anyone else with an S912 device.

GitHub - chewitt/amlogic-boot-fip: Firmware Image Pacakge (FIP) sources used to sign Amlogic u-boot binaries in LibreELEC images <= has all the FIP sources that I've found, and the VIM2 sources seem to work on a number of the other S912 boards and box devices I have. Focus on learning how to build mainline u-boot from sources and then run through the Amlogic signing process to make a bootable firmware. The signing recipe is documented in u-boot sources, see u-boot/board/amlogic/q200 at master · u-boot/u-boot · GitHub

Quote from Plicha

I'm using latest LibreELEC release for Windows.

No you are not, we do not provide software for Windows

Did you put the firmware in /storage/.config/firmware or /storage/.config/firmware/bnx2/ ? .. files are overlaid on /usr/lib/firmware so if files are normally found in subdirs you need to create them too.