Contribute
Register

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

Not sure why I wanted to avoid that procedure, but I gave it a try - unfortunately, now the option for unlocking with Apple Watch has disappeared from settings. I also got several 2FA popups on my devices when signing back in to each (iPad, iPhone, computer)... and those codes that it gave were never needed, only the first one. Super weird. Another visual bug occurred when going into settings: View attachment 465921
I subsequently tried removing the Hackintosh from 'my devices' and signing back in, but that didn't change anything. I guess I'll try re-pairing my apple watch to see if that brings it back. But if any of these bugs sound familiar to anybody, please do share.

An update: completely un-paired and re-paired my watch, that got it back to the same old behavior. Unlock works great if I interrupt full sleep, but not upon wakeup. The login screen is clearly waiting on the watch (or something) because it takes a couple seconds for the password box to appear. I also tried switching from 5GHz to 2.4GHz wifi, but no change there. Idk, @CaseySJ I feel like it must be a problem with how the machine is waking up.
 
Yes, but it's the same. Must be some bios setting or hardware difference. What Radeon VII do you have? Mine it's XFX. Problems brand for Hackintosh. Maybe it's this.
Asrock
 
@CaseySJ

I have one question you might have an answer.
After following your instruction(Mini-Guide for Fresh Installation of Catalina 10.15.4 and Newer),
The hackintool implys there is an error(?) with the power setting. 'hibernationmode=3' and 'proximitywake=1' to be specific. Do I have to or better to change these settings to 'hibernationmode=0' and 'proximitywake=0' as Hackintool suggests?
I haven't set them to 0 myself, but only because my situation (location of the computer and who has access to it) does not require either of them to be disabled.

If you're experiencing unexpected wakes from sleep particularly over long sleep periods then it's a good idea to disable them both, but do so as follows (taken from Sleep Aids guide):

Screen Shot 2020-04-29 at 3.12.36 PM.png
 
Last edited:
Hi all. Just checking in to ask if anyone here with a Vega card, that has followed the RadeonBoost guide and has subsequently seen any noticeable (preferably with some scores/timings) could comment?

I’m seeing whether it’s worth changing my current setup as it’s running wonderfully smooth right now, and don’t want to change anything if all it does is boost benchmarks rather than real-world results.

Thank you!
 
I haven't set them to 0 myself, but only because my situation (location of the computer and who has access to it) does not require either of them to be disabled.

If you're experiencing unexpected wakes from sleep, particularly over long sleep periods, then it's a good idea to disable them both, but do so as follows (taken from Sleep Aids guide):

I read through Sleep Aids Guide (Take Sominex tonight?). Is this only for Designare or will the terminal inputs work for any MB?
 
Hi all. Just checking in to ask if anyone here with a Vega card, that has followed the RadeonBoost guide and has subsequently seen any noticeable (preferably with some scores/timings) could comment?

I’m seeing whether it’s worth changing my current setup as it’s running wonderfully smooth right now, and don’t want to change anything if all it does is boost benchmarks rather than real-world results.

Thank you!
Two Vega 64 benchmarks were added to the Radeon Boost Guide.
 
I read through Sleep Aids Guide (Take Sominex tonight?). Is this only for Designare or will the terminal inputs work for any MB?
The Terminal commands are applicable to all macOS Mojave and Catalina systems. The SSDT / ACPI Patch is for Z390 only.
 
An update: completely un-paired and re-paired my watch, that got it back to the same old behavior. Unlock works great if I interrupt full sleep, but not upon wakeup. The login screen is clearly waiting on the watch (or something) because it takes a couple seconds for the password box to appear. I also tried switching from 5GHz to 2.4GHz wifi, but no change there. Idk, @CaseySJ I feel like it must be a problem with how the machine is waking up.
Today I used Apple Pay on Safari and approved the transaction with my Apple Watch. All of Handoff/Continuity appears to be working nicely at the moment.

Do Messages and FaceTime work?
Does Sidecar work?
 
Today I used Apple Pay on Safari and approved the transaction with my Apple Watch. All of Handoff/Continuity appears to be working nicely at the moment.

Do Messages and FaceTime work?
Does Sidecar work?

Handoff, Continuity Camera, Messages, FaceTime, SideCar, AirPlay, etc. all work perfectly. I also have used the watch for authentication (changing file permissions etc). I decided to try installing my usb 2.0 splitter today (inspired by a recent post) and run 'Clean NVRAM' and 'Reset NVRAM' at the OC bootpicker while I was at it. I also reset the bluetooth module before shutting down for good measure. The result was that unlock worked on the first sleep/wake cycle only. The second cycle failed. I'm seeing that as a recurring theme in posts on the matter. Maybe that is a useful clue as to what is going on?
 
Last edited:
@CaseySJ both NO & YES have been tried and gave the previous results in the JPEGs attached. First photo is NO, second photo are the results of YES.

My bootable backup was giving the same results the other day.

@CaseySJ - hey, just a brief update on where I am now..
It seemed CFG had been reset - probably me!! After much fiddling around, downloading new files and triple checking I've now got a full working up to date Clover (booted without a hitch 1st time) and Opencore EFI's (tried both) backed up on separate USB's. Plus a new CCC of my main drive.

I'm running 0.5.7 OC - all is well.
All Apple FaceTime, iMessage, Handoff etc work, sidecar loads but very old iPad so probably not compatible.
Set 64gb Ram to 2666 for sleep, and sleep works well enough.

The current issues are:
• Dual display, at the moment running one from DP and the other from HDMi both from the RADEON 64
I'll get black screen on load if I don't, won't always turn on from sleep, resolution on BIOS changes etc.
Used to run dual DP ports from Vega and always had some weird issues.
I know there's some discussion in the thread I'll re-read and see what works.
Plus will look at the new RadeonBoost 64 & USBWakefixup methods too, seems promising.

• My UAD Apollo 8 used to run great on the old build, hotplug the works.. however having re-read a few posts and seeing what @smashdownbabylon had mentioned about the audio I realised although I'd been running a stable unit I wasn't getting the full systems potential. Also after updating the EFI I don't have hotplug anymore and it seems like TB is having a few errors in loading up/being recognised by the UAD software.. which in turn doesn't help with loading my USB Softube Console 1 controllers as they want to 'see' the UAD Apollo switched on to work in UAD Console software. I can get them to work - just not instantaneous when the machine switches on as before.
However the Console 1 Faders can eat a lot of USB power - maybe I need to send them more, but unsure of the best method?

So thinking this is TB related and of course wanting better TB options like a real Mac, file transfer etc.
I have purchased the Raspberry Pi 4, Dupont Wires, S0IC8 S0P8 Cable with Clip and
I'm going to try flashing the main TB on the Z390 MOB (not a card).

I have the PI 4 loaded and working etc.
My only question on it all - In the comment section below. Splitting the wire? Does this mean I need to literally open up a wire and split it into a bare wire 'Y' then attach to Pin 7 and 3? Just double checking as the wires are single F/F single ended black plastic.

Once again, thank you for your efforts in this for everybody.

1588237789525.png
 
Back
Top