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

[Beachgirl2802]

For those that used this specific this guide with the ASUS ROG Z370-G, do you remember if you selected UEFI Boot Mode or Legacy Boot Mode? From reading the general installation guide stated, I think it's UEFI Boot Mode but I am not sure.

Per Step #12 of general installation guide " At Bootloader Options screen choose UEFI Boot Mode or Legacy Boot Mode. UEFI Boot Mode is recommended for 7/8/9/100/200 Series CustoMac desktops and all UEFI capable systems. Legacy Boot Mode is recommended for 5/6 Series CustoMac desktops and all BIOS based systems."

 

[pastrychef]

For those that used this specific this guide with the ASUS ROG Z370-G, do you remember if you selected UEFI Boot Mode or Legacy Boot Mode? From reading the general installation guide stated, I think it's UEFI Boot Mode but I am not sure.

Per Step #12 of general installation guide " At Bootloader Options screen choose UEFI Boot Mode or Legacy Boot Mode. UEFI Boot Mode is recommended for 7/8/9/100/200 Series CustoMac desktops and all UEFI capable systems. Legacy Boot Mode is recommended for 5/6 Series CustoMac desktops and all BIOS based systems."

UEFI

 

[Beachgirl2802]

UEFI

Hi Pastrychef,

Step #15 of the general installation guide says to "drag multibeast to your completed USB drive." It wasnt explicitly mentioned in your write up. Is that a step I should still do anyways? Literally download multibeast on my completed USB drive? Thanks.

 

[KingKPS]

Hmm... Doesn't make sense... In your config.plist, Devices section, where Audio-id injection is, it's currently set to "No", try leaving it blank.

Btw, you can also delete CodecCommander.kext.

Also, remember, you need a clean AppleHDA.kext or AppleALC.kext will most likely not work right.

Still not working despite leaving the Audio-ID as blank, deleting the CodecCommander, and using the clean AppleHDA.kext that you provided. Is there a way to test if maybe the Front Panel IO on my case is the issue?

 

[pastrychef]

Hi Pastrychef,

Step #15 of the general installation guide says to "drag multibeast to your completed USB drive." It wasnt explicitly mentioned in your write up. Is that a step I should still do anyways? Literally download multibeast on my completed USB drive? Thanks.

Don't mix-n-match different guides. There are too many different ways to install macOS on to a hackintosh. Mixing and matching can only lead to problems.

Once you've made your USB installer, just follow directions in post #1.

 

[pastrychef]

Still not working despite leaving the Audio-ID as blank, deleting the CodecCommander, and using the clean AppleHDA.kext that you provided. Is there a way to test if maybe the Front Panel IO on my case is the issue?

I guess you can connect your mic directly to the motherboard header pins...

 

[pastrychef]

Hi Pastrychef,

Step #15 of the general installation guide says to "drag multibeast to your completed USB drive." It wasnt explicitly mentioned in your write up. Is that a step I should still do anyways? Literally download multibeast on my completed USB drive? Thanks.

I want to elaborate a little... Usually, there are multiple methods to get different things working. The methods I've chosen for this build keeps everything hackintosh related to a single EFI folder. The macOS installation and your main system drive will have no traces of anything hackintosh related.

The benefits of this are:

1. If/when you want to pull your main system drive and connect to a real Mac or another hackintosh, it will work. You just have (1) delete the EFI folder if you are going to use it with a real Mac or (2) replace the EFI folder with one that's compatible with the other hackintosh.
2. It also means that if/when you pull a system drive from a real Mac or another hackintosh, you can just plug it in, select that drive from the Clover boot menu and it will work (assuming the other hackintosh follows the same principles).
3. It makes it easy for updates.
4. It reduces confusion.

As I stated above, there are too many ways to get things working and often these different methods will conflict with each other. One good example is trying to get audio fixed. One method modifies one of the kexts that is installed by the macOS installer, another method disables the standard macOS driver and uses an entirely custom driver, another requires editing of config.plist, and there are more. Each of these will conflict with each other and using more than one may very well result in no audio and require lots of troubleshooting to undo what some of these methods do.

*Note: Technically speaking, it is not recommended to install all the hackintosh related kexts in to the EFI folder. However, I've been doing it this way for quite a long time and have never experienced any adverse affects from doing so and I will continue to do it this way until I do encounter problems.

 

[hannibal1969]

I have a few new findings:

• Enable iGPU renderer together with VEGA 64 will use the iGPU in Resolve instead of the more powerful VEGA. I have to disable iGPU for much better render performance and enforce the usage of the VEGA. Although VEGA is displayed as the GPU being used significant performance is reduced while iGPU is enabled. As example H265 1080p is about 50fps on average on iGPU. With iGPU disabled I get approx 170fps.
• Latest Apple Compression can cause panics. (well I have some suspicious minds about compression).

Backtrace (CPU 0), .....
0xffffff82113ebc80 : 0xffffff7f9a2d598b com.apple.kext.AMDRadeonX5000 : __ZN37AMDRadeonX5000_AMDAccelDisplayMachine24cleanHWMemoryAndContextsEv + 0xef
0xffffff82113ebcc0 : 0xffffff7f9a2d57f6 com.apple.kext.AMDRadeonX5000 : __ZN37AMDRadeonX5000_AMDAccelDisplayMachine21displayModeWillChangeEv + 0x74
0xffffff82113ebce0 : 0xffffff7f98753442 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOAccelDisplayMachine224display_mode_will_changeEj + 0x238
0xffffff82113ebd20 : 0xffffff7f98779c76 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator217system_will_sleepEib + 0x17e
0xffffff82113ebd50 : 0xffffff7f987804be com.apple.iokit.IOAcceleratorFamily2 : __ZN19IOAccelDisplayPipe222display_change_handlerEPvP13IOFramebufferiS0_ + 0x15e
0xffffff82113ebd90 : 0xffffff7f97dada76 com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer24deliverGroupNotificationEijbiPv + 0x354
0xffffff82113ebe40 : 0xffffff7f97d9a96d com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer30deliverFramebufferNotificationEiPv + 0x145
0xffffff82113ebe80 : 0xffffff7f97da22c6 com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer10systemWorkEP8OSObjectP22IOInterruptEventSourcei + 0x26c
0xffffff82113ebed0 : 0xffffff8016c99785 mach_kernel : __ZN22IOInterruptEventSource12checkForWorkEv + 0x105
0xffffff82113ebf30 : 0xffffff8016c97ef2 mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x1e2
0xffffff82113ebf70 : 0xffffff8016c9752c mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x2c
0xffffff82113ebfa0 : 0xffffff801661d557 mach_kernel : _call_continuation + 0x17
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(519.20)[0E507098-E375-39B7-9AE2-AFF2C7A5D961]@0xffffff7f97d91000->0xffffff7f97dd9fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[AEA4C7F5-CCB0-338B-B471-CF28A9792522]@0xffffff7f96e94000
         com.apple.iokit.IOAcceleratorFamily2(378.26)[AE312652-F3AF-3BFD-AEFF-FE4CCCC33BA9]@0xffffff7f98748000->0xffffff7f987e0fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[4FAE8181-B0B4-3A30-B0F3-77F48D2486E5]@0xffffff7f972a6000
            dependency: com.apple.iokit.IOSurface(211.15)[37BCC686-AF99-3381-AC4F-E54A347E0F40]@0xffffff7f97c0e000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[AEA4C7F5-CCB0-338B-B471-CF28A9792522]@0xffffff7f96e94000
            dependency: com.apple.iokit.IOGraphicsFamily(519.20)[0E507098-E375-39B7-9AE2-AFF2C7A5D961]@0xffffff7f97d91000
         com.apple.kext.AMDRadeonX5000(1.6.8)[17710DC9-5050-390D-BF09-23306F645407]@0xffffff7f9a2ce000->0xffffff7f9a605fff
            dependency: com.apple.iokit.IOSurface(211.15)[37BCC686-AF99-3381-AC4F-E54A347E0F40]@0xffffff7f97c0e000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[AEA4C7F5-CCB0-338B-B471-CF28A9792522]@0xffffff7f96e94000
            dependency: com.apple.iokit.IOGraphicsFamily(519.20)[0E507098-E375-39B7-9AE2-AFF2C7A5D961]@0xffffff7f97d91000
            dependency: com.apple.iokit.IOAcceleratorFamily2(378.26)[AE312652-F3AF-3BFD-AEFF-FE4CCCC33BA9]@0xffffff7f98748000

• Steam is much more responsive with VEGA compared to nVidia,
• In Windows the VEGA performance is not noticeable lower compared to nVidia in Battlefield 1,
• Still strugeling optimal VGTab settings. I have sometimes a video disconnect (to hot) full 100% fan speed and only reset will recover my Hack. This is only happening playing Company of Heroes with Steam on the Mac.
• Sometimes my EFI selectable OS-es are completely messed up (risky when you install windows or do a major update of windows because it modifies the bcfg of your mainboards UEFI registers). I have to boot with macOS installer with clover installed and have to do following commands to get the EFI properly registered again in mainboards bios,

Boot from USB installer,
Boot Clover,
Choose Shell,

map | bcfg boot dump |
remove entries with bcfg boot rm ".."
add entries with bcfg boot add ".." FS.. \EFI\CLOVER\CLOVERX64.EFI macOS

• I noticed that sometimes the disk numbers are changing. Maybe a bug in Mainboards bios. Sometimes I have to mount my EFI folder with disk1s1 sometimes its disk2s1... weird.
• Wake with VEGA is slower then wake with nVidia. Not a real issue its 5-7 secs to be woken compared with 2-5 sec with nVidia.

 

[pastrychef]

I have a few new findings:

• Enable iGPU renderer together with VEGA 64 will use the iGPU in Resolve instead of the more powerful VEGA. I have to disable iGPU for much better render performance and enforce the usage of the VEGA. Although VEGA is displayed as the GPU being used significant performance is reduced while iGPU is enabled. As example H265 1080p is about 50fps on average on iGPU. With iGPU disabled I get approx 170fps.
• Latest Apple Compression can cause panics. (well I have some suspicious minds about compression).

Backtrace (CPU 0), .....
0xffffff82113ebc80 : 0xffffff7f9a2d598b com.apple.kext.AMDRadeonX5000 : __ZN37AMDRadeonX5000_AMDAccelDisplayMachine24cleanHWMemoryAndContextsEv + 0xef
0xffffff82113ebcc0 : 0xffffff7f9a2d57f6 com.apple.kext.AMDRadeonX5000 : __ZN37AMDRadeonX5000_AMDAccelDisplayMachine21displayModeWillChangeEv + 0x74
0xffffff82113ebce0 : 0xffffff7f98753442 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOAccelDisplayMachine224display_mode_will_changeEj + 0x238
0xffffff82113ebd20 : 0xffffff7f98779c76 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator217system_will_sleepEib + 0x17e
0xffffff82113ebd50 : 0xffffff7f987804be com.apple.iokit.IOAcceleratorFamily2 : __ZN19IOAccelDisplayPipe222display_change_handlerEPvP13IOFramebufferiS0_ + 0x15e
0xffffff82113ebd90 : 0xffffff7f97dada76 com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer24deliverGroupNotificationEijbiPv + 0x354
0xffffff82113ebe40 : 0xffffff7f97d9a96d com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer30deliverFramebufferNotificationEiPv + 0x145
0xffffff82113ebe80 : 0xffffff7f97da22c6 com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer10systemWorkEP8OSObjectP22IOInterruptEventSourcei + 0x26c
0xffffff82113ebed0 : 0xffffff8016c99785 mach_kernel : __ZN22IOInterruptEventSource12checkForWorkEv + 0x105
0xffffff82113ebf30 : 0xffffff8016c97ef2 mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x1e2
0xffffff82113ebf70 : 0xffffff8016c9752c mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x2c
0xffffff82113ebfa0 : 0xffffff801661d557 mach_kernel : _call_continuation + 0x17
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(519.20)[0E507098-E375-39B7-9AE2-AFF2C7A5D961]@0xffffff7f97d91000->0xffffff7f97dd9fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[AEA4C7F5-CCB0-338B-B471-CF28A9792522]@0xffffff7f96e94000
         com.apple.iokit.IOAcceleratorFamily2(378.26)[AE312652-F3AF-3BFD-AEFF-FE4CCCC33BA9]@0xffffff7f98748000->0xffffff7f987e0fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[4FAE8181-B0B4-3A30-B0F3-77F48D2486E5]@0xffffff7f972a6000
            dependency: com.apple.iokit.IOSurface(211.15)[37BCC686-AF99-3381-AC4F-E54A347E0F40]@0xffffff7f97c0e000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[AEA4C7F5-CCB0-338B-B471-CF28A9792522]@0xffffff7f96e94000
            dependency: com.apple.iokit.IOGraphicsFamily(519.20)[0E507098-E375-39B7-9AE2-AFF2C7A5D961]@0xffffff7f97d91000
         com.apple.kext.AMDRadeonX5000(1.6.8)[17710DC9-5050-390D-BF09-23306F645407]@0xffffff7f9a2ce000->0xffffff7f9a605fff
            dependency: com.apple.iokit.IOSurface(211.15)[37BCC686-AF99-3381-AC4F-E54A347E0F40]@0xffffff7f97c0e000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[AEA4C7F5-CCB0-338B-B471-CF28A9792522]@0xffffff7f96e94000
            dependency: com.apple.iokit.IOGraphicsFamily(519.20)[0E507098-E375-39B7-9AE2-AFF2C7A5D961]@0xffffff7f97d91000
            dependency: com.apple.iokit.IOAcceleratorFamily2(378.26)[AE312652-F3AF-3BFD-AEFF-FE4CCCC33BA9]@0xffffff7f98748000

• Steam is much more responsive with VEGA compared to nVidia,
• In Windows the VEGA performance is not noticeable lower compared to nVidia in Battlefield 1,
• Still strugeling optimal VGTab settings. I have sometimes a video disconnect (to hot) full 100% fan speed and only reset will recover my Hack. This is only happening playing Company of Heroes with Steam on the Mac.
• Sometimes my EFI selectable OS-es are completely messed up (risky when you install windows or do a major update of windows because it modifies the bcfg of your mainboards UEFI registers). I have to boot with macOS installer with clover installed and have to do following commands to get the EFI properly registered again in mainboards bios,

Boot from USB installer,
Boot Clover,
Choose Shell,

map | bcfg boot dump |
remove entries with bcfg boot rm ".."
add entries with bcfg boot add ".." FS.. \EFI\CLOVER\CLOVERX64.EFI macOS

• I notices that sometimes the disk numbers are changing. Maybe a bug in Mainboards bios. Sometimes I have to mount my EFI folder with disk1s1 sometimes its disk2s1... weird.
• Wake with VEGA is slower then wake with nVidia. Not a real issue its 5-7 secs to be woken compared with 2-5 sec with nVidia.

I would have expected DaVinci Resolve to all you to pick which GPU to use...
I know that installing Windows can mess up the boot items. I didn't know that updates could also mess things up. But I primarily do my Windows updates through VMware Fusion.
Disk numbers changing a fairly common and I've seen it happen on most of my hacks. I don't know the cause of it.
Yes, wake is slower with the last two High Sierra versions. I never looked in to why.

 

[Beachgirl2802]

Hi all,

Currently going through the iDiot's Guide for iMessages. Not able to Mount Partition to get to the config.plist file in the EFI partition. Is it possible I didn't drag the right EFI file (EFI Unifided r4.3.zip ) into my partition of your macOS High Sierra drive after creating my USB installer?