pastrychef's Asus ROG Strix Z370-G Gaming (WI-FI AC) build w/ i9-9900K + AMD 6600 XT

[pastrychef]

2 year update - dualboot 10.13.2 / win10
Hi all, I have been having a blast since following this build in jan 2018, very few issues after the initial setup, even with getting an ultrawide monitor that requires display port to work with 10.13! [csrutil disable in recovery mode]. I use macOS for music production and windows for games. feeling very spoiled.

Here are the problems I am still dealing with. I'm just wondering if anyone recognizes any of these:

-System time on windows is always ahead by 4 hours after rebooting from macOS;

-USB hard drives sometimes need to be replugged in order to be recognized after booting, but doesn't happen with flash storage or other usb devices;

-Sometimes no internet connection after rebooting into the other OS [likely router related];

-High refresh rate monitors not supported (?) by Nvidia web drivers [nobody games on Mac but I would still be interested if there was a fix], as well as no support for Mojave / dark mode (right?); and

-I have a projector plugged into the computer for movies / emulators on Windows, but on macOS. If there is a HDMI plugged in, the image goes through that port and I get no signal on my monitor. So I have to unplug it every time I boot into macOS. Is there a way to disable this port, or maybe just that "feature" in macOS? In Windows you can just disable that display until you are ready to use it.

Please try checking the following to see if it will fix your clock issue:

Fix incorrect time in Windows + OSX dual boot

I just thought I'd give people an easy to find guide for this information. Hope the mods are alright with that, and that this doesn't violate any posting guidelines. 1. Why does this happen? The simple explanation is; Windows uses Greenwhich time, and OSX uses Universal Time. It's as simple...

www.tonymacx86.com

Hmm... I don't know about the USB hard drives... Did you apply one of the proper USB 15 port limit fixes?

Try assigning the same static IP in macOS and Windows.

Yeah, Nvidia dropped support for macOS at High Sierra.

You may need to update WhateverGreen. But that would also mean Lilu and AppleALC would also need updating. Make backups before trying this if you are still on High Sierra.

 

[RickD00]

Hey @pastrychef

I thought my build is perfect, so I deceide to do a upgrade from 10.15.2 to 10.15.3

Then I screwed.
System stack at loading bar(at 75%) for a while then turn into black screen...
I can still enter recover mode(with screen on)
Tried nvram clean, not working
Tried to PCIE only(disable iGPU), not working(then i put it back)

Thanks for any suggestions.

 

[pastrychef]

Hey @pastrychef

I thought my build is perfect, so I deceide to do a upgrade from 10.15.2 to 10.15.3

Then I screwed.
System stack at loading bar(at 75%) for a while then turn into black screen...
I can still enter recover mode(with screen on)
Tried nvram clean, not working
Tried to PCIE only(disable iGPU), not working(then i put it back)

Thanks for any suggestions.

View attachment 449531

When the screen goes black, is there still disk activity?

 

[sonofted57]

Get rid of the following. Why did you add that stuff??
View attachment 449400

If removing SATA-200-series-unsupported.kext increases boot time, put it back.

You are using the wrong Bluetooth kexts. You can't just throw any kexts in there and hope it works...

In /EFI/CLOVER/kexts/Other/ delete:
BrcmFirmwareData.kext
BrcmNonPatchRAM.kext
BrcmPatchRAM.kext
FakePCIID_Broadcom_Wifi.kext
FakePCIID.kext

Use the attached kexts for Bluetooth.

You also added IntelMausi.kext. Why?

Instructions to fix USB:

The New Beginner's Guide to USB Port Configuration

Pre-amble When I originally wrote the Beginner's Guide to Creating a Custom USB SSDT the idea was to demystify and simplify the process of configuring all those USB ports our PC motherboards come with, so that they worked properly under macOS. The main sticking-point for many builders was the...

www.tonymacx86.com

Thank you sir! - bluetooth now works. The reason I added those ROM and MLB was to get iMessage working. As for IntelMausi, I might have merged instead of replaced the folder.

Is there away to enable audio input devices. When using the Mojave guide, I recall being able to record sound with a mic on a HYPERx gaming headset.

 

[RickD00]

When the screen goes black, is there still disk activity?

Yes. CPU light keep on - I leave it run for 10 mins and nothing get change

 

[pastrychef]

Thank you sir! - bluetooth now works. The reason I added those ROM and MLB was to get iMessage working. As for IntelMausi, I might have merged instead of replaced the folder.

Is there away to enable audio input devices. When using the Mojave guide, I recall being able to record sound with a mic on a HYPERx gaming headset.

Where did you get those values to enter? Nowhere in my instructions do I tell you to make up values to enter there. Please see the following guide:

An iDiot's Guide To iMessage

Actually this is less of a guide and more of an explanation of the procedures that I use in my own builds in order to enable access to the App Store, iMessage and FaceTime. Do not be offended by the term 'iDiot', it is not intended as an insult but more my attempt at a humorous play on words...

www.tonymacx86.com

What audio-id are you using? Is audio in working?

 

[RickD00]

When the screen goes black, is there still disk activity?

My bad - The disk light keeping on

 

[pastrychef]

Yes. CPU light keep on - I leave it run for 10 mins and nothing get change

Which CPU light?

If there is still disk activity, leave the system running until there is no more disk activity. The update may very well be progressing.

Things you can try:
Add "agdp=pikera" to boot arguments.
Unplug and re-plug the monitor cable when the screen goes black.

 

[RickD00]

Which CPU light?

If there is still disk activity, leave the system running until there is no more disk activity. The update may very well be progressing.

Things you can try:
Add "agdp=pikera" to boot arguments.
Unplug and re-plug the monitor cable when the screen goes black.

agdomod=pikera or vit9696 do not work for me.

Somehow i got this sorted out by adding FB Name=Orinoco and inject ATI.

I know WEG's notes saying I shouldn't do this. But I guess this have fixed my issue somehow..

I wonder does WEG has a bug collection repo or thread ?

 

[pastrychef]

agdomod=pikera or vit9696 do not work for me.

Somehow i got this sorted out by adding FB Name=Orinoco and inject ATI.

I know WEG's notes saying I shouldn't do this. But I guess this have fixed my issue somehow..

I wonder does WEG has a bug collection repo or thread ?

I don't know where to submit bug reports...