[pre-release] macOS Ventura

[Guest 5T33Z0]

@Stefanalmare You could try adding SSDT-IMEI for testing. It resolved the same issue on Sandy and ivy bridge: newer Board plus oder CPU and vice versa: https://github.com/5T33Z0/OC-Little-Translated/tree/main/01_Adding_missing_Devices_and_enabling_Features/Intel_MEI_(SSDT-IMEI)

[Stefanalmare]

1 minute ago, 5T33Z0 said:

@Stefanalmare You could try adding SSDT-IMEI for testing. It resolved the same issue on Sandy and ivy bridge: newer Board plus oder CPU and vice versa: https://github.com/5T33Z0/OC-Little-Translated/tree/main/01_Adding_missing_Devices_and_enabling_Features/Intel_MEI_(SSDT-IMEI)

Thanx, but IMEI is already present. No metter if I spoof the IGPU or not.

[Cyberdevs]

I've been going through the DeviceProperties on a 2020 iMac (iMac20,1) with an Intel Core i7 10700 processor and an AMD Radeon Pro 5500 XT and there's this settings for the iGPU "PciRoot(0x0)/Pci(0x2,0x0)" called "AAPL00,override-no-connect" with the value of:

00FFFFFF FFFFFF00 06107C9C 5E91EE51 161D0104 B53C2260 206FB1A7 554C9E25 0C505400 00000101 01010101 01010101 01010101 01010000 00100000 00000000 00000000 00000000 00000010 00000000 00000000 00000000 00000000 00FC0069 4D61630A 20202020 20202020 00000000 00000000 00000000 00000000 00000153 70137903 00030014 806E0184 FF139F00 2F801F00 3F0B5100 02000400 7F8118FA 10000101 00127631 FC78FBFF 02108862 D3FAF8F8 FEFFFF00 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000C790 

as DATA type, this might help to shed some light on the display output on iGPU.

I'm not sure if that's gonna do anything on hacks but though worth to share.

 

[Stefanalmare]

3 hours ago, Cyberdevs said:

I've been going through the DeviceProperties on a 2020 iMac (iMac20,1) with an Intel Core i7 10700 processor and an AMD Radeon Pro 5500 XT and there's this settings for the iGPU "PciRoot(0x0)/Pci(0x2,0x0)" called "AAPL00,override-no-connect" with the value of:

00FFFFFF FFFFFF00 06107C9C 5E91EE51 161D0104 B53C2260 206FB1A7 554C9E25 0C505400 00000101 01010101 01010101 01010101 01010000 00100000 00000000 00000000 00000000 00000010 00000000 00000000 00000000 00000000 00FC0069 4D61630A 20202020 20202020 00000000 00000000 00000000 00000000 00000153 70137903 00030014 806E0184 FF139F00 2F801F00 3F0B5100 02000400 7F8118FA 10000101 00127631 FC78FBFF 02108862 D3FAF8F8 FEFFFF00 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000C790 

as DATA type, this might help to shed some light on the display output on iGPU.

I'm not sure if that's gonna do anything on hacks but though worth to share.

 

With the above configuration and GPU I have only H264 acceleration. With no GPU I don't have light.......... With this configuration and #AAPL00,override-no-connect comented I have what I attached:

 

Spoiler

 

Edited July 4, 2022 by Stefanalmare

[Cyberdevs]

@Stefanalmare

So if I understand correctly adding these settings enables HEVC decoding?

[Stefanalmare]

1 minute ago, Cyberdevs said:

@Stefanalmare

So if I understand correctly adding these settings enables HEVC decoding?

Yep, but also makes IGPU no-headless.

[Cyberdevs]

During the first stages of testing Ventura on my SkyLake rig when I was using SKL ig-platform-id i realized when i use iMac18,3 and iMac18,2 SMBIOSes which have AMD GPUs the colors where messed up so I switched to iMac18,1 and macMini8,1 which only have iGPU (and even MacPro7,1 which has a dGPU) the colors were shown correctly so maybe, just maybe, changing the SMBIOS to iMac18,1 or macMini8,1 can have an impact on utilization of the iGPU instead of dGPU. That's as if macOS doesn't refuse to boot due to the incorrect CPU and the SMBIOS.

[lordmacbr]

Could someone who has installed Ventura on Haswell tell me what changes have to be made in OpenCore and which kexts to use????

[Guest ricoc90]

7 minutes ago, lordmacbr said:

Could someone who has installed Ventura on Haswell tell me what changes have to be made in OpenCore and which kexts to use????

There's no support for either your iGPU nor dGPU in Ventura whatsoever

[FirstCustomac]

@ricoc90, @eSaF  Thanks for this info.  After tinkering with few configuration. These are my results under iMac19,1 headless mode.

 

1. To have both dGPU and iGPU to show up in GPU History window of Activity Monitor 

     - Force enable metal on iGPU(enable-metal, igfxmetal=1) under 0300983E or 0300913E platform-id was required.

     - Injecting 07009B3E as platform-id also worked (metal injection was not needed under this platform-id)

 

Spoiler

 

 

2. Correcting "Intel KBL Unknown" to "Intel UHD Graphics 630" only requires injecting device-id - 9B3E0000  (Both Platform-id 0300983E and 0300913E work)

     *Without injecting slot name both iGPU and dGPU are recognized as built-in              

 

Spoiler

 

 

3. Adding slot name to both iGPU and dGPU allows GPU tab to appear in Activity Monitor (Note that injecting slot name breaks iGPU accelerated encoding on FCPX tested multiple times) 

Spoiler

 

 

To sum up, unless the slot name for both iGPU and dGPU are injected, no GPU Tab appears in Activity monitor. But If the slot name is injected, GPUs are no longer recognized as built-in and it breaks IGPU accelerated encoding in FCPX as mentioned.

 

Edited July 5, 2022 by FirstTimeCustomac

[Stefanalmare]

1 hour ago, FirstTimeCustomac said:

@ricoc90, @eSaF  Thanks for this info.  After tinkering with few configuration. These are my results under iMac19,1 headless mode.

 

1. To have both dGPU and iGPU to show up in GPU History window of Activity Monitor 

     - Force enable metal on iGPU(enable-metal, igfxmetal=1) under 0300983E or 0300913E platform-id was required.

     - Injecting 07009B3E as platform-id also worked (metal injection was not needed under this platform-id)

 

  Hide contents

 

 

2. Correcting "Intel KBL Unknown" to "Intel UHD Graphics 630" only requires injecting device-id - 9B3E0000  (Both Platform-id 0300983E and 0300913E work)

     *Without injecting slot name both iGPU and dGPU are recognized as built-in              

 

  Hide contents

 

 

3. Adding slot name to both iGPU and dGPU allows GPU tab to appear in Activity Monitor (Note that injecting slot name breaks iGPU accelerated encoding on FCPX tested multiple times) 

  Hide contents

 

 

To sum up, unless the slot name for both iGPU and dGPU are injected, no GPU Tab appears in Activity monitor. But If the slot name is injected, GPUs are no longer recognized as built-in and it breaks IGPU accelerated encoding in FCPX as mentioned.

 

Totally correct! It is the same on CometLake, mobo 500.

 

Spoiler

 

Edited July 5, 2022 by Stefanalmare

[datafeedexpert]

8 hours ago, lordmacbr said:

Could someone who has installed Ventura on Haswell tell me what changes have to be made in OpenCore and which kexts to use????

Just avoid injecting iGPU Device Properties in config.plist and other things are the same like Monterey/Bigsur, If you have intel Wifi / Bluetooth Dont forget to Airportitlwm for Ventura, You must Update Opencore | Kext to Possibly latest Version....

[Guest ricoc90]

6 hours ago, FirstTimeCustomac said:

@ricoc90, @eSaF  Thanks for this info.  After tinkering with few configuration. These are my results under iMac19,1 headless mode.

 

1. To have both dGPU and iGPU to show up in GPU History window of Activity Monitor 

     - Force enable metal on iGPU(enable-metal, igfxmetal=1) under 0300983E or 0300913E platform-id was required.

     - Injecting 07009B3E as platform-id also worked (metal injection was not needed under this platform-id)

 

2. Correcting "Intel KBL Unknown" to "Intel UHD Graphics 630" only requires injecting device-id - 9B3E0000  (Both Platform-id 0300983E and 0300913E work)

     *Without injecting slot name both iGPU and dGPU are recognized as built-in              

3. Adding slot name to both iGPU and dGPU allows GPU tab to appear in Activity Monitor (Note that injecting slot name breaks iGPU accelerated encoding on FCPX tested multiple times) 

 

To sum up, unless the slot name for both iGPU and dGPU are injected, no GPU Tab appears in Activity monitor. But If the slot name is injected, GPUs are no longer recognized as built-in and it breaks IGPU accelerated encoding in FCPX as mentioned.

Thank you! You're absolutely correct. I do wish the GPU History would actually show the iGPU's usage, but you can't win them all I guess. Intel Power Gadget does for now.

Metal over the iGPU:
https://browser.geekbench.com/v5/compute/5081104

Metal over the dGPU:
https://browser.geekbench.com/v5/compute/5081117

[Guest 5T33Z0]

16 hours ago, Stefanalmare said:

Yep, but also makes IGPU no-headless.

 

In your case I would use either use iMacPro1,1 or MacPro7,1 since these SMBIOSes allow the dGPU to handle all the tasks hat the iGPU would handle otherwise. And then modify the CPU Power Management with CPUFriendFriend.

Edited July 5, 2022 by 5T33Z0

[Stefanalmare]

2 minutes ago, 5T33Z0 said:

 

In your case I would use either use iMacPro1,1 or MacPro7,1 since these SMBIOSes allow the dGPU to handle all the tasks hat the iGPU would handle otherwise. And then modify the CPU Power Management with CPUFriendFriend.

I'm in the testing faze. Just tried side-car and it works like a dream with BCM4331 (n wifi max, and native Bluetooth). In this moment my 500 series mobo with 20.1 SMBIOS is working very well with Ventura. In the near future I'lll try 1.1 and 7.1. BTW: I already used your method in this rig and in Z390 for CPUFrienDataProver.kext (https://github.com/5T33Z0/Gigabyte-Z490-Vision-G-Hackintosh-OpenCore/blob/main/Additional_Files/Optimizing_CPU_Power_ Management.md). Thank you very much! If it is possible, extend this method to work with all board-id's.

[Guest ricoc90]

56 minutes ago, 5T33Z0 said:

 

In your case I would use either use iMacPro1,1 or MacPro7,1 since these SMBIOSes allow the dGPU to handle all the tasks hat the iGPU would handle otherwise. And then modify the CPU Power Management with CPUFriendFriend.

The reason why his iGPU wouldn't work headless was because he was trying out a platform-id provided by @cyberdevs that belongs to the Iris Plus 655 and is a non-headless mobile framebuffer. The framebuffer he is supposed to use, does work on his system.

Read the full conversation before providing contradicting information. It just confuses anyone who might stumble upon your comments.

Edited July 5, 2022 by ricoc90

[Guest 5T33Z0]

@ricoc90 

 

As far as I can recall his iGPU is not working in macOS is because he is using a 10th Gen Intel Core CPU with a 500-seriies board

And: my info is not contradictory – iGPU no work with 500-series board ? = try a different SMBIOS which works around the issue.

I  give advice and make suggestions. If people make use of them or not, is up to them – not me or you!

[Guest ricoc90]

3 minutes ago, 5T33Z0 said:

@ricoc90 

 

As far as I can recall his iGPU is not working in macOS is because he is using a 10th Gen Intel Core CPU with a 500-seriies board

And: my info is not contradictory – iGPU no work with 500-series board ? = try a different SMBIOS which works around the issue.

I  give advice and make suggestions. If people make use of them or not, is up to them – not me or you!

His GPU works fine headless, which was the point of it all. He literally confirmed it in his reply directly above mine.
But again, you'd have known if you had read the whole conversation. You chiming in isn't the issue. it's your attitude I'm having an issue with. In general. 

[FirstCustomac]

17 hours ago, ricoc90 said:

I do wish the GPU History would actually show the iGPU's usage, but you can't win them all I guess. Intel Power Gadget does for now.

 

Just checked and if platform-id 07009B3E is used it is achievable. But then again, it does not fully maximize iGPU in HEVC-8 Bit encoding in FCPX and adding slot-name makes it worse.

Nonetheless, it is good to see VTEncoderXPCService and VTDecoderXPCService appear under GPU process.

 

Spoiler

   

 

Without slot-name injection under platform-id 07009B3E, iGPU is much better utilized. As far as I can tell, IQSV is much faster than UVD for encoding purposes in FCPX.

 

Spoiler

 

GeekBench Score

Spoiler

 

 

 

Edited July 6, 2022 by FirstTimeCustomac

[miliuco]

52 minutes ago, FirstTimeCustomac said:

Just checked and if platform-id 07009B3E is used it is achievable. But then again, it does not fully maximize iGPU in HEVC-8 Bit encoding in FCPX and adding slot-name makes it worse...

Please add a signature to your profile (account details).

[chris1111]

I just have a Security Popup Extensions add Open Security 

 

 Apple Inc as been Updated

I turn Off share Mac analytics 

 

 

 

Edited July 5, 2022 by chris1111

[Guest 5T33Z0]

@FirstTimeCustomac Thanks. I never had that GPU Tab before using the empty framebuffer suggested by Dortania's Install guide. Now it's present in Activity Monitor from Catalina all the way up to Ventura. But you definitely must inject Properies for both iGPU and GPU for it to appear. Not sure about injecting the device-id for my CPU. Boot feels faster without  it.  Gotte test it a little more.

 

 

I am wondering, if the GPU Tab also appear when you only have an iGPU (configured for outputting graphics). On my Laptop I don't have this Tab.

Edited July 6, 2022 by 5T33Z0

[Slice]

This is somehow wrong. iGPU is not in Slot 0 which is on PCI bus. It is Builtin. It is built in CPU.

[Slice]

2 minutes ago, eSaF said:

Yes I agree, when I started to configure a headless setup it read Built-In (see attached) but after removing some items from Device Properties it read as Slot 0. No matter what I did, I cannot get it to read as Built- In again.

I know how it should be but OC is not knowing.

The key is _SUN property in DSDT/SSDT for this device. It must be absent for builtin.

The description and some properties should be present in SMBIOS table 9 corresponding to this device. Clover has a method to inject it. OC no.

[miliuco]

@eSaF

 

As @Slice says, iGPU must be built-in as in real Macs. We have already read that even AMD dGPU must be built-in because it works better in this way.

Do you have AAPL,slot-name key in DeviceProperties? You can remove it (better) or at least change Slot-0 / Slot-1 (if they exist) by Internal@0,2,0 / Internal@0,1,0/0,0/0,0/0,0 or what gfxutil (or Hackintool) shows as your AMD device path.

 

Edited July 6, 2022 by miliuco