I didn't know you could do that. But I wouldn't do it anyway. I keep things as simple as possible to zoom-in quickly on single points of failure. USB key drives are cheap.
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
How are you communicating with the forum? From another Mac?
In order to get that MBP working, you need to have a USB Monterey start up disk made with OCLP 0.6.8 or even 0.4.11 installed. After you have that USB key drive, insert it and start up the MBP while holding the Option key. When you see the EFI icon, use the Tab key to select the EFI icon on the right (hoping it is for the USB) and hit enter. That should bring up another window, Tab to the USB installer and hit Enter.
After that use the Install Monterey option to do an overwrite of the Monterey system. (Don't use Disk Utility to format the internal drive! We want to save your data!)
Last edited:
"either RC2 or the final release."
The Mr. Macintosh site doesn't have anything with the version number 13.6.3, and as he is almost always up-to-date, I suspect the 22G430 13.6.3 we have (OTA for me) must be an RC.
The Developer Beta toggle was set to off in Software Update when OTA d/l 22G430. Only releases can occur with that setting. 🤷♂️ It remains set to off, btw. Time will tell? 🤔 22G430 runs perfectly w/OCLP v.1.2.1, here. 🤗
Last edited:
Hello
Macbook 11,3 Mid 2014 with Nvidia 750m and Ventura 13.6.1 with OCLP 1.2.1
every now and then , mediaanalysisd spike my cpu even when my OS is idle and fans starts to run at max speed - is that some of the limitations in the current status of OCLP or some bug that still not fixed related to my hardware ?
I tried to turn off icloud photos and I'm not using the photos app but the problem still exists, can it be disabled in a safe way or there is some workaround to get around this problem ?
Thank you
Macbook 11,3 Mid 2014 with Nvidia 750m and Ventura 13.6.1 with OCLP 1.2.1
every now and then , mediaanalysisd spike my cpu even when my OS is idle and fans starts to run at max speed - is that some of the limitations in the current status of OCLP or some bug that still not fixed related to my hardware ?
I tried to turn off icloud photos and I'm not using the photos app but the problem still exists, can it be disabled in a safe way or there is some workaround to get around this problem ?
Thank you
Sorry, I thought I was doing a "Like" for K two's post! I certainly do not "Like" your situation.
I don't know about that issue, but I have updated to 13.6.3 using the Software Update pane (iMac 15,1 & OCLP 1.2.1). That issue may be alleviated with the update, but then again those MBPs (model 11,3 etc) are finicky. Your choice on whether or not to attempt the update. (Make a good backup first!)
2 things to try, not in any special order: 1. Update to Ventura 13.6.3 OTA, 2. downgrade to OCLP 1.1, or 3. both
Aaaaand I've decided to give that double APFS volume idea a shot! A slightly smaller volume with a Monterey install (the highest this MacBookPro11,4 officially supports) and a bigger one I will install Ventura on. I even downloaded OCLP 1.1.0 just to be safe, and don't plan to update it to 1.2.1 at all.
Hi I successfully installed on my 2012 MBP but I get an out of device space error when trying to install OCLP to EFI partition on the hard drive. I mounted the EFI partition and it has a file named BootRecord and three folders named Apple, Boot and OC. I have no idea what I can safely delete in order to free some space. Any advice would be very much appreciated as right now I have to keep the USB thumb drive in the computer at all times.
"[Errno 28] No space left on device: '..../Build-Folder/OpenCore-Build/EFI/OC/config.plist' -> '/Volumes/EFI/EFI/OC/config.plist'")]
"[Errno 28] No space left on device: '..../Build-Folder/OpenCore-Build/EFI/OC/config.plist' -> '/Volumes/EFI/EFI/OC/config.plist'")]
Last edited:
Do you have oneof the wired Apple keyboards with 2 USB ports, one on each end? That keyboard has helped me get my iMac 15,1 from 2014 working several times, and my Bluetooth keyboard gets working again after the root patches are applied with OCLP.
thank you for your help , but I think 13.6.3 is only available for Macbook with M1-M3 processor .
I had in this morning my first crash log on 13.6.1 , and I don't know if it's related to medianalysesd ?
this is the crash log , can someone tell me whats going on ?
panic(cpu 2 caller 0xffffff8004995941): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds
WindowServer has not exited since first loaded
service: logd, total successful checkins in 442954 seconds: 44293, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins in 442900 seconds: 44277, last successful checkin: 120 seconds ago
service: opendirectoryd, total successful checkins in 442954 seconds: 44292, last successful checkin: 0 seconds ago
service: configd, total successful checkins in 442954 seconds: 44292, last successful checkin: 0 seconds ago
Panicked task 0xffffff94ec1999d8: 3 threads: pid 112: watchdogd
Backtrace (CPU 2), panicked thread: 0xffffff94ed253b30, Frame : Return Address
0xfffffffdfe8bf5b0 : 0xffffff8001670c7d mach_kernel : _handle_debugger_trap + 0x4ad
0xfffffffdfe8bf600 : 0xffffff80017c4f54 mach_kernel : _kdp_i386_trap + 0x114
0xfffffffdfe8bf640 : 0xffffff80017b4a67 mach_kernel : _kernel_trap + 0x3b7
0xfffffffdfe8bf690 : 0xffffff8001611971 mach_kernel : _return_from_trap + 0xc1
0xfffffffdfe8bf6b0 : 0xffffff8001670f5d mach_kernel : _DebuggerTrapWithState + 0x5d
0xfffffffdfe8bf7a0 : 0xffffff8001670607 mach_kernel : _panic_trap_to_debugger + 0x1a7
0xfffffffdfe8bf800 : 0xffffff8001ddba73 mach_kernel : _panic_with_options + 0x89
0xfffffffdfe8bf8f0 : 0xffffff8004995941 com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27
0xfffffffdfe8bf900 : 0xffffff80049955dc com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments + 0x2e
0xfffffffdfe8bf920 : 0xffffff80049946b9 com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7f
0xfffffffdfe8bfa50 : 0xffffff8001d52d2e mach_kernel : _is_io_connect_method + 0x37e
0xfffffffdfe8bfbb0 : 0xffffff8001771799 mach_kernel : _iokit_server_routine + 0x3609
0xfffffffdfe8bfcc0 : 0xffffff800164b09a mach_kernel : _ipc_kmsg_send + 0x41a
0xfffffffdfe8bfd60 : 0xffffff8001661e52 mach_kernel : _mach_msg_overwrite_trap + 0x592
0xfffffffdfe8bfdd0 : 0xffffff80016624d7 mach_kernel : _mach_msg2_trap + 0x3c7
0xfffffffdfe8bfef0 : 0xffffff800179a383 mach_kernel : _mach_call_munger64 + 0x1f3
0xfffffffdfe8bffa0 : 0xffffff8001611dd6 mach_kernel : _hndl_mach_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[BD08CE2D-77F5-358C-8F0D-A570540A0BE7]@0xffffff8004993000->0xffffff8004995fff
Process name corresponding to current thread (0xffffff94ed253b30): watchdogd
Boot args: keepsyms=1 debug=0x100 ipc_control_port_options=0 -nokcmismatchpanic
Mac OS version:
22G313
Kernel version:
Darwin Kernel Version 22.6.0: Wed Oct 4 21:25:26 PDT 2023; root:xnu-8796.141.3.701.17~4/RELEASE_X86_64
Kernel UUID: 6059599F-7994-349C-8DC6-03F3B60C83DE
roots installed: 0
KernelCache slide: 0x0000000001200000
KernelCache base: 0xffffff8001400000
Kernel slide: 0x00000000012dc000
Kernel text base: 0xffffff80014dc000
__HIB text base: 0xffffff8001300000
System model name: MacBookPro11,3 (Mac-2BD1B31983FE1663)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0
System uptime in nanoseconds: 442954916339227
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000192dd7a70a1da
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000000cac695d32 0x0000000000000000
Compressor Info: 19% of compressed pages limit (OK) and 15% of segments limit (OK) with 7 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff801f20c000 - 0xffffffa01f20c000
. PGZ : 0xffffff801f20c000 - 0xffffff802120d000
. VM : 0xffffff802120d000 - 0xffffff84eda0c000
. RO : 0xffffff84eda0c000 - 0xffffff868720c000
. GEN0 : 0xffffff868720c000 - 0xffffff8b53a0c000
. GEN1 : 0xffffff8b53a0c000 - 0xffffff902020c000
. GEN2 : 0xffffff902020c000 - 0xffffff94eca0c000
. GEN3 : 0xffffff94eca0c000 - 0xffffff99b920c000
. DATA : 0xffffff99b920c000 - 0xffffffa01f20c000
Metadata: 0xfffffffddafee000 - 0xfffffffdfafee000
Bitmaps : 0xfffffffdfafee000 - 0xfffffffdfdfee000
Extra : 0 - 0
macOS 13.6.2 is Apple Silicon exclusive, so far. 13.6.3 OTA Build 22G430 appears to be intel specific. The changing of the guard is underway.
🙃
I never have to update without a wired keyboard and a wired mouse. Getting into Bluetooth trouble while updating needs to be avoided at all cost.
(I still don't use BLE key and mouse on my Mac.)
OCLP precludes the need for a hard-wired k/b and mouse. The Spacebar upon seeing OpenCanopy on boot offers everything needed whether wired or BT.
OCLP precludes the need for a hard-wired k/b and mouse. The Spacebar upon seeing OpenCanopy on boot offers everything needed whether wired or BT.
Obvious, I missed out on this workflow. Thanks for your added correction.
Coming back to this thread to show you my newly created Folder (2023-11-26) on Desktop. macOS 13.6.1. Never seen these logos on Folders before in macOS Ventura or earlier releases of OS for the Mac.
Anybody recognize this 'strange' icon behavior?
Anybody recognize this 'strange' icon behavior?
After booting into macOS 13.6.1 this morning, all Folder icons are back to normal. Next time - if it may occur again - I'll collect the information you suggested. Thanks for now.
Last edited:
Big headache: two very frustrating install attempts yesterday and today to Mac Mini Mid-2010 4,1. Both installs errored out at approx 14 minutes with error software failed something...., don't remember the exact wording. Screen I'm brought to shows frozen MacOS Update Assistant with option beneath that to restart. Back in startup volume, seeing Ventura-Data volume on Desktop with approx 14GB used, so the install must have progressed at least to a certain extent.
Target drive has loads of empty space. Internet connection is good.
Not sure what to try next. Yesterday after trying a second install, the startup volume then showed Ventura-Data and Ventura Data-Data, which seems like the second install just reinstalled the first -Data. So don't want to simply repeat that. Nothing like this happened with the install to the iMac 10,1 some weeks ago using same procedure, but this time with new USB drive formatted for the Mini 4,1.
After today's failure did an SMC Reset, and yesterday a PRAM reset. Also before trying second install today, erased target drive.
Any help or suggestions appreciated.
Target drive has loads of empty space. Internet connection is good.
Not sure what to try next. Yesterday after trying a second install, the startup volume then showed Ventura-Data and Ventura Data-Data, which seems like the second install just reinstalled the first -Data. So don't want to simply repeat that. Nothing like this happened with the install to the iMac 10,1 some weeks ago using same procedure, but this time with new USB drive formatted for the Mini 4,1.
After today's failure did an SMC Reset, and yesterday a PRAM reset. Also before trying second install today, erased target drive.
Any help or suggestions appreciated.
Last edited:
Did a search for "MacOS Update Assistant". The first hit which is from ASC (MacOS Update Assistant frozen) https://discussions.apple.com/thread/252414874 gives a link to Mr. Macintosh https://mrmacintosh.com/big-sur-upgrade-not-enough-hd-space-serious-issue-possible-data-loss/, which is mainly concerned with the upgrade to Big Sur involving either not enough disk free space - how to recover free space, or dealing with File Vault enabled. Neither is my problem, since no File Vault and the drive in question is 270GB minus a little for formatting.
In any case, this is the frozen Update Assistant in question, and the error, or similar:
In any case, this is the frozen Update Assistant in question, and the error, or similar:
Last edited:
I have recenty updated my mac pro 5.1 from mojave to ventura using oc but Im having problems with my apple bluetooth keyboard in the bluetooth page on mac when I click on connect it comes up eith the 6 digit number to enter which I do on the keyboard and press enter the keyboard says connected in the bluetooth page but the apple keyboards green light keeps flashing then it disconnects
any help please?
thanks
any help please?
thanks
Last edited:
Specific version of OCLP (e.g. 0.6.8) and specific version of Ventura (e.g. 13.6.1) would be helpful. Also confirm the model of your Wi-Fi/Bluetooth card.