[pre-release] macOS Ventura

[Guest 5T33Z0]

The OCLP repo contains an informative post about all the things that were removed from Ventura: https://github.com/dortania/OpenCore-Legacy-Patcher/issues/998

[jsl2000]

On 6/15/2022 at 11:59 PM, Hervé said:

Of course! KBL layout 0x591B0000 is a mobile framebuffer... 'cannot understand why you went for that.

 

Make sure to:

1. use the appropriate desktop one
2. identify the output port (i.e. connector) against which your DP screen registers (using apps such IORegistryExplorer)

 

Recommended KBL desktop framebuffer is 0x59120000:

ID: 59120000, STOLEN: 38 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000110B
TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 115 MB, MAX OVERALL: 116 MB (122171392 bytes)
Model name: Intel HD Graphics KBL CRB
Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz
Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP
[3] busId: 0x06, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP
01050900 00040000 87010000
02040A00 00040000 87010000
03060A00 00040000 87010000

Of course, you'll need the appropriate SMBIOS too.

Thanks for your help and instruction.

Unfortunately even it can boot successfully with KBL desktop framebuffer is 0x59120000, its DP/HDMI audio still disabled and only ALC-662 working. My ioreg & config.plist of OC 0.8.2 are attached here for your reference. Please advise me how to fix it.

[Solved]

DP/HDMI audio can be enabled now after disabled SkylakeInjector.kext.

iMac.ioreg

config.plist

Edited June 16, 2022 by jsl2000

[Guest 5T33Z0]

@jsl2000 Try this:

 

• Add key hda-gfx <STRING> onboard-1 to your framebuffer
• Disable PciRoot(0x0)/Pci(0x1F,0x3) (put # in front of it) since it is it referencing "onboard-1" slot but that's already addressed by  PciRoot(0x0)/Pci(0x1b,0x0)
• Save, reboot, test
• If it doesn't work, disable PciRoot(0x0)/Pci(0x1b,0x0) and enable PciRoot(0x0)/Pci(0x1F,0x3)  instead.
• Save, reboot, test

Edited June 16, 2022 by 5T33Z0

[jsl2000]

24 minutes ago, 5T33Z0 said:

@jsl2000 Try this:

 

• Add key hda-gfx <STRING> onboard-1 to your framebuffer
• Disable PciRoot(0x0)/Pci(0x1F,0x3) (put # in front of it) since it is it referencing "onboard-1" slot but that's already addressed by  PciRoot(0x0)/Pci(0x1b,0x0)
• Save, reboot, test
• If it doesn't work, disable PciRoot(0x0)/Pci(0x1b,0x0) and enable PciRoot(0x0)/Pci(0x1F,0x3)  instead.
• Save, reboot, test

Thanks for your kind help and advice.

I have followed your instruction to test step by step, unfortunately all are in vain to fix this issue.

[Joshua60]

I'm experiencing something strange with my rig #2. OC and Kext are up to date. I'm not sure if my DeviceProperties are correct, so I kindly ask for help.

 

The DP for uhd630 in my config are:

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
    <dict>
        <key>AAPL,ig-platform-id</key>
        <data>AACbyA==</data>
        <key>framebuffer-patch-enable</key>
        <data>AQAAAA==</data>
    </dict>
</dict>
</plist>

 

The issue is with Safari, minimizing and maximizing the safari window takes a lot of time.

Is similar but not exactly the same in Ventura, Monterey and Big Sur.

 

Thanks for helping.
 

[aben]

Just now, surenmunoo said:

I was using 0.8.2 but had to revert to 081 because my Fenvi T919 worked sometimes and stopped. When I reverted to 081 it works properly. 

Hmm that's strange since OC shouldn't affect IONetworking in any way. Try once with 0.8.2 and see; if it works that means you do require current OC patched for Ventura.

 I also see an error with one of your boot-args: it's -lilubetaall not -lilubetaal; either remove or test with the correct value. 

[D3v1L]

Ok so, remove weg, remove brcram"etc" ,remove pikera and lilubetaall bootarg, update OC and kext to latest beta, and try ti boot

[Cyberdevs]

Guys I moved "Unknown CPU issue" posts to this topic

Please continue there:

 

[Guest 5T33Z0]

@Cyberdevs Unlles the guy gets his config in order so he can boot with OC 082, he cannot expect that the CPU info is displayer correctly in macOS 13 when he is using OC 081…

 

So  instead of him fixing his config issues moving this to a dedicated thread makes it look like this is a general issue when it's actually not.

[Cyberdevs]

@5T33Z0

Even if it is a misconfiguration on his part this issue is not related to Ventura per se, but there are other people with similar issue so it can be beneficial to everyone that this issue is discussed in its own topic.

 

P.S.:

on my 6700K rig the info isn't detected correctly either it show is i5 because of the SMBIOS so OC doesn't necessarily work correctly. What I mean is that revcpuname doesn't work so it can be a general issue.

[surenmunoo]

14 minutes ago, 5T33Z0 said:

@Cyberdevs Unlles the guy gets his config in order so he can boot with OC 082, he cannot expect that the CPU info is displayer correctly in macOS 13 when he is using OC 081…

 

So  instead of him fixing his config issues moving this to a dedicated thread makes it look like this is a general issue when it's actually not.

I am now booting with 0.8.2 but still the same. I will leave it as is and hope maybe it starts to work later on down the line. Thanks for the help.

[mav96]

Hey guys,

 

I have a skylake rig (i7-6700HQ) with HD530 iGPU and successfully installed macOS 13 without acceleration. The problem is when I try to spoof SKL as KBL. Changing AAPL,ig-platform-id -> <00001B59> and device-id to <16590000> results in the KP shown on the screenshot below. I discovered that this particular device-id causes the KP. If I change it to <16560000>, for example, it boots successfully but without acceleration. (I have aslo added SkylakeInjector.kext, but it does not seem to work).

 

Do you have any idea what the issue might be. Thanks for the help!

Edited June 16, 2022 by mav96

[Cyberdevs]

@mav96

You can try other id-platform-ids and device-ids and see which one works. You also need a specific version of WEG.

WhateverGreen.kext.zip

[ichelash]

15 hours ago, Cyberdevs said:

With the EFI folder I posted there's no retrying on my rigs, the boot process is just normal, I did try to update the OC and the kexts but it went straight back to retrying issue.

I can confirm that test 79 & 80 were a fail also. Going back to Monterey, Ventura wants to kill me 😂

Edited June 16, 2022 by ichelash

[Cyberdevs]

13 minutes ago, ichelash said:

I can confirm that test 79 & 80 were a fail also. Going back to Monterey, Ventura wants to kill me 😂

Last night I've updated my EFI folder and specially with updating WEG i git the same issue as you have.

The WEB i've posted couple of posts above is the one that actually works without that issue because later on they removed SKL to KBL spoofing so i guess you can give it a try and if that didn't work you can stop trying

On my rigs:

1. I only have iGPU activated

2. I don't use any other settings other then ig-platform-id and device-id

3. there are no other deviceproperties other than the iGPU. 

[ichelash]

26 minutes ago, Cyberdevs said:

Last night I've updated my EFI folder and specially with updating WEG i git the same issue as you have.

The WEB i've posted couple of posts above is the one that actually works without that issue because later on they removed SKL to KBL spoofing so i guess you can give it a try and if that didn't work you can stop trying

On my rigs:

1. I only have iGPU activated

2. I don't use any other settings other then ig-platform-id and device-id

3. there are no other deviceproperties other than the iGPU. 

On my rig, VirtualSMC plugins are causing mayhem..i think i will edit that EFI and remove those plugins...will see that in test 81.

[Guest 5T33Z0]

39 minutes ago, Cyberdevs said:

Last night I've updated my EFI folder and specially with updating WEG i git the same issue as you have.

The WEB i've posted couple of posts above is the one that actually works without that issue because later on they removed SKL to KBL spoofing so i guess you can give it a try and if that didn't work you can stop trying

On my rigs:

1. I only have iGPU activated

2. I don't use any other settings other then ig-platform-id and device-id

3. there are no other deviceproperties other than the iGPU. 

 

The Spoofing support has been removed from the master branch but there's another branch (skl-as-kbl-13) which still has it: https://github.com/acidanthera/WhateverGreen/actions/runs/2495481119

Edited June 16, 2022 by 5T33Z0

[mav96]

@Cyberdevs Many thanks for sharing the WhateverGreen.kext. This was indeed the reason and now I have graphics acceleration on HD530 (btw it works even better than on the supported Monterey without spooofing ). So the kernel panic I posted before was indeed related to the spoofing commit that they removed from WEG.

Now the only issue left for me is the HDMI, which does not work at all on Ventura for me. I guess this KBL spoof also changed something regarding the HDMI bus configuration.

[Guest 5T33Z0]

11 minutes ago, ichelash said:

On my rig, VirtualSMC plugins are causing mayhem..i think i will edit that EFI and remove those plugins...will see that in test 81.

 

If you have Intel Power Gadget installed, you can use HWMonitor SMC2 and enable to use Intel Power Gadgets Monitoring capabilities in the options. Then you can disable the virtualsmc plugins

 

[Cyberdevs]

14 minutes ago, 5T33Z0 said:

The Spoofing support has been removed from

Yes I know, thanks for the link by the way it will be useful for future references.

 

@mav96

You're welcome.

HDMI works on my rig tho, although I don't have HDMI audio which is simply because I haven't added any properties to activate it.

[mboy]

I can boot Ventura OS on my build using OpenCore package compiled on June 7 (DBG-082-2022-06-07) with AvoidRuntimeDefrag=NO.  When I use today's build of OpenCore the drive does not boot when selected in the F12 bootloader. What can cause this?

[Guest 5T33Z0]

@mboy June 13th was the latest build from dortania's repo: https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true

 

For me the latest one works as well.

[ichelash]

Yesterday when i was downloading it was 12.2..GB, Now today a full GB is missing, can someone confirm this is correct or  i'm seeing my own things

 

[Cyberdevs]

@eSaF

Oh I thought it was common knowledge!

another great feature is being able to use your iPhone as a webcam. I haven’t tested it yet but this capability is awesome specially with iPhone pro and pro max with 3 cameras.

look it up

[ichelash]

18 minutes ago, eSaF said:

Query - How come no one (that I have seen) has mentioned one of the coolest features in Ventura? I think it is a no brainer and an added vantage when multi-tasking. Hopefully the members with successful installs will benefit from this new feature.

  Hide contents

 

Lol, i can my post somewhere 🤔😂, now imma go try one last shot at ventura