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.
Hi guys, I guess I'm not lucky.

Using OCLP 0.6.1 on Ventura 13.2 (MBP early 2011 8,3) and having created my USB boot device as explained in the Mr Macintosh video, the installation is working fine on the first progress bar, but then after the first reboot, it reaches about "remaining 20 minutes" and boom, it crashes (attached pictures)

Even if I restart, it does the same thing. You can see it started to create a partition on my formated SDD.

Any idea?
 

Attachments

  • PXL_20230127_042605708.jpg
    PXL_20230127_042605708.jpg
    265.8 KB · Views: 275
  • PXL_20230127_042631128.jpg
    PXL_20230127_042631128.jpg
    263.2 KB · Views: 154
  • PXL_20230127_042819470.jpg
    PXL_20230127_042819470.jpg
    351.1 KB · Views: 150
Well with OLCP 0.6.1 released, I decided to go for broke and upgrade almost every piece of elderly Mac hardware I have eligible to 13.2 including:

Mac Pro 3,1 (Early 2008, 28 GB RAM, Nvidia GTX 680)
iMac 8,1 (24" Early 2008, 4 GB RAM, AMD Radeon HD 2600 Pro)
Macbook 5,1 (Late 2008, 8 GB RAM, Nvidia 9400M)
Mac Mini 4,1 (Mid 2010, 4 GB RAM, Nvidia 320M)*
iMac 12,2 (27" Mid 2011, 20 GB RAM, AMD Radeon HD 6970M)*
Macbook Air 6,2 (13" Mid 2013, 8 GB RAM, Intel HD 5000)

* Clean install, not an upgrade from Monterey/OLCP

Of these machines, the Mac Pro worked on a test SSD but I don't have it on my production SSD yet since I daily drive this thing (and am typing on it now) and I want to test it some more before taking the plunge. The Macbook 5,1 keyboard/trackpad don't work but that is a known bug. I am not updating (yet) a 2016 Macbook Pro 13,1 (13" two Thunderbolt ports, Intel Iris Graphics) since this is my wife's daily driver and I don't want to do that machine just yet and she probably won't tolerate any glitchy graphics. It's the newest of the bunch....maybe Iris Graphics is ok?

All the machines use wired Ethernet except the Macbook Air.

The only real hang-up was having to do a clean install on the iMac 12,2 after the upgrade failed and I screwed up the Fusion drive + Bootcamp partition which meant I had to blow away everything and start fresh. Yikes, and I have to install Windows 10 all over again. The Mac Mini 4,1 had a corrupted install from a bad Monterey update a while back which I never fixed so I just started over there too.

But so far, everything works. Non-metal graphics is a little glitchy but it seems to be the same glitchyness with all the machines in the same fashion. I expect better from the Mac Pro except for things that require Metal 2 which right now won't work.

Kudos to everyone on the OLCP team for making this possible. I never thought any of these machines would run Ventura and I keep getting proved wrong.
 
Last edited:
  • Like
Reactions: surszki, osxfr33k, roronl and 4 others
Installed 13.2 (with OCLP v061/v062n) on a iMac10,1 (non-metal) external Samsung T5 SSD (requiring a USB hub for the keyboard & mouse). It booted up well and installed the root patch for the Nvidia Graphics Acceleration, WiFi fix, and USB 1.1 patch. But all external USB devices including the external SSD stopped working after restart (after OCLP picker), The T5 SSD led flashed a few times in the very beginning of the boot up process and then all external USB devices went dead. Reverting the root patch (in recovery mode via terminal command) resolves this issue. But this leaves the Ventura unpatched. I speculate that it is most likely caused by the USB 1.1 patch. It would be nice if I can disable this particular patch before installing the root patch or using terminal command in recovery mode so that others like graphics acceleration & wifi could still be patched up. Also noticed that the wifi doesn’t work (root patch not installed). The confusing thing is that the wifi icon was displayed during the initial setup of Ventura after asking for SSID and password.
 
Last edited:
Newfylox said:
Hi guys, I guess I'm not lucky.

Using OCLP 0.6.1 on Ventura 13.2 (MBP early 2011 8,3) and having created my USB boot device as explained in the Mr Macintosh video, the installation is working fine on the first progress bar, but then after the first reboot, it reaches about "remaining 20 minutes" and boom, it crashes (attached pictures)

Even if I restart, it does the same thing. You can see it started to create a partition on my formated SDD.

Any idea?
Click to expand...
I too am stuck at same point of macos software update assistant. Dont know why. I even tried using a ethernet adapter but no luck
 
Last edited:
Sevenfeet said:
Well with OLCP 0.6.1 released, I decided to go for broke and upgrade almost every piece of elderly Mac hardware I have eligible to 13.2 including:

Mac Pro 3,1 (Early 2008, 28 GB RAM, Nvidia GTX 680)
iMac 8,1 (24" Early 2008, 4 GB RAM, AMD Radeon HD 2600 Pro)
Macbook 5,1 (Late 2008, 8 GB RAM, Nvidia 9400M)
Mac Mini 4,1 (Mid 2010, 4 GB RAM, Nvidia 320M)*
iMac 12,2 (27" Mid 2011, 20 GB RAM, AMD Radeon HD 6970M)*
Macbook Air 6,2 (13" Mid 2013, 8 GB RAM, Intel HD 5000)

* Clean install, not an upgrade from Monterey/OLCP

Of these machines, the Mac Pro worked on a test SSD but I don't have it on my production SSD yet since I daily drive this thing (and am typing on it now) and I want to test it some more before taking the plunge. The Macbook 5,1 keyboard/trackpad don't work but that is a known bug. I am not updating (yet) a 2016 Macbook Pro 13,1 (13" two Thunderbolt ports, Intel Iris Graphics) since this is my wife's daily driver and I don't want to do that machine just yet and she probably won't tolerate any glitchy graphics. It's the newest of the bunch....maybe Iris Graphics is ok?

All the machines use wired Ethernet except the Macbook Air.

The only real hang-up was having to do a clean install on the iMac 12,2 after the upgrade failed and I screwed up the Fusion drive + Bootcamp partition which meant I had to blow away everything and start fresh. Yikes, and I have to install Windows 10 all over again. The Mac Mini 4,1 had a corrupted install from a bad Monterey update a while back which I never fixed so I just started over there too.

But so far, everything works. Non-metal graphics is a little glitchy but it seems to be the same glitchyness with all the machines in the same fashion. I expect better from the Mac Pro except for things that require Metal 2 which right now won't work.

Kudos to everyone on the OLCP team for making this possible. I never thought any of these machines would run Ventura and I keep getting proved wrong.
Click to expand...
To get macbook air wired network i tried ethernet adapter but screen stuck at mac os update assistant updating
 
Last edited:
OK fols - a little advice here if at al possible. So I've got my MP5,1 working flawlessly with OCLP 6.1 although it does have upgraded graphics and BT - but it works fine.

My iMac 10,1 on the other hand refuses to install the post patches and throughs an error at the end of the process

Unable to build new kernel cache
Reason for patch failure (71)
Error Domain=KMErrorDomain Code=71 "Unable to resolve dependancies:

etc (see attached for full log)



What's he earliest mac people have had this working on ?
Using this iMac to type this - connecting via lan and using usb2 keyboard and mous.
obviously legaccy wifi/BT graphics and USB 1.1 not working due to failed post patches
 

Attachments

  • Screenshot 2023-01-27 at 07.43.57.png
    Screenshot 2023-01-27 at 07.43.57.png
    57.7 KB · Views: 82
[ @steverae – I have a similar problem! ]

Good morning,

as one or the other may have read, I was able to upgrade Ventura 13.2 from Monterey directly via the Software Update. But that was just a test drive with a clean install.

I also managed to do this on another drive (existing installation, no clean install), however I am not able to apply the root patches here.

oclp_rp_failed.png


What can I do? Thanks for helpful hints!

Edit: I was able to fix the error myself. In Library/Extensions/ I found a driver from one of my old Western Digital hard disks (WDUSB_64_109HPDriver.kext). After I removed it, the root patching worked without any problems! 👍
 
Last edited:
  • Like
Reactions: LlamaLarry and mikelets456
Newfylox said:
Hi guys, I guess I'm not lucky.

Using OCLP 0.6.1 on Ventura 13.2 (MBP early 2011 8,3) and having created my USB boot device as explained in the Mr Macintosh video, the installation is working fine on the first progress bar, but then after the first reboot, it reaches about "remaining 20 minutes" and boom, it crashes (attached pictures)

Even if I restart, it does the same thing. You can see it started to create a partition on my formated SDD.

Any idea?
Click to expand...
@Newfylox – I had the same problem and described it in an earlier post. For me no solution so far. But I was able to upgrade directly via Software Update on a test drive's Monterey clean installation in the mean time ...
 
@Newfylox

I did that 3 days ago, just to experiment and after the first error (1st pic), I forced restart my Mac to boot from the macOS installer option (3rd pic). After the next error, I forced restart to macOS installer once again. After a few automated restarts the system started the Ventura installation process.
I didn't expect it to succeed, but it did.
Anyway, I'm posting this because we have similar machines and it may help you.
 
Last edited:
  • Like
Reactions: Newfylox and coasterOneEightThree
909allday said:
@Newfylox

I did that 3 days ago, just for experiment and after the first error (1st pic), I forced restart my Mac to boot from the macOS installer option (3rd pic). After the next error, I forced restart to macOS installer once again. After a few automated restarts the system started the Ventura installation process.
I didn't expect it to succeed, but it did.
Anyway, I'm posting this because we have similar machines and it may help you.
Click to expand...
Thats interesting, thanks! Now I see, what you mean.

I always booted from the EFI of the USB stick after each restart (even after the error in picture 1 and 2) and expected the macOS installer to be there, where it then failed to show up.

I will try it at the next opportunity to select the installer directly on the boot screen ...
 
  • Like
Reactions: 909allday
Newfylox said:
Hi guys, I guess I'm not lucky.

Using OCLP 0.6.1 on Ventura 13.2 (MBP early 2011 8,3) and having created my USB boot device as explained in the Mr Macintosh video, the installation is working fine on the first progress bar, but then after the first reboot, it reaches about "remaining 20 minutes" and boom, it crashes (attached pictures)

Even if I restart, it does the same thing. You can see it started to create a partition on my formated SDD.

Any idea?
Click to expand...
It happened to me as well, resolved by re-formatting the partition with "Mac OS Extended (Journaled)" via built-in Disk Utility in Ventura installation USB.
 
  • Like
Reactions: roronl
Does the standard Bluetooth card of the iMac 2010 (imac11,3) work with Ventura and OpenCore?

In my first test a few months ago, I had problems pairing the original mouse and keyboard.
 
So far Ventura 13.2 is operating fine on my MacBookPro11,4. But I do have a problem; I can't easily share files between this and other Macs over a network. If I try to connect to another Mac running Ventura or not, the Finder will usually lock up and I have to either log out and back in, or reboot the Mac. If I "Force Restart" Finder, it simply won't start back up. Same thing happens if I try to access this from another Mac, like my M1 MacBook Air.
Anyone else getting something like this, too? For now, I can only share files between them via Target Disk Mode and my iCloud Drive. (I can't even use AirDrop between them, either!)
 
909allday said:
@Newfylox

I did that 3 days ago, just to experiment and after the first error (1st pic), I forced restart my Mac to boot from the macOS installer option (3rd pic). After the next error, I forced restart to macOS installer once again. After a few automated restarts the system started the Ventura installation process.
I didn't expect it to succeed, but it did.
Anyway, I'm posting this because we have similar machines and it may help you.
Click to expand...

Thank you guys for all your support and tips. I did force reboot the third option and it worked! At first, the boot gave me a black screen without any clue nor noise, but after a few seconds/minutes it started and it continues as mentioned in the video.

Now I have something odd. At the end, it installed all the needed patches and everything is working find except that my computer is a little bit laggy/slow. The patches are installed, I can feel that my touchpad/mouse is fast and response correctly while using the OS, but all other stuff is laggy. Scrolling up/down in browser, minimize any window software in the tray, some effects, etc.

So all the post patches are installed but it's slow and laggy. Also, my menu bar is always black despite selecting a light theme.

I heard that I can apply this code below to only use my Intel graphic card and disable my Radeon, and then having a smooth experience, but I don't get the point of doing this since it's supposed to handle non metal graphic computer.

nvram FA4CE28D-B62F-4C99-9CC3-6815686E30F9:gpu-power-prefs=%01%00%00%00

Do you think there is a better way than doing this?

Thanks again guys, you are very helpful!
 

Attachments

  • Screenshot 2023-01-27 at 8.47.19 AM.png
    Screenshot 2023-01-27 at 8.47.19 AM.png
    2.6 MB · Views: 92
Newfylox said:
OCLP 0.6.1 on Ventura 13.2 (MBP early 2011 8,3) >nip< after the first reboot, it reaches about "remaining 20 minutes" and boom, it crashes (attached pictures) Any idea?
Click to expand...
Have seen this a few times. What appeared to have help me was to make sure the old APFS volume is completely removed and erased before erasing/formatting and creating a new one on the SSD and then start the install again.
Using Disk Utility from the USB, show all devices, open the container, select the main APFS volume and control-click to get the "delete APFS volume" option
It seemed to me that the installer might be confused by the old EFI,APFS or container but that is just my best guess.
World 100% for me tough when seeing this.
Good luck.
 
Last edited:
coasterOneEightThree said:
[ @steverae – I have a similar problem! ]

Good morning,

as one or the other may have read, I was able to upgrade Ventura 13.2 from Monterey directly via the Software Update. But that was just a test drive with a clean install.

I also managed to do this on another drive (existing installation, no clean install), however I am not able to apply the root patches here.

View attachment 2148971

What can I do? Thanks for helpful hints!

Edit: I was able to fix the error myself. In Library/Extensions/ I found a driver from one of my old Western Digital hard disks (WDUSB_64_109HPDriver.kext). After I removed it, the root patching worked without any problems! 👍
Click to expand...
I'll have another go but this time perform a full wipe and reinstall of the OS rather then an upgrade from Monterey
I'll let you know how i get on
 
houser said:
Have seen this a few times. What appeared to have help me was to make sure the old APFS volume is completely removed and erased before erasing/formatting and creating a new one on the SSD and then start the install again.
Using Disk Utility from the USB, show all devices, open the container, select the main APFS volume and control-click to get the "delete APFS volume" option
It seemed to me that the installer might be confused by the old EFI,APFS or container but that is just my best guess.
World 100% for me tough when seeing this.
Good luck.
Click to expand...
I'm glad you're telling me this because that's what I thought, BUT I wasn't sure so I didn't want to erase the main APFS volume. I did what @909allday and it worked.

But now that you're telling me this, do you think that I should restart all over again or it's good enough that my installation is completed? Because I don't think it will solves my "new" issues once in the OS. I'm talking in a "hard drive" perspective, do you think it may cause issues if I'm not restarting the installation like you mentioned or having successfully installed it by forcing the third option is good enough?

Thanks again
 
I asked this in another thread, maybe someone knows an option:

coasterOneEightThree said:
How can I permanently determine from which drive the Mac should boot without a boot screen selection?

My OCL patched MacPro 3,1 on Ventura contains three, sometimes four SSD drives, all of them have own EFIs.

  • I've tried to select the corresponding EFI with control-enter on the boot screen.
  • In the corresponding EFI chosen on boot screen I've also tried to select a startup drive with control-enter.
  • I've tried to determine the startup drive conventionally in System Preferences.

Result in all cases: Without further action the Mac always starts from the drive in Bay 1.

If I swap the drives, the Mac will start from the other drive in Bay 1.

Is there any other possibility I don't know? Or is there a utility that provides exactly this function?

Thanks in advance!
Click to expand...
 
Hello everyone, the method above did not help. Macbook A1398, bluetooth does not work, or rather the mouse sees, there is a connection button. And even connects sometimes but does not work or the connection is constantly spinning
 
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