@wesman said:
@raven-au said:
Screen constantly blanking in Windows (but seemed to be OK in full screen PMP) and wireless not working at all.
Might be the latest Intel drivers, or the firmware patch, or both.
Why do you say the wireless is having issues? I have also, seen buffering issues inside plex (on wireless) but have not been able to point it at intel, just yet.
Buffering over wireless is usually not a problem for me and hasn’t been a problem since around the time AC1300 wireless came out. Distance of devices from my router is are fairly short so throughput is usually pretty good. My D54250WYK has no problem playing a movie that is around 19Mbps at the same location I was using the NUC6CAYH. Of course the 1x1 wireless on the NUC6CAYH might be a different story but I won’t know that until the wireless is working reliably, see below.
do you know something?
LOL, I don’t know much of anything!
On Windows the wireless did appear to be working ok, but in a different location and before a recent driver update, so these things might be a factor.
The problem I see (on Windows) is the NUC6CAYH doesn’t see the SSID broadcasts. At one point it did see the 2.4Ghz SSID for a while but it went away.
In the other location wireless was working ok in Windows, actually I’m not sure I was even getting decent throughput on Windows, can’t remember now, it’s early days and I’ll need to do more to gather accurate info.
Booting into PMP or LibreELEC 8.0 I was unable to connect using connman most of the time but was seeing the expected SSIDs.
The adapter in the NUC, AC-3168, is apparently supported from kernel 4.6 and IIRC PMP had a later kernel than that.
The adapter firmware wasn’t present in PMP so I located it and dropped in into .config/firmware , and it was found and the adapter initialized ok, according to dmesg output. But still there were connection problems and when I was able to connect it was unusable from a throughput POV (almost non-existent actually). Again, IIRC, the firmware was present in LibreELEC 8.0 but I still had the same problems.
I’ll probably need to revert to an earlier driver version (on Windows), when I get time, to check further.