LE 8.1.2 is still on old 4.9 kernel, that's why. LE 9 is using 4.12 I believe, which has the updated driver.
It works for me (TM) 
Posts by escalade
-
-
I don't see why the Kodi devs would care as it has nothing to do with Kodi (except perhaps mapping for the peripheral.input addon). It's not really an "issue" either, it's just that the kernel driver was a big mess before and now they cleaned it up and added functionality. The touchpad even works as a mouse now. Mappings and auto configurations need to be updated.
Here's my mappings for RetroArch and Kodi peripheral.input addon:
-
-
You can look at the commit log on my github. As for the avx build not all changes have been commited.
-
The DS4 changes came with 4.10, I guess the DS3/sixaxis changes came later. However, there is no way but forward. If you want it working, find out what needs to be done and create a PR.
-
How old was the build you updated from? In January I added Linux 4.10 which did some major rework on the hid-sony kernel driver. I guess this is why you now have a "motion sensor" that shows up as it's own joystick device.
The "add back sixaxis patches" you saw in the changelog was just because in the previous build (20170920) I updated to bluez 5.47 and didn't bother to update those patches. Now LE upstream fixed them so I included them again. They are included in the haswell build as well. I think the patches are only necessary for the "gasia" type of unoriginal sixaxis controllers.
Oh and in the future, post the complete log zip and not what you think is the relevant log.
-
-
Sound works great for me (passthrough and pcm) on my x5-z8300 Tronsmart. Note that 4.13 for the first time properly enumerates all the audio devices on cherry trail so you'll need to re-select your audio device and choose the correct one. Also for your asound.conf, for me it's
hdmi:CARD=Audio,DEV=2.
-
Try adding "vers=2.1" or whatever version your server supports to the Options= field.
-
Read the 8.1.0 release notes and the countless SMB threads on the same subject.
-
In this case, I'd suggest giving up. You're unable to follow directions and I'm not going to hold your hand.
Don't have the hardware to test myself and not too much online atm, just ping me if you find out anything more or if there's revised patches. An updated haswell build is uploading in some minutes with 4.14-rc2 and v2 patches perhaps that's worth a shot.
-
The exports file is in /etc as in every other distribution. You'll notice that in my build it's a symlink to /storage/.config where LE keeps most it's config files. Sounds to me like the exports file you have is a leftover from a previous build of mine which could have had the wrong syntax for this version of nfs-utils.
exports(5): NFS server export table - Linux man page
EDIT: I noticed on my front page it still says that I share /var/media, which is incorrect, I only share /storage by default. Reason being that the crossmnt option is broken and mounted volumes needs to be specifically shared. I might fix this similar to how Samba does it in a future build.
-
20170924:
Codebluez: add back sixaxis patches linux: update intel eld patch to v2 linux: update intel hbr audio patch to v2 linux: update to 4.13.3 xf86-video-nvidia: update to 384.90The ELD connector patch v2 might fix your issue, so go ahead and give the latest build a try
-
How did you conclude that connman generates "millions of requests"? That sounds more like a DoS attempt to me.
-
The v2 patch has no practical difference for you.
There's an infinite amount of information available at your fingertips on how to write a proper exports file. There's a proper working example at /usr/config/exports as well.
-
If you use Docker you can pull escalade1/arch-build, clone my tree and do "make". It builds on my regular Arch install as well.
-
This is due to TexturepPacker:host not compiling with glibc 2.26 on the host system. I "solved" it by installing texturepacker from my distribution's (Arch) package system and doing this:
-
You have of course started the nfs server with systemctl start nfs-server?