Jump to content
3338 posts in this topic

Recommended Posts

Guest ricoc90

@eSaF 
Your iGPU might not be showing up because it's using an empty framebuffer. You can verify this with Hackintool. Some framebuffers don't report the GPU name. it's purely cosmetic though (I'm using a framebuffer that's being reported as Mobile = no and GPU name = Intel UHD Graphics 630)

Your RX 580 might not be showing up because it's reported as Built-In. I have it explicitly set to Slot-1 in DeviceProperties. Again, that is purely cosmetic so I am not sure if that is what causes them not showing up in Activity Monitor

Edited by ricoc90
Guest ricoc90
36 minutes ago, eSaF said:

Ok I think I am making progress, this is what I have so far (attached) but I am assuming I have to do some patching to rectify KBL Unknown, as far as I understand it is just cosmetic but hey I got this far so I might as well dig some more and go deeper. :graduated:

Indeed it is only cosmetic. If you do wish to have it reported as uhd 630 you’d need to fake its device id.

There's some information about it on an issue report at WhatEverGreen: 
https://github.com/acidanthera/bugtracker/issues/1905

 

His workaround (I would not call it a fix) is to use device-id 9B3E0000 which I confirmed does show the iGPU as uhd 630.

Edited by ricoc90
Added more info
Guest ricoc90
1 hour ago, eSaF said:

I think I am getting bogged down a little, can you post a screen shot of your Device Properties pertaining to the Entries so that I can make a comparison to what I have achieved so far? I would appreciate that very much. Thanks.


Sure!

RX 580:

 

Spoiler

14233068_Schermafbeelding2022-07-04om10_34_32.thumb.png.e1291ed125e52eb54c290779d9d8126b.png


UHD 630:

 

Spoiler

797139004_Schermafbeelding2022-07-04om10_36_01.thumb.png.48cfec31283bfc3df0d5a79eb33195e5.png



Edit:
I forgot to mention that in order for the iGPU to show up, you'd need to define a slot-name as well. I had removed it from mine

 

Edited by ricoc90
15 hours ago, PMheart said:

To AMD users: Is your CPU brand string patch broken by using the latest version of Lilu and RestrictEvents from the master branch? In other words, can you reproduce https://github.com/acidanthera/bugtracker/issues/2065?

 

Any feedback is greatly appreciated.

When / if I get Ventura to actually install and run I will let you know. 

  • Like 2

@ricoc90

Sorry, I did a search to find the original poster referring to metalgpu without success. 
 

@eSaF

I don’t have dGPU in activity monitor, because it’s built-in, as yours was. 
Now I’ve learned a new thing, thanks to @ricoc90, to put dGPU in slot 1 to see it as a GPU process. It’s cosmetic, I also think so, but it’s interesting how OpenCore (and Clover on the other side) can set a lot of options in our hacks. 
AboutKBL unknown, think that real Macs don’t have such specific model of iGPU, it’s going to work as expected but the exact model name is not well detected. Doing device-id spoofing (thanks again @ricoc90) you can change this behavior but it’s cosmetic. Although it looks nicer right?

  • Like 2
Guest ricoc90

@eSaF How did you manage to get it being reported as being "built in"? I have to fake its device ID, but then it's location is labeled as "Slot-0" rather than "Built In" which I assumed made sense, since I was adding it to the PCI devices, but yours is being reported as Built In so I'm confused 😆

Edited by ricoc90
Guest ricoc90
1 minute ago, eSaF said:


I know, that is what I had linked you before. Going that route shows my iGPU being in "slot 0", but yours is being shown as being Built In so I wonder why that is

4 minutes ago, ricoc90 said:


I know, that is what I had linked you before. Going that route shows my iGPU being in "slot 0", but yours is being shown as being Built In so I wonder why that is

@eSaF has AAPL-slot-name=Internal@0.1.0/0.0.

  • Like 1
Guest ricoc90

@eSaF I think you don't know what I mean. In the mentioned link, the author added a screenshot of their GPU History window. You can see in that window that it shows their iGPU as being in slot 0:

 

Spoiler

1725521099_Schermafbeelding2022-07-04om12_15_59.png.e00f4fa6211c83841a7fad79625aa61b.png

 

Which correspondents with the results I have. However, on your screenshot your iGPU is being reported as Built In.
I mean it's just cosmetic, so it doesn't really matter but I'm just wondering why that is. :)

 

 

6 minutes ago, miliuco said:

@eSaF has AAPL-slot-name=Internal@0.1.0/0.0


So do I, yet it still is being reported as "Slot 0"

Edited by ricoc90

@ricoc90 @eSaF

 

Usually I have iMacPro1,1 SMBIOS with iGPU disabled in BIOS to be able to play TV app and DRM content in Safari.

But I like very much to try all different settings (iMac, MacPro, iMacPro). So I've followed your posts to set iMac19,1 with iGPU as headless mode on slot-0. It's an easy task thanks to your help.

 

Spoiler

act-mon.png.4ed8beb743e89722f6fd6c0ed45bd7f7.png

 

With this settings I've checked if the iGPU helps to the AMD in tasks (and it does) opening Intel Power Gadget while running BlackMagic RAW Speed Test, I see the iGPU (green line) up and down when required.

 

Spoiler

ipg.png.309985332b0b28230ceed55d33b2ca95.png

 

But so Safari doesn't play DRM and TV app works irregularly: sometimes it plays the movie and sometimes it doesn't. I know I can add unfairgva=1 as boot arg to do TV app to work ok but this arg hangs Ventura from time to time (on Monterey it works fine).

 

  • Like 2

Attempt 5,342 underway on my AMD system to install Ventura beta 1. Will most likely be my last attempt if I get another grey screen or reboot at network selection. This attempt is with WEG disabled, no boot args, device property is set for Belknap and all wifi kexts are removed. 
AMD patches are correct, OpenCore is latest as are kexts. Last attempt before a full head of grey hair kicks in. 
Or maybe I’ll go back to Clover….Nope Clover instant KP. Guess I am done with Ventura. 

Edited by SavageAUS
  • Haha 4
22 hours ago, ricoc90 said:

That was me, but it's pretty easy to write your own using SwiftUI's MTLDevice api...

 Excellent! Thanks. This little code fragment works very well. I see Metal 3 in both GPU (dGPU is RX 6600).

% /Applications > ./metalgpu
All credit goes to ricoc90
AMD Radeon RX 6600 supports Metal3 
Intel(R) UHD Graphics 630 supports Metal3 
% /Applications > 

I allow myself to attach the compiled utility so that other users can check the Metal 3 support on their graphics cards. Copy it to a folder and run from there with ./metalgpu.
All credit to @ricoc90.

 

 

metalgpu.zip

Edited by miliuco
  • Like 4
  • Thanks 1
Guest ricoc90
14 minutes ago, miliuco said:

I allow myself to attach the compiled utility so that other users can check the Metal 3 support on their graphics cards. Copy it to a folder and run from there with ./metalgpu.


Awesome, thanks! Do be advised that this will ONLY work in Ventura though, it will crash on any other OS because obviously .metal3 does not exist on other versions :D

11 hours ago, ricoc90 said:


Awesome, thanks! Do be advised that this will ONLY work in Ventura though, it will crash on any other OS because obviously .metal3 does not exist on other versions :D

Noted. Thanks.

 

EDIT: command line tool updated.

Edited by miliuco
Guest 5T33Z0

@ricoc90 This isn't a matter of "it's working fine" – it's about hardware compatibility. The iGPU handles Quick Look and other background tasks. So budget wise, buying a 500-series board with a 10 Gen Intel Core CPU with integrated graphis is just not recommendable.

Edited by 5T33Z0
Guest
This topic is now closed to further replies.
×
×
  • Create New...