Yes. I noticed the FW boot settings in OCLP but I only wanted FW mount support, so I didn't inject those. Mine also crashed using FW Target mode but adding any bus powered FW disk does the same thing, unfortunately.
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
Ext. powered FW disks work as intended, btw.
Ok, that's interesting. Not sure what the issue is then. Bus powered drives don't need a lot of juice and are well within FW400 specs, not sure if FW800 bumps up the power delivered. Either way, everything hangs once you plug it in. Maybe I should try a different cable.Ext. powered FW disks work as intended, btw.
[edit] Just tried with a shorter cable I know works. Still locks up the screen. Mouse pointer won't move nor the keyboard register a press. Total freeze. Maybe it's Covid.
Last edited:
Out of 4 enclosures, this one works every time.
| G-Tech 0G04412 ev Series SATA to FireWire Adapter 0G04412 Product ID: GTC-0G04412 |
Some very bad news! OCLP has become a victim of Russian aggression. Development will cease indefinitely. Read about it on Discord. 👀
OCLP has become a victim of Russian aggression. Development will cease indefinitely. Read about it on Discord. 👀
With FW and Monterey, I had observed the following.
- when wanting to boot from FW, OCLP needs the according flag in Settings / Misc Settings / FireWire Boot and then boots fine from a drive connected to FW. But this I've used this only for booting an installer, not for booting Monterey
- however only without this setting, I can connect a drive to FW in an already booted system... otherwise system freezes as you describe.
As far as I remember. Didn't use it since a while now. See post #4,171 .
Worth mentioning that booting from and using USB3 (on a nanoTECH expresscard, FL1100 chipset) with a storage medium, I see similar behaviour with Monterey, while OK with Big Sur.
Last edited:
Whose post and what specific topic you mean?Some very bad news!
if you reread discord, I think you used the word indefinitely incorrectly.Some very bad news!
The statement indicated temporarily as they are dealing with family issue's.
none the less it is very sad news on both fronts
Do you know when this war ends? I stand by the choice of words.💪
There is a direct link to github on OpenCore Patcher Paradise, if you used it you would know that. 🤷♂️
So I asked you to point me to the proper topic on Discord: Announcements, Anything-Non-Help or OpenCore 1 (2, 3). Now I guess you meant Development - Monterey section, right?
I gave this a shot. Reinstalled OCLP and made sure the FW boot flag was off. Rebooted. Plugged a FW drive in. The mouse kept moving for a second or two then freeze time.
I'll just have to avoid FW. Fortunately, it's not the key for this Mini as USB 3 is much faster.
If you were on the Paradise, it is the entry "github" just below "public development" and above "updates."
It's exactly the thing I asked you for three hours agoIf you were on the Paradise, it is the entry "github" just below "public development" and above "updates."
The single magic word was all I wanted, not all those "if you were on the Paradise". I was, believe me.While OCLP uses the Catalina FireWire kexts for enabling FireWire booting, you could also use the Big Sur or Monterey kexts.
Catalina kexts were chosen in order to have them work on Catalina, Big Sur and Monterey. Remember that Catalina was the first macOS version to not allow FireWire booting. It does so by simply excluding them from the kexts that are loaded together with the kernel.
OpenCore forces the kernel to load the kexts it wants to get loaded, so you can simply overwrite the kexts installed by OCLP with the kexts from /System/Library/Extensions of your macOS installation.
You could try that in order to see if that fixes the crashing issue.
Sorry, I'm not very good at quibbling. You found the info you wanted.It's exactly the thing I asked you for three hours ago
I can´t help if you're having a trackpad hardware issue, otherwise If your problem is a missed trackpad pref panel try to modify manually com.apple.AppleMultitouchTrackpad.plist (This happens when you live without a battery on your mac)
Just wanting to thank the developers for making it possible to run Monterey on most cheap Intel Macs I can buy for about €200. With two drives, my Mac mini has 2TB of storage, something which would have cost me a fortune on my MacBook Air.
Everything works fine for the most part. I only had these small issues:
1. Sometimes the machine gets stuck in the boot process, although turning it off and restarting always seems to fix it.
2. I have never been able to get Boot Camp working with OpenCore and I simply gave up on it.
3. My microphone (Line-In) port does not seem to function.
It is sad to see how Apple simply abandons older hardware. If you can run Monterey on a 2014 Mac mini with 4GB of RAM, why would it not work on a high end Mac mini from 2012 or 2011?
Everything works fine for the most part. I only had these small issues:
1. Sometimes the machine gets stuck in the boot process, although turning it off and restarting always seems to fix it.
2. I have never been able to get Boot Camp working with OpenCore and I simply gave up on it.
3. My microphone (Line-In) port does not seem to function.
It is sad to see how Apple simply abandons older hardware. If you can run Monterey on a 2014 Mac mini with 4GB of RAM, why would it not work on a high end Mac mini from 2012 or 2011?
You can install windows without any problem. Just don´t use bootcamp.
I have had great success with the standard OCLP recommendations for install of Win 10 with Bootcamp: https://dortania.github.io/OpenCore-Legacy-Patcher/WINDOWS.html#disk-formatting
FWIW.
I prefer
I prefer a Legacy installation. No bootcamp or OCLP involved.