[_Spook_]

Cool. I will test it tomorrow on the other NUC. Is the LSPCON patch in there also?

How is #0913y (4.8-rc6 kernel with 4K patch, and without Chris Wilson 8bpc patch)?

@Milhouse

No go. But I think I might have figured out whats causing the problem specifically for me.

So, my LG OLED 65E6 TV has a feature called HDMI Ultra Deep Colors which, among other features, enables HDR on that HDMI input. With HDMI Ultra Deep Colors ENABLED and this 4k patch or the Chris Wilson 8pbc patch I am not able to get a proper HDMI signal. This combined with the fact that the NUC6i7KYK does not have a NATIVE HDMI port but uses a chip ( http://www.paradetech.com/products/displ...ers/ps175/ ) to transform the DisplayPort signal to HDMI 2.0 signal (LSPCON).

This combination causes issue. But I would think that the main issue is the chip/LSPCON. That is based on the fact that HDMI Ultra Deep Colors are enabled with the NUC6i5SYK that has a native HDMI 1.4 output.

So, for now I will just use that NUC6i5SYK. But, this could be a problem when the next generation NUCs are released in Q1-17. From the leakes it looks like all of them will have the same chip and no native HDMI port. That conclusion again is based on the fact that Kaby Lake does not have native HDMI 2.0 and all Kaby Lake NUCs will have HDMI 2.0 output.

I could also just disable HDMI Ultra Deep Colors on HDMI2 input on the TV or just use another HDMI input. But I want everything trough the AVR and be able to watch HDR material from my Shield and Panasonic UHD player.

So, no biggie for me. But if you want to play with this with me you could generate a build without the 4k patch, one with the 4k patch and lspcon patch and one with just the lspcon patch. But I know it's alot of work so again no biggie