computers:hackintosh

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
computers:hackintosh [2020/09/18 13:18] – [Since Mojave Final 10.14.6] localadmincomputers:hackintosh [2023/06/11 19:51] (current) – jon
Line 22: Line 22:
 ===== What software is required? ===== ===== What software is required? =====
   * A legally obtained copy of macOS (via the App Store on a legit Mac, or if older, a physical disk)   * A legally obtained copy of macOS (via the App Store on a legit Mac, or if older, a physical disk)
-  * OpenCore Bootloader/Clover Bootloader +  * OpenCore Bootloader 
-  * ProperTree (for OpenCore)/Clover Configurator+  * ProperTree (for OpenCore)
   * VirtualSMC.kext   * VirtualSMC.kext
   * Any other kexts to cooperate with your installation (NIC, Audio, Bluetooth, etc)   * Any other kexts to cooperate with your installation (NIC, Audio, Bluetooth, etc)
   * A USB drive for the installer - [[https://support.apple.com/en-us/HT201372|The offical Apple way]], the OpenCore Guide uses a scripted method with the same code, but patches within the script.   * A USB drive for the installer - [[https://support.apple.com/en-us/HT201372|The offical Apple way]], the OpenCore Guide uses a scripted method with the same code, but patches within the script.
  
-You will also need a lot of patience, and expect some long nights understanding how everything comes together. The communities that support this hobby are very much in-line with most Linux communities where they want you to RTFM. Once you have RTFM, they want you to RTFM about five more times. Then, maybe then, you are worthy of asking a question that does not seem to resonate with your peeon brain. Reddit's /r/hackintosh and InsanelyMac are the two most reputable communities out there, but both still carry this mentality. Take this as a warning, have a thick skin, and be able to take some tough love. They do not cater to the needy and those who are just plain cheap and can't shell out money for a real Mac. You need to come armed with some education and knowledge about the tools you are using.+You will also need a lot of patience, and expect some long nights understanding how everything comes together. The communities that support this hobby are very much in-line with most Linux communities where they want you to RTFM. Once you have RTFM, they want you to RTFM about five more times. Then, maybe then, you are worthy of asking a question that does not seem to resonate with your "peeon" brain. Reddit's /r/hackintosh and InsanelyMac are the two most reputable communities out there, but both still carry this mentality. Take this as a warning, have a thick skin, and be able to take some tough love. They do not cater to the needy and those who are just plain cheap and can't shell out money for a real Mac. You need to come armed with some education and knowledge about the tools you are using.
  
 ===== Resources ===== ===== Resources =====
Line 34: Line 34:
 ==== Installation Guides ==== ==== Installation Guides ====
  
-  * [[https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide|Vanilla Desktop Guide - Clover.]] A really solid, detailed guide to making your own Vanilla install using Clover. Gives you the how & why. +  * [[https://dortania.github.io/OpenCore-Install-Guide//|OpenCore Install Guide.]] Use this if you are coming from Clover, and also if you're doing a vanilla installation. 
-  * [[https://dortania.github.io/OpenCore-Desktop-Guide/|OpenCore Desktop Guide.]] Use this if you are coming from Clover, but it should also double as a Vanilla guide. +  * [[https://github.com/dortania/OpenCore-Install-Guide/tree/master/clover-conversion|A companion to the OpenCore guide to convert from the older Clover bootloader installation.]]
-  * [[https://github.com/dortania/OpenCore-Desktop-Guide/tree/master/clover-conversion|A companion to the OpenCore guide if you are looking to convert your Clover installation.]] +
-  * [[https://dortania.github.io/vanilla-laptop-guide/|OpenCore Vanilla Laptop Guide.]] This is also a must-read, even if you are not using a laptop, because some methods in here are more up to date as of this writing than the desktop guide. +
-  * [[https://1revenger1.gitbook.io/laptop-guide/|Another OpenCore Vanilla Laptop Guide.]] Once again, must-read to cross-reference all information.+
  
 [[https://hackintosh-multiboot.gitbook.io/hackintosh-multiboot/|Dual/Multibooting OSes]] [[https://hackintosh-multiboot.gitbook.io/hackintosh-multiboot/|Dual/Multibooting OSes]]
 +
 +[[https://dortania.github.io/Wireless-Buyers-Guide/|Wireless Buyers Guide]]
  
 [[https://github.com/ITzTravelInTime/TINU|GUI USB Drive Creator]] [[https://github.com/ITzTravelInTime/TINU|GUI USB Drive Creator]]
  
 ===== Things that have changed ===== ===== Things that have changed =====
 +
 +==== Since macOS 14 - Sonoma ====
 +
 +Major droppage of older Intel CPUs, Broadcom WiFi Chipsets (Apple native hardware for Handoff capabilities). For myself at least, this is where the road ends. I can certainly build a newer hack, but we're now on the last round of Intel-released Macs that are left compatible.
 +
 +==== Since macOS 13 - Ventura ====
 +
 +Mostly just compatibility dropping of older GPUs and CPUs.
  
 ==== Since announcement of Apple moving to ARM architecture Apple processors ==== ==== Since announcement of Apple moving to ARM architecture Apple processors ====
Line 54: Line 61:
 Chill.. first off. It means that we may be seeing the end of Hackintoshing, but that is going to be roughly a decade down the line. Apple is not going to give up on Intel completely. As long as there are Macs that are being supported that use Intel-based processors, this will be around. This is also not to say that devs can spoof the CPU by that point either.. Many a hackintosh builds are using the ever-popular AMD Ryzen processors (Ryzentoshes) currently. If you notice, original Mac Pros are still being supported (albeit just MacPro 5,1, but still) and countless other models will be for some time, especially the new models that have just come out using Intel's processors. Apple will not alienate their customer base overnight. So, if you're looking to start fresh, use a latest gen Intel processor! Or, if you're feeling adventurous, check out the AMD builds. Chill.. first off. It means that we may be seeing the end of Hackintoshing, but that is going to be roughly a decade down the line. Apple is not going to give up on Intel completely. As long as there are Macs that are being supported that use Intel-based processors, this will be around. This is also not to say that devs can spoof the CPU by that point either.. Many a hackintosh builds are using the ever-popular AMD Ryzen processors (Ryzentoshes) currently. If you notice, original Mac Pros are still being supported (albeit just MacPro 5,1, but still) and countless other models will be for some time, especially the new models that have just come out using Intel's processors. Apple will not alienate their customer base overnight. So, if you're looking to start fresh, use a latest gen Intel processor! Or, if you're feeling adventurous, check out the AMD builds.
  
-==== Since Mojave Final 10.14.6 ====+==== Since macOS 12 - Monterey ==== 
 + 
 +https://dortania-github-io.thrrip.space/OpenCore-Install-Guide/extras/monterey.html#table-of-contents 
 +Dropped GPU support for NVidia Kepler-based 6xx-7xx GPUs 
 + 
 +=== Secure Boot === 
 + 
 +OTA Updates are a little restricted if your SMBIOS is supposed to have a T2 secure chip in it. You must have secure boot enabled, and set an additional setting in config. TL:DR don't use an SMBIOS that expects a T2 chip from a real mac. 
 +==== Since macOS 11 - Big Sur ==== 
 + 
 +https://dortania.github.io/hackintosh/updates/2020/11/12/bigsur-new.html 
 +==== Since Catalina 10.15 ==== 
 + 
 +https://www.reddit.com/r/hackintosh/comments/den28t/whats_new_in_macos_catalina/ 
 + 
 +=== End of x86 based software support === 
 +The most notable change which also affects normal macOS users is the end of x86 support for any apps. Most notably for a lot of us "techie" people, using Wine, or MacPorts or the like to get vintage Windows apps running on Mac. I have personally held off from updating to Catalina for this reason. As a ham radio operator, I have quite a few converted apps that I would like to keep running that would stop upon updating. 
 + 
 +== Wine Compatibility == 
 + 
 +Essentially, Wine is dead going forward. Not much progress has been made to keep it going. Now, on the other hand, Crossover is going strong, and they have established a way to keep things working. There are also several forks that utilize PlayonMac, or another service to run x86 programs in Catalina. In short, pay to use CrossOver, or use an alternative. There is a fork of Wineskin (WineskinServer), and as mentioned, PlayOnMac works. There are several other alternatives out there. 
 + 
 +https://www.reddit.com/r/wine_gaming/comments/kc6grp/catalina_big_sur_support/ 
 +https://github.com/Gcenx/WineskinServer 
 + 
 +=== GPU changes after incremental updates === 
 +  
 +After watching the [[https://dortania.github.io/OpenCore-Post-Install/universal/update.html#updating-macos|notes on the changes between each update]] of Catalina, it's very imperative to note what adjustments you'll need to make to ensure your GPU will play nice. Mostly it deals with DRM-related issues, and making sure your kexts are up to date. Do read it before making the switch. 
 + 
 +=== OpenCore Min/Max versions in config for APFS === 
 + 
 +I have to pin down the exact version change, but under UEFI → APFS, MinVersion and MinDate need to be set, otherwise your partitions won't be found. 
 + 
 +I set mine to -1 for now, as I don't know when I'd need to boot into an earlier OS now that I am full APFS. It is once again a reminder that once you go APFS, you're really locked in going forward. There is that line of delineation that starts at High Sierra. 
 + 
 +https://dortania-github-io.thrrip.space/OpenCore-Install-Guide/config.plist/kaby-lake.html#apfs 
 + 
 +==== Since Mojave 10.14 ====
  
 === New Bootloader === === New Bootloader ===
Line 105: Line 149:
 Nvidia stopped making Web Drivers for macOS in Mojave. Bickering aside, you now need to use an AMD GPU or an onboard Intel/AMD GPU for native support. There are ways to patch macOS to use the Nvidia GPU still, but save yourself a headache and get natively supported GPUs. Nvidia stopped making Web Drivers for macOS in Mojave. Bickering aside, you now need to use an AMD GPU or an onboard Intel/AMD GPU for native support. There are ways to patch macOS to use the Nvidia GPU still, but save yourself a headache and get natively supported GPUs.
  
-==== Since High Sierra Final 13.6.5 ====+==== Since High Sierra 10.13 ====
 <note warning>The main change to keep in mind is: APFS <note warning>The main change to keep in mind is: APFS
  
Line 126: Line 170:
 Two kexts that stick out are WhateverGreen (GPU patcher), and ALCAudio (On-board Audio patcher). Two kexts that stick out are WhateverGreen (GPU patcher), and ALCAudio (On-board Audio patcher).
  
-Lilu Pliugin list+Lilu Plugin list
 https://github.com/acidanthera/Lilu/blob/master/KnownPlugins.md https://github.com/acidanthera/Lilu/blob/master/KnownPlugins.md
  
 https://www.tonymacx86.com/threads/solved-is-lilu-kext-required.244136/ https://www.tonymacx86.com/threads/solved-is-lilu-kext-required.244136/
 +
 +===== Upgrading your OpenCore installation =====
 +
 +Probably the toughest part about Hackintoshing is upgrading. Not because it's difficult, but because you forget about how you did everything once it's up and going. You can keep up with the updates, but you may run into headaches every time when something changes. Instead of keeping up with the latest updates, what I suggest is create your Hackintosh on the final version of the previous macOS. So, in this case, build on Catalina, since Big Sur is current and actively changing. The reason is, things will break on updates. There's no need to be on bleeding edge here unless you like punishment.
 +
 +How does this relate to upgrading OpenCore?
 +
 +Don't touch OpenCore until you are ready to update to the next OS build. There will be more of a learning curve on the changes, but it's one slightly larger headache every year, not once smaller every month. That is why I am writing this to help myself, but also to help you out.
 +
 +==== Prepping for the upgrade ==== 
 +
 +  * Use git to download the tools you'll use to update/compare configs. Reason being is, you can save time by just running a git pull in the directory to refresh the latest files.
 +  * Block out a weekend afternoon, or plan to work two nights in a row. Just to give yourself the ample time needed.
 +  * Grab yourself a copy of the latest version of OpenCore that the sanity checker has up to date on its website. Alternatively, you can rely on just the validator I will mention, but the sanity checker does a great job of its namesake.
 +  * Run a backup however you please. Time Machine, or a full clone via Carbon Copy Cloner.
 +  * Make a copy of your current config.plist. Name it config.plist.old
 +  * Boot in and mount your EFI
 +  * Copy over the essential files per this guide -
 +  * Open up propertree. Open your config.plist, and the sample plist (In the OpenCore docs folder) side by side.
 +  * Run the OCValidate tool. Use the sample plist as your source to check against.
 +  * Compare the differences listed in the first group. Go line by line, and add what is missing to your config.plist
 +  * Compare the differences listed in the second group. Go line by line, and remove what is listed in your conflig.plist
 +  * Once done, save your config.plist. Go to the sanity checker, and run it based on your CPU and OpenCore version.
 +  * Make any corrections as needed, while using the guide for help on any changes you are confused on.
 +  * Once validated, reboot!
 +  * Note any issues on boot. If you can't boot, use your Vanilla disk as the bootloader and boot into your main disk.
 +  * If you can boot in, Mount the EFI. Check to see if there are any text files. Read the latest one for errors.
 +
  
 ===== Tips/Fixes I've run into ===== ===== Tips/Fixes I've run into =====
 +
 +==== Give yourself a "Vanilla" boot disk as an emergency ====
 +
 +Once you get macOS installed, and tune your OpenCore configuration to have no errors, make a backup!
 +
 +Download Carbon Copy Cloner, and grab a USB 3.0 drive (minimum size of 32GB) and back it up to there. This ensures that if your working installation breaks when you test something, you have a working clean reference to come back to. After you run Carbon Copy Cloner, copy over the EFI folders to the new drive. 
  
 ==== Getting iMessage to work ==== ==== Getting iMessage to work ====
 +
 +=== New hotness, but really just updated for current macOS issues ===
 +
 +[[https://dortania.github.io/OpenCore-Desktop-Guide/post-install/iservices.html|The OpenCore Guide references a few more steps that you would need to take.]] Most of it carries over into Clover land. The biggest thing to watch out for is that your AppleID is integrated more. You may run the chance of blacklisting your account if you goof up too many times. I've never run into issues, but I've always started with a clean slate when I re-do my hack builds and have to change the serial number.
 +
 +The recommended clean out when running into iServices activation issues:
 +<code>sudo rm -rf ~/Library/Caches/com.apple.iCloudHelper* \
 +            ~/Library/Caches/com.apple.Messages* \
 +            ~/Library/Caches/com.apple.imfoundation.IMRemoteURLConnectionAgent* \
 +            ~/Library/Preferences/com.apple.iChat* \
 +            ~/Library/Preferences/com.apple.icloud* \
 +            ~/Library/Preferences/com.apple.imagent* \
 +            ~/Library/Preferences/com.apple.imessage* \
 +            ~/Library/Preferences/com.apple.imservice* \
 +            ~/Library/Preferences/com.apple.ids.service* \
 +            ~/Library/Preferences/com.apple.madrid.plist* \
 +            ~/Library/Preferences/com.apple.imessage.bag.plist* \
 +            ~/Library/Preferences/com.apple.identityserviced* \
 +            ~/Library/Preferences/com.apple.ids.service* \
 +            ~/Library/Preferences/com.apple.security* \
 +            ~/Library/Messages</code>
  
 === Outdated but useful === === Outdated but useful ===
Line 177: Line 276:
 https://www.tonymacx86.com/threads/how-to-fix-imessage.110471 https://www.tonymacx86.com/threads/how-to-fix-imessage.110471
  
-=== New hotness, but really just updated for current macOS issues === +==== (Legacy) Removing the PreBoot volumes from the Clover Bootloader (APFS volumes only) ====
- +
-[[https://dortania.github.io/OpenCore-Desktop-Guide/post-install/iservices.html|The OpenCore Guide references a few more steps that you would need to take.]] Most of it carries over into Clover land. The biggest thing to watch out for is that your AppleID is integrated more. You may run the chance of blacklisting your account if you goof up too many times. I've never run into issues, but I've always started with a clean slate when I re-do my hack builds and have to change the serial number. +
- +
-The recommended clean out when running into iServices activation issues: +
-<code>sudo rm -rf ~/Library/Caches/com.apple.iCloudHelper* \ +
-            ~/Library/Caches/com.apple.Messages* \ +
-            ~/Library/Caches/com.apple.imfoundation.IMRemoteURLConnectionAgent* \ +
-            ~/Library/Preferences/com.apple.iChat* \ +
-            ~/Library/Preferences/com.apple.icloud* \ +
-            ~/Library/Preferences/com.apple.imagent* \ +
-            ~/Library/Preferences/com.apple.imessage* \ +
-            ~/Library/Preferences/com.apple.imservice* \ +
-            ~/Library/Preferences/com.apple.ids.service* \ +
-            ~/Library/Preferences/com.apple.madrid.plist* \ +
-            ~/Library/Preferences/com.apple.imessage.bag.plist* \ +
-            ~/Library/Preferences/com.apple.identityserviced* \ +
-            ~/Library/Preferences/com.apple.ids.service* \ +
-            ~/Library/Preferences/com.apple.security* \ +
-            ~/Library/Messages</code> +
-==== Removing the PreBoot volumes from the Clover Bootloader (APFS volumes only) ====+
 https://www.insanelymac.com/forum/topic/326527-create-custom-entries-to-hide-preboot-and-recovery-apfs-volumes-fusion-drive-installation-with-clover-configurator/ https://www.insanelymac.com/forum/topic/326527-create-custom-entries-to-hide-preboot-and-recovery-apfs-volumes-fusion-drive-installation-with-clover-configurator/
  
Line 293: Line 372:
   * SS09 - Unknown   * SS09 - Unknown
   * SS10 - Unknown   * SS10 - Unknown
 +
 +=== Disable CFG-Lock ===
 +
 +Using both Apple config lock Quirks still did not unlock my CPUs, it resulted in a 'BORKED' setup where there was partial unlocking of cores. I followed the UEFITool steps outlined by the guide, and found the CFG Lock string in the latest BIOS. Using the modified grub EFI tool, run this string to unlock the CPUs:
 +
 +<code>setup_var_cv Setup 0x502 0x01 0x00</code>
 ==== Dell T3500 ==== ==== Dell T3500 ====
 http://t3500.mcdonnelltech.com/ http://t3500.mcdonnelltech.com/
  • computers/hackintosh.1600435126.txt.gz
  • Last modified: 2020/09/18 13:18
  • by localadmin