It's very unlikely that will work with anything later than El Capitan. If I'm not mistaken, beginning with Sierra, OS X required CPUs capable of processing SSE4.x instructions. Early Mac Pros are not compatible.
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.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I got this hub:
Anker 4-Port USB 3.0 Unibody Aluminum Portable Data Hub with 2ft USB 3.0 Cable for Macbook, Mac Pro / mini, iMac, XPS, Surface Pro, Notebook PC, USB Flash Drives, Mobile HDD and More
Anker 4-Port USB 3.0 Unibody Aluminum Portable Data Hub with 2ft USB 3.0 Cable for Macbook, Mac Pro / mini, iMac, XPS, Surface Pro, Notebook PC, USB Flash Drives, Mobile HDD and More
www.amazon.com
Code:
USB2.0 Hub :
Product ID: 0x2812
Vendor ID: 0x2109 (VIA Labs, Inc.)
Version: 90.90
Speed: Up to 480 Mb/s
Manufacturer: VIA Labs, Inc.
Location ID: 0xfa200000 / 1
Current Available (mA): 500
Current Required (mA): 0
Extra Operating Current (mA): 0
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
I have a MacPro 4.1->5.1 with the latest firmware, with upgraded 8 GB graphic card, SSD, 16 GB RAM, etc.You can test yourself if it's tolerable on your workflow, for anyone that do audio related work is not. External DACs still have the problem, see the thread below for more details:
Strange Audio Issue on MP 4,1>5,1 Mojave 10.14.4
Ok, so this is my first post here since Ive been working with these machines for quite some time and Im fairly knowledgeable with these kinds of things, but this time Ive hit a brick wall so any help would be great. Recently got a Dual Quad 2.26 MP 4.1 with the intentions of maxing it on the...forums.macrumors.com
I had the audio problems first with latest 2 Mojave updates, then they disappeared for me with Catalina ( the only good thing it had from my perspective ) and came back from the first Big Sur betas. So if it worked fine in Catalina, there must be something that it was changed back in that macOS version that could be ported to Big Sur in order to make it work again. The question is "what solved the audio problems in Catalina". At least for me. I though it could be related to OpenCore as I installed macOS Catalina through that method. If that was the case ( the right audio driver ) it's not working right now ( have OpenCore 0.6.4 ).
To make the sound work almost decently I have to open Apple Logic and increase the buffer to 1024 and keep the app open consuming RAM and other resources. And it works for Apple Music but not for Youtube through Safari. For that page and other streaming services I have to use Chrome. It's quite annoying but nobody seems to know what's really going on with the audio ( yes, the CPUs, but that doesn't explain why it worked fine for me in previos macOS version ) or if they do, no one has provide a permanent solution. I asked in these forums and it was just like asking for the holy grail and even some posters seemed annoyed with the request. So will keep waiting until the day I get tired and throw this computer to garbage.
I did not check if I had a Westmere or Nehalem before I tried out OpenCore on this mac back in October. So this is a discovery by accident. There is a Catalina Security Update waiting now. I will install it this weekend.
For Catalina updates, either something changed, or we missed something in the past. Something did change with Big Sur: For the 5,1 Mac Pro, even Software Update in Catalina provides the update to Big Sur without the VMM flag. It would definitely be interesting to see if things are different with the 3,1 as well.
OK. I'm ready to try Big Sur on a spare SATA SSD. Will any precise steps be added to post #1 to upgrade or clean install the OS on cMP?
Things are iffy at the moment with Big Sur. There are problems with DRM, Night Shift and USB. Even more concerning are the obviously unwanted firmware updates that cannot be blocked as before.
While BlacklistAppleUpdate helps, it cannot block all firmware updates:
run-efi-updater flag no longer works in macOS 11, Big Sur · Issue #1255 · acidanthera/bugtracker
With macOS Big Sur, it seems that even though the NVRAM variable is set macOS will still bless the firmware update during both install and update processes: 15:835 00:005 OCB: Perform boot EFI to d...
github.com
The new RestrictEvents kext also helps:
GitHub - acidanthera/RestrictEvents
Contribute to acidanthera/RestrictEvents development by creating an account on GitHub.
github.com
But by blocking some processes, this kext prevents a clean install of Big Sur on the 5,1 Mac Pro.
Now installing Big Sur without trying to block firmware updates will likely still work, but this might happen:
OpenCore on the Mac Pro
Flash back your reconstructed dump. Most of the variables on your nvram -xp are about EFI payloads, for firmware upgrades.
forums.macrumors.com
So until things get sorted out and more testing is done, post #1 cannot include steps for installing Big Sur.
I suppose they would not have introduced the new kext if confident the quirk provided full coverage.
Ok - so I followed a guide on another site to get my Mac Pro 5.1 2010 updated to Big Sur. Eventually it installed and came online. Then I noticed that the old guide had given me an older version of opencore, so I decided to copy over the 0.6.4 version instead to my EFI. Now I seem to have a situation where there’s no output to the monitor at all. I’ve turned it off, done several 3x NVRAM resets and tried all manner of ways to try and get into recovery, but nothing is happening. Any advice? Thanks
Thinking about this, I always manually apply updates by expanding, editing the distribution file and repackaging before installing but this wasn't needed for SecUpdate 2020-006 Mojave as the distribution file did not include the usual checks. All others before that had these checks and could be that Catalina had been like that for a while.
Waiting for the new SecUpdate 2020-007 Mojave file to be posted and will check to see if it does the same.
I currently have an MP4,1->5,1 (144.0.0.0.0, 2x5675, 64GB, RX570) booting OC 0.6.3 from an NVMe EFI partition, then into Catalina 15.7 on the same NVMe drive (marked as internal). That's my primary system right now. I need to be able to boot into Big Sur for testing (I don't plan to use it regularly, unless I discover that it contains something indispensable, which seems awfully unlikely). I'm assuming that the Barry K. Nathan micropatcher will work its magic on my system just as it has for many others.
Questions:
Questions:
- For installation, I'm going to remove my NVMe (and all other drives) and do a clean install to a blank SATA SSD. After installation, I'll replace my NVMe (et al) and re-bless OC. Is that sufficient? I know OC will (should) find the bootable Big Sur on the SATA SSD, but do I need to do any OC tweaking for a Big Sur boot? Also, it seems like having OC out of the picture during install should streamline things and reduce possible errors, but is there any compelling reason to include OC in the Big Sur installation process?
- On a related note, to make Big Sur work in the above scenario, do I need to upgrade to OC 0.6.4, or will 0.6.3 suffice? (I'm firmly in the "if it ain't broke, don't fix it" camp, which includes upgrades/updates).
Interesting that you have OpenCore on the EFI partition of the NVMe drive. I thought that didn't work and was required to be on the EFI partition of a SATA drive. 🤔
Anyway, I can tell you I had no problems with Big Sur and OC 0.6.3 and I even updated to Bug Sur 11.1 with it. But now after I updated to OC 0.6.4 using @h9826790 prepared package I have the problem described here:
Activate AMD hardware acceleration
I had 0.6.3 installed and updated to Big Sur 11.1 with that. Worked fine. After that I decided to update OpenCore with the 0.6.4 package provided by you doing like in the below video (with the exception that I also ran the ”Bless OpenCore” Automator Action). Now when I reboot I don't see my...
forums.macrumors.com
Might just be me, though...
Just to make it clear, I mean connect the USB device directly to the USB 3.0 card without any hub.I got this hub:
And it appears as USB2 hub:Anker 4-Port USB 3.0 Unibody Aluminum Portable Data Hub with 2ft USB 3.0 Cable for Macbook, Mac Pro / mini, iMac, XPS, Surface Pro, Notebook PC, USB Flash Drives, Mobile HDD and More
Anker 4-Port USB 3.0 Unibody Aluminum Portable Data Hub with 2ft USB 3.0 Cable for Macbook, Mac Pro / mini, iMac, XPS, Surface Pro, Notebook PC, USB Flash Drives, Mobile HDD and Morewww.amazon.com
Code:USB2.0 Hub : Product ID: 0x2812 Vendor ID: 0x2109 (VIA Labs, Inc.) Version: 90.90 Speed: Up to 480 Mb/s Manufacturer: VIA Labs, Inc. Location ID: 0xfa200000 / 1 Current Available (mA): 500 Current Required (mA): 0 Extra Operating Current (mA): 0
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Salute to you Martin, thanks for the great effort in maintaining the special 5,1 Opencore package! It's indeed exciting to own and see an 11 year old computer can still run the latest version of MacOS. You and this community is simply amazing!
It's not the name of the thread, but the forum tag.
MP1,1/2,1 Xeon can't run macOS Sierra on-wards. Even if you could install OpenCore, running it wouldn't change the SSE4,1 minimum requirement to run macOS after El Capitan.
can any here help me with reading the info with gfxutil i have a efi flashed rx 480 in the pcie slot that my org 5770 was in. would my address be the same as the one in the guide. my cmp is a mp 5.1 single cpu 3.2ghz running mojave and the only mod is the 480 from macvidcards