Is there a list somewhere that has compatible cards with that chipset? I got this one at the time as it came highly recommended for compatibility and haven't had an issue until I wanted to try booting from external ssd.
Thread summary for latest recommendations. This thread refers to PCIe cards for adding USB 3.0 and 3.1 to classic Mac Pros. General Notes: The USB 3.0 cards in this list support UASP for faster transfer speeds and reduced CPU utilization (exceptions to this are noted). The USB 3.0 cards in...
forums.macrumors.com
Btw, booting USB3.0 is extremely flaky even after you get everything exactly right and does not worth changing your very good USB3 card to one FL1100 based.
Is there a list somewhere that has compatible cards with that chipset? I got this one at the time as it came highly recommended for compatibility and haven't had an issue until I wanted to try booting from external ssd. I guess I'm just looking for the best option for fastest USB speeds via PCIe with external USB booting... but aware that I'm limited to 2.0 speeds.
Thanks guys. Yeah I was just hoping to poke around monterey on an external ssd through usb3 just to leave the accelsior e2 with big sur alone, but not worth the hassle if my usb3 card works fine otherwise.
Since I have a good bootable clone of my big sur setup, I decided to update Martin Lo's package to the last/latest 1.0.1 and works great.
Now that I'm safe to update my big sir (on the accelsior) to monterey, it's not taking for some reason. I watched the video to tweak a couple of things in the config and the install takes, but when it reboots, the install option in the bootpicker just loops back to the bootpicker and I can only go back into big sur. I'm trying again as we speak but something isn't letting monterey complete the install. Anyone dealt with this?
Thanks guys. Yeah I was just hoping to poke around monterey on an external ssd through usb3 just to leave the accelsior e2 with big sur alone, but not worth the hassle if my usb3 card works fine otherwise.
Since I have a good bootable clone of my big sur setup, I decided to update Martin Lo's package to the last/latest 1.0.1 and works great.
Now that I'm safe to update my big sir (on the accelsior) to monterey, it's not taking for some reason. I watched the video to tweak a couple of things in the config and the install takes, but when it reboots, the install option in the bootpicker just loops back to the bootpicker and I can only go back into big sur. I'm trying again as we speak but something isn't letting monterey complete the install. Anyone dealt with this?
It will leave everything intact you have. Then just do a clean upgrade to Monterey using OCLP on the accelsior.
You are making it harder than it needs to be.
You will leave the BIG SUR alone, and will be using a new container.
Be patient when installing. It will loop to boot picker at least five times, then the last loop back you will see the % graph. That's when you know you are almost done.
I'm not making it harder than it needs to. I'm literally following the instructions from Martin Lo for updating Monterey in place of Big Sur.
The problem before was that when the install finished and rebooted, when I clicked the install option on the bootpicker, it would fail and just sent me back to the bootpicker in a loop.
For whatever reason, in the end all I needed to do was attempt the install a second time and I'm now on Monterey.
Thanks for the help guys. Now I can poke around and make sure everything works for me (knowing I've got a bootable clone of my boot drive with big sur as a backup).
The next task is determining which NVME adapter to get for a couple of 1TB blades. Something like the Mcfiver or the Ableconn PEXM2-130.
As for blades, I was wanting a couple of the samsung 970 evo plus but they're gone everywhere. Unsure what to get as a second best option that's available (based on the tested blade list). Any recommendations on nvme adaptor/blades welcome. Trying to not break the bank but still want dependable stuff and the accelsior e2 500gb just ain't quite up to snuff anymore.
Unfortunately, it appears monterey's latest software update (and then changing the flags back in the config file of Martin Lo's 1.0.1) has broken the firewire connection to my Apogee ensemble. I don't see a configurator anymore with the newer 1.0.1. Anyone have any idea how to try to get firewire working again?
This was an in-place upgrade from big sur to monterey.
Unfortunately, it appears monterey's latest software update (and then changing the flags back in the config file of Martin Lo's 1.0.1) has broken the firewire connection to my Apogee ensemble. I don't see a configurator anymore with the newer 1.0.1. Anyone have any idea how to try to get firewire working again?
This was an in-place upgrade from big sur to monterey.
If I unplug the interface, run that, plug it back in, everything works again. Not sure if there's an advantage for this specific scenario to move from Marin Lo's 1.0.1 to OCLP or not.
Now I just need to find out how to run that kept during boot (like it did for Big Sur) so I don't have to do that after booting (since there's no configurater with the latest 1.0.1 from Martin Lo.
Update: I've tried copying the kext into the OC kext folder and adding to the config.plist with propertree, but still won't load the driver during boot. Basically I can turn off the interface, run the command above, turn it back on and it works but would love for it to be automatic during boot.
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 1.0.1]
For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in Catalina and newer macOS for dual processor cMP.
I don't mind you guys discuss anything about this package, but I have no plan to provide any explanation about OpenCore at here. If you want to know more, please join cdf's OpenCore thread. For new joiners, please make sure read through the FAQ in post #1 before you ask anything.
The attached packages (0.9.4 and before) included Clover Configurator (for mounting the EFI partition only, please do NOT use it to edit the OpenCore config plist) and a complete preconfigured OpenCore. All credits goes to the developer teams. If you want to show your support, please give them donation (declaration of interest： I am NOT in any of their developer teams). Since 0.9.5, the Clover Configurator (which we use it only to mount the EFI partitions) is replaced by Macschrauber's Mount ESP Tool (the Bless OpenCore script is also credit to Macschrauber).
Macschrauber is working very hard to keep improving the Mount / Unmount / Bless script. However, there is a macOS internal protection（Gatekeeper) may generate a quarantine flag to the scripts (and the RadeonGadget app indeed) when you download it. Which will make Finder shows you a "damaged" warning when you try to run the scripts. This is a known issue, and is addressed in the latest version. In the current version, if Finder not allow you to run the apps, please right click the apps, then choose "open". If still doesn't work, there is a script (with a self explaining name - Run this to fix the "Damaged" app) should able to fix the issue for you. That "fix" script will NOT change any security settings / mod any system files on your computer. All it does is just to remove the quarantine flags from the downloaded files for you.
For Clover Configurator and OpenCore developers teams, please let me know if you want me to remove the associated software inside my attachment in this post.
This is a "one package fit all" solution. So, it's designed to fit as much setup as possible, which may not be optimized for your setup (e.g. The auto detect HiDPI function may not work correctly for ultra wide screen. For those who are running ultra wide monitor, the Apple logo may be too large during boot). You have to do the optimization by yourself (details in the OpenCore manual, some info also available in cdf's OpenCore thread).
Anyway, for those who have RX 460 or newer AMD GPU, this package should gives you:
Boot screen (via GOP for unflashed card, including some Nvidia card)
Firmware protection (to run Windows in EFI mode without risking the cMP bootROM)
HWAccel (H264 / HEVC hardware decode + encode in Mojave and newer macOS)
ability to watch DRM streaming content (Mojave and newer macOS)
Boot picker (only support EFI systems, tested with Apple wired keyboard, Magic Mouse, and Magic Keyboard, 10s timeout. If you can't see this. Just don't touch the keyboard, and your cMP should continue to boot to desktop)
NVMe and SATA drives on PCIe card show up as internal
Support for Apple USB SuperDrive
TRIM (regardless trimforce status)
Ability to run non-GUI 32bit software in Catalina
Ability to reset NVRAM in boot picker (disabled at this moment to align with the native Apple boot manager)
Ability to run any natively supported ancient OSX with modern graphic card e.g. Radeon VII in 10.6.8 (only can display, no acceleration) [Update 5th May 2020: Sierra and High Sierra may not fully supported yet. Thanks for pierrox's report]
Ability to boot Catalina / Big Sur / Monterey and the associated Recovery Partition [SurPlus (credit to Syncretic) is included and enabled by default to fix the racing condition in macOS 11.3 or later][AVXPel is also included. another credit to Syncretic][ASPP-Override is included for macOS 12.3, credit to dortania]
Sleep should work (tested on my cMP, but I can't guarantee it also work with your setup)
Possible to run 8x32GB RAM in macOS (user need to mod the config.plist manually. Replace the false below CustomMemory to true)
Enable HDMI Audio for some graphic cards
Ability to monitor modern AMD GPU's temperature (by using the attached RadeonGadget. Credit to Aluveitie)
Possible to run AQC107S 10Gbps network in Monterey 12.3 and newer (credit to Jazzzy)
It's impossible for me (and other voluntary helpers) to test every single function in all situations. So, as usual, use at your own risk. But you are welcome to report back if there is any problem / error.
If you want to test run OpenCore, you can install this package onto a bootable USB thumb drive.
Quite a few users reported that can't boot OpenCore from NVMe, analysis shows that depends on hard drives config. It's hard to explain which exact scenario may hit this bug. So, please avoid to install this package on NVMe. You can install this package on ANY SATA drive with virtually no performance lost, not necessary your boot drive.
If you want to remove OpenCore, please mount the EFI partition by using Clover Configurator, then remove BOOT and OC folders inside the EFI folder on EFI partition.
If your cMP stuck at boot. After shutdown, please pull out the hard drive that contain OpenCore, then perform NVRAM reset. If still doesn't work, then please install your emergency graphic card that has boot screen. Hold Option to boot, then select your backup boot drive. This should disable OpenCore.
For those who want to report issue / error. Please provide details (e.g. which graphic card, OpenCore installed on NVMe / SATA drive, the issue's details, etc) otherwise it will be extremely hard (or even impossible) for me to work out what's wrong.
If you installed Lilu for whatever reason (e.g. because of innie), or applied my previous non-OpenCore HWAccel mod, please remove them or revert them. For Lilu + WEG, that means delete Lilu.kext in /Library/Extensions/ and reboot (caution: these kexts may be installed in System/Library/Extensions/ as well). For hex edit method, that means delete AppleGVA.framework in /System/Library/PrivateFrameworks/ and rename AppleGVA.framework.bak to AppleGVA.framework. Warning: My packages already have Lilu and WEG included, "double installation" of these kexts will cause macOS boot failure.
For PULSE RX580, users reported that only can see boot screen when boot from gaming mode. There may be no UEFI GOP in the compute mode's ROM.
Also for RX580, users reported that they can't see the screen during macOS installation / update. Analysis shows that there is bug in macOS. When multiple monitors connected, the installation / update will process as expected, but all screens may remain black. Therefore, for RX580 (may be also applicable to other Polaris GPU), please only connect one monitor when you want to install / update macOS (if you prefer to able to see the progress).
I tried to make the installation as simple as possible. However, I still demand you to learn some very basic skills. Those skills are very useful in the recovery process if something goes wrong. Anyway, here is what you need to do
[Optional] 3x NVRAM reset to avoid some unknown issues.
Disable SIP (must do, especially if you performed step 1)
Download the attachment in this post (if the newer package has compatibility issue. You may download the older package, same installation procedures.)
Follow the steps in this video (please turn on and read the subtitle) [N.B. some tools are updated, but they are very self explanatory. Therefore, I have no plan to create another video just to show how to use the new tools at this moment]
For Big Sur and Monterey, if some ports on your graphic card are disabled, please follow the steps in this video to re-enable them.
Reboot
For existing OpenCore users, you may follow the step in this video to update OpenCore [For those who installed OC onto the Windows drive, please make sure you only replace the OC files, but not the whole EFI folder]
Additional option 1: If you have 4K screen, and you want to have "Retina" boot screen. You may do this. [Depreciated in 0.7.6, which Retina should be enabled automatically on 4K monitor]
Additional option 2: If you have a flashed Thunderbolt 3 card, you can install that in slot 4, then enable Thunderbolt 3 support by doing this.
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. [N.B. you should revert the changes after macOS installation completed. This special setting is not designed for daily use]
Additional option 4: If you have legacy wifi card, you may try the follow steps to re-activate the old wifi card in Big Sur (only avail in my 0.6.4 package or above)
Additional option 5: To enable legacy BT support in the latest unsupported OS, you may turn on both BlueToolFixUp and BlueTooth-Spoof kext.
Additional option 6: Since 0.6.3, I allow OC to take over SIP control. There are various reasons, but anyway, that's defaulted to be disabled. If you want to re-enable SIP, please follow the steps in this video. (please turn on the English subtitle when you watch this video, some useful info at there)
For FCP(X) users, if you want to export HEVC video by using HWAccel, you will need Compressor.
[N.B. The setting MUST identical to the one that I show in the video. Otherwise, HEVC hardware encoding may not work]
If you want to completely uninstall my OpenCore package, please follow the steps in this video.
N.B. Unflashed graphic card means "the ROM is never modified". For those who bought used card, and can't see the boot screen, most likely the last user flashed the card with modified ROM (e.g. downvolt for mining). In this case, you can go to TechPowerUp to find a ROM that fit your own card, and flash it.
Hey, I know this is old but will stock OCLP also work? or does it HAVE to be this patched version? I have an iMac 2011 running OCLP Sequoia with upgraded hardware and was wondering if the un-modded OCLP will work fine. Planning on splitting the 1TB drive into 2x500gb partitions for this. Any and all responses are appreciated
forums.macrumors.com
