macOS 13 Ventura on Unsupported Macs Thread

[Aston441]

Is is possible to use old intel HD 3000/4000 memory hack with OCLP? I've tried without luck. It should work but I was not able to achieve it.

The kext edit should makes the iGPU have 2GB or even 4GB of video memory.

What is the hack? I've never heard of this.

 

[Aston441]

In addition to the post above, I suggest you try using Monterey or Big Sur with that older Mac Mini. I don't have it now, but I did have a MBP8,2 from 2011 that ran much better on Big Sur. It was a problem because those MBP had Radeon GPUs that were prone to sudden death. That particular machine lasted years, but I disabled the discrete GPU using a terminal nvram command. The machine ran hotter than normal but it was usable. Not so with Ventura, which does require a lot of root patches! Of course, going back to Big Sur is a lot of hassle, but it may be worth the time.
I actually think those non-metal computers should be put out of service when that is possible, and now that you have that good iMac, maybe the Mac Mini needs a rest, or at least use as a music server or the like.

I agree. 2011/older machines run fabulously on Monterey.

 

[steverae]

I agree. 2011/older machines run fabulously on Monterey.

Yep, I’ve gave up on my 10,1 iMac running Ventura and switched over to my 12,2 to see how it fairsX currently running Monterey sweet as, anyone had issues with this model before I try and Ventura it ?

(I have a lot of old Mac’s)

 

[Portiere]

What is the hack? I've never heard of this.

It is a macOS installation on standard PC (non Apple).

 

[DerMario]

I have the following Problem:

I update my (allways working and allways updated) legacy patched unsupported mac. Then like normal it starts unoptimised and i have to post install the root patches with oclp 6.1. I do without any error, restart.....and it hangs on the apple logo with loading bar 1/3.

No restart helps, what can I do? I have a iMac late 2013

 

[Tockman]

I have the following Problem:

I update my (allways working and allways updated) legacy patched unsupported mac. Then like normal it starts unoptimised and i have to post install the root patches with oclp 6.1. I do without any error, restart.....and it hangs on the apple logo with loading bar 1/3.

No restart helps, what can I do? I have a iMac late 2013

Update to 13.3 beta?

 

[deeveedee]

It is a macOS installation on standard PC (non Apple).

The question was "what is the hack?," not "what is a hack?" -

@ikir If your HD3000/HD4000 Memory hack was implemented in OpenCore, then you should still be able to implement the hack with OCLP. When you "build opencore" with OCLP, you are simply generating an Open Core EFI. After building the Open Core EFI, you can modify the auto-generated config.plist to your heart's content. You can even upgrade Open Core to a newer version that has not yet been included in OCLP. For example, OCLP 0.6.1 implements its EFI build with Open Core 0.8.8. I wanted Open Core 0.9.0, so I performed the Open Core upgrade myself.

 

[Bmld]

hello, Lot of users as problem with a new os or an update. Don't forget, that it is possible to boot from external USB so I have an old hard disk with all macOS to repare a crash. Another advice is to install 2 os on your Mac. It is possible with OCLP without problems and you choose the os at the boot. To avoid to reinstall all the app, this one are on a third partition. To do this, create a new container with the disk tool and choose this new 'disk' when you install your new OS. Everytime I do this to test à new OS.

 

[DerMario]

Update to 13.3 beta?

Yes!

 

[Tockman]

Yes!

Well, so I've got just two questions:
1. Why update to betas if you are not a developer?
2. Why not read about specific beta behavior before updating to it?
2a. Why not read at least two previous pages of the thread you are asking in? Starting of that, for instance: https://forums.macrumors.com/thread...unsupported-macs-thread.2346881/post-32012782

 

[DerMario]

Well, so I've got just two questions:
1. Why update to betas if you are not a developer?
2. Why not read about specific beta behavior before updating to it?
2a. Why not read at least two previous pages of the thread you are asking in? Starting of that, for instance: https://forums.macrumors.com/thread...unsupported-macs-thread.2346881/post-32012782

Oh, I am sorry. I will do next Time. But thanks for your notice

 

[Tockman]

Oh, I am sorry. I will do next Time. But thanks for your notice

Your nearest future is either downgrade or life without graphic patch, at least for some time.

 

[sinbad21]

Third beta is out. Soon the release ? There will be a big problem with OCLP.

 

[davidlv]

Third beta is out. Soon the release ? There will be a big problem with OCLP.

That "big problem" may disappear soon.
The 0.6.2 nightly has been updated, with the date 3-8-2023. It installs and completes the Post Install root patches much quicker than the previous (2-11-2023) version. So obviously the devs have been working on it.
By the time Apple gets a real 13.3 version out to the public, the OCLP app may well be capable of dealing with it.
Actually, I trust the OCLP devs more than Apple, who have made some changes in the OS I can't really get behind.

 

[DaveFromCampbelltown]

Third beta is out. Soon the release ? There will be a big problem with OCLP.

iMac 17.1 Late 2015 iMac, running Ventura on an external mini-RAID drive.

Installed 13.3 - ok
Upgraded to 13.3 ß1 - ok
Upgraded to 13.3 ß2 - ok
Upgraded to 13.3 ß3 - not ok. Endless re-booting.

Downloading ß2 full installer to start again...

 

[olad]

The question was "what is the hack?," not "what is a hack?" -

@ikir If your HD3000/HD4000 Memory hack was implemented in OpenCore, then you should still be able to implement the hack with OCLP. When you "build opencore" with OCLP, you are simply generating an Open Core EFI. After building the Open Core EFI, you can modify the auto-generated config.plist to your heart's content. You can even upgrade Open Core to a newer version that has not yet been included in OCLP. For example, OCLP 0.6.1 implements its EFI build with Open Core 0.8.8. I wanted Open Core 0.9.0, so I performed the Open Core upgrade myself.

OpenHeartSurgery??

 

[Tockman]

iMac 17.1 Late 2015 iMac, running Ventura on an external mini-RAID drive.

Installed 13.3 - ok
Upgraded to 13.3 ß1 - ok
Upgraded to 13.3 ß2 - ok
Upgraded to 13.3 ß3 - not ok. Endless re-booting.

Downloading ß2 full installer to start again...

May you read two comments upper?

 

[coolio2004]

Installation of 13.3 b3 went fine on my MBA 7,2 2015 with OCLP 0.62 11.02.2023 - no problems at all so far with post patch.

 

[based_tea]

so....I messed up ventura installation using opencore, i tried fixing it but just ended up digging a deeper hole and now whenever i turn my macbook on im presented with
[Bootkicker.efi / Openshell.efi / ResetNVRAM]

help!!

 

[hvds]

Thanks! On MBP5,2, installing 13.3b2 now over b1.

OTA update went unattended up to login screen.
Then as usual connected external keyboard/mouse via USB hub.
Applied post-install patches from latest OCLP 062n (10Feb), internal devices also work after that as usual.
13.3b2 works well enough as b1 did (ie Safari blank pages, Firefox as workaround).

This is NOT a recommendation to try 13.3b3

But just another test on non-metal MBP5,2 with 13.3 and OCLP nightly.

Installed OTA 13.3b3 over b2, using latest OCLP062n (today) which contains a new PatcherSupportPackage binary, to external SSD. KDK handling worked.

Went well. As before, Safari presents empty screen, using Firefox instead. Wifi works well, as before. Books cover images work now!

 

[deeveedee]

Khronokernel committed a new update to the OCLP github repo. First update in a few weeks. Very appreciative of all he does for us and looking forward to OCLP 0.6.2!

EDIT: I just realized I was late to the party. Thanks to @davidlv for first notifying us about the OCLP update here.

EDIT2: Saw this note in Khronokernel's latest commit. Glad you're back from surgery! Hope you have a speedy and full recovery!

 

[osxfr33k]

Today the PCBs for the internal BT hub add-on card arrived. Will see tomorrow how this brings back full BT functionality while running Ventura on cMP4,1 and 5,1.
Stay tuned... ;-)

Is there a thread on this upgrade so we can still use original BT on cMP? With the latest OCLP will this mod work with cMP 3,1?

 

[coolio2004]

This is NOT a recommendation to try 13.3b3

But just another test on non-metal MBP5,2 with 13.3 and OCLP nightly.

Installed OTA 13.3b3 over b2, using latest OCLP062n (today) which contains a new PatcherSupportPackage binary, to external SSD. KDK handling worked.

Went well. As before, Safari presents empty screen, using Firefox instead. Wifi works well, as before. Books cover images work now!

Same to me on my mBP 5,1. As always i had to use a usb hub 2.0 before post patching. Problems still remain with latest compiled OCLP 0.62: emty Safari pages and no stage manager after post patch. But google chrom works fine.
I didńt update my MM Haswell, because the is no full installer 13.3b3 atm in case I had to repair my broken volume after updating on 13.3b3.

 

[tah]

Sorry, never tried that on that machine and I gave it away recently, so I can't test it.

Anyone else out there with MBP 8.2 get facetime camera to work with Big Sur, Montereyor Ventura

 

[deeveedee]

Anyone else out there with MBP 8.2 get facetime camera to work with Big Sur, Montereyor Ventura

It might be that you need to grant permissions for using the camera. Read this. More details below...

Depending on your graphics, OCLP may need to generate an OpenCore config.plist that includes boot-arg amfi=0x80 (same as boot-arg amfi_get_out_of_my_way=1). With this boot-arg, macOS won't display permission request prompts (e.g., you won't see requests to use your camera). Read this to learn how to use tccplus as a work-around for this problem.

I documented this here with some examples.