I'm stuck trying to install macOS Sequoia on GA-AB350-Gaming, Ryzen 7 2700X, Radeon RX 550

[spakk]

I’m currently stuck, as you can see in the video, and I'm not exactly sure where to start to fix the issue. Here are my hardware specifications, the settings I've configured, and the SSDT patch I’ve applied:

Hardware:

• Motherboard: Gigabyte GA-AB350-Gaming

• Processor: Ryzen 7 2700X

• Graphics Card: Radeon RX550/560 Series (4 GB, Polaris 21)

BIOS Settings:

      1. BIOS Update

        I updated the BIOS from version F30 to F53d to improve stability and compatibility.

     2. BIOS Parameters:

• Advanced Frequency Settings: Overclocking Mode set to "Disabled."

• Advanced CPU Core Settings:

• SMT (Simultaneous Multithreading): Enabled

• Cool & Quiet: Disabled

• Core Performance Boost: Disabled (to avoid instability)
  • Peripherals:
    • Initial Display Output: Radeon RX 550 configured as the primary graphics card in the first PCIe slot

    • Audio Controller: Enabled (for AppleALC or VoodooHDA)

    • Network Stack: Disabled

  • Chipset:
    • IOMMU: Disabled

    • SATA Mode: AHCI, Enabled

  • Power Management:
    • ErP (Energy-Related Products): Disabled (prevents sleep/wake issues)

    • SVM Mode (Secure Virtual Machine): Disabled

    • Power Loading: Enabled (helps with potential stability issues)

   3. USB Configurations:

• XHCI Hand-Off: Enabled (allows macOS to recognize and manage USB ports correctly)

• Legacy USB Support: Disabled (avoids USB issues in macOS)

 

   4. Boot Settings:

• Fast Boot: Disabled (important for macOS compatibility)

• CSM Support (Compatibility Support Module): Initially set to "Disabled," but the system kept rebooting into BIOS, so I switched it to "Enabled".

• Secure Boot: Disabled (macOS does not support Secure Boot on Hackintosh systems)

 

5.  

   SSDT-GPU-SPOOF.aml Patch:

• The SSDT-GPU-PROOF.aml file was customized for my graphics card and added to /EFI/OC/ACPI/.

 Patch:

SSDT-GPU-SPOOF.aml Patch:
// SSDT for AMD Radeon RX550 with VRAM set to 4GB
DefinitionBlock ("", "SSDT", 2, "DRTNIA", "AMDGPU", 0x00001000)
{
    External (_SB_.PCI0, DeviceObj)
    External (_SB_.PCI0.GPP8, DeviceObj)

    Scope (\_SB_.PCI0.GPP8)
    {
        if (_OSI ("Darwin"))
        {
            Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
            {
                Local0 = Package (0x06)
                {
                    // FakeID for device identification
                    "device-id",
                    Buffer (0x04)
                    {
                        0xFF, 0x67, 0x00, 0x00  // Adjusted based on PCI device ID (1002-67FF)
                    },

                    // Adjusted GPU name for display purposes
                    "model",
                    Buffer ()
                    {
                        "AMD Radeon RX550 Series"
                    },

                    // Set VRAM to 4GB
                    "VRAM,totalsize",
                    Buffer (0x04)
                    {
                        0x00, 0x00, 0x00, 0x40  // 4GB in hexadecimal format
                    }
                }
                DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                Return (Local0)
            }
        }
    }

    Scope (\_SB.PCI0)
    {                   
        Method (DTGP, 5, NotSerialized)
        {
            If (LEqual (Arg0, ToUUID ("a0b5b7c6-1318-441c-b0c9-fe695eaf949b")))
            {
                If (LEqual (Arg1, One))
                {
                    If (LEqual (Arg2, Zero))
                    {
                        Store (Buffer (One)
                            {
                                 0x03
                            }, Arg4)
                        Return (One)
                    }

                    If (LEqual (Arg2, One))
                    {
                        Return (One)
                    }
                }
            }

            Store (Buffer (One)
                {
                     0x00
                }, Arg4)
            Return (Zero)
        }
    }
}

Graphics Card Configuration:

·         GPU: AMD Radeon RX550 Series

·         PCIROOT(0)#PCI(0301)#PCI(0000)

·         ACPI(SB)#ACPI(PCI0)#ACPI(GPP8)#PCI(0000)

·         Direct3D: Radeon RX550/550 Series (Polaris 11/21 (Baffin))

Device Properties:

·         Device Name: Radeon RX550/550 Series

·         GPU Codename: Polaris 11/21 (Baffin)

·         PCI Device: 1002-67FF / 1682-9550 (Rev FF)

·         Assigned Memory: 4 GB

·         Driver Name: aticfx32.dll

·         Driver Version: 31.0.12027.9001

Device Driver Information:

·         Device: PCI\VEN_1002&DEV_67FF&SUBSYS_95501682&REV_FF\4&1c3d25bb&0&0019

·         Driver Name: oem136.inf

·         Driver Date: 02/20/2024

·         Driver Version: 31.0.21912.14

·         Provider: Advanced Micro Devices, Inc.

I’m unsure whether the issue is caused by the AMD Radeon graphics card or another missing driver that might be causing this loop. For reference, I’m testing with the pre-configured macOS Sequoia uploaded by MaLd0n.

Any detailed assistance would be greatly appreciated!

Thank you in advance.

 

EFI.zip

[MaLd0n]

Try this with bios/uefi in default just disable SecureBoot

EFI-spakk.zip

You can extract USB kext on windows with UsbToolBox

idk if u need Processor things. Just try.

[spakk]

56 minutes ago, MaLd0n said:

Try this with bios/uefi in default just disable SecureBoot

EFI-spakk.zip

You can extract USB kext on windows with UsbToolBox

idk if u need Processor things. Just try.

Thank you for the prompt response. I added the EFI folder with the UTBMap.kext into the new EFI folder, included the UTBMap.kext in the config.plist, and restarted. However, within seconds after the boot process, the system resets.

[MaLd0n]

Boot start? if yes check resize bar on bios/uefi.

[spakk]

9 hours ago, MaLd0n said:

Boot start? if yes check resize bar on bios/uefi.

Sorry, my mistake, I didn’t notice that😃

 

 

Edit:

as described above: When I set CSM to "Disabled," the computer boots directly into the BIOS menu. However, if I set CSM to "Enabled," I can boot normally and either start Windows or access the macOS installation via USB.

 

Here is the boot process after making the change.

 

 

 

 

Here’s the situation: during boot, the system resets. Unfortunately, the video quality is terrible

 

 

 

 

[spakk]

Problem 1

The issue causing the system to suddenly reset shortly after booting was due to a minor oversight when editing the spakk.aml file. This SSDT is not optimized for a Ryzen CPU like the Ryzen 7 2700X, as it defines multiple processor objects (PR00 through PR31). This configuration corresponds to a typical multi-core setup designed for a high number of threads or logical CPUs. Since the Ryzen 7 2700X has 8 cores and 16 threads, the system could not logically boot properly with this SSDT. After modifying the SSDT for the Ryzen 7 2700X with 8 cores and 16 threads, it was possible to boot again. Unfortunately, the suggestion from Chris to remove the entries “bluetoothExternalDongleFailed” and “bluetoothinternalControllerInfo” also did not resolve the issue.

 

 

 

Here is the corrected SSDT in case anyone needs it:

 

/*
 * Intel ACPI Component Architecture
 * AML/ASL+ Disassembler version 20210930 (32-bit version)
 * Copyright (c) 2000 - 2021 Intel Corporation
 * 
 * Disassembling to symbolic ASL+ operators
 *
 * Disassembly of .../EFI/OC/ACPI/spakk.aml, Sat Oct 26 22:41:21 2024
 *
 * Original Table Header:
 *     Signature        "SSDT"
 *     Length           0x00000281 (641)
 *     Revision         0x02
 *     Checksum         0x65
 *     OEM ID           "spakk"
 *     OEM Table ID     "AMDesk"
 *     OEM Revision     0x00001000 (4096)
 *     Compiler ID      "INTL"
 *     Compiler Version 0x20240927 (539232551)
 */
DefinitionBlock ("", "SSDT", 2, "spakk_RYZEN", "R7_2700X", 0x00001000)
{
    Scope (\_SB)
    {
        Device (EC)
        {
            Name (_HID, "spakk_RYZEN0001")  // _HID: Hardware ID
        }
    }

    Scope (\_SB)
    {
        // Defines 16 processor objects for Ryzen 7 2700X (8 cores, 16 threads)
        Processor (PR00, 0x00, 0x00000410, 0x06){}
        Processor (PR01, 0x01, 0x00000410, 0x06){}
        Processor (PR02, 0x02, 0x00000410, 0x06){}
        Processor (PR03, 0x03, 0x00000410, 0x06){}
        Processor (PR04, 0x04, 0x00000410, 0x06){}
        Processor (PR05, 0x05, 0x00000410, 0x06){}
        Processor (PR06, 0x06, 0x00000410, 0x06){}
        Processor (PR07, 0x07, 0x00000410, 0x06){}
        Processor (PR08, 0x08, 0x00000410, 0x06){}
        Processor (PR09, 0x09, 0x00000410, 0x06){}
        Processor (PR10, 0x0A, 0x00000410, 0x06){}
        Processor (PR11, 0x0B, 0x00000410, 0x06){}
        Processor (PR12, 0x0C, 0x00000410, 0x06){}
        Processor (PR13, 0x0D, 0x00000410, 0x06){}
        Processor (PR14, 0x0E, 0x00000410, 0x06){}
        Processor (PR15, 0x0F, 0x00000410, 0x06){}
    }

    Scope (\_SB)
    {
        Device (USBX)
        {
            Name (_ADR, Zero)  // _ADR: Address
            Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
            {
                If (!Arg2)
                {
                    Return (Buffer (One)
                    {
                         0x03                                             // .
                    })
                }

                Return (Package (0x08)
                {
                    "kUSBSleepPowerSupply", 
                    0x13EC, 
                    "kUSBSleepPortCurrentLimit", 
                    0x0834, 
                    "kUSBWakePowerSupply", 
                    0x13EC, 
                    "kUSBWakePortCurrentLimit", 
                    0x0834
                })
            }
        }
    }
}

 

Problem 2

The boot log shows various events and warning messages related to the bluetoothd service on my system. Here’s a summary of the information I gathered from external sources:

1.   Start and Stop of bluetoothd: The bluetoothd service is started multiple times (e.g., “Successfully spawned bluetoothd[196]”) and then shut down (e.g., “exited due to exit(1)”), which indicates issues that could cause macOS to crash during boot.

2    2. Lookup Warnings: The log includes error messages such as:

• failed lookup: name=com.apple.logd

• failed lookup: name=com.apple.securityd.xpc

• failed lookup: name=com.apple.analyticsd

These warnings indicate that the system is attempting to access certain services or processes but cannot find them. This might point to corrupted system files or permission issues.

 

1.   Unmonitored Process: The message “Job is not monitored, can't poll” suggests that the bluetoothd process might not be monitored correctly, which leads to repeated terminations and restarts of the service.

2.  Spawning Loops: The log indicates that the bluetoothd service is trying to start in a looping pattern (service state: spawning). This suggests the system may not be able to successfully start and stabilize the service.

 

Possible Causes and Solutions:

1.   Repair System Files:

• Run the Disk Utility and use “First Aid” to check and repair any file system errors.

2.  Reset Bluetooth Modules:

• Reset Bluetooth settings by deleting the com.apple.Bluetooth.plist file in the Library/Preferences directory and restarting the system.

3.  Reset NVRAM and SMC:

• Resetting NVRAM and SMC can help stabilize the system and potentially resolve Bluetooth issues.

4.  Install macOS Updates:

• Install the latest macOS updates to ensure that all services and drivers are up-to-date and known bugs are fixed.

 

 

I will probably need to download a new Install.app to create a fresh USB installer. It’s possible that the download of the “raw” file was briefly interrupted, causing a defect, though this is just a guess. Thank you both for your support. It took some time to identify the root of the problem, but I’ve learned a lot in the process.

[Shaneee]

I used to have this exact board a few years back, in fact I still have it but no spare RAM for it. I do however remember that no special ACPI files were required for it. Just the usual generic EC/USBX SSDT along side the required kexts and our AMD kernel patches. If I recall I had the 2400G at this point and used both a RX 560 and RX 480 on this board... I have a Athlon 200GE somewhere and if I borrowed RAM from my system could test it out if I get a chance and share an EFI for you

[MaLd0n]

1 hour ago, spakk said:

This SSDT is not optimized for a Ryzen CPU like the Ryzen 7 2700X, as it defines multiple processor objects (PR00 through PR31)

This thing don't cause problem to boot. Most people use an ssdt set to 64 and just work. Just appear extra things on ioreg/log. 

[spakk]

Just now, Shaneee said:

I used to have this exact board a few years back, in fact I still have it but no spare RAM for it. I do however remember that no special ACPI files were required for it. Just the usual generic EC/USBX SSDT along side the required kexts and our AMD kernel patches. If I recall I had the 2400G at this point and used both a RX 560 and RX 480 on this board... I have a Athlon 200GE somewhere and if I borrowed RAM from my system could test it out if I get a chance and share an EFI for you

Hi Shaneee,

Thank you so much for your help! However, I don’t think the issue is with the EFI. The EFI content should work just fine, except for the small issue with the SSDT, just as MaLd0n prepared it. The boot process matches exactly the error description above and what Chris suspected at the beginning.

I’m currently downloading an image to completely reinstall the USB installer and run the test again.

[spakk]

Just now, MaLd0n said:

This thing don't cause problem to boot. Most people use an ssdt set to 64 and just work. Just appear extra things on ioreg/log. 

Hi MaLd0n,

I believe you that it works that way, but my system didn't handle it properly and actually caused a reset after booting😟

[MaLd0n]

k

Do u enable RX550?

[spakk]

On 10/27/2024 at 2:24 AM, MaLd0n said:

k

Do u enable RX550?

Yes, I enabled the graphics card in the Config.plist, and so far there have been no indications of a graphics card problem during boot, as far as I can tell from the boot log

 

Edit:  

I have to put the test on hold for a week. Today, the eye surgery is scheduled first. If everything goes well, I'll get back to working on my Hackintosh after the week of rest.