Search results

In this zip you can find your previous config.plist updated with Tahoe AMD Kernel Patches, some boot arg deleted (amfi and other) more two kexts you have to overwrite yours USBPort is done by Svan71 user in this thread (modified for Tahoe as he said)and whatevergreen is a modified version done...

@hinkin post only your config.plist cleaned from your serial data, i mean a working one with a previous os

@hinkin your EFi is not compatible with Tahoe in many parts First kexts section (also other kernel/block part) It seems you use a broadcom WIFi which for now it is not supported on Tahoe via OCLP it seems you use So, if it is a clean installation from scratch you have to modify some maxkernel...

If you like you can try these configs and see if something change I see you have an USBport kext but it is not working for you and maybe it is not done for your mothrboard

@pvford55 have you tried to move your keyboard on usb mouse working port ( only to see after so long time your is up and running? 😀) Now you should try to map well your usb ports from Windows or find a pretty similar usb port configuration than yours from other users

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