macOS 13 Ventura on Unsupported Macs Thread

[HowowcanIgo]

It doesn't show in the menu bar on top as standard. You have to add that in on of the settingspanes.
I do think all WiFi networks in the area remain visible there, but I'm no sure and can't check at the moment.

 

[Sven G]

I just discovered that, as in Monterey, you can reenable file system protection also in Ventura and successfully boot (of course, only after having done the root patching, which always requires an unrestricted filesystem; and this must then be reenabled at every new root patching: easy to forget, but definitely doable), thus setting SIP to 0x801 instead of 0x803: a little more security, but only for advanced users (don’t try this if you don’t understand what is going to be done!) - a good thing, anyway…

EDIT (IMPORTANT!): After some testing, it looks like WindowServer tends to crash and Safari/Mail/HelpViewer have problems loading content, with the SIP setting above: so, sadly, it is not yet possible to disable unrestricted file system without problems (you can boot, but then some things won’t work), in Ventura - maybe this will improve, who knows…

 

[reneroeten]

It doesn't show in the menu bar on top as standard. You have to add that in on of the settingspanes.
I do think all WiFi networks in the area remain visible there, but I'm no sure and can't check at the moment.

thx man, found it

 

[Sven G]

… Now, if only it were possible to reenable library validation in the future, Ventura could potentially be as secure as Monterey, with SIP fully enabled and only SSV disabled (today, this is not yet possible, as the previous library validation patches broke in Ventura and haven’t yet been reimplemented; if even possible to do it: let’s hope for a solution) - just some ideas for the future (don’t reenable library validation now, as this would break your installation!)…

EDIT (IMPORTANT!): After some testing, it looks like WindowServer tends to crash and Safari/Mail/HelpViewer have problems loading content, with the SIP setting in the previous post: so, sadly, it is not yet possible to disable unrestricted file system without problems (you can boot, but then some things won’t work), in Ventura - maybe this will improve, who knows…

 

[internetzel]

Is your Ventura OS on an external SSD via USB port? If this is the case, I am having the same issue: All external USB devices become inactive after installing the root patches (followed by a reboot) for my iMac10,1.
I am not planning to install Ventura to the internal SSD/HDD (500GB + 500GB fusion drive running dosdude1 Catalina). I've ordered an OWC FireWire port external SSD/HDD case in the hope to get Ventura working via the FireWire port because I suspect the USB 1.1 root patch temporarily (best case scenario) disables all external USB ports at the beginning of the boot up process. The question is that if the FireWire port can be used to boot up Ventura?

Haven't tried in Ventura or Monterey yet, but since Catalina the FireWire booting capability needs to be enabled in the OCLP settings, so the Mojave versions of the FireWire kexts are injected by OpenCore (in fact force injecting the currently installed versions of those kexts should suffice since the problem is only an attribute in the Info.plist file inside the kext).

 

[rodrigomarrafao]

Besides all the app crashing using the arrow keys etc., which I suffer from a lot with my rMBP mid-2012, I've also been experiencing bad keys (JKR). While it sounds like a faulty keyboard, I'm still able to use the keys, but need to hold them down for a very long time before the character appears. Is there any chance this is related to the OCLP Ventura patching? It was working fine before I upgraded from Monterey.
Anyone else experiencing this?

Having the shortcut problem and arrows too. Any fix for that? MacBook Pro Retina 2012 and MacBook Air 2012.

 

[macpro_mid2014]

… Now, if only it were possible to reenable library validation in the future, Ventura could potentially be as secure as Monterey, with SIP fully enabled and only SSV disabled (today, this is not yet possible, as the previous library validation patches broke in Ventura and haven’t yet been reimplemented; if even possible to do it: let’s hope for a solution) - just some ideas for the future (don’t reenable library validation now, as this would break your installation!)…

Hi Sven,

Unfortunately, WindowServer crashes a lot on my MBP. I had to put FS back in as in the default OCLP config (0x803). But thanks for trying...

 

[Sven G]

Hi Sven,

Unfortunately, WindowServer crashes a lot on my MBP. I had to put FS back in as the default OCLP config. But thanks for trying...

Yes, I just discovered that, too (see my edited posts above): sadly, it’s looks like it’s still too early for more extensive SIP enabling…

 

[Sven G]

… So, now, one of the questions is: why do WindowServer and other programs need an unrestricted filesystem in OCLP’d Ventura…? Perhaps it’s tied to the current need to disable Library Validation, too? Hmmm, who knows…

 

[cdf]

I don't have HW accel with Ventura on my 3,1 w RX580? I installed the KDK root patches. I also tried manually installing Mousse4.2.kext and rebuilt kext cache. Kext is loaded but still no HW accel? Do I need to build OCLP spoofing a different machine?

According to the documentation, hardware encode/decode is nonfunctional with Polaris in machines lacking AVX. See Known Issues and the additional notes in

Legacy Metal Graphics Support and macOS Ventura - Sequoia · Issue #1008 · dortania/OpenCore-Legacy-Patcher

With the forth coming release of OpenCore Legacy Patcher v0.5.0, systems with legacy Metal GPUs will finally be able to achieve graphics acceleration in macOS Ventura! Reminder: These patches are s...

github.com

 

[Dilli]

I have moved back to BigSur which is very stable for my Machine MacBook Air 2011 model 4,2.
Both Monterey & Ventura is a bit too heavy for this old 4gb ram machine. and lagging.
Had many crashes with Monterey where all wifi, bluetooth & System preference pane just did not show or work.
It was a good test having it previously but many metal apps not working just was not my cup of tea. Cheers

 

[steverae]

Having the shortcut problem and arrows too. Any fix for that? MacBook Pro Retina 2012 and MacBook Air 2012.

Nope, booting from the internal SSD with the same efi patches installed on there.

Further info though, booted the iMac in verbose mode and here is the output

It just sits there forever ??? Really annoying as so close but no cigar.

 

[steverae]

Might have to go back to Monterey on this for a while longer, had no issues with that

 

[murdock1234]

Having the shortcut problem and arrows too. Any fix for that? MacBook Pro Retina 2012 and MacBook Air 2012.

Yes, you have to disable "Feature Unlock" to fix the app crash.

 

[coasterOneEightThree]

For all MacPro 3,1 owners who still have an optical PATA drive installed and now cannot use it with Ventura:

I got a new DVD-R/W drive with SATA interface for $20.

The great thing is that this MacPro has two unused SATA ports under the front fan unit on the mainboard. Since you can use the installed power cable for PATA with a Molex to SATA adapter, all you really need to do in addition is run a SATA data cable into the optical drive area.

Here is a very good video on how to get to these ports -> ...

The required SATA data cable should be plugged into the motherboard with the angled connector, because the straight connector on the other side is too high for the space under the front ventilation unit.

To route the cable into the optical drive area, you can temporarily unscrew the SATA connector from Bay 1 to route the cable through the space behind it to the optical drive. Make sure the way up is as short as possible, as every millimeter counts to be able to connect the drive. My cable is 50 centimeters long (about 20 Inches).

In any case, the new drive works here. I have ripped an old CD already - excellent!

Hope this helps someone ...

 

[rodrigomarrafao]

Besides all the app crashing using the arrow keys etc., which I suffer from a lot with my rMBP mid-2012, I've also been experiencing bad keys (JKR). While it sounds like a faulty keyboard, I'm still able to use the keys, but need to hold them down for a very long time before the character appears. Is there any chance this is related to the OCLP Ventura patching? It was working fine before I upgraded from Monterey.
Anyone else experiencing this?

Resolved here applying patches again, rebuilt open core, smc and pram reset. Was happening both on rMPB mid 2012 and on MacBook Air 13'' 2012.

 

[VintageMacGS]

I decided to try the OCLP on my 2012 Mac Mini to see how it would work even though I'm fine with Catalina but concerned about future security updates etc. First results look fine and no major problems with the process. I installed to an external Samsung T7 USB SSD using a USB flash drive installer plugged directly into the Mini as I didn't want to change any of my other USB drives or internal drives. I first cloned my Catalina startup partition using CCC to the Samsung and upgraded to Ventura 13.2 that way using OCLP.

Issues I've noticed so far is that accessing information on hard drives with many folders is a bit slow such as iTunes folders with thousands of tracks. This is for internal and external drives. My firewire drives are recognized. I have two USB high speed hubs so that may be one problem but previously was not. I like to use iTunes 10.7 CoverFlow installed with Retroactive and it still works but when going to change something like a genre before importing a CD, clicking OK causes iTunes to quit while pressing Enter to select the choice works fine. Some preferences like disabling the iTunes store cause the app to quit but are set when launching again but these are minor issues. I'm glad to see that my AIFF files now show the art thumbnail in the Finder instead of a generic icon like in Catalina.

Thanks to the developers and those here who are posting their results. OCLP is a great way to extend the life of perfectly usable computers for many tasks.

 

[houser]

Just a comment that OCLP 0.6.1 caused crashes here on my rMBP 10,1 but not on MBA 3,2 mostly when loading the desktop after boot, and also some crashing in Photos and with image handling. To black screen. Unresponsive keyboard. I suspect something with graphics switching. Trying the Switch utility to see if discrete or integrated may help.
Fixed on the rMBP by downgrading to 0.5.3 for now. FWIW. I have a crash log file if someone wants/needs it.
I had stable performance for a few days after 0.6.1 was released and then it started crashing today.
Can not pin down any other change.

 

[TigerA]

Haven't tried in Ventura or Monterey yet, but since Catalina the FireWire booting capability needs to be enabled in the OCLP settings, so the Mojave versions of the FireWire kexts are injected by OpenCore (in fact force injecting the currently installed versions of those kexts should suffice since the problem is only an attribute in the Info.plist file inside the kext).

Thx for the help. Which attribute in the FireWire kext Info.plist may need to be modified, and to what value? Or is it enough by ticking the FireWire Boot option in OCLP build? Furthermore, I tried to replace the AppleUSBLegacyHub.kext with the default AppleUSBHub.kext in Ventura recovery mode (kextunload and kextload were successful but kmutil install --update-all --force --volume-root /Volumes/Ventura failed (asking for KDK which was not installed at the time), not sure if it is necessary to run the kmutil install command?) but did not succeed: The root patched Ventura still failed at the very beginning of the boot process caused by inactive external USB ports. I suspect this AppleUSBLegacyHub.kext may be the cause.
Update-1: Installed 13.2 KDK and applied root patch again and failed boot again. Booted to recovery trying to unload the AppleUSBLegacyHub.kext but it disappeared in /System/Library/Extensions/IOUSBFamily.kext/Contents/Plugins. The AppleUSBHub.kext is there instead.
Update-2: Had a closer look of the AppleUSBHub.kext and can't tell if it is from the 12.6.2. Please see the attached file for details.
Any suggestions?

 

[deeveedee]

For as long as I have been running macOS on my unsupported MBP6,2, I have been using boot-arg amfi_get_out_of_my_way=1. I noticed that Open Core Legacy Patcher is using boot-arg amfi=0x80 to partially disable AMFI for my rig. Does anyone know where I can find documentation on the amfi=0x80 boot-arg? Thank you.

 

[internetzel]

Thx for the help. Which attribute in the FireWire kext Info.plist may need to be modified, and to what value? Or is it enough by ticking the FireWire Boot option in OCLP build?

Just ticking the option and reinstalling OCLP to the EFI partition is enough in order to get FireWire booting to work again - although the Catalina and later OS installer and updates will refuse to install as long as the target drive is connected via FireWire, so unfortunately you'd need to connect the drive via something else like USB for those tasks.

 

[steverae]

Thx for the help. Which attribute in the FireWire kext Info.plist may need to be modified, and to what value? Or is it enough by ticking the FireWire Boot option in OCLP build? Furthermore, I tried to replace the AppleUSBLegacyHub.kext with the default AppleUSBHub.kext in Ventura recovery mode (kextunload and kextload were successful but kmutil install --update-all --force --volume-root /Volumes/Ventura failed (asking for KDK which was not installed at the time), not sure if it is necessary to run the kmutil install command?) but did not succeed: The root patched Ventura still failed at the very beginning of the boot process caused by inactive external USB ports. I suspect this AppleUSBLegacyHub.kext may be the cause.
Update-1: Installed 13.2 KDK and applied root patch again and failed boot again. Booted to recovery trying to unload the AppleUSBLegacyHub.kext but it disappeared in /System/Library/Extensions/IOUSBFamily.kext/Contents/Plugins. The AppleUSBHub.kext is there instead.
Update-2: Had a closer look of the AppleUSBHub.kext and can't tell if it is from the 12.6.2. Please see the attached file for details.
Any suggestions?

Interesting find re the usb ports, I’m having the exact ssme issue on my 10,1 2009 iMac after installing root patches.

In fact I can’t seem to get past this point now know matter what I try.

After completing install, just sticks at loading screen, Ive posted the verbose screenshot earlier, but here it is again incase it can shed some light

 

[TigerA]

Interesting find re the usb ports, I’m having the exact ssme issue on my 10,1 2009 iMac after installing root patches.

Is it possible for you to install Ventura to an internal HDD/SSD, or it has already been installed in an internal SSD?
P.S. If you still have the original ODD in your iMac10,1, you can swap this out with a SSD (requires an adaptor/caddy).
Update: Had a look of my verbose output and it failed at the same spot as yours.

 

[maclancer]

Is your Ventura OS on an external SSD via USB port? If this is the case, I am having the same issue: All external USB devices become inactive after installing the root patches (followed by a reboot) for my iMac10,1.
I am not planning to install Ventura to the internal SSD/HDD (500GB + 500GB fusion drive running dosdude1 Catalina). I've ordered an OWC FireWire port external SSD/HDD case in the hope to get Ventura working via the FireWire port because I suspect the USB 1.1 root patch temporarily (best case scenario) disables all external USB ports at the beginning of the boot up process. The question is that if the FireWire port can be used to boot up Ventura?

I personally had bad luck with thumb drives. After installing a SSD inside my MacPro. Ventura was finally installed. I did made the mistake of upgrading from Monterey but with an old version of OCLP and that drive became unresponsive. So I have to wipe everything from scratch.

 

[TigerA]

I personally had bad luck with thumb drives.

for the Ventura installer?

After installing a SSD inside my MacPro

for the actual Ventura macOS?

I did made the mistake of upgrading from Monterey but with an old version of OCLP and that drive became unresponsive.

I did a clean install to a partition on an external Samsung T5 SSD with OCLP 0.6.1 / 0.6.2N. I am writing this post with this unpatched iMac10,1 running 13.2.