AMD FX CPU macOS Sonoma Black Screen Problem

[Hyuna_4443]

Hello, Everyone.

I am using Hackintosh on an AMD FX system.

AMD Vanilla Kernel was used, and AVX2.0 was patched with OCLP to obtain normal graphics acceleration.

However, they have not yet fixed the bug where the login screen does not appear when first booting and only a black screen flashes.

Skipping login and going to the desktop solves the problem, but if I lock the screen or use sleep mode, WindowServer or LoginWindow crashes immediately.

To fix this bug, I tried switching to Clover Bootloader, switching Legacy/UEFI, turning off CSM, deleting WhateverGreen, using Framebuffer (iriri, Kamarang), and using RadeonDelnit (Clover), but it did not work.

One unusual thing is that if acceleration is disabled with the '-amd_no_dgpu_accel' boot option, both login and lock functions work normally, and in macOS Big Sur and lower, all functions work normally with the same EFI.

macOS Monterey, which does not require AVX 2.0, has the same symptoms, and Ventura also has the same symptoms.

Can't solve this problem?

I am listing my specs and EFI for your reference.


Specs :

CPU : AMD FX(tm)-9590 Eight-Core Processor
M/B : Crosshair V Formula-Z
GPU : AMD Radeon Vega Frontier Edition

 

[Edhawk]

Do you have an XFX graphics card?

If yes, these are known to have suspect VBios that needs to be flashed with a ‘Reference’ bios to fix issues between the OS and GPU.

Was the GPU bought new or second hand?

If second hand then it may not have a normal bios, it may have a Mining bios, that again needs to be flashed with a reference bios.

 

[Hyuna_4443]

Do you have an XFX graphics card?

If yes, these are known to have suspect VBios that needs to be flashed with a ‘Reference’ bios to fix issues between the OS and GPU.

Was the GPU bought new or second hand?

If second hand then it may not have a normal bios, it may have a Mining bios, that again needs to be flashed with a reference bios.

I understand that the Vega FE graphics card only produces reference designs.

The card I have now has no markings from any other company other than AMD, and is probably produced by AMD.

I bought it used last time and flashed several VBIOS downloads from TechPowerUP, but it didn't solve the problem.

In addition, I have also used Sapphire R9 390 (GPU-Spoof) and Gigabyte RX580, but since the same symptoms appear, it is assumed to be a Hackintosh problem.

 

[Edhawk]

OK, first thing I would recommend is replacing FakeSMC.kext with VirtualSMC.kext. VirtualSMC.kext is an 'Essential' kext for any AMD Vanilla Hack.

I would also remove the numerous sensor kexts you have in your /EFI/OC/Kexts folder and config.plist. You do not need all of these sensor kexts, and most work with VirtualSMC.kext as well as FakeSMC.kext.

I would change your Kexts folder as follows:

current kexts folder contents

revised kexts folder contents

Removing these unessential Sensor kexts and using VirtualSMC.kext v1.3.2 might help get you past this issue.

The SSDT-EC-USBX-Desktop.aml table you are using is a generic ACPI table. You would be better served creating custom SSDT-EC.aml and SSDT-USBX.aml using Corpnewt's SSDTTime script (either in Windows or Linux) with your system DSDT.aml table.

GitHub - corpnewt/SSDTTime: SSDT/DSDT hotpatch attempts.

SSDT/DSDT hotpatch attempts. Contribute to corpnewt/SSDTTime development by creating an account on GitHub.

github.com

Select the Green coloured button named 'Code' to download the zipped folder.

At the least I would change the SSDT-EC-USBX-Desktop.aml table for the SSDT-EC-USBX-AMD.aml table, so you are only using AMD compatible options.

You have a lot of unnecessary Tools in the /EFI/OC/Tools folder, you will never need or use most of these Tools. I would recommend reducing the number of tools in this folder as follows:

Current Tools folder contents

revised Tools folder contents

Your Drivers folder has a few unusual entries.

1. Your ASUS ROG Crosshair V Formula-Z motherboard has a UEFI BIOS, so you shouldn't be using the LegacyHfsPlus.efi driver. You should be using the HfsPlus.efi driver.
2. I have never seen anyone else have the FirmwareSettingsEntry.efi driver in thier Old FX systems OC setup. I would remove this driver.
3. You are missing an essential driver - ResetNvramEntry.efi. This driver is essential because it needs to be used after each and every change to the OC folder contents and or config.plist.

Your Drivers folder should be setup as follows:

current Drivers folder contents

revised Drivers folder contents

So overall your OpenCore EFI folder would change as follows:

current OC EFI folder contents

revised OC EFI folder contents

With all the corresponding changes made to your config.plist.

I have cleaned up your config.plist, as well as making the changes listed above.

Give it a try and see if this revised EFI folder helps.

I am assuming that you have set your bios to follow the Dortania guide. If in doubt check the following:

Bulldozer(15h) and Jaguar(16h) | OpenCore Install Guide

 

[Hyuna_4443]

OK, first thing I would recommend is replacing FakeSMC.kext with VirtualSMC.kext. VirtualSMC.kext is an 'Essential' kext for any AMD Vanilla Hack.

I would also remove the numerous sensor kexts you have in your /EFI/OC/Kexts folder and config.plist. You do not need all of these sensor kexts, and most work with VirtualSMC.kext as well as FakeSMC.kext.

I would change your Kexts folder as follows:

View attachment 14273 current kexts folder contents

View attachment 14274 revised kexts folder contents

Removing these unessential Sensor kexts and using VirtualSMC.kext v1.3.2 might help get you past this issue.

The SSDT-EC-USBX-Desktop.aml table you are using is a generic ACPI table. You would be better served creating custom SSDT-EC.aml and SSDT-USBX.aml using Corpnewt's SSDTTime script (either in Windows or Linux) with your system DSDT.aml table.

GitHub - corpnewt/SSDTTime: SSDT/DSDT hotpatch attempts.

SSDT/DSDT hotpatch attempts. Contribute to corpnewt/SSDTTime development by creating an account on GitHub.

github.com

Select the Green coloured button named 'Code' to download the zipped folder.

At the least I would change the SSDT-EC-USBX-Desktop.aml table for the SSDT-EC-USBX-AMD.aml table, so you are only using AMD compatible options.

You have a lot of unnecessary Tools in the /EFI/OC/Tools folder, you will never need or use most of these Tools. I would recommend reducing the number of tools in this folder as follows:

View attachment 14275 Current Tools folder contents

View attachment 14276 revised Tools folder contents

Your Drivers folder has a few unusual entries.

1. Your ASUS ROG Crosshair V Formula-Z motherboard has a UEFI BIOS, so you shouldn't be using the LegacyHfsPlus.efi driver. You should be using the HfsPlus.efi driver.
2. I have never seen anyone else have the FirmwareSettingsEntry.efi driver in thier Old FX systems OC setup. I would remove this driver.
3. You are missing an essential driver - ResetNvramEntry.efi. This driver is essential because it needs to be used after each and every change to the OC folder contents and or config.plist.

Your Drivers folder should be setup as follows:

View attachment 14277 current Drivers folder contents

View attachment 14278 revised Drivers folder contents

So overall your OpenCore EFI folder would change as follows:

View attachment 14279 current OC EFI folder contents

View attachment 14280 revised OC EFI folder contents

With all the corresponding changes made to your config.plist.

I have cleaned up your config.plist, as well as making the changes listed above.

Give it a try and see if this revised EFI folder helps.

I am assuming that you have set your bios to follow the Dortania guide. If in doubt check the following:

Bulldozer(15h) and Jaguar(16h) | OpenCore Install Guide

thank you!

I tried applying the efi folder you provided, but the same symptom still appears.

The reason for using Hfspluslegacy instead of HFSPlus is because it go to a black screen when booting the OC.

I understand that this is due to the lack of RDRAND instructions in the FX processor.

 

[Edhawk]

That's not correct, as I used HfsPlus.efi with both my FX systems.

See this success story as an example.

Success - Asus Sabertooth 990FX R2.0 / FX 8350 / Nvidia GTX 690 / OC 0.7.6 - Big Sur 11.6.2 & Monterey 12.1

I have been playing around with my old AMD FX 8350 system (again) and decided to see if I could get it running macOS Big Sur. I used OpenCore 0.7.6 and followed the Dortania AMD Bulldozer guide when creating the EFI folder. I created my macOS Big Sur USB installer using the following...

forum.amd-osx.com

I would recommend checking your Bios options are correctly configured to run macOS.

 

[Hyuna_4443]

That's not correct, as I used HfsPlus.efi with both my FX systems.

See this success story as an example.

Success - Asus Sabertooth 990FX R2.0 / FX 8350 / Nvidia GTX 690 / OC 0.7.6 - Big Sur 11.6.2 & Monterey 12.1

I have been playing around with my old AMD FX 8350 system (again) and decided to see if I could get it running macOS Big Sur. I used OpenCore 0.7.6 and followed the Dortania AMD Bulldozer guide when creating the EFI folder. I created my macOS Big Sur USB installer using the following...

forum.amd-osx.com

I would recommend checking your Bios options are correctly configured to run macOS.

After reading the linked post, I looked into the EFI folder and checked the BIOS.

Instead of HFSPlus, there is OpenHFSPlus, so I applied it and it booted successfully, but the black screen problem still persists.

One thing that was different about the BIOS collation process was that there was no option to turn Serial Port off or on.

I guess it's probably the difference between Sabertooth and Crosshair.

 

[Edhawk]

OK just to be clear. OpenHfsPlus.efi was Acidanthera's attempt to fix the fact that they can't include HfsPlus.efi in their OpenCore release. As it has a separate licence that prohibits the inclusion of the driver in their OC release folder.

HfsPlus.efi is the better driver and should be used in preference to OpenHfsPlus.efi.

Your motherboard doesn't appear to have a Serial/COM Port, according to the User Manual. So don't worry about not finding it in the bios.

Motherboard internal connectors/layout

Motherboard connectors list.

How are you connecting the Hack to your display/TV, DisplayPort or HDMI?
Are you using an adapter cable or other graphics adapter, such as HDMI to VGA, or something similar?

The best option is to use DisplayPort to DisplayPort cable from Hack to display.
Next best would be HDMI to HDMI.

Use of a graphics adapter is a field strewn with issues.

 

[Hyuna_4443]

OK just to be clear. OpenHfsPlus.efi was Acidanthera's attempt to fix the fact that they can't include HfsPlus.efi in their OpenCore release. As it has a separate licence that prohibits the inclusion of the driver in their OC release folder.

HfsPlus.efi is the better driver and should be used in preference to OpenHfsPlus.efi.

Your motherboard doesn't appear to have a Serial/COM Port, according to the User Manual. So don't worry about not finding it in the bios.

View attachment 14297 Motherboard internal connectors/layout

View attachment 14298 Motherboard connectors list.

How are you connecting the Hack to your display/TV, DisplayPort or HDMI?
Are you using an adapter cable or other graphics adapter, such as HDMI to VGA, or something similar?

The best option is to use DisplayPort to DisplayPort cable from Hack to display.
Next best would be HDMI to HDMI.

Use of a graphics adapter is a field strewn with issues.

OK. I made several attempts to use HFSPlus.efi, but ultimately failed. It would be great if I could use HFSPlus, but for now I think I have no choice but to use OpenHFSPlus or HFSPlusLegacy.

I am using a Hackintosh connected to a 4K monitor using a DP cable.

I am not using a separate adapter, and the same goes for HDMI.

The Vega FE's three DP ports and one HDMI port all have the same symptom, and my i7-2600K Hackintosh works properly in the same environment, so it doesn't seem to be a hardware or environment problem.

In addition, while looking through various posts on this forum, I saw many posts complaining of the same symptoms in the FX processor.

It may be a graphics-related issue, but we also cannot rule out the possibility of an FX compatibility issue with the AMD Kernel Patch or a conflict with macOS' power management.

I'm doing a little more research on this as well.

 

[Edhawk]

The problems that started surfacing in Monterey and later in Ventura was part of the reason I retired my FX system. These systems while fairly robust and still capable of running Windows or Linux really well, are simply too old for the newer releases of macOS, in my opinion.

 

[Hyuna_4443]

The problems that started surfacing in Monterey and later in Ventura was part of the reason I retired my FX system. These systems while fairly robust and still capable of running Windows or Linux really well, are simply too old for the newer releases of macOS, in my opinion.

It is unfortunate that the main cause of the error seems to have been the fact that AMD designed the Bulldozer differently in order to differentiate it from Intel in several ways.

I like the FX system and want to continue using it, so I've been trying various things for nearly a year, but it's really difficult.

Sonoma 14.2 beta3 booted by legacy OpenCore 0.9.5 in FX-6300 hackintosh

My FX-6300 hackintosh can boot Sonoma 14.2 beta3 & Ventura 13.6.3 by legacy OpenCore 0.9.5 with ProvideCurrentCpuInfo quirk enabled without red screen panic or blank screen issue now after its GPU RX-560 replaced by R9 270 and config.plist modified. My config-OC-M5A.plist is attached for...

forum.amd-osx.com

I want to give up, but seeing success stories like this post makes me want to keep trying.

Anyway, thank you very much for the reply. It was very helpful.

If you have any good thoughts, please share them.

 

[Edhawk]

You may be better served installing Catalina or Big Sur, as these older macOS releases are less problematic with the FX series. You can then work your way forward to Monterey or newer if you choose, having the Catalina disk to fall back on should you bork your upgrade to a newer OS.

If you install Catalina make sure you set the UEFI > APFS > MinDate and MinVersion entries to allow the older APFS to be recognised and used.

Bulldozer(15h) and Jaguar(16h) | OpenCore Install Guide

Do not use ‘-1’. Use the correct date and version entries for Catalina in your config.plist.