I believe typing this into Terminal once has resolve this issue for me.
defaults write com.apple.coremedia hardwareVideoDecoder -string disable
Got a tip for us?
Let us know
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
- Thread starter 0xCUBE
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
defaults write com.apple.coremedia hardwareVideoDecoder -string disable
Did it stay this way? I had YouTube running for one login session but then again it did not work anymore.
Has anyone successfully gotten Ventura to work on a Mac Pro 6.1 with the manual Kernel debug kit?
can you send the instructions how to install this and modify thanksSlow boot up Ventura 13.0.1, just set in OpenCore configurator => SetApfsTrimTimeout to 0. Now my system boots in 10sec.
First you need to download OpenCore Configurator => https://mackie100projects.altervista.org/download/occ/
Mount the EFI partition with this tool, load config.plist with OpenCore Configurator than sel Kernel in OpenCore Configurator and change the value of SetApfsTrimTimeout from -1 to 0, save the config.plist and reboot.
Awesome 22 Seconds on my MacBook Pro 9.2
I had been using the Aerial screensaver before updating the OS. What I noticed is the crash seemed to happen as the screen saver started. When I looked at the screensaver settings screen, the box showing the current screensaver was black. I just switched to the new ventura screensaver, saved the setting, then switched back to my preferred.
Guessing the setting was pointing to something not a screensaver after the update.
I’ll rather have SSD trim enabled than faster boot times, The use of TRIM can improve the performance of writing data to SSDs and contribute to longer SSD life, just me.
For me speed is the key to get a better system but Trim was off on mine system long time ago
I haven't had the issue since the last time, a few days ago, but I'll keep this fix in mind. what's causing it you think? im not familiar with the terminal command.
From the looks of it the command turns off hardware video decoding, meaning the dedicated energy-efficient piece of silicon that can decode various common web-video formats gets turned off, forcing the CPU to do it instead.
That'd lead me to believe that, with the hardware decoding enabled, video formats that aren't fully compatible are sent to the decoder if you leave it turned on, causing problems. Alternatively that the decoder in combination with the legacy gpu-driver is somehow misconfigured when running the unsupported OS.
I was trying to do that but to get some reference, before deleting the files, I rebooted the Mac mini (late 2012, core i7 with 16Gb RAM) and the same thing that happened to @Vado hasn't happened again.
But I didn't delete the files. I just opened the folder and some of the files in there.
The one thing I noticed was that the boot takes about 15 seconds more than it used to, with Ventura installed. It used to be 40s and now is 55s.
I had another issue that happened to a number of users. I too had freezes with wake up. I solved it by disabling the password require to unlock the screen. It stopped freezing.
This was with Ventura 13.0. With 13.01 I didn't reintroduced the password to unlock the screen, so I don't know if that was sorted out with ventura 13.01.
Thanks, now 21 seconds with my 11.2 mbp !
Last edited:
The most common things that I have seen over the years that cause login delays are related to sleep settings and login items. On an iMac I would first look at your preference settings that start an application automatically when you login, especially if it is something that has to establish a network connection.
On Ventura, I would go to System Settings -> General -> Login Items and have a look at what is turned on. If there is anything there that you really don't need to have started immediately when you login, turn it off.
Also, sometimes it is possible to still have a login item setting trying to start an application that you have deleted, which takes a long time to time out.
This is really important.
If these are the original drives, and they have not been replaced, it is time to check them and decide if you want to go any further with a fusion drive configuration, and also if you want to continue using the iMac.
First, if you have anything already installed on this system that will report the S.M.A.R.T. data for both the SSD and the HDD, see what your utility reports about drive health and time in use. If you don't have a disk utility that will give you S.M.A.R.T. information, download the trial of DriveDX from Binary Fruit. https://binaryfruit.com/drivedx
Next, go to iFixit and look at what it takes to replace the drives. The odds are really good that both of your drives are at or beyond their life span. A 2014 27 inch iMac is a bear to replace internal drives. If you want to keep using it, I would suggest booting from an external SSD.
You don’t need any utility for that.
One way is to check in System Profiler, or in Disk utility.
Other much more detailed way is to install “smartmontools” via terminal and brew. Then you can run in terminal “smartctl”.
Attachments
Last edited:
As an update, I ended up having to wipe the drive, install Ventura, then migrate using the Time Machine backup I made to a quick Samsung Flash drive I have on hand. Then it worked without a hitch.
I will say, it's a damn shame Apple stopped supporting this 2013 i7 MBA. Ventura is more fluid and quicker than Big Sur ever was and my wife would never know that it's patched on here. I'm downright impressed. Great work to the OCLP team!
Ventura working smoothly on Nvidia dGPUs? I've got a nice iMac 14,3 that I'd like to attempt an install on toward the end of the month.
Edit: Did some scrolling in this thread and it appears yes. Very impressive, will try it!
Edit: Did some scrolling in this thread and it appears yes. Very impressive, will try it!
Last edited: