[pre-release] macOS Ventura

[Cyberdevs]

@prcmelo

From what I can see there are no kext for 300 series available your device is using AMD9000Controller.kext which is absent in macOS Ventura. I guess only 400 series and above are supported.

[Middleman]

6 hours ago, miliuco said:

To all who have tried on a 300 series without success-

 

This is what I have tried so far:

• OC 0.8.2 with latest Lilu, VirtualSMC and WG
• AvoidRuntimeDefrag y/n
• AdviseFeatures y/n
• SMBIOS iMacPro1,1 / iMac20,2 / MacPro7,1
• SSDT-PMC.aml y/n
• Combinations of all options.

AvoidRuntimeDefrag disabled + AdviseFeatures disabled + iMac20,2 + SSDT-PMC enabled is the combination with which the installation program goes the furthest but never reaches the language selection.

Miliuco,

Just remembered - did you add a UEFI driver for the Aptio memory to this and if so which one?

[aben]

35 minutes ago, Cyberdevs said:

Actually yes, I tried the clean install method and I even I ran the installer from an exiting macOS and once it was done the Ventura boot process nags about nvram and then stops at AppleSMC and then reboots.

I too had experienced this same issue during my initial trials, with the system rebooting right after this AppleSMC error log shown post final install phases, however this occurrence was a one-timer after which I remember having to include -vsmcbeta along with the other settings I mentioned earlier for successful boot right away. I've since had success installing macOS 13 one more time during which I saw no errors; both installations were performed on the same drive and was accomplished using the same macOS 13 install.app via macOS 12 (had to arrange for an additional EFI source with AvoidRuntimeDefrag off so that install would complete after reboot); the first attempt was a direct upgrade to pre-installed macOS 12 APFS partition and the second was a clean install directed to the same APFS partition that was formatted, the second time was a breeze.

 

Suggestion: Try create new APFS partition not volume (click CMD+2 to enable Show All Devices view while in Disk Utility and tap on the root Drive to create partition; preferably through macOS 12 recovery) and use macOS 13 install.app to direct a clean install onto that partition through an internal macOS volume on same drive. Do ensure you are booting with AvoidRuntimeDefrag ON while initiating the install for proper NVRAM handovers and when the first restart is being initiated, be ready to boot off an EFI with AvoidRuntimeDefrag off. These were the steps I followed for successful installation OR you can wait it out till Acidanthera team comes with a fix to improve NVRAM compatibility for Ventura.

[ndungu6678]

2 hours ago, Middleman said:

I know what you're saying here - but that is CPU spoofing you are doing right there.

Well value you have above for the so-called Álder Lake' processor is actually Comet Lake i9! I know as I was the one of the first few to find

that and post that particular value on my Z490 guides for High Sierra/Catalina. As for the CPU values the system does derive it from the SMBIOS.
Which is why when choosing a SMBIOS you have to find one that a) matches the processor to the best similar-specced Mac model and b) find

one that also matches the graphics card line-up as some of the more basic SMBIOSes doesn't have a DGPU (which is why they'll crash on boot).

Sorry got that all wrong- thanks for the the correction

[Pavo]

1 hour ago, ghost8282 said:

Nice thought!

Tried also the tpm version, compiled edk2 202205 (which I'm using in a windows 11 vm); there's no difference in my case compared to audk 202202 with no tpm support.

Can you share your compiled versions of audk 202202 OVMF?

[miliuco]

22 minutes ago, Middleman said:

... Just remembered - did you add a UEFI driver for the Aptio memory to this and if so which one?

No, I haven't tried aptio memory driver yet, I think it will not be very compatible with OpenCore 0.8.2.

Tried the other advises that you posted (-no_compat_check, max kernel, -lilubetall...) with no luck.

Thanks again.

[Cyberdevs]

@aben

I guess I'm gonna wait a bit and see how it goes, I already installed it on my AlderLake rig so I can wait for other systems to be supported (or not)

[miliuco]

5 hours ago, aben said:

@Cyberdevs @miliuco @eSaF Hi guys, test with below settings: ...

Thank you for your post but I have had no luck with these options, even with MaxBiosVersion.

 

[ghost8282]

23 minutes ago, Pavo said:

Can you share your compiled versions of audk 202202 OVMF?

Sure, these are ovmf files (from audk), no tpm support.

As said these are synced with edk2 stable 202202 with some commits from acidanthera (edk2-->audk); I think that soon new commits will be available to sync with the latest edk2 202205.

OVMF_AUDK_202202-06-03-2022.zip

 

Attaching also v 202205 from edk2 (no tpm support) and edk2 202205 with tpm support.

ovmf-stable-202205.zip ovmf-tpm-stable-202205.zip

Edited June 8, 2022 by ghost8282

[PropoFlexWX4]

Will try something different.

Someone on reddit said their installer froze at the 12 minute mark, as mine did.

But that turning on "AdviseFeatures" in config plist prevent the installer from hanging.

 

I didn't try a fresh install with that quirk enabled.

Worth the attempt.

Edited June 8, 2022 by PropoFlexWX4

[prcmelo]

1 hour ago, Cyberdevs said:

@prcmelo

From what I can see there are no kext for 300 series available your device is using AMD9000Controller.kext which is absent in macOS Ventura. I guess only 400 series and above are supported.

@Cyberdevs Thank you! SO I guess that's the end of Hack to me, will be keep using Monterey, anyway is better than back to Windows 11 which is also killing old PCs like mine.

[Middleman]

36 minutes ago, ndungu6678 said:

Sorry got that all wrong- thanks for the the correction

You're welcome. However I have one more thing to say to you...

 

I had a look at your config.plist for the setup. To be absolutely frank, I don't know how your machine ever managed to boot because it has so many errors!

It is how can I say, very messy sadly. You've got way too many SSDTs plus ACPI patches in the list. Your device properties list is also very long as is your kexts list (there's a Firewire driver in there and the Intel IGPU device properties has been mixed into the same PCIRoot address as a RX580). As well as having a DSDT.aml (which is a no-no) you've even got laptop trackpad SSDTs in your desktop build! Not forgetting, you've also got a big EFI drivers list and enabled more than 4 HFS efi drivers including HFSLegacy (only need one). Plus also enabled a bunch of USB port maps and XHCI kexts (you should only use ever ONE USB map kext not many, and only ONE XHCI kext added if required for one particular generation of motherboard (denoted by either Z200 or Z300 series - not three including the XHCI for the X99 board). If you don't take some of those out you could well run and burn out and overheat your system at some point because it is improperly configured.

That said, I am intrigued at what has caused your machine to boot. And I see you do have a couple of interesting kexts installed some of which I've not ever seen used before:

SIPManager.kext
EFICheckDisabler.kext
DebugEnhancer.kext
Innie.kext
AppleMCEReporterDisabler.kext (I've only seen this working on AMD Ryzen setups so far, not Intel)
FeatureUnlock.kext
RTCMemoryFixup.kext

[Guest 5T33Z0]

@eSaF Is this an external drive connected via USB you are trying to install macOS on?

[ndungu6678]

29 minutes ago, Middleman said:

You're welcome. However I have one more thing to say to you...

 

I had a look at your config.plist for the setup. To be absolutely frank, I don't know how your machine ever managed to boot because it has so many errors!

It is how can I say, very messy sadly. You've got way too many SSDTs plus ACPI patches in the list. Your device properties list is also very long as is your kexts list (there's a Firewire driver in there and the Intel IGPU device properties has been mixed into the same PCIRoot address as a RX580). As well as having a DSDT.aml (which is a no-no) you've even got laptop trackpad SSDTs in your desktop build! Not forgetting, you've also got a big EFI drivers list and enabled more than 4 HFS efi drivers including HFSLegacy (only need one). Plus also enabled a bunch of USB port maps and XHCI kexts (you should only use ever ONE USB map kext not many, and only ONE XHCI kext added if required for one particular generation of motherboard (denoted by either Z200 or Z300 series - not three including the XHCI for the X99 board). If you don't take some of those out you could well run and burn out and overheat your system at some point because it is improperly configured.

That said, I am intrigued at what has caused your machine to boot. And I see you do have a couple of interesting kexts installed some of which I've not ever seen used before:

SIPManager.kext
EFICheckDisabler.kext
DebugEnhancer.kext
Innie.kext
AppleMCEReporterDisabler.kext (I've only seen this working on AMD Ryzen setups so far, not Intel)
FeatureUnlock.kext
RTCMemoryFixup.kext

I feel embarrassed by your observations- as I said beforeI am no guru and have absolutely no coding experience-i accept i have used a trial and error approach without any real logic to boot my hacks over the last few years- should have been more careful to follow the strict guidelines governing proper EFI construction-as I can see my settings do not help anyone to find the correct settings guess even make it more difficult for one  to sift through my inexcusable mess I call  my EFI - now wish I never posted my configplist to start with-just want to learn from experts like you-i also don't know why my machine is booting Ventura-i will try and make all the fixes you suggest to improve-sorry again for so many mistakes

Edited June 8, 2022 by ndungu6678

[Guest 5T33Z0]

@ndungu6678 The first thing you should do is drop OpenCore Configurator and use OpenCore Auxiliary tools instead since it has OC Validate instegrated and tells you immediately about errros and automatically migrates your config to the lastest version. No more maving keys around manually. It also has dropdown menus which show sou which quirks to use for the CPU you are using.

[PropoFlexWX4]

Made some progress.

By turning off AvoidRuntimeDefrag and turning on AdviseFeatures I was able to start the installer from USB without using “-lilubetaall”

 

Will keep everyone posted.

 

Perhaps this has to do with the SMBIOS I’m using as well — MacPro7,1.

 

Update — hit another error: “A required firmware update could not be installed.”

 

Update 2: Changed SMBIOS to iMac20,2 — Second try.

 

Update 3: No avail. iMac20,2 SMBIOS leads to freeze at 12 minute mark.

 

Update 4: Turns out I don’t need “AdviseFeatures” to get the installer to boot. If I could only manage to get past the “Required firmware update could not be installed” error…

 

 

Edited June 8, 2022 by PropoFlexWX4

[Middleman]

17 minutes ago, ndungu6678 said:

I feel embarrassed by your observations- as I said beforeI am no guru and have absolutely no coding experience-i accept i have used a trial and error approach without any real logic to boot my hacks over the last few years- should have been more careful to follow the strict guidelines governing proper EFI construction-as I can see my settings do not help anyone to find the correct settings guess even make it more difficult for one  to sift through my inexcusable mess I call  my EFI - just want to learn from experts like you-i also don't know why my machine is booting Ventura-i will try and make all the fixes you suggest to improve-sorry again for so many mistakes

You're welcome! And no need to apologise. It is just a learning curve and we all make learn and mistakes as part of the growth (we've all been there). The main reason I wanted to point it out to you is I didn't want it to cause some sort of fire hazard as having more drivers and kexts installed means its running a lot of programs and files in the background. If not carefully checked your PC could easily overheat and we don't want that. 😄

As to correcting and learning about the issues, well I'd say a good way to start would be to actually try to do a simple EFI build for an already well documented and working OS you're already familiar with like Big Sur or Monterey. You could follow the Dortania guide online on the particulars of your system on how to get it to boot with the new EFI (in this case a Desktop Coffee Lake) and work on the config.plist build from there from the devices all the way to the GPU and SMBIOS settings. That should allow you more than enough of an insight on how to get the system working. Once you have that you can then work on the Ventura build.

[Stefanalmare]

9 minutes ago, eSaF said:

I will try the Drive internally and see if that makes a difference.

Doesn't work. 

[ndungu6678]

31 minutes ago, Middleman said:

You're welcome! And no need to apologise. It is just a learning curve and we all make learn and mistakes as part of the growth (we've all been there). The main reason I wanted to point it out to you is I didn't want it to cause some sort of fire hazard as having more drivers and kexts installed means its running a lot of programs and files in the background. If not carefully checked your PC could easily overheat and we don't want that. 😄

As to correcting and learning about the issues, well I'd say a good way to start would be to actually try to do a simple EFI build for an already well documented and working OS you're already familiar with like Big Sur or Monterey. You could follow the Dortania guide online on the particulars of your system on how to get it to boot with the new EFI (in this case a Desktop Coffee Lake) and work on the config.plist build from there from the devices all the way to the GPU and SMBIOS settings. That should allow you more than enough of an insight on how to get the system working. Once you have that you can then work on the Ventura build.

Thanks again - you are completely right- I didn't realise these setting could not only reduce the lifespan of my hack if not cause a disaster -will do-cheers!

[Pavo]

2 hours ago, ghost8282 said:

Sure, these are ovmf files (from audk), no tpm support.

As said these are synced with edk2 stable 202202 with some commits from acidanthera (edk2-->audk); I think that soon new commits will be available to sync with the latest edk2 202205.

OVMF_AUDK_202202-06-03-2022.zip 938.48 kB · 0 downloads

 

Attaching also v 202205 from edk2 (no tpm support) and edk2 202205 with tpm support.

ovmf-stable-202205.zip 959.82 kB · 0 downloads ovmf-tpm-stable-202205.zip 1.22 MB · 1 download

Thanks, got it working now with unraid's normal OVFM by changing

<qemu:arg value='host,vendor=GenuineIntel'/>

to 

<qemu:arg value='Cascadelake-Server,vendor=GenuineIntel'/>

[ghost8282]

1 hour ago, Pavo said:

Cascadelake-Server

Nice Pavo!that was a thing I was planning to do tomorrow, but thanks for the confirmation it's working!Does it boot to desktop in some way?Because I had no issue in completing part of the installation with the gui.

I think the spoofing could be however fixed (maybe) with an opencore commit (?), or maybe in the config with cpuid spoofing (?)

Edited June 8, 2022 by ghost8282

[PC IT]

14 hours ago, aben said:

Good news for Skylake users looking to experience the flavors of macOS Ventura on iGPU-only Skylake systems (tested on HD 520). Seeing acceptable iGPU hardware acceleration even with KBL framebuffer (not surprising since KBL is loosely based off SKL, architecture-wise with slight improvements to the 14nm manufacturing process bringing higher base-clock speeds to the CPU while using lower voltage thereby improving performance-per-watt metric essentially making KBL CPUs a better "tuned" version of SKL. With regards to integrated graphics, only KBL's Iris Plus Graphics 650 showcased any significant performance gains with Intel HD 620/630 being largely identical to Intel HD 530/520 found in SKL)

TBH I actually don't see any difference in graphics performance with the HD 520 compared to macOS 12; just as smooth and snappy. The following 3 attributes are essential to get working graphics acceleration for Skylake on macOS 13:

• for mobile/laptop users, inject recommended KBL framebuffer profile: 0x591B0000 (Big Endian) to AAPL,ig-platform-id  property.
• inject fake device-id to match against equivalent KBL counterpart, for eg: Intel HD 520 can opt for Intel HD 620's Device ID: 0x5916 to Little Endian 16590000 to device-id property.
• inject boot-arg: -disablegfxfirmware

Required device-properties reference format for Intel HD 520:

AAPL,ig-platform-id     00001B59       DATA
device-id               16590000       DATA

Two issues currently faced on my Dell Inspiron with current OC build: 1. system freezes when OS tries to access NVRAM variables, for eg: when changing brightness (should be fixed soon by Acidanthera team) and 2. display sometimes wakes up to black screen from sleep.

 

Other than seeing the usual UI-related glitches/intermittent choppiness with the new redesigned System Settings, this build has been pretty stable so far which is kinda baffling given the fact that it's the very first pilot beta and being surprisingly performant even on un-supported hardware.

Absolutely stoked to learn that Skylake owners don't have to be left behind now with acceptable iGPU support on macOS Ventura.

 

  Reveal hidden contents

 

Hello dear, may i have your skylake config plist or your efi for test?, i tried your solution on my skylake hd520 laptop but seems i am missing something, the usb installer halt with graphics properties, i appreciate your help. Thanks

[Pavo]

48 minutes ago, ghost8282 said:

Nice Pavo!that was a thing I was planning to do tomorrow, but thanks for the confirmation it's working!Does it boot to desktop in some way?Because I had no issue in completing part of the installation with the gui.

I think the spoofing could be however fixed (maybe) with an opencore commit (?), or maybe in the config with cpuid spoofing (?)

I do all installs/upgrades using VNC without GPU pass through, because sometimes it glitches out with the way macOS resets it. But I can get to desktop without issues.

[Djlild7hina]

Easy update on ASUS X299 here

 

Edited June 9, 2022 by Djlild7hina

[PropoFlexWX4]

I am afraid, that like many others here, this is where I stop.

 

iMac20,2 SMBIOS — Freeze At 12 Minutes Remaining.

 

Any other SMBIOS (iMac19,1 / MacPro7,1…) leads to the message on the picture.

Edited June 8, 2022 by PropoFlexWX4