macOS 13 Ventura on Unsupported Macs Thread

[alfon_sico]

Yes, you can do it with OCLP in Safe Mode on 13.3 beta. But since you can not log on, I think clean reinstall is your way.

In my case (downgrade from one of problem betas) it was not necessary. But if clean install is all that left...

That’s the clue. While you cannot log in system I only think if there is a way for
- unpatch from other system (could be great if developers aggregate to OCPL patcher
- delete of replace some files to by pass the issue
- boot in safe mode to enter the system bypassing the problem

 

[Tockman]

That’s the clue. While you cannot log in system I only think if there is a way for
- unpatch from other system (could be great if developers aggregate to OCPL patcher
- delete of replace some files to by pass the issue
- boot in safe mode to enter the system bypassing the problem

Alas, no slightest idea how to achieve that :-(

 

[alfon_sico]

Alas, no slightest idea how to achieve that :-(

Do you think that maybe wait till 13.3b4 arise could solve the issue
In the other installations always need to re patch every time, it seems that now, that could be good that it happens, the system doesn't unpatch for itself

 

[Tockman]

Do you think that maybe wait till 13.3b4 arise could solve the issue
In the other installations always need to re patch every time, it seems that now, that could be good that it happens, the system doesn't unpatch for itself

It's a smart move. if you can afford to wait a little, that might help. But, on the other hand, there's always a chance that next beta will keep this bug, let alone some new ones

 

[davidlv]

Do you think that maybe wait till 13.3b4 arise could solve the issue
In the other installations always need to re patch every time, it seems that now, that could be good that it happens, the system doesn't unpatch for itself

You are overthinking this by far...., or as one wise person said, "Too much, by half." (meaning 150%)
On some hardware (I didn't see what your hardware is) you may need to use a wired keyboard and mouse, or even a USB hub. That varies widely, so first try with whatever you have been using.

See Post 3,909 (page 157 in this thread), and download the latest version of OCLP 0.6.2n. (do not build and run from source code, download the GUI using the link halfway down post 3,909)
Use that OCLP app to make a USB installer using Ventura 13.2.1.
DO NOT USE THE BETAS, the KDK files are broken at present.
Boot from the 0.6.2 USB and use Disk Utility to wipe the target disk, GUID partition, APFS.
Then choose the Install Ventura option.
After the install finishes use the Migration tool to restore your data.
Reboot, from the USB, run the root patches.
Reboot, run 0.6.2 again, Build and Install to the internal disk, and reboot
Done

 

[alfon_sico]

It's a smart move. if you can afford to wait a little, that might help. But, on the other hand, there's always a chance that next beta will keep this bug, let alone some new ones

For now I could work launching with my external SSD USB3 plug Ventura macOS

There's so many years that I don't do a fresh install. Is could be able to format System partition and maintain Data partition to get a fresh instalation without loosing personal configs?

 

[Tockman]

For now I could work launching with my external SSD USB3 plug Ventura macOS

There's so many years that I don't do a fresh install. Is could be able to format System partition and maintain Data partition to get a fresh instalation without loosing personal configs?

Never did that so can't suggest, but why not give it a try? Especially for that rainy day I always keep all my data on external disks.

 

[alfon_sico]

Boot from the 0.6.2 USB and use Disk Utility to wipe the target disk, GUID partition, APFS.
Then choose the Install Ventura option.
After the install finishes use the Migration tool to restore your data.

Do you mean that I can wipe "target disk" as "system partition" and later on the system recover the "data partition"? Or are you talking of doing migration of a backup as Carbon Clone or Time Machine?

 

[alfon_sico]

Never did that so can't suggest, but why not give it a try? Especially for that rainy day I always keep all my data on external disks.

I have a backup do it before I launched to the cliff yesterday ;-) I am a risky boy but not so much. Anyway I would like save the original data, you never know if the backup without mistakes or something goes wrong in the last moment. Any way if there is not other chance I wipe system and do a fresh installation

Thanks for the interest

 

[davidlv]

Do you mean that I can wipe "target disk" as "system partition" and later on the system recover the "data partition"? Or are you talking of doing migration of a backup as Carbon Clone or Time Machine?

There you go again... too much by 3/4.
"Wipe the disk" means wipe the whole internal disk.
Use a CCC backup or a Time machine backup in the Migration process.
Just be sure you have a good backup disk (I always have at least 3).

BTW, OCLP 0.6.2n has been updated today, 3-12-2023.

 

[osxfr33k]

Is there a way to install the OCLP root patching from a different Mac model? I have a Macpro3,1 with rEFIplus and OpenCore dual boot mode. I installed Ventura on my MacBookPro11,3 with the internal drive and did the root patching with it. Then plugged in a SSD using a Seagate SSD to thunderbolt and installed another instance of Ventura on that. I can’t seem to boot that install when I place that SSD into the MacPro3,1 it starts to boot hangs then reboots after some time. It’s starting to look like the only way you can apply the root patching is while the MacOS is loaded on the device and it will automatically choose the Mac model outside of the OCLP even if I go to OCLP settings and change the model, it still wants to root patch with the actual model that is loaded and can’t seem to overwrite this action in anyway?

 

[osxfr33k]

There you go again... too much by 3/4.
"Wipe the disk" means wipe the whole internal disk.
Use a CCC backup or a Time machine backup in the Migration process.
Just be sure you have a good backup disk (I always have at least 3).

BTW, OCLP 0.6.2n has been updated today, 3-12-2023.

I there a way to get a copy without compiling one?

Never-mind its on the site

 

[davidlv]

Is there a way to install the OCLP root patching from a different Mac model? I have a Macpro3,1 with rEFIplus and OpenCore dual boot mode. I installed Ventura on my MacBookPro11,3 with the internal drive and did the root patching with it. Then plugged in a SSD using a Seagate SSD to thunderbolt and installed another instance of Ventura on that. I can’t seem to boot that install when I place that SSD into the MacPro3,1 it starts to boot hangs then reboots after some time. It’s starting to look like the only way you can apply the root patching is while the MacOS is loaded on the device and it will automatically choose the Mac model outside of the OCLP even if I go to OCLP settings and change the model, it still wants to root patch with the actual model that is loaded and can’t seem to overwrite this action in anyway?

When you run OCLP to make an Installer USB, look at the setting menu. There you can specify the Mac the USB will be used with. The Developer Menu also can be tweaked, to lengthen the period before time out in the Boot Picker. The default is 5 seconds which can be too short sometimes. That setting is good for one time only as it will revert to the default once you quit the app.
Of course, the root patches have to be done on the target disk, either internal or external disk, not the USB disk.
But the USB disk should work booting up the MacPro 3,1 if you make the USB on another Mac and specify the MacPro in the settings menu. So booted from the internal disk, connect the Seagate SSD, run the OCLP app, specify the MacPro and run the Build and install, pointing the write to disk at the EFI partition on the Seagate. Once the MacPro boots from the Seagate, run the OCLP again and run the root patches.
You only need one install of the EFI, so the EFI partition on the internal disk is enough.

 

[justperry]

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

Nope, you've got that wrong, it's a hack to have more RAM allocated to Graphics.

 

[justperry]

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.

They are not empty, just not showing contant, PDF will show up, as with some sites, but yes...most are not displayed.
If there's a window in front of Safari, all content IS displayed, a window like "About This Mac"

 

[Tockman]

I've got third kernel panic for the last three days. Maybe someone of developers would see the reason.

panic(cpu 2 caller 0xffffff8023d485f3): Kernel trap at 0xffffff8023d26ccc, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x00000001120d5000, CR3: 0x0000000028174000, CR4: 0x00000000001626e0
RAX: 0xfffffff0beca9ea0, RBX: 0xfffffeb4e47f8340, RCX: 0x00000000002e3f5e, RDX: 0x80000002e3f5e047
RSP: 0xffffffc0fad4be00, RBP: 0xffffffc0fad4be80, RSI: 0xffffffffffffffdf, RDI: 0xffffff95a6688280
R8:  0x000ffffffffff000, R9:  0xfffffeb4e47f8340, R10: 0x000000008030b97b, R11: 0xffffff8033d0d9f8
R12: 0x0000000000000020, R13: 0xbffffff0b19aebc0, R14: 0x00000000002e3f5e, R15: 0xfffffff0b19aebc0
RFL: 0x0000000000010202, RIP: 0xffffff8023d26ccc, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00000001120d5000, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 1, VF: 0

Panicked task 0xffffff90db874208: 240 threads: pid 0: kernel_task
Backtrace (CPU 2), panicked thread: 0xffffff95a7982b30, Frame : Return Address
0xffffff802390d1a0 : 0xffffff8023beb38d mach_kernel : _handle_debugger_trap + 0x4ad
0xffffff802390d1f0 : 0xffffff8023d58ed6 mach_kernel : _kdp_i386_trap + 0x116
0xffffff802390d230 : 0xffffff8023d48120 mach_kernel : _kernel_trap + 0x3e0
0xffffff802390d280 : 0xffffff8023b85951 mach_kernel : _return_from_trap + 0xc1
0xffffff802390d2a0 : 0xffffff8023beb66d mach_kernel : _DebuggerTrapWithState + 0x5d
0xffffff802390d390 : 0xffffff8023bead19 mach_kernel : _panic_trap_to_debugger + 0x1a9
0xffffff802390d3f0 : 0xffffff80243e072b mach_kernel : _panic + 0x84
0xffffff802390d4e0 : 0xffffff8023d485f3 mach_kernel : _sync_iss_to_iks + 0x2c3
0xffffff802390d660 : 0xffffff8023d482e2 mach_kernel : _kernel_trap + 0x5a2
0xffffff802390d6b0 : 0xffffff8023b85951 mach_kernel : _return_from_trap + 0xc1
0xffffff802390d6d0 : 0xffffff8023d26ccc mach_kernel : _phys_attribute_clear + 0x15c
0xffffffc0fad4be80 : 0xffffff8023cce890 mach_kernel : _vm_page_balance_inactive + 0xd0
0xffffffc0fad4beb0 : 0xffffff8023ce54ed mach_kernel : _vm_page_activate + 0x12d
0xffffffc0fad4bee0 : 0xffffff8023cd02aa mach_kernel : _vm_pageout_scan + 0x19ea
0xffffffc0fad4bf80 : 0xffffff8023cd12c6 mach_kernel : _vm_pageout_continue + 0x36
0xffffffc0fad4bfa0 : 0xffffff8023b8519e mach_kernel : _call_continuation + 0x2e

Process name corresponding to current thread (0xffffff95a7982b30): kernel_task
Boot args: keepsyms=1 debug=0x100 ipc_control_port_options=0 -nokcmismatchpanic -v

Mac OS version:
22D68

Kernel version:
Darwin Kernel Version 22.3.0: Mon Jan 30 20:42:11 PST 2023; root:xnu-8792.81.3~2/RELEASE_X86_64
Kernel UUID: 10E5D254-4A37-3A2A-B560-E6956A093ADE
roots installed: 0
KernelCache slide: 0x0000000023800000
KernelCache base:  0xffffff8023a00000
Kernel slide:      0x00000000238dc000
Kernel text base:  0xffffff8023adc000
__HIB  text base: 0xffffff8023900000
System model name: iMac13,2 (Mac-FC02E91DDD3FA6A4)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 69193079580818
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00003eee44edfeb6
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x0000000fd4d6072c 0x0000000000000000
Compressor Info: 2% of compressed pages limit (OK) and 1% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
  Zone map: 0xffffff80d9793000 - 0xffffffa0d9793000
  . PGZ   : 0xffffff80d9793000 - 0xffffff80dd794000
  . VM    : 0xffffff80dd794000 - 0xffffff85a9ac7000
  . RO    : 0xffffff85a9ac7000 - 0xffffff874312d000
  . GEN0  : 0xffffff874312d000 - 0xffffff8c0f460000
  . GEN1  : 0xffffff8c0f460000 - 0xffffff90db793000
  . GEN2  : 0xffffff90db793000 - 0xffffff95a7ac6000
  . GEN3  : 0xffffff95a7ac6000 - 0xffffff9a73df9000
  . DATA  : 0xffffff9a73df9000 - 0xffffffa0d9793000
  Metadata: 0xffffff8047783000 - 0xffffff8067783000
  Bitmaps : 0xffffff8067783000 - 0xffffff8073783000

 

[philippemarques]

I've got third kernel panic for the last three days. Maybe someone of developers would see the reason.

Mac OS version:
22D68

Kernel version:
Darwin Kernel Version 22.3.0: Mon Jan 30 20:42:11 PST 2023; root:xnu-8792.81.3~2/RELEASE_X86_64
Kernel UUID: 10E5D254-4A37-3A2A-B560-E6956A093ADE

Try to update to a new revision? It's difficult to say what happened with this log, the problem was before the trap.
A kernel panic, is ofen the injection of a bad kernel driver. KDK problem ?

 

[Tockman]

Try to update to a new revision? It's difficult to say what happened with this log, the problem was before the trap.
A kernel panic, is ofen the injection of a bad kernel driver. KDK problem ?

You know, my system works since January, 24 with no problems. Just the last three days. I guess, it's a little late for KDK problem revealing.

 

[coolio2004]

I there a way to get a copy without compiling one?

Never-mind its on the site

wow- latest self compiled build supports now…

• Implement Continuity Camera Unlocking for pre-Kaby Lake CPUs
  • Applicable for all legacy Macs in macOS Ventura
• but no notice about fix for 13.3 beta.

Works fine with my iPhone XR. Thanx to the developers for their hard work.

 

[TOM1211]

wow- latest self compiled build supports now…

• Implement Continuity Camera Unlocking for pre-Kaby Lake CPUs
  • Applicable for all legacy Macs in macOS Ventura
• but no notice about fix for 13.3 beta.

Works fine with my iPhone XR. Thanx to the developers for their hard work.

Continuity Camera Unlocking impressive OCLP devs got this working on macs where the webcam really is shockingly bad again amazing work to have pulled this off and the other massive amount of updates that have been committed recently.

 

[davidlv]

Continuity Camera Unlocking impressive OCLP devs got this working on macs where the webcam really is shockingly bad again amazing work to have pulled this off and the other massive amount of updates that have been committed recently.

Another nightly update to 0.6.2 has be published Dated 3-13-2023. Several changes, but not sure what. In any case, I am sure it is for the better!

 

[vince22]

Continuity Camera Unlocking impressive OCLP devs got this working on macs where the webcam really is shockingly bad again amazing work to have pulled this off and the other massive amount of updates that have been committed recently.

thanks to all devs, i can confirmed its finally working latest OCLP 0.62n continuity Camera with my iPhone 14 Pro Max 12MP front facing camera paired with 2015 13" MBP (12,1) say goodbye to 720p MacBook pro camera.

 

[osxfr33k]

I have all original components working using OCLP v0.6.2N on Ventura. I can't figure out how to enable the original Bluetooth card, I think it should be working with all these new drivers OCLP has enabled in kernel section of config. Thanks to the developers for a masterful release. I also use rEFIndPlus to boot Catalina and Ventura. It must be some hardware issue with my BT card because its the same issue in Catalina with Dosdude1 Patcher.

 

[davidlv]

I have all original components working using OCLP v0.6.2N on Ventura. I can't figure out how to enable the original Bluetooth card, I think it should be working with all these new drivers OCLP has enabled in kernel section of config. Thanks to the developers for a masterful release. I also use rEFIndPlus to boot Catalina and Ventura. It must be some hardware issue with my BT card because its the same issue in Catalina with Dosdude1 Patcher.

Original components of what?
You could give us the curtesy of listing your hardware so readers can understand your post and reply appropriately.
Or perhaps list that hardware in your signature? If I had to guess, do you have a cMP from 2010?

 

[osxfr33k]

Original components of what?
You could give us the curtesy of listing your hardware so readers can understand your post and reply appropriately.
Or perhaps list that hardware in your signature? If I had to guess, do you have a cMP from 2010?

Updated Signature