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 Sequoia on the 5,1
- Thread starter flyproductions
- Start date
- Sort by reaction score
Its working ok for me OCLP 2.2.0 and Sequoia 15.3.1 Mac Pro 5,1
excepting that WhatsApp app keeps crashing, but that I think, is a WhatsApp issue.
Hi folk !
Good news about 15.3.1 on cMP 5,1.
Unfortunately, my Logitech Camera Brio 4K still doesn't work on Sequoia (connected on my USB PCI card) nor Dictation (keep crashing)
Good news about 15.3.1 on cMP 5,1.
Unfortunately, my Logitech Camera Brio 4K still doesn't work on Sequoia (connected on my USB PCI card) nor Dictation (keep crashing)
Hi all, I have a 5,1 with sequoia 15,3,1 installed on it with OCLP, the one thing I was wondering is I currently have 5770 graphics card, what card would you recommend that has metal and is supported in sequoia? TIA
You can check out what OCLP supports here
Hi ,
I would recommend you to buy an AMD Radeon RX 580 8GB, but a flashed one (on eBay) so that it will display the boot screen.
It will be more friendly at use.
It depends on your graphic needs.
i strongly recommend a saffire pulse rx 580 or 570(essentially twins) 8 gb. Comapatible on every modern macos.
There is a new version of Open Core Legacy Patcher 2.3.0. Is there anyone on Sequoia who can check is the USB webcam bug finally fixed?
I can check this on Friday when I return home. I haven't seen anything on the OCLP discord that suggests this has been fixed, so I am not optimistic.
I, too, recommend a Sapphire RX 580 graphics card. It will need a Mac compatible flashed BIOS which I found on eBay. 👍
-- update: this landed me in trouble (prohibited sign ) so I have reverted back to OCLP 2.3.1 boot. I will leave till I understand what's going on but for now OCLP updated on EFI to 2.3.2 with 15.4.1 does not boot.
-----
I have just successfully updated to 15.4.1 (OCLP 2.3.2) and OCLP wants to update my bootloader. However I had the bluetooth partial loss of function problem referred to in post 49 and 76 when I switched from DIY OpenCore to OCLP because I wanted to run Sequoia. I finally figured out the issue after struggling a lot (wish I'd seen post 76 then!) and tracked it down to the "AirportBrcmFixup.kext" which I knew was not needed having done the OC configs myself. Once that was manually edited out and kext deleted I was good to go again with BT working properly (I have an updated card).
Now OC wants to re-write the bootloader and insists on including "Adding AirportBrcmFixup.kext 2.1.9" which IMO is a bug - i.e. its not identifying my hardware properly and installing this kext this will break BT again. How can I get rid of this in OCLP Patcher? Or do I have to install it and manually reconfigure OC afterwards again. Its a bit annoying and long winded to do that and have OCLP just overwrite everything again.
I tried to report this a bug earlier but I am not a github member.
Anyone know how I configure OCLP patcher in terms of what it automatically (but wrongly) decides is needed for my hardware?
TIA
-----
I have just successfully updated to 15.4.1 (OCLP 2.3.2) and OCLP wants to update my bootloader. However I had the bluetooth partial loss of function problem referred to in post 49 and 76 when I switched from DIY OpenCore to OCLP because I wanted to run Sequoia. I finally figured out the issue after struggling a lot (wish I'd seen post 76 then!) and tracked it down to the "AirportBrcmFixup.kext" which I knew was not needed having done the OC configs myself. Once that was manually edited out and kext deleted I was good to go again with BT working properly (I have an updated card).
Now OC wants to re-write the bootloader and insists on including "Adding AirportBrcmFixup.kext 2.1.9" which IMO is a bug - i.e. its not identifying my hardware properly and installing this kext this will break BT again. How can I get rid of this in OCLP Patcher? Or do I have to install it and manually reconfigure OC afterwards again. Its a bit annoying and long winded to do that and have OCLP just overwrite everything again.
I tried to report this a bug earlier but I am not a github member.
Anyone know how I configure OCLP patcher in terms of what it automatically (but wrongly) decides is needed for my hardware?
TIA
Last edited:
Sorry, I totally lost track of this. No go with USB webcams on OCLP 2.3.0. The only type of webcam I know of to work with a 5,1 Mac Pro is an iSight--at least, when used with an Apple Cinema Display. I purchased a 27'' ACD a week or two ago and have confirmed this works in Zoom and Facetime.
My 4,1 -> 5,1 is very stable on Monterey using Martin Lo’s OCLP package, but I’m about ready to try the OCLP by itself (again) to get Sonoma or Sequoia working.
I tried it a few weeks ago, building the patcher, downloading Sequoia, and burning the OCLP install usb.
But the first try failed. Mainly my fault I think, as I thought it was hung up when it got to that “less than a minute” message, but never seemed to complete. I did a hard reboot. Then tried to reinstall several times but got an error every time.
After reading all the posts, I’m encouraged to press on. So I ’m going to try again with a fresh install using a blank SSD. And I’ll make sure to create a new OCLP install disk. Must have messed up the first one.
I tried it a few weeks ago, building the patcher, downloading Sequoia, and burning the OCLP install usb.
But the first try failed. Mainly my fault I think, as I thought it was hung up when it got to that “less than a minute” message, but never seemed to complete. I did a hard reboot. Then tried to reinstall several times but got an error every time.
After reading all the posts, I’m encouraged to press on. So I ’m going to try again with a fresh install using a blank SSD. And I’ll make sure to create a new OCLP install disk. Must have messed up the first one.
This minute can be an hour or more, as the Xeon takes forever to finish this step.
Patience is a virtue when it comes to upgrading these old machines.
I've had my patience tested.....and I'm negative.
Also, when the updates are ready from Apple or OCLP, I usually wait a week or so and try them on my Retina MacBook Pro first, but recently, every thing has worked, as it says on the can.
Sequoia 15.4 and OCLP 2.3.2
Did an experimental install of 15.4.1 on my cMP 5,1 today, using OCLP 2.32.
Have not had a chance to try much out, but at least I got it installed and booting.
I've tried twice to use Migration Assistant to move my Monterey configuration over, but it's stuck in a "boot loop".
So, will start from scratch and see how it goes.
UPDATE: The clean update from scratch seems to be the way to go. And so far, seems pretty stable. Compared to what I read about earlier versions of Sequoia running on 5,1 hardware, this seems pretty good. OCLP even has my original Mac Pro Wifi card working....I haven't upgraded that yet in this machine.
Have not had a chance to try much out, but at least I got it installed and booting.
I've tried twice to use Migration Assistant to move my Monterey configuration over, but it's stuck in a "boot loop".
So, will start from scratch and see how it goes.
UPDATE: The clean update from scratch seems to be the way to go. And so far, seems pretty stable. Compared to what I read about earlier versions of Sequoia running on 5,1 hardware, this seems pretty good. OCLP even has my original Mac Pro Wifi card working....I haven't upgraded that yet in this machine.
Last edited:
Just a data point, I have a Sapphire Pulse RX570 8GB card. Bought it used off eBay, and had to flash the VBIOS using a Windows PC to set it back to the original OEM version...which means the card I bought was probably a crypto miner card.
The card was sold to me as an RX580, but it identifies as an RX570 when queried. Runs about as good as a Pulse RX580 in all the benchmarks. Fully supported as Metal in MacOS. Worked fine when I flashed my Mac with EnableGOP, so I have the native boot screen. Only reason I mention it if you are stuck with an RX570, it will work fine in Sequoia.
Edit: this post was made before I realised the SSD I was using was the problem. Most likely the slow down was a hardware problem due to an aging SSD that I was trying.
Hate to ramble on here....but today I booted up my 5,1 and the nice clean install of 15.4.1 from yesterday was running SLOW. I kept getting the rotating "beach ball", just doing simple tasks (web browsing, text editing, etc.)
Not sure what was going on. The SSD that I had used for the test was an old one and maybe that was causing a problem.
So I swapped it out for a much newer one and started the install all over.
Is anybody else had the experience of a nice fast Seqoua install, that suddenly starts slowing down to a crawl?
I may be missing something?
Hate to ramble on here....but today I booted up my 5,1 and the nice clean install of 15.4.1 from yesterday was running SLOW. I kept getting the rotating "beach ball", just doing simple tasks (web browsing, text editing, etc.)
Not sure what was going on. The SSD that I had used for the test was an old one and maybe that was causing a problem.
So I swapped it out for a much newer one and started the install all over.
Is anybody else had the experience of a nice fast Seqoua install, that suddenly starts slowing down to a crawl?
I may be missing something?
Last edited:
My 2012 Retina MBook Pro **** itself when installing 15.4.1 OTA, but that may have been me being impatient and not letting the install screen fully provcess before I gave up.
A clean install and rebuild with OCLP 2.3.2 and 15.4.1 and it works fine now.
My Mac Pro 2009 4,1/5,1 did the OTA 15.4.1 install with OCLP 2.3.2 and post install patches no problems, all been fine so far.
A clean install and rebuild with OCLP 2.3.2 and 15.4.1 and it works fine now.
My Mac Pro 2009 4,1/5,1 did the OTA 15.4.1 install with OCLP 2.3.2 and post install patches no problems, all been fine so far.
I am still on Sonoma with my 5.1 but I plan to do the update very soon. Regarding SSD, it could be connected to the bus speed. Do you use SATA SSD in a standard tray or do you use something faster such as a NVME drive in Slot #2 ??
The newer MacOS may have a software that detects the HDD bus speeds and might slow it down when not sufficient. That would be of course Apple all over again, throwing down more stumbling blocks to force new sales.
I think it was the fact that the first SSD I tried was really old and slow. After looking up the specs on it, turns out it was a SATA 2 spec drive. Not sure where I got that drive.... Anyway, after installing on a new, but not great, SATA 3 drive (AData), all the slow downs have gone away.