Leaderboard

Released August 28th, 2024. Build 24A5331b. Smooth update on Hackintosh, as usual. OCLP root patching required afterwards, also as usual. Same Clover r5159 setup for my Dell Latitude E7270 as used with initial beta3 version and posted here.

Released August 5th, 2024. Build 24A5309e. Smooth update on Hackintosh, as usual. OCLP root patching required afterwards, also as usual. Same Clover r5159 setup for my Dell Latitude E7270 as used with initial beta3 version and posted here. Post-install issue: As mentioned on other Hackintosh forums, after this update, the EFI partition hosting the bootloader setup no longer mounts properly using tools such a CloverConfigurator, OpenCoreConfigurator, etc. or the line command: sudo diskutil mount <disk id> where <disk id> is the disk reference of the EFI partition; for instance disk0s1. The command executes with apparent success but no EFI icon on the desktop and nothing in mounting point directory /Volumes/EFI which is just empty. admin@macbook-pro ~ % ls -la /Volumes/EFI total 2 drwx------@ 1 admin staff 0 Jan 1 1970 . drwxr-xr-x 6 root wheel 192 Aug 6 11:58 .. A workaround has been posted which consists of manually recreating the directory /Volume/EFI as a mounting point and then mount the EFI partition on it. This can be done as follows: 1) Identify EFI partition disk id: admin@macbook-pro ~ % sudo diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *240.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 <-- This is the EFI partition disk reference/id 2: Apple_APFS Container disk2 119.9 GB disk0s2 3: Apple_APFS Container disk1 120.0 GB disk0s3 [...] 2) If you've already attempted to mount the partition, unmount it, otherwise proceed directly to step #3 : admin@macbook-pro ~ % sudo diskutil unmount <disk id> (for instance disk0s1) This will remove the /Volumes/EFI mounting point. 3) Create EFI volume manually as mounting point: admin@macbook-pro ~ % sudo mkdir /Volumes/EFI 4) mount EFI partition on it: admin@macbook-pro ~ % sudo mount -t msdos /dev/disk0s1 /Volumes/EFI Executing: /usr/bin/kmutil load -p /System/Library/Extensions/msdosfs.kext Your EFI partition will then be mounted and its disk icon will appear on the desktop. Something has clearly changed with this beta 5 update, I suspect something to do with security or Gatekeeper and the mounting tools and/or methods previously used now need to be updated for Sequoia.

Released June 24th, 2024. Build 24A5279h. Available through OTA with @Lorys89's version of RestrictEvents v1.1.4 of June 2024 as long as your Apple account is registered for beta updates. RestrictEvents.kext.zip Failing that, install assistant package is available here. Straight update; a bit long to complete. No changes to bootpack used for beta 1.

Remember that bluetoolfixup active on config can cause ota update to fail, it is recommended that it is disable and restart and then look for update. Because if it fails with kext active, then download the full installer.

Released May 12th, 2025. Build 24F74. Bug fixes and security update. Safe to install on our Hackintosh platforms. Also released at the same time: macOS Sonoma Security Update 14.7.6 (Build 23H626) macOS Ventura Security Update 13.7.6 (Build 22H625) View full article

Post your EFI Might need to patch the pre-allocated DVMT, see here Dell don't have the option in the BIOS to set it conveniently like HP

There is substantial documentation on the Dortania site. Failing that, you may opt for a Clover classic installation on which you'll apply OCLP patching; that's what I do with my unsupported laptops.

For Sonoma, it's exactly the same as for Ventura which dropped official support for Haswell platforms; as such, no native support for Haswell graphics HD4400/4600. In addition, Sonoma dropped support for legacy Broadcom wireless cards. See our previous communications on these matters. I would expect there are existing threads about installing/running Ventura and/or Sonoma on Haswell laptops, whether Dell or otherwise. https://osxlatitude.com/forums/topic/17636-macos-ventura-is-out https://osxlatitude.com/forums/topic/18228-macos-sonoma-140-beta-1-early-feedback-and-findings https://osxlatitude.com/forums/topic/19456-oclp-patcher-support-for-legacy-broadcom-wireless-cards-in-sonoma https://osxlatitude.com/forums/topic/19519-macos-sonoma-is-out https://osxlatitude.com/forums/topic/20304-macos-sonoma-144-update-is-out https://osxlatitude.com/forums/topic/19730-wifi-in-sonoma-patching-for-legacy-broadcom-wireless-cards/ OCLP brings everything back to life: graphics acceleration and wireless (provided you have the required card).

Released August 20th, 2024. Build 24A5327a. Smooth update on Hackintosh, as usual. OCLP root patching required afterwards, also as usual. Same Clover r5159 setup for my Dell Latitude E7270 as used with initial beta3 version and posted here.

Baio77 you are a genius. I searched for this solution for so a long time! thanks a lot for your precious help and also your clear explanation of what you did to make it works!!

Thanks a lot for your help Baio77 ! So I booted using your complete EFI folder. It seems to work much better than my current EFI, also the touchpad is working great now. MacBook Pro.ioreg Here is my new ioreg

It should come as no surprise that the same issue that initially affected legacy Broadcom cards in macOS Sonoma now applies to freshly released macOS Sequoia beta. The OCLP tool will need to be updated for Sequoia.

Never seen this KP on "watchdog" before; that's a first. Can't see any obvious mistake in your setup arrangements or config file. Nothing wrong with the patched ACPI tables or the injected kexts. So, I'd say the issue is somewhere in your OC config, maybe the quirks. I'm not too convinced by those boot args: agdpmod=vit9696 (isn't this for external GPU?) gfxfcms=1 (that's invalid, it's igfxfcms=1) and igfxdvmt (it's for Ice Lake platforms). I don't believe you need any of those at all. You would need to read the Whatevergreen documentation: https://github.com/acidanthera/WhateverGreen/tree/master https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md Regarding the properties you inject for HD530, faked KBL device id and injected KBL framebuffer layout id look Ok to me. Not so sure about the injected HDMI 2.0 properties but I can't see them do any harm. Re: quirks, a few suggestions: Booter: enable "SyncRuntimePermissions" Kernel: I think you can disable "AppleXcpmCfgLock" UEFI: not sure if you really need "RequestBootVarRouting" Kernel -> Scheme set to Fuzzy match. Do you really need this? Pretty sure you can also leave KernelArch to auto.

Released July 10th, 2024. Build 24A5289g. Straight update; no change to the bootpack. Some significant changes to Gatekeeper with this 3rd beta: it can no longer be disabled with command sudo spctl --master-disable; the command is deprecated. Apple has decided to drop support for global subsystem assessment which, until now, allowed users to disable Gatekeeper and allow all apps to be run without assessment. See the built-in manual for details (man spctl). https://developer.apple.com/documentation/devicemanagement/systempolicycontrol Here is my revised Clover r5159 setup for my Skylake/HD520 Dell Latitude E7270 laptop, now including the settings to support legacy wireless services after OCLP Modern Wireless Networking root patching. E7270_Clover_pack_Seq_15.0.b3.zip

This message is usually associated with absence of disk or no boot sector. 1st make sure that the disk is visible/detected in BIOS settings. If it is and it remains non-bootable, you probably did not install your newer Clover version with the suitable settings (legacy vs. UEFI for instance). You'll have to recover your installation through an alternative boot device, whether a USB key or an external USB disk for instance. It dates back to Oct 2019 so it's a bit old now but here, you'll find details of Clover version and Clover settings that I used for Catalina on the Latitude E7250. Then you may look at my E7270 guide for Clover settings used to install more recent versions of Clover and macOS. Recommended BIOS settings for the E7250 (and E7270) are available at the top of the E7xxx forum section.

currently I'm running Monterey, with no problems, on my precision 5510. but more on that in a second. I just got a 5530 yesterday, and spent the day trying to install macos on it. but, it kept getting stuck just trying to boot into the installer. kernel panics kept happening. IONVMEFamily.kext is where it was failing. after doing some research, there are 2 models of ssds that are having issues with that kext. the Samsung PM981, and the micron 2200s. looking into the drives that came on both my laptops, the 5530 came with the micron ssd, and looking back at what drive came in my 5510, i found out it originally had the Samsung one. obviously the samsung drive is not currently in my 5510. and I have a replacement ssd on order for my 5530. Hopefully that fixes my problem. just sharing my experience to point out something to check if your having NVME errors, as it seems from my experience, the trouble drives were shipped on these laptops. https://dortania.github.io/OpenCore-Install-Guide/macos-limits.html#storage-support otherwise for troubleshooting purposes, if you think it might be related to the wireless card, disable the related kexts in your config.plist, and see if the errors resolve themselves.

Last updated: 15 Jun 2024 We occasionally get questions about compatible graphics cards, so these articles should be useful for Hackintoshing purposes: 1) Best budget (under $50) graphics cards in 2024 Some of those cards are compatible with macOS up to High Sierra. Only a handful support Metal and Mojave/Catalina/Big Sur, i.e. Kepler architecture for nVidia (e.g.: GeForce GT 710) and GCN1.0 architecture for AMD (e.g.: AMD R5 240). And remember that, since Monterey, macOS dropped all support for nVida cards. 2) Best low-profile single-slot graphics cards for Small Form Factor (SFF) PCs in 2024 All those cards are compatible with late versions of OS X/recent versions of macOS. Afaik, all meet the minimum requirements for Metal but caution with nVidia cards since Mojave/Catalina/Big Sur only support Kepler models and, since Monterey, macOS dropped all support for nVida cards. 3) Best 1080p gaming graphics cards under $150 Those are good and reasonably priced cards, compatible with late versions of OS X/recent versions of macOS. Some do not need dedicated power supplies and will draw power from the PCIe bus. Afaik, all meet the minimum requirements for Metal but, again, caution with nVidia cards in Mojave/Catalina/Big Sur since those only support Kepler models and, since Monterey, macOS dropped all support for nVida cards. The site offers other "best graphics cards..." articles like "under $100", "under $200", etc. All available through a basic search.

List of dropped platforms only extends to Intel 8th gen. Amber Lake MacBookAir8,1 this year, all other platforms officially supported by Sonoma remaining supported in Sequoia. Good news for Skylake platforms: since KBL graphics drivers are retained, SKL graphics remain supported through the same patches used for Ventura and Sonoma. On the wireless front, OCLP patcher will need to be updated for Sequoia so that legacy Broadcom cards are supported again. Other than that, nothing much to report after just a brief spell with Sequoia 1st beta other than it feels a little more responsive than Sonoma and there are odd bugs (for example, an empty white window that may pop up at startup and cannot be closed or occasional mouse selection trailings). Installation on my Skylake Latitude E7270 was very straightforward and totally painless: from Sonoma, I updated Clover to r5159 (revised to boot Sequoia), changed my Clover config's SMBIOS to MBP15,2 (necessary), disabled the BlockSkywalk kernel & kext patch (necessary) and added boot arg -lilubetaall (also necessary). I then rebooted Sonoma, downloaded the Sequoia beta installation package and launched the installation targeting a dedicated Sequoia volume (previously created in Disk Utility). That was it, after a couple of reboots, I was offered the Sequoia setup screens and was presented with the Sequoia desktop. Resources: Sequoia beta 1 installation package can be downloaded here. Clover_r5159.pkg.zip E7270_Clover_pack_Seq_15.0.b1.zip Working: graphics acceleration with same KBL settings as in Ventura/Sonoma brightness control HDMI output mini-DP output touchscreen touchpad (after replacing VoodooPS2Controller's PlugIn "VoodooInput" by 1Revenger1's version v1.1.5 due to changes in Sequoia as explained here. 1Revenger1_VoodooInput_v1.1.5.zip) audio (incl. DP/HDMI audio) LAN Apple (Broadcom) BCM94360CS2 Bluetooth USB ports SD card reader full CPU power management sleep & wake (having disabled hibernation) Not working: Apple (Broadcom) BCM94360CS2 wireless, as per Sonoma. We'll have to wait for the OCLP patcher to be updated for Sequoia. Meantime, it's important not to boot with the BlockSkywalk kernel & kext patch and/or with AMFI prevention or Sequoia will KP/fail to boot. Things looking different in System Information->Software->Extensions: injected kexts are listed and everything is listed as loaded.

Hi @Lorys89 yes! force polling work too, but I think force polling will take more resource, so I decide to try activate touchpad with Interrupt mode.

Revised wireless kexts for Sonoma 14.4, the previous ones not providing wifi service beyond Sonoma 14.3. OCLP 1.4.1 or later required too. Wifi_kexts_Sonoma_14.4.zip

Further to my communication of July 2023 and Jake Lo's post above, I can confirm that Clover r5157 now supports blocking of vanilla kext IOSkywalkFamily kext which is required to support and use "legacy" wireless cards in Sonoma, i.e. cards that worked perfectly, natively or not, up to Ventura. This is basically equivalent to the kext exclusion available in OpenCore but limited to IOSkywalkFamily kext. The blocking is available as kext patch called BlockSkywalk and is integrated to latest versions of CloverConfigurator too. Process with Clover is therefore as follows: update or install Clover r5157 (versions r5155 and r5156 are supposed to provide the patch too but I found that it was not working and resulted in a freeze at startup) apply/enable Kernel & Kexts patch BlockSkywalk in your Clover config either add boot arg -amfi_get_out_of_way=1 in your config or add AMFIPass kext provided above by Jake to your kexts/14 or kexts/Other Clover folder and add boot arg -amfipassbeta boot arg in your Clover config add kexts IOSkywalk (renamed copy of older version of IOSkywakFamily kext) and IO80211FamilyLegacy kexts provided above by Jake to your kexts/14 or kexts/Other Clover folder you can keep SIP disabled with CsrActiveConfig set to 0xFEF, I found there was no need to change to, say, 0x803 install and run OCLP Patcher and apply Networking: modern wireless or Networking legacy wireless (depending on the card) root patch which should be automatically offered reboot and enjoy recovered wireless services out of your PCIe wireless card Clover_r5157.pkg.zip Clover Configurator.zip Example with the Apple BCM94360CS2 card fitted with an adapter board to the M.2 WLAN slot of my Dell Latitude E7270: or (as text): <key>BlockSkywalk</key> <true/>

Here is my working EFI OC097 for Latitude 5490 (i5-8350U, Intel Wifi), for Sonoma. Due to file uploading size limitation, AirportItlwm.kext (V1.23 Alpha for Sonoma) is not included. Both HDMI port and Display Port via USB-C port are working. You may give it a try. This EFI was based on this GitHub repository: juanpy0223/Dell-Latitude-5490-8th-gen. My bios is still 1.26 and did not update to the latest (V1.32) since the latest BIOS may prevent the CFG LOCK changing. Also once updated, it can not go back to earlier BIOS. I experienced this with my Latitude 5400. If you are able to disable CFG LOCK with 1.32 BIOS and set DVMT to 64MB (instruction is in the link above), then you can make the following changes to the Config.plist: - Root->Kernel->AppleCpuPmCfgLock = FALSE (for native CPU power management) - Remove the following two properties from your iGPU's DeviceProperties (PciRoot(0x0)/Pci(0x2,0x0) for my case): framebuffer-fbmem framebuffer-stolenmem Goodluck! DELL-5490-OC097.zip

OPENCORE - Sonoma Supports Sonoma Follow BIOS Configuration above Working: full graphics acceleration on Intel HD520 iGPU, including brightness control (F5 and F6) multi-display with DisplayPort (Video & Audio) audio, microphone input and headset output (F8 and F9) Mute button IS working by Human7900 GigEthernet LAN connection wireless and bluetooth with any compatible card (a DW1560 in my case, no Whitelisting) left and right USB ports including USB Type-C integrated webcam CPU power management sleep (Lid, Energy Saver settings, Apple menu, PWR button) & wake (Lid, PWR button) battery management keyboard and touchpad keyboard backlight (Fn + F3) touchpad with gestures, mouse buttons (can be disable with PrtScr key) RTS522a microSD card reader Not working: Trackpoint and mouse buttons Finger Print reader Wifi button Installation: Download macOS Sonoma app Format a 16GB USB drive (GUID / Extended (Journaled)) Create USB Installer with createinstallmedia command Download attached folder and rename as EFI Mount EFI partition and add EFI folder Configure BIOS setting according to guide Boot with USB installer Complete installation Post Installation: Mount EFI partition of newly installed drive and copy EFI folder over Update / Change in Config.plist under PlatformID->Generic (use genSMBIOS or Hackintool.app) MLB, ROM, SystemSerialNumber and SystemUUID Resources: https://dortania.github.io/OpenCore-Install-Guide/ https://github.com/VoodooSMBus/VoodooRMI https://github.com/OpenIntelWireless/itlwm https://github.com/cholonam/Sinetek-rtsx https://github.com/0xFireWolf/RealtekCardReader/releases Updated to OC 0.9.5 Note: Config is set for Broadcom DW1830 If you have Intel, rename Config-IntelWifi to Config.plist (not tested) SMBIOS, ig-platform-id, device-id, USBPorts kext set to MacBookAir8,1 to support Sonoma Since Sonoma has dropped all/most of the Broadcom wireless we've been using, you'll need to patch the system using OpenCore Legacy Patcher.app (currently using 1.1.0) For Broadcom wireless system only, see here for patching Multiboot from OC picker is also working! HP840G3_OC_0.9.5-Sonoma.zip

My Dell's specs: CPU: Intel Core i5 4210U RAM: 8GB DDR3 Graphics: Intel HD 4400 SSD: 512GB (macOS) HDD: 320GB (Kali Linux + Windows 11.5) Working: Graphics acceleration Patch OCLP 0.6.9 Dev Brightness control WiFi. I'm using airporlitlwm.kext version 5 Sonoma Beta All USB 2.0 and 3.0 ports work Bluetooth, with IntelBluetoothFirmware/Injector Audio, incl. integrated microphone Sleep Ethernet HDMI output Touchpad Integrated camera Card reader MacBook Air.ioreg

Hi, there is the guide written by JakeLo in the dell installation guide section: That should be the right place where to start from

Here's the OpenCore EFI for my Dell Latitude 7400. Everything works great. macOS Monterey 12.6.3 configured for Intel WiFi/BT: Dell 7400 OC 0.8.9 Monterey IntelWiFi If you have BCM card remove the kexts Airportitlwm, IntelBluetoothFirmware and BlueToolFixup. Ventura tested and not working well with Intel 9560NGW, if you have Intel 8260/8265 it will work flawlessly. Enjoy! My specs are: Whiskey Lake i7-8665U CPU Intel UHD 620 graphics 14" FHD IPS touchscreen 16GB DDR4 Realtek ALC295 Audio Intel 9560NGW wireless

OPENCORE - Ventura Supports Ventura Follow BIOS Configuration above Working: full graphics acceleration on Intel HD520 iGPU, including brightness control (F5 and F6) multi-display with DisplayPort (Video & Audio) audio, microphone input and headset output (F8 and F9) Mute button IS working by Human7900 GigEthernet LAN connection wireless and bluetooth with any compatible card (a DW1560 in my case, no Whitelisting) left and right USB ports including USB Type-C integrated webcam CPU power management sleep (Lid, Energy Saver settings, Apple menu, PWR button) & wake (Lid, PWR button) battery management keyboard and touchpad keyboard backlight (Fn + F3) touchpad with gestures, mouse buttons (can be disable with PrtScr key) RTS522a microSD card reader Not working: Trackpoint and mouse buttons Finger Print reader Wifi button Installation: Download macOS Ventura app Format a 16GB USB drive (GUID / Extended (Journaled)) Create USB Installer with createinstallmedia command Download attached folder and rename as EFI Mount EFI partition and add EFI folder Configure BIOS setting according to guide Boot with USB installer Complete installation Post Installation: Mount EFI partition of newly installed drive and copy EFI folder over Update / Change in Config.plist under PlatformID->Generic (use genSMBIOS or Hackintool.app) MLB, ROM, SystemSerialNumber and SystemUUID Resources: https://dortania.github.io/OpenCore-Install-Guide/ https://github.com/VoodooSMBus/VoodooRMI https://github.com/OpenIntelWireless/itlwm https://github.com/cholonam/Sinetek-rtsx https://github.com/0xFireWolf/RealtekCardReader/releases Updated to OC 0.9.5 Note: Config is set for Broadcom DW1830 If you have Intel, rename Config-IntelWifi to Config.plist Multiboot from OC picker is also working! HP840G3_OC_0.9.5.zip HP840G3_OC_0.8.5_Ventura.zip

Add this SSDT and rename patch to Config file Comment: Rename GPRW to XPRW Find:47505257 02 Replace:58505257 02 If still not work, go into BIOS and disable wake on LAN / Wifi SSDT-GPRW.aml.zip

I was asked if the above trick was deprecated because DVMT pre-alloc can be bypassed with some Whatevergreen patches but sometimes it's still needed. For example, you want support for 4k display, DVMT will need to be increased and the bypass won't work. It's not recommended for everyone since it can brick your system if done incorrectly. But you can still reset it back to default by setting the BIOS to load the default or remove all the batteries for a period of time.

Jake Lo THANKS a lot for your time and your help!!!! your are just a fantastic person and a genius tech guy! Your knowledge is just facinating!

so using the OC files you uploaded but only changing the DSDT with mine will cause this issue? But with the other DSDT, you don't have brightness control? Let me compare them, see if it need extra patching or remove some....

As a nice complement to our wireless inventories, there's a pretty good summary of Broadcom BCM4350, BCM4352 and BCM4360 cards here: https://khronokernel-7.gitbook.io/wireless-buyers-guide/types-of-wireless-card/m2 By far and large, cards are size 2230 and Key A/E with very limited Key E models. As a recap: Broadcom BCM4360 (14e4:43a0): Fenvi BCM94360NG Subsys id 106b:0117 BT id 05ac:828d Key A/E , size 2230 supported OOB up to Ventura Broadcom BCM943602 (14e4:43ba): Dell DW1830 BT id 05ac:6410 Key A/E, size 3030 3 x antennas Broadcom BCM94352 (14e4:43b1): Fenvi AC1200 Key A/E, size 2230 Dell DW1560 Subsys id 1028:0019 BT id 05ac:216f Key A/E, size 2230 AzureWave AW-CB162NF BT id 13d3:34xx Key E, size 2230 seems quite rare Foxconn T77H543 Lenovo 04X6020 Lite-On WCBN802B Key E, size 2230 Broadcom BCM94350: (see our dedicated guide on those) Dell DW1820A (Key A/E, size 2230) Lenovo Foxconn T77H649 (Key A/E, size 2230) Lite-On WCBN808B (Key A/E, size 2230)

I found this: https://www.insanelymac.com/forum/topic/329390-amd-firepro-w5100-on-macpro-51-high-sierra/ Seems that the card will work with these mods, you will just have a blank boot screen until the system starts. I'm planning to change my FirePro W5100 with a Quadro M1200 because I need CUDA for what I'm working on.

'found an old Realtek RTL8139D PCI card whist clearing out old computer stuff. It's an ancient Connectland CR-CNL-FAST-R model dating back to 2008/2009... http://www.connectland.eu/products/fiche/category_id/133/culture/en/id/167/name/10-100-mbps-fast-ethernet-pci-card Gave it a shot in my old Vostro200 running High Sierra and Mojave. Installed the old IONetworkingFamily fat-binary kext from osx86.net and the card still works under macOS! First drivers for this card were released for OS X 10.1/10.2! IONetworkingFamily.kext.zip Note that the card is not supported by Mieze's RTL810x FastEthernet driver. Initially, I only installed the RTL8139 kext in /L/E and that brought the card to life but no traffic passed. The card only fully worked once I actually installed the entire IONetworkingFamily kext in /L/E, without touching the vanilla equivalent in /S/L/E. There must have been some dependancies... After the usual permissions repair + cache rebuild + reboot, the card was 100% functional. There goes an old 32bit PCI (not PCIe) card in macOS High Sierra and Mojave! Must work in all previous versions from Snow Leopard to Sierra too. vostro200:~ admin$ lspci -nn [...] 00:19.0 Ethernet controller [0200]: Intel Corporation 82562V-2 10/100 Network Connection [8086:10c0] (rev 02) [...] 04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 10) Edit: 17 Jan 2021 osx86.net now dead. Old link to file was: https://osx86.net/files/file/3172-realtek-rtl8139/

Hi all, I am very excited to finally hack this world famous GPU mining motherboard and pleased to share with you all the clover bootpack. Specifications Asrock H81 BTC Pro Ver 2.0 4th Gen 3.5 GHz i3-4330 8 GB DDR3 1600 MHz Memory Intel Graphics HD 4600 HDMI output on 24-inch LED Monitor (1920 x 1080) OpenCore Bootpacks Big Sur Support for Mac OS Big Sur 11.0.1 (OpenCore 0.6.3) OC-11.0.1.zip Clover Bootpacks Big Sur Support for Mac OS Big Sur 11.0.1 (Clover 5126) CLOVER-10.15.7.zip Catalina Support for Mac OS Catalina 10.15.7 (Clover 5126) CLOVER-10.15.7.zip Support for Mac OS Catalina 10.15.4 (Clover 5116) CLOVER-10.15.4.zip Support for Mac OS Catalina 10.15.1 (Clover 5070) CLOVER-10.15.1.zip Support for Mac OS Catalina 10.15 (Clover 5070) CLOVER-10.15.zip Support for Mac OS Catalina 10.15 Beta (19A471t) (Clover 4945) CLOVER-10.15 Beta (19A471t).zip Mojave Support for Mac OS Majave 10.14.6 (Clover 4945) CLOVER-10.14.6.zip Support for Mac OS Majave 10.14.5 (Clover 4934): CLOVER-10.14.5.zip Support for Mac OS Majave 10.14.4 (Clover 4910): CLOVER 10.14.4.zip Support for Mac OS Mojave 10.14 Beta 4 18A326h (Clover 4586): CLOVER 10.14 Beta 4.zip Support for Mac OS Mojave 10.14 Beta 18A293U (Clover 4517): CLOVER 10.14 Beta.zip High Sierra Support for Mac OS High Sierra 10.13.6 (Clover 4635) CLOVER 10.13.6.zip Support for Mac OS High Sierra 10.13.4 (Clover 4428) CLOVER-V4.zip Support for Mac OS High Sierra 10.13.2 (Clover 4360) CLOVER-V3.zip Support for Mac OS High Sierra 10.13.1 (Clover v4293) CLOVER-V2.zip Support for Mac OS High Sierra 10.13.1 (Clover v4293) with Intel Graphics: CLOVER-Intel.zip Support for Mac OS High Sierra 10.13.1 (Clover v4293) with ATI Graphics: CLOVER-ATI.zip Credits goes to Jake Lo and Bronx Teck OpenCore & Clover Notes on Mac OS Big Sur 11.0.1 (1) Everything works (2) Updated all kext to latest version Clover Notes on Mac OS Catalina 10.15.7 (1) Everything works (2) Updated all kexts to latest version Clover Notes on Mac OS Catalina 10.15.4 (1) Everything works (2) Updated Lilu.kext, VirtualSMC.kexts and Whatevergreen.kext to latest version Clover Notes on Mac OS Catalina 10.15.1 (1) Everything works (2) Updated Whatevergreen.kext to latest version Clover Notes on Mac OS Catalina 10.15 (1) Everything works (2) Updated clover, efi drivers & kexts to latest version (3) Swapped from FakeSMC to VirtualSMC Clover Notes on Mac OS Catalina 10.15 Beta (19A471t) (1) Everything works (2) Whatevergreen.kext requires graphics injection from Clover Clover Notes on Mac OS Mojave 10.14.5 (1) Everything works (2) Mac OS 10.14.5 Update Installer now complaints "Cannot Find Installer Resources". A very crude workaround is to remove all other hard drives except for the Mac OS hard drive. Let me know if anyone find a solution to this without having to open the casing each time we want to update. Clover Notes on Mac OS Mojave 10.14.4 (1) Everything works (2) Whatevergreen.kext now autodetects the graphics card. Make sure no graphics injection is done in Clover. Clover Notes on Mac OS Mojave 10.14 Beta 4 18A326h (1) Everything works (2) Updated from Mac OS Majave 10.14 Beta 18A293U via Software Update in the System Preference. Clover Notes on Mac OS Mojave 10.14 Beta 18A293U (1) Everything works including sleep. (2) Dedicated GPU Radeon Pro 560 not displaying on monitor. May need to wait for WhateverGreen.kext to be updated with support for this Mac OS version. Clover Notes on Mac OS High Sierra 10.13.1 (1) Everything works including sleep. (2) Updated all kexts to latest versions (3) Added IntelGraphicsFixup.kext and Shiki.kext (4) Combined all ATI & Intel GPU configs & kexts into single bootpack for multi GPU support (5) For those that need to update 10.13 to 10.13.1, you will need to install the latest clover (version 4293 is the one I used). If there are error messages, you may try to remove EmuVariableUefi-64.efi from Clover EFI temporarily, clear NVRAM using sudo nvram -c in terminal, download the update directly from apple website and install. Clover Notes on Mac OS High Sierra 10.13.2 (1) Everything works including sleep. (2) Updated all kexts to latest versions (3) For those updating from 10.13.1 to 10.13.2, you will need to install the latest clover and lilu including plugins (or download latest bootpack above) as well as download and install the update directly from apple website. Updating via App Store doesnt seem to work for me as I get the mkpg not found error message after reboot. Clover Notes on Mac OS High Sierra 10.13.4 (1) Everything works including sleep. (2) Updated all kexts to latest versions (3) For those updating from an earlier version of 10.13 to 10.13.2, you will need to install the latest clover and lilu including plugins (or download latest bootpack above) as well as download and install the update directly from apple website. The OS X installer will reboot several times. Clover Notes on Mac OS High Sierra 10.13.6 (1) Everything works including sleep. General Notes (1) The UEFI Bios does not detect Clover EFI natively. For first boot into Mac OS, you will need to boot Clover EFI using the Installer USB. In order to add Clover EFI into UEFI Bios, you will need to manually add it using the Clover UEFI shell using the following command:- (a) bcfg boot add 3 fsX:\EFI\CLOVER\CLOVERX64.EFI "Clover" (You will need to replace X with the location of your Clover EFI partition. This is shown in the list when you first enter the UEFI shell) (b ) Lastly, do bcfg boot mv 3 0 to move the Clover boot order to the first. (2) I found that this motherboard is very compatible with Mac OS and patched DSDT / SSDT is not required. Notes on Mining (1) As all you miners know, this motherboard can take up to six (6) GPUs, I have yet to test additional GPU on the PCIEx1 slots. At the moment, the single GPU that i'm using is installed on the PCIEx16 slot. I will test it once I have opportunity to get additional GPU. In the mean time, for those miners who already have this motherboard in their rig and are already using Windows or Linux, Mac OS may be a good OS to try since some miners (like ethereum's ethminer) are also released for Darwin and both NVIDIA and ATI have provided drivers for their latest GPUs. This does open up a good possibily of using Mac OS for GPU mining! (2) I was able to use the dedicated RX560 GPU for both as primary display as well as for mining. However, it causes the system to slow down and created artifacts when I rebooted / shutdown. I was able to make the system more stable by using the integrated HD4600 GPU as primary display and the dedicated RX560 GPU for mining. In order to use both integrated GPU and dedicated GPU, both Intel and ATI need to be injected by Clover. In the case of ethereum miner, ethminer was able to recognized all GPU but I only selected the RX560 for mining. This made the system more stable. (3) [10-11-2017] I just installed a third old AMD Radeon HD 7750 GPU on the first PCIEx1 slot and am very happy to see that Mac OS recognized it straight away. In the case of ethereum miner, ethminer was able to recognized all GPU. Attached pictures below:- (4) One of my main concern is I am still not able to get HWMonitor to show GPU temperature which is very important to monitor the current health of the GPUs. We would not want the GPU to overheat due to unforeseen reasons. Let me know if you are able to solve this issue. (5) During my discussion with crew member Rhyker, we were discussing on ways to tune the GPU from within Mac OS. As you know, currently the manufacturer only provide tuning software for Windows and to a limited extend Linux. We were thinking of running Windows under a virtual machine to access the GPU tuner to tune the GPUs. However, based on my last attempt, accessing native GPU from a virtual machine is still not possible although there are projects that are attempting to do this. Let me know if this idea is workable. Let me know if the clover bootpack works for you.

***Codec Verbs Info*** 071CXY X = Default Association Values: 1, 2, 3, 4, 5, 6, 7, 8, 9, a, b, c, d and f Y = Sequence Values: Always set this to '0' because Apple dont use analog multi outputs in their codec. 071DXY X = Color: Color of the jack Values: Unknown 0 Black 1 Grey 2 Blue 3 Green 4 Red 5 Orange 6 Yellow 7 Purple 8 Pink 9 Reserved A-D White E Other F Y = Misc - Jack detect sensing capability Values: 1 for Internal Devices(Speaker etc.,) and 0 for External Devices(Headphones etc.,) 071EXY X = Default device - Intended use of the Jack Values: Speakers 1 HP Out 2 CD 3 SPDIF Out 4 Digital Other Out 5 Modem Line Side 6 Modem Handset Side 7 Line In 8 AUX 9 Mic In A Telephony B SPDIF In C Digital Other In D Reserved E Other F Y = Connection type - indicates the type of physical connection Values: Unknown 0 1/8 stereo/mono 1 1/4 stereo/mono 2 ATAPI internal 3 RCA 4 Optical 5 Other Digital 6 Other Analog 7 Multichannel Analog (DIN) 8 XLR/Professional 9 RJ-11 (Modem) A Combination B Other F 071FXY X = Port Connectivity - indicates the external connectivity of the Pin Complex. Software can use this value to know what Pin Complexes are connected to jacks, internal devices, or not connected at all. 00b - The Port Complex is connected to a jack (1/8, ATAPI, etc.). 01b - No physical connection for Port. 10b - A fixed function device (integrated speaker, integrated mic, etc.) is attached. 11b - Both a jack and an internal device are attached. Y = Location Location indicates the physical location of the jack or device to which the pin complex is connected. This allows software to indicate, for instance, that the device is the “Front Panel Headphone Jack” as opposed to rear panel connections. Details: Convert the 2 digit hex number to binary. Pad the front with zeros to make it 8 dgits. Example: Code: 0x02 = binary 10 = 00000010 8 digit binary Reading the bits from left to right: Port Connectivity bits 7:6 ----------------------------------------------------------- 00 - Port is connected to a Jack 01 - No External Port -or- No physical connection for Port** 10 - Fixed Function/Built In Device (integrated speaker, mic, etc) 11 - Jack and Internal device are attached Location Part 1 - bits 5:4 ----------------------------------------------------------- 00 - External on primary chassis 01 - Internal 10 - Separate chassis 11 - Other Location Part 2 - bits 3:0 ----------------------------------------------------------- The meaning depends on Location Part 1 00 0000****N/A 00 0001** Rear 00 0010** Front 00 0011** Left 00 0100** Right 00 0101** Top 00 0110** Bottom 00 0111** Special (Rear panel) 00 1000** Special (Drive bay) 01 0000** N/A 01 0111** Special (Riser) 01 1000** HDMI 01 1001** ATAPI 10 0000****N/A 10 0001** Rear 10 0010** Front 10 0011** Left 10 0100** Right 10 0101** Top 10 0110** Bottom 11 0000** N/A 11 0110** ? 11 0111** Inside Mobile Lid (example: mic) 11 1000** Outside Mobile Lid ************Bits Hex******76 54 3210 ------------------- 71cf01 = 00 00 0001 - Port has a jack - It is External - Rear Location 71cf02 = 00 00 0010 - Port has a jack - It is External - Front Panel Location 71cf59 = 01 01 1001 - No External Port - ATAPI 71cf18 = 00 01 1000 - Port has a jack - External - HDMI 71cf90 = 10 01 0000 - Built In Device - Internal - N/A ******** |**|**|||| ******** |**|**|--------- Location part 2 ******** |**|------------ Location part 1** ******** |--------------- Port Connectivity

CHAPTER -2 PATCHING XML FILES: ***Platforms and Layoutxx file Patch Explanation*** COMPRESSING AND UNCOMPRESSING ZLIB FILES OF PLATFORM AND LAYOUT XML: From 10.8 or later, the xml files are compressed to zlib format. We have to uncompress them to edit the files. After editing, again we have to compress it back to zlib. For Compressing and uncompressing, use the attached perl script and below commands in terminal: for uncompressing perl zlib.pl inflate layout28.xml.zlib > layout28.xml for compressing perl zlib.pl deflate layout28.xml > layout28.xml.zlib Layoutxx.xml file Patching You can either use the attached xml files (or) can choose any one of the layout xml file from the apple Resources directory inside AppleHDA kext that matches Inputs and outputs of your codec and try this only if you want to experiment. I'm using the Layout28.xml of Apple and edited to the values of ALC269. One of the reason to choose layout28 is because its used in MacBookPro8,1 and works very well. The other layout id's which also works for some codecs are '1' and '12' in hackintosh. Note: We removed the tags External Mic, SPDIF from the Apple layout28 xml file since they are not needed for our example ALC269. In the Layout xml file, we have to edit the following information. 1. LayoutID <key>LayoutID</key> <integer>28</integer> 2. CodecID [ALC 269 Vendor id decimal value =283902569 ] <key>CodecID</key> <array> <integer>283902569</integer> </array> 3. Edit the Inputs key like below for External Mic(LineIn) and Internal Mic in Notebooks <key>Inputs</key> <array> <string>Mic</string> <string>LineIn</string> </array> 4. Edit the "IntSpeaker" key like below and remove all the signal processing elements. Note: set MuteGPIO to 0 (or) remove this if its not working [ not supported by some codecs] For Realtek: <key>IntSpeaker</key> <dict> <key>MaximumBootBeepValue</key> <integer>48</integer> <key>MuteGPIO</key> <integer>0</integer> </dict> For others: <key>IntSpeaker</key> <dict> <key>MaximumBootBeepValue</key> <integer>110</integer> </dict> 5. Edit the "LineIn" key like below. For Realtek: <key>LineIn</key> <dict> <key>MuteGPIO</key> <integer>1342242840</integer> </dict> For Others: <key>Mic</key> <dict/> 6. Edit the "Mic" key like below. For Realtek: <key>Mic</key> <dict> <key>MuteGPIO</key> <integer>1342242841</integer> </dict> For Others: <key>LineIn</key> <dict/> 7. Edit the Outputs key like below for Speakers and Headphone in Notebooks <key>Inputs</key> <array> <string>Headphone</string> <string>IntSpeaker</string> </array> 8. Edit the PathMapID tag at the end of the file with the PathMapID value used in Platforms xml file. <key>PathMapID</key> <integer>269</integer> Note: SignalProcessing elements for Mic and Speaker are not supported by some codecs, so i've removed it. But can provide some good audio if used but not sure, so try to experiment with this later after getting audio working. I've attached xml files with the SignalProcessing working fine in ALC269 for speaker and Mic in Realtek and IDT for your reference, you can get more from Apple xml files. Platforms.xml Patching: This file contains the Mapping of Controls to its nodes giving a path. These path maps are contained in the key tag "PathMaps". Note:You can use the Platforms xml file i've attached which has all the PathMaps of Apple codec are removed and has only one PathMap of ALC269 in order to make it easy for editing instead of Apple file. We need to add our pathMaps to this root key which is a mapping of our Pin Complex's(O/P & I/P) to its Output/Input controls. Follow the pattern i've explained below and edit the values of your codec nodes PathMaps calculated in the first post for each input and output. After editing then add the PathMap pattern of yours inside the file Platforms.xml at the end after the key tag of PathMapID like below. <key>PathMapID</key> <integer>[some apple id]</integer> </dict> <<< Your pathMaps >> The pattern for the PathMap is <dict> <key>PathMap</key> <array> <array> <array> Data of Input1 (LineIn) </array> <array> Data of Input2 (Mic) </array> </array> <array> <array> Data of Output1 (Speaker) </array> <array> Data of Output2 (Headphone) </array> </array> </array> <key>PathMapID</key> <integer>[PathMapID used in layout#]</integer> </dict> Input Data pattern: <array> <dict> <key>Amp</key> <dict> <key>Channels</key> <array> <dict> <key>Bind</key> <integer>1</integer> <key>Channel</key> <integer>1</integer> </dict> <dict> <key>Bind</key> <integer>2</integer> <key>Channel</key> <integer>2</integer> </dict> </array> <key>MuteInputAmp</key> <true/> <key>PublishMute</key> <true/> <key>PublishVolume</key> <true/> <key>VolumeInputAmp</key> <true/> </dict> <key>NodeID</key> <integer>[Input Node#]</integer> </dict> <dict> <key>NodeID</key> <integer>[Audio Mixer/Selector Node#]</integer> </dict> <dict> <key>Boost</key> <integer>[Boost value# 1-3]</integer> <key>NodeID</key> <integer>[Pin complex Node#]</integer> </dict> </array> Input Data pattern without Audio Mixer/Selector: Note: Some codecs doesn't need (or) use Audio Mixer/Selector node, so in order to get them working we should remove it from the pattern. Mostly this has been seen from IDT and Conexant codecs so far by me. <array> <dict> <key>Amp</key> <dict> <key>Channels</key> <array> <dict> <key>Bind</key> <integer>1</integer> <key>Channel</key> <integer>1</integer> </dict> <dict> <key>Bind</key> <integer>2</integer> <key>Channel</key> <integer>2</integer> </dict> </array> <key>MuteInputAmp</key> <true/> <key>PublishMute</key> <true/> <key>PublishVolume</key> <true/> <key>VolumeInputAmp</key> <true/> </dict> <key>NodeID</key> <integer>[Input Node#]</integer> </dict> <dict> <key>Boost</key> <integer>[Boost value# 1-3]</integer> <key>NodeID</key> <integer>[Pin complex Node#]</integer> </dict> </array> Output data pattern: <array> <dict> <key>Amp</key> <dict> <key>MuteInputAmp</key> <false/> <key>PublishMute</key> <true/> <key>PublishVolume</key> <true/> <key>VolumeInputAmp</key> <false/> </dict> <key>NodeID</key> <integer>[Pin complex Node#]</integer> </dict> <dict> <key>Amp</key> <dict> <key>MuteInputAmp</key> <true/> <key>PublishMute</key> <true/> <key>PublishVolume</key> <true/> <key>VolumeInputAmp</key> <false/> </dict> <key>NodeID</key> <integer>[Audio Mixer Node#]</integer> </dict> <dict> <key>Amp</key> <dict> <key>Channels</key> <array> <dict> <key>Bind</key> <integer>1</integer> <key>Channel</key> <integer>1</integer> </dict> <dict> <key>Bind</key> <integer>2</integer> <key>Channel</key> <integer>2</integer> </dict> </array> <key>MuteInputAmp</key> <true/> <key>PublishMute</key> <true/> <key>PublishVolume</key> <true/> <key>VolumeInputAmp</key> <false/> </dict> <key>NodeID</key> <integer>[Output Node#]</integer> </dict> </array> Output Data pattern without Audio Mixer: Note: Some codecs doesn't need (or) use Audio Mixer, so in order to get them working we should remove it from the pattern. Mostly this has been seen from IDT and Conexant codecs so far by me. <array> <dict> <key>Amp</key> <dict> <key>MuteInputAmp</key> <false/> <key>PublishMute</key> <true/> <key>PublishVolume</key> <true/> <key>VolumeInputAmp</key> <false/> </dict> <key>NodeID</key> <integer>[Pin complex Node#]</integer> </dict> <dict> <key>Amp</key> <dict> <key>Channels</key> <array> <dict> <key>Bind</key> <integer>1</integer> <key>Channel</key> <integer>1</integer> </dict> <dict> <key>Bind</key> <integer>2</integer> <key>Channel</key> <integer>2</integer> </dict> </array> <key>MuteInputAmp</key> <true/> <key>PublishMute</key> <true/> <key>PublishVolume</key> <true/> <key>VolumeInputAmp</key> <false/> </dict> <key>NodeID</key> <integer>[Output Node#]</integer> </dict> </array> Layout12_XML_Files_ref.zip Layout28_XML_Files_ref.zip zlib.zip