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.

sebo2001

macrumors member
Jun 18, 2018
36
7
2. if you are using Martin's version check "additional option 3"


I have tried Martin's Lo method:
-SIP is disabled
-VMM flag was on
-Martin's 0.8.0 version loaded

I created a Big Sur bootable USB key, selected it via boot picker. I decided to do a clean install so I erased the main disk and followed the installation, I pointed to the disk to copy files and the installation process started fine, once all data was copied to the disk mac restarted but I got a grey circle grayed out. I tried to reboot into BigSUr recovery but it failed at the same moment also giving me that grey circle crossed.
 

Gustav Holdoff

macrumors regular
Oct 23, 2020
201
82
I have tried Martin's Lo method:
-SIP is disabled
-VMM flag was on
-Martin's 0.8.0 version loaded

I created a Big Sur bootable USB key, selected it via boot picker. I decided to do a clean install so I erased the main disk and followed the installation, I pointed to the disk to copy files and the installation process started fine, once all data was copied to the disk mac restarted but I got a grey circle grayed out. I tried to reboot into BigSUr recovery but it failed at the same moment also giving me that grey circle crossed.
I have tried Martin's Lo method:
-SIP is disabled
-VMM flag was on
-Martin's 0.8.0 version loaded

I created a Big Sur bootable USB key, selected it via boot picker. I decided to do a clean install so I erased the main disk and followed the installation, I pointed to the disk to copy files and the installation process started fine, once all data was copied to the disk mac restarted but I got a grey circle grayed out. I tried to reboot into BigSUr recovery but it failed at the same moment also giving me that grey circle crossed.
you didn't read the instructions carefully.
You absolutely did not correctly prepare OC for MACOS update
so you will be wrong every time
and every time you will lose your disk or crash the system
You wrote
I have tried Martin's Lo method:
-SIP is disabled - NOT CORRECT- ITS NOT NEEDED FOR UPDATE
-VMM flag was on YES CORRECT
-Martin's 0.8.0 version loaded ???

please watch the video again, YOU FOGOT TO MAKE ONE MORE CONFIG CHANGE

updating the system for old macros is now like a minefield,
and if you are not prepared for this, then it’s better not to start
 

sebo2001

macrumors member
Jun 18, 2018
36
7
Since this thread is NOT devoted to Martin Lo's method, is there a particular reason why you would choose not to use the advice provided in post #1?

Post 1 is amaizingnly comprehensive and frankly cool, few years back (maybe more than few) I would be literally bathing in it, and enjoying it. I stopped beeing computer geek and become photography and drone geek, and simply do not have time to fully digest entire post, I need my Mac do help me with photography and drone footage.

Martin's Lo method saves me time by modifying stuff for my Old MacPro5.1 It would take me a month at this moment to set eveything myslef and understand each function, as I alwasy like to go deep, I simply do not have that time.

I just found "Dual-processor workaround" my MAC is dual CPU I would need now spend even more time to see how all that works... Martin's LO method saves a lot of time with his precooked config.
 
Last edited:

sebo2001

macrumors member
Jun 18, 2018
36
7
I have tried Martin's Lo method:
-SIP is disabled - NOT CORRECT- ITS NOT NEEDED FOR UPDATE
-VMM flag was on YES CORRECT
-Martin's 0.8.0 version loaded ???

please watch the video again, YOU FOGOT TO MAKE ONE MORE CONFIG CHANGE

  1. [Optional] 3x NVRAM reset to avoid some unknown issues.
  2. Disable SIP (must do, especially if you performed step 1)
  3. Download the attachment in this post (Some users reported 0.6.1 package has compatibility issue. You may download the 0.5.9 package if you prefer that, same installation procedures.)
MArtin Version 0.8.0 I'm refering to attachemnt link from his post. file name is 0.8.0.zip

post says VMM flag needs to be on for Catalina and Monterey, BigSur was crossed out (I have stil lset the flag)

"Additional option 3: If you want to enable the ability to install / update Catalina, Big Sur and Monterey, please follow the steps in this video."

I did hit bless OpenCore after copying the files.

Can you say what I have missed?
 

SJerc

macrumors newbie
Nov 2, 2021
6
2
Hey guys, after upgrading my Mac Pro 4.1/5.1 to 12.5 and now 12.6 (patched with Martin Lo's package) I get frequent beach balls and overall system unresponsiveness until I reboot again. Then it will mostly work for some time and then start to freeze up again. It all started with 12.5 and sadly didn't remedy itself with the update to 12.6. Anybody got an idea what can cause this? It is mainly obvious while browsing or accessing files through the Finder.

Edit: after seeing UVFSService hogging quite a bit of CPU power in activity monitor I searched the web and found out that it might have to do with Spotlight and a problem with it searching a Bootcamp partition. While I still have a Bootcamp partition (which I haven't brought back to life yet) I don't actually use it anymore but the solution might probably be to exclude it from Spotlight indexing. So I did and so far so good but I have to see if that really fixed the problem for good.

Apparently also other people with different machines have had this issue so it is apparently not related to the cMP.
I noticed the same issues and have a BOOTCAMP partition as well. Thanks for the tip, I've excluded my BOOTCAMP from Spotlight as well, so hopefully that does it.
 

sebo2001

macrumors member
Jun 18, 2018
36
7
So, why you are not asking about your issues on the correct thread? Why hijack a thread that have a very different way to install and maintain OpenCore installs then the one you are using?


Sorry my inexpirience, I think this is the only sensibly named thread that stics out, sorry again.
 

Gustav Holdoff

macrumors regular
Oct 23, 2020
201
82
Sorry my inexpirience, I think this is the only sensibly named thread that stics out, sorry again.
About Martin's version ask Martin LO
or
 

sebo2001

macrumors member
Jun 18, 2018
36
7
About Martin's version ask Martin LO
or

Thank you for pointing me to the right direction, I found first link yesterday when I realized I'm asking in the wrong spot. Thank you agin.
 

sebo2001

macrumors member
Jun 18, 2018
36
7
Thank you for pointing me to the right direction, I found first link yesterday when I realized I'm asking in the wrong spot. Thank you agin.

By looking at the dates and threads, Martin Lo first post was Mar 2020 I upgraded my Mac to Mojave Jan 2020, that means I had to have Open Core 0.6.7 from this thread so all things considered I was asking in the right thread after all.
Not beeing here for over 2 yaers I didn't realize how this project evolved.
 
Last edited:

TECK

macrumors 65816
Nov 18, 2011
1,129
478
@cdf quick question about screen resolution: when I start my cMP, the screen resolution at login prompt is Default value (1920 x 1080). As soon as I login, the screen resolution switches to my preferred resolution More Space value (3840 x 2160). Is this the expected behaviour? Or is there a variable in OC that allows me to define my preferred resolution. If the Mac goes in sleep mode, when I wake it up, it displays the preferred resolution More Space value, as expected. Only when I restart, the Default value is used at login prompt.
 

cdf

macrumors 68020
Original poster
Jul 27, 2012
2,256
2,583
@cdf quick question about screen resolution: when I start my cMP, the screen resolution at login prompt is Default value (1920 x 1080). As soon as I login, the screen resolution switches to my preferred resolution More Space value (3840 x 2160). Is this the expected behaviour? Or is there a variable in OC that allows me to define my preferred resolution. If the Mac goes in sleep mode, when I wake it up, it displays the preferred resolution More Space value, as expected. Only when I restart, the Default value is used at login prompt.
Yes, this is the expected behavior. In fact, the same thing happens on supported Macs (with built-in HiDPI displays). Changing UIScale from 0 (automatic) to 1 (1x scaling) should give you the desired result.
 
  • Like
Reactions: TECK

star-affinity

macrumors 68000
Nov 14, 2007
1,998
1,334
The system log contains regular AMPDeviceDiscoveryAgent 'AMMuxedDeviceDisconnected' notices (about every 5 seconds). I tried quitting the AMPDeviceDiscoveryAgent, which naturally stopped the messages, but still had the login screen issue afterwards, so it's probably irrelevant.
Did you ever get to solve what that was about?

After waking from sleep I have these mesages in the system.log

Code:
AMPDeviceDiscoveryAgent[766]: Entered:_AMMuxedDeviceDisconnected, mux-device:446
AMPDeviceDiscoveryAgent[766]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:446

The problem I'm facing is that I can't watch any videos on YouTube for example – the video tries to start (spinning circle) but it doesn't start no matter which wen browser I try. So I understand the problem is deeper. A restart will fix the problem, but would be nice to understand what causes it and possibly prevent it from happening.
 

mode11

macrumors 65816
Jul 14, 2015
1,452
1,172
London
Did you ever get to solve what that was about?
Wouldn't say I solved it, but from what I could gather it related to communicating with an iOS device. I turned off the function in Finder to connect to my iPhone and iPad over WiFi (so would need to use a Lightning cable to sync etc.), and don't get these messages any more. Don't know if they were significant though. I also spent a bit of time uninstalling old / unnecessary apps and so on, which may have helped.

In general, Monterey 12.5.1 is pretty stable for me now - very occasionally get an unexplained pause (i.e. a beachball when the computer's not really doing anything), and even more rarely get a freeze at the login screen. The latter only happens if I let the Mac go to sleep on its own timer rather than put it to sleep manually.

I've never had any issues with YouTube though. I use Safari, with Wipr to block ads generally, and 1Blocker Scripts to block ads on YouTube specifically (which otherwise get through).
 
  • Like
Reactions: star-affinity

star-affinity

macrumors 68000
Nov 14, 2007
1,998
1,334
Wouldn't say I solved it, but from what I could gather it related to communicating with an iOS device. I turned off the function in Finder to connect to my iPhone and iPad over WiFi (so would need to use a Lightning cable to sync etc.), and don't get these messages any more. Don't know if they were significant though. I also spent a bit of time uninstalling old / unnecessary apps and so on, which may have helped.

In general, Monterey 12.5.1 is pretty stable for me now - very occasionally get an unexplained pause (i.e. a beachball when the computer's not really doing anything), and even more rarely get a freeze at the login screen. The latter only happens if I let the Mac go to sleep on its own timer rather than put it to sleep manually.

I've never had any issues with YouTube though. I use Safari, with Wipr to block ads generally, and 1Blocker Scripts to block ads on YouTube specifically (which otherwise get through).

Thanks for the info.

You're right – my video playback problem wasn't related to AMPDeviceDiscoveryAgent – after a restart I still get that in the logs and now I can play videos just fine. I have ”Show this iPhone when on Wi-Fi” unchecked for my phone in the Finder and the messages are still there. Did you change it somewhere else, or?
Monteray is working well for me too overall, but there's always something annoying, right? :)
 

SEJU

macrumors member
Dec 27, 2014
64
32
Europe
I am not sure if this is the right thread, so please advice in case it is not...

I tried to install Opencore through the Opencore legacy patcher (v 0.4.11) on my beloved 2010 Mac Pro 5.1. I was not interested in upgrading the OS beyond Mojave, just in having the bootselector and to have pcie Sata SSDs displayed as internal.

I installed OCLP on the System SSDs EFI partition, did not reboot, but enter into Recovery mode and blessed as adviced. Upon start I got to a boot selector with only one selection: my Boot SSD (which is a SATA SSD on a PCIE slot). After that I get a no access sign and the MacPro restarts.

For now I put my old system disk into the machine and it booted. I am unable to enter recovery partition with the system SSD

My questions are:
1) why did I get a no access sign?
2) how can I delete OCLP for now from my SSD and regain its boot ability?

Thank you in advance! Please advice if there is a better thread to ask this question or find an answer.
 

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
No, this is not an OCLP support thread. This thread is devoted to the method advocated in post #1. Many users of this thread, myself included, know next to nothing regarding OCLP. I think you should be able to locate an OCLP support group if you google for Dortania and OCLP.
 
  • Like
Reactions: NC12 and SEJU

SEJU

macrumors member
Dec 27, 2014
64
32
Europe
No, this is not an OCLP support thread. This thread is devoted to the method advocated in post #1. Many users of this thread, myself included, know next to nothing regarding OCLP. I think you should be able to locate an OCLP support group if you google for Dortania and OCLP.
That is what I was afraid of. Thanks nevertheless. Found a discord channel and hope someone there can shed some light on my situation.
 
  • Like
Reactions: dataharvested

sfalatko

macrumors 6502a
Sep 24, 2016
641
365
That is what I was afraid of. Thanks nevertheless. Found a discord channel and hope someone there can shed some light on my situation.
I think your first problem is that the current approach to spoofing is to spoof the cMP5,1 as a 7,1 and the 7,1 cannot run Mojave. If you can change your config.plist to include the "no_compat_check" boot argument you should be able to run Mojave with OpenCore.

However - your best bet is the OLCP discord channel.
 
  • Like
Reactions: SEJU and hwojtek

Cyberdoc71

macrumors member
Jan 17, 2018
37
4
Hi. Have an opencore system trying to get a SSD7204 working and no luck. Its dual bootable and windows sees the array but in Catalina side all four disks show up individually. Using latest Highpoint non bootable kext which is loaded but to no effect. Anyone advise please?

Thanks
 

SEJU

macrumors member
Dec 27, 2014
64
32
Europe
I think your first problem is that the current approach to spoofing is to spoof the cMP5,1 as a 7,1 and the 7,1 cannot run Mojave. If you can change your config.plist to include the "no_compat_check" boot argument you should be able to run Mojave with OpenCore.

However - your best bet is the OLCP discord channel.
Exactly what happened.

I found on the discord server all the help I needed to get my Mac Pro running again! Great community and amazing people over there. On my Mac Pro I need Mojave, because I rely on Aperture.

I have some related questions:

1) Can I use the method described in this thread to run Opencore with Mojave? Or has it the same requirements?

2) Can I have two macOS versions on the same machine (probably two partitions), without them interfering with each other? Updating, launching apps, etc...

Thanks for your help and this great thread.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.