Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

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.
cdf said:
11.2.3 has always been functional. The issue is with the 11.3 betas.
Click to expand...
I've already asked twice, but no answer was provided. Are there any known problems with the Titan-Ridge Thunderbolt 3 PCI card in Big Sur 11.3 betas? If so, is there any hope that the release version of 11.3 will solve those issues? Can OpenCore alleviate the problem, if any?
 
PeterHolbrook said:
I've already asked twice, but no answer was provided. Are there any known problems with the Titan-Ridge Thunderbolt 3 PCI card in Big Sur 11.3 betas? If so, is there any hope that the release version of 11.3 will solve those issues? Can OpenCore alleviate the problem, if any?
Click to expand...
Flashed Titan Ridge cards were reported to be problematic in hacks. See the link I included in post #7,644. I certainly hope that the release version of 11.3 will be issue free!
 
  • Like
Reactions: PeterHolbrook
Can somebody point to the right solution.

  1. Mac Pro 2010, 3.46Ghz Dual CPUs, Vega 56.
  2. Opencore 0.6.8
  3. Catalina 10.5.7

Installed all works fine except wifi. Have the following code in the OC config.plist. The wifi icon shows up on the top bar. But it seems that it would try to scan the wifi networks only for a while. But got nothing and eventually grep out every time it performs a scan to wifi network. I've already followed the post-installation guide here and changed to 19.0.0. The wifi Preference also showing wifi is On. But it just wouldn't show the scanning or scanned network to join:

According to Mac Pro 5,1 in the URL table. The wifi chip should be BCM4322 series.
Still no luck. The Wifi would scan for a while but always grep out finally. It wouldn't return any wifi ESSID in the air. Any helps would be appreciated.


<dict>
<key>Comment</key>
<string></string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
<key>Enabled</key>
<true/>
<key>MaxKernel</key>
<string>20.99.99</string>
<key>MinKernel</key>
<string>19.0.0</string>
<key>ExecutablePath</key>
<string>Contents/MacOS/IO80211Mojave</string>
<key>Arch</key>
<string>Any</string>
<key>BundlePath</key>
<string>IO80211Mojave.kext</string>
</dict>
<dict>
<key>Comment</key>
<string></string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
<key>Enabled</key>
<true/>
<key>MaxKernel</key>
<string>20.99.99</string>
<key>MinKernel</key>
<string>19.0.0</string>
<key>ExecutablePath</key>
<string>Contents/MacOS/AirPortBrcm4331</string>
<key>Arch</key>
<string>Any</string>
<key>BundlePath</key>
<string>IO80211Mojave.kext/Contents/PlugIns/AirPortBrcm4331.kext</string>
</dict>
 
Last edited:
TECK said:
I personally do only the NVRAM reset with a wired Apple keyboard (3 chimes), since my vanilla Mojave is on Sata1 SSD (tray 1) and already contains all flashing tools. I do all my flashing with a wired Apple keyboard, for safety reasons. I don't even login into iCloud on that disk, is 100% vanilla. That is the only case you don't need to remove all disks and instead perform only a NVRAM reset. Say your vanilla Mojave is on Sata2 SSD (tray 2), this will not work, it must be on Sata1. This way, I never open the case and thinker with hardware inside.
Click to expand...
You can also plug your Apple BT keyboard into the front/back builtin USB ports with the charging cable attached.
 
Jimboee said:
This is posted in cMP 5,1 forum but if you look at the screenshot, his MP is not cMP. There are 12 DDR4 slots in that MP.
Click to expand...
Unless I am mistaken, I think what you're seeing there is BS displaying 12 slots because of how it saw the cMP on his configuration. I believe the system was seeing it as the new MP at that time.
 
cdf said:
Take a look at the guide. There is no requirement for an external disk. OpenCore can be installed on the EFI partition of the Big Sur disk. A second disk (internal or external) with Mojave is recommended to help with the initial installation and to use in case of a misconfiguration.
Click to expand...
Alright,
I followed successfully on 2 setups (one with exta disk, one over built-in SSD) and upgraded to Big Sur
*BOTH* machine rebooted without any networking. The clean install on new disk just has no network devices. The upgraded machines has placeholder in Networking for ethernet and wifi, but no drivers and no joy.
I attempted adding a few .kext with obvious disastrous effect!
You are right, slightly easier if you have a sacrificial boot device :-D
At any rate, cannot figure out why it is not detecting any networking.
I attempted to change the device ID to point to the real hardware and still no luck.
Any suggestions?
 
JeDiGM said:
You can also plug your Apple BT keyboard into the front/back builtin USB ports with the charging cable attached.
Click to expand...
Is not the same, for example in Big Sur, the Apple Magic keyboard is not seen in certain cases (known bug), if is attached with the USB cable. The only keyboard that works all the time in any situation is a real USB wired keybaord.
 
TECK said:
Is not the same, for example in Big Sur, the Apple Magic keyboard is not seen in certain cases (known bug), if is attached with the USB cable. The only keyboard that works all the time in any situation is a real USB wired keybaord.
Click to expand...
Fair enough. I was referring specifically for NVRAM resets or other operations that need to be done prior to the system loading the os as you had mentioned in your original post. I thought it might be helpful for people to know it's an option if they don't have a USB keyboard available in those cases.
 
  • Like
Reactions: TECK
After Big Sur upgrade, macfuse isn't working. Anyone else seeing this? I don't think the kext is loading. I've searched elsewhere but not finding anything that works.

Resolved - thanks
 
Last edited:
I’ve had my cMP running Mojave for about a year now with a Sapphire RX560 4GB GPU but haven’t been able to get the boot screen to work. Actually, I had it briefly at one point but uninstalled/reinstalled and updated OC a few times since and have never had it work again. This isn’t a huge deal for me since I’m only using one boot drive but now I’m trying to update to Catalina and it’s not working. I’m wondering if the issues are related. I’m using the “Dual Socket - Update On” EFI provided by CreatePro which should allow software updates through System Preferences but since Big Sur is the current OSX and some of my software isn’t compatible, I downloaded the Catalina installer. I ran it as usual but upon restart it won’t boot. I had also made a bootable USB installer prior to installing via the installer app so I tried that. Since I don’t have a boot screen, I reboot into Recovery Mode, select the install USB as my Startup Disk and reboot but after about a minute my machine just shuts off. I’m sure the solution is here somewhere but this thread is 314 pages long. Can anyone shine some light on this for me?
 
diamondj421 said:
I’ve had my cMP running Mojave for about a year now with a Sapphire RX560 4GB GPU but haven’t been able to get the boot screen to work. Actually, I had it briefly at one point but uninstalled/reinstalled and updated OC a few times since and have never had it work again. This isn’t a huge deal for me since I’m only using one boot drive but now I’m trying to update to Catalina and it’s not working. I’m wondering if the issues are related. I’m using the “Dual Socket - Update On” EFI provided by CreatePro which should allow software updates through System Preferences but since Big Sur is the current OSX and some of my software isn’t compatible, I downloaded the Catalina installer. I ran it as usual but upon restart it won’t boot. I had also made a bootable USB installer prior to installing via the installer app so I tried that. Since I don’t have a boot screen, I reboot into Recovery Mode, select the install USB as my Startup Disk and reboot but after about a minute my machine just shuts off. I’m sure the solution is here somewhere but this thread is 314 pages long. Can anyone shine some light on this for me?
Click to expand...

Same here. Back in last year when the Opencore and Catalina were first introduced. I was afraid of bugs and had been staying on Mojave till yesterday. So actually I jumped directly from 10.14.6 to 10.15.7 overnight.

I followed their official steps in the first page. I also couldn't get it worked. Hanged in the boot screen.

Then I tried h9826790's hardware acceleration batch (zip). It works out. You just need to drop the entire EFI folder into the Opencore drive's EFI folder. Then boot into recovery mode to "bless" the partition for once. And begin the Catalina installation from Mojave. That's all.

Ignore the dual socket thing. It is never a problem. I am on a dual socket Mac Pro 5,1 3.46Ghz system. When I ignored the dual socket instruction. It works out. If I followed their instruction. It hangs out.

Credit goes h9826790 in this case. Download attachment (custom version 0.6.8 from h9826790)
 
Last edited:
solaris8x86 said:
Same here. Back in last year when the Opencore and Catalina were first introduced. I was afraid of bugs and had been staying on Mojave till yesterday. So actually I jumped directly from 10.14.6 to 10.15.7 overnight.

I followed their official steps in the first page. I also couldn't get it worked. Hanged in the boot screen.

Then I tried h9826790's hardware acceleration batch (zip). It works out. You just need to drop the entire EFI folder into the Opencore drive's EFI folder. Then boot into recovery mode to "bless" the partition for once. And begin the Catalina installation from Mojave. That's all.

Ignore the dual socket thing. It is never a problem. I am on a dual socket Mac Pro 5,1 3.46Ghz system. When I ignored the dual socket instruction. It works out. If I followed their instruction. It hangs out.

Credit goes h9826790 in this case. Download attachment (custom version 0.6.8 from h9826790)
Click to expand...
Talk about great timing, huh? Lol. Appreciate it!
 
Alright... So I finally got Catalina installed. I couldn't get it working with h9826790's 0.6.8 so I ended up resorting to the DosDude1 patch. Even after that, it took me about 3 hours to get it booting. I eventually realized it was my OWC Accelsior E2 PCIe SATA drive that was causing the issue.

I've spent the last few hours searching the forums for a solution but can't find a solid answer. I've seen a lot of posts about using Innie to get PCIe SATA drives to be recognized as internal but none say that the disk being external was keeping them from booting so I'm not sure that's the solution. I don't want to run Innie if it's strictly for dual boot/aesthetic purposes since neither really are concerns for me.

Everything else is working wonderfully without the Accelsior (finally got the boot screen back!!!) but unfortunately the drive in question contains all of my Pro Tools files and they're just a LITTLE bit important. Of course, I haven't backed up that drive recently. That would've made my life much easier and my brain seems to hate that. Any ideas/suggestions?
 
diamondj421 said:
Alright... So I finally got Catalina installed. I couldn't get it working with h9826790's 0.6.8 so I ended up resorting to the DosDude1 patch. Even after that, it took me about 3 hours to get it booting. I eventually realized it was my OWC Accelsior E2 PCIe SATA drive that was causing the issue.

I've spent the last few hours searching the forums for a solution but can't find a solid answer. I've seen a lot of posts about using Innie to get PCIe SATA drives to be recognized as internal but none say that the disk being external was keeping them from booting so I'm not sure that's the solution. I don't want to run Innie if it's strictly for dual boot/aesthetic purposes since neither really are concerns for me.

Everything else is working wonderfully without the Accelsior (finally got the boot screen back!!!) but unfortunately the drive in question contains all of my Pro Tools files and they're just a LITTLE bit important. Of course, I haven't backed up that drive recently. That would've made my life much easier and my brain seems to hate that. Any ideas/suggestions?
Click to expand...


Great. It is working now!

It doesn't work on the external drive such as SAS drives/enclosure. I tried too. Booting from SAS controller. No luck.
However, it works on my internal PCI-e adaptered NVMe drive and it is recognized as an internal drive. Not external drive. I think it is chip-depend on your PCI-e controller.

I'm on Catalina now after 18 months of waiting and holding on this upgrade from Mojave. I was very patient because I don't want either the Opencore or Catalina ruins my Mac data. At that time, both Catalina and Opencore were very buggy.

The Catalina seems run a little bit faster than Mojave in all aspects. No matter the mouse response, launching speed of apps and Final Cut Pro timeline response. But I lost the 32bit software compatibility in this part which is deadly to me.

I've some very legacy software such as DTS Master Audio Suite is a 32bit Java application and some arcade 32bit street-game-center emulation games runs on emulator are now all dead in the water. When I have to compile DTS audio track or to play this very legacy childhood games. I've to go back my Mojave boot drive.

Also, the hardware acceleration supports to my Vega 56 is amazing. Now I can export FCPX project to HEVC or h264 at lightning speed. I compare my benchmark of GPU that it is very close or even a little faster than a MacBook Pro 2019 16's full-spec model. Now, I've got a Metal/OpenCL score over 50,000 on Geekbench 5. Which is awesome.

Basically, Opencore 0.6.8 does its job very solid and amazingly. The stability is very ok too.
One word. It is just very Fast. As fast as a new MacBook Pro model.


** one recap: I tried to install Catalina to the stock SATA3 slot SSD and PCI-e NVMe respectively to check out which is faster. The performance seems very close. Which is weird. It's supposed that the NvME drive should run faster by Catalina but it is not the case. I couldn't notice any different when operating on any apps. But when measuring with a hard drive benchmark app such as AJA System Tool. Of course, they are different. Just when you are doing with basic working tasks. The SATA3 SSD and PCI-e NvME makes no different in feeling the performance in normal user operation. Including on Final Cut Pro. which is unexpected the SATA3 slot SSD could be that fast... in feeling.
 
Last edited:
diamondj421 said:
Alright... So I finally got Catalina installed. I couldn't get it working with h9826790's 0.6.8 so I ended up resorting to the DosDude1 patch. Even after that, it took me about 3 hours to get it booting. I eventually realized it was my OWC Accelsior E2 PCIe SATA drive that was causing the issue.

I've spent the last few hours searching the forums for a solution but can't find a solid answer. I've seen a lot of posts about using Innie to get PCIe SATA drives to be recognized as internal but none say that the disk being external was keeping them from booting so I'm not sure that's the solution. I don't want to run Innie if it's strictly for dual boot/aesthetic purposes since neither really are concerns for me.

Everything else is working wonderfully without the Accelsior (finally got the boot screen back!!!) but unfortunately the drive in question contains all of my Pro Tools files and they're just a LITTLE bit important. Of course, I haven't backed up that drive recently. That would've made my life much easier and my brain seems to hate that. Any ideas/suggestions?
Click to expand...
I remember I had problems with the original Accelsior (two 480GB, $930 each back in 2012) but I believe that was with Windows BIOS booting not working with some GPUs or you had to change slots or something.

I found my tech support e-mails about the problems. The problem was with a HD 5870 1024MB in slot 1 and the Accelsior in slot 2 in a MacPro3,1. It won't boot Windows unless the Accelsior is in slot 4. Or unless the GPU is replaced with a 8800 GT 512MB or a HD 4870 512MB.

Those problems were with BIOS. There was also some EFI issues where the Accelsior drives would not appear in Startup Manager. The Accelsior drives would not appear in rEFIt or rEFInd unless they were installed on the Accelsior. In that case, the built-in drives wouldn't appear.

Another problem with the Accelsior devices is that they use a non-standard form factor for the blades and OWC doesn't have an adapter to use the blades as normal SATA drives.
https://eshop.macsales.com/blog/136...tosh-and-pc-supported-bootable-pcie-ssd-card/
https://eshop.macsales.com/item/OWC/SSDPHW2R480/

The moral of this story is - use SSDs in the Mac Pro drive bays and/or stay away from SATA controllers that have weird firmwares (for BIOS or EFI).
 
I had all sorts of issues with my Accelsior (Slot 3) and finally just gave up on it and plugged my drive into the unused lower port for the DVD drive in the end.

Main issue I had was random but frequent instances when there would be an extra 30 or so seconds added to boot time. When that happened, the drive connected would not show up.

I didn't link it to rEFInd (RefindPlus). I guess I should dig it out and try it again since it has been about a year and many changes have gone into RP since.
 
Like solaris9x86 I've been lurking here occasionally over the past year watching OC developments, and last week decided to take the plunge from Mojave. My rig is an (actual) 2012 DP with a flashed GTX680, and my boot drive for the last 3 years or so has been an EVO 840 Pro 512G in an Accelsior PCIe card. It's been rock solid with Mojave (and prior), with the only quirk being the boot drive shows up as an external (but no issues with this other than aesthetics).

Last week I replaced the 840 Pro with an 870 1TB and cloned my boot drive to to it. It's been rock solid so far with Mojave. I was originally going to go straight to BS, but a dirty upgrade with h9826790's 0.6.8 OC package failed. It worked flawlessly when I tried a clean install after wiping the drive, but after discovering VMware is irrevocably broken on the 5,1 in Big Sur (I was prepared to lose some 32-bit stuff -- hello Steam, but no VMWare is a bridge too far) I decided to go back to Catalina. Yesterday I recloned my Mojave boot drive and upgraded it to 10.15.7 (+ the latest security update) without a hitch. The upgrade actually seemed to go faster on this box than on the real iMacs (with SSDs) I manage at work.

The boot drive (and OC) are both hosted on the 870 in the Accelsior card, and I have had no issues at all so far (across multiple cold and warm reboots and PRAM zaps).

Just trying to keep this system alive until I can decide what to replace it with...
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back