Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.

thinkinginventor

macrumors newbie
Oct 28, 2022
20
7
Report, Installed Ventura on Mac Pro 2013.

-Core 1 is maxed out solid red "uh oh"
-restoring with migrate assistant crashes Ventura where I have to reinstall it. Tried it Twice.
-What is this odd menu power of video card etc.
Tired it ejected on the the GPU's I had to run the open core post install to get it back.

Anywho any ideas, I think the core thing is annoying me more. System P. Menu is horrible!

Cheers

PS Performance seem good maybe better then Monterey. Core 1 thing is annoying my OCD lol.

Feel like its running hotter
I zapped the pram and it crashed lol. Reinstalling Monterey. I might even go back on m1 been buggy as hell on that too.
 

startergo

macrumors 601
Sep 20, 2018
4,786
2,184
This is really weird. I have several disks, but Ventura can only see the disk it is installed on. Nothing else in dish utility. Anybody has seen this issue?
 

MP39

macrumors member
Aug 6, 2016
54
29
Reporting successful install Ventura on Mac Pro 5,1 using OC 0.5.1. Had some trouble with screen going blank on final boot of install -- even after following prior directions. Ended up swapping my AMD Radeon HD 7950 graphics card for an older NVIDIA GeForce GTX 770 4GB and it worked fine after. Ventura seems very responsive. Impressed so far.

Also, got this idea to swap cards after taking the NVMe drive over to my Mac Pro 3,1 with same graphics card and it booted fine with OC 0.5.1. So, I can share as well that preliminarily, my Mac Pro 3,1 is running Ventura just fine as well. It seemed speedy too! I need to officially go and do an install all the way through to double confirm.

Cheers to the developers...we know this is not possible without you...thank you! 🤗
 

Attachments

  • Screenshot 2022-10-30 at 10.03.49 PM.png
    Screenshot 2022-10-30 at 10.03.49 PM.png
    47.7 KB · Views: 78
Last edited:

plugsnpixels

macrumors regular
Jul 10, 2008
115
76
LA area
Is the USB Installer machine specific?

I downloaded Ventura and created a USB installer using the Opencore patcher and installed it on my MacBook Air, can I use this same usb installer for my iMac?
In my (early) experience with OCLP, I moved a USB among different Mac models. On the non-original-install models, OCLP knew what happened and offered to rebuild Open Core for each differing model (as I recall).

So ideally you'd build the USB on the specific target system itself. And as someone else posted, download the Ventura installer just once and move it from machine to machine for the USB build.
 
  • Like
Reactions: Ausdauersportler

nekton1

macrumors 65816
Apr 15, 2010
1,000
731
Asia
Reporting successful install Ventura on Mac Pro 5,1 using OC 0.5.1. Had some trouble with screen going blank on final boot of install -- even after following prior directions. Ended up swapping my AMD Radeon HD 7950 graphics card for an older NVIDIA GeForce GTX 770 4GB and it worked fine after. Ventura seems very responsive. Impressed so far.

Also, got this idea to swap cards after taking the NVMe drive over to my Mac Pro 3,1 with same graphics card and it booted fine with OC 0.5.1. So, I can share as well that preliminarily, my Mac Pro 3,1 is running Ventura just fine as well. It seemed speedy too! I need to officially go and do an install all the way through to double confirm.

Cheers to the developers...we know this is not possible without you...thank you! 🤗
On the 3,1 and 4,1 and 5,1, there seems to be some issue with the GPU drivers in the boot install process. With my Mac-rom flashed RX580, the 3,1 screen goes black at about 10 minutes into the install which may or may not still be proceeding. Hopefully, the devs can figure out a solution.
 
  • Like
Reactions: MP39

nekton1

macrumors 65816
Apr 15, 2010
1,000
731
Asia
Created a new USB installer with 0.5.1 for a MBP 2016 (13,3) and booted from patched EFi boot but same problem as with MP3,1; installer progress bar moves about 1 cm and then connected Apple TB 27" screen goes black and cannot see anything. Cannot use internal display because of infamous problem with internal screen flex cable that Apple refuses to fix under warranty and wants $800 to fix otherwise.
No progress today.
 

Marty56

macrumors member
May 13, 2019
48
34
While creating the installer USB Stick I am receiving the following error

Error: 2022-10-31 09:23:12.756 OCLP-Helper[9946:346026] Starting...

Erasing disk: 0%... 10%... 20%... 30%... 100%

IA app name cookie write failed

The bless of the installer disk failed.

2022-10-31 09:28:00.656 OCLP-Helper[9946:346026] Done

Any idea what's wrong?
 

Ausdauersportler

macrumors 603
Nov 25, 2019
5,001
5,804
While creating the installer USB Stick I am receiving the following error

Error: 2022-10-31 09:23:12.756 OCLP-Helper[9946:346026] Starting...

Erasing disk: 0%... 10%... 20%... 30%... 100%

IA app name cookie write failed

The bless of the installer disk failed.

2022-10-31 09:28:00.656 OCLP-Helper[9946:346026] Done

Any idea what's wrong?
Yes, either the download is damaged or the USB thumb drive is. This type of message comes up once a day here (heavily underestimated). You might know the really obvious cure, if not search back the thread.
 

chris1111

macrumors 6502
Jul 8, 2015
418
1,004
Montréal Canada
While creating the installer USB Stick I am receiving the following error

Error: 2022-10-31 09:23:12.756 OCLP-Helper[9946:346026] Starting...

Erasing disk: 0%... 10%... 20%... 30%... 100%

IA app name cookie write failed

The bless of the installer disk failed.

2022-10-31 09:28:00.656 OCLP-Helper[9946:346026] Done

Any idea what's wrong?
Probably the SIP is not disable?
 

kocoman

macrumors 6502
Dec 26, 2007
308
38
I am trying CryptexFixup on final version but it keeps giving me an error occured preparing the software update (macos update assistant), then hang at 18 min.. using osx-kvm in qemu..
 

mortiis

macrumors newbie
Jul 8, 2009
27
7
I installed Ventura on MacBookPro9,2 mid 2012 sometimes this error happen Mac OSX freeze and nothing move and the only solution I have to press the power button until it restarts
this is the error report I have someone can help me in this:

panic(cpu 0 caller 0xffffff800c2d3941): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds


WindowServer has not exited since first loaded


service: logd, total successful checkins in 52138 seconds: 5007, last successful checkin: 0 seconds ago


service: WindowServer, total successful checkins in 52090 seconds: 4991, last successful checkin: 120 seconds ago


service: opendirectoryd, total successful checkins in 52138 seconds: 5006, last successful checkin: 0 seconds ago


service: configd, total successful checkins in 52138 seconds: 5006, last successful checkin: 0 seconds ago





Panicked task 0xffffff9432050df8: 3 threads: pid 98: watchdogd


Backtrace (CPU 0), panicked thread: 0xffffffa296e890c8, Frame : Return Address


0xffffff8dc1adb590 : 0xffffff8008fedf9d mach_kernel : _handle_debugger_trap + 0x4ad


0xffffff8dc1adb5e0 : 0xffffff800915b786 mach_kernel : _kdp_i386_trap + 0x116


0xffffff8dc1adb620 : 0xffffff800914aa10 mach_kernel : _kernel_trap + 0x3e0


0xffffff8dc1adb670 : 0xffffff8008f88951 mach_kernel : _return_from_trap + 0xc1


0xffffff8dc1adb690 : 0xffffff8008fee27d mach_kernel : _DebuggerTrapWithState + 0x5d


0xffffff8dc1adb780 : 0xffffff8008fed929 mach_kernel : _panic_trap_to_debugger + 0x1a9


0xffffff8dc1adb7e0 : 0xffffff80097e0f93 mach_kernel : _panic_with_options + 0x89


0xffffff8dc1adb8d0 : 0xffffff800c2d3941 com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27


0xffffff8dc1adb8e0 : 0xffffff800c2d35e0 com.apple.driver.watchdog : __ZN10IOWatchdog35userspaceDisableUserspaceMonitoringEP8OSObjectPvP25IOExternalMethodArguments


0xffffff8dc1adb900 : 0xffffff800c2d26cd com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7f


0xffffff8dc1adba30 : 0xffffff80097544ca mach_kernel : _is_io_connect_method + 0x37a


0xffffff8dc1adbb90 : 0xffffff8009102319 mach_kernel : _iokit_server_routine + 0x38c9


0xffffff8dc1adbca0 : 0xffffff8008fc5999 mach_kernel : _ipc_kmsg_send + 0x569


0xffffff8dc1adbd50 : 0xffffff8008fde892 mach_kernel : _mach_msg_overwrite_trap + 0x4a2


0xffffff8dc1adbdc0 : 0xffffff8008fdef9a mach_kernel : _mach_msg2_trap + 0x3ba


0xffffff8dc1adbef0 : 0xffffff800912d02a mach_kernel : _mach_call_munger64 + 0x1ea


0xffffff8dc1adbfa0 : 0xffffff8008f88db6 mach_kernel : _hndl_mach_scall64 + 0x16


Kernel Extensions in backtrace:


com.apple.driver.watchdog(1.0)[A71DE745-044D-37DB-B730-8F8FFB66B24A]@0xffffff800c2d1000->0xffffff800c2d3fff





Process name corresponding to current thread (0xffffffa296e890c8): watchdogd


Boot args: keepsyms=1 debug=0x100 -lilubetaall ipc_control_port_options=0





Mac OS version:


22A380





Kernel version:


Darwin Kernel Version 22.1.0: Sun Oct 9 20:14:54 PDT 2022; root:xnu-8792.41.9~2/RELEASE_X86_64


Kernel UUID: BF7C9676-EF23-3E8D-A2E2-25DAC63091B6


roots installed: 0


KernelCache slide: 0x0000000008c00000


KernelCache base: 0xffffff8008e00000


Kernel slide: 0x0000000008cdc000


Kernel text base: 0xffffff8008edc000


__HIB text base: 0xffffff8008d00000


System model name: MacBookPro9,2 (Mac-6F01561E16C75D06)


System shutdown begun: NO


Panic diags file available: YES (0x0)


Hibernation exit count: 4





System uptime in nanoseconds: 52138717140292


Last Sleep: absolute base_tsc base_nano


Uptime : 0x00002f6b7db6e846


Sleep : 0x000025e12fa28eed 0x0000000030b7baf4 0x000025df91715cba


Wake : 0x000025e1397497f5 0x0000000030d71e28 0x000025e138afdb7b


Compressor Info: 4% of compressed pages limit (OK) and 7% of segments limit (OK) with 2 swapfiles and OK swap space


Zone info:


Zone map: 0xffffff8dc8bd1000 - 0xffffffadc8bd1000


. PGZ : 0xffffff8dc8bd1000 - 0xffffff8dcabd2000


. VM : 0xffffff8dcabd2000 - 0xffffff92973d1000


. RO : 0xffffff92973d1000 - 0xffffff9430bd1000


. GEN0 : 0xffffff9430bd1000 - 0xffffff98fd3d1000


. GEN1 : 0xffffff98fd3d1000 - 0xffffff9dc9bd1000


. GEN2 : 0xffffff9dc9bd1000 - 0xffffffa2963d1000


. GEN3 : 0xffffffa2963d1000 - 0xffffffa762bd1000


. DATA : 0xffffffa762bd1000 - 0xffffffadc8bd1000


Metadata: 0xffffff802c879000 - 0xffffff804c879000


Bitmaps : 0xffffff804c879000 - 0xffffff8052879000
 

georgeimac

macrumors member
Jun 13, 2021
48
10
Tried it again, with similar results. I don't know if the OWC drive has anything to do with it. Staying on Monterey for now until I can figure this out. Thanks everyone for your help.
 

georgeimac

macrumors member
Jun 13, 2021
48
10
Yes, either the download is damaged or the USB thumb drive is. This type of message comes up once a day here (heavily underestimated). You might know the really obvious cure, if not search back the thread.
I'm having issues moving to VENTURA on a MBP 15 11,4. USB EFI loads fine but when selecting upgrade it stalls on status bar. I'm suspicious that an upgrade to a non Apple SSD may be part of the issue or itself corrupted. My upgrade was to an OWC Aura 1 TB SSD. I remember when migrating to Monterey, I had to remove the OWC and put in the Apple SSD for the upgrade to complete. Could this be an issue with Ventura? Thank you for any help you can offer.
 

Ausdauersportler

macrumors 603
Nov 25, 2019
5,001
5,804
I'm having issues moving to VENTURA on a MBP 15 11,4. USB EFI loads fine but when selecting upgrade it stalls on status bar. I'm suspicious that an upgrade to a non Apple SSD may be part of the issue or itself corrupted. My upgrade was to an OWC Aura 1 TB SSD. I remember when migrating to Monterey, I had to remove the OWC and put in the Apple SSD for the upgrade to complete. Could this be an issue with Ventura? Thank you for any help you can offer.
My only idea:
You should update the firmware in case a new version has been published by Apple, check the first post how to do this. The method published by @startergo should work on non Apple SSD, too. Did this successfully a few days ago on my (Catalina supported) MBA 2012 with a third party SSD. Updating Catalina did not apply the firmware update, it did not even copy it to the EFI.
 

rehkram

macrumors 6502a
May 7, 2018
656
874
upstate NY
I'm having issues moving to VENTURA on a MBP 15 11,4. USB EFI loads fine but when selecting upgrade it stalls on status bar. I'm suspicious that an upgrade to a non Apple SSD may be part of the issue or itself corrupted. My upgrade was to an OWC Aura 1 TB SSD. I remember when migrating to Monterey, I had to remove the OWC and put in the Apple SSD for the upgrade to complete. Could this be an issue with Ventura? Thank you for any help you can offer.
Just an FYI, I have the same, or similar, OWC drive in my rMBP10,1, works fine. Disk Utility tells me the model I have is an Aura Pro S MB258, 1TB

It's probably a different model in yours, my rMBP10,1's card connector is non standard. I've never had to put back the OEM card, all through Catalina, Big Sur, Monterey and now Ventura, and I don't understand why that would achieve anything. I do keep the OEM card in an OWC Envoy external enclosure, have Catalina on it so I can keep firmware up to date. See my signature in the spoiler below.
 
Last edited:

rehkram

macrumors 6502a
May 7, 2018
656
874
upstate NY
I installed Ventura on MacBookPro9,2 mid 2012 sometimes this error happen Mac OSX freeze and nothing move and the only solution I have to press the power button until it restarts
this is the error report I have someone can help me in this:

panic(cpu 0 caller 0xffffff800c2d3941): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds

Have you tried booting a couple of times in safe mode? You may ask why: See the Monterey unsupported Macs thread, search for 'watchdog'
 

LordDeath

macrumors member
Feb 28, 2013
68
83
My only idea:
You should update the firmware in case a new version has been published by Apple, check the first post how to do this. The method published by @startergo should work on non Apple SSD, too. Did this successfully a few days ago on my (Catalina supported) MBA 2012 with a third party SSD. Updating Catalina did not apply the firmware update, it did not even copy it to the EFI.

My MBA 2012 is still running firmware 421, I don't have the original SSD anymore and manually installing Catalina on another partition did not flash the new firmware.
Can I use startergo's method even when I am not running Catalina anymore, or would it cause issues if I try this from a system running Monterey or Ventura booted with OCLP?
 

MacPeet

macrumors member
Jul 26, 2018
57
115
germany
Note to developers:
My MacPro3,1 with 0.5.0 alpha works very well with Monterey and Ventura. The problems regarding USB and thus BT with Ventura are known, which you also mentioned. The Nvidia Quadro doesn't cause any problems here, the rollback of the kext's works.
Today I tried current 0.5.2, Monterey works, but Ventura gets stuck with USB messages in Verbose. I'm back to 0.5.0.
I hope it helps in further improving the USB issue.
 
  • Like
Reactions: macinfo and Tockman

vince22

macrumors 6502a
Oct 12, 2013
648
627
I installed Ventura on MacBookPro9,2 mid 2012 sometimes this error happen Mac OSX freeze and nothing move and the only solution I have to press the power button until it restarts
this is the error report I have someone can help me in this:

panic(cpu 0 caller 0xffffff800c2d3941): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds


WindowServer has not exited since first loaded


service: logd, total successful checkins in 52138 seconds: 5007, last successful checkin: 0 seconds ago


service: WindowServer, total successful checkins in 52090 seconds: 4991, last successful checkin: 120 seconds ago


service: opendirectoryd, total successful checkins in 52138 seconds: 5006, last successful checkin: 0 seconds ago


service: configd, total successful checkins in 52138 seconds: 5006, last successful checkin: 0 seconds ago





Panicked task 0xffffff9432050df8: 3 threads: pid 98: watchdogd


Backtrace (CPU 0), panicked thread: 0xffffffa296e890c8, Frame : Return Address


0xffffff8dc1adb590 : 0xffffff8008fedf9d mach_kernel : _handle_debugger_trap + 0x4ad


0xffffff8dc1adb5e0 : 0xffffff800915b786 mach_kernel : _kdp_i386_trap + 0x116


0xffffff8dc1adb620 : 0xffffff800914aa10 mach_kernel : _kernel_trap + 0x3e0


0xffffff8dc1adb670 : 0xffffff8008f88951 mach_kernel : _return_from_trap + 0xc1


0xffffff8dc1adb690 : 0xffffff8008fee27d mach_kernel : _DebuggerTrapWithState + 0x5d


0xffffff8dc1adb780 : 0xffffff8008fed929 mach_kernel : _panic_trap_to_debugger + 0x1a9


0xffffff8dc1adb7e0 : 0xffffff80097e0f93 mach_kernel : _panic_with_options + 0x89


0xffffff8dc1adb8d0 : 0xffffff800c2d3941 com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27


0xffffff8dc1adb8e0 : 0xffffff800c2d35e0 com.apple.driver.watchdog : __ZN10IOWatchdog35userspaceDisableUserspaceMonitoringEP8OSObjectPvP25IOExternalMethodArguments


0xffffff8dc1adb900 : 0xffffff800c2d26cd com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7f


0xffffff8dc1adba30 : 0xffffff80097544ca mach_kernel : _is_io_connect_method + 0x37a


0xffffff8dc1adbb90 : 0xffffff8009102319 mach_kernel : _iokit_server_routine + 0x38c9


0xffffff8dc1adbca0 : 0xffffff8008fc5999 mach_kernel : _ipc_kmsg_send + 0x569


0xffffff8dc1adbd50 : 0xffffff8008fde892 mach_kernel : _mach_msg_overwrite_trap + 0x4a2


0xffffff8dc1adbdc0 : 0xffffff8008fdef9a mach_kernel : _mach_msg2_trap + 0x3ba


0xffffff8dc1adbef0 : 0xffffff800912d02a mach_kernel : _mach_call_munger64 + 0x1ea


0xffffff8dc1adbfa0 : 0xffffff8008f88db6 mach_kernel : _hndl_mach_scall64 + 0x16


Kernel Extensions in backtrace:


com.apple.driver.watchdog(1.0)[A71DE745-044D-37DB-B730-8F8FFB66B24A]@0xffffff800c2d1000->0xffffff800c2d3fff





Process name corresponding to current thread (0xffffffa296e890c8): watchdogd


Boot args: keepsyms=1 debug=0x100 -lilubetaall ipc_control_port_options=0





Mac OS version:


22A380





Kernel version:


Darwin Kernel Version 22.1.0: Sun Oct 9 20:14:54 PDT 2022; root:xnu-8792.41.9~2/RELEASE_X86_64


Kernel UUID: BF7C9676-EF23-3E8D-A2E2-25DAC63091B6


roots installed: 0


KernelCache slide: 0x0000000008c00000


KernelCache base: 0xffffff8008e00000


Kernel slide: 0x0000000008cdc000


Kernel text base: 0xffffff8008edc000


__HIB text base: 0xffffff8008d00000


System model name: MacBookPro9,2 (Mac-6F01561E16C75D06)


System shutdown begun: NO


Panic diags file available: YES (0x0)


Hibernation exit count: 4





System uptime in nanoseconds: 52138717140292


Last Sleep: absolute base_tsc base_nano


Uptime : 0x00002f6b7db6e846


Sleep : 0x000025e12fa28eed 0x0000000030b7baf4 0x000025df91715cba


Wake : 0x000025e1397497f5 0x0000000030d71e28 0x000025e138afdb7b


Compressor Info: 4% of compressed pages limit (OK) and 7% of segments limit (OK) with 2 swapfiles and OK swap space


Zone info:


Zone map: 0xffffff8dc8bd1000 - 0xffffffadc8bd1000


. PGZ : 0xffffff8dc8bd1000 - 0xffffff8dcabd2000


. VM : 0xffffff8dcabd2000 - 0xffffff92973d1000


. RO : 0xffffff92973d1000 - 0xffffff9430bd1000


. GEN0 : 0xffffff9430bd1000 - 0xffffff98fd3d1000


. GEN1 : 0xffffff98fd3d1000 - 0xffffff9dc9bd1000


. GEN2 : 0xffffff9dc9bd1000 - 0xffffffa2963d1000


. GEN3 : 0xffffffa2963d1000 - 0xffffffa762bd1000


. DATA : 0xffffffa762bd1000 - 0xffffffadc8bd1000


Metadata: 0xffffff802c879000 - 0xffffff804c879000


Bitmaps : 0xffffff804c879000 - 0xffffff8052879000
Hmm, currently have 2 of these 2012 Mid MacBookPro9,2 fresh install with Ventura 13.1beta for my kids, no issues here
OCLP 0.5.2n.
 

tokyogentleman

macrumors member
Sep 4, 2020
30
51
Tokyo
My MBA 2012 is still running firmware 421, I don't have the original SSD anymore and manually installing Catalina on another partition did not flash the new firmware.
Can I use startergo's method even when I am not running Catalina anymore, or would it cause issues if I try this from a system running Monterey or Ventura booted with OCLP?
you dont need the original ssd. i use aftermarket western digital ssd. install catalina on and extra ssd and let it upgrade the firmware.
 

djlauria

macrumors newbie
Oct 31, 2022
2
0
Is Firewire working correctly? Late 2012 Mac Mini, Ventura installation went perfectly but it does not recognize my Firewire audio device (Phonic Helix Board 12).
 

sl0wmotion

macrumors newbie
May 24, 2017
12
4
Macmini7,1 windowserver crashed around after running 20+ hours.

Was running OCLP 0.5.0 and installed Ventura a day before, crashed yesterday early morning.
Upgraded to OCLP 0.5.1, patched again, tested on USB boot then SSD EFI, and crashed today early morning.
Both crashes are from windowserver no response, and the Mac mini is freeze like a stone.

This Mac mini (16GB RAM, 512GB SSD, on Ethernet no Wifi, mainly as TM backup and file server with external RAID 1) has been serving me well for the past 8 years with no crash, so I don’t think it is hardware broken yet.

I stopped all the background tasks today (including iStats which I suspect), and will report how it goes.
Reboot, uninstall / reinstall iStat, re-inspect all the background tasks (and disable those old unused ones), run Amphetamine to ensure it does not sleep unexpectedly, and now it runs more than 29 hours without crash. 🤞🏻
Will report how it goes a few days later if it still keeps running.
 

Portiere

macrumors member
Sep 25, 2022
89
71
Is Firewire working correctly? Late 2012 Mac Mini, Ventura installation went perfectly but it does not recognize my Firewire audio device (Phonic Helix Board 12).
Yes, My firewire devices are connected to Mac mini by a Moshi Lynx device 4 usb2 ports and 2 firewire 800.
 

Attachments

  • SC.jpg
    SC.jpg
    105.5 KB · Views: 66
  • SC1.jpg
    SC1.jpg
    42.6 KB · Views: 57
  • Unknown.jpeg
    Unknown.jpeg
    4.3 KB · Views: 61
  • Like
Reactions: macinfo
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.