Search results

Have you tried to disable whatevergreenkext?

then, official whatervergreen kext must be disabled in first installation steps i think also your 6600 doesnt need of it (not sure of this)

are you doing a clean install in another disk or are you updating your previous OSX installed?

Yes some mess also in this EFI If you like, backup yours and use this one attached: if you use it in initial boot menu reset/clear Nvram then choose your booting icon and click on it with ctrl key pressed and left mouse butto on icon to fix your os booting icon (it useful when you reset Nvram...

OCLP it seems you use for broadcom wifi in attached EFI , it DOES not work with tahoe @unclesam

Corpghost did patches for this user and motherboard.. I do not know if he took other patches in a other place because also latest efi is changed in a wrong way

This message. You said you booted in SOnoma so you must start from here adjusting things from here I mean Sonoma/Sequoia should work fine with minimal adjustment in bootloader and Kernel Patches

Hi @pvford55 if you see this EFi is worst than previous one you use and it does not start Opencore booting process You miss an important part for asus motherboard (ACPI patches for bios done by CorpGhost or also @etorix if he has some time to do :) ) You should add those patches to this config...

Yes it is possible. you could check also this thread where many systems as yours have been well configured in the near past time: https://macos86.it/topic/3307-discussion-trx40-bare-metal-vanilla-patches/

Hi you should re-check starting from here In Latest EFI you added stuff you do not need USB mapping must be done to see your audio and all USB port you use If your motherboard has USB audio you do not need any kext for it (APPLEAlc i mean) no layout id and similar stuff You miss then a useful...

this EFI is completely different from previous one you posted it has stuff not useful for you if you are trying to instal a new OS i suggst if possible to use a opencore debug version and to enable SysReport to have a printout of your ACPI folder From this you can produce then useful SSDT and...

replace completely them with the ones corpghost did for you :) Edit If you have problem post here only config.plist and patches.plist corpghost did for you

@pvford55 in this EFI you have to put (and to change) only the section ACPI/Patches tha CorpNewt did for you on discord server No need anymore to pu entire EFI or Sysreport (only a photo or video of your verbose output if system hangs or reboot So take the file patches.plist done for your...

@pvford55 Realtek 5Gb Ethernet is not compatible with any OSX for now, in this EFI you missed again DevirtualiseMMIo quirk and other stuff mandatory to boot in AMD X670/x870E platform, and you had also a pleteroa of ethernet kexts So to install you have to build a full installer for OSX or use...

to generate it SSDTTime asks for system ACPI folder..then it takes what installed hardware needs to create proper SSDT In my case i have system you can see in my signature (so x870e and 9950x CPU (16c/32t) edit: attached my ssdt

Edhawk maybe i am completely wrong but SSDTTime calls plugin type (option 5) a similar option... (i use it in my AM5 system)

@lfbaptista your opencore log are not useful because they miss of many usefull data as MMIO area for now i have bypassed to build a proper MMIO whitelist area but in a future you should do it well (also if you luckily boot fine with this) Also, your cpu is a 12 cores cpu so 08 was wrong as cores...

No, in my case also in ventura they are useful to boot(without it many acpi errors and system hangs) @CaseySJ if you are talking about ACPI patches useful for different board and manufacturer as your ASUS and mine)

<IT> Ciao Sembra invece che non serva nessuna patch particolare per il 9900 (e questo e' emerso anche parlandone con Shaneee) <\IT> <EN> Hi it seems your 9900 does not need any different patch (and this was also discussed in private with Shaneee sometime ago) <\EN>

your system could work..but your EFI is a disaster! it misses many parts mandatory to have the chance to boot and ProxMox route is very different to vanilla way! 1) DevirtualizeMMIO quirk and relative MMIO Whitelist area set (or without setting it enabling also a quirk like...