One thing I noticed that is suspect (at least to me) is that the drivers 'insist' that the monitor on HDMI is actually DP. The Intel Graphics utility shows the HDMI monitor as part of the the Display Port topology on the NUC6i7KYK and not on the NUC5iRYH. This at least COULD explain the behavior shown in the videos.
* Digital Television *
Display Type: Digital
DDC2 Protocol: Supported
Connector Type: DisplayPort
Device Type: Digital Television
Thank you for contacting the Intel Communities.
Yes that configuration should be doable, due to the available bandwidth on the Intel® NUC Kit NUC6i7KYK.
Let me further investigate this in order to better troubleshoot the scenario.
All the information provided is really helpful, really appreciate it.
I will keep you posted.
Edited for Clarity : Issues I have are likewise on the NUC6I7KYK - Firmware 0034 - Graphics - 15.4444
Hi, I was going to start my own topic but this is pretty much spot on for me too though I'm using the DP connection (rather than HDMI) at 3840x2160.
I also had exactly the same issues on initial release of my older NUC5i5RYH which drivers fixed. Display can be perfect but sometimes on resume from sleep, monitor power off or even a full reboot I get the artefacts and occasional full screen flicker off and on.
It seems to be resolved by any of the below actions:
a) turning monitor off and on
b) Unplugging and re-plugging the display port cable
c) Changing the display resolution down and then back up again (easiest option)
I guess all this are forcing some form of displayport re-sync. I know its not the monitor or cable due to my prior experience with the NUC5i5RYH which was also used with the same setup and was fine post updates.
It is frustrating to have had to wait so long for a 'Real' i7 NUC to arrive and then have it mostly unusable. I was exceptionally disappointed in the 'fake' i7 in the NUC5iRYH. I was also disappointed that Intel doesn't 'support' these devices using Linux. (For which that particular NUC was intended to be a Linux front end.) AFAIK the 'i7' in the NUC5iRYH was the first dual core i7. This was a complete shock as I would NOT have purchased that unit had I actually KNOWN that. The irony is that even with the device ~barely~ able to keep up with some of my LOCAL workloads, it is considerably more usable than a machine that is (as a whole) over double the performance.
I want to move to using the NUC6i7KYK as my primary 'thin client' on the setup shown, but given the (lack of) quality in the Firmware/Display Drivers (supporting MY setup) I can not. So far the investment has been heavy with very little return. The dual M.2 NVMe support works decent with Samsung 950's and having double the memory is nice, but having the screens flash on and off constantly + the corrupted output from the HDMI display makes the device useless. I really don't understand how such a step backwards was taken. Unless the support for the IGP was forked prior to the fix and no one bothered to integrate it, I can't fathom why Intel would release such a compromised (for ~MY~ setup) set of firmware/drivers. Given that I PLAN on using the NUC6i7KYK as a test for dual 4K displays this doesn't bode well.
I'd consider getting a 3.1c to DP adapter, but given the current support I don't really want to spend MORE money for something that should ALREADY WORK.
ErnieE, as per alexhaddock's indication I would like to invite you to test the BIOS 0035 and the graphics driver 4454 to check the behavior of your system.
In regards to the investigation on this matter, it is being handled for sure as rguevara commented above, but let me get an update from the investigation team in order to provide you with some information about that.
I will keep you posted on this.
This morning I updated the firmware and video drivers and certainly have different behavior. A HUGE step backwards! After POST if I enter the firmware all three displays show the Intel firmware.
Now at the OS level NEITHER of the Display Port monitors works. The drivers DETECT them, but refuse to USE them.
I had to run into the office for a meeting so I didn't get a chance to get screen shots or videos.
I'll do that tonight or over the weekend.
Basically, only the single HDMI is supported at the moment.
That's a shame, I've had a massive improvement on mine since the update.
Updated BIOS to 35 - Still had issue (but the release notes didn't mention any graphics improvements to be honest)
Updated Chipset drivers 10.1.1.18 - rebooted
Updated Graphics to 4454 (it actually went to a black screen with cursor) - rebooted
Updated Graphics again (to be sure and it went fine that time) - rebooted
I also installed the newer ME drivers but doubt they have any relevance.
So far I've only noticed a couple of flickers (so perhaps a little more work needed) but nothing like the issues before.
I hope they fix your problem given how closely this mirrors the initial experience on the last NUC.
The current display configuration is:
Display (L2R) Dell U3014 (DP via MST) | Dell U3014 (DP) | Dell U3014 (HDMI)
Cable DP to Mini DP | Mini DP to DP | HDMI 1.4
At the OS level I can NOT get the new drivers (22.214.171.12454) to recognize monitors via display port. I haven't tried disconnecting the HDMI display. I have tried various features of the firmware to select how displays are reported to the OS. This hasn't been an exhaustive test with all permutations as I have limited time to 'mess with this' before having to revert back to a working system. (Same video cables, keyboard etc works.)
NUC6i7KYK Attempt to extend desktop to DP
NUC6i7KYK Boot Ignoring DP at OS level
NUC6i7KYK Attempt to use SINGLE DP display
NUC6i7KYK at firmware setup
Interestingly or annoyingly (depends on your point of view) after switching the cables back to the NUC5i7RYH and letting it boot with the exact configuration, I switched the cables BACK to the NUC6i7KYK. When the NUC6i7KYK came up, it ~finally~ decided the DP monitors were 'worth talking to', however, the behavior of the system has NOT improved AT ALL. The DP monitors wink on and off constantly and the HDMI monitor has the same artifacts shown in the original videos.
During the weekend my whole 'rig' was moved and the displays remained unplugged for at least 24 hours. When I did the firmware update on Friday, I had the displays setup so that I could selectively use three separate computers. (Which will eventually be duplicated in the 'new' location.) The NUC6i7KYK was the setup that got the same cable treatment. I don't know if the display driver is caching EDID information and this is causing issues. I have tried uninstalling and re-installing drivers.
Basically after hooking up the older NUC and then swapping the NUC6i7KYK back in, I am now back to the behavior in the original email. Sigh.
Thank you for your input on thisYu-Hao, the issue is being reviewed at the moment, as soon as I get a resolution on this I will let you know for sure.
Thank you for your patience on this, I just got an outcome from the investigation performed, it would be to install the HDMI 2.0 Firmware for your unit.
Here is the link to download it: https://downloadcenter.intel.com/download/26061/HDMI-2-0-Firmware-Update
Please let me know how your system behaves after installing this Firmware.