iATKOS | United Kingdom

The error message WaitSecsForNotBusy: : 3905:Port 0 PxTFD: 0x150 typically points to an issue related to the storage controller or the communication between the motherboard and the storage device. When installing macOS on a Hackintosh, especially with AMD CPUs like your Ryzen 7 5800X, it's important to ensure that the EFI configuration is correctly set up for AMD systems, as they require specific patches and adjustments.

Here are some troubleshooting steps you can take:

1. Verify AHCI Mode: Ensure that your BIOS is set to AHCI mode for SATA operation. This is necessary for macOS to communicate correctly with your drives.

2. Check Storage Kexts: Ensure you have the appropriate kexts for your storage controller. For AMD systems, you might need third-party kexts that support the controller on your ROG STRIX B550-F motherboard.

3. Update BIOS: Make sure your motherboard's BIOS is updated to the latest version, as this can resolve compatibility issues.

4. Correct SSDT and DSDT Patches: Make sure you have the correct SSDT or DSDT patches applied for your system. AMD systems usually require different patches compared to Intel-based systems.

5. AMD Specific Kexts and Patches: Ensure you're using an AMD-specific OpenCore EFI folder. You will need specific kexts like AMD_Vanilla patches in your config.plist.

6. USB Mapping: Incorrect USB mapping can sometimes cause the system to hang. Verify that your USB ports are correctly mapped in your EFI configuration.

7. Boot Args: Check your boot arguments (boot-args) in your config.plist. For AMD systems, you may need to include arguments like npci=0x2000 or npci=0x3000, and agdpmod=pikera for your RX5500xt GPU to prevent black screen issues.

8. Verbose Mode: Boot in verbose mode to see where the boot process stops. This can give you clues about what's going wrong.

9. OpenCore Sanity Checker: Use the OpenCore Sanity Checker online to verify your config.plist against your hardware.

10. Consult the Hackintosh Community: Check forums and communities specifically for your hardware setup. Someone with the same hardware may have encountered and resolved the same issue.

Since you mentioned that you've had a Kernel Panic previously and the error message changes with each reboot, it could also indicate a general instability in the EFI configuration. Double-checking each of these areas thoroughly can help resolve the boot issue.

If you have access to the error logs or the EFI folder, I could provide more specific advice. It's often a process of trial and error, and community support forums can be very helpful in resolving these types of issues.