Contribute
Register

[SUCCESS] blouse's "Hack Pro" :: i9-9900K + Z390 Aorus Pro + Vega 64 + TB3 + USB3 :: 100% working

Status
Not open for further replies.
with my setup - I Just spent the time inbetween checking the combos - You need AptioMemoryFix-64.

  • AtherosE2200Ethernet (probably taking up space?) - Don't need
  • RealtekRTL8111 (probably taking up space?) - Don't need
  • You DO need USBInjectAll... Made the mistake of getting rid of that... Ech. Caused issues.
  • OH and I am also runinng rehab's XHCI Unsupported kext.
Including my UIAC, USB Map, and exclusion args (apply them in the usbmap.plist. If you can get them to work with your MacMini 2018 that's essentially the USB 3.0 header + USB 2.0 headers w/ the weird ITC device on HS12 and the USB Bluetooth on HS14 mapped out. Get power setup to work with that DSDT - you're laughing. My BT is working and all I need to do is get shutdown and sleep to work - build a processor SSDT and DSDT - and she's Golden! And working for both HS an Mojave with GTX and Radeon cards.

If we could only get the iGPU to work lol.

I take it you're using FileVault2 If you aren't using filevault you don't need below
  • AppleImageCodec-64
  • AppleKeyAggregator-64
  • AppleKeyFeeder-64
  • AppleUITheme-64
  • VBoxHfs-64
  • FirmwareVolume-64
They only slow your boot
FAKESMC + SMCHelper seem to cause KP. T

This is my Kexts --> Other folder:
AppleALC.kext <-- Rescripted I posted (assign -> 16. Kinda works with 1 and 3 but 16 gives Digital Audio)
Lilu.kext
SMCSuperIO.kext
SMCProcessor.kext
VirtualSMC.kext
WhateverGreen.kext
IntelMausiEthernet.kext
CodecCommander.kext

this is my drivers64UEFI folder:
(only have a driver64UEFI folder - you're not booting legacy and don't need the DriverBios64 - AT ALL)

EmuVariableUefi-64.efi <- 30 seconds away from testing. If I log back on quickly after posting this it didn't F*** things up.
AptioMemoryFix-64.efi
HFSPlus-64.efi
ApfsDriverLoader-64.efi
DataHubDxe-64.efi
FSInject-64.efi
PartitionDxe-64.efi

APCI : darkwake=8 dart=0 -gux_defer_usb2 keepsyms=1

Boot : fixShutdown, FixHDA, Automerge

Devices : InjectUSB AddClockID FixOwnership

AppleRTC, KernelPM

Config : CSRActiveConfig: 0x07F or 0x067

Using MacPro6,1 for now... the SSDT I have WORKS (holy s*** I know) and rather than bother with figuring out how to do the damned deconstructing of an iMac18,3's IOPowerManagement.kext I just used the parts of a DSDT from the macpro... It's not ideal lemme tell ya. 2oC hotter and 5-10% slower, but it works. AND my iogear 4.0BT usb dongle works again. So, there's that...

I am also discovering that (apparently) OsxAptioFix2Drv-free2000.efi may help with faster startups and shutdown / fix sleep/wake. The different APTIO fixes for memory (AptioMemoryFix-64, drv3, drv2, free2000) basically tell the boot process how to allocate memory based on the processes that need to be done. the free2000 and MemoryFix-64 do it differently. free2000 seems to be for x99 chips whereas MemoryFix-64 is essentially an optimized and stripped down version of Drv3 for better compatibility... In theory. Some of these drivers are not compatible with other drivers and kexts - things like EmuVariableUEFI.efi causing issues on some systems with OSXAptioFixDrv series (the original one) or VirtualSMC.efi not working with FAKESMC.Kext for instance...

YOU SHOULD NEVER BE MIXING THESE APTIO memory fixes TOGETHER. EVER. Unless someone can prove me wrong. Hell I welcome it because learning to get better is awesome. You only need ONE at a time installed in Drivers64UEFI as it could mix up how your system tells the memory to store information and you'll get allocation errors. Which means your memory takes a look at what it's booting, and instead of sorting it neatly onto the shelf it shits itself before wiping its butt with the data and stuffing the pockets of your sports coat you left on a chair the kitchen. Then drools while choking on it's own spittle. You will also get this with BIOS -> CSM DISABLED. DO NOT DISABLE CSM. Anyone tells you to do it they are dumb or crazy or running one monitor and do not care about compatibility. I run 4 monitors off of a GTX1070 - compatibility counts.

But I digress...

Basic rule of tumb thta works 8/10 times, depending on your build and mainboard: Generally you try one and if it doesn't work add EMU or roll back one step up and try with EMU. They are top to bottom in order of release and instruction set.

- Oldest - OSXAptioFixDrv-64.efi + EmuVariableUEFI.efi + SMCHelper + FakeSMC.kext
- Older - OSXAptioFixDrv2-64.efi + EmuVariableUEFI.efi + SMCHelper + FakeSMC.kext
- Not too old - OSXAptioFixDrv3-64.efi + EmuVariableUEFI.efi + SMCHelper + FakeSMC.kext
- New Hotness -AptioMemoryFix-64.efi + VirtualSMC.kext...
--> [ + EmuVariableUEFI.efi if problems. if not roll back one up or try with VirtualSMC.efi ]
- New Hotness's Kinky older Cousin - OsxAptioFix2Drv-free2000.efi <--- Haven't tested this yet
https://nickwoodhams.com/x99-hackintosh-osxaptiofixdrv-allocaterelocblock-error-update/

EDIT:
OS X 10.11.3 and earlier

https://nickwoodhams.com/x99-hackintosh-osxaptiofixdrv-allocaterelocblock-error-update/
  1. Upgrade Clover to at least version r3354.
  2. Install OsxAptioFixDrv-64.efi in your /EFI/ClOVER/drivers64UEFI folder. Remove any other OsxAptioFix files.
  3. Download and place Test2.efi alongside OsxAptioFixDrv-64.efi in your /EFI/ClOVER/drivers64UEFI folder.
  4. Restart and try.
 

Attachments

  • Exclusion-Arg.txt
    66 bytes · Views: 140
  • SSDT-UIAC.aml
    867 bytes · Views: 142
  • SSDT-UIAC.dsl
    4.2 KB · Views: 117
  • usb.plist
    7.1 KB · Views: 180
  • SSDT-UIAC.dsl
    4.2 KB · Views: 136
  • XHCI-unsupported.kext
    512 bytes · Views: 161
Last edited:
@blouse
Thank you so much for this build tutorial! And thanks to everyone else contributing this thread as well! I have near identical hardware (different Mainboard: Z390 Aorus Master) and you saved me a lot of time and trouble. I use my machine primary for music production in my studio and sometimes I do video stuff too. As I have dedicated PCIe audio interfaces (with macOS Support), my onboard audio is deactivated, so I don't know if it would work. I can confirm, that using the iGPU headless brings a lot more smoothness and overall performance. The only things currently not working for me are shutdown (reboot works), and I'm not able to get the Vega 64 temp data into HWMonitor. It also would be cool to get the onboard Bluetooth working. Did anyone ever manage to do so?

All the best,
Jan

No. It’s 5.0 BT which there is no Mac equiv for. Your best bet is to use USBMap-Master or manually build a USB mapping SSDT-UAL.aml file to tell the OS to exclude the BT card on-board (HS14 btw) so you can use a USB connected Broadcom Bluetooth device that’s vanilla with macOS.

I got my Bluetooth up and I’m pretty sure I’m the first to do it as of this morning.

Shut down and sleep are effed tho. The downside to using APTIOMemoryFix-64. Your system runs. Just can’t shut it down lol.
 
Man even if its working for you, your SMBIOS is not close to the real hardware, so your juggling around other issues probably, just go with MacMini 8.1 or iMac18.3, they're closest to the hardware used here Z390...
Virtual SMC will be great in the future but at the moment not crucial, FakeSMC has way better sensor support at the moment AND
it doesn't make sense to recommend SMBIOS which are not appropriate for the hardware...

You're right! Which is why I switched BACK to the iMac18,3 as the 6,1 was used for initial usb SSDT setup. Now that bluetooth is working z270 chipsets are back on the menu.

@blouse - I let the processor and the BIOS do the work. If it works for you - golden.
 
with my setup - I Just spent the time inbetween checking the combos - You need AptioMemoryFix-64.

  • AtherosE2200Ethernet (probably taking up space?) - Don't need
  • RealtekRTL8111 (probably taking up space?) - Don't need
  • You DO need USBInjectAll... Made the mistake of getting rid of that... Ech. Caused issues.
  • OH and I am also runinng rehab's XHCI Unsupported kext.
Including my UIAC, USB Map, and exclusion args (apply them in the usbmap.plist. If you can get them to work with your MacMini 2018 that's essentially the USB 3.0 header + USB 2.0 headers w/ the weird ITC device on HS12 and the USB Bluetooth on HS14 mapped out. Get power setup to work with that DSDT - you're laughing. My BT is working and all I need to do is get shutdown and sleep to work - build a processor SSDT and DSDT - and she's Golden! And working for both HS an Mojave with GTX and Radeon cards.

If we could only get the iGPU to work lol.

I take it you're using FileVault2 If you aren't using filevault you don't need below
  • AppleImageCodec-64
  • AppleKeyAggregator-64
  • AppleKeyFeeder-64
  • AppleUITheme-64
  • VBoxHfs-64
  • FirmwareVolume-64
They only slow your boot

Hello.
Because it is the same motherboard as you,
I will use SSDT-UIAC. Thank you.
I will use it with USBInjectAll.
What is USB.plist used for?

I am now imac 18.3 SMBIOS.
Is it worth changing SMBIOS to Macmini 8.1?
If I try, can I change the SMBIOS in Config.plist? Or should I clean install MacOS?
 
@blouse - I let the processor and the BIOS do the work. If it works for you - golden.

For me, HWP was not enabled with iMac18,3 which meant the computer was not taking advantage of any of Intel built in Turbo functionality. Fine to use iMac18,3 for doing "all core" overclocks (with MCE enabled). By the way, I turned back my overclock because I was having too many stability issues.

Plus I am getting faster single core speeds with greater stability using HWP (Turbo) and 65-70C temps (MacMini8,1) with standard cooling. Single core can properly boost up to 5Ghz. Hope this info helps someone!
 
No you don't need to do a clean install. macOS has a modular driver set in it, it takes out what it needs according the detected SMBIOS while booting. You can just play around with different SMBIOS...but make sure that you finally generate a UUID in Clover...

Thank you,
My Intel Power Gadget does not display 5 GHz without overclocking.
If the HWP works properly, I will try it.
 
I have a 1080 Ti sat in a box, and I need to know if I should send it back and get a vega 64 for editing in FCPX and also photoshop stuff, etc.? Any help hugely appreciated!!!
 
There may be hope on the horizon for Nvidia drivers, but I wouldn't count on it.

Vega64 is a super safe bet, for the most part works out of the box. With the fan fix the Vega64 seems to run very, very well.
 
Woot woot. I got my Gigabyte Z390 Pro WiFi up and running with an i5-9600k. No wifi or sound yet but it booted from through clover.
 
Pulled out one of the Vega64's and popped in the Gigabyte Titan Ridge card...

Screen Shot 2018-12-08 at 4.47.02 PM.png
 
Status
Not open for further replies.
Back
Top