Contribute
Register

Intel NUC 10 Frost Canyon

I just wrote to OC post in the other site to @vit9696 with the issue related to device H_EC, hopefully we will find a way to prevent AppleACPIEC from loading, just a note to everyone in this post.

Once the issue has been solved I'll try helping with the other issues too.
Your support is greatly appreciated!!
 
dolgarrenan, thank you for your efforts!

svandive, do you have any issues with sleep/awake?
I discovered very unpleasant behaviour with waking up from sleep.
You can have NUC go to sleep either by hand (Apple Logo --> Sleep) or by timer (in System Preferences --> Energy Saver) and as soon as you awake it by mouse/keyboard it starts flashing HDD LED actively for 15-20sec (looks like it is intensively reading/writing something) and then nothing happens - display says NO SIGNAL and NUC becomes unresponsive.
Still finding a solution... there are many topics with it but none of them worked for me so far.

For me unclear situation with EC, sound and now sleep issue does really prevent from migrating to NUC from my current MacBook.
 
Last edited:
Let's work backwards. Try my EFI and let me know if this gives you resolution control. Then we can figure out why. also check your BIOS settings. What do you have for the three entries under video?

This EFI works very well. Thank you. All I needed to do was plug in a Serial number.

I have HDMI audio/video working (1080P) from the built in HDMI port, and two more 1080P monitors are connected via a dell D6000 using display port drivers.


That's not bad.
 
Last edited:
dolgarrenan, thank you for your efforts!

svandive, do you have any issues with sleep/awake?
I discovered very unpleasant behaviour with waking up from sleep.
You can have NUC go to sleep either by hand (Apple Logo --> Sleep) or by timer (in System Preferences --> Energy Saver) and as soon as you awake it by mouse/keyboard it starts flashing HDD LED actively for 15-20sec (looks like it is intensively reading/writing something) and then nothing happens - display says NO SIGNAL and NUC becomes unresponsive.
Still finding a solution... there are many topics with it but none of them worked for me so far.

For me unclear situation with EC, sound and now sleep issue does really prevent from migrating to NUC from my current MacBook.
I'm not able together sleep working properly (or I should say Wake) working properly. I have a plan to sit down and be a bit more methodical about the settings in the BIOS and how they might effect Sleep/Wake. I'll let you know if the various settings in the BIOS have any effect on allowing a sleep/wake cycle to work properly.
 
I'm not able together sleep working properly (or I should say Wake) working properly. I have a plan to sit down and be a bit more methodical about the settings in the BIOS and how they might effect Sleep/Wake. I'll let you know if the various settings in the BIOS have any effect on allowing a sleep/wake cycle to work properly.

It's likely we may have to dig into a DSDT fix for sleep.
 
It's likely we may have to dig into a DSDT fix for sleep.
I'm using the USBPorts.kext attached and turned off XhciPortLimit in the config.plist under Kernel/Quirks. It doesn't identify the internal USB ports, just the external ones. I think there is another controller that Hackintool doesn't identify and/or I need to do a deep dive into the guide for creating the kext because it won't always reliably wake up.
Hackintool.png
 

Attachments

  • USBPorts.kext.zip
    2.3 KB · Views: 65
It doesn't identify the internal USB ports, just the external ones.
Leesureone, why you think there are hidden (not recognised by Hackintool) USB port(s)?

According to the Intel's spec:
The USB port arrangement is as follows:
  • USB 3.1 Gen 2 (10 Gbps) Type C port implemented via the external back panel Type C connector (maximum current is 3A @5V or 2A @9V) = 1
  • USB 3.1 Gen 2 (10 Gbps) Type A ports (maximum current is 900 mA for each port): Two ports are implemented with external front panel connectors (blue) = 2
    Two ports are implemented with external back panel connectors (blue) = 2
  • USB 2.0 ports (maximum current is 500 mA for each port of the white header (1 A total): Two ports via two single-port internal 1x4 1.25 mm pitch headers (white) = 2
    One port is reserved for the M.2 2230 Wireless module = 1
8 in total + some of them are switched so Hackintool shows 13. The same amount is shown by USBMap tool.

If you use USBInjectAll.kext you will get the same quantity (with XhciPortLimit OFF), so I reckon this is real number of USB and there is no need to build special USB kext excluding some ports, because it's less than 15. Or I lack of some knowledge?
 
Leesureone, why you think there are hidden (not recognised by Hackintool) USB port(s)?

According to the Intel's spec:

8 in total + some of them are switched so Hackintool shows 13. The same amount is shown by USBMap tool.

If you use USBInjectAll.kext you will get the same quantity (with XhciPortLimit OFF), so I reckon this is real number of USB and there is no need to build special USB kext excluding some ports, because it's less than 15. Or I lack of some knowledge?
Did you see the screen shot with the question mark? Regardless something is off, permanent sleep isn't what I'm looking for. Wondering if the kernel patch needed for the CPU is messing with it. I've got a wireless keyboard plugged in, that's it
 
Last edited:
Did you see the screen shoot with the question mark? Regardless something is off, permanent sleep isn't what I'm looking for. Wondering if the kernel patch needed for the CPU is messing with it. I've got a wireless keyboard plugged in, that's it
One of those is the XHCI and the other is the Thunderbolt USB controller. you do have two controllers but one is part of the Titan Ridge and the other is part of the Chipset.
 
One of those is the XHCI and the other is the Thunderbolt USB controller. you do have two controllers but one is part of the Titan Ridge and the other is part of the Chipset.
I knew that but was wondering if I needed to rename the USB controller. Hackintool sees a question mark and because its a new chipset wondered if the kext I created was missing something. Guess not but sleeps not dependable.
 
Back
Top