Leaderboard

DISCLAIMER - Pay attention! Patching a DSDT is risky. Do only if you know risks and how to recover it if something goes wrong! Hi everyone, with the release of new bios for am5 platforms which allow pre-support for 8000 series CPUs we came across a bug that no longer started macos. @fabiosun and I started by trying these new bios without success in starting macos, until I had the idea of injecting the old dsdt of the previous bios with true on the RebaseRegions quirks. Subsequently I dedicated myself to patching new bios and removing new conditions that were added : removing the entire CPVS section generates 30 errors in my case : I started to correct these errors by removing conditions for loading devices or _PRW methods : there are so many that it removes the if... string with the bracket { and at the end of the scope also remove a bracket } so as not to generate other errors. and I also removed this whole part: Attached in this post original dsdt of new asus b650e-i's bios f and the patched one (asus b650e-i) Original - DSDT.aml.zip --------------------------- (asus b650e-i) Patched - DSDT.aml.zip --------------------------- (asus x670e gene) Patched - DSDT.aml.zip --------------------------- (asus x670e hero) Patched - DSDT.aml.zip ---------------------------

Beta3

Release v0.9.6 Updated builtin firmware versions for SMBIOS and the rest Fixed hang while generating boot entries on some systems Added efidebug.tool support for 32-bit on 32-bit using GDB or LLDB Fixed potential incorrect values in kernel image capabilities calculation Added FixupAppleEfiImages quirk to allow booting Mac OS X 10.4 and 10.5 boot.efi images on modern secure image loaders

macOS Sonoma 14.1.2 (23B92) Full Installer https://swcdn.apple.com/content/downloads/24/37/052-09398-A_DIKZGBNOM0/y4rz9dued01dtyl65nxqgd08wj2ar5cr6v/InstallAssistant.pkg

@fabiosun @Lorys89 What a crazy thing! I follow a model I created, which is this one: https://github.com/luchina-gabriel/BASE-EFI-AMD-RYZEN-THREADRIPPER I always keep it updated (Opencore, Kexts, Kernel Patches, etc.) month to month... I've been trying everything for more than 7 hours and haven't been able to boot the installer. With its EFI I made some small adjustments and it booted perfectly. I went crazy! I took this model of mine, inserted its DSDT and I just enabled RebaseRegions for her, and it worked perfectly! Summary of everything: This damn BIOS 1709 LOL LOL LOL! I'm going to follow my script here, to see if everything is working, and I'll share the results with you later. Thanks a lot for the help! 😄 😄 😄 [offtopic] My Italian passport should be out in a year! When I go to Italy, I'll have to buy you a beer! 🙂

My FX-6300 hackintosh can boot Sonoma 14.2 beta3 by legacy Clover 5155 with ProvideCurrentCpuInfo quirk enabled without blank screen issue now after its GPU RX-560 replaced by R9 270. No more need RadeonInit enabled now ! My config-5155-M5A.plist is attached for your reference. config-5155-M5A.plist.zip

Se nascondi tramite scanpolicy non vedrai più Win al boot Bisogna poi creare " Custom Entries " Guida nella mia firma Solitamente mettendo i file .ContentVisibity ...risolve ,lasciando scanpolicy sullo 0

Scusa se hai OpenCore perchè clicchi su f12? in uefi/bios nella sezione boot imposta come primo ssd quello dove è installato macOS

After a lot of work and a lot of help from @fabiosun and @Lorys89, the monster is finally ready! Thank you very much for your help! Asus ROG X670E Hero + AMD Ryzen 9 7950X + AMD Radeon RX VEGA 56 Component Versions macOS: Sonoma 14.1.1 Opencore: 0.9.6 AMD Kernel Patches: Latest from https://github.com/AMD-OSX/AMD_Vanilla BIOS: 1602 Some Notes Latest BIOS 1709 or higher, DSDT patch required, developed by @Lorys89 - Pls inject this DSDT.aml and set Enable/True RebaseRegions in config.plist This EFI is compatible with Intel Wireless and Bluetooth (onboard Wi-Fi 6e AX210) for macOS Ventura and Sonoma USBMap (corpnewt) method For BIOS newer or equal to v1709 Post reference Benchmarks - Speedometer v2.1 - Geekbench v5 & v6 https://browser.geekbench.com/v6/cpu/3609806 https://browser.geekbench.com/v5/cpu/21961976 - Dehancer Benchmark / Davinci - CPU Endurance for 10 minutes - Cinebench R23 - Cinebench 2024 (CPU & GPU) - Blackmagic RAW Speed Test - Blackmagic Disk Speed Test - Amorphous Memory Speed Test

Io uso coi kext citati da @fabiosun e modificati da @Lorys89 Macs Fan Control

Other users who also have the same issue please do dump your ACPI tables and post it here. Thanks!

Si si puoi usare amdpowergadget oppure anche dei kext che sono stati adattati da @Lorys89 io uso questi ultimi insieme ad hwsensorSMC

Beh che dire, sembra girare estremamente bene @fabiosun Grazie dell'aiuto!

macOS - 14.2 b3 build 23C5047e

Virtualization on AMD based Hackintosh on Sonoma real hardware... possible! The key program is Virtualbox 6.1.46 or its minor latest updates + related USB 3 extensions, where the code to support AMD-V/SVM are still present. VirtualBox 7 is not ok because it only works with VT-X/VT-D owned only by Intel CPUs now, nobody created a wrapper yet. But how can we get Virtualbox running on recent macOS? The prerequisite is to disable SIP and use the AMFIpass.kext with the bootflag -amfipassbeta in order to allow VirtualBox kexts to be loaded once installed, nothing more. In fact, once rebooted and allowed the kexts to run in Security section you can even disable the loading of AMFIpass.kext and remove the related bootflag, by now the kexts have bypassed the blacklist, forever! After that you can also install Windows 11 as a VM, direct without any issue, and the performance is also great if you don't overdo the number of cores (my maximum is 2 then it starts to slow down)!!! Me and @fabiosun have also experimented with various macOS: all of them work with the original ISO/DMGs starting from Tiger Server to Monterey... probably Ventura and Sonoma need an updated bootloader than the internal EFI one (which I'd like to understand what it is because it even performs better than clover and OC imho). Let's go through all the attempts made with the various macOS, as there is often a need for CPU spoofing since we have an AMD based host. For all Apple VMs the GPU will be emulated in EFI and should be set with 128Mb or where possible 256Mb RAM. Starting from Mojave till Monterey use the Mac OS X 64 bit template. Don't give more than 2 virtual CPUs to the VM or it will slow down. Set in Ports, USB -> USB 3.0 Controller (xHCI), hence the need to have VBox extensions installed. Set everything as per the screenshots where I do not specify anything else. With Tiger, I was only able to start the installation via Tiger Server 10.4.7 since the previous stock kernels do not work even with spoof. If we create the virtual machine with the name Tigro, the following commands are needed to start the installation, after selecting Mac OS X and Mac OS X 32 bit as Guest OS. Also set ICH6 as the controller for the disks, IDE. It is mandatory to choose only one CPU as processor otherwise we will have a panic: tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion EFI32..Virtual.Box tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro VBoxInternal/Devices/efi/0/Config/DmiSystemProduct "MacBookPro3,1" tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro VBoxInternal/Devices/efi/0/Config/DmiUseHostInfo 0 tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Tigro --cpu-profile 'Intel Pentium 4 3.00GHz' tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Tigro --cpuidset 00000000 00000004 756e6547 6c65746e 49656e69 tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Tigro --cpuidset 00000001 00000f43 00020800 fbffffff ffffffff tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Tigro --cpuidset 80000001 00000000 00000000 ffffffff ffffffff tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro VBoxInternal/Devices/smc/0/Config/DeviceKey "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC 1 tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro VBoxInternal2/EfiGraphicsResolution 1280x800 The startup speed is impressive! Here it is as I am upgrading the operating system to 10.4.11: For Snow Leopard select Mac OS X and Mac OS X 64-bit Snow Leopard, always one CPU. I used a retail installation DVD version 10.6.7 in ISO format. Startup always lightning fast! These are the commands by calling Snow the VM: tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Snow --cpu-profile "Intel Xeon X5482 3.20GHz" tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Snow --cpuidset 00000000 00000004 756e6547 6c65746e 49656e69 tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Snow --cpuidset 00000001 00000f43 00020800 fbffffff ffffffff tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Snow --cpuidset 80000001 00000000 00000000 ffffffff ffffffff tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Snow VBoxInternal2/EfiGraphicsResolution 1280x800 @fabiosun reports to me that the lines with cpuid definitions are redundant. You can omit them! For El Capitan always create a virtual machine by choosing Mac OS X 64 bit El Capitan from the templates, only strings to enter by hand, assuming you have named it ElCap: tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm ElCap --cpu-profile "Intel Xeon X5482 3.20GHz" tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata ElCap VBoxInternal2/EfiGraphicsResolution 1280x800 To create the iso I used the script https://gist.github.com/coolaj86/8c36d132250163011c83bad8284975ee. Place script and downloadable file directly from Apple InstallMacOSX.dmg in your home, give chmod +x to the script and run it. You will always get the el-capitan.iso file in your home ready for installation. Note that you can also use 2 CPUs this time, increasing the number as well as slowing down the boot may generate panic so watch out. For other versions of Mac OS X we will have to create the bootable media suitable for VBox ourselves. For Mavericks after downloading from the App Store and copying Install Mac OS Mavericks to the Applications folder we need to create a temporary 8 Gb blank volume using disk utility, File, New Image, Blank Image: The command to create the bootable media is: sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/Mavericks --applicationpath /Applications/Install\ OS\ X\ Mavericks.app --nointeraction We must then convert it to a disk image for VBox because an ISO would return an error since the Mavericks installation app must reside on a medium where it can also be written to: /Applications/VirtualBox.app/Contents/MacOS/VBoxManage convertdd ~/Desktop/Mavericks.dmg ~/Desktop/Mavericks.vdi Now the commands to be able to run the VM, named Mav, are: /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Mav --cpu-profile "Intel Xeon X5482 3.20GHz" /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Mav VBoxInternal2/EfiGraphicsResolution 1280x800 Create a Mac OS X 64 bit Mavericks VM, you can also use 2 CPUs, add among the storage devices a Hard Disk and give it the Mavericks.vdi image. Bring in Hard Disk as the first boot device. Inside the VM, before partitioning the virtual disk where you will install Mavericks, open Terminal and type: date 0202020216 Proceed slowly with partitioning and you will have Mavericks installed. For Yosemite proceed similarly, mutatis mutandis. The command for the date is: date 1020170014 From Catalina on up an empty 16384 MB image must be created in disk utility. To get the Installers from High Sierra and up use our blazoned Runme_downloaderV4 which I attach. The commands to create the bootable and writable installation media are respectively: sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/HighSierra sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/Mojave sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/Catalina sudo /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/BigSur sudo /Applications/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/Monterey ...and to generate the bootable vdi disk: /Applications/VirtualBox.app/Contents/MacOS/VBoxManage convertdd ~/Desktop/HighSierra.dmg ~/Desktop/HighSierra.vdi /Applications/VirtualBox.app/Contents/MacOS/VBoxManage convertdd ~/Desktop/Mojave.dmg ~/Desktop/Mojave.vdi /Applications/VirtualBox.app/Contents/MacOS/VBoxManage convertdd ~/Desktop/Catalina.dmg ~/Desktop/Catalina.vdi /Applications/VirtualBox.app/Contents/MacOS/VBoxManage convertdd ~/Desktop/BigSur.dmg ~/Desktop/BigSur.vdi /Applications/VirtualBox.app/Contents/MacOS/VBoxManage convertdd ~/Desktop/Monterey.dmg ~/Desktop/Monterey.vdi In particular, to allow, for example, the installation of Big Sur, assuming you have called the VM Mac, the commands to be given are: /Applications/VirtualBox.app/Contents/macOS/VBoxManage modifyvm mac --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff /Applications/VirtualBox.app/Contents/macOS/VBoxManage modifyvm mac --cpu-profile "Intel Core i7-6700K" /Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac19,1" /Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" /Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" /Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 /Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac “VBoxInternal2/EfiGraphicsResolution 1280x800 /Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac "VBoxInternal/TM/TSCMode" "RealTSCOffset" /Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-AA95B1DDAB278B95" The installation of Ventura and Sonoma is under consideration... for now they crash during the second pass of Sealing... I will try loading a generic OpenCore. Stay tuned! RunMe_DownloaderV4.zip

Full Installer ( Mist App ) https://github.com/ninxsoft/Mist/releases/tag/v0.9.1

14.2 Beta (23C5041e) 🙂

Buonasera, dopo svariati tentativi sembra che ho trovato un giusto compromesso, anzi più che buono, non ho neanche crash improvvisi per adesso, ho settato SetApfs TrimTimeout a -1 e sto usando un app che si chiama Trim enabler, e improvvisamente il boot lo ha fatto in 16 secondi e il trim sembra abilitato (vedete screen) e ha anche come performance non mi sembra affatto male. Meglio così 😇

Farei un tentativo x la 6700 con il Kext NootRX https://github.com/ChefKissInc/NootRX

Salve ragazzi, la scheda e- arrivata, ho dovuto fare un upgrade all'alimentatore, ho preseo un VX650W. vi allego lo screen delle informazioni. Vorrei fare un piccolo test ma non so dove partire, qualche consiglio? Grazie a tutti

macOS Sonoma 14.2 ( 23C5047e ) Full Installer https://swcdn.apple.com//content//downloads//49//25//042-99545-A_C4VQQ27KG5//jx6c4q0kb0zm992rqpl0m6sb3cyj6wnjx2//InstallAssistant.pkg

Adesso l'Audio della scheda grafica funziona! Grazie

passa un ioreg, da bios l hai setatta bene? windows 10 thunderbolt support mettilo enabled + rtd3

@luchina @lorys89 repo has a modified kext to work well with AMD system Original kexta is not updated for us

Copy/Download of EFI EFI-OC096-ASUS-ROG-CROSSHAIR-X670E-HERO-AMD-RYZEN-9-7950X-RADEON-VEGA-56.zip Important - EFI without kexts for Wireless because of the file size limit here on the forum; - Download of AirportItlwm for Sonoma: https://github.com/OpenIntelWireless/itlwm/releases/download/v2.3.0-alpha/AirportItlwm-Sonoma-v2.3.0-DEBUG-alpha-ff1138b.zip - Download of AirportItlwm for Ventura: https://github.com/OpenIntelWireless/itlwm/releases/download/v2.2.0/AirportItlwm_v2.2.0_stable_Ventura.kext.zip - Pls rename this files for "AirportItlwm-Sonoma.kext", "AirportItlwm-Ventura.kext" and copy to Kexts directory in EFI/OC/Kexts

non postare config presi cosi a caso su altri lidi qui non sono supportati il config precedente cera troppa immondizia ecco perché non funzionava quello che hai ora manca tutto

I tested with the new DSDT for the X670E Hero, and it worked with BIOS 1709. Now I'm testing with the previous BIOS and without DSDT to see if it works too. I had the misfortune of setting up the setup, updating the BIOS and getting this problem with the 1709. LOL! Thank you very much for all of your help.

Hey @fabiosun and @Lorys89, Thank you very much for the guidance from DSDT and EFI. I'm going to test it now, I'm just modifying it to remove the BCM because I'm initially going with the Ventura. I'll be back to give feedback! Regarding the videos, I can definitely give you a mention, thank you very much! 🙂

No @luchina @Lorys89 is writing a how to do so I didn’t update his modified dsdt

per la gpu oltre a SMC2 che vedi in foto quali parametri ti fornisce i soliti come Istat menus (sempre con i kext modificati per AMD)

Disattivato WEG e rimosso boot-arg pikera. Attivato resize bar e ora avvia correttamente @fabiosun

Finita installazione, ma al primo avvio di MacOS si riavvia EDIT: Risolto 😄

CSM da disabilitare, l'avevo perso di vista.

Se vuoi il nuovo vai di 6600 liscia, su eBay si trova questa XT però che è un usato praticamente nuovo, io ci farei un pensierino: la XT la uso in produzione dove lavoro per fare prores ed è una manna dal cielo. Nessun paragone con le Polaris!!! https://www.ebay.it/itm/325865684539

Ciao Ciro per la efi credo ti serva esclusivamente ssdt ec usbx e le nuove vanilla patches del kernel impostando 06 per le prime 4 ultimo Monterey o superiore nel bios csm off , 4g on cosi dovrebbe partire poi potrebbe servire mappare le usb per un eventuale Bluetooth se lo hai e lo utilizzi Domani provo a mandarti una efi se non hai già installato

gogolando in rete , ho trovato che gia qualcuno ha suo tempo era riuscito a far andare la cosa....

@Extreme™ @Giaccaz risolto mi è bastato reinstallare sonoma e adesso ho sotto la vers.16.78.3 va benissimo grazie a tutti a prescindere un ringraziamento particolare all'amico @fabiosun

eccolo👍

https://macos86.it/forum/34-mercatino-macos86/

Negativo, purtroppo.

passa log ioreg

nella gestione periferiche di windows i dischi sono già impostati in AHCI mode ed è per quello che non trovo l'impostazione nel bios. questo pc supporta solo AHCI mode.

@fabiosun fatte tutte le prove e ti posso dire che funziona, ovviamente dopo aver rinominato il file da .cdr a .iso

@carlos78quelli che ho in firma sono ottimi non uso ne kext ne particolari settaggi

23H2 22631.2506

metti questi cartella senza nome.zip

P.s.: se ottenete un errore riguardo la mancanza di dipendenze piazzate la cartella wxmac in /usr/local/Cellar e la cartella sdl2 in /usr/local/opt. Qualora mancassero proprio Cellar e opt createle manualmente. Le sdl2 fornite funzionano su Ventura: installatele con brew per tutte le altre versioni di macOS. Ciao a tuttiiii, voglio presentarvi il progetto PCem precompilato per macOS da BigSur in su, funzionante perfettamente anche su Hackintosh AMD. Si tratta di un emulatore di PC x86 dagli 8086/8088 agli 80686 altresì detti Pentium II, comprendendo un'enormità di schede video 2D ISA / PCI e i celeberrimi acceleratori 3D 3dfx, financo in configurazione SLI, e moltissime schede audio con relativi banchi sonori, come la AWE32 o la Soundblaster PCI, senza dimenticare l'incredibile GUS. Sul mio ammiraglio AMD Ryzen 9 7950x ho configurato un Pentium II 450 con uno SLI di Voodoo2 da 12 mb e Soundblaster AWE32 da 32 mb, e nella stragrande maggioranza dei casi non ho rallentamenti nell'esecuzione dei programmi. https://drive.google.com/file/d/1_d_MmlAnqBW8xdSp9r5xKFhr89pOOKYy/view?usp=share_link questo è Quake 2 con la suddetta configurazione a 1024x768: se lo scaricate invece di vederlo da browser potrete notare che sta quasi sempre a 60 fps. Ve lo allego già compilato correttamente per macOS da BigSur a salire, a risolvere un brutto segmentation fault, in caso vogliate provvedere voi stessi trovate i sorgenti qui, ma vi avverto che dovrete modificare i makefile sorgenti aggiungendo gli switch di compilazione -fno-inline-functions -mtune=native: https://github.com/PCemOnMac/PCemV17macOS Allego per comodità anche tutte le rom conosciute: sovrascrivetele in ~/Application Support/PCem/roms dopo aver eseguito e chiuso l'applicazione da terminale PCem, che la prima volta si lamenterà della loro carenza. Potete creare hard disk della dimensione che preferite sia in formato RAW .img che .vhd, Floppy disk, CD-Rom e emulare pure una scheda di rete. Lo trovo ottimo per creare retro-macchine virtuali a 32 bit con accelerazione video, normalmente problematiche con Wine a 32 bit sotto AMD Hackintosh. Ci ho caricato Windows 98 con il CD demo della AWE32, lacrimuccia per il sound che mi ricordava i miei 16 anni col mio primo 486 sniff sniff... PCemV17macOS.zip roms.zip sdl2.zip wxmac.zip