[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[vicantu]

Yes you’re right.

I am out of the house right now but try the following:

Open the SSDT in MaciASL and find _INI. Then change it to PINI and save the file. Reboot.

Didn't work, I tried all types of boot, any suggestions? thanks Bro

 

[NCMacGuy]

@vicantu @NCMacGuy

Please try the attached SSDTs:

• NUC 7 (Hades Canyon?)
  • Rename RP01:_INI to RP01:XINI
  • Rename _E20 to XE20
  • Use file: SSDT-TbtOnPCH-NUC-7-OSY86.aml
• NUC 8 (Bean Canyon)
  • Rename RP05:_INI to RP05:XINI
  • Rename _E40 to XE40
  • Use file: SSDT-TbtOnPCH-NUC-8-OSY86.aml

@CaseySJ

First - thanks for spending so much time trying to develop an SSDT for my unpatched NUC7i7. I don't know how you do things like this and keep up with all the activity on this thread! Are you a real person or a highly sophisticated artificial intelligence computer behind the CaseySJ moniker?

I agree it's time to pull the plug on your work on this. I had hoped it would be like some of the other recent SSDTs you had written.

I have another NUC 7 that I had flashed some weeks ago. Unfortunately the NUC 7 has to be completely disassembled to get to the TB3 chip. I was hoping the TB3 bus could be activated via an SSDT to avoid disassembly. I'm a hobbyist so these NUCs are not critical to me and are not worth further effort by you.

When I flashed my first NUC 7 there was no TB firmware for it in your repository. So I had to decide whether to try the NUC 8 firmware, or the GC-Alpine Ridge AIC firmware? I perhaps unwisely decided to try the GC-AR AIC firmware (GC-ALPINE-RIDGE-NVM21-V3-NATA.bin) knowing I could back out and try something else if it didn't work.

This firmware displays the System Info TB3 bus on boot, consistently displays whether my TB3 drive is connected or not, but there is no hot plug. The Finder does not consistently display the TB3 drive. So this is not a good solution for the NUC 7.

I was going to revert back to the original TB3 firmware, but was unable to read the chip again. I've now got a new chip clip to see if that helps to re-flash the chip.

Would you suggest I just revert back to Intel's original firmware on my flashed NUC 7, or perhaps try to find an SSDT that would work with the current flashed firmware?

Could you suggest good references for learning how to write/modify SSDTs?

Thanks again for your fantastic support!

P.S. I don't know what Intel's code name for the NUC 7 is, but I think "Hades Canyon" was one of two versions of the NUC 8.

 

[vicantu]

Didn't work, I tried all types of boot, any suggestions? thanks Bro

Hi @CaseySJ I don't know if this is relevant, but on my other untoched and unflashed NUC I have this:

I don't know if you can review SSDT-TYPC-NUC8-BC.aml and SSDT-NUC8-BC.aml attached, with these files ( I suspect just with SSDT-TYPC-NUC8-BC.aml) partial TB3 functionality is achieved:

Fix USB-C hotplugging on bean canyon NUCs by Rashed97 · Pull Request #5 · RehabMan/Intel-NUC-DSDT-Patch

github.com

No matter the kind of boot I make, every single time I can hot plug my eGPU:

unplug it :

Re- hot-plug it, etc:

In System Information this is what appears:

No tree, no bus and no eject button appears on the top bar, but the system works until sleep....

The problem is that as soon as sleep starts, my computer reboots instantly.

I wish I would have a better understanding of how this work to be more helpful, but I think maybe you could evaluate if there are something that gives you a hint on the SSDT-TYPC-NUC8-BC.aml that helps your patch works on this Bean Canyon NUCs.

Thank you Bro.

 

[WhosMac]

Please try attached config.plist after copying serial number back into SMBIOS. If this still gives ++++++ on boot, a CMOS Reset might be needed. This will also reset BIOS parameters to factory defaults and it may re-lock MSR 0xE2 so both BIOS and MSR will have to be adjusted again.

@CaseySJ Using the config.plist you sent over worked to get me past the +++++ and booted up the system.
May I ask what was it that was modified? Thru in my Serial number and boom booted right up used verbose just to track if there was an issue.

 

[CaseySJ]

@CaseySJ Using the config.plist you sent over worked to get me past the +++++ and booted up the system.
May I ask what was it that was modified? Thru in my Serial number and boom booted right up used verbose just to track if there was an issue.

Because you're running Mojave, there are Hackintosh kexts installed in /Library/Extensions. So it is necessary in Clover Configurator --> System Parameters to set Kext Inject to Detect. This was set to Yes, which has the effect of injecting kexts from CLOVER/kexts/Other even if those kexts are already in /Library/Extensions. That's not a good thing.

 

[CaseySJ]

@NCMacGuy @vicantu

Alas we tried, but I agree for now we should park this... alongside all those shiny jets.

 

[CaseySJ]

Hi @CaseySJ I don't know if this is relevant, but on my other untoched and unflashed NUC I have this:

I don't know if you can review SSDT-TYPC-NUC8-BC.aml and SSDT-NUC8-BC.aml attached, with these files ( I suspect just with SSDT-TYPC-NUC8-BC.aml) partial TB3 functionality is achieved:
...

That is actually a Thunderbolt SSDT. To try out the one I provided, this file will have to be removed.

 

[vicantu]

That is actually a Thunderbolt SSDT. To try out the one I provided, this file will have to be removed.

Yes, all the tests with your files were done on one of my unflashed NUC8 without this file following all your instructions.

 

[vicantu]

@NCMacGuy @vicantu

Alas we tried, but I agree for now we should park this... alongside all those shiny jets.

Thank you!!

 

[WhosMac]

Because you're running Mojave, there are Hackintosh kexts installed in /Library/Extensions. So it is necessary in Clover Configurator --> System Parameters to set Kext Inject to Detect. This was set to Yes, which has the effect of injecting kexts from CLOVER/kexts/Other even if those kexts are already in /Library/Extensions. That's not a good thing.

Would the same be true if I was on Catalina, both my drives are on 10.15.3
I did notice some changes that had been made to the ACPI in comparison to my EFI on my main drive.
I think they had been modifications when changing audio layout as well.

Also Thank You again for the save and helping keep me running lol