[GUIDE] macOS 13 Ventura with OpenCore 0.8.6 on Z390 Aorus Elite (AMD RX 6600 or Intel UHD 630)

[miliuco]

macOS Monterey / Ventura with OpenCore 0.8.6 on Z390 Aorus Elite motherboard (AMD RX 6600 or Intel UHD 630)

• Guide using OpenCore 0.8.6 for Monterey and Ventura
• Gigabyte Z390 Aorus Elite motherboard
• Settings for AMD dGPU as main card or iGPU as single card
• EFI folder available for different SMBIOS.

Hardware

• Motherboard: Gigabyte Z390 Aorus Elite
• CPU:Intel i7 9700
• iGPU:Intel UHD Graphics 630
• dGPU:AMD Radeon RX 6600 8GB
• Sound:Realtek ALC1220
• Ethernet:Intel I219V7
• Wifi + BT:Fenvi FV-T919 BCM94360CD.

What works well?

• Radeon graphics card (VDA decoder fully supported)
• Shutdown, restart and sleep
• Audio (ALC1220 and HDMI)
• USB ports (USB ports map for this motherboard)
• Airdrop, iMessage...

BIOS settings (version F10h)

• CFG Lock: Disabled
• CSM: Disabled
• VT-d: Disabled
• Fast Boot: Disabled
• OS Type: Windows 8/10 WHQL
• Platform Power Management: Disabled
• XHCI Hand-Off: Enabled
• Network Stack: Disabled
• Wake on LAN: Disabled
• Secure Boot: Disabled
• DVMT Pre-Allocated: 256M or higher
• Integrated Graphics: Disabled / Enabled (according to SMBIOS)

OpenCore 0.8.6

For the installation to be successful, 3 parameters related to security must be set:

• SecureBootModel=j160 or SecureBootModel=Default in config.plist (Apple secure boot j160 corresponds to MacPro7,1 and Default sets the same model as in SMBIOS)
• SIP enabled (csr-active-config=00000000 in config.plist)
• Gatekeeper enabled (sudo spctl --master-enable in Terminal).

These security options can be changed after installation as they do not are required for Monterey / Ventura to run.

SMBIOS

SMBIOS model that works best on my systems is iMac19,1. This Mac model requires:

• AMD dGPU as main card
• Intel 630 iGPU enabled in BIOS
• iGPU code for headless mode in config.plist.

MacPro7,1 SMBIOS can be set if desired. It works also very well. This Mac model requires:

• AMD dGPU as main card
• Intel 630 iGPU disabled in BIOS (as this Mac models lack integrated GPU, they have only AMD GPU)
• RestrictEvents.kext to avoid RAM misconfiguration warnings
• CPUFriend.kext: not mandatory but in my opinion it improves CPU Power Management.

CPUFriend.kext

Although the CPU is well detected with MacPro's SMBIOS, my guess is that it does not run at low frequency as often as it does with iMac19.1. For this reason, I have generated a CPUFriendDataProvider.kext extension from the CPUFriendFriend command to accompany CPUFriend.kext. With these 2 kexts (CPUFriendDataProvider.kext + CPUFriend.kext) the CPU shows correct power management and frequency drops to 800 MHz at system idle.

SSDTs, drivers and tools

SSDTs

• SSDT-AWAC-DISABLE: to fix errors with system clock on Z390, B460, Z490 motherboards
• SSDT-EC-USBX: fake Embedded Controller on Skylake and later, also fix USB power
• SSDT-PLUG: power management on Haswell and newer CPUs; to configure the plugin-type=1 parameter on the first processor
• SSDT-PMC: native NVRAM support on systems that lack it, for example Z390 chipsets
• SSDT-USBW: to wake from sleep with a single mouse or keyboard touch (this SSDT works with USBWakeFixup.kext) >> very likely not needed if USB device in DeviceProperties has acpi-wake-type=01.

Drivers

• HfsPlus.efi: to recognize HFS+ devices
• OpenRuntime.efi: essential driver to run macOS
• OpenCanopy.efi: graphical picker with themes
• CrScreenshotDxe.efi: Screenshots in OpenCore.

Tools

• OpenShell.efi: UEFI shell to perform command line tasks from OpenCore

config.plist

Some settings:

• DeviceProperties >> Add >> PciRoot(0x0)/Pci(0x14,0x0): acpi-wake-type as data=01, to improve wake from sleep
• Misc >> Boot >> PickerAttributes=144 to enable Flavours system
• NVRAM> 7C436110-AB2A-4BBB-A880-FE41995C9F82> boot-args: alcid=7 agdpmod=pikera (agdpmod=pikera not needed with RX 580, only with RX 6600 and other Navi cards)
• Misc >> Security >> AllowToggleSip=True to show in the picker the ToggleSIP tool that allows to easily switch between SIP enabled and SIP disabled for the current boot.

Intel UHD 630 headless mode

• iGPU and dGPU must be enabled in BIOS with dGPU as primary
• There should be no cable between iGPU HDMI port and any type of display
• Lilu and WhatEverGreen properly installed
• SMBIOS iMac19.1.

You have to add in DeviceProperties >> Add:

 <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
	<key>AAPL,ig-platform-id</key>
	<data>AwCRPg==</data>
	<key>device-id</key>
	<data>mz4AAA==</data>
	<key>enable-metal</key>
	<data>AQAAAA==</data>
	<key>igfxfw</key>
	<data>AgAAAA==</data>
	<key>force-online</key>
	<data>AQAAAA==</data>
	<key>rps-control</key>
	<data>AQAAAA==</data>
</dict>

This code has data values in Base64, in plist editors they can be seen as hexadecimal, e.g. AwCRPg== in Base64 (AAPL,ig-platform-id) = 0300913E in hexadecimal.

To check if the VDA Decoder function is activated you can get Hackintool app (Fully Supported or Failed in the first System tab).

 

Notes:

• AAPL,ig-platform-id=07009B3E is mandatory
• device-id=9B3E000 to be displayed as Intel UHD Graphics 630 instead of Kabylake Unknown
• enable-metal=01 to enable Metal 3 in Ventura
• force-online=01 to force online status on all displays (mandatory)
• igfxfw=02 to force loading of Apple GuC firmware (improves IGPU performance)
• rps-control=01 to enable RPS control patch (improves IGPU performance).

Spoiler

 

Intel UHD 630 as single GPU

If you don't have an external graphics card and need to use the iGPU as single card, you have to use iMac19,1 SMBIOS with code in config.plist to patch the framebuffer and other properties so that the iGPU is well detected:

<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
	<key>AAPL,ig-platform-id</key>
	<data>BwCbPg==</data>
	<key>device-id</key>
	<data>mz4AAA==</data>
	<key>device_type</key>
	<string>VGA compatible controller</string>
	<key>enable-hdmi20</key>
	<data>AQAAAA==</data>
	<key>enable-metal</key>
	<data>AQAAAA==</data>
	<key>framebuffer-con0-busid</key>
	<data>AAAAAA==</data>
	<key>framebuffer-con0-enable</key>
	<data>AQAAAA==</data>
	<key>framebuffer-con0-pipe</key>
	<data>EgAAAA==</data>
	<key>framebuffer-con1-busid</key>
	<data>AAAAAA==</data>
	<key>framebuffer-con1-enable</key>
	<data>AQAAAA==</data>
	<key>framebuffer-con1-pipe</key>
	<data>EgAAAA==</data>
	<key>framebuffer-con2-busid</key>
	<data>BAAAAA==</data>
	<key>framebuffer-con2-enable</key>
	<data>AQAAAA==</data>
	<key>framebuffer-con2-pipe</key>
	<data>EgAAAA==</data>
	<key>framebuffer-con2-type</key>
	<data>AAgAAA==</data>
	<key>framebuffer-patch-enable</key>
	<data>AQAAAA==</data>
	<key>framebuffer-stolenmem</key>
	<data>AAAwAQ==</data>
	<key>hda-gfx</key>
	<string>onboard-1</string>
	<key>igfxfw</key>
	<data>AgAAAA==</data>
	<key>force-online</key>
	<data>AQAAAA==</data>
	<key>rps-control</key>
	<data>AQAAAA==</data>
</dict>

Spoiler

 

AMD RX 6600 on Ventura with MacPro or iMacPro SMBIOS

 

AMD Navi cards run fine on Ventura when using iMac SMBIOS with agdpmod=pikera in boot args as the only needed setting. But when using MacPro or iMacPro SMBIOS a lot of users have reported black screen. The simplest way to fix this is to add in DeviceProperties of config.plist some properties that set Henbury framebuffer for each of the 4 ports of this GPU.

By default, Radeon framebuffer (ATY,Radeon) is loaded. But, in AMDRadeonX6000Framebuffer.kext >> Contents >> Info.plist we can see that AMDRadeonNavi23Controller has ATY,Henbury and 6600 series are Navi 23. This is why this framebuffer is selected.

The patch is added in this way:

<key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>@0,name</key>
                <string>ATY,Henbury</string>
                <key>@1,name</key>
                <string>ATY,Henbury</string>
                <key>@2,name</key>
                <string>ATY,Henbury</string>
                <key>@3,name</key>
                <string>ATY,Henbury</string>
            </dict>
        </dict>
        <key>Delete</key>
        <dict/>
    </dict>

 

Notes:

• PCI path to the GPU may be the same on your system but it is convenient to check it with Hackintool (app) or gfxutil (Terminal utility).
• This is not needed for Monterey.
• This is not needed for RX 580 or Polaris card.

If needed for other Navi cards, the framebuffers to be loaded are different for each family:

• 5500 ATY,Python
• 5700 ATY,Adder
• 6600 ATY,Henbury
• 6800 ATY,Belknap
• 6900 ATY,Carswell

Installing Monterey or Ventura

The process is almost the same for installation and for update:

• You need a working EFI folder
• Download macOS from Software Update or create USB installer; I don't comment about creating USB installer because there are a lot of sites with this info
• Run Install macOS Monterey / Ventura app or the setup program from the booted USB
• The process has 2 reboots booting from Install macOS disk and a third reboot booting from the target disk.

SMBIOS and config.plist files

There are eight configuration files, the ones starting with config-12 are for and Monterey and the ones starting with config-13 are for Ventura. Variants are included for 4 possible SMBIOS:

• iMac19,1 with AMD dGPU + iGPU headless mode
• iMac19,1 with iGPU as main card without dGPU
• MacPro7,1 with dGPU + iGPU disabled
• iMacPro1,1 with dGPU + iGPU disabled.

List of config.plist files:

• config-12-imac-amd.plist: iMac19,1 + dGPU AMD + iGPU enabled in BIOS
• config-12-imac-intel.plist: iMac19,1 + iGPU enabled in BIOS as main card
• config-12-imacpro.plist: iMacPro1,1 + dGPU AMD + iGPU disabled in BIOS
• config-12-macpro.plist: MacPro7,1 + dGPU AMD + iGPU disabled in BIOS
• config-13-imac-amd.plist: iMac19,1 + dGPU AMD + iGPU enabled in BIOS
• config-13-imac-intel.plist: iMac19,1 + iGPU enabled in BIOS as main card
• config-13-imacpro.plist: iMacPro1,1 + dGPU AMD + iGPU disabled in BIOS
• config-13-macpro.plist: MacPro7,1 + dGPU AMD + iGPU disabled in BIOS.

Notes

• rename selected config file to config.plist
• current GPU is AMD RX 6600 XT; for RX 580 and other Polaris cards remove agdpmod=pikera from boot-args and don't use the framebuffer patch
• add serial numbers for the SMBIOS model.

Important!

• Don't forget to rename the selected config file to config.plist.
• Do ResetNVRAM the first time you boot a new EFI.
• Press spacebar to show auxiliary entries in the picker.

Credits

Acidanthera: OpenCore and kexts
Dortania: OpenCore guides.

 

 

EFI-0.8.6.zip

Edited October 27, 2022 by miliuco

[eSaF]

Great write-up Bro, very good informative info for newbies and seasoned members alike. 

[CloverLeaf]

Amazing! Well done! 🙌

[BALDY_MAN]

Stunning work 

bien hecho

[miliuco]

Alternative method to Henbury patch to avoid black screen with MacPro or iMacPro SMBIOS on Ventura (thanks @dreamwhite)

 

Using SSDT-BRG0.aml fixes black screen on Ventura with SMBIOS models lacking iGPU. This SSDT allows to define a missing pci-bridge device. With it, the Henbury patch is no longer necessary.

 

Do not forget that the Henbury patch clearly drops down the GeekBench 5 scores, however with SSDT-BRG0 scores are as expected, in line with those got by many users with this graphics card.

 

SSDT-BRG0:

/*
 * This table provides an example of creating a missing ACPI device
 * to ensure early DeviceProperty application. In this example
 * a GPU device is created for a platform having an extra PCI
 * bridge in the path - PCI0.PEG0.PEGP.BRG0.GFX0:
 * PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
 * Such tables are particularly relevant for macOS 11.0 and newer.
 */
 
DefinitionBlock ("", "SSDT", 2, "ACDT", "BRG0", 0x00000000)
{
    External (_SB_.PCI0.PEG0.PEGP, DeviceObj)

    Scope (\_SB.PCI0.PEG0.PEGP)
    {
        Device (BRG0)
        {
            Name (_ADR, Zero)  // _ADR: Address
            Device (GFX0)
            {
                Name (_ADR, Zero)  // _ADR: Address
            }

            Device (HDAU)
            {
                Name (_ADR, One)  // _ADR: Address
            }
        }
    }
}

Be sure of the PCI path to your dGPU, mine is /PCI0@0/PEG0@1/PEGP@0/GFX0@0 so the SSDT has these lines:

External (_SB_.PCI0.PEG0.PEGP, DeviceObj)
Scope (\_SB.PCI0.PEG0.PEGP)

Modify the SSDT (if needed) to be set within your system. How to chek the PCI path?

• gfxutil utility in Terminal, look for the line containing GFX0 at the end
• Hackintool >> PCIe tab >> pointer over Navi 23 line >> copy IOReg patch.

Edited October 28, 2022 by miliuco

[Baio77]

On 10/28/2022 at 9:45 PM, miliuco said:

Alternative method to Henbury patch to avoid black screen with MacPro or iMacPro SMBIOS on Ventura (thanks @dreamwhite)

 

Using SSDT-BRG0.aml fixes black screen on Ventura with SMBIOS models lacking iGPU. This SSDT allows to define a missing pci-bridge device. With it, the Henbury patch is no longer necessary.

 

Do not forget that the Henbury patch clearly drops down the GeekBench 5 scores, however with SSDT-BRG0 scores are as expected, in line with those got by many users with this graphics card.

 

SSDT-BRG0:

/*
 * This table provides an example of creating a missing ACPI device
 * to ensure early DeviceProperty application. In this example
 * a GPU device is created for a platform having an extra PCI
 * bridge in the path - PCI0.PEG0.PEGP.BRG0.GFX0:
 * PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
 * Such tables are particularly relevant for macOS 11.0 and newer.
 */
 
DefinitionBlock ("", "SSDT", 2, "ACDT", "BRG0", 0x00000000)
{
    External (_SB_.PCI0.PEG0.PEGP, DeviceObj)

    Scope (\_SB.PCI0.PEG0.PEGP)
    {
        Device (BRG0)
        {
            Name (_ADR, Zero)  // _ADR: Address
            Device (GFX0)
            {
                Name (_ADR, Zero)  // _ADR: Address
            }

            Device (HDAU)
            {
                Name (_ADR, One)  // _ADR: Address
            }
        }
    }
}

Be sure of the PCI path to your dGPU, mine is /PCI0@0/PEG0@1/PEGP@0/GFX0@0 so the SSDT has these lines:

External (_SB_.PCI0.PEG0.PEGP, DeviceObj)
Scope (\_SB.PCI0.PEG0.PEGP)

Modify the SSDT (if needed) to be set within your system. How to chek the PCI path?

• gfxutil utility in Terminal, look for the line containing GFX0 at the end
• Hackintool >> PCIe tab >> pointer over Navi 23 line >> copy IOReg patch.

 

 

To clarify: SSDT-BRG0 only adds the name to a device where it would be missing. Apple for the Navi-BigNavi GPUs and also the Vegas uses this method of renaming the PCI Bridge.

 

Source Darwin Dump Apple:

https://applelife.ru/threads/dampy-originalnyx-makov.2943712/

Ioreg very IMacPro 1.1 

 

The most suitable solution is the use of SSDT-Navi_Vega.
SSDT-Navi_Vega.aml

This SSDT uses only the proper renaming and is devoid of any other patches.

I would be grateful if anyone could provide Ioreg of a real Mac with BigNavi GPU. This would help me understand what is missing to load the Henbury FB natively. Although I believe that everything is linked to the Bios of the Big Navi Apple GPUs themselves.

I believe the Hembury FB is loaded when ALL Apple reference values are loaded. I believe this happens when the OS, through the BIOS GPU information, senses both the Apple GPU, while when it reads a common PC Bios GPU it loads the generic FB. This obviously affects performance. Reading Ioreg Vero Mac with BigNavi might allow us to make the OS believe we have an Apple BigNavi, but until we test it's just theories.

Edited October 31, 2022 by Baio77

[D3v1L]

good work! ...just a little...

 

• SSDT_PLUG not needed anymore (from Monterey 12.3...);
• whatevergreen kext and agdpmod=pikera related bootarg, not needed in MacPro7,1 smbios (MP71 have pegp not gfx0);
• SSDT-AWAC needed only if you have ACPI000E in your DSDT (as example, my AorusPro z390 don't have it, so this ssdt is not required...but , otherwise , it require HPET ssdt+irq patch....so, verify in your DSDT.dsl);
• usb wake device patch: not needed if you set ram clock speed as expected from MacOS, otherwise it's ok to use it;
• ssdt EC/USBX ...you need to verify if you already have _STA method (mine have it) and, in case, you need to create a new "fake" EC (use laptop ec/usbx instead of desktop version)... 🙂 

 

...btw, why not to entering in the darkness world of......papparapaaaaaaaaa MMIOWHITELIST? xD LoL btw, i'll repeat, GREAT TOPIC AND WORK @miliuco!

Edited November 1, 2022 by D3v1L

[miliuco]

@D3v1L

 

Thanks for the reminders.

 

SSDT-PLUG: it's said that it's not needed in 12.3 and newer because Apple dropped plugin-type=1 check enabling x86PlatformPlugin by default but, as khronokernel says, "There is no harm keeping the variable in your ACPI tables regardless of OS so long as the hardware supports XCPM. You could manually omit it in 12.3 and newer yourself, but this is on the basis that Apple may not re-introduce the plugin-type check".

 

MacPro7,1 SMBIOS can work indeed without WEG and agdpmod=pikera, but I keep them to address a wide audience that does not play with complex tasks, without forgetting that some users alternate MacPro with iMac SMBIOS and WEG is necessary to have the iGPU in headless mode.

 

SSDT-AWAC: you are right, for example I really don't need it since I don't have Device (AWAC) in my DSDT but I want to make this easy for users with 300 series boards so they don't have to search if they need the SSDT or not.

 

USB wake device patch: I use it together with USBWakeFixup.kext and SSDT-USBW.aml to wake PC from sleep with one click of USB mouse or keyboard, otherwise I need 2 clicks, but I don't understand "set ram clock speed as expected from macOS". Can you explain me more about it?

 

As in the beginning, thanks for the help, I'll try to include anything in the main post.

Edited November 1, 2022 by miliuco

[D3v1L]

Absolutely right dude!

Please don't take my word as bible lol...

Btw, for wake issue, in many cases works...

 

Disable temporarly acpi and kext you use for wake, 

 

Reboot in BIOS ,

 

Set XMP on,

Set manually RAM clock to 2666

Leave other RAM setting, on "auto"

 

After this, start MacOS 

Try to put it in stop, than wake with KB or mouse...

[D3v1L]

LoL another TIPS, gatekeeper spctl now is "global" and no more "master" ...

 

sudo spctl --global-enable

 (or maybe, disable) 🙂👍🏻

[eSaF]

Is anyone seeing this annoying pop-up when you reach the Desktop? This is happening on my machine since Beta 13.1 btw the software mentioned in the message is for my Master Keys Mouse and Keyboard, if I disable it as suggested, I lose quite a bit of functionality from both Mouse and Keyboard.

Spoiler

 

Edited November 1, 2022 by eSaF

[D3v1L]

6 minutes ago, eSaF said:

Is anyone seeing this annoying pop-up when you reach the Desktop? This is happening on my machine since Beta 13.1 btw the software mentioned in the message is for my Master Keys Mouse and Keyboard, if I disable it as suggested, I lose quite a bit of functionality from both Mouse and Keyboard.

  Hide contents

 

Yep...much of it... From 13,1 Ventura, Tuxera NTFS, Opera updater, Logitech, Wacom...every boot this badge (Say me something add background item) appears...

[aniuks27]

21 minutes ago, eSaF said:

Is anyone seeing this annoying pop-up when you reach the Desktop? This is happening on my machine since Beta 13.1 btw the software mentioned in the message is for my Master Keys Mouse and Keyboard, if I disable it as suggested, I lose quite a bit of functionality from both Mouse and Keyboard.

  Hide contents

 

I get that everytime I reboot the system. Not exactly this but notifications about something added to the login/background. Running Ventura 13.1 Beta

 

[miliuco]

5 hours ago, D3v1L said:

sudo spctl --global-enable

 (or maybe, disable) 🙂👍🏻

 

I didn't know, noted, thanks.

[miliuco]

Alternative method to Henbury patch to avoid black screen with MacPro or iMacPro SMBIOS on Ventura (2)

 

There are some more advanced SSDT configurations such as SSDT-VEGA.aml which, in addition to creating devices, does so by mimicking the way real Macs are configured (EGP0 and EGP1 devices instead of BRG0).

 

SSDT-VEGA has the same benefits as SSDT-BRG0: Henbury patch not needed and good GeekBench 5 scores.

 

It also requires checking the PCI path to your graphics card. In the example code I keep the same path as in the previous SSDT-BRG0.

 

DefinitionBlock ("", "SSDT", 2, "HACK", "VEGA", 0x00000000)
{
    External (_SB_.PCI0, DeviceObj)
    External (_SB_.PCI0.PEG0, DeviceObj)
    External (_SB_.PCI0.PEG0.PEGP, DeviceObj)

    Scope (\_SB)
    {
        Scope (PCI0)
        {
            Scope (PEG0)
            {
                Scope (PEGP)
                {
                    Method (_STA, 0, NotSerialized)  // _STA: Status
                    {
                        If (_OSI ("Darwin"))
                        {
                            Return (Zero)
                        }
                        Else
                        {
                            Return (0x0F)
                        }
                    }
                }

                Device (EGP0)
                {
                    Name (_ADR, Zero)  // _ADR: Address
                    Method (_STA, 0, NotSerialized)  // _STA: Status
                    {
                        If (_OSI ("Darwin"))
                        {
                            Return (0x0F)
                        }
                        Else
                        {
                            Return (Zero)
                        }
                    }

                    Device (EGP1)
                    {
                        Name (_ADR, Zero)  // _ADR: Address
                        Device (GFX0)
                        {
                            Name (_ADR, Zero)  // _ADR: Address
                        }

                        Device (HDAU)
                        {
                            Name (_ADR, One)  // _ADR: Address
                        }
                    }
                }
            }
        }
    }
} 

 

Edited November 3, 2022 by miliuco

[aniuks27]

On 10/31/2022 at 11:54 AM, Baio77 said:

 

 

To clarify: SSDT-BRG0 only adds the name to a device where it would be missing. Apple for the Navi-BigNavi GPUs and also the Vegas uses this method of renaming the PCI Bridge.

 

Source Darwin Dump Apple:

https://applelife.ru/threads/dampy-originalnyx-makov.2943712/

Ioreg very IMacPro 1.1 

 

The most suitable solution is the use of SSDT-Navi_Vega.
SSDT-Navi_Vega.aml

This SSDT uses only the proper renaming and is devoid of any other patches.

I would be grateful if anyone could provide Ioreg of a real Mac with BigNavi GPU. This would help me understand what is missing to load the Henbury FB natively. Although I believe that everything is linked to the Bios of the Big Navi Apple GPUs themselves.

I believe the Hembury FB is loaded when ALL Apple reference values are loaded. I believe this happens when the OS, through the BIOS GPU information, senses both the Apple GPU, while when it reads a common PC Bios GPU it loads the generic FB. This obviously affects performance. Reading Ioreg Vero Mac with BigNavi might allow us to make the OS believe we have an Apple BigNavi, but until we test it's just theories.

Unfortunately this SSDT prevents me from even booting into the OS. My device path is the same as per example , the only difference is it being recognised as pci-bridge in the path. I must be doing something wrong here...any help is appreciated

Edited November 3, 2022 by aniuks27

[miliuco]

@aniuks27

This screenshot is without SSDT-BRG0, right?

Your PCI path seems to be exactly as mine: PCI0/PEG0/PEGP. You can skip pic-bridge@0, it doesn't matter.

I don't know why you can't boot with this SSDT. Did you try it without any changes?

 

[aniuks27]

Just now, miliuco said:

@aniuks27

This screenshot is without SSDT-BRG0, right?

Your PCI path seems to be exactly as mine: PCI0/PEG0/PEGP. You can skip pic-bridge@0, it doesn't matter.

I don't know why you can't boot with this SSDT. Did you try it without any changes?

 

That's correct. This is without SSDT-BGR0. Just for reference I am on iMac19,1 SMBIOS. And yeah that's what I have done , skipped pci-bridge and just used as it is with that pci path. Will have to give it a go tonight when back from work. 

 

[miliuco]

@aniuks27

 

Same as me, iMac19,1. Don't forget to add the SSDT in ACPI folder and config.plist also.

Please upload here your config.plist (don't if you are using mine).

Really for iMac19,1 you only need agdpmod=ventura in boot args, nothing more, if you can't solve the issue forget about the SSDT.

[aniuks27]

10 minutes ago, miliuco said:

@aniuks27

 

Same as me, iMac19,1. Don't forget to add the SSDT in ACPI folder and config.plist also.

Please upload here your config.plist (don't if you are using mine).

Really for iMac19,1 you only need agdpmod=ventura in boot args, nothing more, if you can't solve the issue forget about the SSDT.

agdpmod=ventura? will share my config.plist later. I am using my EFI just borrowed some settings for IGPU from this post:) Thanks for sharing btw.

 

[miliuco]

4 minutes ago, aniuks27 said:

agdpmod=ventura? will share my config.plist later. I am using my EFI just borrowed some settings for IGPU from this post:)

Ok, share your efi.

[aniuks27]

4 hours ago, miliuco said:

Ok, share your efi.

It did work this time. 👌

[miliuco]

@aniuks27

Ok, enjoy it 🙂

[aniuks27]

Not sure if it's worth creating a new post. I thought I will share it here. 

I have done soft powerplay table for my XFX 6600XT and added device property for it. 

I am not using WEG nor have agdpmod=pikera boot arg in NVRAM. Currently running on SMBIOS iMacPro1,1. The question I have regarding Geekbench benchmarks..

With Weg and boot arg I keep getting around 76-80k , with framebuffer patch ( Henbury) I keep getting very similar scores.

Same is with softpowertable.... However there was couple of times where I got 93-95k with softpowerplaytables only.

Since then it keeps around 76-80k and never goes back to the same results.

The reason I am asking because of this site which shows consistent 95k results with softpowerplaytables only. I believe it's @miliuco website and he is running exactly the same hackintosh hardware wise. https://perez987.es/amd-rx-6600-en-macos-13/ I am just wondering what can be different ....

 

 

 

 

Edited November 15, 2022 by aniuks27

[miliuco]

@aniuks27

 

Look at my GeekBench 5 scores, only RX 6600 XT, over several months.

As you can see, there is a difference of up to 15.000 points between the minimum and maximum. Always the same GPU, the same PC, no apps running but GeekBench.

In my opinion, there is something that greatly influences this test. It is the temperature of the GPU. I don't have much confidence in GeekBench 5, although it really is the one we use the most to compare equipment. But I have seen that, if the GPU is cold, below 40º (short time after turning on the PC or when using sPPT which keeps the fans spinning all time), the scores are higher, between 85000 and 95000. But when is in its normal operating temperature without sPPT (50 to 55º), the score clearly drops to 70000 - 76000.
I don't really know the reason for this behavior. It is not a high temperature because this GPU can reach 90º when graphic stress tests are done.

 

The options are the ones you already know:

1. WEG + pikera (iMac19,1 or MacPro7,1 or iMacPro1,1)
2. WEG + pikera + Henbury patch (iMac19,1 or MacPro7,1 or iMacPro1,1)
3. WEG + pikera + sPPT ( iMac19,1 or MacPro7,1 or iMacPro1,1)
4. sPPT without WEG and pikera (only MacPro7,1 or iMacPro1,1)
5. Henbury patch without WEG and pikera (only MacPro7,1 or iMacPro1,1).

You have to try the different configurations and choose the one you like best. I don't like options 3 and 5. My preferred are 1 (iMac19,1 and iGPU enabled in BIOS) and 3 (MacPro7,1 and iGPU disabled in BIOS). 

 

Spoiler

 

Edited November 16, 2022 by miliuco