macOS 13 Ventura on Unsupported Macs Thread

[deeveedee]

I have upgraded my iMac 12.2 (with metal capable GPU GTX780M) from OCLP 0.3.1 Bug Sur 11.3 to OCLP 1.0.1 Ventura 13.6

Everything seems to work fine, except that I keep getting two pop-up error messages.

What can I do to solve this ?.

Thanks

I haven't seen these messages, so I'll admit that I'm taking a guess...

Do you still get these messages when you patch Ventura 13.6 with OCLP 0.6.8? To test, you should download Open Core 0.6.8, "Build and Install Open Core" using OCLP 0.6.8 and apply post-install patches using OCLP 0.6.8. Then reboot, press space bar to show Open Core extended menu, select "Reset NVRAM" and then boot Ventura 13.6.

 

[stephengrenfell]

I haven't seen these messages, so I'll admit that I'm taking a guess...

Do you still get these messages when you patch Ventura 13.6 with OCLP 0.6.8? To test, you should download Open Core 0.6.8, "Build and Install Open Core" using OCLP 0.6.8 and apply post-install patches using OCLP 0.6.8. Then reboot, press space bar to show Open Core extended menu, select "Reset NVRAM" and then boot Ventura 13.6.

OCLP 0.6.8 installed.
post-install patches applied.
Reboot.
(not able to access OC extended menu as BT keyboard doesn't work at boot menu)
Error messages come back after few minutes.
Everything else OK, including BT.

Connected USB keyboard & mouse.
Reboot and access extended OC menu, Reset NVRAM selected.
Unable to activate BT after reboot.
Error messages back after few minutes.

Several reboots and power down/ power up performed.
Always no BT and error messages after few minutes each time.

Power off & disconnected power cord for 20 minutes.
Started up.
Unable to activate BT.
Error messages still there after few minutes.

OCLP 1.0.1 installed.
post-install patches applied.
Reboot.
BT now back.
Initially no Error messages....for several hours.
But wake from sleep now seems broken. Wake from sleep worked after initial upgrade to OLCP 1.0.1 + Ventura 13.6
After forced shutdown by holding power on button then reboot, error messages now back after few minutes.

 

[deeveedee]

@stephengrenfell do you know how to find your Open Core config.plist? If so, could you please post it?

EDIT: I just noticed that you can't access the OC extended menu. Please shutdown, reset NVRAM and test again.

 

[Macstefws]

Got a Mac Pro 5.1 2x6 core Xeon, 128 GB, 1GB ATI HD5770, 2GB+1GB NVMe PCI storage, 128GB sata SSD, only it fails to finish installation og either Monterey, Ventura or Sonoma with OCLP 1.01. All OS variants seems to boot of OCLP boot image and launch Installation, then after rebooting to a installed image of interal storage, installation process continues only to crash around 23 minutes left approx 40% done. Dunno how to investigate this futher. Even tried a running Ventura 13.6 NVMe PCI 1 GB from my Mac pro 3.1 also with ATI HD5770, where it works superb. but seems this can't boot in my Mac Pro 5.1 which I would expect .

Mac Pro 5.2 HW seems fine, it runs Promox VE v.8 and Catalina 10.15.7 without problems...

Hints much appreciated, TIA!

Tail from an ia.log when installation dies:

...
Oct 21 14:06:40 Mac-Pro Installer Progress[59]: IASGetCurrentInstallPhase: Current phase name is "Language Chooser"
Oct 21 14:06:40 Mac-Pro Installer Progress[59]: currentPhase = "<IASPPhase: 0x600000bbd9c0: 'Language Chooser', percentage 5.0, delay 0>", phases = (
        "<IASPPhase: 0x600000bbdae0: 'Boot 1', percentage 5.0, delay 0>",
        "<IASPPhase: 0x600000bbd9c0: 'Language Chooser', percentage 5.0, delay 0>",
        "<IASPPhase: 0x600000bbdb40: 'OS Installer', percentage 5.0, delay 0>",
        "<IASPPhase: 0x600000bbd9a0: 'EFI Firmware Update', percentage 5.0, delay 0>",
        "<IASPPhase: 0x600000bbdc40: 'Boot 2', percentage 5.0, delay 0>",
        "<IASPPhase: 0x600000bbd880: 'Language Chooser 2', percentage 5.0, delay 0>",
        "<IASPPhase: 0x600000bbda40: 'OS Installer 2', percentage 70.0, delay -1>"
    )
Oct 21 14:06:40 Mac-Pro Installer Progress[59]: Showing Progress UI
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: Disabling system idle sleep.
Oct 21 14:06:40 Mac-Pro powerd[46]: Assertion Created. Type:PreventUserIdleDisplaySleep Name:'OSInstaller' Id:0x50000800f Process:macOS Update Assistant [System: PrevIdle PrevDisp kDisp]
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: Using product <OSProduct: 0x600001140570> at distance 5
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: Setting shouldMigrate: 1 ((null))
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: Skipping firmware update because the machine is a MacPro 5,1.
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: SUSoftwareUpdateController: Service connection invalidated!
Oct 21 14:06:40 Mac-Pro Installer Progress[59]: IASSetCurrentInstallPhase: Current phase name set to "OS Installer 2"
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: InstallerDiagnostics: mUA: Did not find prior build.
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: ROM Features from IODeviceTree:/rom returned: 0x00c0001403
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: ROM Features from IODeviceTree:/options returned: nil
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: ROM does not support APFS
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: Allowing install on incompatible EFI ROM: virtual machine
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Purging snapshots[D53C0079-5777-4C7E-8F10-8731A6F19F9C](disk4s1): /Volumes/macOS - Data - Data - Data
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Removing VM volume [D89CC853-0E14-4D6E-B508-CDE51AA43532](disk4s6)
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Removing: D89CC853-0E14-4D6E-B508-CDE51AA43532 progress: 0.000000 message: (null)
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Removing: D89CC853-0E14-4D6E-B508-CDE51AA43532 progress: 0.000000 message: Deleting APFS Volume from its APFS Container
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Removing: D89CC853-0E14-4D6E-B508-CDE51AA43532 progress: 10.000000 message: (null)
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Removing: D89CC853-0E14-4D6E-B508-CDE51AA43532 progress: 10.000000 message: Unmounting disk4s6
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Removing: D89CC853-0E14-4D6E-B508-CDE51AA43532 progress: 20.000000 message: (null)
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Removing: D89CC853-0E14-4D6E-B508-CDE51AA43532 progress: 20.000000 message: Erasing any xART session referenced by D89CC853-0E14-4D6E-B508-CDE51AA43532
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Removing: D89CC853-0E14-4D6E-B508-CDE51AA43532 progress: 35.000000 message: (null)
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Removing: D89CC853-0E14-4D6E-B508-CDE51AA43532 progress: 35.000000 message: Deleting Volume
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Removing: D89CC853-0E14-4D6E-B508-CDE51AA43532 progress: 50.000000 message: (null)
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Removing: D89CC853-0E14-4D6E-B508-CDE51AA43532 progress: 75.000000 message: (null)
Oct 21 14:06:40 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Removing: D89CC853-0E14-4D6E-B508-CDE51AA43532 progress: 75.000000 message: Removing any Preboot and Recovery Directories
Oct 21 14:06:41 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Removing: D89CC853-0E14-4D6E-B508-CDE51AA43532 progress: 100.000000 message: (null)
Oct 21 14:06:41 Mac-Pro OSInstaller[219]: OSIPurgeSnapshotsElement: Successfully removed D89CC853-0E14-4D6E-B508-CDE51AA43532
Oct 21 14:06:41 Mac-Pro Installer Progress[59]: Status is "About 29 minutes remaining…"
Oct 21 14:06:41 Mac-Pro opendirectoryd[61]: [session] Received a network change notification
Oct 21 14:06:41 Mac-Pro opendirectoryd[61]: [session] Received a network change notification
Oct 21 14:06:28 Mac-Pro Language Chooser[213]: ISAP: Done with Phase "Language Chooser"
Oct 21 14:06:28 Mac-Pro Installer Progress[59]: Done with phase = "Language Chooser"
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking storage system and repairing if necessary and if possible
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Performing fsck_apfs -y -x /dev/disk1s3
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking the container superblock.
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking the checkpoint with transaction ID 4752.
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking the EFI jumpstart record.
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking the space manager.
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking the space manager free queue trees.
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking the object map.
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking the encryption key structures.
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking volume /dev/rdisk4s1.
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking the APFS volume superblock.
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: The volume macOS - Data - Data - Data was formatted by diskmanagementd (1934.141.2) and last modified by apfs_kext (2235.0.13).
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking the object map.
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking the snapshot metadata tree.
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking the snapshot metadata.
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking the document ID tree.
Oct 21 14:06:42 Mac-Pro OSInstaller[219]: Checking the fsroot tree.
Oct 21 14:06:45 Mac-Pro opendirectoryd[61]: [session] Processing a network change notification
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the extent ref tree.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Verifying volume object map space.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: The volume /dev/rdisk4s1 with UUID D53C0079-5777-4C7E-8F10-8731A6F19F9C appears to be OK.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking volume /dev/rdisk4s2.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the APFS volume superblock.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: The volume Preboot was formatted by diskmanagementd (2142.101.3) and last modified by apfs_kext (2235.0.13).
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the object map.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the snapshot metadata tree.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the snapshot metadata.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the fsroot tree.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the extent ref tree.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Verifying volume object map space.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: The volume /dev/rdisk4s2 with UUID DB107A77-143D-421F-98CA-17E596E1296D appears to be OK.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking volume /dev/rdisk4s3.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the APFS volume superblock.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: The volume Recovery was formatted by diskmanagementd (2142.101.3) and last modified by apfs_kext (2235.0.13).
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the object map.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the snapshot metadata tree.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the snapshot metadata.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the fsroot tree.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the extent ref tree.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Verifying volume object map space.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: The volume /dev/rdisk4s3 with UUID 122F3A73-8532-4289-AA61-68FDB17313E6 appears to be OK.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking volume /dev/rdisk4s5.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the APFS volume superblock.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: The volume Update was formatted by com.apple.MobileSo (2142.101.3) and last modified by apfs_kext (2235.0.13).
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the object map.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the snapshot metadata tree.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the snapshot metadata.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the fsroot tree.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Checking the extent ref tree.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Verifying volume object map space.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: The volume /dev/rdisk4s5 with UUID EB1AEC46-F3AA-419D-B3D7-BF50FFCABAB6 appears to be OK.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Verifying allocated space.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: The container /dev/disk1s3 appears to be OK.
Oct 21 14:06:49 Mac-Pro OSInstaller[219]: Storage system check exit code is 0.
Oct 21 14:06:51 Mac-Pro OSInstaller[219]: Repair completed successfully.
Oct 21 14:06:53 Mac-Pro OSInstaller[219]: Set use ROSV paths to YES.
Oct 21 14:06:53 Mac-Pro OSInstaller[219]: SUPreferenceManager: Service connection invalidated!
Oct 21 14:06:53 Mac-Pro OSInstaller[219]: SUPreferenceManager: Connection proxy failure with error:Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.softwareupdated was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.softwareupdated was invalidated: failed at lookup with error 3 - No such process.}
Oct 21 14:07:18 Mac-Pro OSInstaller[219]: Did not move file from: /Volumes/macOS - Data - Data - Data - Data/private to: /Volumes/macOS - Data - Data - Data - Data/Previous System/private
    Reason: “private” couldn’t be moved to “Previous System” because an item with the same name already exists.
Oct 21 14:07:18 Mac-Pro OSInstaller[219]: Did not move file from: /Volumes/macOS - Data - Data - Data - Data/Previous System to: /Volumes/macOS - Data - Data - Data - Data/Previous System/Previous System
    Reason: “Previous System” couldn’t be moved to “Previous System”.
Oct 21 14:07:18 Mac-Pro OSInstaller[219]: System Reaper: Archiving previous system logs to /Volumes/macOS - Data - Data - Data - Data/private/var/db/PreviousSystemLogs.cpgz
Oct 21 14:07:18 Mac-Pro OSInstaller[219]: Reaping 1 of 4
Oct 21 14:07:18 Mac-Pro OSInstaller[219]: Reaping 2 of 4
Oct 21 14:07:18 Mac-Pro OSInstaller[219]: Reaping 3 of 4
Oct 21 14:07:18 Mac-Pro OSInstaller[219]: Reaping 4 of 4
Oct 21 14:07:19 Mac-Pro OSInstaller[219]: System Reaper: free space before: 336.81 GB
Oct 21 14:07:19 Mac-Pro OSInstaller[219]: System Reaper: free space after : 336.81 GB
Oct 21 14:07:19 Mac-Pro OSInstaller[219]: System Reaper: free space diff  : Zero KB
Oct 21 14:07:19 Mac-Pro OSInstaller[219]: Free space is enough, will continue install.
Oct 21 14:07:21 Mac-Pro OSInstaller[219]: Will try to attach log to: /Volumes/macOS - Data - Data - Data - Data/macOS Install Data/ia.log
Oct 21 14:07:21 Mac-Pro OSInstaller[219]: Waking up update brain
Oct 21 14:07:23 Mac-Pro OSInstaller[219]: MSU: Starting preflight personalize
Oct 21 14:07:23 Mac-Pro OSInstaller[219]: MSU: Starting preflight FDR
Oct 21 14:07:23 Mac-Pro OSInstaller[219]: MSU: Starting prepare
Oct 21 14:07:23 Mac-Pro mobileassetd[191]: SUPreferenceManager: Service connection invalidated!
Oct 21 14:07:23 Mac-Pro mobileassetd[191]: SUPreferenceManager: Connection proxy failure with error:Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.softwareupdated was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.softwareupdated was invalidated: failed at lookup with error 3 - No such process.}
Oct 21 14:07:23 Mac-Pro mobileassetd[191]: SUPreferenceManager: Service connection invalidated!
Oct 21 14:07:23 Mac-Pro mobileassetd[191]: SUPreferenceManager: Connection proxy failure with error:Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.softwareupdated was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.softwareupdated was invalidated: failed at lookup with error 3 - No such process.}
Oct 21 14:07:23 Mac-Pro mobileassetd[191]: SUPreferenceManager: Service connection invalidated!
Oct 21 14:07:23 Mac-Pro mobileassetd[191]: SUPreferenceManager: Connection proxy failure with error:Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.softwareupdated was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.softwareupdated was invalidated: failed at lookup with error 3 - No such process.}
Oct 21 14:07:27 Mac-Pro Installer Progress[59]: Status is "About 28 minutes remaining…"
Oct 21 14:08:27 Mac-Pro Installer Progress[59]: Status is "About 27 minutes remaining…"
Oct 21 14:09:27 Mac-Pro Installer Progress[59]: Status is "About 26 minutes remaining…"
Oct 21 14:10:27 Mac-Pro Installer Progress[59]: Status is "About 25 minutes remaining…"
Oct 21 14:11:27 Mac-Pro Installer Progress[59]: Status is "About 24 minutes remaining…"
Oct 21 14:12:27 Mac-Pro Installer Progress[59]: Status is "About 23 minutes remaining…"
Oct 21 14:13:27 Mac-Pro Installer Progress[59]: Status is "About 22 minutes remaining…"
Oct 21 14:13:58 Mac-Pro OSInstaller[219]: ------- Install Failed -------
Oct 21 14:13:58 Mac-Pro OSInstaller[219]: Operation: Install Mobile Software Update failed, Failure Reason: Error Domain=com.apple.osinstall Code=-81 "An error occurred preparing the software update." UserInfo={NSLocalizedDescription=An error occurred preparing the software update., NSUnderlyingError=0x6000011554a0 {Error Domain=MobileSoftwareUpdateErrorDomain Code=53 "Splat global ticket failed to verify" UserInfo={target_update=23A344, NSLocalizedDescription=Splat global ticket failed to verify, NSUnderlyingError=0x600001155ec0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}}}
Oct 21 14:13:58 Mac-Pro OSInstaller[219]: Flushed install.log has been flushed to /Volumes/Update/install-log-1697897638.log
Oct 21 14:13:58 Mac-Pro OSInstaller[219]: Symlinked /Volumes/Update/install-log-latest.log -> /Volumes/Update/install-log-1697897638.log
Oct 21 14:13:58 Mac-Pro OSInstaller[219]: Removing incomplete system volume

 

[stephengrenfell]

@stephengrenfell do you know how to find your Open Core config.plist? If so, could you please post it?

EDIT: I just noticed that you can't access the OC extended menu. Please shutdown, reset NVRAM and test again.

I can access the OC extended menu, just need to use USB keyboard.

Tried shutdown, reset NVRAM. Same Error messages appear after 5 minutes. Wake up problem resolved however.

config.plist in attached zip

 

[deeveedee]

I can access the OC extended menu, just need to use USB keyboard.

Tried shutdown, reset NVRAM. Same Error messages appear after 5 minutes. Wake up problem resolved however.

config.plist in attached zip

config.plist looks ok, so you've selected the correct options in OCLP GUI. I don't have any further advice and don't have your Mac to test. Hopefully someone else can chime in. Maybe OCLP 1.1.0 will help? Not sure.

 

[stephengrenfell]

config.plist looks ok, so you've selected the correct options in OCLP GUI. I don't have any further advice and don't have your Mac to test. Hopefully someone else can chime in. Maybe OCLP 1.1.0 will help? Not sure.

OK. Thanks for your help.

Wake up isn't solved however. Even with "Prevent automatic sleeping when the display is off" set to never and hard disks set to never hibernate. If the screen is off (due to inactivity) after a certain amount of time, the only solution is forced shutdown by holding the power-on button.

 

[Styluslover]

Hi all

I've just wiped / updated my aging 2012 iMac with Open Core - and for the most part it's very happy with Ventura. However the part that isn't working is fairly vital - and that's GPU acceleration when using Adobe products. I am presuming the GPU drivers added post-install are missing something subtle. Video within Premiere plays back as green with some digital artifacts - switch off the acceleration and the picture reappears. But this can't be solved in Media Encoder.

In terms of the OS / playing video back in other video players apps like VLC or QuickTime Pro is fine.

Anyone else come across this? This with an NVIDIA GeForce GTX 680MX 2GB system (Mac 13, 2 - 3.4Ghz Quad core i7)

Otherwise I guess it's up to upgrade!

Thanks.

 

[deeveedee]

OK. Thanks for your help.

Wake up isn't solved however. Even with "Prevent automatic sleeping when the display is off" set to never and hard disks set to never hibernate. If the screen is off (due to inactivity) after a certain amount of time, the only solution is forced shutdown by holding the power-on button.

Now that you're running an unsupported version of macOS on your Mac, there will be issues. Review this and watch it for updates. Also review the GitHub commits occasionally to see if Devs have checked-in fixes for any of your issues. Hopefully others here with your Mac can offer assistance.

EDIT: Also, now that you are using Open Core, some of the Dortania advice that applied to hackintoshes may apply to your Mac. Review this for advice (including pmsettings and Energy Saver settings) that may help. You will need to distinguish between the advice applicable only to hackintoshes and that which is relevant to your Mac. You will also need to distinguish between advice specific to various Mac SMBIOS Models to be sure you're applying suggestions relevant to your Mac.

 

[stephengrenfell]

Now that you're running an unsupported version of macOS on your Mac, there will be issues. Review this and watch it for updates. Also review the GitHub commits occasionally to see if Devs have checked-in fixes for any of your issues. Hopefully others here with your Mac can offer assistance.

EDIT: Also, now that you are using Open Core, some of the Dortania advice that applied to hackintoshes may apply to your Mac. Review this for advice (including pmsettings and Energy Saver settings) that may help. You will need to distinguish between the advice applicable only to hackintoshes and that which is relevant to your Mac. You will also need to distinguish between advice specific to various Mac SMBIOS Models to be sure you're applying suggestions relevant to your Mac.

For the moment as suggested on the Troubleshooting page I have set hibernatemode to 0 using "sudo pmset -a hibernatemode 0".

Hibernate / Wake Up was working perfectly Ok until earlier today I "downgraded" OCLP from 1.01 to 0.6.8

Many thanks for your help anyway.

 

[deeveedee]

For the moment as suggested on the Troubleshooting page I have set hibernatemode to 0 using "sudo pmset -a hibernatemode 0".

Hibernate / Wake Up was working perfectly Ok until earlier today I "downgraded" OCLP from 1.01 to 0.6.8

Many thanks for your help anyway.

The downgrade and then upgrade of OCLP should not have resulted in any "permanent" errors. Try Resetting NVRAM again. Stay patient and keep experimenting. You'll be learning and finding solutions with the rest of us.

EDIT: OCLP generates an Open Core EFI and post-install patches that are customized to each Mac Model. Solutions that work for one model may or may not work for another. Always have a way to recover to a previously known (and hopefully working) state before experimenting.

EDIT2: I almost always add a new APFS volume for experimentation, keeping my current macOS volume safe and untouched in a separate APFS Volume. Application of OCLP post-install patches is unique to each APFS volume. In my experiments, it is not unusual for me to have different versions of OCLP post-install patches applied to different APFS volumes. I'm not suggesting that you do this unless you know what you're doing (or don't mind screwing up, deleting your APFS volume and starting again), but it is very useful to preserve a "working" volume while experimenting in another.

EDIT3: This goes without saying, but I'll say it anyway. We're all on the same team and we're doing our best to help each other. If any of us tries the advice of another, it's our own responsibility to vet the advice and then to test in a way that does not risk our Mac and our data and it's our own responsibility to have a way to recover if necessary.

 

[RK78]

Basic question: the USB drive, now named Install macOS Ventura, is completely formatted and ready. My current OS is High Sierra 10.13.6, which I want to keep as is and install the Ventura to an already created empty APFS formatted partition.

From the directions at https://dortania.github.io/OpenCore-Legacy-Patcher/BOOT.html

the next step would be to
Now that you've loaded OpenCore, "select Install macOS":

This will be the OpenCore Picker

Since I definitely do not want to install Ventura over the High Sierra volume, how can I be certain to select that empty partition to install the Ventura to?

 

[davidlv]

Basic question: the USB drive, now named Install macOS Ventura, is completely formatted and ready. My current OS is High Sierra 10.13.6, which I want to keep as is and install the Ventura to an already created empty partition.

From the directions at https://dortania.github.io/OpenCore-Legacy-Patcher/BOOT.html

the next step would be to
Now that you've loaded OpenCore, "select Install macOS":

This will be the OpenCore Picker

Since I definitely do not want to install Ventura over the High Sierra volume, how do I select that empty partition to install the Ventura to?

First, see the post # 2472 on the macOS Sonoma on Unsupported Macs thread. About the preboot partition corruption in High Sierra, and the in answer to how to select the target drive, See post # 2,554 in the macOS Sonoma on Unsupported Macs. I posted an answer to a very similar question there.
Have you actually read the OCLP instructions? I would think that you can easily find the answer there.

https://forums.macrumors.com/threads/macos-14-sonoma-on-unsupported-macs-thread.2391630/page-104?post=32651517#post-32651517

OpenCore Legacy Patcher

Experience macOS just like before

dortania.github.io

 

[rehkram]

See post # 2,554 in the macOS Sonoma on Unsupported Macs. I posted an answer to a very similar question there.
Have you actually read the OCLP instructions? I would think that you can easily find the answer there.

https://forums.macrumors.com/threads/macos-14-sonoma-on-unsupported-macs-thread.2391630/page-104?post=32651517#post-32651517

OpenCore Legacy Patcher

Experience macOS just like before

dortania.github.io

Spoiler: The answer is the installer will always pause and ask you to select where you want to install it. Just select your new empty partition. I had the same question the first time I did it.

 

[deeveedee]

Basic question: the USB drive, now named Install macOS Ventura, is completely formatted and ready. My current OS is High Sierra 10.13.6, which I want to keep as is and install the Ventura to an already created empty APFS formatted partition.

Unless you know what you're doing, having High Sierra and Big Sur or newer in your Mac at the same time will be a problem Search to learn more. I never have a HS disk/volume in my Mac while tesing Big Sur or newer macOS.

EDIT: One of the problems with checking this forum on my phone - didn't see davidlv and rehkram excellent answers. Sorry for the duplication.

EDIT2: @RK78 My preference is to keep a disk dedicated to High Sierra (the last version of macOS that runs natively on my Mac) and I have a completely separate physical disk for Big Sur, Monterey, Ventura and Sonoma testing. I physically swap disks so that I never have the HS and the new unsupported versions of macOS installed simultaneously.

 

[davidlv]

Unless you know what you're doing, having High Sierra and Big Sur or newer in your Mac at the same time will be a problem Search to learn more. I never have a HS disk/volume in my Mac while tesing Bog Sur or newer macOS.

Do a search for "preboot partition". Second one down; @deeveedee is right, having HS there is maybe a No-No, probably better to wipe the disk with the disk utility on the Ventura USB installer disk. MUST have a good backup in that case!

 

[erikkfi]

Hi folks, I'm having sudden, terrible trouble with my Ventura install and I'm all out of tinkering options I can think of to get it going.

Summary: My MacBookPro11,2 (mid-2014 w/ integrated graphics only) turns on and the backlight comes on but there is no video for 5-6 minutes, after which it finally shows a folder icon with a question mark. At that point I can try to boot from a bootable USB drive made in OCLP, but the system doesn't behave as expected. When I insert the stick, after exactly 2.5 minutes it shows the bootable partitions of the USB drive, and I have like ten seconds to choose one or the system will go back to a blank screen and be non-responsive. Even if I do choose one in time, the system restarts itself rather than actually booting from the USB stick. It's quite a bad situation and I'm all out of ideas.

I think OCLP is "to blame" because if I take the drive out of the machine, it starts behaving normally with regard to external USB drives and everything is just faster. I don't know what went wrong; maybe my Mac installed an update overnight the other day that hosed the machine?

I'm basically asking for any ideas before I cut my losses and recycle this otherwise perfectly fine old computer.

 

[deeveedee]

I'm basically asking for any ideas before I cut my losses and recycle this otherwise perfectly fine old computer.

I didn't follow your summary, so forgive what are probably remedial questions. Is the behavior that you are describing after you have installed Ventura 13.6 and now you observe your issues when attempting to boot/run Ventura 13.6? If so, are you booting your newly installed Ventura 13.6 with the Open Core EFI that you created with OCLP's "Build and Install Open Core?"

Also, what version of OCLP? Are you an experienced OCLP user (have you previously used OCLP to successfully install/boot an unsupported version of macOS)?

 

[davidlv]

Hi folks, I'm having sudden, terrible trouble with my Ventura install and I'm all out of tinkering options I can think of to get it going.

Summary: My MacBookPro11,2 (mid-2014 w/ integrated graphics only) turns on and the backlight comes on but there is no video for 5-6 minutes, after which it finally shows a folder icon with a question mark. At that point I can try to boot from a bootable USB drive made in OCLP, but the system doesn't behave as expected. When I insert the stick, after exactly 2.5 minutes it shows the bootable partitions of the USB drive, and I have like ten seconds to choose one or the system will go back to a blank screen and be non-responsive. Even if I do choose one in time, the system restarts itself rather than actually booting from the USB stick. It's quite a bad situation and I'm all out of ideas.

I think OCLP is "to blame" because if I take the drive out of the machine, it starts behaving normally with regard to external USB drives and everything is just faster. I don't know what went wrong; maybe my Mac installed an update overnight the other day that hosed the machine?

I'm basically asking for any ideas before I cut my losses and recycle this otherwise perfectly fine old computer.

Can you try to Shut down the Mac and then boot the Mac holding the Option key down?
If you see an EFI icon (OCLP installed) use the Tab key to select it and click on that, then when it shows your internal disk, use the tab key to select that and click on it.
What happens?
Whatever, don't recycle that otherwise perfectly fine old computer! It is possible to get it working.
Of course, if you have the cash and want to buy a M2 MBA, go ahead, you will not regret it. Fantastic computer.
(Ship the old one to me?) 😀😀

 

[erikkfi]

If so, are you booting your newly installed Ventura 13.6 with the Open Core EFI that you created with OCLP's "Build and Install Open Core?"

No problem, thanks for replying. I used OCLP to install Ventura back in December of last year and it's been fine since then; every time I update the OS I know I need to launch into OCLP and reapply patches.

As for the version of OCLP, I'm not sure since I can't get into the system. I hadn't updated it for some time since it was working well. I'd guess I was on .5 or .6, somewhere in there.

The question quoted above I don't really know how to answer. I'm just... trying to boot and nothing is happening. Upon boot I always had to select which drive I wanted to boot from even though there was only one option; this was a small quirk I learned to live with, and I think this may be the EFI you were talking about. But just to reiterate: this is not a newly-installed Ventura. This is a Ventura install that began last December and had been working fine until two days ago.

 

[erikkfi]

Can you try to Shut down the Mac and then boot the Mac holding the Option key down?
If you see an EFI icon (OCLP installed) use the Tab key to select it and click on that, then when it shows your internal disk, use the tab key to select that and click on it.
What happens?

Pressing Option does nothing. It's supposed to call up the boot picker, right? The screen just stays black (w/ backlight on) for 7-8 minutes even if the Option key is pressed the entire time (don't worry - I used a weight to hold the key down for that long). Then I hear the boot chime and presumably it just resets itself. No boot picker ever appears.

The only way I seem to be able to get one to appear is to let it try to start up and get to the point where there's a folder question mark icon, then insert a bootable USB drive, quickly select that option to boot from, but unfortunately it just resets itself and never boots from the external drive.

At this point I feel like what I need is to be able to erase this hard drive and start over with a fresh install, but I can't think of any way to do that with the puzzle pieces I have. I know that the external USB boot process works fine if I take the SSD out. Longshot, but... I don't suppose it's safe to insert an SSD into the empty slot on the motherboard after getting to the install screen from the bootable USB drive (i.e., hot-swapping)?

 

[deeveedee]

As for the version of OCLP, I'm not sure since I can't get into the system. I hadn't updated it for some time since it was working well. I'd guess I was on .5 or .6, somewhere in there.

Lots of OCLP improvements and fixes Since .5 or .6. Diagnosing a problem with an older OCLP may be difficult, especially since the fixes in .6, .7 and .8 were for Ventura.

EDIT: Just want to report that power management with MBP6,2 / Ventura 13.6 is PERFECT. Fan hardly runs, temps are cool, sleep/wake is flawless. Devs - whatever you did with MBP6,2, keep doing it! Well done.

Running Ventura 13.6 post-install patches with OCLP 0.6.8. Open Core EFI: Upgraded to Open Core 0.9.5.

 

[davidlv]

Hi folks, I'm having sudden, terrible trouble with my Ventura install and I'm all out of tinkering options I can think of to get it going.

Summary: My MacBookPro11,2 (mid-2014 w/ integrated graphics only) turns on and the backlight comes on but there is no video for 5-6 minutes, after which it finally shows a folder icon with a question mark. At that point I can try to boot from a bootable USB drive made in OCLP, but the system doesn't behave as expected. When I insert the stick, after exactly 2.5 minutes it shows the bootable partitions of the USB drive, and I have like ten seconds to choose one or the system will go back to a blank screen and be non-responsive. Even if I do choose one in time, the system restarts itself rather than actually booting from the USB stick. It's quite a bad situation and I'm all out of ideas.

I think OCLP is "to blame" because if I take the drive out of the machine, it starts behaving normally with regard to external USB drives and everything is just faster. I don't know what went wrong; maybe my Mac installed an update overnight the other day that hosed the machine?

I'm basically asking for any ideas before I cut my losses and recycle this otherwise perfectly fine old computer.

Can you tell us what you mean by "if I take the drive out of the machine"? Do you mean take the internal SSD drive out of the MBP? It sounds to me like the internal drive (is that an SSD or a HDD?) is going bad. Without trying to install a new SSD it may be difficult to diagnose the real issue. Not sure if the internal SSD is replaceable or not.
Edit: This URL indicates it is possible to upgrade or replace the internal SSD.

How to Upgrade Retina MacBook Pro SSD Storage: 15-Inch: EveryMac.com

How to instructions and video to upgrade the SSD storage in the 2012, 2013, 2014 and 2015 15-Inch Retina MacBook Pro models (A1398).

everymac.com

Specifically, "third-parties, like site sponsor OWC have released a 6 Gb/s SATA-based SSD upgrade with a compatible connector for the "Mid-2012" and "Early 2013" models and another PCIe 2.0-based flash SSD with a compatible connector for the "Late 2013" and subsequent MacBook Pro models."

 

[erikkfi]

Can you tell us what you mean by "if I take the drive out of the machine"?

It means if I just run the machine without an SSD inside, suddenly the booting functionality works "normally" as in it quickly obeys pressing the option key to get to the boot selector. Obviously it doesn't properly boot in this condition since there's no drive.

Slight progress on my end! I installed OpenCore to a USB drive and was able to actually get it to do something! I was able to get the middle option working in this screenshot and access OpenShell.efi. It's responding to text input and everything. Does this do anything for me? Can I use command line to try to run patches on my system or something?

 

[deeveedee]

Slight progress on my end! I installed OpenCore to a USB drive and was able to actually get it to do something! I was able to get the middle option working in this screenshot and access OpenShell.efi. It's responding to text input and everything. Does this do anything for me? Can I use command line to try to run patches on my system or something?

If this is a test for us, you're doing a great job. Please include the version of OCLP (Open Core Legacy Patcher, different from Open Core) that you are using to "Build and Install Open Core" to the USB thumb drive. Do your best to leave no room for us having to guess. Thanks.

EDIT: If you are not using OCLP 0.6.8 or 1.0.1, please explain why.