Search results

I suggest to try to leave only the second mmio enabled and see if it boots fast If you have all stuff i see in your signature maybe some devices slow your boot

@Mylo i see your EFI in other thread in Sonoma it was working if i understood well is it always working in Sonoma, or now you doesnt boot any osx? if so, Have you updated your Gigabyte Bios? i see also you use DevirtualizeMMIo quirk and disableVariableWrite quirk they shouldnt be useful for...

A 265-9950x dual rx 6950xt 192Gb DDR3 4800 19.1.3 Studio (@fabiosun) Added my dual GPU benchmark

@JohnFante I used now your last working EFI backup This EFI couldnt work for latest OS for three main reasons New AMD kernel patches, new MMIO changed with latest bios you use and SecureBootModel setting Let see now i disabled some kexts for now till you will be able to pass that hang Edit I...

@JohnFante I am short of ideas to try I bypassed MMIO stuff using DisableVariable quirk and ACPI patches are there for your Gigabyte I am very curious to see your previous working config.plist with Sonoma (and old bios version if i understood well your message because it is weird we havent...

Yes A spoof and a ssdt bridge nothing else

Mmhhh now no ACPI error (it seems so) but no boot could you try this and if it is the same hang try to change only usb port you are trying to boot?

Using the same EFI only change this config.plist Let see if it does some good results :) Clean Nvram (as usual)

Johnfante, use this EFI you should see a different graphic in boot menu Let see if we win :) I used latest data from your SysReport folder and all the patches SSDTTime does for your system also used a minimal set of kext..if it will work then you have to add other kexts and map your USB port

@JohnFante Are you sure you are using Efi i posted above?

@JohnFante with the help of CorpNewt from AMD OSX Discord channel he understood that some SSDT was not proper for your system try this EFI then if system does a step forward we will try to adjust MMIO Area if you have 4G option in your BIOS set it to on

could you post only ACPI section of that config.plist (the working one i mean)

@JohnFante I wonder if you update your motherboard bios from when you had a working sonoma in this system If not, it is weird ifyou didnt use acpi patches or dsdt patched before

@JohnFante i see always an important ACPI error This means your DSDT must be patched better (via ACPI patches) i sent your DSDT to CorpNewt and he will take a look on it whwn he has time

@JohnFante if you like try this config (rename it before) and let see if you do a step forward in this config i have bypassed (for now ) mmio whitelist to see if your config has oter problems than MMIO! Post a photo or a video where it hangs

Have you tried my config.plist?🥹

attached config is based from Edhawk's one a bit simplified till you achieve a working boot if you like to try (first backup yours)

@JohnFante attached is your config.plist. i added a proper converted from hex to number MMIO area from your debug log and i added also ACPI patch done using your DSDT and SSDTime script this should allow you to by pass Gigabyte mistake on acpi and also MMIO hang I have no checked at my best...

@JohnFante if you had a previous working EFi with sonoma you have only to update your kernel patches for AMD Efi proposed has some typo in Nvram section (bootarg like E1000=0 not useful with ethernet kext i see in your kext folder) Probably in your previous (and working sonoma EFI) you add also...

could you post here that working EFI? thank you