Contribute
Register

[Guide] Intel Skylake NUC6 (and Skull Canyon) using Clover UEFI (NUC6i5SYK, NUC6i7KYK, etc)

Status
Not open for further replies.
Andy1 said:
I created an override file with an EDID that set the native screen refresh to 48Hz instead of 60Hz. Since then I have had no reoccurrence of the problem.
Click to expand...

Today I removed the override file/rebooted and the blanking/black flash (for 2/3s) returned within 5 mins. So I am confident that creating an override file with EDID data specifying a native resolution of 3840*2160 @ 48Hz is a solid workaround for me. I have gone nearly 3 weeks now with no issues. I did try various other refresh rates and none worked. Some were so bad that the screen was almost unusable, but I presume the display just couldn't work at those frequencies. So I'm not sure why this works, just reduced data to the display possibly. I'd tried various other solutions including a new cable, so I'm pretty sure that isn't the issue and as has been posted, there are no problems with Windows. 48Hz seems to give me a smooth enough response, noticeable better than 30Hz, (I don't game).
 
Andy1 said:
Today I removed the override file/rebooted and the blanking/black flash (for 2/3s) returned within 5 mins. So I am confident that creating an override file with EDID data specifying a native resolution of 3840*2160 @ 48Hz is a solid workaround for me. I have gone nearly 3 weeks now with no issues. I did try various other refresh rates and none worked. Some were so bad that the screen was almost unusable, but I presume the display just couldn't work at those frequencies. So I'm not sure why this works, just reduced data to the display possibly. I'd tried various other solutions including a new cable, so I'm pretty sure that isn't the issue and as has been posted, there are no problems with Windows. 48Hz seems to give me a smooth enough response, noticeable better than 30Hz, (I don't game).
Click to expand...

48Hz is 80% of the data required by 60Hz (48/60=.8).
 
RehabMan said:
48Hz is 80% of the data required by 60Hz (48/60=.8).
Click to expand...

Although there must be a bit more to it than just data volume. I tried 45Hz and that was the value that was completely unusable. I eventually tried 48Hz as it's a multiple of 24 which tends to be a good value to try when video is involved.
 
@RehabMan
Thanks a lot for your great guide. My skull canyon works great within verified feature set. Nevertheless I´m wondering if there are chances to get some missing pieces added. In particular I´m looking for enabling "wake up on LAN" using my skull canyon. Not sure if this is a feature, which you are interested in or looking forward to. First step from my perspective is looking how come the NUC is rebooting after triggering a shut down in OSX if WOL is enabled in BIOS. NUC shuts down correctly while triggering a shut down in Win10. Willing to do some research and trials on my own. Appreciate a push into the right direction for accomplishing this in task it does not catch your interest. Next steps to look into the faulty recoveries from sleep. Of course can not assess if this target is achievable within reasonable amount of effort anyway. Appreciate your thoughts on this.
 
maedula said:
@RehabMan
Thanks a lot for your great guide. My skull canyon works great within verified feature set. Nevertheless I´m wondering if there are chances to get some missing pieces added. In particular I´m looking for enabling "wake up on LAN" using my skull canyon. Not sure if this is a feature, which you are interested in or looking forward to. First step from my perspective is looking how come the NUC is rebooting after triggering a shut down in OSX if WOL is enabled in BIOS. NUC shuts down correctly while triggering a shut down in Win10. Willing to do some research and trials on my own. Appreciate a push into the right direction for accomplishing this in task it does not catch your interest. Next steps to look into the faulty recoveries from sleep. Of course can not assess if this target is achievable within reasonable amount of effort anyway. Appreciate your thoughts on this.
Click to expand...

You're welcome to experiment and investigate. WOL just doesn't interest me...
 
RehabMan said:
You're welcome to experiment and investigate. WOL just doesn't interest me...
Click to expand...

Well...I would have hoped for a bit of guidance on where to start. But I take your response as I have to start from scratch on my own. Thanks for all nevertheless.
 
maedula said:
Well...I would have hoped for a bit of guidance on where to start. But I take your response as I have to start from scratch on my own. Thanks for all nevertheless.
Click to expand...

It probably has to do with the way the hardware is initialized by BIOS.
Or something ACPI is doing or not doing.
Or a specific combination of BIOS setting required.

Happy hunting.
 
Dear RehabMan，
To fix my hd630 hdmi audio, I followed your advice, I run ./install_downloads.sh，after reboot I got a AppleIntelInfo panic，please help me
 
Last edited by a moderator:
xinbaohongbao said:
Dear RehabMan，
To fix my hd630 hdmi audio, I followed your advice, I run ./install_downloads.sh，after reboot I got a AppleIntelInfo panic，please help me
Click to expand...

install_downloads.sh does not install AppleIntelInfo.kext.
That must have been something you did...

Remove AppleIntelInfo.kext.

Note: You should have never installed it, as with correct usage of AppleIntelInfo.kext you load it with kextutil, not install it...

Note: This guide is not for Kaby Lake NUC (NUC7). It is for Skylake NUC (NUC6)... as per post #1 and the title of the thread.

Kaby Lake support may come after the NUC7 is released.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top