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

[MuffinCrumbs]

Thanks,
I remember we already met in a German discord some month ago. (OpenCore 0.3 was the newest version that time.)
I tried 2-3 evenings already even with help... I'm not able to get past the memory trouble...
I just blindly tried your EFI folder, and it didn't work too.
Maybe we have different BIOS versions or configurations. But I don't get OpenCore working. Clover runs pretty stable. But I wan t to get rid of the bad 2000 fix, and I like the adventure,

Did you update to OpenCore 0.5.3 already? Do you mind sharing aa updated EFI folder, and maybe a BIOS setting export?
My explanation is that it runs on yourr board that you have rainbow unicorn version of the Designare.

I've never been on German Hackintosh Discord. But if there is such thing, I'll try to find it. Sounds fun.

I am not the only one with OpenCore running here. There are a few of us here in this thread.

I don't run 0.5.3, as I only get OpenCore from the release section. So far, 0.5.2 is the latest from the release section. Getting OpenCore from the release section is way better than getting an early later version compiled. In my opinion.

If you somehow get the memory allocation issues, then that is a common issue for the entire setup. And can even change when you do a UEFI fw update.

If you somehow get to use the OpenCore folder I last uploaded here, you could change it. Amend to it, for your own liking.

-I've turned off show-picker, you can turn it on.
-I've changed boot entry policy, you can change it to your own liking.
-You can check the booter section, perhaps you need something more, or something less.
-I don't need to emulate NVRAM, so far. You might need to.

The thing is, it is not really that difficult to run OpenCore and boot macOS with this board. Tbh, no offense. It seems like you're out after OpenCore-EFI folders. Yet you say you like the adventure. The proper adventure is to have trials and tribulations, fail and pass. This is done through reading the documentation, finding out why you get problems, why you can't boot in and so on. As I said earlier, there is no special thread in specific to OpenCore and Z390 Designare, where you'll get a good extensive help support. So far CaseySJ's thread is the only dedicated thread, and it is not for OpenCore, well not at the moment, if ever. There are probably reasons to it, a big reason is that OpenCore is public beta.

I hope you find your adventure well.

 

[hyperx136]

So Gigabyte just released F8 Firmware update for Z390 Designare on 10/28. Just curious if anybody updated to it and is everything still working fine? The description said BIOS Structure refresh and Optimize for the i9-9900KS.

 

[CaseySJ]

So Gigabyte just released F8 Firmware update for z390 Designare on 10/28. Just curious if anybody updated to it and is everything still working fine? The description said BIOS Structure refresh and Optimize for the i9-9900KS.

Yes it’s a cool blue new version and working well.

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

So I updated to Catalina this evening and began to do the initial tests :) I noticed that my USB drives are no longer getting ejected after sleep! Can anyone else confirm or deny this behavior? I've tested various USB ports and various sleep lengths, as soon as I wake the system, the drives are...

www.tonymacx86.com

 

[CaseySJ]

Although I thought I followed your guide 100% completely, I realized the other day that I made a couple of errors. Some were easy fixes - like I had two different versions of WEG in Clover and /L/E, both of them being old. I updated both. But I also noticed that I'm running 10.14.6 with the "pro apps" configuration for 10.14.4 - you know, all the config mentioned in the "not recommended for 10.14.5 or later" part of the guide - an SMBIOS of iMac 18,3, the framebuffer patch / Orinoco, etc.

As it stands, everything seems to work great - the iGPU is enabled for compute tasks, VideoProc / VDADecoderChecker shows hardware acceleration for h264/265, my bruceX test with an RX580 blows my mind (8-9 seconds?!?). But I'm wondering if I should bite the bullet and switch to iMac 19,1.

If I decide to do that, should I do everything in your previous (quoted) post, plus -- delete the PCI device (in Devices), null out the Orinoco frame buffer (in Graphics), and run Hackintool to generate the corresponding platform id patch (0x3E980003)?

I'm a little hesitant to poke a sleeping bear, but it's kinda something I'll have to do eventually, probably?

The adage if it ain't broke don't fix it is both a blessing and a curse. Maintaining a working status quo is the wiser decision in circumstances where mission critical uptime is necessary. But if time permits, change can be made in a safe manner if we start with a full bootable backup and proceed with care (i.e. not rush it).

 

[mobi]

This might be remedied with a CMOS Reset. This involves shorting two pins on the motherboard as explained in the Designare user's manual. This will reset BIOS parameters to factory defaults, so the parameters will have to be configured once again before booting macOS.

I did the CMOS reset, but the next day I booted the "scan entries" blues showed again

 

[CaseySJ]

I did the CMOS reset, but the next day I booted the "scan entries" blues showed again

Some other things to check:

• Is firmware version still F6, F7, or F8 (i.e. it has not reverted back to F3)?
• In Clover Configurator --> Boot section, is the Debug flag checked OFF?
  
• Can you grab a screenshot of the BIOS boot menu (F12 at BIOS splash screen)?
  • If you insert a USB flash disk prior to starting, you may be able to press F12 (print-screen) within the BIOS Boot Menu to capture a screenshot to the USB disk.
• Reflashing the BIOS is another option.

 

[mobi]

Some other things to check:

• Is firmware version still F6, F7, or F8 (i.e. it has not reverted back to F3)?
• In Clover Configurator --> Boot section, is the Debug flag checked OFF?
  View attachment 434967
• Can you grab a screenshot of the BIOS boot menu (F12 at BIOS splash screen)?
  • If you insert a USB flash disk prior to starting, you may be able to press F12 (print-screen) within the BIOS Boot Menu to capture a screenshot to the USB disk.
• Reflashing the BIOS is another option.

Debug was on!! ,( probably got checked when I was fighintg to get VirtualSMC (any version after 1.06) to work in my system, btw I got that sorted out after experimenting with Bios F8 and going back to F6)

So far in 4 attempts to boot , just the first one after disabling debug got stuck , the others no problem

Thanks a lot @CaseySJ !!

 

[MacMarshall]

Yes it’s a cool blue new version and working well.

Not going to be able to post my new build until this weekend, but I am having a problem that is maybe related to BIOS?

New build, Designare Z390, i7-9700K, 64GB Ballistix Sport LT 3200, Sapphire 580, Samsung Pro NVMe for boot, Fenvi T919. Rev 1.0 board came with F7 and I flashed to F8 before starting build. Seems like everything working OK, but when system sits overnight in the morning I get this boot failure screen, so I guess system is crashing/restarting and then can't figure out how to boot. Also getting this at least sometimes now when powering on after a shutdown.

Boot priorities are OK, and I can get to the Clover screen and then boot into Mojave by selecting the boot drive in Boot Overide, screen shot of that below. So despite fact that the NVMe is at the top of the boot priority list, to get it to go there seems like I have to force it.

Any thoughts on troubleshooting:

a) The instability that is causing the Hack to restart when sitting idle?

b) The problem getting past the boot failure and into Clover? For this maybe I need to load defaults and then set the BIOS up again (I did this on initial setup)? Before that I guess I can go through all of the settings and make sure I didn't miss anything.

Hopefully they are related!

 

[CaseySJ]

...
Any thoughts on troubleshooting:

a) The instability that is causing the Hack to restart when sitting idle?

If Sleep was enabled, and by default it is enabled and set to sleep after 15 minutes, then it's possible that the system crashed once or repeatedly while attempting to sleep. Does sleep (and wake) work when invoked from the Apple menu?

b) The problem getting past the boot failure and into Clover? For this maybe I need to load defaults and then set the BIOS up again (I did this on initial setup)? Before that I guess I can go through all of the settings and make sure I didn't miss anything.

Yes that is definitely the first thing to do.

 

[MacMarshall]

If Sleep was enabled, and by default it is enabled and set to sleep after 15 minutes, then it's possible that the system crashed once or repeatedly while attempting to sleep. Does sleep (and wake) work when invoked from the Apple menu?

Yeah I put into sleep manually from Apple menu item a couple of times and no problem waking system back up.

At work and Hack is at home so can't work on this now, but I don't think there is an explicit sleep setting in System Preferences any more, seems like it is a toggle keying off display sleep setting, "Prevent computer from sleeping automatically when the display is off." I do have that unchecked right now so system should be sleeping after 15 minutes, I think. I guess I can also try forcing system to stay 'awake' overnight and see if that makes a difference. Or putting it to sleep manually and see if it makes it through the night, I s'pose.

Searching the Internet I see a few cases of people having this problem, but at a glance didn't find an answer, just suggestions that possibly a hardware issue (mobo battery or mobo or PSU, my PSU is a new Corsair AX850, so I did not scrimp there) or BIOS problem.

One other person with this problem found that exiting BIOS without saving changes brought the same error screen up, but saving changes and exiting (which is maybe similar to me forcing the boot drive) gave a successful boot (GA-Z170). Which seems kind of strange. A Steve99 on a Gigabyte forum a couple of years ago, I'll have to register there to try to send him a note to see if he ever figured it out.