macOS 13 Ventura on Unsupported Macs Thread

[olad]

List of Mac models grouped by CPU type - Wikipedia

en.wikipedia.org

cheers

Or if you, like me, feel overwhelmed by the plenitude of information, you may try the free Mactracker app, which gives you all the info about your specific machine. It's available on the App Store.

 

[igisokMK2023]

Any news about Pages and import images with 0.6.5 release also wifi continunity camera working in Facetime please test and let me know.

 

[deeveedee]

It seems to me that my MBP6,2 is running Ventura 13.3.1 even better after patching with the released version of OCLP 0.6.5. I had been following the progress of 0.6.5 and patched a couple of times with developer (nightly) builds of 0.6.5, but after patching with the release, my Mac just seems "snappier." Probably just an illusion. Well done (again) OCLP developers!

Spoiler

 

[dictoresno]

I asked this before and someone said it shouldn’t work, but my Apple Watch still won’t unlock my 2014 Mac Mini (even though it says it’s unlocking and fails) but using the Apple Watch to confirm passwords or admin prompts works. It doesn’t work on 13.2.1 or 13.3.1.

Is anyone running a 2014 Mac mini with Ventura have a successful Apple Watch unlocking? If not what’s the known cause for the unlock not to work but the confirmation prompts to work just fine? On my dual boot with Monterrey on the same machine, it works as it should.

 

[coasterOneEightThree]

Yesterday the OpenCore Legacy Patcher was released in version 0.6.5.

For me and my MacPro 3,1 (specs below) maybe a good opportunity to summarize what works or doesn't work with my configuration and usage, or doesn't work quite satisfactorily. Please, dear developers, don't take this as a criticism, but only as an inventory, also so that other users can compare whether this applies to their configuration as well or not.

This is a Pre-Haswell-Mac: Therefore Apple's Rapid Security Response updates cannot be installed. So far, the only option is to wait for the next normal update for macOS 13.3.1.

Sleep mode: With Ventura, this Mac does not go into sleep. Any attempt to enter sleep is aborted and the computer continues to run. The connected display remains dark and has to be woken up as if the computer was actually in sleep mode.

After such an unsuccessful attempt to sleep and wake up the display again, Bluetooth and the Magic Mouse work, but the WiFi function is not available - the icon in the menu bar is dimmed, diagonally crossed out and WiFi cannot be reactivated without a restart.

I use a FENVI FV-T919 PCIe card for Bluetooth and WiFi. Interesting in this context is that in Monterey the Mac sleep was possible reliably, but after waking up WiFi worked and Bluetooth was disabled afterwards, but at least it could be reactivated via the keyboard control in the System Preferences without a reboot. So, the question is what causes the different behavior and perhaps if or how it could be improved or fixed.

AirDrop: Still in Monterey, AirDrop was completely unobtrusive and worked reliably. In Ventura, Airdrop is very slow to connect and occasionally does not work, aborting a transfer attempt of, for example, a picture to and from an iPhone after a long wait or during transfer.

Universal Control: Worked in Monterey, now no longer works in Ventura. (Note: In the meantime I changed the brcmfx-country code in in EFI/OC/config.plist from US to DE. I have no idea why that changed. The AirDrop channel changed from 149 to 44 after this, so that Universal Control works again! It's a bit of a hassle to set up the connection, but it works.)

Handoff and Continuity, on the other hand, work fine.

Shortcuts: Here I noticed that on the wired USB Apple Keyboard, which is not directly connected to the MacPro 3.1 but to the Mac via the USB 3 hub of my monitor, certain shortcuts (e.g. crtl-eject for the Restart, Sleep, Cancel and Shut Down dialog) or ctrl-alt-cmd-eject for direct shutdown do not work reliably. Sometimes it works, but sometimes only the drawer of the optical SATA drive opens. This was also never a problem in Monterey.

I would be interested to know if the mentioned problems are known or if someone might have a tip for fixing one or the other point.

Thanks in advance for helpful comments and hints!

 

[deeveedee]

Yesterday the OpenCore Legacy Patcher was released in version 0.6.5.

This is a Pre-Haswell-Mac: Therefore Apple's Rapid Security Response updates cannot be installed. So far, the only option is to wait for the next normal update for macOS 13.3.1.

I also have a pre-Haswell Mac (MBP6,2) and am running 13.3.1 patched with OCLP 0.6.5. I assumed that I was stuck at 13.3.1 until a fix was found for the security update implemented by the 13.3.1a RSR. Am I incorrectly assuming that the "offending" security update in the RSR (13.3.1a) would be part of all subsequent macOS releases?

EDIT: If the 13.3.1a RSR is a security update that is indeed going to be included with all subsequent versions of macOS, then I believe the only solution for pre-Haswell Macs would be to address the AVX2 requirement stated by @educovas here which may require something like this?

 

[Ready-for-Apple]

Crashing 15" rMBP 2014 with OCLP 0.6.4/0.6.5 + macOS 13.3.1​

Hi, first of all, thanks to the OCLP development team for breathing new life into our older Mac's; also many thanks to Mister Macintosh for the helpful videos.👍🏻


Issue/Bug:
My 15" retina MacBook Pro mid 2014 (base model) works fine with OCLP 0.6.4 + macOS 13.2.1

Then I installed 13.3.1, of course then with post install. But after this my MBP started crashing always I start Apple TV app, Youtube on Safari etc.

• with 0.6.5 + 13.3.1 + Post install - same Problem
• with 0.6.5 + 13.3.1 + installing the RSR + Post install – also same crashing

Safe mode (Shift + Enter on boot, right?) isn't working – always stuck at 50% also if I wait for hours


Any Solutions?🤔

1. Is there a way to send developers diagnostic report?
2. Any ideas for solution (stop crashing AND to get in safe mode)?

Thanks in advance! Best regards from Germany


PS:
Crash reports look like these 2

 

[coasterOneEightThree]

After my difficulties with AirDrop mentioned here, I found out that my MacBookPro 14,2 and my MacPro 3,1 are using two different channels for Airdrop (channel 44 and 149). ls there a way to change the AirDrop channel and the country code (from US to DE) on the MacPro 3,1 for the built-in Fenvi PCIe card?

(Note: In the meantime and after some research I was able to change the brcmfx-country code in in EFI/OC/config.plist from US to DE. I have no idea why that changed before. The AirDrop channel changed from 149 to 44 after this, so that Universal Control works again! It's a bit of a hassle to set up the connection, but it works. AirDrop is still quirky.)

 

[luckyduke23]

I also have a pre-Haswell Mac (MBP6,2) and am running 13.3.1 patched with OCLP 0.6.5. I assumed that I was stuck at 13.3.1 until a fix was found for the security update implemented by the 13.3.1a RSR. Am I incorrectly assuming that the "offending" security update in the RSR (13.3.1a) would be part of all subsequent macOS releases?

I think I read somewhere that machines older than 2013 or 2012 are not capable for RSR...

 

[luckyduke23]

Crashing 15" rMBP 2014 with OCLP 0.6.4/0.6.5 + macOS 13.3.1​

Hi, first of all, thanks to the OCLP development team for breathing new life into our older Mac's; also many thanks to Mister Macintosh for the helpful videos.👍🏻


Issue/Bug:
My 15" retina MacBook Pro mid 2014 (base model) works fine with OCLP 0.6.4 + macOS 13.2.1

Then I installed 13.3.1, of course then with post install. But after this my MBP started crashing always I start Apple TV app, Youtube on Safari etc.

• with 0.6.5 + 13.3.1 + Post install - same Problem
• with 0.6.5 + 13.3.1 + installing the RSR + Post install – also same crashing

Safe mode (Shift + Enter on boot, right?) isn't working – always stuck at 50% also if I wait for hours


Any Solutions?🤔

1. Is there a way to send developers diagnostic report?
2. Any ideas for solution (stop crashing AND to get in safe mode)?

Thanks in advance! Best regards from Germany


PS:
Crash reports look like these 2

did you upgrade to 13.3.1 before installing OCLP 0.6.5 or afterwards? Doing it afterwards should have worked fine. Doing it with OCLP 0.6.4. causes such issues as mentioned by you. In the worst case you might need to do a clean install...

 

[deeveedee]

I think I read somewhere that machines older than 2013 or 2012 are not capable for RSR...

Is it the act of applying an RSR that is not supported on pre-Haswell Macs, or is it the security update implemented in the 13.3.1a RSR that is not supported on pre-Haswell Macs?

 

[luckyduke23]

Is it the act of applying an RSR that is not supported on pre-Haswell Macs, or is it the security update implemented in the 13.3.1a RSR that is not supported on pre-Haswell Macs?

I don't know. And I don't know either if it is possible to download the RSR for manual installation somewhere. In the worst case you have to wait for the next major update 13.3.2 resp. 13.4 which also contains all previous RSRs

 

[Ready-for-Apple]

did you upgrade to 13.3.1 before installing OCLP 0.6.5 or afterwards? Doing it afterwards should have worked fine. Doing it with OCLP 0.6.4. causes such issues as mentioned by you. In the worst case you might need to do a clean install...

Always this procedure:
1. Check Update OCLP
2. Update OCLP, patch the OS and install "Post Install Root Patch" after reboot
3. Install macOS Update
4. Check + if required install "Post Install Root Patch"

I tried to update to 13.3.1 three times – also with clean install crashes like explained here: #5,377

 

[luckyduke23]

Always this procedure:
1. Check Update OCLP
2. Update OCLP
3. Install macOS Update
4. Check + Install "Post Install Root Patch"

I tried to update to 13.3.1 three times – also with clean install crashes like explained here: #5,377

just to avoid any misunderstanding I would specify item #2 more detailed such as 2. Update OCLP, patch the OS and do a post install after reboot. 🤓

 

[deeveedee]

1. Is there a way to send developers diagnostic report?

I'm not sure the extent to which crash reporting has been implemented, but in OCLP 0.6.5, Settings -> Developer Settings -> Uncheck "Disable Crash / Analytics" and apply patches.

If you have previously disabled crash reporting, then you should be able to enable crash reporting with the terminal command

defaults write com.dortania.opencore-legacy-patcher DisableCrashAndAnalyticsReporting -bool false


EDIT: @Ready-for-Apple I just performed a "defaults read | grep -i disable" on my MBP6,2 patched with OCLP 0.6.5 and did not find DisableCrashAndAnalyticsReporting. I then issued the command

defaults write com.dortania.opencore-legacy-patcher DisableCrashAndAnalyticsReporting -bool true

and now when I run "defaults read | grep -i disable" I see the following:

DisableCrashAndAnalyticsReporting = 1;


Therefore, I am not sure if the OCLP Developer setting does anything at this time.

 

[rbart]

Crashing 15" rMBP 2014 with OCLP 0.6.4/0.6.5 + macOS 13.3.1​

Hi, first of all, thanks to the OCLP development team for breathing new life into our older Mac's; also many thanks to Mister Macintosh for the helpful videos.👍🏻


Issue/Bug:
My 15" retina MacBook Pro mid 2014 (base model) works fine with OCLP 0.6.4 + macOS 13.2.1

Then I installed 13.3.1, of course then with post install. But after this my MBP started crashing always I start Apple TV app, Youtube on Safari etc.

• with 0.6.5 + 13.3.1 + Post install - same Problem
• with 0.6.5 + 13.3.1 + installing the RSR + Post install – also same crashing

Safe mode (Shift + Enter on boot, right?) isn't working – always stuck at 50% also if I wait for hours


Any Solutions?🤔

1. Is there a way to send developers diagnostic report?
2. Any ideas for solution (stop crashing AND to get in safe mode)?

Thanks in advance! Best regards from Germany


PS:
Crash reports look like these 2

I think your Mac has an AMD R9 GPU.
There are known issues in OCLP with this hardware. Video hardware decode/encode is not supported and make some apps crash:
- TV app
- Photos.app when you browse Live Photos or HEVC videos
- very slow startup for Chrome/Edge browsers
...

It's very annoying, and I don't know if we can hope for a solution.

 

[internetzel]

Is it the act of applying an RSR that is not supported on pre-Haswell Macs, or is it the security update implemented in the 13.3.1a RSR that is not supported on pre-Haswell Macs?

RSRs cannot be installed when using OCLP because of the workaround OCLP uses (using the Rosetta cryptex instead of the x86_64 one, because the latter needs an AVX2.0 capable CPU) in order to make Ventura run on pre-Haswell Macs at all.

 

[steve123]

I recall the Lilu plugin "OpCodeEmulator." I thought this plugin was supposed to emulate opcodes, including AVX2 on platforms where native OpCode support was not available. If there is hope for pre-Haswell platforms, could OpCodeEmulator be a possible solution? OpCodeEmulator

It does not look like OpCodeEmulator is compatible with Xeon processors 🥲:

Opcode Emulator (OPEMU) Plug-in Project

this is OPEMU for Lilu Plugin Intel Haswell Pentium / Celeron Series Or older processor expansion instruction set Emulation USAGE: copy Lilu.kext & OpcodeEmulator.kext To /EFI/CLOVER/kexts/Other/ NOTE: if it don't work, please rebuild Lilu and OpcodeEmulator On Your Machine. Lilu Releases: ht...

www.insanelymac.com

 

[rehkram]

Just confirming that OCLP 6.5 installs- and post-installs fine on rMBP10,1 w/13.3.1. Pre Haswell m/c so I'm not even attempting any RSR installs until further public advice from Dortania.

 

[deeveedee]

RSRs cannot be installed when using OCLP because of the workaround OCLP uses (using the Rosetta cryptex instead of the x86_64 one, because the latter needs an AVX2.0 capable CPU) in order to make Ventura run on pre-Haswell Macs at all.

Sorry I'm still not smart enough to figure this out, but I was hoping for a "yes" or "no" answer. Will we be able to install 13.4 on pre-Haswell Macs, or is 13.3.1 the last because pre-Haswell Macs are not currently compatible with the security update in the 13.3.1a RSR? Again, is it the act of applying RSRs that requires AVX2, or is it the security update in 13.3.1a that requires AVX2?

It does not look like OpCodeEmulator is compatible with Xeon processors 🥲:

Opcode Emulator (OPEMU) Plug-in Project

this is OPEMU for Lilu Plugin Intel Haswell Pentium / Celeron Series Or older processor expansion instruction set Emulation USAGE: copy Lilu.kext & OpcodeEmulator.kext To /EFI/CLOVER/kexts/Other/ NOTE: if it don't work, please rebuild Lilu and OpcodeEmulator On Your Machine. Lilu Releases: ht...

www.insanelymac.com

Yes. And Ventura didn't run on our Macs a few months ago. I'm sure OpCodeEmulator would need improvements. Hopefully Devs can figure it out

 

[steve123]

Any news about Pages and import images with 0.6.5 release also wifi continunity camera working in Facetime please test and let me know.

I attempted to import a PDF into Pages running patched Ventura 13.3.1 with OCLP 0.6.5 on Mac Pro 6,1. Crashed.

 

[steve123]

I'm sure OpCodeEmulator would need improvements. Hopefully Devs can figure it out

There was a post today so it does appear to still be active. Unfortunately, there is a Venture issue with libraries:

on old macs without avx2 on ventura cause patch the app not enough - ventura as embedded avx2 checks in some libraries

We need some way to patch the AVX2 check.

 

[steve123]

Patched Ventura 13.3.1 with OCLP 0.6.5 is still using 100% CPU on Core 1 of my Mac Pro 6,1. Does anyone else experience this anomaly?

 

[jgleigh]

Yeah, yesterday afternoon it automatically downloaded and installed without my permission on my MacBook Pro 11,4 when shutting it down, so I got the problem where it would get stuck while booting. But I was able to boot the Pro into Safe Mode, re-patch MacOS using the OCLP 0.6.5 beta, and now it runs just fine, even with the 13.3.1 (a) update still installed.

You probably want to turn off automatic updates to prevent this next time.

 

[TimmuJapan]

Sorry I'm still not smart enough to figure this out, but I was hoping for a "yes" or "no" answer. Will we be able to install 13.4 on pre-Haswell Macs, or is 13.3.1 the last because pre-Haswell Macs are not currently compatible with the security update in the 13.3.1a RSR? Again, is it the act of applying RSRs that requires AVX2, or is it the security update in 13.3.1a that requires AVX2?


Yes. And Ventura didn't run on our Macs a few months ago. I'm sure OpCodeEmulator would need improvements. Hopefully Devs can figure it out

You should watch the latest Mr. Macintosh video about this.

As of right now, pre-haswell macs using OCLP cannot install the RSR.
From what we know right now, when 13.4 comes out, it will have the updates from the RSR bundled within it.
There is no reason to assume right now that pre-haswell macs will NOT be able to update to 13.4 like previous version updates, but we just have to wait and see. It’s always possible that a major change could be introduced that prevents certain OCLP macs from updating, but we don’t need to assume or fear at this moment that because pre-haswell macs can’t install the RSR that it means it is the end of the road for pre-haswell macs on Ventura. ☝🏼