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.

KennyW

macrumors 6502
Sep 5, 2007
452
389
Something that just occurred to me: why don't you try to customize the EFI (kext, config, etc.) per macOS?
Create a customized EFI for Big Sur and put it on USB stick 1; then customize EFI for Monterey and put it on USB stick 2; even if both initial EFIs are identical at the beginning.
And every time you switch from one macOS to the other, do an NVRAM reset before booting the other macOS.

I don't know if this makes any sense, but this is something I would try in your situation.
Just wonder whether there is a lifespan of the eeprom chip storing the NVRAM data with a limited no. of read/write cycles in reseting ...
Perhaps we won't exceed that even after 10 yrs of usage and perhaps daily NVRAM reset ...
 
  • Like
Reactions: macpro_mid2014

0134168

Cancelled
May 21, 2009
2,964
2,805
Just wonder whether there is a lifespan of the eeprom chip storing the NVRAM data with a limited no. of read/write cycles in reseting ...
Perhaps we won't exceed that even after 10 yrs of usage and perhaps daily NVRAM reset ...
I recommend you to get a reconstructed ROM image, if you are talking about Mac Pro 5,1. Ask @tsialex
 

KennyW

macrumors 6502
Sep 5, 2007
452
389
Not sure that is entirely valid. With two drive bays in this Mini3,1 - Drive 2 is a 1TB Pioneer SSD w/ four partitions, 3 APFS and one HFS for High Sierra then Mojave, Catalina and Big Sur, all completely up-to-date. Drive 1 is an OWC 500GB w/only a Monterey Beta installed. The cascading crash effect commenced w/Beta 7 and persists to Beta 9. To fix, the RAM modules were replaced to no effect, as some have suggested, the SSD was completely erased and Beta 9 was installed fresh with createinstallmedia USB. Moved or installed apps manually after tedious Control Panel settings. OCLP Step #3, reboot. Ran overnight, sleep/wake perfect, no problems until quitting Safari. No other app would launch after that, eventually Force Quit quit entirely. Cold boot the only recovery. Both drives have latest OCLP_030 Nightly EFI installed.

The non-Monterey multi-boot SSD has NEVER exhibited a cascading crash on any partition. This is a post-Beta 6 Monterey issue, perhaps Webkit-related because the multi-app crash can be precipitated by simply quitting Safari after an hour or so of browsing, commenting, seeing if Otis won the Fat Bear Championship. ?

? . . . . . . . The point being - Multi-boot may not be a factor because mono-booting a Monterey fresh-install Beta 9 is still broken. Too bad because Beta 9 runs great until it doesn't. ?
I only know that multibooting between High Sierra and the other newer macOS (Catalina and Big Sur) would corrupt the pre-boot EFI partition, despite the OSes are in separate disk.
That was a consistent nuisance I encountered previously with no easy solution.
So, finally I have updated the High Sierra to Monterey beta when Big Sur is stable enough as my daily OS.

Besides, the older APFS driver in Catalina does not show (read/write) the Big Sur and Monterey disks, but not the vice versa.

So, can you read/write the other partitions freely when you boot into your Drive 2 ?
 

houser

macrumors 6502
Oct 29, 2006
405
544
Something that just occurred to me: why don't you try to customize the EFI (kext, config, etc.) per macOS?
Create a customized EFI for Big Sur and put it on USB stick 1; then customize EFI for Monterey and put it on USB stick 2; even if both initial EFIs are identical at the beginning.
And every time you switch from one macOS to the other, do an NVRAM reset before booting the other macOS.

I don't know if this makes any sense, but this is something I would try in your situation.
Thanks. Appreciate the reply and that's kind of what I do now.
However, my main Macbook Pro is a 10,1 with a decent large SSD and it would certainly be nice with a stable simple multiboot setup on there for obvious reasons. But there are workarounds ;)
 
  • Like
Reactions: macpro_mid2014

K two

macrumors 68020
Dec 6, 2018
2,314
3,187
North America
I only know that multibooting between High Sierra and the other newer macOS (Catalina and Big Sur) would corrupt the pre-boot EFI partition, despite the OSes are in separate disk.
That was a consistent nuisance I encountered previously with no easy solution.
So, finally I have updated the High Sierra to Monterey beta when Big Sur is stable enough as my daily OS.

Besides, the older APFS driver in Catalina does not show (read/write) the Big Sur and Monterey disks, but not the vice versa.

So, can you read/write the other partitions freely when you boot into your Drive 2 ?
Perfectly, the SSD with the CRASHING b9 fresh install was formatted by the latest Big Sur. High SIerra has not been run since the b9, install. The b9 crash cascade can be triggered by quitting Safari, Firefox, Terminal or Textedit, so far. Your assertion that a HFS partition on a separate SSD can be the cause of crashes on Monterey seems questionable. This started with b7, Monterey ran crash free before that. What changed to enable the problem? If your point is valid, this should have been seen before b6. :rolleyes:
 
  • Like
Reactions: KennyW

AlexSakha67

macrumors member
Hallo! Hooray installed on his original old hdd disk (MacBook7,1 2010) everything works. Many thanks to the developers we hope that when the official (final) version of Monterey12 comes out, we will also be happy to update our unsupported computers as real modern Apple technology.
Thank you again?
 

Attachments

  • 1  Screenshot 2021-10-10 at 21.22.48.png
    1 Screenshot 2021-10-10 at 21.22.48.png
    32.7 KB · Views: 93
  • 2 Screenshot 2021-10-10 at 21.28.21.png
    2 Screenshot 2021-10-10 at 21.28.21.png
    58.7 KB · Views: 112
  • 3 Screenshot 2021-10-10 at 23.42.22.png
    3 Screenshot 2021-10-10 at 23.42.22.png
    106.4 KB · Views: 120
  • 4 Screenshot 2021-10-10 at 21.44.30.png
    4 Screenshot 2021-10-10 at 21.44.30.png
    114 KB · Views: 112

K two

macrumors 68020
Dec 6, 2018
2,314
3,187
North America
OCLP fails ? to disable SIP even when set to do so in Item #5>2. Re-installed Nighly TUI to confirm. Console reports SIP is enabled as does SilentKnight. . . . The Monterey Bluetooth crash on every boot and delay prevents B/T KB from being of any use until the Desktop appears. Both ControlCenter and Notifications crash, frequently. b9 has issues! :oops: ?
 

0134168

Cancelled
May 21, 2009
2,964
2,805
OCLP fails 🚧 to disable SIP even when set to do so in Item #5>2. Re-installed Nighly TUI to confirm. Console reports SIP is enabled as does SilentKnight. . . . The Monterey Bluetooth crash on every boot and delay prevents B/T KB from being of any use until the Desktop appears. Both ControlCenter and Notifications crash, frequently. b9 has issues! :oops: 🚧
Never worked for me in any version of of OCLP, neither Big Sur nor Monterey, disable the SIP. If you find the solution please let me know.
 
  • Like
Reactions: K two

figyu

macrumors member
Sep 20, 2016
34
18
Hallo! Hooray installed on his original old hdd disk (MacBook7,1 2010) everything works. Many thanks to the developers we hope that when the official (final) version of Monterey12 comes out, we will also be happy to update our unsupported computers as real modern Apple technology.
Thank you again?
Do you have a graphic acceleration in your MacBook 7,1 after patching OCLP v. 0.2.5?
 

KennyW

macrumors 6502
Sep 5, 2007
452
389
Perfectly, the SSD with the CRASHING b9 fresh install was formatted by the latest Big Sur. High SIerra has not been run since the b9, install. The b9 crash cascade can be triggered by quitting Safari, Firefox, Terminal or Textedit, so far. Your assertion that a HFS partition on a separate SSD can be the cause of crashes on Monterey seems questionable. This started with b7, Monterey ran crash free before that. What changed to enable the problem? If your point is valid, this should have been seen before b6. :rolleyes:
Agree. The mere presence of the HS partition should not cause your problem, and the preboot eEFI corruption happens only when one boots into the HS. However, with SecureBoot disabled, one can still boot into the various different OSes.

My point is that with various different new and old and beta OSes in different partitions of a drive can easily cause cascading problems when bugs occur and difficult to troubleshoot from the interacting EFI files. Not that it is impossible to run such system. Besides, issues are bound to happen with beta anyway ;)
 

hvds

macrumors 6502a
Sep 1, 2017
852
2,032
Switzerland
Update
+ Photos 7.0 isn't crashing anymore in this beta 8 installation.
+ And Arduino runs fine without replacement of AppleUSBACM.kext.
- Safari 15.0 and 15.1 still freezing after a while. Firefox 92.0.1 working.

I did update SkyLight with ASentientBot's new versions he gave on Discord in the public-development channel (3 Oct), for SkyLight and SkyLightOld.dylib (using jackluke BigSurmountsrw.app); but Photos still ran well when reverting to the previous version for a test.
Thanks ASentientBot! Great work hidden behind one of your nice understatements.

So looking forward to 12.0 release - seems I can live with Monterey on my non-metal MBP5,2.
In preparation for 12.0 release, exercised again clean Monterey installation with migration of settings/data/apps from Big Sur 11.6. Still using USB disks for Monterey, the internal disk still reserved for nice and stable Big Sur.

Using the migration assistant, even directly during setup, failed i.e. left a non-bootable system which was of course bootable before migration.

In a 2nd attempt, used CCC instead to do cloning to a freshly erased SSD on USB. Then installed 12.0 beta 8 over it and applied the post install patches.
- did this first with jackluke's BaseSystemfix method. Booted right to user login. Photos working. Looks good (no graphics artefacts) with reduced transparency. Graphics acceleration working. Apps won't start after a while of system usage as others have reported. Will try to keep terminal active all the time so can do a sudo purge in case.
- now repeating this procedure with OCLP 030n and beta 9 instead, to another SSD.

EDIT: updated the BaseSystemfix installation to beta 9, running fine.
As for oclp so far, installation went fine and proceeded to user login without intervention. Then applied to post-install patches (oclp 030n from 11 Oct) but then booting failed. Investigating.
 

Attachments

  • thissys.png
    thissys.png
    56 KB · Views: 76
  • Bildschirmfoto 2021-10-12 um 22.13.34.png
    Bildschirmfoto 2021-10-12 um 22.13.34.png
    52.2 KB · Views: 57
Last edited:
  • Like
Reactions: macpro_mid2014

chris1111

macrumors 6502
Jul 8, 2015
432
1,037
Montréal Canada
Hi all,
Monterey Beta 9 fully working on MacBook Pro 9,1 15" Mid 2012 (non-retina)
Just one question. Control Center looks a bit weird, probably non-hidpi related as it is non-retina screen.
Any chance to make these corners look smooth? With HD4000 it looks even worse.

https://www.reddit.com/r/MontereyPatcher/comments/ocsz02

Yea I see in dark mode but Light mode. looks good; not perfect but acceptable
This is from my ProBook 6570b
Screen Shot 2021-10-11 at 9.29.56 AM.png
 
  • Like
Reactions: AlexSakha67

K two

macrumors 68020
Dec 6, 2018
2,314
3,187
North America
Agree. The mere presence of the HS partition should not cause your problem, and the preboot eEFI corruption happens only when one boots into the HS. However, with SecureBoot disabled, one can still boot into the various different OSes.

My point is that with various different new and old and beta OSes in different partitions of a drive can easily cause cascading problems when bugs occur and difficult to troubleshoot from the interacting EFI files. Not that it is impossible to run such system. Besides, issues are bound to happen with beta anyway ;)
Could what has been observed be local to iHacks? Noticed a commonalIty.?
 

K two

macrumors 68020
Dec 6, 2018
2,314
3,187
North America
Agree. The mere presence of the HS partition should not cause your problem, and the preboot eEFI corruption happens only when one boots into the HS. However, with SecureBoot disabled, one can still boot into the various different OSes.

My point is that with various different new and old and beta OSes in different partitions of a drive can easily cause cascading problems when bugs occur and difficult to troubleshoot from the interacting EFI files. Not that it is impossible to run such system. Besides, issues are bound to happen with beta anyway ?
.
 
Last edited:

alfon_sico

macrumors regular
Oct 3, 2015
236
79
O Know this is off topic actually

I have a Mac mini 2014 supported for Monterey but from yesterday I have some issues with EFI menu. It doesn’t recognize any USB bootable (Mojave macOS)

the thing is that I mount EFI partition of my internal SDD and I see there is a firmware file in folder

is it better delete every file of EFI?

proofs: when I reset PRAM the next boot discover the USB with bootable macOS but just another boot it doesn’t show

if I check EFI of external USB it was empty but if I save the file of the internal one then it get show in the boot menu. Anyway on the second time it doesn’t show

my personal try is to erase every file of my internal ssd but I’m not sure of do it. Here you all are experts about EFI issues
 

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
O Know this is off topic actually

I have a Mac mini 2014 supported for Monterey but from yesterday I have some issues with EFI menu. It doesn’t recognize any USB bootable (Mojave macOS)

the thing is that I mount EFI partition of my internal SDD and I see there is a firmware file in folder

is it better delete every file of EFI?

proofs: when I reset PRAM the next boot discover the USB with bootable macOS but just another boot it doesn’t show

if I check EFI of external USB it was empty but if I save the file of the internal one then it get show in the boot menu. Anyway on the second time it doesn’t show

my personal try is to erase every file of my internal ssd but I’m not sure of do it. Here you all are experts about EFI issues
Deleting OC from your system is part of the docs....
Installing OC newly is also part of the same documentation.
 

amaze1499

macrumors 65816
Oct 16, 2014
1,194
1,221
Hi all,
Monterey Beta 9 fully working on MacBook Pro 9,1 15" Mid 2012 (non-retina)
Just one question. Control Center looks a bit weird, probably non-hidpi related as it is non-retina screen.
Any chance to make these corners look smooth? With HD4000 it looks even worse.

https://www.reddit.com/r/MontereyPatcher/comments/ocsz02
Same here. I assume its because of the graphics card specs, non retina screens etc.
 

alfon_sico

macrumors regular
Oct 3, 2015
236
79
O Know this is off topic actually

I have a Mac mini 2014 supported for Monterey but from yesterday I have some issues with EFI menu. It doesn’t recognize any USB bootable (Mojave macOS)

the thing is that I mount EFI partition of my internal SDD and I see there is a firmware file in folder

is it better delete every file of EFI?

proofs: when I reset PRAM the next boot discover the USB with bootable macOS but just another boot it doesn’t show

if I check EFI of external USB it was empty but if I save the file of the internal one then it get show in the boot menu. Anyway on the second time it doesn’t show

my personal try is to erase every file of my internal ssd but I’m not sure of do it. Here you all are experts about EFI issues
Thank you. But not talking about OC folder. It’s a Apple folder inside EFI. Could be delete? I think it’s a kind of problem that affect to recognaise others bootable drivers plugged
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.