[pre-release] macOS Ventura

[Anto65]

habla italiano señor ? 😆  🤔 

 

 

[nexusneko]

Comme ci, comme ça. 🙃

[aben]

9 hours ago, greythorne said:

meaning that is it ok to remove the SSDT-Plug.aml?

Sure! You may safely omit this good old SSDT, used for rectifying CPU power management, from EFI(s) configured to boot macOS Monterey 12.3 and above, on x86 machines post-Ivy Bridge. X86PlatformPlugin on these macOS versions (incl. Ventura) no longer checks/matches against plugin-type=1 condition while assigning CPU power management, thereby enabling native XCPM correctly (no ASPP), by default. No harm whatsoever with keeping this non-functional SSDT as is, but if you feel the need to clear up an unnecessary patch, feel free to do so.
 

Technically, no reason whatsoever for existence of this legacy, rather obsolete ASPP (ACPI_SMC_PlatformPlugin) anymore, given the fact that support for pre-Haswell architecture (non AVX-2) too is now fully out of the picture in Ventura as well; surprised that Apple decided to leave this antique non-functional dead-log behind.

[eSaF]

I am throwing this out to the knowledgeable ones (says he, looking @5T33Z0 and @antuneddu before I forget, also the lovable joker @ricoc90 )

Spoiler

 

[miliuco]

7 hours ago, nexusneko said:

... Did it! and it works. 😜

 Then maybe powerd issue happens upgrading to beta 4 on some system languages (not all @antuneddu ) but not in English.

 

6 hours ago, aben said:

Sure! You may safely omit this good old SSDT, used for rectifying CPU power management, from EFI(s) configured to boot macOS Monterey 12.3 and above, on x86 machines post-Ivy Bridge...

 

I'll try and comment, didn't know it.

 

6 hours ago, eSaF said:

  Hide contents

 

 

I don't have such tab in Activity Monitor. I think it wasn't in past macOS.

Edited July 29, 2022 by miliuco

[Guest 5T33Z0]

7 minutes ago, eSaF said:

I am throwing this out to the knowledgeable ones (says he, looking @5T33Z0 and @antuneddu before I forget, also the lovable joker @ricoc90 )

  Hide contents

 

 

You can right-click the column bar and have more options, but "Temperature" is  not an option. At least on Big Sur.

[deeveedee]

Thanks for the assist, @ricoc90.  Here, I have documented the differences between editing com.apple.SystemProfiler.plist in Monterey and Ventura.

[Stefanalmare]

45 minutes ago, aben said:

Sure! You may safely omit this good old SSDT, used for rectifying CPU power management, from EFI(s) configured to boot macOS Monterey 12.3 and above, on x86 machines post-Ivy Bridge. X86PlatformPlugin on these macOS versions (incl. Ventura) no longer checks/matches against plugin-type=1 condition while assigning CPU power management, thereby enabling native XCPM correctly (no ASPP), by default. No harm whatsoever with keeping this non-functional SSDT as is, but if you feel the need to clear up an unnecessary patch, feel free to do so.
 

Technically, no reason whatsoever for existence of this legacy, rather obsolete ASPP (ACPI_SMC_PlatformPlugin) anymore, given the fact that support for pre-Haswell architecture (non AVX-2) too is now fully out of the picture in Ventura as well; surprised that Apple decided to leave this antique non-functional dead-log behind.

No SSDT-Plug, it works on my Z690. Also on Ivy Bridge:

 

Spoiler

 

Edited July 29, 2022 by Stefanalmare

[Guest 5T33Z0]

34 minutes ago, Stefanalmare said:

No SSDT-Plug, it works on my Z690. Also on Ivy Bridge:

 

  Hide contents

 

 

I think this might a a false positive. Because: With macOS 12.3 Beta 1, Apple dropped the 'plugin-type' check within X86PlatformPlugin. Because of this, the X86 PlatformPower plugin will match to the CPU instead of ACPI_SMC_PlatformPlugin. In other words. The PlatformPlugin is loaded but might not be working correctly: https://github.com/acidanthera/bugtracker/issues/2013

 

And if it says XCPM is working without an SSDT-PLUG and even for Ivy Bridge – then something is fishy, since enabling XCPM on Ivy Bridge requires Kernel patches.

Edited July 29, 2022 by 5T33Z0

[ndungu6678]

Beta 4 ( 22A5311F ) done-all is well🙂

Thanks to everyone here, moderators, donators ,the OC group and developers for all your help!

 

On 7/27/2022 at 8:06 PM, antuneddu said:

Beta 4 ( 22A5311F )

 

 

 

Build 1: iMac20,2, i5-9400F, Samsung 16GB DDR4 RAM, MSI Z390 Gaming Plus , Radeon RX 580 8GB, OC 0.8.3

Edited July 29, 2022 by ndungu6678

[Stefanalmare]

21 minutes ago, 5T33Z0 said:

 

I think this might a a false positive. Because: With macOS 12.3 Beta 1, Apple dropped the 'plugin-type' check within X86PlatformPlugin. Because of this, the X86 PlatformPower plugin will match to the CPU instead of ACPI_SMC_PlatformPlugin. In other words. The PlatformPlugin is loaded but might not be working correctly: https://github.com/acidanthera/bugtracker/issues/2013

 

And if it says XCPM is working without an SSDT-PLUG and even for Ivy Bridge – then something is fishy, since enabling XCPM on Ivy Bridge requires Kernel patches.

OK, how can I check if is false-positive or true?

[Guest 5T33Z0]

36 minutes ago, Stefanalmare said:

OK, how can I check if is false-positive or true?

 

Fals positive is the wrong word. If your CPU supports the x86 platform plugin (which all Intel Core CPUs from 4th gen onwards do), it'll work for Monterey and newer withut SSDT-Plug. But ony Ivy Bridge it doesn't work without Kernel patches. So even if the plugin is loaded it's not used. My guess is thatsysctl machdep.xcpm.mode would still return 0 in this case.

 

 

Edited July 29, 2022 by 5T33Z0

[PoMpIs]

5 hours ago, miliuco said:

@PoMpIs

How do yo find about sudo pmset schedule cancelall and our powerd issue? 🤔

Anyway, nice find, high usage of powerd has gone and CPU team is 30-40º at idle.

The strange thing is the relationship between the issue and the system language as nobody with non Spanish system has reported it.

Next thing is to see if it happens again after boots.

Gracias!!!

Lo comento para @nexusneko @DocXavier

 

I learned this in beta 2, when sleep didn't work for me, I spent many hours fighting with "pmset" and learned many options...😄

 

Still, if you put this in the terminal, it tells you if there are more things scheduled:

sudo pmset -g sched

It still reports this to me:

 

 

 04/12/62  ?¿?¿?

 

It has to be a beta 4 bug.

 

 

The strange thing is that this does not happen to my Lenovo 520s, and it is in Spanish too.......... and in Europe 🤣

 

Edited July 29, 2022 by PoMpIs

[miliuco]

@Stefanalmare @5T33Z0

 

I've tried without SSDT-PLUG and macOS boots and runs fine. IOReg shows X86PlatformPlugin key below AppleACPICPU. Does it mean that indeed macOS can run without this SSDT or IOReg key isn't important to check this?

[Stefanalmare]

5 minutes ago, miliuco said:

@Stefanalmare @5T33Z0

 

I've tried without SSDT-PLUG and macOS boots and runs fine. IOReg shows X86PlatformPlugin key below AppleACPICPU. Does it mean that indeed macOS can run without this SSDT or IOReg key isn't important to check this?

I learnt that if you have in ioreg x86PlatformPlugin, you have native power management. But, @5T33Z0 say it can be false-positive. At least for Ivy Bridge.

Edited July 29, 2022 by Stefanalmare

[miliuco]

@PoMpIs

Thanks for the info and the fix.

I see that sudo pmset -g sched shows the same items seen in System Profiler >> Power >> scheduled events.

About 1962, I remember a text somewhere about files having and very old date in macOS and its explaining but I don't find the text, even I don't remember if it was 1962 and why.

 

3 minutes ago, Stefanalmare said:

I learnt that if you have in ioreg x86PlatformPlugin, you have native power management. But, @5T33Z0 say it can be false-positive. At least for Ivy Bridge.

Ok. I have Coffee Lake so it must be a true positive.

Edited July 29, 2022 by miliuco

[Guest 5T33Z0]

10 minutes ago, miliuco said:

@Stefanalmare @5T33Z0

 

I've tried without SSDT-PLUG and macOS boots and runs fine. IOReg shows X86PlatformPlugin key below AppleACPICPU. Does it mean that indeed macOS can run without this SSDT or IOReg key isn't important to check this?

 

Well, on macOS Monterey and newer you don't need SSDT-PLUG since the plugin check has been removed so the plugin will load anyways. I don't know if you still need SSDT-ALT if you have an alderlake CPU, though.

[PoMpIs]

 @miliuco  

 

After leaving the computer for almost 12 hours in sleep, the problem has happened again... 🤷‍♂️ I had to delete it.... 

 

If I turn it off or restart it doesn't happen....   ¿a rare bug? 

[miliuco]

@PoMpIs

Mine goes on fine, after a few hours powerd is still away.

Logic says that it has to come back on at some point. 
We are still having a problem with the scheduler options in the Energy Saver panel.
When I open System Preferences, Energy Saver is not there from the first moment but appears a few tenths of a second later than the other options.

Edited July 29, 2022 by miliuco

[Guest 5T33Z0]

@miliuco The Energy Saver entry pops in a bit later here as well. I guess this just the usual "it's a beta" issue. This System Preferences menu is horrible, btw. It takes significantly longer to find anything in this list compared to the previous layout. You really need this find function now to reach "software update" since it os not on the top level. Apple could at least a button to switch the layout – Windows could do this 20 years ago

[Extreme™]

1 hour ago, PoMpIs said:

 @miliuco  

 

After leaving the computer for almost 12 hours in sleep, the problem has happened again... 🤷‍♂️ I had to delete it.... 

 

If I turn it off or restart it doesn't happen....   ¿a rare bug? 

 

The problem occurred to me again while i was doing some work on Ventura and without the operating system ever going to sleep. As usual, the "powerd" process is non-existent in activity monitoring

 

 

[PoMpIs]

10 minutes ago, Extreme™ said:

 

The problem occurred to me again while i was doing some work on Ventura and without the operating system ever going to sleep. As usual, the "powerd" process is non-existent in activity monitoring

 

 

 

Yes, come back, I bought it...

It returns to me like this:

 

The awakening of sleep... and after a few minutes this appears again:

 

 

But I still don't have any abnormal CPU usage caused by powerd for an hour... After an hour I already notice the increase in CPU usage caused by powerd..

I have these running every time I wake up "sudo pmset schedule cancelall" 🤷‍♂️

 

@miliuco @5T33Z0   

 

I only see this in system settings:

 

 

Do you have any other option?

 

 

[eSaF]

4 minutes ago, PoMpIs said:

I only see this in system settings:

If I may, as posted earlier these are my options in Energy Saver. I don't know why the difference unless the comparison is between a Laptop and a Desktop.

Spoiler

 

[PoMpIs]

@eSaF 

 

Thank you very much...

 

I don't use SATA drives, only NVME, that's why I don't see "put the drives to sleep"... then I have the same options as you...

I have never seen other options in Ventura 🤷‍♂️

 

PS: I have put the system back to sleep for a while and at 18:45 I have woken it up and a schedule for 5 minutes later had already been created ..... incredible

 

 

It is something related to the calendar, or the widget, as it happened in beta 2 with weather??

 

Edited July 29, 2022 by PoMpIs

[Extreme™]

22 minutes ago, eSaF said:

If I may, as posted earlier these are my options in Energy Saver. I don't know why the difference unless the comparison is between a Laptop and a Desktop.

  Reveal hidden contents

 

I have exactly the same options as you in Energy Saver: but I still have the problem. So it doesn't depend on options in Energy Saver.