Leaderboard

Hey all, I'm up and running with the latest Clover EFI and Bios 12d - it updated to Catalina 10.5.5 latest security update with no issues. Thanks for all your hard work on this. I was worried about problems with my Samsung 970 Evo Plus NVME, but it shipped with the latest firmware and I didn't even have to update - everything just worked. I started out to do this with OC but had a couple problems with the install, so I'll read through the documentation again and try loading the EFI from a separate card. For anyone specifically thinking of using this hardware for a music workstation, so far it's performing great under Logic Pro X with an Audient ID22 and Audient ASP880. ____ Gigabyte Z390 Aorus Pro, I59600k, XFX Radeon 580, Samsung 970 Evo Plus NVME, unlocked BIOS 12d, Audiogod Clover profile, Catalina 10.5.5

The fork hasn't been updated in over a month, and the last version available is based on OpenCore 0.5.8. Those no scheme errors are from changes in OpenCore 0.5.9 which doesn't apply to the now out-of-date OC fork.

NDK-OC is not maintained since May,4 and his latest release 0.5.8. No news from @n.d.k since one month

I've removed the previous 3.1.0b7 beta and am now supplying the next beta here for testing. Still tweaking before a release..... This new beta includes (Changes from 3.1.0b7 -> 3.1.0b8) - Don't attempt to read MBR and PBR of APFS containers. - Don't attempt to read MBR and PBR of APFS physical stores when SIP File Protection is enabled. - Print hex bytes as single bytes in disk dumps (Thanks slice) - Change writeable path check from command line - Add detection for OpenCore bootstrap.efi - Improve OpenCore detection for when file has been renamed - Add detection for OpenCore log from file, Data Hub or UEFI var Please report any issues.

X99/X299 EFI sample for 10.15.5 #This is sample EFI for X99/X299 OC 0.6.0 #Ensure you understand EVERY field before booting. https://www.insanelymac.com/applications/core/interface/file/attachment.php?id=350551 https://www.insanelymac.com/applications/core/interface/file/attachment.php?id=350552

Apologies - a typo. It is 3.61. The EFI I posted is for 3.61 (not 3.91 which was a type). Have you tried using the files from that?

Hey there, I am trying to install Catalina on my Z800 Specs: Latest Bios 3.61 2x X5690 48GB RAM 1x 128GB SSD 2x2 TB HDD Gigabyte RX 570 8GB What am I doing wrong? Tried several different EFI Folders I've found. EDIT: I've managed to install Mac OS Catalina with my older GTX1050ti, but it's not well supported in Catalina so I went back trying with the RX570. No luck so far. I guess I have to patch my DSDT? But I am very new to this.

Updated my T460 to Catalina 10.15.5 Supplemental Update without any problems today. As everytime I published my actual EFI on GitHub it's based on OpenCore 0.59 final with updated kext.

new build 19F101

Got solution for Ivy Bridge XCPM patch for Catalina 10.15.5. I compared the Kernels from 10.15.4 and 10.15.5 with a Disassembler and examined the _xcpm_bootstrap looking for 0xC4 & 0x3B (which were patched in 10.15.4). In 10.15.5, they changed code a bit and "CMP BL, 0x3B" is not there but offset to a table dereference to 0xC4 was there. Changing the 0xC4 to 0xC6 (for Ivy Bridge) enables XCPM. The patch is (ONLY for 10.15.5): Find: 8D43C43C42 Replace: 8D43C63C42 Full OC entry in Kernel->Patch: <dict> <key>Base</key> <string>_xcpm_bootstrap</string> <key>Comment</key> <string>_xcpm_bootstrap (For Ivy Bridge) 10.15.5 by MacNB</string> <key>Count</key> <integer>1</integer> <key>Enabled</key> <true/> <key>Find</key> <data> jUPEPEI= </data> <key>Identifier</key> <string>kernel</string> <key>Limit</key> <integer>0</integer> <key>Mask</key> <data> </data> <key>MaxKernel</key> <string>19.99.99</string> <key>MinKernel</key> <string>19.5.0</string> <key>Replace</key> <data> jUPGPEI= </data> <key>ReplaceMask</key> <data> </data> <key>Skip</key> <integer>0</integer> </dict> I get P-States from 1.6Ghz up to my overclock 4.8Ghz. Thanks to all who helped. I cannot upload screenshots as the site keeps failing to upload.

OpenCorePkg / Documentation / Configuration Template / Bugtracker Discussion and installation should be done in a separate thread! This thread is for development only! Current status as of April 2019: Support for UEFI and DuetPkg (legacy) booting APFS and HFS+ compatibility ACPI patcher (adding, dropping, binary patching, relocation) Apple-compatible bless implementation DeviceProperties injection DataHub and SMBIOS generation Symbolic kext and kernel patcher Direct kext injection/patching/blocking within prelinkedkernel Installation/Recovery/FileVault 2 support Configuration in config.plist with open documentation Simple boot picker for quick launch Direct boot from dmg images Known defects live here. For those, who are not familiar with the history, OpenCore is a project initially born in HermitCrabs Lab that unfortunately almost died before its birth. This release is both a rebirth and a complete rewrite of OpenCore, which brings a number of new ideas, and tries to preserve the smart moves incorporated by iNDi and his team. Other than that, I wish to express my deepest words of gratitude to Acidanthera and WWHC members: your participation was and remains the key for project success, and you are simply the best.

Hackintoshing is a niche. Those who do it are either a) not going to buy a Mac or b) already own one. The vast majority of us here are in column A. Mac hardware is simply not that good. Macs are expensive as {censored} and not worth the money.

OpenCore is not meant to be included in firmware. Anyway, nowadays I would not do it. There is no gains now that everyone is booting from SSD. I am to the point where I will not go back anymore and staying with OpenCore. I have to make some adjustments to the firmware I assembled and then write a migration guide. Presumably because they were already paired with your dongle ... unpair them , remove the dongle In Finder Command-K, then hit the Browse button. Do you see them ? Number of fans. The only software that will give you only the fans we have is HWSensors if and only if you are also using the SMC sensors built into the firmware. If you have FakeSMC in anywhere or VirtualSMC .. it will list additional fans because they don't have a profile for the motherboard. This is something I might want to try to do for OpenCore (make a QUO motherboard profile to include for VitualSMC). Unless your fans are Spectre Pro PWM (your sig says Spectre Pro ..which means regular) there is nothing to control. Set them in firmware - choose Silent). The Intel stock CPU cooler sucks a lot, if you do any kind of very cpu extensive work.. I suggest you get a decent cooler else the CPU have have to throttle down to prevent it from reaching too high temperatures. 71C @ idle is a lot .....you did put the thermal paste right ? Here r my temps and rpms...

@pkatzman @jcarnell Please make a build signature @jcarnell

Defaults.plist are read from SATA0,0 (if a drive is connected there..that is why i always recommend using this connector to make it predictable) and stored in NVRAM until NVRAM is cleared (flashing firmware, Command-Option-P-R). KernextPatcher.plist are read from the disk that contains the kernel you are booting if present, else it is read from the one i built into the firmware. KernextPatcher.plist is read at every boot.

I would start back at page 160 (Feb 3rd).. if you read from there you should be able to get up to speed fairly quick. The firmware will create the Oz directory itself after you flash the correct firmware if it is not there. If it is not already there it is because you were using Clover and not Ozmosis.

Updated Defaults.plist template ( applies to HighSierra & above notice the change to BiosVersion format) : Defaults.plist template : <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Version</key> <string>1.0.1</string> <key>Date</key> <integer>0</integer> <key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key> <dict> <key>BiosDate</key> <string>07/24/2019</string> <key>BiosVersion</key> <string>288.0.0.0.0</string> <key>FirmwareFeatures</key> <integer>0xE00DE137</integer> <key>FirmwareFeaturesMask</key> <integer>0xFF1FFF3F</integer> <key>ProductId</key> <string>Mac-FC02E91DDD3FA6A4</string> <key>ProductFamily</key> <string>iMac</string> <key>ProductName</key> <string>iMac13,2</string> <key>SystemSerial</key> <string>InsertYoursHere</string> <key>BaseBoardSerial</key> <string>InsertYours+5Digits</string> </dict> <key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <dict> <key>boot-args</key> <string>-v</string> <key>csr-active-config</key> <integer>103</integer> </dict> <key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key> <dict> <key>DisableNvidiaInjection</key> <true/> <key>BootEntryTemplate</key> <string>$label</string> <key>DarwinDiskTemplate</key> <string>$label $platform.$major.$minor</string> <key>DarwinRecoveryDiskTemplate</key> <string>$label $platform.$major.$minor</string> </dict> </dict> </plist>

To invoke the board's Backup Firmware (in case you brick it while flashing BIOS) Method #1 Turn off power via AC main switch on PSU. Press and hold the ATX power switch then switch the PSU back on while still holding ATX power switch. Hold the power button until the PC starts and shuts down again. Release the ATX Power switch, wait 5 secs and press it again. Backup Firmware should kick in. If not, repeat. Method #2 1. Shut your PC down 2. Hold the power AND the reset button for about 10 sec, then release. 3. Backup BIOS should kick in anytime soon now.

You could also integrate my 64-bit patches into the sources. Yes if somebody made a max 1024B boot1a (boot1 APFS) we could. It has the same proceedings as HFS+ (1024B of space at the beginning of the partition)

I have assembled a new firmware. I call it XMAX-E (E for Expandable). I have based it on the XMAS firmware , built into the firmware is APFSDriverLoaded, KernextPatcher and DBounce. Kernel patches up to 10.14.4 are built into the firmware but can be expended by placing KernextPatcher.plist in /Efi By default DBounce is disabled until you place DBounce.plist in /Efi (you can use DBounce to Expand the firmware by loading more drivers such as DarBoot or BeepBeep ) Credits go to @cecekpawon for UEFTW, @PMheart for the kernel patches and @alberto21 who's RE-XMAX firmware sparked the idea for me to build this one. Z77MXQUOAOS.H2O.167X-XMAX-E.ROM.zip

Yes I meant vanilla .. On El Cap & Sierra Apple imposed some USB ports restrictions for some models. F_USB3 is not the target of those restrictions. On El Cap, you can use the kexts I posted here to remove restrictions (if you need those ports). I haven't published for Sierra yet since I have not upgraded.

I switched to 0.5.9 and all the boot icons no longer appear, just default text menu? What’s changed? Boot back to 0.5.8 with the same resources folder, the icons were back with the same config. thanks, louis