Sonoma OC boot problem

[_HITMAN_]

Mobo: Asrock Steel Legend x670e
RAM: 2 x 16 Kingston Fury 6000 MhZ
CPU: Ryzen 9 7900X
GPU: Power Color Devil 6800XT

I was following the guide for OC install but i'm stuck at booting. BIOS is the latest with recommended options according to guide i even disabled iGpu in BIOS. Changed like 4 usb port the result is the same. I'm attaching my .plist file and screenshot.
Any help is appreciated.

 

[Edhawk]

You have an error in one of the SSDT's you are using in your setup, as highlighted in the screenshot below.



Find the SSDT with the matching APCI device path and remove or edit the SSDT to fix the error. As you only posted a copy of your config.plist we can't point you to the suspect SSDT.

 

[_HITMAN_]

Hello Edhawk,
please find attached full EFI folder. I have only one SSDT-EC-USBX-DESKTOP.aml. By ACPI device you mean sb.pcio.gpp7.up00.dp40.up00.dp68?

I was following this guide -

 

[Edhawk]

You seem to have forgotten to include the CPU core count in the first three AMD Kernel patches. Your 12-core CPU requires that you add '0C' to the first four kernel patches, in place of the 3rd and 4th numbers in the Replace field. You have the correct core count entry in the fourth patch, which would be fine for Ventura or Sonoma.

The SIP entry in the config.plist isn't correct, you have <67000000>, which is an old setting from Clover. You should try running the system with SIP enabled <00000000>. Before looking to use a lower level of SIP. See the link below for disabling SIP.

# Disable SIP OpenCore

The SMBIOS you are using is wrong for your setup. As you have a fully functional discrete GPU, but don't have an IGPU in your system you should be using MacPro7,1 or iMacPro1,1. You should not be using an iMac20,2 SMBIOS, due to the lack of an IGPU, which that system expects to be present.

As you say, there are no other SSDT's enabled in your setup. So I have no idea what caused that error message to be generated.

1. You may need to make sure that none of the drives in your system contain an old EFI folder in any of the EFI partitions.
2. Try using the ResetNvramEntry.efi driver from the OC Picker List, to see if that message was a hang over from a previous installation attempt.
   1. Press the spacebar while on the Picker list screen to display the hidden Drivers and Tools. Selecting the ResetNvramEntry Driver will clear any existing NVRAM entries and automatically reboot the system. So only the NVRAM entries in the new setup are used.
3. You may need to remove any other drives (Windows, Linux, Data drives etc.) while installing macOS, to eliminate any issues that they may bring to the table. This would be temporary while installing and running the Post-Install processes.

 

[_HITMAN_]

I tried all of the above suggestions andsteps (except removing all the drives) and nothing did change I'm going to try https://dortania.github.io/OpenCore-Install-Guide/prerequisites.html and see what will happen. Today was busy day but maybe i will be able to do quick test rebuilding all from scratch. This is a first time i'm trying to install macos on AMD, last 10+ years I was using Intel cpus.

Thank you for trying to help!

 

[_HITMAN_]

Ok tried again following opencore guide, now it hangs quite fast. iTryed - https://dortania.github.io/OpenCore...rnel-issues.html#stuck-on-eb-log-exitbs-start without Using DevirtualiseMmio. No success the error stays the same. Before every boot i did Clear NVRam.

71:264 00:165 AAPL: #[EB.LD.OFS|OPEN!] Err(0xE) <"usr\\standalone\\OS.dmg.root_hash">
71:310 00:045 AAPL: #[EB.RH.LRH|P!] Err(0xE) <- EB.LD.LF
71:462 00:151 AAPL: #[EB.BST.FBS|!] Err(0xE) <- EB.RH.LRH
71:612 00:150 OCSMC: SmcReadValue Key 4D535463 Size 1
71:658 00:045 OCSMC: SmcReadValue Key 4D534163 Size 2
71:814 00:156 AAPL: #[EB|LOGT] 2023-11-14T20:56:12
71:965 00:151 AAPL: #[EB|LOG:EXITBS:START] 2023-11-14T20:56:12

 

[_HITMAN_]

Hello, after some play with DevirtualiseMmio i was able to install Ventura. Everything seems to work sleep, usb, sound .. except WIFI but i really don't care i'm on wired network.

Trying to upgrade to sonoma produces exactly the same error as above post. I will keep trying when i have more free time.