Contribute
Register

AMD Radeon Graphics — macOS Sonoma

Joined
Nov 6, 2012
Messages
33
Motherboard
Asrock Deskmini 310
CPU
i5 9500
Graphics
630HD
Mac
  1. iMac
  2. Mac mini
  3. Mac Pro
Mobile Phone
  1. iOS
I have an Asrock B550 Phantom Gaming ITX board with a Ryzen 5700G. When using the attached EFI, video memory only indicates 512MB even though I set it to 8GB in the BIOS. Can anyone out there help me figure this out. The machine is very sluggish with only 512MB.
 

Attachments

  • EFI.zip
    17.6 MB · Views: 132
I have an Asrock B550 Phantom Gaming ITX board with a Ryzen 5700G. When using the attached EFI, video memory only indicates 512MB even though I set it to 8GB in the BIOS. Can anyone out there help me figure this out. The machine is very sluggish with only 512MB.
You have both NootedRed and WhateverGreen in your EFi kext folder!. From the Noot site, it says you only use one. You have two USBX.amls, one from OpenCore and did you generate the other one?. You can replaccan e SSDT-EC-USBX-DESKTOP.aml with the one you generated, SSDT-USBX.aml.

Screenshot 2023-10-12 at 8.11.11 AM.png


Screenshot 2023-10-12 at 8.48.43 AM.png


 
Last edited:
You have both NootedRed and WhateverGreen in your EFi kext folder!. From the Noot site, it says you only use one. You have two USBX.amls, one from OpenCore and did you generate the other one?. You can replaccan e SSDT-EC-USBX-DESKTOP.aml with the one you generated, SSDT-USBX.aml.

View attachment 572847

View attachment 572850

Whatevergreen was already disabled in the config.plist to not conflict with nootedred. I disabled SSDT-EC-USBX-DESKTOP. Did not solve problem. I upgraded the BIOS to the latest version and now I'm getting the full 8GB of VRAM I selected in the BIOS. Machine is running Sonoma flawlessly now.
 
Whatevergreen was already disabled in the config.plist to not conflict with nootedred. I disabled SSDT-EC-USBX-DESKTOP. Did not solve problem. I upgraded the BIOS to the latest version and now I'm getting the full 8GB of VRAM I selected in the BIOS. Machine is running Sonoma flawlessly now.
New problem. When I shutdown, I see the verbose mode message go across the screen, the screen goes black, the fans keep running and the motherboard LEDs stay on. I have to hold the power button to get it to completely shutdown. Same thing happens if I try to restart. I've encountered this before, but it's been several years and I can't remember how I solved it.
 
Last edited:
@ejh4286 you have a number of issues in your OC setup, EFI from post #73. Below are two screenshots showing AMD OC EFI folder trees. The first is from your EFI in post #73, the second is how I would configure the EFI.

Screenshot 2023-10-14 at 15.43.48.png Screenshot 2023-10-14 at 15.52.43.png

The most likely cause(s) for the system not shutting down are related to the USB configuration.

You have a mis-configured USBPorts.kext, a USBMap.kext (with USBTooBox.kext?) and the XhciPortLimit quirk enabled. You only need one of these three USB options, never all three.

The USBMaps.kext looks as though it is more correctly configured than the USBPorts.kext. Although it has the wrong SMBIOS Name for the system you are using, so it won't work. You need to edit the USBMap.kext/Contents/Info.plist to remove the MacPro7,1 name and replace it with iMac20,1 name, in two locations for each USB controller. This is a common issue when changing SMBIOS for your Hack and very easily forgotten.

You need to delete the USBPorts.kext and disable the XhciPortLimit quirk. The USBToolBox.kext is an orphan, it won't work with USBPorts.kext or USBMap.kext it requires UTBMap.kext to be of any use, so it should also be deleted.

You have a number of kexts in your setup that are not used, i.e. are set as false in the config.plist. I would recommend deleting the kexts and config entries to clean up your setup, so it is easier to identify any issues.

You are missing the IntelBTPatcher.kext, which is required in recent versions of macOS for Intel BT modules to work correctly. I would recommend adding this kext and making sure the IntelBluetoothFirmware.kext you are using is from the same release.

You have a number of DeviceProperties in your config.plist, these are known to cause issues when using NootedRed.kext, so I would recommend deleting the four (4) device properties and using alternative methods for adding the Audio layout ID, Ethernet enabling, WiFi identification plus whatever the other device is you are setting as built-in.

You don't have the Kernel > Emulate > DummyPowerManagement entry enabled in your config.plist. This is an essential option for any AMD system and should be set to True, not False.

You have three (3) entries under the Misc > Entries section in your config, but none are enabled. I would recommend deleting these three entries, as they do nothing useful for your setup.

The SSDT-EC-USBX-Desktop.aml table you are using is a generic ACPI table which is used as a catch-all option when first installing macOS. It contains a lot of Intel settings, which your system would never use. There is an alternative SSDT-EC-USBX-AMD.aml table that is specific to AMD systems, which I think is a better option when first installing macOS.

As a longer term option you would be advised to download Corpnewt's SSDTTime-Master folder and use his python script to generate a number of custom SSDT's for your system, using your system DSDT.aml table as the base for the custom SSDT's. The custom SSDT's will be a much better match to your system and will be quicker when loading/being read. See the guide below for how to use the script.


I have attached a revised EFI that incorporates all the changes I recommended, bar the Corpnewt SSDT option.

Testing/Booting Revised EFI:

If you want to try this revised EFI, simply add your Serial Number, MLB and SystmUUID data to the revised config.plist. Don't make any other changes to the setup.

Copy the revised EFI folder to the EFI partition on a spare USB pen drive, which has been formatted HFS+. Then boot from the pen drive to test the EFI.

Don't replace your current EFI until you are sure the revised EFI works and boots without any issues.

You will need to use the ResetNvramEntry.efi option of the first boot with this revised OC setup.
  • 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 boot in to macOS using the revised EFI.
Hope this is helpful.
 

Attachments

  • EFI.zip
    17.1 MB · Views: 88
Very helpful as always @Edhawk!, btw where do I find SSDT-EC-USBX-AMD.aml?, I've never heard of it before.
 
Attached below.
 

Attachments

  • SSDT-EC-USBX-AMD.aml.zip
    1.1 KB · Views: 42
@craighazan I am really surprised, you've had your Hack(s) long enough to have used Corpnewt's SSDTTime script and should be using custom SSDTs in all your Hacks.

The SSDT-EC-USBX-AMD.aml table is again something that should only be used when first installing macOS. It can be used long term but that's not how I would do things.

As far as I am concerned, EVERYONE who creates a Hack should be creating the custom SSDT's for their system. As every system needs more than just the two 'starter' SSDT's. Using the system DSDT.aml as a base for the custom SSDTs means you only get the elements your system needs to improve how it runs macOS. No fluff and nonsense that other systems require.
 
@craighazan I am really surprised, you've had your Hack(s) long enough to have used Corpnewt's SSDTTime script and should be using custom SSDTs in all your Hacks.

The SSDT-EC-USBX-AMD.aml table is again something that should only be used when first installing macOS. It can be used long term but that's not how I would do things.

As far as I am concerned, EVERYONE who creates a Hack should be creating the custom SSDT's for their system. As every system needs more than just the two 'starter' SSDT's. Using the system DSDT.aml as a base for the custom SSDTs means you only get the elements your system needs to improve how it runs macOS. No fluff and nonsense that other systems require.
I should have been clearer, I generated my own in SSDTs by dumping them from Hackintool then using SSDTTime to create the amls.
Screenshot 2023-10-14 at 11.41.44 AM.png
 
@craighazan my apologies, I misunderstood the reason for your post. I thought you wanted to use the SSDT-EC-USBX-AMD.aml table for your systems.
 
Back
Top