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

[CaseySJ]

Casey, when upgrading to Catalina does it really say Boot macOS... ... from Mojave... ?
Just curious -

That example assumes that under Mojave, the user set the name of the macOS SSD to Mojave. The build guide in Post #1 suggests giving it this name.

So when we begin the Catalina upgrade from Mojave, the name of the SSD will still be "Mojave". So that's the name you'll see in Clover Boot Menu.

 

[LeftHandMedia]

If you're installing Mojave, please follow the main guide in Post #1. No shortcuts! For Catalina, we can follow the streamlined mini-guide (link is at the top of Post #1).

You may also compress and upload the CLOVER folder from EFI partition of the USB install disk.

Wait I'm lost.

1. Yes I'm installing Mojave.
2. I followed the guide to a "T" the first time.
3. Last night when I used a brand new USB stick, I followed the guide all the way until it got to the point where I was supposed to follow the guide for setting the config.plist I didn't do that because you sent me a new CLOVER file to use. I thought this would allow me to start anew. However, I had all of the drive options still on there. It did not look like the first attempt to install.

Just trying to confirm that I do NOT need to go through the config.plist setup because you made changes and sent me an updated one. And if I'm not, what would be my next steps?

Thanks

 

[CaseySJ]

Wait I'm lost.
...

That's why it's important to be specific because I never sent you a CLOVER file or folder. I only asked you to try removing the -v flag.

Regardless, please compress and upload the CLOVER folder from EFI partition of your USB install disk.

 

[LeftHandMedia]

That's why it's important to be specific because I never sent you a CLOVER file or folder. I only asked you to try removing the -v flag.

Regardless, please compress and upload the CLOVER folder from EFI partition of your USB install disk.

This wasn't a new CLOVER folder?? I know you're working with a bunch of people. I bet it gets confusing!

 

[trouble74]

• So the progress bar hangs during startup -- this is what I wanted to check. If the screen went blank, that would be a different issue.
• Your experience also shows that agdomod=pikera is necessary.

What you're doing now is the right approach. Namely, detaching all unnecessary devices and paring it down to the bare essentials. Hackintoshing often requires this type of trial and error. Anyone not willing or able to do what you're doing should head over to an Apple Store and buy one off the shelf.

Note, however, that on-board HDMI will be deactivated once the macOS driver attaches to it during the late boot stage. You'll then get a blank screen. It is better to instead use a USB-C to DisplayPort cable connected to either of the two Thunderbolt/USB-C ports on the rear IO panel. We can also activate the on-board HDMI port by following Injecting Audio and Enabling On-Board HDMI.

OK, here is where I stand. I made the new usb installer. Back to square 1. No devices inside machine except for the SSD. I attached a USB-C hub to the back with HDMI out on it. If the HDMI is connected to the hub or the motherboard I get a boot loop. I see all the information running and then it gets real fast and reboots to the Gigabyte logo. Any suggestions please and thanks for the help. Also, I used the hub to compensate for the fact I do not have a Thunderbolt to DisplayPort only the hub with HDMI out. Either way I got the same result from both...the reboot.

 

[thegubatoshchamp]

`

 

[CaseySJ]

This wasn't a new CLOVER folder?? I know you're working with a bunch of people. I bet it gets confusing!

Yes you're right. I have to multitask between a lot of different people's scenarios.

Anyway, at this point I'm not sure what else to suggest. The build guide in Post #1 has been used successfully time and time again. After 10,000 posts in this thread, there's rarely some new phenomenon with regard to Mojave.

Hackintoshing often involves a willingness to experiment on one's own and to search this thread and other threads for problems.

 

[CaseySJ]

OK, here is where I stand. I made the new usb installer. Back to square 1. No devices inside machine except for the SSD. I attached a USB-C hub to the back with HDMI out on it. If the HDMI is connected to the hub or the motherboard I get a boot loop. I see all the information running and then it gets real fast and reboots to the Gigabyte logo. Any suggestions please and thanks for the help. Also, I used the hub to compensate for the fact I do not have a Thunderbolt to DisplayPort only the hub with HDMI out. Either way I got the same result from both...the reboot.

• Double check all BIOS parameters. They are listed in Post #1 (settings for Catalina are the same as for Mojave).
• Set Initial Display Output to IGFX because there's no discrete AMD GPU now.
• Avoid the USB-C hub. It adds an extra layer of complexity.
• To use HDMI port on motherboard, you must add the HDMI connector patch described in the spoiler.

 

[Zip1]

This wasn't a new CLOVER folder?? I know you're working with a bunch of people. I bet it gets confusing!

I might have some suggestions -
First remove ALL hard drives except desired Mac drive, ALL PCI devices except the graphics card, ALL RAM except one card left in slot #1, ALL USB devices except boot drive and keyboard/mouse, ALL USB header cables - we want a bare-bones system.

Carefully confirm all BIOS custom settings

Try the attached installer EFI. This is a little more bare-bones than your previous, but based completely on post #1 parameters. This is the EFI I used on my recent rebuild of my system.

If this still doesn't work, see if you can borrow a true 1920x1080 computer monitor just for the install.
If this DOES work, it's because you didn't follow post #1 carefully enough...

 

[Schlinnster]

Ever since updating my system to 10.15.1 my Finder app crashes after a bit, reliably. When that happens, I'm unable to shut the computer down and I have to press the physical reset button. What could this be? I also changed the system definition to iMacPro1,1 because I wanted to see if that speeds up FCPX, which it seems to do.