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

[JoanSilva17]

@CaseySJ
Hi Casey !, First of all I am grateful for all your work that you offer us. I would like to know what I am doing wrong ...
Yesterday I bought on ebay my TR Flashed for Mac pro & Hackintosh. Plug it into slot 4 and with the THBC header. The bios recognizes the board, but if I turn on the hack with something connected, it gets stuck on startup ... In order to boot and view the information on PCI & Thunderbolt Bus, I must connect a device on the bios screen and sometimes it boots and sometimes not. I put an ssdt that makes me see the card in pci as "Alpine Ridge" I can modify it so that Titan Ridge appears, but it is cosmetic isn't it?
Anyway, I hope and need your help! Sometimes I get frustrated!

 

[CaseySJ]

Hello CaseySJ,
Before I start - this is my first post here, I was so happy to see this Golden Build, as I had bought such similar Hardware - though with my RX570, I am more "iMac19,2.
I followed your Build completely - and was up and running in no time - incredibly Happy! My UAD Apollo Twin mkII was 100%. However I somehow missed the last part on Backing up (the EFI). So I did a Restore from My CCC of an earlier setup (application wise, and of course - no Boot. So - Started again - but this time no joy. not anything, 10 days. Can NOT get to the install/Format stage. I have tried so much, here is a brief list:
Reformatted my Hackintosh SSD to the original EXFAT.
Tried FakeSmc and SMCHelper-64.efi (after a "VirtualSMC is broken" message) Did NOT have both Virtual and Fake at same time.
tried earlier version of Clover Configurator (as was my first success - 5.9.3 perhaps.) because things (apps) changed from first boot.
Nothing. My screen freezes have all been different but here is the latest:
Thank you for such a great Build. It was SUPERB when it ran. It's simply an I/O error. (Idiot Operator Error).
Also - pleas advise if this should be posted elsewhere.

Hello @Togril,

Welcome to the forum!

I assume you're installing Mojave. Do you still have the USB install disk from the earlier successful installation of Mojave? If so, boot from that disk by pressing F12 at BIOS splash screen to invoke the BIOS Boot Menu and selecting the USB disk.

When Clover Boot Menu appears, choose the USB flash disk (usually the icon on the far left of the Clover menu). When macOS installer starts, format the internal macOS SSD as:

• Name: Mojave
• Format: APFS (not ExFAT)
• Scheme: GUID Partition Map

Then continue with Mojave installation.

 

[CaseySJ]

@CaseySJ
Hi Casey !, First of all I am grateful for all your work that you offer us. I would like to know what I am doing wrong ...
Yesterday I bought on ebay my TR Flashed for Mac pro & Hackintosh. Plug it into slot 4 and with the THBC header. The bios recognizes the board, but if I turn on the hack with something connected, it gets stuck on startup ... In order to boot and view the information on PCI & Thunderbolt Bus, I must connect a device on the bios screen and sometimes it boots and sometimes not. I put an ssdt that makes me see the card in pci as "Alpine Ridge" I can modify it so that Titan Ridge appears, but it is cosmetic isn't it?
Anyway, I hope and need your help! Sometimes I get frustrated!

Hello @JoanSilva17,

To address the boot-related issues please try:

• CMOS Reset. Simply follow the procedure in your motherboard's manual. BIOS parameters will need to be re-configured afterwards. CMOS Reset is often the single best "detoxifier" for the firmware (BIOS).
• After configuring BIOS, grab screenshots of all the Thunderbolt parameters. If you insert a USB flash disk that has an EFI partition (such as your USB install disk), you can press F12 to capture screenshots in BIOS. Screenshots will be saved in the EFI partition of the USB flash disk, in BMP format. We can convert BMP to JPEG (I believe Preview can do this; open the BMP file and select File --> Export...).

To address SSDT please have a look at the post below and try Option 1 to generate a new SSDT:

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

@CaseySJ @Elias64Fr Could we dump the nvmem of the Thunderbolt controller using Linux from /sys/bus/thunderbolt/devices/0-0/nvm_active0/nvmem, patch the 7 bytes if applicable, and then do host NVM upgrade using these instructions? Here's the nvmem file I have dumped, it's 516,096 bytes, I'm not...

www.tonymacx86.com

 

[PTuser]

Hi @CaseySJ
Some developments - In addition to my main Hackintosh I have a Mac Mini with Thunderbolt 2 running Mojave. Using a TB3 to TB2 adapter I was able to successfully test the RedLine16 which told me that 1) the Thunderbolt connection on the unit works fine, and 2) I have taken some screenshots of what IOreg sees when its working. There are a lot of similarities between the two but also some differences. Surprisingly in the aged Mac Mini the firmware version is higher although this is TB2 not 3. I don't know if that is important. The reg is different in IO reg as its the pciedebug and assigned address. Not sure what this means but if these can be adjusted I may be able to succeed. I don't know enough really so looking for advice....3rd August is Titan Ridge -

 

[egroys]

Hi everyone,

I made a second Catalina drive to ease the transition from Mojave. I had issues logging into my iCloud this morning. It kept throwing errors.
"Unable to sign in because of a problem communicating with iCloud."

And now, I went back to my Mojave drive, I am having similar issues. I am going to try to log out completely but I was curious if anyone has any experience or tips with this? The EFI is the same (clover) and so is the serial number, etc.

Edit: Now I get the same error trying to log into icloud.com via the web!!

Does this mean I may need a new serial number?

Thank you in advance!

 

[oopsmybad]

Glad to hear it! Are both of your Ethernet ports showing in “System Information —> Ethernet Cards”?

I think I figured out my missing Ethernet problem.

For some reason, the Mausi driver version 2.5.1d1 doesn't work when injected specifically into Mojave 10.14.6 (with all the latest security patches). If I use the 1.0.2 version of the Mausi driver, the interface shows up properly in Mojave. This was reproducible for me with both OpenCore and Clover.

I've been using your patches/drivers/kexts included in the "May 2020 Update - Catalina 10.15.4 Fresh Install" (injecting everything for both Mojave and Catalina in a vanilla-type way). This has worked beautifully for both versions of MacOS. I just didn't realize that Mausi driver in your OpenCore EFIs is different from the one included in the May 2020 Update bundle. (And I probably remember earlier versions of OpenCore+2.5.1d1 working because i was looking in Catalina, where both the 2.5.1d1 and 1.0.2 Mausi drivers work for me.)

Maybe this observation will be helpful to someone else stuck in the (Mojave 32bit-land) past!

 

[vovkinson]

I'm curious about this too. Want to update from OC 0.5.9 to OC 0.6.0 wondering if I'll need to generate a new S/N.

Hi everyone,

I made a second Catalina drive to ease the transition from Mojave. I had issues logging into my iCloud this morning. It kept throwing errors.
"Unable to sign in because of a problem communicating with iCloud."

And now, I went back to my Mojave drive, I am having similar issues. I am going to try to log out completely but I was curious if anyone has any experience or tips with this? The EFI is the same (clover) and so is the serial number, etc.

Edit: Now I get the same error trying to log into icloud.com via the web!!

Does this mean I may need a new serial number?

Thank you in advance!

 

[CaseySJ]

I'm curious about this too. Want to update from OC 0.5.9 to OC 0.6.0 wondering if I'll need to generate a new S/N.

A new serial number is definitely not needed for this update.

 

[CaseySJ]

Hi everyone,

I made a second Catalina drive to ease the transition from Mojave. I had issues logging into my iCloud this morning. It kept throwing errors.
"Unable to sign in because of a problem communicating with iCloud."

And now, I went back to my Mojave drive, I am having similar issues. I am going to try to log out completely but I was curious if anyone has any experience or tips with this? The EFI is the same (clover) and so is the serial number, etc.

Edit: Now I get the same error trying to log into icloud.com via the web!!

Does this mean I may need a new serial number?

Thank you in advance!

Please do two things:

• Reset NVRAM from the OpenCore Picker Menu
• Check your serial number on Apple's website (click here). If the result comes back as:

We’re sorry, but this serial number isn’t valid. Please check your information and try again.

... then your serial number is OKAY. It means no one else is using it. Otherwise you will need to change the number.

 

[CaseySJ]

I think I figured out my missing Ethernet problem.

For some reason, the Mausi driver version 2.5.1d1 doesn't work when injected specifically into Mojave 10.14.6 (with all the latest security patches). If I use the 1.0.2 version of the Mausi driver, the interface shows up properly in Mojave. This was reproducible for me with both OpenCore and Clover.

I've been using your patches/drivers/kexts included in the "May 2020 Update - Catalina 10.15.4 Fresh Install" (injecting everything for both Mojave and Catalina in a vanilla-type way). This has worked beautifully for both versions of MacOS. I just didn't realize that Mausi driver in your OpenCore EFIs is different from the one included in the May 2020 Update bundle. (And I probably remember earlier versions of OpenCore+2.5.1d1 working because i was looking in Catalina, where both the 2.5.1d1 and 1.0.2 Mausi drivers work for me.)

Maybe this observation will be helpful to someone else stuck in the (Mojave 32bit-land) past!

I've added the following note to the OC 0.6.0 Guide: