Posts by escalade
-
-
20170710 uploading:
Codeffmpeg: update to f58e5b9 kodi: update to 80844fd (pre 17.4-rc1) dolphin: update to dcb4386 vulkan-loader: update to 1.0.51.0 curl: update to 7.54.1 wpa_supplicant: update to 2.6 for compatibility with openssl 1.1.0 openvpn: update to 2.4.3 for compatibility with openssl 1.1.0 libssh: update to 0cb2974 for compatibility with openssl 1.1.0 kodi: use mariadb instead of mysql openssl: update to 1.1.0fSABnzbd users may need to remove certificate/key in /storage/.config/sabnzbd/admin to get new ones regenerated if https isn't working.
-
Are you sure the hardware supports it with HDMI? Perhaps try DP.
-
Same way as with a tar.
-
Your log is reporting 1080p@60 as the maximum:
CodeINFO: ID:0x48 Name:1920x1080 Refresh:60.000000 Width:1920 Height:1080For a recent NUC I would recommend a community build with the latest and greatest kernel / display driver stack. Try mine or Milhouse's.
-
I've located the issue (CONFIG_BASH_IS_ASH wasn't enabled in the updated busybox config), this caused rpi-btuart which uses #!/bin/bash to fail.
20170708 uploaded:
Code
Display Morelinux: update to 4.11.9 retroarch: update to dc521b4 desmume-libretro: update to 73531d7 genesis-plus-gx-libretro: update to 9c10f4f tyrquake-libretro: update to a0502d1 SABnzbd: update to 2.2.0Alpha2 mame2003-libretro: update to e0a9df4 quicknes-libretro: update to 05a742e retroarch-joypad-autoconfig: update to 8e68505 reicast: add pr1002 to improve keyboard handling xf86-video-nvidia: update to 384.47 -
I uploaded a new build with libevdev, can you check again? I'm surprised if that ends up being the issue, can't quite understand the relation to bluez or the rpi-btuart script.
-
Yeah I think you are right, busybox mount doesn't seem to support NFSv4. It works for me as I've packaged nfs-utils in my build
LibreELEC.tv/packages/escalade/network/nfs-utils at le8-test · escalade/LibreELEC.tv · GitHub
-
I noticed this in your previous log: "09_Journal-cur.log:Jun 28 08:20:21 LibreELEC systemd[559]: brcmfmac_sdio-firmware.service: Failed at step EXEC spawning /usr/bin/rpi-btuart: No such file or directory"
This could be an indication to what's going wrong, seems related to the bluetooth interface. Could you compare with the working build? Does the service start correctly there?
Also I've uploaded 20170705 which is a full rebuild with busybox reverted and no libevdev (I don't think that's it but just to exclude that too). If it still doesn't work play around with the rpi-btuart script see why it's failing. Also check that the bluetooth service didn't get disabled in libreelec settings.
-
Libreelec 8.0 doesn't support nfs4 (is built in, but it lacks idmap i think), which would ease your way just by using port 111 and 2049. Problem is the client (v3) opens a random port below 1024, that changes for every mount. From what i know librelec doesn't provide a way to set this to a static port. Maybe a custom rebuild?, i wouldn't know where to start looking for this configuration.
You need to relax the outgoing connections, and use an input rule for established connections.
LE8 supports NFS4 client connections (through mount/kernel), idmap is only needed server side.
-
You can use autostart.sh or systemd.
-
20170704 uploaded for the rpi please test.
-
HEVC decoding is supported on Intel, HDR is not supported yet. For Kodi purposes, I'd say stay with Intel.
-
-
That's client support, you'll need to look for CONFIG_NFSD_V4 unless it's a userspace NFS server.
That being said, NFSv4 client support is enabled for all projects in LE:
LibreELEC.tv/linux.arm.conf at libreelec-8.0 · LibreELEC/LibreELEC.tv · GitHub
-
Then I've no clue as to what's the problem. There's no relevant commits since the working build from june 15. There's updated busybox and kernel, both which were reversed in the test builds without success. Might be due to my build system being a rolling distribution, so updated packages there could cause unforeseen issues with packages due to the nature of LE's toolchain. I'll do a build on my older build system some time this weekend to see if that solves it.
Poking around with bluetoothd (perhaps using strace or adding debugging) might give some clues.
-
It's not released yet, you would need to build yourself. There are community builds that has samba4 like mine or Milhouse's.
-
And bluetoothctl after startup of the daemon? You did activate bluetooth in LibreELEC settings right? Not doing so would result in the daemon not starting.
Latest has legacy drivers. I'll keep them for now, but they will get cut sooner or later then you'll need to build yourself. I simply do not care for decade old hardware that I don't even have.
