[pre-release] macOS Ventura

[Ellybz]

1 hour ago, PropoFlexWX4 said:

How do I prevent Ventura from automatically putting the machine to sleep?
There was a slider in the "Power Saver" page in System Preferences... But in the new System Settings app this slider is absent.

• Display- > Advanced -> Energy

 

• HEVC/H264  is also working fine on RX580 & Skylake-X 9th GEN. without any extra kext.

 

• Sleep is however non functional on my X299 - Instant wake with KP.

 

 

 

 

Edited June 12, 2022 by Ellybz

[Matgen84]

12 hours ago, eSaF said:

DRUM ROLL Please - 'Ladies and Gentlemen, we got him' (historic words and quite apt). Seriously thanks to the tireless efforts of the OC Devs making it possible and a big thank you to @Cyberdevs and @pico joe for sharing the Folder that saved my sanity. Bigups to fellow members that offer up help along the way, much appreciated, if you guys were nearby, I'd smother you all with kisses.   The wife is happy, it's socks again this year.

 

Now please excuse me while I have a play with my new toy.

 

 

Hi @eSaF Can you share your EFI folder, please !  I want to play with this new toy too 🙂

[Gravarty]

8 hours ago, PropoFlexWX4 said:

That's life in the bleeding edge my friend.
BTW what is your SMBIOS?

 

iMac19,1

 

8 hours ago, PropoFlexWX4 said:

Changing the timezone apparently crashes the clock on this beta. Irreversibly.

Well.. its a beta.

 

Both upgrade and clean install. 

 

Confirmed: As soon as you change the timezone, to anything other than Cupertino, notification center, control center and the clock crash and permanently disappear from the menu bar.

 

I see, yeah i changed my timezone in OOBE and after getting into desktop, the right part of the menu bar was just "frozen" and beachballing.

[mhaeuser]

On 6/8/2022 at 7:17 AM, Middleman said:

As STLVNUB says it might work with the Aptio fixes, but it could gets tricky as there are more than 6 variations of AptioFix if I recall:

- OSXAptioMemoryFix, OSXAptioFix2, OSXAptioFix3, AptioMemoryFix-64, OsxAptioFix2Drv-64, and EmuVariable64.

I was just linked this thread... please don't (even in the future). Anything but OC's quirk code is broken and outdated. Generally, issues at this level cannot be resolved by throwing random approaches till one doesn't break boot, because there is plenty to break outside kernel handoff (and these things may or may not be obvious). AvoidRuntimeDefrag is not optional and cannot be safely disabled on machines that are not Macs, known to not have SMM usage (e.g. OVMF compiled without it) and maybe legacy BIOS (I lack knowledge there).

[v-volodi]

6 hours ago, The Tech said:

Make sure you have patched your FB connectors.

it works normally in monterey with skl properties, without patched connectors, but ventura with kbl properties - black screen, now i patched connectors , but also black screen, any ideas?

[Cyberdevs]

To all people that encountered the "A required firmware update could not be installed" issue:

 

After cross examining several config.plist files I realized the key factor that was missing from my configs is the set of string "run-efi-updater=No" which only was present at: 7C436110-AB2A-4BBB-A880-FE41995C9F82 entry under the NVRAM section.

After taking a closer look at @pico joe's config I realized in his config the "run-efi-updater=No" was also available in the NVRAM under "4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14" and "4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102" so I added these values to my original config which I was using for Monterey and earlier versions of macOS, updated the kexts and OC to latest version (0.8.2) and the installer went smoothly without any issues.

 

I just finished the installation of Ventura with these settings being added to the config.plist and I will try once more without these stings just to prove my conclusion and share the results.

 

Thanks to all the OC devs and all the people that helped to resolve this issue.

[MorenoAv]

Today I compared my config.plist with the config.plist of @MaLd0n, and tweaked mine...

Now I'm able to boot with my original EFI.

As you can see below...

[Matgen84]

34 minutes ago, eSaF said:

Sure Buddy here you go, this is a clean install EFI. Insure you clean the NvRAM before you run it from your installer USB stick. Good luck.

 

Thanks, Bro. 🙂

[Middleman]

1 hour ago, Download-Fritz said:

I was just linked this thread... please don't (even in the future). Anything but OC's quirk code is broken and outdated. Generally, issues at this level cannot be resolved by throwing random approaches till one doesn't break boot, because there is plenty to break outside kernel handoff (and these things may or may not be obvious). AvoidRuntimeDefrag is not optional and cannot be safely disabled on machines that are not Macs, known to not have SMM usage (e.g. OVMF compiled without it) and maybe legacy BIOS (I lack knowledge there).

Yup, I totally agree with you! Using OC quirk is much better and safer. I only quoted them because folks were talking about 'needing' an alt form of the quirk.
Believe me, I've had my fair share of using and testing the various memory efis when I was building my Comet Lake setup! It was such a pain, I DO NOT recommend it.

 

Edited June 12, 2022 by Middleman

[Takiller]

11 hours ago, Gravarty said:

Has someone found out how fix the menu bar bug? I only have Spotlight and everything else is missing.

I think it has to do with wifi not working proper, as I have the same issue and the only time it worked was when my Intel WiFi was on. Unfortunately I had to turn it off, as it is causing a panic.

[Takiller]

How do I disable Apple RSN, as it seems for me to be able to use Intel WiFi in Ventura, Apple RSN must be disabled?

 

"Update: The Monterey version with Apple RSN disabled works fine on Ventura. Using Apple RSN will trigger a kernel panic."

Edited June 12, 2022 by Takiller

[FrDakota]

Hi all.

I installed Ventura with  Big Sur on external disk in OpenCore 8.2 on Coffee Lake Asus Rog Strix-E Gaming i9-9900, but I'm hit with the infamous "A required firmware update could not be installed.".

 

With the same OC config I successfully boot the USB installer that I created following this https://apple.stackexchange.com/questions/324710/install-macos-high-sierra-app-does-not-appear-to-be-a-valid-os-installer-applica since the 11GB download of InstallAssistant.pkg only gives once extracted a 32MB Install application.

 

I tried MaLdOn's EFIs for Coffee Lake but it resulted with a KP both with the installed disk and the boot key.

 

Included my config.plist

config copie.plist

[Cyberdevs]

@eSaF

Thanks for testing and proving my theory right. The original run-efi-updater should have been enough but that's strange why it didn't work on our hacks in the first place. There are some reports that macOS installer (not Ventura) boots into a grey screen which was cause by some settings like prev-lang:kbd and other settings in the NVRAM which could be resolved by removing those setting from the NVRAM.

 

Now the interesting part is that I did another test without the extra run-efi-updater entries and even with the NVRAM being reset before booting into the installer, the installation went smoothly so if you're up to the task you can test that as well.

For some reason run-efi-updater simply didn't work on our rigs before and now it does.

 

 

[MorenoAv]

In order to fix my unknown processor what is the number of my i5 9600K?, until Ventura I didn't need to put the number of the processor it was detected automatically...

Or more clearly processor type...

Thanks

 

Edited June 12, 2022 by MorenoAv

[simmel]

Hello!

 

Just want to report partial success installing Ventura on my H61 Sandy Bridge system with Clover version 5146. Installation went smooth with AvoidRuntimeDefrag (ARD) disabled. I don't need ARD to boot Monterey. The only quirk I need is EnableWriteUnprotector. But it looks like there is an error mounting the boot device.

 

I hope updated OcRuntime.efi will help. Not sure about AVX2. If it is really required now, there might be a chance that it will not be required later, as we could see at RDRAND instruction. 

[Anto65]

11 minutes ago, MorenoAv said:

In order to fix my unknown processor what is the number of my i5 9600K?, until Ventura I didn't need to put the number of the processor it was detected automatically...

Or more clearly processor type...

Thanks

 

[Guest 5T33Z0]

@MorenoAv Here's a list of what numbers which can be entered. But I think you have to change the Endianness from big (0xVWXY) to little endian (XYVW)

 

https://github.com/acidanthera/OpenCorePkg/blob/master/Include/Apple/IndustryStandard/AppleSmBios.h

[miliuco]

@Stefanalmare

You already know that some of us with Z390 have been able to boot Ventura with your EFI. I have a comment for you.

 

Just before the picker there is a message for just a few tenths of a second, do you see it too?

It says "OC: Failed to drop ACPI 52414D44", it refers to the item that is in ACPI >> Delete, TableSignature is the value of the error message but with the bytes reversed (444D4152), if I delete that item from ACPI >> Delete or set Enabled = False, the error message disappears.

 

Without SSDT-DMAR.aml, Ventura boots fine and loads its own DMAR table from BIOS. I think this is better than loading SSDT.DMAR provided into your EFI as it corresponds to your motherboard.

 

Anyway, thanks again.

[SavageAUS]

3 hours ago, Cyberdevs said:

To all people that encountered the "A required firmware update could not be installed" issue:

 

After cross examining several config.plist files I realized the key factor that was missing from my configs is the set of string "run-efi-updater=No" which only was present at: 7C436110-AB2A-4BBB-A880-FE41995C9F82 entry under the NVRAM section.

After taking a closer look at @pico joe's config I realized in his config the "run-efi-updater=No" was also available in the NVRAM under "4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14" and "4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102" so I added these values to my original config which I was using for Monterey and earlier versions of macOS, updated the kexts and OC to latest version (0.8.2) and the installer went smoothly without any issues.

 

I just finished the installation of Ventura with these settings being added to the config.plist and I will try once more without these stings just to prove my conclusion and share the results.

 

Thanks to all the OC devs and all the people that helped to resolve this issue.

 

Would be good if the devs of OC could chime in and provide some light on this. Like is having both these values needed or are they redundant and where this is actually needed. 

[MorenoAv]

Thanks @antuneddu, @5T33Z0, for your prompt answers,

My Processor type is 0, and the result is below...

I don't know how to change the Endianness, could you please explain it to me?

Thanks

PS: My SMBIOS is IMac20,2 and it shows Mac only...

 

Edited June 12, 2022 by MorenoAv

[Stefanalmare]

16 minutes ago, miliuco said:

@Stefanalmare

You already know that some of us with Z390 have been able to boot Ventura with your EFI. I have a comment for you.

 

Just before the picker there is a message for just a few tenths of a second, do you see it too?

It says "OC: Failed to drop ACPI 52414D44", it refers to the item that is in ACPI >> Delete, TableSignature is the value of the error message but with the bytes reversed (444D4152), if I delete that item from ACPI >> Delete or set Enabled = False, the error message disappears.

 

Without SSDT-DMAR.aml, Ventura boots fine and loads its own DMAR table from BIOS. I think this is better than loading SSDT.DMAR provided into your EFI as it corresponds to your motherboard.

 

Anyway, thanks again.

If you use a modified ACPI table, you need to block the genuine one. The DMAR table from my EFI is done like this to support AppleVTD in the same time non affecting WIFI and ethernet. AppleVTD exist in all new Mac and for me is usefull for thunderbolt, thunderbolt ethernet, etc. To the one in my folder I changed "Reserved Memory Region" with one from genuine iMac19.1 and it is working great. Also you need to disable DisableloMapper.

PS: If you have Z390 Aorus, for sure our genuine DMAR tables are the same.

Edited June 12, 2022 by Stefanalmare

[Matgen84]

3 hours ago, Cyberdevs said:

To all people that encountered the "A required firmware update could not be installed" issue:

 

After cross examining several config.plist files I realized the key factor that was missing from my configs is the set of string "run-efi-updater=No" which only was present at: 7C436110-AB2A-4BBB-A880-FE41995C9F82 entry under the NVRAM section.

After taking a closer look at @pico joe's config I realized in his config the "run-efi-updater=No" was also available in the NVRAM under "4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14" and "4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102" so I added these values to my original config which I was using for Monterey and earlier versions of macOS, updated the kexts and OC to latest version (0.8.2) and the installer went smoothly without any issues.

 

I just finished the installation of Ventura with these settings being added to the config.plist and I will try once more without these stings just to prove my conclusion and share the results.

 

Thanks to all the OC devs and all the people that helped to resolve this issue.

@Cyberdevs @eSaF

Unfortunately, I can't actually test Ventura on my Z390. Thanks  both of you for your explanations and efi folder. I don't understand  about "run-efi-updater=No" under "4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14" and "4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102"
Dortinia Guide refers to BlacklistAppleUpdate=true for Coffee Lake (Z390). It do not work on Ventura ? Let me know, please.
 

Spoiler

 

Edited June 12, 2022 by Matgen84

[miliuco]

@Stefanalmare

Thank you. Understood.

[ghost8282]

1 hour ago, simmel said:

Just want to report partial success installing Ventura on my H61 Sandy Bridge system

I'm interested in this, were you able to get to the language selector?

In my system with sandy bridge I'm able to partially complete the installation, by also overwriting the os.dmg taken from a m1 machine+patch for root hash check, till when (I think) the language selector should appear, where it hangs.

 

On another forum there are instructions about how to install ventura on a macpro 5,1: the user says that on the mac pro 5,1 you can start installation, overwrite os.dmg, then take out the hd and complete installation on an ivy bridge (or more recent) machine (what I don't understand is why it should complete on ivy and not on sandy, since both lack avx2..); after installation is completed install again the hd in the mac pro and it boots.

Edited June 12, 2022 by ghost8282

[Stefanalmare]

Just now, ghost8282 said:

I'm interested in this, were you able to get to the language selector?

In my system with sandy bridge I'm able to partially complete the installation, by also overwriting the os.dmg taken from a m1 machine+patch for root hash check, till when (I think) the language selector should appear, where it hangs.

You'll never install VENTURA IN Ivybridge and older without AVX2 emulation.

https://forums.macrumors.com/threads/monterand-probably-the-start-of-an-ongoing-saga.2320479/post-31162545