FirstTimeCustomac Posted July 5, 2022 Share Posted July 5, 2022 (edited) @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 7 Link to comment Share on other sites More sharing options...
Stefanalmare Posted July 5, 2022 Share Posted July 5, 2022 (edited) 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 4 Link to comment Share on other sites More sharing options...
datafeedexpert Posted July 5, 2022 Share Posted July 5, 2022 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.... 1 Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted July 5, 2022 Share Posted July 5, 2022 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 Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted July 5, 2022 Share Posted July 5, 2022 (edited) 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 Link to comment Share on other sites More sharing options...
Stefanalmare Posted July 5, 2022 Share Posted July 5, 2022 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. Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted July 5, 2022 Share Posted July 5, 2022 (edited) 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 Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted July 5, 2022 Share Posted July 5, 2022 @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! Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted July 5, 2022 Share Posted July 5, 2022 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. Link to comment Share on other sites More sharing options...
FirstTimeCustomac Posted July 5, 2022 Share Posted July 5, 2022 (edited) 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 1 Link to comment Share on other sites More sharing options...
miliuco Posted July 5, 2022 Share Posted July 5, 2022 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). 2 Link to comment Share on other sites More sharing options...
chris1111 Posted July 5, 2022 Share Posted July 5, 2022 (edited) 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 3 2 Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted July 6, 2022 Share Posted July 6, 2022 (edited) @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 Link to comment Share on other sites More sharing options...
eSaF Posted July 6, 2022 Share Posted July 6, 2022 (edited) @5T33Z0 - Hi if I may point out something in your Activity Monitor GPU pic, yes I know and we are all in agreement that there is no real benefit but in your posted pic you have both iGPU and GPU occupying the same Slot. Whereas mine is displayed correctly, personally that would be a bugbear for me and a great need to put it right. No biggie, just thought I'd bring it to your attention. Spoiler Spoiler Edited July 6, 2022 by eSaF Link to comment Share on other sites More sharing options...
Slice Posted July 6, 2022 Share Posted July 6, 2022 This is somehow wrong. iGPU is not in Slot 0 which is on PCI bus. It is Builtin. It is built in CPU. 5 Link to comment Share on other sites More sharing options...
eSaF Posted July 6, 2022 Share Posted July 6, 2022 6 minutes ago, Slice said: This is somehow wrong. iGPU is not in Slot 0 which is on PCI bus. It is Builtin. It is built in CPU. 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. 2 Link to comment Share on other sites More sharing options...
Slice Posted July 6, 2022 Share Posted July 6, 2022 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. 4 2 Link to comment Share on other sites More sharing options...
eSaF Posted July 6, 2022 Share Posted July 6, 2022 3 minutes ago, Slice said: Clover has a method to inject it. OC no. I suppose my next question would be, why did it appear correct and then disappear if OC has not the capability to inject it. At this point I think it's better than having both registered as occupying the same Slot. 1 Link to comment Share on other sites More sharing options...
miliuco Posted July 6, 2022 Share Posted July 6, 2022 (edited) @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 4 2 Link to comment Share on other sites More sharing options...
eSaF Posted July 6, 2022 Share Posted July 6, 2022 @miliuco Thanks Bro I'll have another play around and see if I can replicate my initial first attempt settings and see if I can correct it to read as Built-In as before. 4 Link to comment Share on other sites More sharing options...
aben Posted July 6, 2022 Share Posted July 6, 2022 (edited) You may also choose to have this GPU property corrected by simply adding "built-in" key under respective GPU location, and enabling said property by injecting value 01 or 01000000. Remove AAPL,slot-name key if present as well. EDIT: In most cases, simply omitting AAPL,slot-name key from iGPU alone should suffice, however there are instances where injection of above property can help depending on framebuffer profile chosen. Edited July 6, 2022 by aben Added info 7 1 Link to comment Share on other sites More sharing options...
eSaF Posted July 6, 2022 Share Posted July 6, 2022 (edited) Sorry but no amount of permutations, Combinations or followed examples will induce the Built-In readout. Removing AAPL,slot-name key in DeviceProperties as suggested also removes GPU Tab in Activity Monitor which defeats the purpose. I have included a series of pics so that the keen eye and knowledgeable can scrutinise and offer up advice (or just say.....Give it up Dude) because I am at lost at what else to try. Spoiler Edited July 6, 2022 by eSaF 1 2 Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted July 6, 2022 Share Posted July 6, 2022 (edited) Here are my obervations: For the GPU Tab to be displayed under macOS Ventura, AAPL,slot-name entry is mandatory for me. In older macOS versions it's not mandatory. I am co-signing @eSaF in this case. Changing AAPL,slot-name to "built-in" or keeping "internal@…" with an additional "built-in" key doesn't make a difference. It still says the Slot 01, GPU 1 for the UHD 630. DevProps: Outcome: Edited July 6, 2022 by 5T33Z0 Link to comment Share on other sites More sharing options...
Slice Posted July 6, 2022 Share Posted July 6, 2022 Not AAPL,slot-name=Built-in The correct syntax is built-in=01 6 Link to comment Share on other sites More sharing options...
eSaF Posted July 6, 2022 Share Posted July 6, 2022 (edited) 18 minutes ago, Slice said: Not AAPL,slot-name=Built-in The correct syntax is built-in=01 Tried that didn't get the desired result. @Slice - Could you please give an exact example of the Entry to induce Built-In. Thanks. Edited July 6, 2022 by eSaF 1 Link to comment Share on other sites More sharing options...
Recommended Posts