View attachment 2174702I have a problem with update from 13.2.1 to 13.3 beta 4 on Macbook Pro 13“ 11.1 mid. 2014!
After the update and installation of graphic drivers, it only boots up to half and hangs.What can I do!?
..or you create a full usb installer 13.3b3 (found by MrmacIntosh) and install over the broken volume. You will have a running system but no acceleration. You have to wait for 13.3 beta fix for haswell and ivy bridge by the developers.Boot into safe mode and unpatch if you can get into safe mode hopefully you didn’t install on main volume patches are in development again 13.3 but not available or promise it will work yet no official release yet or wipe hard drive and go back to 13.2.1 .
MBP5,2 (Penryn+Nvidia 9400M): same good result.Ventura 13.3 beta 4 is out.
Installation on my MBA 7,2 and mBP 5,1 went fine with latest 0.62n. On mBP 5,1 stage manager and safari issue are still present with latest 0.62n.
Now I am waiting for haswell and ivy bridge fix from the developers for 13.3 betas.
Noticed that the 0.6.2 nightly was updated again, dated 3-17-2023.MBP5,2 (Penryn+Nvidia 9400M): same good result.
KDK handling re-installed KDK (which gets incomplete during 13.3b4 OTA installation) correctly from KDK backup.
Can you play HEVC (H.265) video files (for example videos recorded on the iPhone)?
I tried this and I can’t boot after all. Nothing change nor 13.3 b4 installer + OPCL 0.6.2n patcher using default settings. Do you know if I need to force some settings in the patcher to avoid the bug and boot over my system without wipe it before?..or you create a full usb installer 13.3b3 (found by MrmacIntosh) and install over the broken volume. You will have a running system but no acceleration. You have to wait for 13.3 beta fix for haswell and ivy bridge by the developers.
With that hardware, you will not be able to avoid that bug, but the real question is; Why do you insist on installing the betas? I posted a process you can use to install 13.2.1, (post #4,200)which will work with your Mac Mini. Did you even read that or try to install 13.2.1?I tried this and I can’t boot after all. Nothing change nor 13.3 b4 installer + OPCL 0.6.2n patcher using default settings. Do you know if I need to force some settings in the patcher to avoid the bug and boot over my system without wipe it before?
I solve booting problems using safe mode boot. For get it I press “shift+enter” in the moment of select system boot. Then I could enter system and unpatch it to boot without graphics accelerationI tried this and I can’t boot after all. Nothing change nor 13.3 b4 installer + OPCL 0.6.2n patcher using default settings. Do you know if I need to force some settings in the patcher to avoid the bug and boot over my system without wipe it before?
The whole point of using OCLP is to have Ventura (or Monterey, big Sur) running just as if the hardware was not on the unsupported list. That is, with graphics acceleration. Go back to 13.2.1 to get a usable system. Without graphics acceleration, every little mouse click will take forever, closing a window will make you wait forever, and in general the system is unusable. What you achieved is not success.I solve booting problems using safe mode boot. For get it I press “shift+enter” in the moment of select system boot. Then I could enter system and unpatch it to boot without graphics acceleration
Not problem for now. I have a second system running with 13.2.0 and full hardward graphicsThe whole point of using OCLP is to have Ventura (or Monterey, big Sur) running just as if the hardware was not on the unsupported list. That is, with graphics acceleration. Go back to 13.2.1 to get a usable system. Without graphics acceleration, every little mouse click will take forever, closing a window will make you wait forever, and in general the system is unusable. What you achieved is not success.
Yes, maybe I'm a little hard head, obviously I could back to 13.2.1 if I wipe the SSD and the restore files from backup but it looks more tedious and at the end of the day always there are some tiny aspect that you can recover 100%. My second system has 13.2.1 and by the moment I could waitWith that hardware, you will not be able to avoid that bug, but the real question is; Why do you insist on installing the betas? I posted a process you can use to install 13.2.1, (post #4,200)which will work with your Mac Mini. Did you even read that or try to install 13.2.1?
If you actually have a backup disk, it is very easy to use the migration utility after a clean install of the official release of Ventura 13.2.1. There are no magic settings in the OCLP app that will let you retain your data and still overwrite that borked beta install. You do have your data backed up on another disk, don't you?
Look into the Release Notes... TUI-Mode is no longer available.I could run OCLP 0.6.1 in "TUI" mode but OCLP 0.6.2 is using the same executable for CLI mode. I can --build but when I try to use --disk it runs GUI saying there are no arguments... Am I missing something?
Regarding the non-functional dual-display on my MacMini late 2014 with OS13.2.1 and OCLP0.6.1, I ran a night-build from a couple of days ago and the problem has been resolved, so I can now run HDMI+MiniDP together.Thanks for your input. I'm going to hold off for 0.6.2 and see whether that does the trick. If not, I'll spend a bit of time looking into your suggestion. Luckily, my MacMini isn't my main Mac, so I can live with 1 screen for now.
Appreciate your time with investigating.