Barfish AMD radeon r9 350x stuck on installing Ventura and Sequoia

[Naveed]

i am trying to install macos via Opencore

my Pc Biostar B550MH
CPU ryzen 5 5600
Ram memory 24GiB
Graphics Barfish AMD Radeon r9 350x 2gb

my efi Attached help me Brothers

 

[Edhawk]

Your SSDT-SBUS is not set correctly for your system. I would recommend disabling or removing the SSDT.

When installing macOS on your Sys I would recommend you only have SSDT-CPUR.aml and SSDT-EC-USBX.aml present and enabled in your /EFI/OC/ACPI folder. Any other custom SSDTs can be create and added after macOS has been installed.

 

[Naveed]

Your SSDT-SBUS is not set correctly for your system. I would recommend disabling or removing the SSDT.

When installing macOS on your Sys I would recommend you only have SSDT-CPUR.aml and SSDT-EC-USBX.aml present and enabled in your /EFI/OC/ACPI folder. Any other custom SSDTs can be create and added after macOS has been installed.

Thanks for reply, i try without ssdt.

 

[Naveed]

Dear Sir now check what error is this, i boot only ssdtcpur.aml and
ssdt usbx-desktop.aml

 

[Edhawk]

I need to have a look at your EFI folder contents, when I am at my desk. I am currently using an iPad so won’t be downloading anything for a while.

 

[Naveed]

Ok Sir

 

[Edhawk]

I have a very similar AMD system to yours, Asus TUF Gaming B550 Plus WiFi II. Ryzen 5 5600G, VEGA 56 that is still running macOS Sonoma.

The only issue I see with your setup is your AMD R9 390X GPU, it is not natively supported in macOS beyond Monterey.
So installing Sequoia may require that you use OpenCore Legacy Patcher (OCLP) to get graphics acceleration working.
It will not work during the installation process, to my knowledge.

AMD GPUs | GPU Buyers Guide

Upgrading to a natively supported GPU might be your best course of action, if you run in to too many issues with the R9 390X.

Installing Monterey in the first instance might give you more joy, and once the R9 issues have been resolved update to Sequoia with the fixes in place.

EFI folders:
Your EFI should be very similar to mine, which looks like this:

My OC 1.0.2 EFI folder contents as viewed in Finder. Your EFI folder contents

ACPI folder:

1. The SSDT-EC.aml, SSDT-HPET.aml and SSDT-USBX.aml tables in my ACPI folder were generated from my system DSDT.aml and Corpnewt's SSDTTime python script. So they were custom created for my system.
2. The SSDT-SBUS-MCHC.aml table was created using the information from my system DSDT.aml, so again custom for my system.
3. The only 'Generic' ACPI table in my setup is SSDT-CPUR.aml.
4. You can create these custom SSDT's in Windows or macOS with Corpnewt's SSDTTime script.
   1. https://github.com/corpnewt/SSDTTime

• Your SSDT-MCHC.aml and SSDT-SBUS.aml look like they have been created from or for an Intel system, as the IOReg Pathnames don't match what I would expect for an AMD system.
• The SSDT-CPUR.aml, SSDT-HPET.aml and SSDT-USBX.aml appear to be OK.
• You are however missing an SSDT-EC.aml, which is essential for your system to boot macOS.
  • There may have been a misunderstanding with regards my earlier post, if you deleted this SSDT. As normally people use the generic SSDT-EC-USBX.aml when first installing macOS, which I expected you to retain in your ACPI folder.

Your Drivers, Resources and Tools folder contents are OK.

Kext folder:

1. We have different Ethernet controllers, so the kexts required by our systems are different.
   1. My 2.5GB Realtek Ethernet requires LucyRTL8125Ethernet.kext
   2. Your 1GB Realtek Ethernet requires RealtekRTL8111.kext
2. The rest of the kexts in this folder should be the same.
3. You do not need to use AMDRyzenCPUPowerManagement.kext or SMCAMDProcessor.kext when installing macOS.
   1. These are not essential and to be honest can cause more issues than they are worth.
   2. I would recommend deleting these two kexts.
4. USBPorts.kext.
   1. Unfortunately this doesn't appear to be correct for your system. It is probably close, but not completely correct.
   2. Your Booster B550MH motherboard contains the following USB ports:
      1. 8 x USB 3.2 (Gen1) ports (4 on rear I/Os and 4 via internal headers)
      2. 6 x USB 2.0 ports (2 on rear I/Os and 4 via internal headers)
   3. This means
      1. You have a maximum of 16 x ports that should be set with the connector type USB3 (3).
         1. 8 x Physical USB3 ports and 8 x virtual USB2 ports.
         2. 8 of these ports are provided by 2 x motherboard USB headers, serving your Front Case ports.
         3. You may not be using both USB3 headers, if so then a maximum of 4 ports will be available.
         4. Motherboard layout showing the locations of the USB3 and USB2 headers
      2. The 2 x USB2 headers should provide a maximum of 4 x ports.
         1. These will be serving Front Case connectors and any Bluetooth module, if present.
         2. These ports should be set with connector type 'Internal' (255), not as USB2 (0).
      3. You have a maximum of 2 x USB2 Physical ports that should be set with the connector type USB2 (0)
         1. The 2 x ports on the Rear I/O plate with the Black Tangs, immediately below the Ethernet connector.
         2. 
            
         3. Rear I/O plate showing 6 x USB ports, 4 x USB3 (Blue tang) and 2 x USB2 (Black tang)
   4. If all the USB ports available are activated in your system then you would have a maximum of 22 x ports.
   5. You have to remember that with an AMD system you are not stuck with the 15 x port limit the same as Intel systems.
   6. Your Motherboard appears to support 2 x USB controllers, PTXH and XHC0,
      1. So you could in theory activate 30 x USB ports, as each USB controller can support 15 x ports.
         1. 16 x ports set as USB3
         2. 2 x ports set as USB2 physical (Black tang)
         3. 4 x ports set as Internal (USB2 motherboard headers ports)
   7. Your USBPorts.kext contains the following:
      1. 5 x USB3 physical ports
      2. 4 x USB3 virtual ports
      3. 3 x USB2 physical ports.
   8. The wrongness in your setup is that you have 3 x USB2 physical ports, when there are only 2 x USB2 ports available on your motherboard.
   9. Presumably one of these ports is actually served from a USB2 header.
   10. Using your current USBPorts.kext may cause you unnecessary issues during installation, so I would recommend deleting or disabling the kext.

When you look to install macOS, I would recommend you use one of the 2 x USB2 physical ports for your USB installer, as they are less likely to cause issues during the installation process.

I am going to create a new/clean OC EFI for your system, which I will post below shortly.

 

[Edhawk]

Here is a revised OpenCore 1.0.2 EFI folder for your B550MH/R5 5600 system.

I have made the changes listed above.
I have removed any unnecessary or incorrect entries.

Testing/Booting:

1. Assuming you want to try this revised EFI, I have added your Serial Number, MLB, ROM and SystemUUID data to the revised config.plist.
2. Don't make any changes to the setup.
3. Copy the revised EFI folder to the EFI partition on your MacOS Installation USB pen drive and boot from the pen drive.

You will need to use the ResetNvramEntry.efi option before you boot with this revised OC setup, to clear any old or obsolete NVRAM settings from the system.

• Simply boot from the USB pen drive, press the Spacebar when you arrive on the OC boot screen (GUI),
  • This will unhide the tools and drivers contained in your OC setup.
• Select the ResetNvramEntry.efi and the system should automatically reboot.
• Select your USB pen drive from the system Boot Menu again, and
  • This time select the macOS installer from the OC boot screen.

I would recommend removing or disconnecting any other drives you may have in your system (Windows, Linux or Data drives).

Let us know how this goes.
IF you get a Kernel Panic, take a photo and post it here, so wee can see what is causing the KP.