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.
******* thanks so much.

The problem is what crjackson2134 and I have is our audio interface (firewire) works fine.

Although running Pro Tools and quitting a session it won't quit and have to force quit.

I'm just thinking out of the box here. but I noticed on Mojave in the network tab it shows the firewire icon, but in Monterey is gone,

So I'm thinking maybe that's why Pro Tools doesn't see the firewire device to shut it down >?

1703214041208.png
 
  • Like
Reactions: 0134168
******* thanks so much.

The problem is what crjackson2134 and I have is our audio interface (firewire) works fine.

Although running Pro Tools and quitting a session it won't quit and have to force quit.

I'm just thinking out of the box here. but I noticed on Mojave in the network tab it shows the firewire icon, but in Monterey is gone,

So I'm thinking maybe that's why Pro Tools doesn't see the firewire device to shut it down >?

View attachment 2327728
In Mojave Pro Tools gets to shut it down?
 
What I can tell you is that in Monterey, some time ago I had a thunderbolt Titan pci card, and It could see a thunderbolt to Firewire adapter.
 

Attachments

  • Captura de Pantalla 2023-12-22 a las 7.22.09.png
    Captura de Pantalla 2023-12-22 a las 7.22.09.png
    85.3 KB · Views: 55
  • Captura de Pantalla 2023-12-22 a las 7.25.40.png
    Captura de Pantalla 2023-12-22 a las 7.25.40.png
    79.5 KB · Views: 62
Last edited:
According to this post IOFireWireIP.kext was removed with Big Sur - which should be the driver for getting an ethernet device on a FireWire connection.
So, from Big Sur on, you cannot any longer conclude from the network device list whether you have a working FireWire device or not.
 
Yeah in Mojave Pro Tools shut downs as always. What is strange Is this scenario. Running pro Tools all the way back from PT7, through all the version, along with all the MacOS versions up to Mojave and never encountered any program that didn't quit.

So on went on the DUC Avid forum the inquire about and apparently I'm no the only one and even happens with newer Macs.

Tried their solution and still now go.

So I was thinking maybe because the Firewire icon wasn't showing in the network tab maybe it was something missing in the kexts even though it works flawless when when in Pro Tools, other and I have to force quit the program.

I guess I just have to live with it, and maybe a update on OCLP, or Pro Tools might resolve it in the future.

I greatly thank all for actually spending time to help others.
 
Yeah in Mojave Pro Tools shut downs as always. What is strange Is this scenario. Running pro Tools all the way back from PT7, through all the version, along with all the MacOS versions up to Mojave and never encountered any program that didn't quit.

So on went on the DUC Avid forum the inquire about and apparently I'm no the only one and even happens with newer Macs.

Tried their solution and still now go.

So I was thinking maybe because the Firewire icon wasn't showing in the network tab maybe it was something missing in the kexts even though it works flawless when when in Pro Tools, other and I have to force quit the program.

I guess I just have to live with it, and maybe a update on OCLP, or Pro Tools might resolve it in the future.

I greatly thank all for actually spending time to help others.
Thanks for the heads-up on this! I've been running Pro Tools with my firewire Digi 003 on a MacPro 5,1 with Mojave without problems and was contemplating a move to Monterey (only cuz I'm tired of getting messages that my browsers are out-of-date & can't be updated--not a good enough reason when you think about it...)
 
Thanks for the heads-up on this! I've been running Pro Tools with my firewire Digi 003 on a MacPro 5,1 with Mojave without problems and was contemplating a move to Monterey (only cuz I'm tired of getting messages that my browsers are out-of-date & can't be updated--not a good enough reason when you think about it...)
You should be fine if you use Firefox Legacy. When I went to Github that Package installers would not populate in Safari, but went I used Firefox the package installer popped up. Timeline 5:56 explain why you need Firefox Legacy browser.

It's no biggie having to force quit.

Plus it's a good move to be able to stay current with PT 2023.12 and I really dig using Waves Cosmos V14, and you can't run Cosmos without Monterey on PT.

Video is the same for installing Monterey.

Simple here.
 
  • Like
Reactions: quadra605
I have a question about Migration Assistant. I'm planning to install Monterey on a MacBook Air 6,2 using OCLP 0.6.2. I'm aware of the need to revert root patches before attempting to run Migration Assistant. But I've also seen a recommendation to run Migration Assistant before any users have been set up on the system - during initial setup. But since OCLP automatically installs the root patches as needed during setup, how would you revert the root patches on a fresh installation without first setting up a user? As far as I know, to run the GUI and revert the patches, you need to set up a user.

Thanks in advance
 
You should be fine if you use Firefox Legacy. When I went to Github that Package installers would not populate in Safari, but went I used Firefox the package installer popped up. Timeline 5:56 explain why you need Firefox Legacy browser.

It's no biggie having to force quit.

Plus it's a good move to be able to stay current with PT 2023.12 and I really dig using Waves Cosmos V14, and you can't run Cosmos without Monterey on PT.

Video is the same for installing Monterey.

Simple here.
Thanks for the video link! I'm gonna take it slow as I should probably get an SSD drive for the install (I switched everything over to NVMe and I understand there could be boot issues with OC & NVMe), and I need to familiarize myself with the Martin Lo installation instead of OCLP. I understand there is the possibility of bricking my cMP 5,1 with OCLP and since I use it for my daily work, I gotta be extra careful.
 
Thanks for the video link! I'm gonna take it slow as I should probably get an SSD drive for the install (I switched everything over to NVMe and I understand there could be boot issues with OC & NVMe), and I need to familiarize myself with the Martin Lo installation instead of OCLP. I understand there is the possibility of bricking my cMP 5,1 with OCLP and since I use it for my daily work, I gotta be extra careful.
Martin Lo's I feel is more geared to us in the way that you can actually boot into older MacOS's like say I have some older Izotope mastering plugins that run in PT10 on Mt. Lion.

I"m probably going to install a different SSD for Martin's packet. But for now I just simply went this route due to the simplicity with OCLP.

By the way I have Monterey running on a NVMe Samsung 970 Plus with absolutely no issues.

I highly recommend to have Alex reconstruct you rom to avoid any issues down the road.

NVMe ( ALL THE WAY )

All I have to do is remove the NVMe and put in my Mojave NVMe and back to where I started.
 
Last edited:
Today I want to upgrade 4G to 8G memory for my mac mini Late 2009, but not successful. I restore original 4G memory and boot again, I found the boot not from external SSD where I installed Monterey by OCLP, even I reinstall OCLP to interal HDD and external SSD again, the boot is still from internal HDD.
The boot is from external SSD before I upgrade, do I have to install Monterey to external SSD by OCLP again?
 
Today I want to upgrade 4G to 8G memory for my mac mini Late 2009, but not successful. I restore original 4G memory and boot again, I found the boot not from external SSD where I installed Monterey by OCLP, even I reinstall OCLP to interal HDD and external SSD again, the boot is still from internal HDD.
The boot is from external SSD before I upgrade, do I have to install Monterey to external SSD by OCLP again?
Press the option key at boot to get to the Apple Startup Manager. Use the arrow keys to select OCLP. Hold the control-key so that the up arrow turns into a circular arrow and press return to select OCLP as the default boot option and to begin booting OCLP.
 
When I boot, there is two icons, one is internal with El Capitan and one is external with Monterey by OCLP.
Even if I press Control key to select external icon to boot, it still show the same, default on internal icon.
I tried several times, all in the same results, what can I do next?
 

Attachments

  • macboot1.png
    macboot1.png
    320.6 KB · Views: 39
  • macboot2.png
    macboot2.png
    290.3 KB · Views: 45
OpenCore Newbie Here.
I just completed my very first successful patch, a Mojave -> Monterrey upgrade on Mac Pro 5,1 using OCLP 1.3.0.
The process was hard (for me).

After a failed install with 480 without using AMD GOP Injection, I selected AMD GOP injection.
This install worked, with GOP injection selected.

But now, when OCLP offers to patch the internal disk ,
OCLP proposes a build WITHOUT AMD GOP injection.

Is this just what OCLP does by default, or does OCLP know something I do not know about my system ???
OCLP correctly identifies GPU make and model ,architecture (Polaris), metal capability (yes), etc.

Anyone with similar hardware, help!
I am torn between :
1) do what already worked (AMD GOP Injection), OR
2) go with OCLP's suggestion (No GOP Injection.)
But I've already been burned once by attempted install without the injection.

What should I do?

Here are the two build logs to compare: (attached)
 

Attachments

  • buildlogsopencore.txt
    5.8 KB · Views: 89
GOP injection is optional. OCLP does not check the video BIOS installed and will therefore never propose GOP injection automatically. There are always limits …

If you figured out to need it just enable it manually before building OpenCore.

OCLP will auto detect the AMD dGPU.
 
When I boot, there is two icons, one is internal with El Capitan and one is external with Monterey by OCLP.
Even if I press Control key to select external icon to boot, it still show the same, default on internal icon.
I tried several times, all in the same results, what can I do next?
Is this the Apple Startup Manager or OCLP? You should show the entire screen.
Does pressing the Control key change the up arrow to a circular arrow?
Is OCLP stored on an EFI partition or not? Why does it say SSD600GB?
 
Is this the Apple Startup Manager or OCLP? You should show the entire screen.
Does pressing the Control key change the up arrow to a circular arrow?
Is OCLP stored on an EFI partition or not? Why does it say SSD600GB?
I am not sure if it is Apple Startup manager or OCLP, but even if I don't press Option key, the screen is still show, do I have to reset PRAM when boot?
 
I am not sure if it is Apple Startup manager or OCLP, but even if I don't press Option key, the screen is still show, do I have to reset PRAM when boot?
Apple Startup Manager should not appear unless you hold option key.
The OCLP boot picker looks different than Apple Startup Manager which is why I asked for a picture of the entire screen.
The OCLP boot picker has a release version in the bottom right corner and it may have a shutdown and restart button at the bottom middle of the screen.

Seems like OCLP works but Monterey won't boot. If you select Monterey it just reboots back into OCLP?

Maybe zap the PRAM so you can get into Apple Startup Manager. What do you see in Apple Startup Manager? Do you have more than one OCLP? Maybe one of them works.
 
Apple Startup Manager should not appear unless you hold option key.
The OCLP boot picker looks different than Apple Startup Manager which is why I asked for a picture of the entire screen.
The OCLP boot picker has a release version in the bottom right corner and it may have a shutdown and restart button at the bottom middle of the screen.

Seems like OCLP works but Monterey won't boot. If you select Monterey it just reboots back into OCLP?

Maybe zap the PRAM so you can get into Apple Startup Manager. What do you see in Apple Startup Manager? Do you have more than one OCLP? Maybe one of them works.
There have a shutdown and restart button at the bottom middle of the screen, so this should be OCLP.
I named external SSD to SSD500GB, only one OCLP on SSD500GB, when I pressed Ctrl key and select Monterey (SSD500GB), the Monterey will be boot, it still select Internal HDD default when I reboot again.
 
Video artifacts at login

Mac - MacBook Air 6,2 - mid 2013, 13", Haswell iGPU
OCLP version - 0.6.2
MacOS Monterey 12.7.1

Perhaps a cosmetic issue, but I wonder if it's to be expected. The installation completed successfully, but when booting the Mac, just before the user's login screen appears, the entire display fills up with a flash of multicolored (mainly pink) light, with both horizontal lines and vertical columms being visible. It does this for perhaps 0.2 seconds, then it disappears. I have concerns because it looks a lot like whatever I've seen in the past with a Mac that had a failed video card. Except it's not permanent.

I checked on whether root patches had been applied, and apparently, with Intel HD 5000 graphics and Monterey none are required. At least that's what OCLP says when I click on Post Install Root Patch.

I also got the Monterey volume hash mismatch error notification after initial installation. That hasn't repeated.

Thanks in advance
 
I named SSD as "SSD500GB" when I format my SSD, then I installed Monterey by OCLP, now the "SSD500GB" as lable show on boot picker even if I modified name to "Monterey SSD", how can I change this to "Monterey SSD"?
 
On a early 2011 MacBook Pro 8,1 with a Kingston A400 480GB SSD drive. I was able to install Monterey 12.6.3 and OLPC 0.6.1 on it last year. It became sluggish. Applying OLPC 1.3.0 root patch did not help.

I tried upgrading to the latest Monterey 12.7.2, OCLP 1.3.0 and get the "A require firmware update cannot be installed".

I wipe the drive and reinstalled High Sierra 10.12.6 (last version supported). This was successful. I try upgrading to Ventura 13.6.3, OCLP 1.3.0 again and get the same message of "A require firmware update cannot be installed". I tried doing the same process with Monterey 12.7.2 OLPC 1.3.0 and again with the same message of "A require firmware update cannot be installed".

Any ideas?

Note I was successful installing and running Ventura 13.6.3, OCLP 1.3.0 on a early 2009 iMac 9,1 and with same type of Kingston A400 480GB SSD drive.

Also, I was successful installing and running Monterey 12.7.2, OCLP 1.3.0 on a 2010 MacBook Pro 7,1 with same type of Kingston A400 480GB SSD drive.
 
I replaced internal SDD to SSD and installed Sonoma 14.1.1 by OCLP 1.3.0, it is better than Monterey 12.7.2 on external SSD until now.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.