First time hackintosh—can't get past Clover

[georgebannerman]

I guess it seems like OsxAptioFixDrv is the way to go, right? But then how do I handle the +s?

 

[Feartech]

I guess it seems like OsxAptioFixDrv is the way to go, right? But then how do I handle the +s?

try adding EmuVariableUefi as well

 

[UtterDisbelief]

Hey, just noticed in post #9 you mentioned installing El Capitan.

That's brave on a Z390 and I'm sure you need to install the very latest 10.11.6 version to get any CPU support.

You also need a "slide=0" boot-command.

 

[halo12]

@halo12, does OpenCore install 10.11?

OpenCore requires a version of macOS that supports either a Prelinked Kernel or Kernel Collections, this means any install of OS X 10.7 Lion or newer are supported.

 

[halo12]

If you want use clover you can use OcQuirks as a substitute for any aptio fix. it much better.

Link: https://github.com/ReddestDream/OcQuirks

 

[georgebannerman]

@Feartech AptioMemoryFix and EmuVariableUefi together get me a row of +s:

OsxAptioFixDrv and EmuVariableUefi looks the same as OsxAptioFixDrv without EmuVariableUefi.

@UtterDisbelief slide=0 doesn't seem to change anything. Nor does presence or absence of "-f UseKernelCache=no". I saw that someone else had a successful build of 10.11.6 on the Z390, hence me going this way—a lot of the other boards that folks were able to install 10.11 on are no longer available, at least new.

@halo12 I tried removing the Aptios and EmuVariableUefi and replacing with OcQuirks and it looks exactly the same as the image above—a bunch of pluses.

What now? Remove the graphics card? Could the problem somehow be the memory—should I do a memory scan?

 

[halo12]

It could be the configuration of the bios, follow the instructions of this post, its configuration should work since aorus pro is equal auros pro wifi Link:https://www.tonymacx86.com/threads/psedogs-mod-pro-aorus-z390-8700k-vega64.283904/

 

[georgebannerman]

@halo12 Thanks! I changed a bunch of BIOS settings based on the configuration of @psedog. I left VT-d disabled as I think that dart=0 does the same thing anyway, and left Software Guard Extension (SGX) as disabled. I also couldn't find DVMT Pre-Allocated or DVMT Total Gfx Mem.

Anyhow, it still doesn't boot. Now I see the +s but it just stays there instead of immediately power cycling. So...progress?

I noticed that @psedog's drivers are different than mine. He's got:
- ApfsDriverLoader.efi
- AptioMemory.efi
- HFSPlus.efi
- NTFS.efi
- NvmExpressDxe.efi
- Vboxhfs.efi
- VirtualSMC.efi

I've got:
- FSInject-64.efi
- HFSPlus.efi
- OcQuirks.efi
- OcQuirks.plist
- OpenRuntime.efi
- OsxFatBinaryDrv-64.efi

Should I match the ones he has? Or should I try something else?

I did notice in the debug.log that it has the wrong amount of memory for me—I've got 32GB in two sticks, and debug.log says I have 16GB total in 8GB sticks:

8:077 0:023 Trusting SMBIOS...
8:118 0:041 Channels: 2
8:141 0:022 Interleave: 0 2 1 3 4 6 5 7 8 10 9 11 12 14 13 15 16 18 17 19 20 22 21 23
8:757 0:616 partNum=[redacted]
8:780 0:022 SMBIOS Type 17 Index = 0 => 0 0:
8:802 0:022 DIMM1 3200MHz 8192MB
8:824 0:022 mTotalSystemMemory = 8192
8:883 0:058 partNum=[redacted]
8:905 0:022 SMBIOS Type 17 Index = 1 => 2 2:
8:927 0:022 DIMM2 3200MHz 8192MB
8:949 0:022 mTotalSystemMemory = 16384
8:972 0:022 SMBIOS Type 17 Index = 2 => 1 1:
9:013 0:041 DIMM3 EMPTY
9:035 0:022 SMBIOS Type 17 Index = 3 => 3 3:
9:058 0:022 DIMM4 EMPTY

Does that matter?

What makes sense now? Reformat the Clover stick? Remove the graphics card? Something else?

 

[Feartech]

@halo12 Thanks! I changed a bunch of BIOS settings based on the configuration of @psedog. I left VT-d disabled as I think that dart=0 does the same thing anyway, and left Software Guard Extension (SGX) as disabled. I also couldn't find DVMT Pre-Allocated or DVMT Total Gfx Mem.

Anyhow, it still doesn't boot. Now I see the +s but it just stays there instead of immediately power cycling. So...progress?

I noticed that @psedog's drivers are different than mine. He's got:
- ApfsDriverLoader.efi
- AptioMemory.efi
- HFSPlus.efi
- NTFS.efi
- NvmExpressDxe.efi
- Vboxhfs.efi
- VirtualSMC.efi

I've got:
- FSInject-64.efi
- HFSPlus.efi
- OcQuirks.efi
- OcQuirks.plist
- OpenRuntime.efi
- OsxFatBinaryDrv-64.efi

Should I match the ones he has? Or should I try something else?

I did notice in the debug.log that it has the wrong amount of memory for me—I've got 32GB in two sticks, and debug.log says I have 16GB total in 8GB sticks:

8:077 0:023 Trusting SMBIOS...
8:118 0:041 Channels: 2
8:141 0:022 Interleave: 0 2 1 3 4 6 5 7 8 10 9 11 12 14 13 15 16 18 17 19 20 22 21 23
8:757 0:616 partNum=[redacted]
8:780 0:022 SMBIOS Type 17 Index = 0 => 0 0:
8:802 0:022 DIMM1 3200MHz 8192MB
8:824 0:022 mTotalSystemMemory = 8192
8:883 0:058 partNum=[redacted]
8:905 0:022 SMBIOS Type 17 Index = 1 => 2 2:
8:927 0:022 DIMM2 3200MHz 8192MB
8:949 0:022 mTotalSystemMemory = 16384
8:972 0:022 SMBIOS Type 17 Index = 2 => 1 1:
9:013 0:041 DIMM3 EMPTY
9:035 0:022 SMBIOS Type 17 Index = 3 => 3 3:
9:058 0:022 DIMM4 EMPTY

Does that matter?

What makes sense now? Reformat the Clover stick? Remove the graphics card? Something else?

try taking a memory module out, try it in different slots

 

[georgebannerman]

@Feartech @halo12 I tried removing each memory module and moving one module into slot 2 (before they were in slots 1 and 3). I also tried removing the graphics card. No dice—still just the +s.

Any other ideas?