Contribute
Register

Intel NUC 10 Frost Canyon

bmillzthedefector said:
New subtopic- Has anyone had success getting windows up and running as well? I have the FNH- 10.14.6 on the m.2 and trying to get the 2.5" slot with 1/2 windows and 1/2 additional storage for macOS.

Windows is not recognizing the network card! I tried rocking different versions of bootcamp drivers or no boot camp drivers, no dice there. I friggin hate windows tbh, but I need it for work sometimes....
Click to expand...
Same experience for me as the other guys but for the first time ever I'm sharing an 1 TB Evo Plus NVMe drive and I'm actually happy with it. I've set up dual boot on the same drive before with Clover but it was always a source of endless frustration.
Have you run the windows media creation tool recently and copied the Intel drivers into a seperate folder?? I had to install the network card dri rr but then windows update found everything else if I remember correctly.
 
Last edited:
zavrus said:
Well, will reply to myself ;)
If I disable any of those SSDTs then I don't see an error, so yes - the error is caused by doubled code
At the same time I don't want to disable SSDT-SBUS-MCHC because otherwise com.apple.driver.AppleSMBusPCI isn't loading to SBUS (below is how it should be according to this guide):
View attachment 476943

So the question is what option to prefer:
  1. Delete Method (DTGP, 5, NotSerialized) from SSDT-SBUS-MCHC and keep both SSDTs to be loaded
  2. Delete SSDT-DTPG (as it consists of this code only)
But I am in doubts regarding the different DefinitionBlock naming - does it have a sense?
Please advise.

PS: by the way, while I was checking my SSDTs I found an error in my SSDT-SBUS-MCHC:
was
Code: 
External (_SB_.PCI0.SBUS, DeviceObj)
needed to be
Code: 
External (_SB_.PCI0.SBUS.BUS0, DeviceObj)


UPDATE: I deleted Method (DTGP, 5, NotSerialized) from SSDT-SBUS-MCHC and kept it in SSDT-DTPG - looks like it's OK
View attachment 476953
Resulting amls are attached.
Click to expand...
I'm going to need to read through this one more time to get it all but thank you for the awesome find... and great focus to detail in spotting this..
 
zavrus said:
dolgarrenan, would you please look at this photo taken in the beginning of boot process when ACPI tables are being loaded:
View attachment 476934

It seems SSDT-DTPG.aml loads with error that I don't know what means.
Can it be related to wake or some other issue ?

UPDATE: I see this code
Code: 
    Method (DTGP, 5, NotSerialized)
    {
        If ((Arg0 == ToUUID ("a0b5b7c6-1318-441c-b0c9-fe695eaf949b")))
        {
            If ((Arg1 == One))
            {
                If ((Arg2 == Zero))
                {
                    Arg4 = Buffer (One)
                        {
                             0x03                                             // .
                        }
                    Return (One)
                }

                If ((Arg2 == One))
                {
                    Return (One)
                }
            }
        }

        Arg4 = Buffer (One)
            {
                 0x00                                             // .
            }
        Return (Zero)
    }
in SSDT-DTPG.aml and SSDT-SBUS-MCHC.aml but in different DefinitionBlock sections - is this a reason of error?

SSDT-DTPG.aml has:
Code: 
DefinitionBlock ("", "SSDT", 2, "KGP ", "DTPG", 0x00001000)
while SSDT-SBUS-MCHC.aml has:
Code: 
DefinitionBlock ("", "SSDT", 2, "ACDT", "MCHCSBUS", 0x00000000)
Click to expand...
I'd say the system is comparing tables with on board DSDT and is finding the same devices, I do get some of these too, but I have not experienced any issues, are you getting a KP on boot?
 
bmillzthedefector said:
New subtopic- Has anyone had success getting windows up and running as well? I have the FNH- 10.14.6 on the m.2 and trying to get the 2.5" slot with 1/2 windows and 1/2 additional storage for macOS.

Windows is not recognizing the network card! I tried rocking different versions of bootcamp drivers or no boot camp drivers, no dice there. I friggin hate windows tbh, but I need it for work sometimes....
Click to expand...
I don't see why would you try to load bootcamp drivers..? Your internal Ethernet card is fully compatible with Windows, you don't need to port drivers over from mac. Just look for drivers in the Intel NUC site, if not just look for the specific chipset drivers. Intel I219-V
 
zavrus said:
Well, will reply to myself ;)
If I disable any of those SSDTs then I don't see an error, so yes - the error is caused by doubled code
At the same time I don't want to disable SSDT-SBUS-MCHC because otherwise com.apple.driver.AppleSMBusPCI isn't loading to SBUS (below is how it should be according to this guide):
View attachment 476943

So the question is what option to prefer:
  1. Delete Method (DTGP, 5, NotSerialized) from SSDT-SBUS-MCHC and keep both SSDTs to be loaded
  2. Delete SSDT-DTPG (as it consists of this code only)
But I am in doubts regarding the different DefinitionBlock naming - does it have a sense?
Please advise.

PS: by the way, while I was checking my SSDTs I found an error in my SSDT-SBUS-MCHC:
was
Code: 
External (_SB_.PCI0.SBUS, DeviceObj)
needed to be
Code: 
External (_SB_.PCI0.SBUS.BUS0, DeviceObj)


UPDATE: I deleted Method (DTGP, 5, NotSerialized) from SSDT-SBUS-MCHC and kept it in SSDT-DTPG - looks like it's OK
View attachment 476953
Resulting amls are attached.
Click to expand...
That is a great self fix! We need DTGP method in order to load certain tables like SSDT-THUNDERBOLT, which calls to DTGP MethodObj. Tables could be compiled without it as someone very wise once said, but if I'm honest, even Apple uses MethodObj DTGP in their tables, it all over the system.

We haven't had the chance to make this post a "how to", so perhaps we should try to create a compilation of what is working and make a complete sort of post in this very same post.

What else is there that needs to be fixed so far?
 
this is my minimal "last known good" working efi ... without the need to unlock the BIOS (current release 41)
 

Attachments

  • minimal_without_unlocked_cfg-lock.zip
    870.1 KB · Views: 97
daTscharlie said:
this is my minimal "last known good" working efi ... without the need to unlock the BIOS (current release 41)
Click to expand...
I would suggest unlocking BIOS, otherwise your system can't write to MSR_Register which is needed to have a properly working NVRAM in the end, that's how real macs work.
 
dolgarrenan said:
are you getting a KP on boot?
Click to expand...
Nope... Just noticed an error that lead to above mentioned fix

dolgarrenan said:
We need DTGP method in order to load certain tables like SSDT-THUNDERBOLT, which calls to DTGP MethodObj. Tables could be compiled without it as someone very wise once said, but if I'm honest, even Apple uses MethodObj DTGP in their tables, it all over the system.
Click to expand...
I googled quite a lot on that DTGP and I also found that Apple uses it widely, and I think it doesn't matter what DefinitionBlock declares this Method - the aim is that method must be declared.

dolgarrenan said:
What else is there that needs to be fixed so far?
Click to expand...
As for me, then I have two main issues - no wake up and sound with AppleALC (Voodoo I remind works).
For second one I advanced a bit with PinConfigurations for Codec but now the problem is that I can't test PinConfiguration because for some reason AppleALC doesn't patch AppleHDA as it's supposed. I feel I am close to the point and I need just a little help :banghead:. But there is silence on this topic here (in Audio section) as well as on InsanelyMac.

Plus we all expect you will get a luck to finish TB3 power settings :)
 
Last edited:
zavrus said:
Nope... Just noticed an error that lead to above mentioned fix


I googled quite a lot on that DTGP and I also found that Apple uses it widely, and I think it doesn't matter what DefinitionBlock declares this Method - the aim is that method must be declared.
Click to expand...
back in the "old days" before dynamic dsdt patching/fixing, we used to be required to add method DTGP to the beginning of our DSDT. so I agree it doesn't matter where the method is defined as long as it is defined.
 
dolgarrenan said:
That is a great self fix! We need DTGP method in order to load certain tables like SSDT-THUNDERBOLT, which calls to DTGP MethodObj. Tables could be compiled without it as someone very wise once said, but if I'm honest, even Apple uses MethodObj DTGP in their tables, it all over the system.

We haven't had the chance to make this post a "how to", so perhaps we should try to create a compilation of what is working and make a complete sort of post in this very same post.

What else is there that needs to be fixed so far?
Click to expand...
An oddity that I am trying to look in to is this:

1592564866786.png


Here you can see in Hackintool the WiFi (AX201) issuing reported as an AC-9462. Even the Device ID is being reported as 0x02F0. I believe this is why I'm not getting any response from the Wireless Drivers by zxystd.

I know several people have said they don't really care about having the Wireless working, but in my view this is a very PC centric attitude. If you have a real Mac and use Apple products you know that having the Bluetooth and Wireless working is extremely part of the beauty of Mac for the holistic ecosystem. Once you get used to working on a Mac with the whole ecosystem up and operating you can truly see the beauty in what it means to use OS X.

Anyway I've checked windows and the proper AX201 driver is loaded. So something else is happening here.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top