macOS 13 Ventura on Unsupported Macs Thread

[roysterdoyster]

@hvds You can go to /private/var/folders/zz and delete the largest size folder or file. This is the update file downloaded OTA. Cheers

This may or may not be the case, in my case it was not.

 

[Dilli]

Tried that, resulted in a "Permissions error". Tried to set the permissions and can't get access to anything in /private, SIP related? Suggestions?

I got success and deleted file and got 11gb of my space back without permission errors popping up. Perhaps its different for every machine I dont know

 

[hvds]

@hvds You can go to /private/var/folders/zz and delete the largest size folder or file. This is the update file downloaded OTA. Cheers

Thanks, I'll try next time when using OTA, after loading and preparing, but before letting it restart.
I do see the files with terminal ls -la /private/var/folders/zz but it seems some are gone after installation finishes.

 

[robocatx]

there is some setting in open patcher core LIBRARY HEART OF OCLP not patcher probably you dont have the latest library which is version 0.9.1 once that is in you efi and you are admin you are good to go

I have the exact same issue. Unfortunately your response is not understandable to me. Could you explain in more detail how to fix the issue where the root patches fail with the error message "Could not use 'com.nvidia.web.GeForceWeb' because: ..."

 

[luckyduke23]

Hello, I don't use firevault, so I don't know how do it work. I think it is a high level of security, I don't need it and I thing it's not a good idea to add this with our old Imac an OCPL.. I will create a youtub to explain my config and how to do it.

I meanwhile created a second encrypted volume (FileVault) in same container and installed the latest version of MacOS and OCLP on it. As I can there access my regular volume via Finder I can use the test volume with my data and applications to check latest updates before applying them to my regular volume. So thanks again for your inspiration.

 

[chris1111]

New Themes Flavours-Ventura13 is add on Github repos with all Background for every screens.

Enjoy! 👍

 

[rdfincher]

I've successfully installed Ventura 13.3.1 on a MacBook Pro 8.2 and a 27 in iMac 17.1, using OCLP v 0.6.4. Both machines are working well on apps like Mail, Safari, Pages, Calendar and Zoom.

I'm totally in awe of the work done by Dortania and all the other developers who have got OCLP running so well.
However, there's a bigger issue that I'm only just discovering, sufficiently serious to warrant a WARNING on this thread.

I imagine many users like myself have been so impressed with Ventura on their unsupported Macs, that they have relegated earlier macOS versions to their scrapheap, secure in the knowledge that Ventura has become their preferred macOS. And without checking whether their favourite apps still work correctly. And there are only a few posts here by users saying that all their apps are working well to support such relegation.

So beware that the following non-exhaustive list of apps may not work for you: Keynote, Maps, Photobooth, Apple TV shows, GarageBand and iMovie. Ironically iMovie works on the MBP but not on the 27 in iMac, whereas Photobooth works correctly on the iMac but not on the MBP. Garage Band doesn't work on the MBP, and displays a warning that the app can't initialise Graphics because the computer is unsupported.

So make sure your preferred apps still work before you discard an earlier version of macOS which previously supported these apps!

If there are other users here who have had problems with these apps, then please let us know. And of course if others have found ways to get these apps eventually to work, then likewise. For me Keynote not working is a deal breaker, and may force a retreat to Monterey 12.6.5?

 

[roysterdoyster]

MBP4,1 17-inch (Early 2008) successfully updated from Monterey 12.6.5 to Ventura 13.3.1 via OCLP 0.6.5n.

Many thanks to the developer, and special thanks to Larsvonhier for his great advice!

Issue#1:
When lid is closed for some time, a kernel panic occurs and the machine has to be powered-off by pressing the on/off key for 5secs.

Issue#2:
Stage Manager isn't working

 

[roysterdoyster]

Does someone know ho to get rid of the new menu item for Ethernet controller etc. on/off? No need nor want for that.
Temporarily it can be removed from the menu bar, after Restart it reappears, which is annoying.
Tip anyone?

 

[adrianlondon]

For me Keynote not working is a deal breaker, and may force a retreat to Monterey 12.6.5?

Keynote is working well for me. Have you tried a re-install of that app? I didn't install it directly but migrated it (using the "migration assistant") from my other laptop.

I was surprised it worked as I installed Ventura 13.3 on my old Pro and it migrated everything from my 13.4 beta install on my Air.

I believe I have it easy, as the late-2013 15" MBP with the Intel Iris Pro doesn't cause many issues for OCLP.

 

[educovas]

I've successfully installed Ventura 13.3.1 on a MacBook Pro 8.2 and a 27 in iMac 17.1, using OCLP v 0.6.4. Both machines are working well on apps like Mail, Safari, Pages, Calendar and Zoom.

I'm totally in awe of the work done by Dortania and all the other developers who have got OCLP running so well.
However, there's a bigger issue that I'm only just discovering, sufficiently serious to warrant a WARNING on this thread.

I imagine many users like myself have been so impressed with Ventura on their unsupported Macs, that they have relegated earlier macOS versions to their scrapheap, secure in the knowledge that Ventura has become their preferred macOS. And without checking whether their favourite apps still work correctly. And there are only a few posts here by users saying that all their apps are working well to support such relegation.

So beware that the following non-exhaustive list of apps may not work for you: Keynote, Maps, Photobooth, Apple TV shows, GarageBand and iMovie. Ironically iMovie works on the MBP but not on the 27 in iMac, whereas Photobooth works correctly on the iMac but not on the MBP. Garage Band doesn't work on the MBP, and displays a warning that the app can't initialise Graphics because the computer is unsupported.

So make sure your preferred apps still work before you discard an earlier version of macOS which previously supported these apps!

If there are other users here who have had problems with these apps, then please let us know. And of course if others have found ways to get these apps eventually to work, then likewise. For me Keynote not working is a deal breaker, and may force a retreat to Monterey 12.6.5?

Since your MacBook is a non-Metal machine, apps that require the metal API or DRM will never work but older versions that did not require Metal should work.

On your iMac, you might have some issues with apps that require DRM or VA that we couldn't find a proper fix yet so if you need those apps, going back to Monterey is your best option for now

 

[educovas]

MBP4,1 17-inch (Early 2008) successfully updated from Monterey 12.6.5 to Ventura 13.3.1 via OCLP 0.6.5n.

Many thanks to the developer, and special thanks to Larsvonhier for his great advice!

Issue#1:
When lid is closed for some time, a kernel panic occurs and the machine has to be powered-off by pressing the on/off key for 5secs.

Issue#2:
Stage Manager isn't working

Stage manager is not supported on non-Metal machines. The wake from sleep panic is a known issue on Nvidia Tesla 1.0 GPUs running MacOS Ventura. Monterey should work without this problem

 

[roysterdoyster]

(...) The wake from sleep panic is a known issue on Nvidia Tesla 1.0 GPUs running MacOS Ventura. Monterey should work without this problem

Indeed, I did not encounter the problem in Monterey.

Do you know of a solution in Ventura?

Hibernation workaround in OCLP Settings does not work on MBP4,1.

At present I'm running with Terminal cmd

sudo pmset -a hibernatemode 25

strictly as a precaution against system and file damages.

 

[educovas]

Indeed, I did not encounter the problem in Monterey.

Do you know of a solution in Ventura?

Hibernation workaround in OCLP Settings does not work on MBP4,1.

At present I'm running with Terminal cmd

sudo pmset -a hibernatemode 25

strictly as a precaution against system and file damages.

The problem appears to be between the old graphics driver and the kernel so it's something very difficult to fix

The only workaround would be to completely disable sleep which is not a good idea for a laptop

 

[davidlv]

Indeed, I did not encounter the problem in Monterey.

Do you know of a solution in Ventura?

Hibernation workaround in OCLP Settings does not work on MBP4,1.

At present I'm running with Terminal cmd

sudo pmset -a hibernatemode 25

strictly as a precaution against system and file damages.

Quite a while ago, I found a through explanation of the sleep commands at

macOSã®å¯ç¸ã«ã¤ãã¦èããã㨠-- `pmset` - ã°ãããã ã

é»æºã¾ããã®è¨å®ï¼ åãããä½ã¨ãªãæ°ã«ãªã£ã¦ãã¦ï¼ãªãä½æãããããªãï¼åæ¥ã触ãã¾ãããï¼ãã·ã³ã®æ°èª¿ãã£ããã§ï¼ãã®è¾ºãæ´çãã¦ãããï¼ã¨æã£ãããã§ãï¼ å¿è«"ããã¾ã§èªåã¬ãã«"ã§æµãð ã¤ãï¼ã¹ãªã¼ãï¼ããããããªãï¼ å¾ã§è§¦ããããã¨ã¯æã£ã¦ããã®ã§ããï¼ãã¾ãã¡ã¹ãã¨å¥ã£ã¦ããªããã§ãããï¼ æãã«ï¼"ä½å¦ãåãããªãã®ãï¼ãï¼åãã£ã¦ããªã"ï¼...

baqamore.hatenablog.com

Unfortunately, it is in Japanese. As I can read Japanese, that wasn't an issue for me, but you may need to try a translation yourself.
The short suggestion, try
sudo pmset -a hibernatemode 0

Hibernation usage:
hibernatemode = 0 (binary 0000) by default on supported desktops. The system will not back memory up to persistent storage. The system must wake from the contents of memory; the system will lose context on power loss. This is, historically, plain old sleep.
hibernatemode = 3 (binary 0011) by default on supported portables. The system will store a copy of memory to persistent storage (the disk), and will power memory during sleep. The system will wake from memory, unless a power loss forces it to restore from disk image.
hibernatemode = 25 (binary 0001 1001) is only settable via pmset. The system will store a copy of memory to persistent storage (the disk), and will remove power to memory. The system will restore from disk image. If you want "hibernation" - slower sleeps, slower wakes, and better battery life, you should use this setting.

In actual use, I have used the following without issues on a MBP 8,2 (Big Sur only, via OCLP), and an iMac 15,1 (Big Sur through Ventura via OCLP). Not having tried it on the hardware you have, I cannot say it will work, but for me, these commands have all worked fine (ignore any and all messages that pop up).

pmset -g Shows the settings you have set now.
sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0
sudo rm /var/vm/sleepimage or
sudo rm /private/var/vm/sleepimage
--Ignore any message saying there is no such file
Create a blanked zero-byte file so the OS cannot rewrite the file:
sudo touch /var/vm/sleepimage or sudo touch /private/var/vm/sleepimage
Make the file immutable:
(sudo chflags nouchg ... to revert)
sudo chflags uchg /var/vm/sleepimage
or
sudo chflags uchg /private/var/vm/sleepimage
The sleep image file is actually in /private/var/vm/ but /var/vm/ is a symbolic link to that location.
sudo pmset -a proximitywake 0
sudo pmset -b tcpkeepalive 0
--This command may produce a warning saying some features may not work properly. This is fine, it simply disables Internet access during sleep. This is the same as disabling "PowerNap" Apple's badly implemented (demented?) attempt to have apps update themselves during sleep behind the users back.
sudo pmset -a powernap 0
sudo pmset -a standbydelaylow 86400
sudo pmset -a standbydelayhigh 86400
sudo pmset -a highstandbythreshold 0

If necessary;
sudo pmset restoredefaults

 

[roysterdoyster]

The problem appears to be between the old graphics driver and the kernel so it's something very difficult to fix

The only workaround would be to completely disable sleep which is not a good idea for a laptop

Thanks for your reply. In fact, since sleep mode can't be used, as it leads to kernel panic, the consequence would be the Shut-down instead or go back to Monterey.

 

[roysterdoyster]

Quite a while ago, I found a through explanation of the sleep commands at

macOSã®å¯ç¸ã«ã¤ãã¦èããã㨠-- `pmset` - ã°ãããã ã

é»æºã¾ããã®è¨å®ï¼ åãããä½ã¨ãªãæ°ã«ãªã£ã¦ãã¦ï¼ãªãä½æãããããªãï¼åæ¥ã触ãã¾ãããï¼ãã·ã³ã®æ°èª¿ãã£ããã§ï¼ãã®è¾ºãæ´çãã¦ãããï¼ã¨æã£ãããã§ãï¼ å¿è«"ããã¾ã§èªåã¬ãã«"ã§æµãð ã¤ãï¼ã¹ãªã¼ãï¼ããããããªãï¼ å¾ã§è§¦ããããã¨ã¯æã£ã¦ããã®ã§ããï¼ãã¾ãã¡ã¹ãã¨å¥ã£ã¦ããªããã§ãããï¼ æãã«ï¼"ä½å¦ãåãããªãã®ãï¼ãï¼åãã£ã¦ããªã"ï¼...

baqamore.hatenablog.com

Unfortunately, it is in Japanese. As I can read Japanese, that wasn't an issue for me, but you may need to try a translation yourself.
The short suggestion, try
sudo pmset -a hibernatemode 0

Hibernation usage:
hibernatemode = 0 (binary 0000) by default on supported desktops. The system will not back memory up to persistent storage. The system must wake from the contents of memory; the system will lose context on power loss. This is, historically, plain old sleep.
hibernatemode = 3 (binary 0011) by default on supported portables. The system will store a copy of memory to persistent storage (the disk), and will power memory during sleep. The system will wake from memory, unless a power loss forces it to restore from disk image.
hibernatemode = 25 (binary 0001 1001) is only settable via pmset. The system will store a copy of memory to persistent storage (the disk), and will remove power to memory. The system will restore from disk image. If you want "hibernation" - slower sleeps, slower wakes, and better battery life, you should use this setting.

In actual use, I have used the following without issues on a MBP 8,2, and an iMac 15,1. Not having tried it on the hardware you have, I cannot say it will work, but for me, these commands have all worked fine (ignore any and all messages that pop up).

pmset -g Shows the settings you have set now.
sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0
sudo rm /var/vm/sleepimage or
sudo rm /private/var/vm/sleepimage
--Ignore any message saying there is no such file
Create a blanked zero-byte file so the OS cannot rewrite the file:
sudo touch /var/vm/sleepimage or sudo touch /private/var/vm/sleepimage
Make the file immutable:
(sudo chflags nouchg ... to revert)
sudo chflags uchg /var/vm/sleepimage
or
sudo chflags uchg /private/var/vm/sleepimage
The sleep image file is actually in /private/var/vm/ but /var/vm/ is a symbolic link to that location.
sudo pmset -a proximitywake 0
sudo pmset -b tcpkeepalive 0
--This command may produce a warning saying some features may not work properly. This is fine, it simply disables Internet access during sleep. This is the same as disabling "PowerNap" Apple's badly implemented (demented?) attempt to have apps update themselves during sleep behind the users back.
sudo pmset -a powernap 0
sudo pmset -a standbydelaylow 86400
sudo pmset -a standbydelayhigh 86400
sudo pmset -a highstandbythreshold 0

If necessary;
sudo pmset restoredefaults

Thank you davidlv for your suggestions
I put in the terminal cmds as per your instructions, to no avail, it did not solve the problem.

 

[coolio2004]

Does someone know ho to get rid of the new menu item for Ethernet controller etc. on/off? No need nor want for that.
Temporarily it can be removed from the menu bar, after Restart it reappears, which is annoying.
Tip anyone?

There is no Ethernet menu item in Ventura -only wifi. If I disable it on my MM 7,1/ MBA 7,2 with 13.4b2 it remains 0ff after reboot the volume.

 

[roysterdoyster]

There is no Ethernet menu item in Ventura -only wifi. If I disable it on my MM 7,1/ MBA 7,2 with 13.4b2 it remains 0ff after reboot the volume.

What is that, then?

 

[rbart]

...

On your iMac, you might have some issues with apps that require DRM or VA that we couldn't find a proper fix yet so if you need those apps, going back to Monterey is your best option for now

Do you think we can be optimistic to have a fix for VA/DRM on AMD R9 GPUs ?
It's very annoying, it's the only real problem I have noticed on my late 2015 27" iMac ...

 

[hvds]

What is that, then?

I've seen this symbol in the menu bar before on my MBP5,2.
I think it appeared when an express card was plugged in - will verify later today. The express card I was using was an USB3.0 from nanotech, during Catalina (maybe also Big Sur) times. I'll see if it still works (doesn't crash the system) in Ventura.
...

Yes, the card still works. The symbol disappears from the menu bar permanently only if card is taken out. It will disappear temporarily if the card is switched off using the menu.
The symbol is not Eth specific, but seems to apply to any such card plugged in.

(now I remember that this specific card works in Big Sur and later with simple USB devices like terminal. Once a storage device is plugged in, system crashes. Just for completeness)

 

[educovas]

Do you think we can be optimistic to have a fix for VA/DRM on AMD R9 GPUs ?
It's very annoying, it's the only real problem I have noticed on my late 2015 27" iMac ...

I'll be getting a Mac with an R9 GPU in a month, hopefully I'll be able to finally fix that.

 

[deeveedee]

Not sure if this helps with the Tesla 1.0 Ventura issue, but my Dell Latitude E6410 would never sleep with any version of MacOS. The problem was that Dell's ACPI did not call the NVidia _OFF method in _PTS (and the macOS driver was not turning off the graphics on S3), so sleep would hang. I fixed macOS sleep on my hack by copying an NVidia _OFF method from a newer Dell laptop and calling _OFF from _PTS. Now this Dell Latitude E6410 HackBookPro6,2 runs Ventura 13.3.1 (patched with OCLP 0.6.4) and sleep / wake works perfectly (as it does in other versions of macOS)

I know this is long-winded, but could the Tesla 1.0 fix be similarly implemented with an ACPI patch? My hack is documented here. The relevent SSDTs in my ACPI patches are SSDT-GFX0.aml (defines _OFF) and SSDT-PTS-WAK.aml (adds _OFF to _PTS).

 

[educovas]

From my research on the TeraScale 1 case, which seems to have the same problem, Apple changed something in the kernel on early Ventura betas that's causing these panics. At least on TeraScale 1, it's not related to ACPI or sleep itself but it's apparently something wrong with the old graphics driver. Most likely the same change in the kernel is also affecting Tesla 1.0 GPUs.

 

[roysterdoyster]

I've seen this symbol in the menu bar before on my MBP5,2.
I think it appeared when an express card was plugged in - will verify later today. The express card I was using was an USB3.0 from nanotech, during Catalina (maybe also Big Sur) times. I'll see if it still works (doesn't crash the system) in Ventura.
...

Yes, the card still works. The symbol disappears from the menu bar permanently only if card is taken out. It will disappear temporarily if the card is switched off using the menu.
The symbol is not Eth specific, but seems to apply to any such card plugged in.

(now I remember that this specific card works in Big Sur and later with simple USB devices like terminal. Once a storage device is plugged in, system crashes. Just for completeness)

Thanks hvds for tipping me to that. I put my NanoTECH USB 3.0 card into the ExpressCard34 slot and from now it only appears, when I put the card in. When I eject the card the menu item is gone.
Looks like it appears with a first time installation of Ventura, I guess.