Where are these nightly builds located actually?for me, OCLP 0.6.2 nightly exactly fixed the settings issue ...
Where are these nightly builds located actually?for me, OCLP 0.6.2 nightly exactly fixed the settings issue ...
Does your Apple Bluetooth mouse and keyboard work without problems in Ventura on the iMac 2010?View attachment 2149352Thank you, so far problem with Bluetooth but, the enter+tab trick works , but, I have to reset it at each start. This was an upgrade on top of Monterey, so all my files and setting were okay. My second monitor is working, but, strangely not present in the set up display. Sound is pebble but okay with adding soundSource app. InMap there is no display, I can see my position but there is no image. Zoom is working, Safari is okay. All USB working without problem, I have a WIFI dongle, no problem , same things since BigSur, Mail was slow to setup but working now, no problem. using Wireless USB BigSur Adapter-V13. Clean my Mac works as well.Thank you all for your Help and Hard work, I admire your dedication and passion...
I used OCLP 0.6.1 to install Ventura 13.1 and the black boxes disappeared after the root patches. I didn't have to change anything on the display section of the settings menu.So I managed to do the work around by selecting unknown display which removed the black marks, but that was after I had already tried OCLP 0.6.2 without success. Are you saying the black areas disappeared for you without having to apply the display work around? Seems very strange how people can have different experiences with the same setup!
With 0.6.1 and 0.6.2 for me with mini 5,1 root patches didn't fix the black box. I had to change display to unknown to fix that.I used OCLP 0.6.1 to install Ventura 13.1 and the black boxes disappeared after the root patches. I didn't have to change anything on the display section of the settings menu.
Where are these nightly builds located actually?
yes, the black areas disappeared only with the new OCLP version. No display workaround and no uninstallation of OCLP 0.6.1. That's why I replied to you.So I managed to do the work around by selecting unknown display which removed the black marks, but that was after I had already tried OCLP 0.6.2 without success. Are you saying the black areas disappeared for you without having to apply the display work around? Seems very strange how people can have different experiences with the same setup!
Try this:So to follow up on my previous posts - having seent a good while attempting to get 13.2 installed on my iMac 10,1 - here are the updates
Installed onto a Clean SSD- done
Boots into Venura find from patched Efi volume on SSD- done
Installing root patches- not good
Gets all the way to the end then fails with the error below as before.
View attachment 2149977
Any idea's folks ?
Have a look at Library/Extensions and remove the corresponding .kext on a test basis. Try then to re-apply the root patches ...So to follow up on my previous posts - having seent a good while attempting to get 13.2 installed on my iMac 10,1 - here are the updates
Installed onto a Clean SSD- done
Boots into Venura find from patched Efi volume on SSD- done
Installing root patches- not good
Gets all the way to the end then fails with the error below as before.
View attachment 2149977
Any idea's folks ?
Try this:
View attachment 2149985
I have same issue on Mac mini Late 2012 , macOS 13.2 installer with OCLP 0.6.1 on separate partition from Catalina via the new USB3 Kingston , any idea ?Clean or conventional installation of macOS 13.2 with OCLP 0.6.1 via USB3 card reader on a native USB 2 port or a card reader in my display (actually a USB 3 hub ...) doesn't work here. With about remaining 12 minutes of the installation procedure this error suddenly appears:
View attachment 2147259
An offered restart always brings me back to this point.
Can this be fixed or circumvented?
Thanks in advance for useful hints!
OK - so I have nothing in there except those kext files
View attachment 2149999
What's next ?
I remember when I installed this on my MacPro it downloaded some KDK ? (maybe) file during the post patch install ?
Maybe the hint in this post helps, haven't tried yet ...I have same issue on Mac mini Late 2012 , macOS 13.2 installer with OCLP 0.6.1 on separate partition from Catalina via the new USB3 Kingston , any idea ?
Ohh I'll try later tonight and let you know - hope I can get this sorted, its the last piece of the puzzle....What about System/Library/Extensions/ ?
Lucky you!! I've got a MacPro 4.1 to 5.1 firmware upgraded with 12 GB RAM, Radeon RX580 Nitro 8 GB. First I had some issues installing Ventura because, after a fresh install, the screen flashed all the time when getting to the logging screen. I was able ( I don't know how ) to introduce the password in one of those flashes, get to the Desktop, update the patchers for AMD Polaris and finally get an usable computer again. But after 3 days, the MacPro started to freeze every x minutes ( around 15-20 minutes ). And then the computer didn't come back. I'm trying to reinstall Monterey with an external USB but when it gets to 13 minutes the computer hangs again. I'm afraid Ventura has mess with the hardware somehow. Fist time I have to regret for using OCLP. I think it isn't mature enough for the release, at least for the older MacPros. Yes, I know it's always a risk, and may be I have been too lucky during the last 6-7 years using Open Core. Thankfully I bought a MacStudio few months ago in anticipation for this to happen.Ohh I'll try later tonight and let you know - hope I can get this sorted, its the last piece of the puzzle....
Super chuffed my MacPro 5,1 is working perfectly though - as previously mentioned by other members, seems to run as good, if not better on Ventura than previously on Monterey.
You have to do a fresh install. Even though Catalina may be in different partition it clashes with the opencore efi folder firmware inputs , so you will get this error as per image you posted.I have same issue on Mac mini Late 2012 , macOS 13.2 installer with OCLP 0.6.1 on separate partition from Catalina via the new USB3 Kingston , any idea ?
Nothing "mysterious" about it, the KDKs reside in Library/Developer/KDKs/KDK_13.2_22D49.kdk <--- this is what you should see. Delete that KDK and try the Post Install Root Patch again (after checking that the Library/Extensions folder only has those 3 files mentioned above). This KDK subject has been mentioned several times on previous pages, maybe a search is suggested?OK - so I have nothing in there except those kext files
View attachment 2149999
What's next ?
I remember when I installed this on my MacPro it downloaded some KDK ? (maybe) file during the post patch install ?
There is a very real difference in the complexity involved in getting Ventura to work on older Macs without Metal capable GPUs. I have an old MBP 2011 that runs Big Sur fine using OCLP 0.6.1 but even Monterey is difficult on that machine. If you need stability, stay with Monterey or Big Sur. Ventura will work, with some iffy areas, but I think that hardware is simply too old to run the latest OS (my opinion only, others may think differently).I have a Late 2009 iMac 27" 11,1 with a K2100M. I use OCLP 0.6.1 and am running 12.6.3. It is very stable for me.
Is the current version of OCLP stable enough for this Mac to consider upgrading to Ventura? Although it's not a work-critical machine, it's for my son - so stability is most important here.
I do have a Metal-capable GPU (NVIDIA K2100M).There is a very real difference in the complexity involved in getting Ventura to work on older Macs without Metal capable GPUs. I have an old MBP 2011 that runs Big Sur fine using OCLP 0.6.1 but even Monterey is difficult on that machine. If you need stability, stay with Monterey or Big Sur. Ventura will work, with some iffy areas, but I think that hardware is simply too old to run the latest OS (my opinion only, others may think differently).
You certainly can't go wrong with a fresh installation. But even that doesn't always mean a good result.You have to do a fresh install. Even though Catalina may be in different partition it clashes with the opencore efi folder firmware inputs , so you will get this error as per image you posted.