Help with Ventura

[loganMac]

Hi all,

Sorry if in wrong section.

I would like to update Ventura.  Currently, I'm using latest Clover v5150.  I tried to update but I'm stuck at Apple logo.  Not sure what else to give for more info so you can help.  Should I use OCLP?  Thank You

 

https://imgur.com/a/HxU0Ec9

[naiclub]

You need OC to install and clover is not supported, but clover is bootable.

After you successfully installed root patch with OC
Then you can boot with clover.

Edited November 1, 2022 by naiclub

[miliuco]

I think recent Clover releases can install and use Ventura. As 5150, used by @loganMac.

 

But you are talking about SandyBridge that has lost support for Ventura. You must set a SMBIOS model supported by Ventura, I guess that you have done so.

I see CrytexpFixup, are you using also config.plist patches extracted from OCLP?

I see that you have also added -crypt_force_avx in boot args.

Maybe it's time to try to build an OpenCore EFI.

[loganMac]

Thank you all for your help.  Last night I read OC guide from dortania's github and view youtube video of Mr Macintosh.  Per my system, do I use  OpenCore-Patcher-GUI.app or OpenCore-Install-Guide?

 Attach is my EFI I created last night using OpenCore-Install-Guide. Hope some can review config.plist if it's good.  Is VT1705 the same as VT1705S? Thank you.

 

Screenshot inside USB

 

Edited November 2, 2022 by loganMac

[loganMac]

Here's my new EFI.  When booting from USB, I'm stuck at

00:000 00:000 OC: Failed to bootstrap SB NVRAM values - Invalid Parameter

 

Not sure what I need to do.  I google but nothing.

 

Thanks!

 

EFI.zip

Edited November 3, 2022 by loganMac
reupload efi

[stagtrader]

after installing Opencore you need to use the ocvalidate utility located in the utilities folder of your Opencore download. not sure which version you used but always use the latest release found here:

https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true

 

using the appropriate Opencore validate tool shows what may be preventing you from booting or having a valid config. plugging your config file in yielded:

 

 

once you have a successful booting Opencore monterey install then you can move onto upgrading to ventura 😅

Edited November 3, 2022 by stagtrader

[loganMac]

@stagtrader I used 0.8.5 from acidanthera's github but follow dortania's guide.  Once home, I will use dortania OC 0.8.6. and his's Kext.  I will clear CMOS just in case because I have Clover Bootloader.  I my bios, I saw 2 Mac OSx, OpenCore and my 2 SSD. 

 

Edited November 3, 2022 by loganMac

[stagtrader]

@loganMac i would suggest cloning (use CCC with Legacy Bootable Copy Assistant option enabled) your current monterey install with clover & then unplugging it. that way if anything goes wrong you can still boot to your original drive. then i would begin experimenting with Opencore on the cloned drive & yes you will want to remove all traces of clover nvram from your newly cloned drive.

you could also use 2 usb drives one with your original clover & another with OC if cloning isn't an option.

Edited November 3, 2022 by stagtrader

[miliuco]

@loganMac

 

Add the following item in

NVRAM >> Delete >> 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 >> BridgeOSHardwareModel.

Reboot and do ResetNVRAM first time.

 

[loganMac]

@miliuco Does this mean I don't need to clear CMOS (3-pin and battery removed)? Is BridgeOSHardwareModel need to stay in config.plist even after post installation? I'm planning to do clean installation.  Eager to go home and test it out lol.

 

Thanks to both of you.

[miliuco]

@loganMac

No, clear CMOS on the board only if it's required when usual methods (sudo nvram -c in Terminal or ResetNVRAM in the OC picker) do not work.

 

Adding BridgeOSHardwareModel in the NVRAM delete keys usually fixes the  Failed to bootstrap SB NVRAM values - Invalid Parameter error.

 

Edited November 3, 2022 by miliuco

[loganMac]

I was able to do clean monterey installation using OC 0.8.6. All work for my pc.
Now I’m using the same EFI folder. Install a clean Ventura. Installation done and pc boot from usb then OC start running internal drive. At this point, It's been boot looping for the last 10min.  Maybe I need to disabled AvoidRuntimeDefrag?

EFI (2).zip

Edited November 4, 2022 by loganMac
add EFI folder for review

[loganMac]

Do I need to use OCLP gui for my system to work? Or do I need any other boot-arg so it's not boot looping?

[miliuco]

@loganMac

No, don't disable AvoidRuntimeDefrag.

 

I think your EFI lacks patches for SkyLake, they can be got from OCLP config.plist but I don't know which patches are suitable ones. And they are for OC, not Clover. You need somebody with more skills about this.

 

 

 

 

 

 

[loganMac]

35 minutes ago, miliuco said:

@loganMac

No, don't disable AvoidRuntimeDefrag.

 

I think your EFI lacks patches for SkyLake, they can be got from OCLP config.plist but I don't know which patches are suitable ones. And they are for OC, not Clover. You need somebody with more skills about this.

 

 

 

 

 

 

 

I'm using OC, not Clover.

[stagtrader]

@loganMac you need the CryptexFixup.kext in order to boot Ventura its missing from the above efi folder you posted.

you will need to add these to your boot arguments

'-cryptbeta'

'-amd_no_dgpu_accel'

'amfi_get_out_of_my_way=0x1' (Ventura specific as amfi_get_out_of_my_way=1 only works in Monterey & below)

 

you will also most likely need NoAVXFSCompressionTypeZlib-AVXpel.kext in order to boot Ventura if your CPU is pre-Sandy.

 

also disable secure boot in order to apply the OCLP Root Patch. once patched you can remove '-amd_no_dgpu_accel' from your boot arguments 😅

 

you may also need to reinstall Ventura with the above info if your Preboot is not over 4GB+

Edited November 7, 2022 by stagtrader

[loganMac]

@stagtrader is that what you mean by disabled secure boot Misc—> Security—> SecureBootModel—>Disabled

 

Is SecureBootModel need to stay disabled after removing “-amd_no_dgpu_accel“ or change back to Default?

 

Thanks. 

[stagtrader]

@loganMac yes exactly 😃

i left mine disabled for the time being on Ventura. On Monterey its set to Default.

Edited November 4, 2022 by stagtrader

[loganMac]

Finally got Ventura fully working. I don’t need NoAVXFSCompressionTypeZlib.Kext because it caused blackscreen. 
 

for OCLP root patch, doing this will not be able to install patch., Misc—> Security—> SecureBootModel—>Disabled.  I had to edit in NVRAM and change from 00000000 to 03080000 to disable SIP then I can install the patch. 
 

Thank you at @stagtrader and @miliuco

 

[loganMac]

Another question for OpenCore boot menu.  I have 3 SSD. Each SSD only install one operation system.  Since I have extra unused SSD, just in case one (MacOS) is acting up and I have other SSD to use.

SSD 1 Windows 11

SSD 2 Monterey

SSD 3 Ventura

 

When only 2 SSD, OC don't show EFI but when I have 3 SSD, EFI drive show on OC menu.  How can I hide EFI drive from showing in OC Menu? See attached.

 

https://imgur.com/a/6qoeVmU

[naiclub]

6 hours ago, loganMac said:

Another question for OpenCore boot menu.  I have 3 SSD. Each SSD only install one operation system.  Since I have extra unused SSD, just in case one (MacOS) is acting up and I have other SSD to use.

SSD 1 Windows 11

SSD 2 Monterey

SSD 3 Ventura

 

When only 2 SSD, OC don't show EFI but when I have 3 SSD, EFI drive show on OC menu.  How can I hide EFI drive from showing in OC Menu? See attached.

 

https://imgur.com/a/6qoeVmU

Spoiler

Try this selection.

[miliuco]

@loganMac  @naiclub

 

The proposed ScanPolicy hides Windows disk. Not good for loganmac. 
The EFI entry comes from the not booting macOS disk. OpenCore hides itself (macOS boot disk hides its EFI) but shows other macOS EFIs. This can‘t be skipped in my opinion. 

Edited December 22, 2022 by miliuco

[loganMac]

54 minutes ago, miliuco said:

@loganMac  @naiclub

 

The proposed ScanPolicy hides Windows disk. Not good for loganmac. 
The EFI entry comes from the not booting macOS disk. OpenCore hides itself (macOS boot disk hides its EFI) but shows other macOS EFIs. This can be skipped in my opinion. 

 

So that mean, I can't hide it? per MountEFI, it came from Monterey - Data (disk4s1).  Not a big deal having an extra drive but if it's "hide-able"  would be great. More cleaner look  

[naiclub]

10 minutes ago, loganMac said:

 

หมายความว่าฉันไม่สามารถซ่อนมันได้? ตาม MountEFI มันมาจาก Monterey - Data (disk4s1) ไม่ใช่เรื่องใหญ่ที่จะมีไดรฟ์พิเศษ แต่ถ้า "ซ่อนได้" จะดีมาก ดูสะอาดตาขึ้น 

Spoiler

 

[stagtrader]

@loganMac you can set your ScanPolicy to your liking here https://oc-scanpolicy.vercel.app/ & plug that value into your OC config 😅