Leaderboard

macOS Sonoma 14.5 (23F79) ( Same build as RC ) Full Installer https://swcdn.apple.com/content/downloads/32/06/062-01946-A_0PEP7JHIWA/1pfs4xh22555dj51fkep7w06s4eiezh21p/InstallAssistant.pkg

Here all fine too

My "new" Hackmini8,1 with RX560x dGPU upgraded from Sonoma 14.4.1 to Sonoma 14.5 without issues. Booting with Open Core 1.0.0. About This Hack: Sonoma 14.5 GB5 Metal Score (Tested in Sonoma 14.4.1) Note that this hack uses the Mobile Radeon RX560x. GB6 Metal Score (Tested in Sonoma 14.5)

macOS Monterey 12.7.5 (21H1222) ( Same build as RC ) Full Installer https://swcdn.apple.com/content/downloads/02/18/052-96238-A_V534Q7DYXO/lj721dkb4wvu0l3ucuhqfjk7i5uwq1s8tz/InstallAssistant.pkg

...nice, normal update from 14.4.1, took all of 20 minutes 💯

No issue

macOS Ventura 13.6.7 (22G720) ( Same build as RC ) Full Installer https://swcdn.apple.com/content/downloads/46/31/052-96247-A_MLN9N00Y8W/dmml3up52hrsb01krjtczmdhexiruv1b5m/InstallAssistant.pkg

👍

---All EFI folders is updated to OpenCore 1.0.1 and all Kexts to last version--- OpenCore MOD - https://www.olarila.com/topic/25111-hackintosh-efi-folders-with-opencore-mod/ OpenCore Official - https://www.olarila.com/topic/5676-hackintosh-efi-folder-with-clover-and-opencore/

https://github.com/0xCUB3/About-This-Hack

With iMac19.1 you don't need R.Event (in my case iMac19.1 the update was notified) ... anyway try this https://github.com/Lorys89/RestrictEvents/releases/tag/1.1.4 no need boot-args Normally in RCs the pkg is not released , also because perhaps the Release will be released on Monday then you will have the pkg so either you wait or download the full ... it's still 13 GB (also for the pkg) 💁‍♂️

To get the incremental update, you need to revert OCLP patches if you're using it then reboot the machine. It will also help if you have revpatch=sbvmm in boot-args in config.plist. Won't hurt to have SIP fully enabled. After try to see if the small update is available. Obviously to use OCLP again, you'll have to revert all the changes you made. Good luck.

OpenCore 1.0.0 is out. Despite the version number, it is not a major change but rather one more step in the continuous evolution of OpenCore. There are quite a few changes and improvements, updating is recommended. You can get it from Acidanthera. Main changes Updated builtin firmware versions for SMBIOS and the rest Utilities now require macOS 10.9+ (OpenCore itself still supports macOS 10.4+) Added AllowRelocationBlock support for 32-bit version Fixed problem loading non-firmware runtime drivers (e.g. OpenRuntime.efi) in OpenDuet Fixed alphabetical ordering in Configuration.pdf. Config.plist Added Booter -> Quirks -> AllowRelocationBlock (support for 32-bit OpenCore): this quirk is needed to boot macOS 10.6 and older with 32-bit kernel in 32-bit OVMF. Hibernation wake is not compatible with this quirk. Sample.plist and SampleCustom.plist: The settings required to reactivate the Broadcom Wi-Fi that have lost support in Sonoma have been added, they are the ones that we already use proposed by OCLP. Kexts AppleALC 1.9.0 HibernationFixup 1.5.0 VoodooInput 1.1.4.

Without any basis other than naive optimism, I am expecting Apple to support Intel-based Macs in macOS 15. If that's the case, I'll continue to support this thread. If Apple does not include Intel-based Macs in macOS 15, then I won't be spending much more effort on this thread. The Open Core 1.0.0 EFI that I have attached to Post #1 is working very well for macOS versions through Sonoma 14.5.

---All EFI folders is updated to OpenCore 1.0.1 and all Kexts to last version--- OpenCore MOD - https://www.olarila.com/topic/25111-hackintosh-efi-folders-with-opencore-mod/ OpenCore Official - https://www.olarila.com/topic/5676-hackintosh-efi-folder-with-clover-and-opencore/

Installing Sonoma , Ventura, Monterey and Big Sur from Clover Duet its a differant story. but Booting Latest Sonoma already installed this is not an issue with clover duet. To make it possible I have to Add NVRAM creation from the Clover duet script but now I dont have the full time to do this. EDIT*** I will make some test tonight then let you know

If you want your "About This Mac" screen in Sonoma 14.5 to show your EliteDesk 800 info, you'll need to edit ~/Library/Preferences/com.apple.SystemProfiler.plist. The format for the "CPU" in com.apple.SystemProfiler.plist is Description, Date For example, for my About This Mac screen below, I changed all instances of CPU description in com.apple.SystemProfiler.plist to "HP EliteDesk 800 G4 Mini, 2018" (without quotes). The iMac descriptions in my com.apple.SystemProfiler.plist become "iMac (HP EliteDesk 800 G4 Mini, 2018)" and the MacMini instances become "Mac mini (HP EliteDesk 800 G4 Mini, 2018)" (without quotes). About This Mac (iMac19,2) My GB6 scores with SMBIOS iMac19,2 EDIT: Performance on this hack, even with i5-8500T, is phenomenal. This little hack is very responsive. The RX560x graphics acceleration over the UHD630 iGPU makes a big difference.

Update failed to “prepare for upgrade”. Rebooted and upgrade went without issue.

@Anto65 The RestrictEvent kext and revpatch=sbvmm command have been deleted. This is the case when installing from scratch. Thanks again.

EFI with OpenCore 1.0.0 config-14-imac-amd.plist SMBIOS iMac19,1 IMPORTANT: fill in your own SMBIOS data iGPU headless mode and AMD as main card iGPU Enabled in BIOS unfairgva=6 in dGPU properties to get some kind of DRM config-14-macpro.plist SMBIOS MacPro7,1 IMPORTANT: fill in your own SMBIOS data iGPU disabled in BIOS config-extra config-fenvi.plist: if you have a Fenvi combo card or any of the Broadcom wifi chipsets that have lost support in Sonoma and are included in the OCLP root patch config-amfipass.plist: to have the Fenvi card with AMFIpass.kext instead of amfi=0x80 in boot args config-ax210.plist: if you have an Intel AX210 combo card (only wifi) (this file has AirportItlwm.kext but you can try itlwm.kext instead) config-ax210-bt.plist: if you have an Intel AX210 combo card (wifi + Bluetooth) (this file has AirportItlwm.kext but you can try itlwm.kext instead). Notes Rename the selected config to config.plist. Required kexts are not included because of the size of the ZIP file (only CPUFriendDataProvider.kext and UTBMap.kext are included) Fenvi and Broadcom Wi-Fi cards AMFIPass.kext 1.4.0. IO80211FamilyLegacy.kext 1.0.0 / IOSkywalkFamily.kext 1.1.0. Intel supported combo cards - OpenIntelWireless. AirportItlwm.kext / itlwm.kext (Ventura v2.2.0, Sonoma v2.3.0). IntelBluetoothFirmware.kext / IntelBTPatcher.kext. BlueToolFixup.kext: BrcmPatchRAM by Acidanthera. Wi-Fi 6 Intel AX210 on macOS Sonoma. Get back Fenvi T919 and other Broadcom Wi-Fi on macOS 14 Sonoma thanks to OLCP. List of used kexts (not included in the ZIP file): AMFIPass.kext AirportItlwm.kext AppleALC.kext BlueToolFixup.kext CPUFriend.kext IO80211FamilyLegacy.kext IOSkywalkFamily.kext IntelBTPatcher.kext IntelBluetoothFirmware.kext IntelMausi.kext Lilu.kext NVMeFix.kext RestrictEvents.kext SMCProcessor.kext SMCSuperIO.kext USBToolBox.kext VirtualSMC.kext WhateverGreen.kext itlwm.kext. Don't forget any other kext that you are using now. EFI 1.0.0 Sonoma.zip

HP Z840 upgrade from Sonoma 14.4.1 to Sonoma 14.5 without issues.

Hi and Welcome, you need to read @fantomas post at the top of this page that directs you to the reason why as a new User you are limited and where you can only initially post.

SDL3 version of dosbox-x with sdl2-compat library. This version also has glide support (Voodoo graphics card). Enjoy Minimum deployment target is 14.0. dosbox-x-SDL3.zip

I have built dosbox-x for Intel and Apple Silicon. Works on 10.13 and better. Enjoy dosbox-x-2024.03.01-Universal.zip

Using the Open Core 1.0.0 EFI attached to Post #1, I upgraded from Sonoma 14.4.1 to 14.5 without issues. About This Hack: Sonoma 14.5 Note that SecureBootModel is already Disabled, so I did not need to change this for the Sonoma upgrade. I'm currently testing this hack with the EFI attached to Post #1 (Macmini8,1 SMBIOS with DeviceProperties for both RX560x and UHD630 for multi-display operation), but I have only a single physical display connected to the RX560x DP port and I have Internal Graphics set as Boot VGA in BIOS. This hack works fine with the single physical display and the multi-display EFI. Note that with the single physical display connected to the RX560x DP port and the multi-display EFI, the "About This Hack" screen shot above reports graphics as Radeon RX 560x. It appears to me that the multi-display EFI (configured for a combination of RX560x and UHD630 graphics ports) works just fine, regardless of the physical graphics configuration. GB6 Metal Score after upgrade to Sonoma 14.5

macOS upgrades to Ventura 13.6.7 and Sonoma 14.5 proceeded without issues using the new Open Core 1.0.0 EFI attached to Post #1. Before upgrading Sonoma from 14.4.1 to 14.5, I set OpenCore's SecureBootModel = Disabled. After the Sonoma upgrade, I restored SecureBootModel to j174. About This Hack: Ventura 13.6.7 About This Hack: Sonoma 14.5

I implemented gcc-14.1.0 compilation with some Clover sources changed. The sources can be still compiled by gcc-13 and by xcode-15. Don't know about older versions.

Upgraded my HackBookPro6,2 to Open Core 1.0.0. LegacyBoot, LogoutHook and Vault all working perfectly. Running Big Sur, Monterey, Ventura and Sonoma. Well done, Devs!

Thanks my Genius brother, nice solution !!!

Rename Mint.icns -> Ubuntu Ubuntu.icns -> -Ubuntu.icns 😁

Ok. Thanks.

I can't get an incremental update; 13.65 GB. Please, installer.can you share the pkg?

Done.

AMD is alive & kicking

All set.

@BALDY_MAN - Hello old friend, old boy here to the rescue No need for anything complicated, this is an easy fix. On Finder, goto /Library/Logs/DiagnosticReports. Delete all the Files in this folder, reboot, clean Nvram and you're good to go. Cheers!!!

I like the way you think!

@miliuco Great summary as always. I see that VoodooInput has been updated, but VoodooPS2 has not. According to this, "WARNING: This kernel extension [VoodooInput] is designed to be bundled with a dedicated multitouch client driver and exists for the developers only. Please download the latest version of VoodooPS2 or VoodooI2C to make use of this kext." Just curious as to why developer kext VoodInput was updated without updating the end-user kexts.

I have upgraded the OC EFI attached to Post #1 with Open Core 1.0.0. The EFI assumes that TPM and VT-d are enabled in BIOS (an ACPI patch hides TPM from macOS and the EFI includes a revised DMAR table). Enabling TPM isn't required and is only necessary if you're also booting Windows 11. Changes to the EFI are below. Since I have not posted a new EFI since OC 0.9.6, all of my changes since OC 0.9.6 are listed below. If you use this EFI with Sonoma 14.4+, be sure to set SecureBootModel = Disabled before installing/upgrading Sanoma. You can restore SecureBootModel to your preferred setting after the Sonoma installation / upgrade. OC 1.0.0 EFI R001 EFI/BOOT: Update BOOTx64.efi EFI/OC: Update OpenCore.efi EFI/OC/Drivers: Update OpenRuntime.efi, AudioDxe.efi, ResetNvramEntry.efi EFI/OC/Kexts: Upgrade AppleALC.kext from 1.8.9 -> 1.9.0 EFI/OC/config.plist Add ACPI > Add: SSDT-TPM-Off Add ACPI > Patch: change TPM._STA -> TPM.XSTA (paired with SSDT-TPM-Off) EFI/OC/Tools: Update tools EFI/OC/ACPI Add SSDT-TPM-Off OC 0.9.9 EFI R001 EFI/BOOT: Update BOOTx64.efi EFI/OC: Update OpenCore.efi EFI/OC/Drivers: Update OpenRuntime.efi, AudioDxe.efi, ResetNvramEntry.efi EFI/OC/Kexts: No changes EFI/OC/config.plist Change Misc > Security > SecureBootModel=Default -> =j174 (MacMini8,1) EFI/OC/Tools: Update tools OC 0.9.8 EFI R001 EFI/BOOT: Update BOOTx64.efi EFI/OC: Update OpenCore.efi EFI/OC/Drivers: Update OpenRuntime.efi, AudioDxe.efi, ResetNvramEntry.efi EFI/OC/Kexts: Upgrade AppleALC.kext 1.8.8 -> 1.8.9 EFI/OC/config.plist No changes EFI/OC/Tools: Update tools OC 0.9.7 EFI R001 EFI/BOOT: Update BOOTx64.efi EFI/OC: Update OpenCore.efi EFI/OC/Drivers: Update OpenRuntime.efi, AudioDxe.efi, ResetNvramEntry.efi EFI/OC/Kexts: Upgrade AppleALC.kext 1.8.7 -> 1.8.8 EFI/OC/config.plist No changes EFI/OC/Tools: Update tools

Finally I had a few hours to play with my Mini. I was not able to boot the latest MacOS Sonoma 14.5 with your EFI but the fix was easy. Computer will stuck or restart on checking the iGPU firmware and I had to remove igfxfw=2 boot arg. After that everything was flawless. I also added the dGPU property. My dGPU is set to primary in BIOS and I am using DP->HDMI adapter connected directly to the dGPU. The other DP (iGPU) ports will not output anything with the current setup. Audio through the DP is also working. I have added Intel 8265 Wifi/BT card and it's working great for both Wifi and BT. Right before the welcome screen I see "No Output" for just a second. Guess that's a normal behaviour. I see the igfxonln boot arg. Might not be needed since it's created for Intel iGPUs ? Will test the EFI without it when I have time again. This boosted the performance with ~10% (at least in the benchmarks). I was able to get ~22000 in Geekbench. System is snappy and the temps of the dGPU are great. During the stress test it never exceeded 60'C. Only downside for me is no support for 4K@120Hz but hey... it's still impressive for the price

cool now that you can boot try wahtevergreen with some device properties or nblue with no device props there's also a way to disable PEG1 with device properties (this helps a lot as the gpu just vanish from ioreg) add boolean variable disable-gpu=yes info.plist with no edid injection migth work for you like this and maybe boot with -v keepsyms=1 debug=0x100 agdpmod=pikera you have a VoodooGPIOTigerLakeH device hmmm try i2c kext posted above no keyboard ? i dont see tpad device. is xosi patch working ? only if system is unstable change csr-config and security wifi+bluettoth are possible to setup with right kexts that's all i can see for now to get a lot after boot open terminal paste log show --style syslog --predicate 'processID == 0' --last 1h --info --debug > x.log you get a file x.log on home folder i fixed some acpi errors here's my latest EFI.zip for those with displays that attach to framebuffer 0 try swap connector to frame 1 that avoids lcd+power code that prevents display to work todo so 1st check logs. if the display attaches to frame 0 then better swap connectors i have it in nblue reversed order but same logic

I have successfully installed macOS Sonoma 14.4 on this hack with RX560x. I need to cleanup my EFI a bit and optimize it, but for those who wish to attempt before I post my first EFI, here's what I did: Start with my original EFI here Upgrade to Open Core 0.9.9 (not necessary, but I did anyway) Add ACPI patch to rename GFX0 -> IGPU Add ACPI patch to rename PEGP -> GFX0 and disable unused PEG1.GFX0 and PEG2.GFX0 (formerly PEG1.PEGP and PEG2.PEGP) Create graphics DeviceProperties (in config.plist) for Radeon, but spoof RX580 (I wasn't able to get RX560 to work on my first pass which is why I still need to clean up my EFI. I don't know if this is because of the graphics card or the fact that I'm using DP->DVI adapters). Spoof by setting ATY,DeviceID = 0xDF67 and Framebuffer name to ATY,Orinoco. There are probably other spoofs that work, but this is what I did to get around the black screen for now. My goal is to eliminate the spoof after I examine IOReg, but this spoof results in a working macOS. Keep WhateverGreen.kext and add boot-arg agdpmod=vit9696 (not sure this was necessary, didn't test without) Keep Macmini8,1 SMBIOS (I'd like to test with iMac19,1 and plan to switch if it works) Next steps for me before I post my first EFI are: Experiment with other DeviceIDs / Framebuffers. This might be tricky for me, because I am using DP->DVI adapters Experiment with SMBIOS iMac19,1 Eliminate unnecessary changes (e.g., I may not have needed some of the ACPI renames) Cleanup my EFI and make sure I've documented my changes / steps EDIT: I changed SMBIOS to iMac19,1 and upgraded to Sonoma 14.4.1. This will be my last update for a while as I'm busy with other things. EDIT2: Ok, I couldn't resist. I now have my hack working with Framebuffer = Acre (should be the native Framebuffer for this RX560). Now, no more updates for a while.

Well in my limited understanding of OC I don't know what breaks the windows, but I'll ask, if it is the DSDT that breaks the windows why with OC MOD the same DSDT don't break the windows, because of the no ACPI? Me too I don't know why that has happened bit when I have time I'll find it, comparing the others EFi with this one until I find the culprit...

Known Issues, Observations and Solutions Possible RX560x performance increase when adding @0,name and @0,compatible GFX0 properties. See here. I'm suspicious of my 20-byte connectors property in my SSDT-GFX0. While it works, I think it should be 16 or 24 byte as stated here. I tried without success to use Lilu and WhateverGreen debug kexts (to produce debug log and to see discovered connectors). I think it is necessary to try another attempt at producing debug log with the debug kexts so that the correct connectors byte sequence can be created. This is a low priority, since my solution is working. Note that padding the connectors patch with an additional four 0x00 bytes (for a total of 24 bytes) breaks the patch and causes boot to black screen. For those who wish to use a single display connected to the RX560x DP port (no displays connected to UHD630 iGPU ports), this configuration (iMac19,1) or this configuration (iMac19,2) may be desirable. With DAGPM.kext disabled while testing iMac19,2 SMBIOS, I observed hesitation during operation of GeekBench6 and I lost my left mouse button. I did not test long enough to confirm that disabling DAGPM.kext was the cause of this. I am leaving DAGPM.kext enabled and don't plan to test further. See more here. When switching between SMBIOS models during my testing (e.g., switching between Macmini8,1, iMac19,1 and iMac19,2), I noticed that graphics performance improved after more than one reboot / NVRAM reset cycle. I'm not sure why this would be the case, but when switching SMBIOS models, it may be best to reboot and reset NVRAM more than once before running benchmarks. I'm using RestrictEvents.kext property revblock=media on my HackBookPro6,2 and I think it has improved non-metal performance on that old hack. I've seen posts that suggest the property is useful for Metal dGPUs also. I have added this property to my OC config.plist and am testing. At the time of this writing, wake from sleep results in black screen when I use SMBIOS iMac19,2 (possibly for iMac19,1 also - haven't tested). With SMBIOS MacMini8,1, wake works fine. I am using DP->DVI adapters, so this might affect my wake behavior (the reason I needed to add No-hda-gfx property for my original UHD630 solution). I tried darkwake=0 and darkwake=2 boot-args without success. My baseline SMBIOS is MM8,1, so iMac19,x wake is a low-priority fix for me. EDIT: Need to look at com.apple.PowerManagement plists in /Library/Preferences. It's possible that I need to delete these and recreate power management settings, since I'm switching between SMBIOS models during testing (and MM81 was the first SMBIOS I tested).

macOS Monterey 12.7.5 (21H1211)

Bro I think @MaLd0n is teaching you bad habits. But I am jealous.