Sidebar Sidebar
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

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 friends!

I reinstalled Mojave on my cMP4,1->5,1 to try OCLP 0.4.5 and Monterey 12.4.

Without success, sadly. What I'm doing:

1 - Reinstalled Mojave (using Nvidia GT120)
2 - Boot to recovery mode and Disabling SIP
csrutil disable
3 - Boot Mojave SSD with GT120 to check SIP. SIP disabled
4 - Shutdown and replace GT120 by ASUS STRIX R9 380 2GB
5 - Open OCLP GUI 0.4.5
a - generate installer (previously downloaded Monterey 12.4 installer
b - build opencore
c - install to usb drive (Sandisk Cruzer Blade 16Gb)
6 - Reboot
As I'm using a non flashed Apple GPU, I did:
sudo mount disk1s1 (EFI partition on USB installer)
sudo bless --verbose --file /Volumes/EFI/EFI/OC/OpenCore.efi --folder /Volumes/EFI/EFI/OC/ --setBoot
7 - Bootpicker shown. Selecting USB EFI: black screen... No OpenCore bootpicker... :(

Thanks in advance!
 
No progress with Sidecar. Problem is still the same as reported in post 5632.

Mac 13,1 is now running macOS 12.4. Sidecar does not work over WiFi, only over USB. Error message is "The device timed out". My earlier post 5243 reported that Sidecar worked correctly under 12.3. iPad was updated to iPadOS 15.5, but that did not resolve the problem.
 
laertemeira said:
Hi friends!

I reinstalled Mojave on my cMP4,1->5,1 to try OCLP 0.4.5 and Monterey 12.4.

Without success, sadly. What I'm doing:

1 - Reinstalled Mojave (using Nvidia GT120)
2 - Boot to recovery mode and Disabling SIP
csrutil disable
3 - Boot Mojave SSD with GT120 to check SIP. SIP disabled
4 - Shutdown and replace GT120 by ASUS STRIX R9 380 2GB
5 - Open OCLP GUI 0.4.5
a - generate installer (previously downloaded Monterey 12.4 installer
b - build opencore
c - install to usb drive (Sandisk Cruzer Blade 16Gb)
6 - Reboot
As I'm using a non flashed Apple GPU, I did:
sudo mount disk1s1 (EFI partition on USB installer)
sudo bless --verbose --file /Volumes/EFI/EFI/OC/OpenCore.efi --folder /Volumes/EFI/EFI/OC/ --setBoot
7 - Bootpicker shown. Selecting USB EFI: black screen... No OpenCore bootpicker... :(

Thanks in advance!
Click to expand...
Ok, there is always the option your AMD GPU has no GOP vBIOS and cannot display an OC boot picker at all and you do not need to bless the USB if you follow my advice and use only the target drive and the USB (which would be the only bootable device plugged in).

Edit:
You can follow this instructions to add a GOP part to the vBIOS of your AMD card. An alternative way would be to add this AMDGOP.efi driver to OpenCore in the same way OpenCanopy.efi has been included. Drop the file at the same folder and add an analogous config.plist entry as shown in the post linked.
 
Last edited:
  • Like
Reactions: macpro_mid2014 and laertemeira
report

MacBookPro10,1 (Mid 2012 Retina MBP)
Did software update to 12.4
Applied post installation patch 4.5

I am amazed how good this 10 year old MPB is with 12.4 - fast, the battery is still at 90% - great keyboard. Just keep it as a spare - clean system install - likely the best MAC I owned until 2021 M1 Max 16".
 
  • Like
Reactions: makra and rehkram
shafez said:
To whome of you updated to 12.4, does Volume Hash Mismatch still exists.
Click to expand...
Yes. I have this showing up, after upgrading a Late 2009 iMac.
Shows up after every reboot. What is the fix, please?
 

Attachments

  • Screen Shot 2022-05-17 at 7.52.39 PM.jpeg
    Screen Shot 2022-05-17 at 7.52.39 PM.jpeg
    10.9 KB · Views: 63
  • Like
Reactions: shafez
There's no verified fix for the hash mismatch error message. I had it occur sometimes randomly, but usually on login after boot up, for a few weeks after installing Big Sur. Suddenly it stopped for unknown reasons, nothing since.

Smells very much to me, as a 40 year veteran programmer, like a spurious error message. There have been zero reports of it having any effect on the m/c's that get it, or, at least, no reports on the macrumors.com unsupported Macs topics.

Clearly we'd all like to know what triggers it, but I wouldn't worry about it.
 
  • Like
Reactions: shafez, Bmju and BuffyzDead
Observations
  • 12.4 appears to be (subtly) graphically smoother & generally faster than 12.3.1 on my rMBP 10,1
  • In retrospect 12.3.1 seems to have been a little rough around the edges
  • Apple may have taken some 400 grit sandpaper to macOS for the 12.4 release
  • I have no hard data to back up these totally subjective observations but hey, this is macrumors
 
  • Like
Reactions: shafez
hvds said:
Well, it's the same device as in my MBP5,2, when searching BRCM in ioreg's output: Broadcom BRCM2046 for Bluetooth (and BRCM4331 for Wifi).
I could for completeness try tonight the latest 045n on my system to see if it still works the same as the nightly from Friday; I guess it will.
What does "Systembericht" show for Bluetooth? Mine looks as attached (but I need to run 12.3.1 at the moment).

EDIT: now on 12.4RC. Booted from EFI made now from latest 045n. Didn't re-apply post-install patches as they don't affect BT.
Bluetooth still works, listening to BT earphones now. Had to remove them first from the BT system prefpane then reconnect but that sometimes happens.
Bluetooth in the Systembericht looks as in 12.3.1 i.e. THIRD_PARTY_DONGLE.
Click to expand...
Thanks for looking into the issue.
OCLP 0.4.6n addressed the non-functioning Bluetooth, no it works.
Before, System info showed BT as _no_name, no it appears as THIRD_PARTY_DONGLE.
 
hvds said:
In time for the releases of 11.6.6 and 12.4, my MBP5,2 develops a hardware problem in the powering circuitry.
Had happened in 2017 (the notorious capacitor C7771 and a comparator in the OneWire circuit). Repaired by soldering work with dosdude's advice. This time different components... (and not the battery).
Seems the MBP5,2 approaches the end of its life, after the repairs and all the patches from 2017 on - Sierra, HS, Mojave, Cat (all thanks to dosdude), BS, Monterey (thanks to the OCLP team) and always ASentientBot for non-Metal affairs, and jackluke. So the machine was on patches for half of its 13 years.
As I need a reliable single machine which can also survive travelling to conferences etc, already ordered a refurbished MBP16,1 16" as replacement. A pity.
Click to expand...
I am sorry to hear about your MacBook Pro developing "fatal" flaw; my machine had an issue with Nvidia video chip and, as yours, was kept in service via patches.

I second your praise for the OCLP and non-metal developer teams' ingenuity.

Mac 16,1 with 16" screen is a powerful laptop indeed, and I have no doubt you will enjoy it.
 
Last edited:
  • Like
Reactions: olad and hvds
Developed problems with Bluetooth connectivity on both iMac 13,2 ( late 2012) and the MacBook Pro 5,2.
Both are running "on" latest OS 12.4 wihch was installed via OCLP 0.4.6n.

In short, iPhone will pair with either machine for a moment, then disconnect, and message appears that "this iMac (or MacBook Pro) is not supported" (?) In addition, if at this point not surprisingly, I also can no longer "screen share" between the two macs. Reinstalling the system and reapplying patches had no effect. Changing OCLP versions also did not resolve the issue. Problem is reminiscent of one described in this post (link): https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-31062684

I may have to completely remove OCLP installation and reapply it (?)

Hope this information may be useful.

***EDIT: Resolved all issues by logging out from handoff on each device (iPhone, iMac and MacBook Pro), restarting each device, then reactivating handoff on all devices, and restarting each of the devices again. Not sure whether resintalling OS 12.4 had any actual effect on the problem reslution.
This turned out not to be a direct OCLP matter, rather a quirk of the 12.4 update which scrambled inter-connectivity.
 
Last edited:
  • Like
Reactions: Aston441
Someone managed to get the isigh webcam to work on iMac 21.5 Late 2009, I could not find anything about it in the forum, thanks if anyone will be able to answer me, sorry for the translated English
 
Mystere65 said:
Someone managed to get the isigh webcam to work on iMac 21.5 Late 2009, I could not find anything about it in the forum, thanks if anyone will be able to answer me, sorry for the translated English
Click to expand...
This is slightly off topic here but you may find some information on this thread (of this forum). Using a TB2<->FW adapter might do the trick on systems having TB.
 
rehkram said:
There's no verified fix for the hash mismatch error message. I had it occur sometimes randomly, but usually on login after boot up, for a few weeks after installing Big Sur. Suddenly it stopped for unknown reasons, nothing since.

Smells very much to me, as a 40 year veteran programmer, like a spurious error message. There have been zero reports of it having any effect on the m/c's that get it, or, at least, no reports on the macrumors.com unsupported Macs topics.

Clearly we'd all like to know what triggers it, but I wouldn't worry about it.
Click to expand...
For me when the hash mismatch error occurs it closes the running App which I am using and can't reopen it until I restart, happened with Microsoft Excel 2021 and also with TextEdit.
 
  • Like
Reactions: rehkram
shafez said:
For me when the hash mismatch error occurs it closes the running App which I am using and can't reopen it until I restart, happened with Microsoft Excel 2021 and also with TextEdit.
Click to expand...
We all know this problem and the only way to get around (at least for me) this was a mix of this:
  1. reinstalling using a newly created APFS container created by the disk utility version included into the (Monterey/Big Sur) installer
  2. avoid at any cost booting into High Sierra (which is known to overwrite the Big Sur/Monterey PreBoot partition) while having the Big Sur/Monterey disk connected to the same system
  3. avoid cross macOS updates, i.e. from Catalina to Big Sur and to Monterey when still facing this issue.
  4. moving on to Monterey (clean installation, too)
The last installation I had with this particular problem was on an external test SSD possibly attached to too many different systems in too many different scenarios. Did the new (Big Sur latest) installation some days ago and since then (fingers crossed) the dying app phenomena went away. I deleted all High Sierra installations from all of my iMacs.

The other idea was disabling FeatureUnlock from your OC config manually, but this is/was a hunch, only.
 
Last edited:
  • Like
Reactions: rehkram, shafez and Tockman
macOS 12.4 + OCLP 0.4.5 is working perfect so far. I still have my Display brightness HUD bug, but it's nothing serious.

0.4.5 for me, seems to have fixed my issue with my other SSD volume (High Sierra) not reading after a while asleep and forcing a reboot.
Screen Shot 2022-05-18 at 4.24.01 AM.png
 
@khronokernel

MacBookPro4,1 Early 2008, 17-inch, OCLP 0.4.6n
Fatal error: macOS 12.4 consistently crashes, rendering 12.4 unusable, while 12.3.1 was performing flawlessly,
Can you look into it, please?

Thank you very much, khronokernel, for your outstanding work.


Crash report:
Code: 
panic(cpu 1 caller 0xffffff80137d0d53): Kernel trap at 0xffffff8014bd3090, type 6=invalid opcode, registers:
CR0: 0x0000000080010033, CR2: 0x00007ff8535106b8, CR3: 0x00000000045ba000, CR4: 0x00000000000026e0
RAX: 0x7dc1c4077f7dc1c4, RBX: 0x0000000000000660, RCX: 0x0000000000000000, RDX: 0xffffffac1e900b14
RSP: 0xffffffac9045b520, RBP: 0xffffffac9045b9e0, RSI: 0x0000000000000200, RDI: 0xffffffac9045b980
R8:  0xffffffa5b9058008, R9:  0x0000000000000000, R10: 0x0000000000000702, R11: 0x0000000000000702
R12: 0xffffffac1e900b14, R13: 0x0000000000001394, R14: 0xffffffa5b9058008, R15: 0xffffffac9045b780
RFL: 0x0000000000010246, RIP: 0xffffff8014bd3090, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00007ff8535106b8, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0, VF: 0

Panicked task 0xffffffa5b7f933b0: 4 threads: pid 2558: mdworker_shared
Backtrace (CPU 1), panicked thread: 0xffffff92914f5aa0, Frame : Return Address
0xffffffac9045aed0 : 0xffffff8013681c8d mach_kernel : _handle_debugger_trap + 0x41d
0xffffffac9045af20 : 0xffffff80137e1596 mach_kernel : _kdp_i386_trap + 0x116
0xffffffac9045af60 : 0xffffff80137d0963 mach_kernel : _kernel_trap + 0x4d3
0xffffffac9045afb0 : 0xffffff8013621a70 mach_kernel : _return_from_trap + 0xe0
0xffffffac9045afd0 : 0xffffff801368205d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffac9045b0f0 : 0xffffff8013681816 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffac9045b150 : 0xffffff8013f15163 mach_kernel : _panic + 0x84
0xffffffac9045b240 : 0xffffff80137d0d53 mach_kernel : _sync_iss_to_iks + 0x2c3
0xffffffac9045b3c0 : 0xffffff80137d0a36 mach_kernel : _kernel_trap + 0x5a6
0xffffffac9045b410 : 0xffffff8013621a70 mach_kernel : _return_from_trap + 0xe0
0xffffffac9045b430 : 0xffffff8014bd3090 com.apple.AppleFSCompression.AppleFSCompressionTypeZlib : _lzvn_decode_buffer + 0x550
0xffffffac9045b440 : 0xffffff80169c507d com.apple.filesystems.apfs : _btree_node_get_internal + 0x1a3
Unaligned frame
Backtrace terminated-invalid frame pointer 0xffffffac0000000f
      Kernel Extensions in backtrace:
         com.apple.filesystems.apfs(1934.121.2)[5F9A9C41-A343-3348-AC4C-EFF424B665E1]@0xffffff80168cf000->0xffffff8016a4dfff
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[BE14BE1A-DA79-32DA-B569-1A5F50EE132F]@0xffffff8014b9e000->0xffffff8014ba7fff
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[6CED4A69-71E3-3953-8416-44ED41F44F8B]@0xffffff8014bb4000->0xffffff8014bb9fff
            dependency: com.apple.iokit.CoreAnalyticsFamily(1)[A82BAE32-B338-3EDD-B243-315BBD060A4B]@0xffffff80150ad000->0xffffff80150b4fff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[66DDF66B-57B8-3994-83B5-B5A169C445E1]@0xffffff8016351000->0xffffff8016367fff
            dependency: com.apple.kec.corecrypto(12.0)[16C95E29-A132-35C1-80C7-42709C756950]@0xffffff8016a87000->0xffffff8016b07fff
            dependency: com.apple.security.AppleImage4(4.2.0)[CBD952F5-D556-3829-9F12-721749B650E2]@0xffffff8014c3b000->0xffffff8014c53fff
         com.apple.AppleFSCompression.AppleFSCompressionTypeZlib(1.0)[1489EB74-7D7C-34F6-91C0-E6CDD3A25459]@0xffffff8014bd1000->0xffffff8014be2fff

Process name corresponding to current thread (0xffffff92914f5aa0): mdworker_shared
Boot args: keepsyms=1 debug=0x100 -disable_sidecar_mac ipc_control_port_options=0

Mac OS version:
21F79

Kernel version:
Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:22 PDT 2022; root:xnu-8020.121.3~4/RELEASE_X86_64
Kernel UUID: 3C587984-4004-3C76-8ADF-997822977184
KernelCache slide: 0x0000000013400000
KernelCache base:  0xffffff8013600000
Kernel slide:      0x0000000013410000
Kernel text base:  0xffffff8013610000
__HIB  text base: 0xffffff8013500000
System model name: MacBookPro4,1 (Mac-F42C89C8)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 2

System uptime in nanoseconds: 2064949422363
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000001e0c893b6da
  Sleep   : 0x000000addeca7e7d 0x0000001d4886c7dd 0x000000adde9a8738
  Wake    : 0x000000afb3926311 0x000000002c29f16f 0x000000afb251e5cf
Compressor Info: 1% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
  Zone map: 0xffffff8c1ec02000 - 0xffffffac1ec02000
  . PGZ   : 0xffffff8c1ec02000 - 0xffffff8c1f803000
  . VM    : 0xffffff8c1f803000 - 0xffffff90ec302000
  . RO    : 0xffffff90ec302000 - 0xffffff9285c02000
  . GEN0  : 0xffffff9285c02000 - 0xffffff9752702000
  . GEN1  : 0xffffff9752702000 - 0xffffff9c1f202000
  . GEN2  : 0xffffff9c1f202000 - 0xffffffa0ebd02000
  . GEN3  : 0xffffffa0ebd02000 - 0xffffffa5b8802000
  . DATA  : 0xffffffa5b8802000 - 0xffffffac1ec02000
  Metadata: 0xffffffac42d94000 - 0xffffffac62d94000
  Bitmaps : 0xffffffac62d94000 - 0xffffffac65194000
 
Hi everyone. I successfully upgraded to Monterey 12.4 on my Macbook 5,5. I noticed problems in Google Spreadsheets which is unusable until I deactivate hardware acceleration in Google Chrome. Is this a known problem? Thanks everyone.
 
  • Like
Reactions: macinfo
techguy82 said:
Hi everyone. I successfully upgraded to Monterey 12.4 on my Macbook 5,5. I noticed problems in Google Spreadsheets which is unusable until I deactivate hardware acceleration in Google Chrome. Is this a known problem? Thanks everyone.
Click to expand...
Thanks for reporting the solution!

No, but when crawling through the whole App Store we might find tons of apps not any longer fully compatible after applying non metal patches. The main purpose was getting back the graphics acceleration on the desktop and OpenGL support, but a lot of apps left OpenGL to use metal....nothing one can really tackle.
 
  • Like
  • Love
Reactions: OKonnel, macinfo, macpro_mid2014 and 1 other person
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