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 12 Monterey on Unsupported Macs Thread
- Thread starter khronokernel
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
The developers have repeatedly requested not to post the direct links to Nightlies. 🙅♂️
Last edited:
I see, I thought I was following the warning:
"Warning: These binaries should not be used without first consulting the CHANGELOG. Do not distribute these links in forums, instead direct to this file."
The wording is somewhat misleading because it reads like a no but yes. I did edit the link in the post related. On the funny side, since you quoted my original post including the wrong link, you might want to edit this one as well. 😃
Last edited:
If you had observed the developers on Discord and MacRumors you would know no doesn't mean yes. Posting the direct links just makes for unnecessary work for developers.
OCLP_044n runs flawless and better than expected on this most primitive of unsupported Macs.
Tested 12.3.1 on my late 2008 Unibody MacBook using OCLP 0.4.3. Two issues worth mentioning:
1) Messages crashes after a while for no reason.
2) Migration assistant works only the first time, during the Monterey installation phase. Any subsequent use of the Migration Assistant, after the install is finished, is practically useless. It starts as usual but keeps switching to user login screen with a "Setup User" account shown as well. I can login back to my account but the Migration Assistant hangs there. The only way to proceed is to Force Quit the Migration Assistant, and re start it. It comes back to where it was stuck and continues from there but within seconds goes back to the user login screen again. Needless to say, going through this Force Quit and re start hoopla is an unbearable way to deal with the problem.
1) Messages crashes after a while for no reason.
2) Migration assistant works only the first time, during the Monterey installation phase. Any subsequent use of the Migration Assistant, after the install is finished, is practically useless. It starts as usual but keeps switching to user login screen with a "Setup User" account shown as well. I can login back to my account but the Migration Assistant hangs there. The only way to proceed is to Force Quit the Migration Assistant, and re start it. It comes back to where it was stuck and continues from there but within seconds goes back to the user login screen again. Needless to say, going through this Force Quit and re start hoopla is an unbearable way to deal with the problem.
oclp 0.4.3 MacPro3.1 update Monterey 12.4 without problem great work developer..
Had to re-enroll into the Beta program to get the update. Went smooth.
Appears my display brightness HUD for my second monitor is working. No more overlap with main screen.<- Persists
macOS 12.4 + OCLP v0.4.4 = 👍 Nice work devs!
macOS 12.4 + OCLP v0.4.4 = 👍 Nice work devs!
Last edited:
Hello,
i have installed my favorite imac 7.1 to Monterey . Now I get an issue with the Bluetooth, BCM_4350C2 get no power on, there is no valid MAC adress. So far I have read, there is no Supoort for maverics, is this right?
And if yes, what can I do to get the Bluetooth connection works, is ther a USB Bluetooth dongle possible to use?
i have installed my favorite imac 7.1 to Monterey . Now I get an issue with the Bluetooth, BCM_4350C2 get no power on, there is no valid MAC adress. So far I have read, there is no Supoort for maverics, is this right?
And if yes, what can I do to get the Bluetooth connection works, is ther a USB Bluetooth dongle possible to use?
Last edited:
The latest OS your iMac supports, is indeed Mavericks (OS X 10.9). But is that what you mean? This thread covers installing Monterey (macOS 12) on unsupported Macs.
I upgraded to 12.4 while running OCLP 0.4.3 and post upgrade, at random times my machine would just freeze (didn't matter if woke up from sleep or running normal, just a few minutes into my session, lock up - no error message or anything, just the notice after booting that system recovered from issue). I saw above posts for OCLP 0.4.4 and decided to give that a try, installed and booted from new OCLP version with fingers crossed.
I mean, the BCM_4350C2 is not supported. I know the Supoort Ends with 10.9 but the iMAC runns well with 6 GB Ram, SSD and a newer CPU on Monterey. I have also a newer iMAC, but I Like the 24" format. So I try to leave the iMAC alive as long as possible.
Last edited:
The next release of OCLP will correct your Item#1 non-Metal issue. Migration Assistant works perfectly on a supported Mac, not sure if a fix for item#2 exists but MA does work sufficient on fresh installs.
I don't know if it's related to your mouse problem but I can confirm that firmware 426.0.0.0.0 was included with a late breaking security update for Catalina, see previous discussions on this thread. Several of us missed that update, having jumped to Big Sur and Monterey before the Catalina update was released.
To fix it I installed Catalina on an external SSD, booted it, picked up the security update via sys prefs > OTA software update. 426.0.0.0.0 installed fine. I'll be keeping Catalina around for the foreseeable future in case they release any more security updates for it containing new firmware.
I had the same issue when using Migration Assistant after installation, with no positive exceptions.
Since that I'm using CCC data-only cloning instead of Migration Assistant (doing this before installing macOS over it, but there was a report that first clean install, then CCC works as well).
Anyway would be better to be able to use the native Apple tool for migrating user data/apps/settings.
Well it appears my external display HUD bug still persists. Guess I didn't give my machine enough time to sit when I initially reported 🤷♂️
Last edited:
I've just found a fix for some problems I've been having with Magic keyboard 2 & mouse 2 not talking to my rMBP. I had the lightning charging cable for them plugged into my other Mac (mini) USB C port due to being short of USB old-style ports on the rMBP
This had always worked fine for charging them in the past.
Monterey 12.3 or 12.3.1 seemed to break it. In desperation I freed up one of the two USB ports on the rMBP and plugged an old style USB to lightning cable into it. I then plugged the lightning end into charging port of firstly the mouse 2 and then the keyboard 2. Both are now working fine. Weird, but I'm just happy to get them back.
This had always worked fine for charging them in the past.
Monterey 12.3 or 12.3.1 seemed to break it. In desperation I freed up one of the two USB ports on the rMBP and plugged an old style USB to lightning cable into it. I then plugged the lightning end into charging port of firstly the mouse 2 and then the keyboard 2. Both are now working fine. Weird, but I'm just happy to get them back.
My MacPro3,1 no problems with 12.4 Beta 1, everything works. Thanks and regards to the OCLP development team.
I think I found my reoccurring panics,
panic(cpu 2 caller 0xffffff80097d2943): Kernel trap at 0xffffff8009ab53ce, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000028, CR3: 0x00000003a207f12e, CR4: 0x00000000001626e0
RAX: 0x0000000000000000, RBX: 0xffffff8bb1913aa0, RCX: 0x0000000000000000, RDX: 0x0000000000000000
RSP: 0xffffffe576c7bd70, RBP: 0xffffffe576c7bdc0, RSI: 0xffffff90851192e0, RDI: 0x0000000000000000
R8: 0x0000000000000000, R9: 0x00000000000012f3, R10: 0x0000000000000002, R11: 0xffffff8bb83deaa8
R12: 0xffffff8009fa2395, R13: 0xffffff9083fe4c01, R14: 0xffffff8bb1913e68, R15: 0xffffff7f7fffffff
RFL: 0x0000000000010282, RIP: 0xffffff8009ab53ce, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000028, Error code: 0x0000000000000002, Fault CPU: 0x2, PL: 0, VF: 0
Panicked task 0xffffff8bb7ebaa20: 121 threads: pid 589: Dropbox
Backtrace (CPU 2), panicked thread: 0xffffff8bb83deaa8, Frame : Return Address
0xffffffe576c7b720 : 0xffffff8009683efd mach_kernel : _handle_debugger_trap + 0x41d
0xffffffe576c7b770 : 0xffffff80097e3186 mach_kernel : _kdp_i386_trap + 0x116
0xffffffe576c7b7b0 : 0xffffff80097d255d mach_kernel : _kernel_trap + 0x51d
0xffffffe576c7b800 : 0xffffff8009623a60 mach_kernel : _return_from_trap + 0xe0
0xffffffe576c7b820 : 0xffffff80096842cd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffe576c7b940 : 0xffffff8009683a86 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffe576c7b9a0 : 0xffffff8009f1580d mach_kernel : _panic + 0x84
0xffffffe576c7ba90 : 0xffffff80097d2943 mach_kernel : _sync_iss_to_iks + 0x2c3
0xffffffe576c7bc10 : 0xffffff80097d2632 mach_kernel : _kernel_trap + 0x5f2
0xffffffe576c7bc60 : 0xffffff8009623a60 mach_kernel : _return_from_trap + 0xe0
0xffffffe576c7bc80 : 0xffffff8009ab53ce mach_kernel : _cfil_sock_close_wait + 0x40e
0xffffffe576c7bdc0 : 0xffffff8009cb870a mach_kernel : _soclose_locked + 0xda
0xffffffe576c7be10 : 0xffffff8009cb92eb mach_kernel : _soclose + 0xab
0xffffffe576c7be30 : 0xffffff8009c21f13 mach_kernel : _kern_close_file_for_direct_io + 0x453
0xffffffe576c7bea0 : 0xffffff8009c229b5 mach_kernel : _fdt_exec + 0x6e5
0xffffffe576c7bf40 : 0xffffff8009d8a72b mach_kernel : _unix_syscall64 + 0x1fb
0xffffffe576c7bfa0 : 0xffffff8009624226 mach_kernel : _hndl_unix_scall64 + 0x16
Process name corresponding to current thread (0xffffff8bb83deaa8): Dropbox
Boot args: keepsyms=1 debug=0x100 ipc_control_port_options=0
Mac OS version:
21F5048e
Kernel version:
Darwin Kernel Version 21.5.0: Mon Mar 28 19:53:00 PDT 2022; root:xnu-8020.120.43.111.1~1/RELEASE_X86_64
Kernel UUID: ACC5F23C-A2E0-3E73-86C9-38119B418C2F
KernelCache slide: 0x0000000009400000
KernelCache base: 0xffffff8009600000
Kernel slide: 0x0000000009410000
Kernel text base: 0xffffff8009610000
__HIB text base: 0xffffff8009500000
System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0
System uptime in nanoseconds: 2978570226345
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000002b5809edc60
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000000b9ec4705b 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff808280b000 - 0xffffffa08280b000
. PGZ : 0xffffff808280b000 - 0xffffff808480c000
. VM : 0xffffff808480c000 - 0xffffff855100b000
. RO : 0xffffff855100b000 - 0xffffff86ea80b000
. GEN0 : 0xffffff86ea80b000 - 0xffffff8bb700b000
. GEN1 : 0xffffff8bb700b000 - 0xffffff908380b000
. GEN2 : 0xffffff908380b000 - 0xffffff955000b000
. GEN3 : 0xffffff955000b000 - 0xffffff9a1c80b000
. DATA : 0xffffff9a1c80b000 - 0xffffffa08280b000
Metadata: 0xffffffffc9fee000 - 0xffffffffe9fee000
Bitmaps : 0xffffffffe9fee000 - 0xffffffffeffee000
No more Dropbox until its updated I guess. It didn't matter if I had dGPU or iGPU, so hopefully just DropBox needs to be updated by vendor.
Similar deal with Transmission, sounds like this beta is causing previously stable apps to go haywire.
I might try that on a rainy Sunday afternoon. I've got only 1 external SSD, which I use for Time Machine. I've got an old 80 GB SATA HDD that I can use in a Sharkoon dock and connect with USB 2.0. Should 80 GB be enough to install macOS Catalina 10.15.7 and the supplemental updates?
Add VMware Fusion Professional Version 12.2.3 (19436697) to the list as well. Not sure if anyone else is having all fun (not!) issues with this latest 12.4 Beta.
Confirm this fix (connecting a USB to Apple Lightning cable from the computer's USB port when booting Monterey 12.3.1 running OCLP 0.4.3 on an external Crucial MX500 SSD). Using that Lightening cable via a USB 3 port made it possible to connect a brand new Magic Mouse 2 that previously the computer absolutely refused to recognize (a battery older magic mouse reliably connected). After I removed the lightening cable after boot up, the new mouse connected and has been reliably connecting after a reboot.