The everything works Asus Z390-I Gaming * i7-8700K * SAPPHIRE NITRO+ Radeon RX Vega 64 Build

[ModMike]

iCloud is a pain but no need to log out.

Your best bet would be to pull your card, install Catalina with IGPU efi. When everything runs perfectly, then drop in the DGPU-efi and drop in Radeon VII.

 

[Poli169]

i can boot to with new D-EFI just fine, it is wrong @ModMike ?

will update here :
1. Set igpu to on -> After mac optimzer finish -> reboot, i still got injectintel turn on by default :
View attachment 459759
1b. this is very weird escpecally :

is it possible if i turn on igpu at bios it will automatically change clover config to enable that by default?

2. if i turn injectintel off manually, i can boot and then launch FCPX. but im not yet stress test it.
3. DisplayPort audio glitchy at the start (first second). not even normal at first and glitchy after +/- 5 minutes
4. is this new EFI in headless mode? how do i check it? as far as i know this one :
View attachment 459762
there's should be an icon there to indicated we are in headless mode?
5. My build can launch FCPX with this 2 option :

View attachment 459773

View attachment 459774

which one should i chose? im also dual booting to win10 in separated ssd

bonus (because of grand scheme of things this is very minor):
6. i just noticed, while airdrop from phone to this build works, hand off etc but couples dont :
6a. Airdrop from this build to iphone didn't works (nothing show up at finder -> airdrop)
6b. unlock with apple watch didn't works it shows progress bar unlocking with apple watch but revert back to using passcode seconds latter
6c. did you guys have same experience?



p.s. Did we have discord chat/server? Or that kind of thing is forbidden here?

In Hackintool my icon shows a lock.

 

[iDrakus]

My computer sometimes wakes up at night 1–2 times a night, but sometimes it doesn’t happen. I got rid of private records and now I see the reason why my hackintosh wakes up. For now, I'm using my old EFI. I’ll be using the new EFI from @ModMike the other day when I’ll figure out why it doesn’t work for me.

This is the reason my computer wakes up during sleep. I have disabled my Mac from waking up from sleep in Bluetooth in the settings.

2020-04-05 06:07:04.768728+0300  localhost powerd[125]: [powerd:sleepWake] vm.darkwake_mode: 0 -> 0
2020-04-05 06:07:04.790663+0300  localhost powerd[125]: [powerd:sleepWake] sendNoRespNotification: 0x19
2020-04-05 06:07:04.829748+0300  localhost powerd[125]: [powerd:sleepWake] AppWoke:com.apple.bluetoothd-blueavengers Reason:BlueAvengers: Toggle beacon state
2020-04-05 06:07:04.829777+0300  localhost powerd[125]: [powerd:sleepWake] Wake reason: "BlueAvengers: Toggle beacon state"  identity: "com.apple.bluetoothd-blueavengers"
2020-04-05 06:07:07.377981+0300  localhost powerd[125]: [powerd:sleepWake] vm.darkwake_mode: 0 -> 0
2020-04-05 06:07:09.043506+0300  localhost powerd[125]: [powerd:sleepWake] Updating wake end timestamp to 1096541748557
2020-04-05 06:07:09.043815+0300  localhost powerd[125]: [powerd:sleepWake] sendNoRespNotification: 0x1f
2020-04-05 06:07:12.811455+0300  localhost powerd[125]: [powerd:sleepWake] vm.darkwake_mode: 0 -> 0
2020-04-05 06:09:01.512984+0300  localhost powerd[125]: [powerd:sleepWake] vm.darkwake_mode: 0 -> 0
2020-04-05 06:09:21.376001+0300  localhost powerd[125]: [powerd:sleepWake] vm.darkwake_mode: 0 -> 0
2020-04-05 06:09:21.401174+0300  localhost powerd[125]: [powerd:sleepWake] sendNoRespNotification: 0x19
2020-04-05 06:09:36.447841+0300  localhost powerd[125]: [powerd:sleepWake] chooseStandbyDelay(): lowBattery = false, battery powered = false, capacity=0, lowBatteryThreshold=0; chosen delay=86400
2020-04-05 06:09:36.456547+0300  localhost powerd[125]: [powerd:sleepWake] Eligible for Standby: 0
2020-04-05 06:09:36.456548+0300  localhost powerd[125]: [powerd:sleepWake] standbyDelay:86400 eligibleForStandby:0 elapsedTime:0 gDelta2Standby:86400
2020-04-05 06:09:36.456591+0300  localhost powerd[125]: [powerd:sleepWake] Entering Sleep state due to 'Software Sleep pid=199'
2020-04-05 06:09:36.456886+0300  localhost powerd[125]: [powerd:sleepWake] connectionFireNotification: 0x0
2020-04-05 06:09:41.467707+0300  localhost powerd[125]: [powerd:sleepWake] No AdaptiveWake is requested. InactivityEnd:Mon Jan  1 03:00:00 2001 PowerNap State:0

As I understand it, the reason is "com.apple.bluetoothd-blueavengers".

I use the combo module BCM94360CS2 and I do not use any of the four kexts (BrcmBluetoothInjector.kext, BrcmFirmwareData.kext, BrcmPatchRAM3.kext, AirportBrcmFixup.kext) for Wi-Fi and Bluetooth. Perhaps this is the case?

Update 1:

In one of the forums, I found out that some people have such a problem after upgrading to Catalina. I started using Catanlina in November when I switched to it with Mojave after purchasing a 5700 XT graphics card.

In the "Power" section in the "About the system" application, I have several scheduled events about the computer leaving sleep mode at once. I do not know where they came from, since I did not set any events. All of them are at night, and are planned for the day ahead.



They were planned by the com.apple.alarm.user-visible-Weekly Usage Report process.

Terminal command: pmset -g sched



Update 2:

I conducted an experiment by manually changing the date and time, and my computer actually woke up from sleep on one of the planned events.

I turned off the “Screen Time” function on the Mac, disabled notifications for all applications on the computer, and also disabled all functions in the calendar settings.

I canceled all already scheduled events using the command for Terminal: sudo pmset schedule cancelall

Now I do not have scheduled events, but they may appear in the future if I did not find out why they are created automatically.

If this solves my problem, I will report it.

I do not use the Do Not Disturb mode at night. Do you use it?

 

[ModMike]

My computer sometimes wakes up at night 1–2 times a night, but sometimes it doesn’t happen. I got rid of private records and now I see the reason why my hackintosh wakes up. For now, I'm using my old EFI. I’ll be using the new EFI from @ModMike the other day when I’ll figure out why it doesn’t work for me.

This is the reason my computer wakes up during sleep. I have disabled my Mac from waking up from sleep in Bluetooth in the settings.

2020-04-05 06:07:04.768728+0300  localhost powerd[125]: [powerd:sleepWake] vm.darkwake_mode: 0 -> 0
2020-04-05 06:07:04.790663+0300  localhost powerd[125]: [powerd:sleepWake] sendNoRespNotification: 0x19
2020-04-05 06:07:04.829748+0300  localhost powerd[125]: [powerd:sleepWake] AppWoke:com.apple.bluetoothd-blueavengers Reason:BlueAvengers: Toggle beacon state
2020-04-05 06:07:04.829777+0300  localhost powerd[125]: [powerd:sleepWake] Wake reason: "BlueAvengers: Toggle beacon state"  identity: "com.apple.bluetoothd-blueavengers"
2020-04-05 06:07:07.377981+0300  localhost powerd[125]: [powerd:sleepWake] vm.darkwake_mode: 0 -> 0
2020-04-05 06:07:09.043506+0300  localhost powerd[125]: [powerd:sleepWake] Updating wake end timestamp to 1096541748557
2020-04-05 06:07:09.043815+0300  localhost powerd[125]: [powerd:sleepWake] sendNoRespNotification: 0x1f
2020-04-05 06:07:12.811455+0300  localhost powerd[125]: [powerd:sleepWake] vm.darkwake_mode: 0 -> 0
2020-04-05 06:09:01.512984+0300  localhost powerd[125]: [powerd:sleepWake] vm.darkwake_mode: 0 -> 0
2020-04-05 06:09:21.376001+0300  localhost powerd[125]: [powerd:sleepWake] vm.darkwake_mode: 0 -> 0
2020-04-05 06:09:21.401174+0300  localhost powerd[125]: [powerd:sleepWake] sendNoRespNotification: 0x19
2020-04-05 06:09:36.447841+0300  localhost powerd[125]: [powerd:sleepWake] chooseStandbyDelay(): lowBattery = false, battery powered = false, capacity=0, lowBatteryThreshold=0; chosen delay=86400
2020-04-05 06:09:36.456547+0300  localhost powerd[125]: [powerd:sleepWake] Eligible for Standby: 0
2020-04-05 06:09:36.456548+0300  localhost powerd[125]: [powerd:sleepWake] standbyDelay:86400 eligibleForStandby:0 elapsedTime:0 gDelta2Standby:86400
2020-04-05 06:09:36.456591+0300  localhost powerd[125]: [powerd:sleepWake] Entering Sleep state due to 'Software Sleep pid=199'
2020-04-05 06:09:36.456886+0300  localhost powerd[125]: [powerd:sleepWake] connectionFireNotification: 0x0
2020-04-05 06:09:41.467707+0300  localhost powerd[125]: [powerd:sleepWake] No AdaptiveWake is requested. InactivityEnd:Mon Jan  1 03:00:00 2001 PowerNap State:0

As I understand it, the reason is "com.apple.bluetoothd-blueavengers".

I use the combo module BCM94360CS2 and I do not use any of the four kexts (BrcmBluetoothInjector.kext, BrcmFirmwareData.kext, BrcmPatchRAM3.kext, AirportBrcmFixup.kext) for Wi-Fi and Bluetooth. Perhaps this is the case?

Update 1:

In one of the forums, I found out that some people have such a problem after upgrading to Catalina. I started using Catanlina in November when I switched to it with Mojave after purchasing a 5700 XT graphics card.

In the "Power" section in the "About the system" application, I have several scheduled events about the computer leaving sleep mode at once. I do not know where they came from, since I did not set any events. All of them are at night, and are planned for the day ahead.

View attachment 459812

They were planned by the com.apple.alarm.user-visible-Weekly Usage Report process.

Terminal command: pmset -g sched

View attachment 459814

Update 2:

I conducted an experiment by manually changing the date and time, and my computer actually woke up from sleep on one of the planned events.

I turned off the “Screen Time” function on the Mac, disabled notifications for all applications on the computer, and also disabled all functions in the calendar settings.

I canceled all already scheduled events using the command for Terminal: sudo pmset schedule cancelall

Now I do not have scheduled events, but they may appear in the future if I did not find out why they are created automatically.

If this solves my problem, I will report it.

I do not use the Do Not Disturb mode at night. Do you use it?

That is some excellent work. I also realized my computer is being brought out of sleep and not going back after scheduled events. I had looked into this 18 months ago so I guess I need to look into it again.

I do not use do not disturb but am wondering if that will work. Let us know.

 

[ModMike]

In Hackintool my icon shows a lock.

I just checked and it was off when I started, I wonder if setting BIOS to boot from IGOU causes the issue. It is supposed to be set to PEG but that kills FCPX. Let me test but I can't spend much time on it, I was at it for 10 hours yesterday.

 

[iDrakus]

No that should not make a difference though you can always try. Try to disable IGPU in BIOS and add agdpmod=piker.

How many monitors do you have and how are they plugged in and where?

If all else fails, re-enable IGPU, use the IGPU-EFI from post #1, pull the 5700XT, plug monitor into MB DP port and boot. Set everything up as needed.

If that works well, we can re-install the 5700XT and work out the issue once it runs properly.

Edit: Just saw a few posts and that’s what people who got it to work are doing.

I plan to try your new EFI again tonight.

Do I understand correctly that it should work without any changes on my part on the AMD 5700 XT graphics card?

The argument agdpmod = pikera should only be used when using WhateverGreen.kext, right?

 

[ModMike]

View attachment 459762
there's should be an icon there to indicated we are in headless mode?

5. My build can launch FCPX with this 2 option :

I inadvertently deleted a device property. Please try new EFIs posted. I am currently able to start FCPX using PEG as graphics card and multi monitor enabled in headless mode:

 

[ModMike]

I plan to try your new EFI again tonight.

Do I understand correctly that it should work without any changes on my part on the AMD 5700 XT graphics card?

The argument agdpmod = pikera should only be used when using WhateverGreen.kext, right?

I inadvertently made an error in my EFI so theoretically, yes to both.

 

[iDrakus]

I inadvertently made an error in my EFI so theoretically, yes to both.

I think I understand you. So I should have used your EFI, add the argument agdpmod = pikera and set everything like this in the BIOS?

Advanced Items> System Agent (SA) Graphics Configuration> Primary Display> PEG for DGPU
Advanced Items> System Agent (SA) Graphics Configuration> IGPU Multi-Monitor> Enabled for DGPU

________________
Why would anyone use WhateverGreen.kext then?

 

[ModMike]

I think I understand you. So I should have used your EFI, add the argument agdpmod = pikera and set everything like this in the BIOS?

Advanced Items> System Agent (SA) Graphics Configuration> Primary Display> PEG for DGPU
Advanced Items> System Agent (SA) Graphics Configuration> IGPU Multi-Monitor> Enabled for DGPU

________________
Why would anyone use WhateverGreen.kext then?

Yes. If you want to try it now I can standby to work with you.

By the way, always be sure to ERASE your old EFI, not just copy over it.