Intel NUC 10 Frost Canyon

[svandive]

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.

have you been able to sleep and wake your machine at all? I've not successfully put mine to sleep and been able to wake it back up again. The system is permanently frozen once it sleeps. I have to power cycle to regain access.

 

[Leesureone]

have you been able to sleep and wake your machine at all? I've not successfully put mine to sleep and been able to wake it back up again. The system is permanently frozen once it sleeps. I have to power cycle to regain access.

I have, my EFI folder is posted here in the NUC7/8 thread Rehabman started if you want to try it. #894

Pretty much the same as yours with some tweaks.

 

[dolgarrenan]

Hello guys, finally we have a solution to H_EC and AppleACPIEC loading! Thanks to a user from the OC dev forum we managed to come with the correct patch and SSDT for our NUC10!

No more device H_EC loading

and no more AppleACPIEC kernel extension

Find the patch code for OC and the new SSDT for EC.

Let's now try to find a solution to our wake and video issues, after trying to sleep/wake I have found that what's causing not to wake (in my case) is the thunderbolt!

panic(cpu 10 caller 0xffffff7f90952399): "UPSB(Macmini8,1): thunderbolt power on failed 0xffffffff\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-370.100.21/IOPCIBridge.cpp:1398
Backtrace (CPU 10), Frame : Return Address
0xffffff83b86b3a60 : 0xffffff800ff1f5cd mach_kernel : _handle_debugger_trap + 0x49d
0xffffff83b86b3ab0 : 0xffffff8010058b05 mach_kernel : _kdp_i386_trap + 0x155
0xffffff83b86b3af0 : 0xffffff801004a68e mach_kernel : _kernel_trap + 0x4ee
0xffffff83b86b3b40 : 0xffffff800fec5a40 mach_kernel : _return_from_trap + 0xe0
0xffffff83b86b3b60 : 0xffffff800ff1ec97 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff83b86b3c60 : 0xffffff800ff1f087 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff83b86b3cb0 : 0xffffff80106c27cc mach_kernel : _panic + 0x54
0xffffff83b86b3d20 : 0xffffff7f90952399 com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge14constructRangeEP17IOPCIAddressSpaceyyP7OSArray.cold.1
0xffffff83b86b3d40 : 0xffffff7f90939fcf com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge19_restoreDeviceStateEP11IOPCIDevicej + 0x88b
0xffffff83b86b3da0 : 0xffffff7f9093a50e com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge18restoreDeviceStateEP11IOPCIDevicej + 0x60
0xffffff83b86b3dc0 : 0xffffff7f909386f6 com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge19setDevicePowerStateEP11IOPCIDevicejmm + 0x282
0xffffff83b86b3e10 : 0xffffff7f9094301f com.apple.iokit.IOPCIFamily : __ZN11IOPCIDevice13setPowerStateEmP9IOService + 0x63
0xffffff83b86b3e30 : 0xffffff80106148a4 mach_kernel : __ZN9IOService19driverSetPowerStateEv + 0x184
0xffffff83b86b3ea0 : 0xffffff80106146aa mach_kernel : __ZN9IOService15pmDriverCalloutEPS_ + 0x2a
0xffffff83b86b3ec0 : 0xffffff800ff61565 mach_kernel : _thread_call_delayed_timer + 0xec5
0xffffff83b86b3f40 : 0xffffff800ff61091 mach_kernel : _thread_call_delayed_timer + 0x9f1
0xffffff83b86b3fa0 : 0xffffff800fec513e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOPCIFamily(2.9)[BE052F4D-9B80-3FCD-B36D-BACB7DEE0DF2]@0xffffff7f90931000->0xffffff7f90969fff

BSD process name corresponding to current thread: kernel_task
Boot args: -v keepsyms=1 debug=0x100 alcid=28 npci=0x2000

Mac OS version:
19F101

Kernel version:
Darwin Kernel Version 19.5.0: Tue May 26 20:41:44 PDT 2020; root:xnu-6153.121.2~2/RELEASE_X86_64
Kernel UUID: 54F1A78D-6F41-32BD-BFED-4381F9F6E2EF
Kernel slide:     0x000000000fc00000
Kernel text base: 0xffffff800fe00000
__HIB  text base: 0xffffff800fd00000
System model name: Macmini8,1 (Mac-XXXXXXXXXXXXXXX)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 991308741800

Could be related to USB since everything TB has to go through UPSB, so perhaps we could improve the THUNDERBOLT-SSDT? I don't know if you guys are using the one I posted? We could give it a go.

 

[zavrus]

Hello guys, finally we have a solution to H_EC and AppleACPIEC loading! Thanks to a user from the OC dev forum we managed to come with the correct patch and SSDT for our NUC10!

Wow, really great news! I confirm it works! Much appreciation, thank you and everybody involved.

I don't know if you guys are using the one I posted?

Sure, I use it since you posted (before I tried SSDT-TB3HP.aml from here )

Update: I have just tried the following:
1. Disabled your SSDT-NUC10-THUNDERBOLT-DRENAN.aml and enabled SSDT-TB3HP.aml - sleep behaviour is the same
2. Disabled both - sleep behaviour is the same, but these TB3 devices is now shown as on pictures (identified as ExpressCard)



As for making SSDT tables I am not an expert at all here, so unfortunately I am of no help

 

[dolgarrenan]

Wow, really great news! I confirm it works! Much appreciation, thank you and everybody involved.

You welcome!

Update: I have just tried the following:
1. Disabled your SSDT-NUC10-THUNDERBOLT-DRENAN.aml and enabled SSDT-TB3HP.aml - sleep behaviour is the same
2. Disabled both - sleep behaviour is the same, but these TB3 devices is now shown as on pictures (identified as ExpressCard)

That's a normal behaviour, the system doesn't really know what it is or what devices should be making calls to, so that's alright.

I will try to check TB SSDT again, I might be missing something USB related, perhaps power table..

 

[Leesureone]

You welcome!

That's a normal behaviour, the system doesn't really know what it is or what devices should be making calls to, so that's alright.

I will try to check TB SSDT again, I might be missing something USB related, perhaps power table..

Thats awesome, I'll add the patch and change out the SSDT. I too found the Thunderbolt SSDT is not playing well with OS X, its causing the system to panic and lock up. For the time being I edited out and waiting to see if sleep/wake is working better.

 

[svandive]

Thats awesome, I'll add the patch and change out the SSDT. I too found the Thunderbolt SSDT is not playing well with OS X, its causing the system to panic and lock up. For the time being I edited out and waiting to see if sleep/wake is working better.

Okay just getting caught up here.

1: I can confirm that @Leesureone EFI does allow my system to sleep and wake and be fully operational. I'm working on isolating what in this EFI is allowing this behavior. @Leesureone you don't happen to know what difference between your EFI and my EFI is allowing the Sleep/Wake?

2: @dolgarrenan fantastic work and I am so excited for the updates. I'm going to give them a try right now!!

UPDATE: @dolgarrenan Works Fantastic!!! Totally appreciate your perseverance on this EC issue.

 

[bluejaye]

Could you guys share the latest EFI please

 

[Leesureone]

Okay just getting caught up here.

1: I can confirm that @Leesureone EFI does allow my system to sleep and wake and be fully operational. I'm working on isolating what in this EFI is allowing this behavior. @Leesureone you don't happen to know what difference between your EFI and my EFI is allowing the Sleep/Wake?

2: @dolgarrenan fantastic work and I am so excited for the updates. I'm going to give them a try right now!!

Will report back soon!!

The main difference is how the USB ports are configured, sleep/wake issues generally are. If you eliminate the Thunderbolt.ssdt it will work even better, with it I was still getting lock ups.

 

[svandive]

Wow, really great news! I confirm it works! Much appreciation, thank you and everybody involved.


Sure, I use it since you posted (before I tried SSDT-TB3HP.aml from here )

Update: I have just tried the following:
1. Disabled your SSDT-NUC10-THUNDERBOLT-DRENAN.aml and enabled SSDT-TB3HP.aml - sleep behaviour is the same
2. Disabled both - sleep behaviour is the same, but these TB3 devices is now shown as on pictures (identified as ExpressCard)
View attachment 476677
View attachment 476678

As for making SSDT tables I am not an expert at all here, so unfortunately I am of no help

@zavrus Did you manually add in the entries you picking up in System Report--> PCI for the Audio and Gigabit Ethernet? Or are those being picked dup automatically? I'm guessing you added them.