[pre-release] macOS Ventura

[aben]

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

[Guest 5T33Z0]

Here are my obervations:

1. 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.
2. 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

[Slice]

Not AAPL,slot-name=Built-in

The correct syntax is

built-in=01

[Guest 5T33Z0]

@Slice Like I said. AAPL;slot-name for iGPU is MANDATORY in macOS Ventura. Otherwise no GPU Tab in Activity Monitor!

Edited July 6, 2022 by 5T33Z0

[Slice]

1 hour ago, eSaF said:

Tried that didn't get the desired result.

@Slice - Could you please give an exact example of the Entry to induce Built-In. Thanks.

Look four posts up to the post by @aben

1 hour ago, 5T33Z0 said:

@Slice Like I said. AAPL;slot-name for iGPU is MANDATORY in macOS Ventura. Otherwise no GPU Tab in Activity Monitor!

It looks like Activity Monitor is not intended for iGPU.

[Guest ricoc90]

35 minutes ago, Slice said:

It looks like Activity Monitor is not intended for iGPU.

That indeed is the same conclusion I came to. However, when not defining the AAPL,slot-name for the iGPU it won't show the dGPU either. Might be per Apple's design as well though, but then it's a weird design lol.
Maybe @Cyberdevs can confirm this assuming that he still has access to the iMac 20.1?


On another note, I ordered a Z490 board which should arrive today. I want to see if it makes any difference in comparison to a 500 series motherboard (apart from the iGPU actually being able to output)

Edited July 6, 2022 by ricoc90

[Guest 5T33Z0]

If this would be the case there wouldn't be diferent processes assigned to iGPU and GPU…

[Guest ricoc90]

I mean, fair point. However a google search leads me to posts about viewing GPU usage on genuine Macs and none of them show the GPU tab in their Activity monitor.
E.g. https://apple.stackexchange.com/questions/400360/0-gpu-usage-on-imac-2019-with-radeon-pro-560x-help

It seems like it is intended to be viewed through Window -> GPU History instead.

I don't understand why the tab DOES show up when the slot-name is being injected as it seems not per Apple's design allthough you might expect it is, why else would that tab exist in the first place? Might be SMbios-specific? E.g. Mac Pro's

Edited July 6, 2022 by ricoc90

[Slice]

This is ioreg from real iMac20,1

 

dGPU is also built-in

[Slice]

MacBookAir8,1

iGPU is built-in.

[deeveedee]

Not sure if this helps, but real MacMini8,1 IORegistry doe not have AAPL,slot-name defined for IGPU.  It does have built-in = 00.

Edited July 6, 2022 by deeveedee

[FirstCustomac]

1 hour ago, ricoc90 said:

Might be SMbios-specific? E.g. Mac Pro's

Is it possible to have GPU tab to be present under SMBIOS MacPro7,1?

 

1 hour ago, ricoc90 said:

I mean, fair point. However a google search leads me to posts about viewing GPU usage on genuine Macs and none of them show the GPU tab in their Activity monitor.
E.g. https://apple.stackexchange.com/questions/400360/0-gpu-usage-on-imac-2019-with-radeon-pro-560x-help

It seems like it is intended to be viewed through Window -> GPU History instead.

And even with this, I can't see iGPU usage in GPU History under Headless Mode unless non-headless mode is used which increase booting time by double.

 

10 hours ago, 5T33Z0 said:

@FirstTimeCustomac Thanks. I never had that GPU Tab before using the empty framebuffer suggested by Dortania's Install guide.

You are welcome. But, I merely tested this based on information shared and what was already stated by @ricoc90  so the credit goes to him.

[aben]

macOS Ventura Beta 3 seeded! 

[Wayang-NT]

hi all ... I'm back ...

macOS Ventura 13.0 beta 3 (22A5295h) seeded .....

[Skyfallkavu]

Failed on Z370 (requires avoidruntimedefrag quirk) on 0.8.2 dev — updating to latest to try again.

[Stefanalmare]

First try failed on first stage on z690. All updated. Faild w/wo avoidruntimedefrag.

Edited July 6, 2022 by Stefanalmare

[PMheart]

Where did you get stuck?

[Stefanalmare]

3 minutes ago, PMheart said:

Where did you get stuck?

Where ramrod need to start. Continuous loop,

Edited July 6, 2022 by Stefanalmare

[Skyfallkavu]

Looks to be the same place as B1 before avoidruntimedefrag worked -- past the OC initialisation and then quick messages until an ACPI Shutdown is called.

 

I can take a video if you'd like; unsure how else to record messages like that.

 

I did notice my real MBP rebooted about three times before showing the "About 10 minutes remaining..." message. Might be new firmware as well.

[PMheart]

2 minutes ago, Skyfallkavu said:

Looks to be the same place as B1 before avoidruntimedefrag worked -- past the OC initialisation and then quick messages until an ACPI Shutdown is called.

 

I can take a video if you'd like; unsure how else to record messages like that.

 

I did notice my real MBP rebooted about three times before showing the "About 10 minutes remaining..." message. Might be new firmware as well.

Yes please. You can also send the video in PM if you want.

[D3v1L]

don't update to beta 3...(for z3xx) ...same as beta 1 ...newly change to runtimedefrag needed? ...

btw, installed and works with no problem on my MP7,1

 

 

Edited July 8, 2022 by D3v1L

[Skyfallkavu]

Just sent the PM. Does (to me) look like the problems we had with B1 for everyone else. Fails at syncing ramdisk then shuts down.

[Anto65]

Same here ... bootlop , with OC , Clover  with and without AvoidRuntimeDefrag ... lol

[Slice]

Same here....

[PG7]

same here

bootloop