Vanilla AMD Hackintosh
Why vanilla?
It’s clean
The AMD distros are designed to be ran on various different hardware combinations, while a vanilla install is made for your specific hardware. This means that your install will only have what it needs and no extra useless junk.
Tailor made for your hardware
A vanilla install doesn’t have any unneeded kexts or modifications which could cause issues.
More instructive
Making your own install teaches you a lot more about how hackintoshing works which in turn makes it easier for you to troubleshoot any potential issues.
The good, the bad and the ugly:
What works
- AMD Ryzen CPUs
- Native USB
- Native Audio
- The latest version of macOS High Sierra
- iCloud
So much works, that it is easier to say what doesn’t so here we go:
- AMD FX CPUs (I don’t have one to use for testing)
- Internal Graphics. Be it an AMD Ax CPU or one of the G Ryzen chips, the GPU will not work.
- Lower GPU performance, more specifically:
- About 10% lower on AMD GPUs
- About 75% lower on Nvidia GPUs
- I have been told that this is not the case. Performance varies a lot per model, but it is safe to assume it is a lot lower than on Windows.
- IOMMU
- iMessage, FaceTime
- Siri
Источник
Vanilla AMD Hackintosh
Why vanilla?
It’s clean
The AMD distros are designed to be ran on various different hardware combinations, while a vanilla install is made for your specific hardware. This means that your install will only have what it needs and no extra useless junk.
Tailor made for your hardware
A vanilla install doesn’t have any unneeded kexts or modifications which could cause issues.
More instructive
Making your own install teaches you a lot more about how hackintoshing works which in turn makes it easier for you to troubleshoot any potential issues.
The good, the bad and the ugly:
What works
- AMD Ryzen CPUs
- Native Audio
- macOS Mojave 10.14.1
- iCloud
- AMD GPUs
- Nvidia GPUs that don’t need Nvidia Web Drivers
So much works, that it is easier to say what doesn’t so here we go:
- AMD FX CPUs (I don’t have one to use for testing)
- Any other version of Mojave (Kernel sources haven’t been released for other versions, so no patched AMD kernels)
- Internal Graphics. Be it an AMD Ax CPU or one of the G Ryzen chips, the GPU will not work.
- Nvidia GPUs that need Nvidia Web Drivers (no Web Drivers yet)
- Lower GPU performance, more specifically:
- About 10% lower on AMD GPUs
- About 75% lower on Nvidia GPUs
- I have been told that this is not the case. Performance varies a lot per model, but it is safe to assume it is a lot lower than on Windows.
- IOMMU
- iMessage, FaceTime
- Siri
Источник
Mac os vanilla amd
AMD Clover config.plist
- Please get the patches.plist (Ryzen, FX) from AMD OS X Github (Right click, Save Page As, Remember to change the suffix to .plist)
- Open patches.plist with Clover Configurator (CCG) or Clover Cloud Editor (CCE).
<% hint style="info" %>If you are using CCE, please go to home page and set _ Show Find/Replace/TgtBridge values as: to Hex _because the following CCE screenshots are in Hex.
Explanations
Patches:
The first thing we’ll go over is the Patches section. This section allows us to dynamically rename parts of the DSDT via Clover. Since we’re not running a real mac, and macOS is pretty particular with how things are named, we can make non-destructive changes to keep things mac-friendly. We have one entries here:
- change SAT0 to SATA — for potential SATA compatibility
Enable Fix Shutdown
- This can fix some shutdown issues like reboot instead of shutting down. But this might also cause shutdown issues on some board. So if you are having some issues with shutting down, disable this.
Arguments:
- -v — enable verbose which shows all the behind-the-scenes text that scrolls by as you’re booting instead of the Apple logo and progress bar. It is very helpful for tracking issues are fixing them.
- npci=0x2000 — a fix for stuck at [PCI Configuration Start].
Default Volume — setting the default volume for booting.
- LastBootedVolume — let Clover uses the last booted volume (no matter if it boot successfully) as default.
Timeout (sec) — setting the timeout for auto-booting.
- -1 — disable auto-boot.
Legacy (PBR) — let Clover use PBR to boot legacy system.
Boot Graphics (which doesn’t matter much)
We have nothing to do here. You can tweak it if Clover doesn’t show correctly.
We have nothing to do here also.
- Reset HDA — Puts the codec back in a neutral state between OS reboots. This prevents some issues with no audio after booting to another OS and then back.
- USB — Under this section, we ensure that Inject and FixOwnership are selected to avoid issues with hanging at a half-printed line somewhere around the Enabling Legacy Matching verbose line. You can also get past that by enabling XHCI Hand Off in BIOS.
We have nothing to do here.
Scan:
The only settings I’ve tweaked on this page are the Scan settings. I’ve selected Custom, then checked everything except Legacy and Kernel. This just omits some of the unbootable entries in Clover to clean up the menu.
Please refer to GPU Buyers Guide and see which settings do you need for your GPU.
Kernel And Kexts Patches
The patches.plist (which you are editing) already has all of the patches you want to have. Those patches are used to patch the native Kernel.
- AppleRTC (enabled) — this ensures that we don’t have a BIOS reset on reboot.
Rt Variables and SMBIOS
RAW XML (Rt Variables)
RT Variables: (From CorpNewt’s Vanilla Guide)
We set Rt Variables -> ROM to UseMacAddr0 which just utilizes our onboard Mac address — this should be unique enough to not conflict with any others.
BooterConfig gets set to 0x28 , and CsrActiveConfig is set to 0x3e7 which effectively disables SIP as SIP is not supported on AMD Systems unfortunately.
SMBIOS: Skip this first
Explanations
Inject Kexts:
This setting has 3 modes:
- Yes — this tells Clover to inject kexts from the EFI regardless.
- No — this tells Clover not to inject kexts from the EFI.
- Detect — this has Clover inject kexts only if FakeSMC.kext or VirtualSMC.kext are not in the kext cache.
We set it to Yes to make sure that all the kexts we added before get injected properly.
Inject System ID:
This setting tells clover to set the SmUUID as the system-id at boot — which is important for iMessage and such.
NvidiaWeb:
This setting will force nvda_drv=1 on every boot, this is recommended for users with non-functional NVRAM ****(EmuVariableUEFI) or issues switching from the default macOS drivers to the Nvidia WebDrivers.
At this point, you can do File -> Save to save the config.plist (or go back to home page and download your config.plist if you are using CCE). Keep it to somewhere you’ll remember.
Now go to the next page to configure SMBIOS.
Источник
Mac os vanilla amd
AMD Vanilla OpenCore
Patches for Beta versions are provided but no support is given until the OS is released.
Try these patches at your own risk and always have a backup EFI to boot.
Languages: English (current)
Binary Kernel patches to enable almost native AMD CPU support on macOS.
Patches are now universal across 15h, 16h, 17h and 19h by utilizing the OpenCore Kernel Quirk ProvideCurrentCpuInfo . OpenCore 0.7.1 or newer is required.
Make sure to enable this quirk or the system won’t boot.
This quirk provides the kernel with the CPU frequencies for macOS to boot.
Core Count patch needs to be modified to boot your system. Find the three algrey — Force cpuid_cores_per_package patches and alter the Replace value only.
Changing B8000000 0000 / BA000000 0000 / BA000000 0090 * to B8 0000 0000 / BA 0000 0000 / BA 0000 0090 * substituting with the hexadecimal value matching your physical core count.
Note: The three different values reflect the patch for different versions of macOS. Be sure to change all three if you boot macOS 10.13 to macOS 12
See the table below for the values matching your CPU Core Count.
| CoreCount | Hexadecimal |
|---|---|
| 4 Core | 04 |
| 6 Core | 06 |
| 8 Core | 08 |
| 12 Core | 0C |
| 16 Core | 10 |
| 24 Core | 18 |
| 32 Core | 20 |
So for example a 6 Core 5600X Replace value would result in these replace values, B8 06 0000 0000 / BA 06 0000 0000 / BA 06 0000 0090
Note: MacOS Monterey installation requires Misc -> Security -> SecureBootModel to be disabled in the config.
Also TPM needs to be disabled in the BIOS. Both can be enabled after install.
Enables macOS to run on AMD CPUs on the fly.
Enables iMessage, Siri, FaceTime, Continuity etc.
Stable compared to custom XNU kernel.
- No 32-bit support (OPEMU) in 10.14 and lower
Supported AMD CPU’s
| Family | Codename | Example |
|---|---|---|
| 15h | Bulldozer | FX Series |
| 16h | Jaguar | A Series (including AM4 A-Series) |
| 17h and 19h | Zen | Ryzen, 1st, 2nd + 3rd Gen Threadripper, Athlon 2xxGE |
Information on the PAT fix patch
The default enabled patch is Algrey’s original patch. This will work for all GPUs and doesn’t affect audio but doesn’t improve the performance.
The other choice is Shaneee’s patch which will increase GPU performance on AMD GPUs but can stop Nvidia GPUs booting. It also causes audio issues when using HDMI and DP audio.
The choice is yours on which patch to use. Please don’t try to use them both at the same time.
Note on TRX40 Systems
Disabling the mtrr_update_action — fix PAT patch has shown an improvement in GPU performance on some systems that have tested. If you wish to test this it is recommended to do so on a USB with OpenCore to ensure it works first. There may be issues with different motherboard/GPU combos that we aren’t aware of. Proceed at your own risk.
Supported macOS versions
High Sierra 10.13.x
Monterey 12.x ( No Support until OS Release )
Download macOS High Sierra, Mojave, Catalina, Big Sur or Monterey from the App Store.
Plug in an empty USB drive.
Run one of the below commands in your Terminal to prepare the bootable macOS USB.
Install OpenCore on your USB drive. (For OpenCore releases see: https://github.com/acidanthera/OpenCorePkg/releases)
Read the OpenCore Documentaion for config.plist setup. A default config will not be provided.
Merge the patches provided into your OpenCore config.plist and edit it as per your needs.
Use the latest Release of OpenCore to avoid incompatibles. Find the latest release here.
For support creating OpenCore config read the docs and visit this guide or the Discord server.
For 15h_16h CPU family users on macOS Mojave:
Upon booting to macOS Mojave for first time, the system will reboot after the Data & Privacy screen. To fix this issue follow the procedure mentioned here under UPDATE-2 heading.
On macOS Mojave certain webpages will crash upon loading (eg. brew.sh, facebook.com). To fix this issue follow the procedure mentioned here under the UPDATE-5 heading.
To boot 10.15 two things needs to be taken care of:
If you have an EC device with ID PNP0C09 in your DSDT then macOS might get stuck while booting at the initial stage. To fix that you need to make sure your EC device is disabled by making it return status Zero . You can use a custom SSDT-EC0.aml to do that and if you want to see how it works you can refer to here.
-or-
You can change the ID of the EC device. Using this ACPI patch:
- When using these SMBIOS profiles MacPro6,1 , MacPro7,1 , or iMacPro1,1 , AppleIntelMCEReporter.kext macOS might panic. To prevent this you need to either use a different SMBIOS or use a disabler kext from here.
AlGrey for the idea and creating the patches.
XLNC for maintaining patches to various macOS versions.
Sinetek, Andy Vandijck, spakk, Bronya, Tora Chi Yo, Shaneee and many others for sharing their AMD/XNU kernel knowledge
Источник
