Recent content by silkroadonsale

if you need AppleIntelI210Ethernet.kext then I just add this kext for you. also if it doesn't work then you need combination `SSDT + this kext and boot args

you can test with AppleIGC.kext to see if it work or not. if it doesn't work you can still use the old method which is adding AppleIntell210Ethernet.kext plus the boot args e1000=0

I'm afraid not though if Dev want to support they have rewritten entire code for 5G b/c it's different than the one they Dev atm.

post your hardware specs, it's easier for diagnostics. base on your EFI provide, it's either conflict by so many drivers that you have in Drivers folder. also your ACPI is a mess. you can take a look on https://chefkiss.dev/guides/hackintosh/ website for further guidance how to make proper EFI...

for AM5 system, you need to Generate your own SSDT files to work with your hardware like SSDT: Plug-alt.aml, EC.aml and USBX.aml. also it required to have proper configuration for Mmiowhitelist entries to make it work properly. set SecureBootModel to Disabled. the rest setup just like AM4 with...

in order to make Tahoe to work, first you need to get the right SSDT files for your system like SSDT-Plug-alt.aml, SSDT-EC.aml and SSDT-USBX.amal. second which is required Mmiowhitelist Entries configuration correctly and the reset setup just like AM4 with B550/A520. For Sonoma or newer macOS...

https://github.com/AMD-OSX/AMD_Vanilla/branches Look for Beta section.

Are you use OC-Simplify to Generate your EFI?

yes you can but you need to update kext to latest version, and you have to use beta patch for Tahoe. also you need to dealt with FileVault before you update it to your main hack b/c Tahoe is automatically enable it.

you are missing revpatch=auto,sbvmm. if you want to use OTA then you need to remove auto world out otherwise it will break the OTA update.

you don't have latest amd kernel patch yet. so just replace with latest and fix all necessary thing that required then u are ok to update to Sonoma.

is that the x stand for Enable? this is weird though. Or you can check to update latest BIOS to see if it fix the issue?

only last resource is remove npci=0x3000 and try to use this one to enable above 4G decoding to test out. https://github.com/DavidS95/Smokeless_UMAF

I attach exact specifications of my equipment in case it helps. I made some change for your boot arg b/c you didn't put it in right .. u can test the EFI I upload to seen any better. also take screenshot and upload it here is much easier for troubleshoot.

add these 3 to your boot args and test again to see what error you get next. since your laptop doesn't have support above 4G decoding so you have to use the npci= boot arg to by pass it.