Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 13 Ventura on Unsupported Macs Thread

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
After trying to upgrade 2 external partitions running 13.2 to 13.3 beta4 I have found both upgrade OK but upon running OCLP 0.6.2 Mar15 all I get is a bitmap display with a working cursor - no other access. This is on a MacbookPro11,5 - 15” Mid 2015.
Any idea - redo all partitions?
 
Portiere said:
First i again thank all developers. Unfortunately at the moment no way to boot my mac mini L2012 on every 13.3 installation after root patch. I found something to boot them with i thing 70 % acceleration. There are 3 kinds of systems acceleration on unsupported macs. In the first just installed sys info shows 7 MB screen gray dock safari not working, but any other browser works and it is impossible to have custom background. The second, the one i found and use is with 1536 MB screen, monitor used described, gray dock everything works, all resolution displayed, all showed apps in apps folder works flawlessly except Safari. The third is Full one, with traslucent dock bar. I am going to test heavy apps like Final cut Premiere and others, at the moment i am able to play you tube videos also 8K ones, surf with firefox and as i dont work with it i accept it.
Click to expand...
Huh???

I know you're not native, but, at least try to be more specific.
As in, I have no idea what you actually said.
There is no solution (yet) for running 13.3 b3 and onwards on a 2012 Mac Mini, so, what do you mean by these 3 ways of running....erm....what.
 
justperry said:
Huh???

I know you're not native, but, at least try to be more specific.
As in, I have no idea what you actually said.
There is no solution (yet) for running 13.3 b3 and onwards on a 2012 Mac Mini, so, what do you mean by these 3 ways of running....erm....what.
Click to expand...
As just installed on unsupported mac there's no acceleration, grey dock bar, unknown display incorrect vram, impossible custom background, firefox works safari not, all the apps (photo, meteo, wifi, bluetooth etc) start.
If you copy HD4000 kexts in Library/Extensions it works 70% grey dock but all is joined (display name, correct grahic vram, apps etc), safari doesn't work, firefox works, custom background works.
OCLP patch if works, not at the moment, compete functionality.
I am not a developer, there is people playing online with PC/MAC and people like me that, on his risk, plays with his PC/MAC. I have never asked help cause i know the job all dev's are doing. Since early febraury i know that OCLP doesn't patch some machines.
 

Attachments

  • screen.jpg
    screen.jpg
    176.7 KB · Views: 60
SparkX said:
Look into the Release Notes... TUI-Mode is no longer available.
Click to expand...

I did read the release notes. TUI is no longer available as a stand-alone app. You run the GUI with arguments. That's where I got the "--build" and the "-h" (help) arguments and both arguments worked, but the "--disk" argument did not and it does not accept any combination I have tried (not too much documentation on this). I tried "0", "0s1", "disk0", "disk0s1", "/dev/disk0" and "/dev/disk0s1" but it does not recognize the argument "--disk" at all.
 
Hi, guys! Not sure if this is the right thread but...

I'm trying to revive my old Mac mini Early 2009 (mini 3,1) using OCLP 0.6.1 and am seeking advice: I tried Ventura and Monterey, but in both, I can't get to the installer, as the system hangs early on boot.

I tried tweaking some settings in OCLP GUI app to the same early system hang.

Not sure if it matters, but my wi-fi card was upgraded to a MacBook model and I also applied the DOSDude1 firmware patch to support APFS natively in the High Sierra days.
 

Attachments

  • IMG_20230319_203946.jpg
    IMG_20230319_203946.jpg
    370.3 KB · Views: 74
  • Like
Reactions: K two
harlleysathler said:
Hi, guys! Not sure if this is the right thread but...

I'm trying to revive my old Mac mini Early 2009 (mini 3,1) using OCLP 0.6.1 and am seeking advice: I tried Ventura and Monterey, but in both, I can't get to the installer, as the system hangs early on boot.

I tried tweaking some settings in OCLP GUI app to the same early system hang.

Not sure if it matters, but my wi-fi card was upgraded to a MacBook model and I also applied the DOSDude1 firmware patch to support APFS natively in the High Sierra days.
Click to expand...
I have my Mac mini Early 2009 (mini 3,1) using OCLP 0.6.1 running with Monterey. You need a USB 2.0 hub to use your mouse. It took a long time to install 6 or 7 hours.

From OCLP troubleshooting -
A common area for systems to get "stuck", namely for units that are missing the AES CPU instruction/older mobile hardware. During this stage, a lot of heavy cryptography is performed, which can make systems appear to be stuck. In reality they are working quite hard to finish up the installation.

Because this step can take a few hours or more depending on drive speeds, be patient at this stage and do not manually power off or reboot your machine as this will break the installation and require you to reinstall. If you think your system has stalled, press the Caps Lock key. If the light turns on, your system is busy.

#​

 
  • Like
Reactions: K two and perez987
coolio2004 said:
There is no fix atm for haswell and ivy bridge 13.3 betas. i try nearly every day with latest compiled 0.62n.
Click to expand...
I have 13.3 b4 installed successfully on a Haswell iMac 15,1 late 2014, using 0.6.2n latest, so I don't know about that "no fix for haswell with 13.3 betas". Perhaps something is different with the iMac?
 
dcabq said:
I have my Mac mini Early 2009 (mini 3,1) using OCLP 0.6.1 running with Monterey. You need a USB 2.0 hub to use your mouse. It took a long time to install 6 or 7 hours.

From OCLP troubleshooting -
A common area for systems to get "stuck", namely for units that are missing the AES CPU instruction/older mobile hardware. During this stage, a lot of heavy cryptography is performed, which can make systems appear to be stuck. In reality they are working quite hard to finish up the installation.

Because this step can take a few hours or more depending on drive speeds, be patient at this stage and do not manually power off or reboot your machine as this will break the installation and require you to reinstall. If you think your system has stalled, press the Caps Lock key. If the light turns on, your system is busy.

#​

Click to expand...
Hi, @dcabq, thank you for your reply. I'm using an external hard as the installation disc. I already was using a USB 2.0 for the keyboard and mouse when trying Ventura but did not for Monterey. When my system is stuck, I tried the caps lock thing and it didn't turn on, so I believe that the computer crashed. Does this cryptography perform during the boot process? I leave the machine on for a few hours but see no progress. I can, of course, leave it on for some more (much more) time though.
 
  • Like
Reactions: K two
davidlv said:
I have 13.3 b4 installed successfully on a Haswell iMac 15,1 late 2014, using 0.6.2n latest, so I don't know about that "no fix for haswell with 13.3 betas". Perhaps something is different with the iMac?
Click to expand...
Installing 13.3 beta1-4 is not the problem. Post patch causes windowserver crash and boot problem with „some“ haswell and ivy brigde as well known.
 
  • Like
Reactions: perez987, justperry, olad and 2 others
So where can you download 0.6.2 anyway ? On the official site of OCLP only 0.6.1 is available? Is it not officially released yet?
 
Last edited:
  • Like
Reactions: freqrider
harlleysathler said:
Hi, @dcabq, thank you for your reply. I'm using an external hard as the installation disc. I already was using a USB 2.0 for the keyboard and mouse when trying Ventura but did not for Monterey. When my system is stuck, I tried the caps lock thing and it didn't turn on, so I believe that the computer crashed. Does this cryptography perform during the boot process? I leave the machine on for a few hours but see no progress. I can, of course, leave it on for some more (much more) time though.
Click to expand...
Ok, I tried to leave the mini on for about 4 hours. At this time the screen was frozen exactly at the same point (as in the picture in my first post) and the caps lock LED was off, despite I pressed the key hours before. So now I'm sure the computer was stuck. The installer freezes at early boot. Does anyone have any advice?
 
I hear you. If you're not certain it is still chugging away, bite the bullet and start again. What have you go to lose? Another 4 hours? Take the plunge :)
 
Latest 0.6.2 Nightly build fixed HW encode/decode Accel with Polaris GPU on my 3,1! Wifi settings and USB bugs are gone too! Ventura seems to be working perfectly now.
 

Attachments

  • DE9F4B0C-EFFF-4B65-8090-0AA53500DE06.jpeg
    DE9F4B0C-EFFF-4B65-8090-0AA53500DE06.jpeg
    155.6 KB · Views: 94
  • Like
Reactions: perez987
BTW, it looks like a future fix for Ivy Bridge, Haswell and Kepler not booting with macOS Ventura 13.3b1+ now has its own experimental branch:

github.com

sys_patch: Add experimental Metal patches for 3802-based GPUs by khronokernel · Pull Request #1034 · dortania/OpenCore-Legacy-Patcher

Following patches are highly experimental and fragile, this should only be seen as an experiment for internal development. These patches are currently required for boot macOS 13.3 Beta 1 and newer ...
github.com github.com

Sadly, it looks like this is not an ideal solution, as AMFI needs to be disabled (in addition to disabling LV), in order to boot: well, we’ll see if all this (i.e., AMFI + LV disabled) can be alleviated, in the future; for example, this was said originally (source), about Library Validation:

Library Validation and AMFI changes​

With Ventura, our _cs_require_lv patch broke which we rely on to pass our shim'd binaries as allowable in macOS under their security policy. In addition to our patch breaking, Apple has modified the requirements for disabling AMFI outright.

With Ventura, AMFI can no longer be disabled in Safe Mode, as well when CSR_ALLOW_UNTRUSTED_KEXTS is not toggled (we assume this is related to DriverKit). Thus to disable Library Validation and AMFI in general, you'll need:

  • Bit 0x1 flipped in SIP
  • amfi_get_out_of_my_way=0x1 in boot-args
We will be researching what other patches can be used in the future to alleviate this.
 
Last edited:
  • Like
Reactions: freqrider, macinfo, MacRumors3590 and 2 others
Sven G said:
BTW, it looks like a future fix for Ivy Bridge, Haswell and Kepler not booting with macOS Ventura 13.3b1+ now has its own experimental branch:

github.com

sys_patch: Add experimental Metal patches for 3802-based GPUs by khronokernel · Pull Request #1034 · dortania/OpenCore-Legacy-Patcher

Following patches are highly experimental and fragile, this should only be seen as an experiment for internal development. These patches are currently required for boot macOS 13.3 Beta 1 and newer ...
github.com github.com

Sadly, it looks like this is not an ideal solution, as AMFI needs to be disabled (in addition to disabling LV), in order to boot: well, we’ll see if all this (i.e., AMFI + LV disabled) can be alleviated, in the future; for example, this was said originally (source), about Library Validation:

Library Validation and AMFI changes​

With Ventura, our _cs_require_lv patch broke which we rely on to pass our shim'd binaries as allowable in macOS under their security policy. In addition to our patch breaking, Apple has modified the requirements for disabling AMFI outright.

With Ventura, AMFI can no longer be disabled in Safe Mode, as well when CSR_ALLOW_UNTRUSTED_KEXTS is not toggled (we assume this is related to DriverKit). Thus to disable Library Validation and AMFI in general, you'll need:

  • Bit 0x1 flipped in SIP
  • amfi_get_out_of_my_way=0x1 in boot-args
We will be researching what other patches can be used in the future to alleviate this.
Click to expand...
Thanks a lot for your job.
I've tried those fixes but nothing changes.
The partial solution is to copy in L/E standard graphic kexts of related mac Ivy or Haswell, the only unconfortable thing is not traslucent dock bar, in my case.
 
Yes, thanks a lot to the developers (I’m not one of them; just reading the documentation and pointing out some IMHO interesting things: also because I’m for SIP being enabled as much as possible (OCLP “built with security in mind”), which however seems to be rather problematic with Ventura; while with Monterey it was much easier)…! :cool::)

Probably, it’s much better that you/we wait for an official fix, anyway…
 
  • Like
Reactions: sinbad21 and Larsvonhier
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back