MP 1,1-5,1 Activate AMD hardware acceleration

[Chung123]

Awesome! I'll give it a try...

Update: Disregard, ever since the last update, Mac OS 11 doesn't really like my eSATA hard drive dock.

(Doesn't like, as after dismounting a drive from the dock, the drive is gone from desktop, but if I then power off the dock, I get a complaint about the disk not properly ejected. This didn't happen in previous updates.)

I had left the dock powered on, but with no hard drive in the dock, and the booting hung. Once I powered off the dock, rebooting was consistent. So with this latest update, I must remember to keep the eSATA hard drive dock powered off during booting.

Spoke to soon. Did a normal restart and had some issue booting back. However, after a full shutdown and a couple pram zaps. Monitor on and off and it finally booted.
Probably should have made sure to redesignate the startup disk? This sort of happened last time.

Happy, as everything works as it should on 11.4.

 

[Stex]

NVMe configurations do not support anything past macOS 11.2.3. It appears Apple changed the boot process.
If you can, get an installer for 11.2.3 and try that. Do not update beyond this until the issue is fixed.
If necessary, create a USB installer.

For those of you who need the MacOS 11.2.3 Installer, you can find in the link pasted below. And yes, as @haralds stated, good idea to create a USB installer for future troubleshooting etc.

Install mac OS 11.2.3 20D91 : Free Download, Borrow, and Streaming : Internet Archive

macOS 11.2.3 Installer

archive.org

 

[h9826790]

Thank you so kindly folks. Yeah I used a OWC Accelsior PCI partitioned in half. Mt. Lion & Mojave. May be I should just clean install Mojave then open core. Once that is accomplished then I can add a SSD Mt. Lion ?
Can you steer me back to the correct install for Mojave with OC install. Thank you all immensely. View attachment 1780961

You need to disable SIP to run that Bless tool properly.

 

[mhartel]

Strange things happen... One of my two 5,1 did perfectly fine with the system preferences update (3GB download or so) & the whole thing took maybe 15 minutes. No issues.

The other machine kept canceling out of the update & I ended up manually getting the whole 12GB full install and the update took around an hour and required multiple reboots. Both machines are running 11.4 perfectly OK now.

 

[Stex]

Strange things happen... One of my two 5,1 did perfectly fine with the system preferences update (3GB download or so) & the whole thing took maybe 15 minutes. No issues.

The other machine kept canceling out of the update & I ended up manually getting the whole 12GB full install and the update took around an hour and required multiple reboots. Both machines are running 11.4 perfectly OK now.

Please, if you have 5min, head over to the thread pasted below and post your upgrade experience and exact cMP setups, particularly where you have boot drives installed etc. It will help us better understand success cases, there are very few so far. More data the better.

Mac OS 11.3 has broken support for older Mac Pros

macOS Big Sur 11.3 Beta 3 has broken Mac Pro's early-2009 to mid-2012 ability to boot reliably into macOS. It's still possible to boot 11.3/11.4, but the process requires multiple restarts and a connection has been made between PCIe devices, especially storage related devices and USB controller...

forums.macrumors.com

 

[basslik]

You need to disable SIP to run that Bless tool properly.

Indeed I did. I want to start from scratch. Is it possible to do a clean install of Mojave then install OC ?. Or do I have install El Capitan first ?. I already have firmware 144.

 

[h9826790]

Indeed I did. I want to start from scratch. Is it possible to do a clean install of Mojave then install OC ?. Or do I have install El Capitan first ?. I already have firmware 144.

Since I don't know the exact situation of you cMP, please do the following.

1) make a Mojave USB installer

2) Shutdown, and remove all hard drives except the target drive for installing Mojave

3) boot to the Mojave installer

4) format the target drive and install a Mojave

5) After installation completed, shutdown, remove the USB installer

6) 3x NVRAM reset

7) boot to recovery partition, disable SIP

8) boot to Mojave, install OC as per post #1314

 

[basslik]

Since I don't know the exact situation of you cMP, please do the following.

1) make a Mojave USB installer

2) Shutdown, and remove all hard drives except the target drive for installing Mojave

3) boot to the Mojave installer

4) format the target drive and install a Mojave

5) After installation completed, shutdown, remove the USB installer

6) 3x NVRAM reset

7) boot to recovery partition, disable SIP

8) boot to Mojave, install OC as per post #1314

Thank you very much. I take it the format has to be APFS for the Mojave ?

 

[h9826790]

Thank you very much. I take it the format has to be APFS for the Mojave ?

HFS+ also work, the installer will convert it to APFS anyway.

 

[basslik]

Here's what strange. I did a clean install of Mojave and now all of a sudden the OS is offering to update to 11.4BS.

Before with Mojave installed I clicked update and it only said no updates available. Then when I installed OC 0.6.9 it found an update.

I currently haven't installed OC but it's now showing an update?.

I see success with 11.4. Should I give it a try to update to that then install OC 0.6.9 ?

 

[tsialex]

Here's what strange. I did a clean install of Mojave and now all of a sudden the OS is offering to update to 11.4BS.

Before with Mojave installed I clicked update and it only said no updates available. Then when I installed OC 0.6.9 it found an update.

I currently haven't installed OC but it's now showing an update?.

I see success with 11.4. Should I give it a try to update to that then install OC 0.6.9 ?

Since @h9826790 AMD hardware acceleration needs spoofing to work, Software Updates then think that you have a supported Mac and offer you to update to BigSur.

BigSur past 11.2.3 is not reliably with a MP5,1 and the frequent crashes at boot can led to disk corruption or even to a brick if your NVRAM is near full/garbage collection not working - several people didn't took the warn from the first post of the thread below seriously and now have to desolder the SPI flash or buy a MATT card and pay for a firmware reconstruction to get the backplane working again.

Mac OS 11.3 has broken support for older Mac Pros

macOS Big Sur 11.3 Beta 3 has broken Mac Pro's early-2009 to mid-2012 ability to boot reliably into macOS. It's still possible to boot 11.3/11.4, but the process requires multiple restarts and a connection has been made between PCIe devices, especially storage related devices and USB controller...

forums.macrumors.com

 

[basslik]

I am wondering if that installation failure is really GPU related.


I don't think ML support 128GB RAM, you may make it 64GB and try again.

Anyway, did you install ML on a SATA connected drive?

Martin I followed instructions, and your 0.6.9 installed great. I have video acceleration now.

My concern ( two things). I was able to grab BS 11.2.3 from Jesse's flying depository and after install I had a relocated items folder popup. I found this in the folder. I absolutely freaked out. Is this a virus >

I only use my Mac for Pro Tools and nothing else and how this got there I suspect in the BS download. Should I remove and find another reliable BS 11.2.3 ?

I also noticed the system firmware has changed from 1.44 to 9144.0.6.9 is that normal ?

I also noticed instantly app are sluggish opening up ?

 

[h9826790]

My concern ( two things). I was able to grab BS 11.2.3 from Jesse's flying depository and after install I had a relocated items folder popup. I found this in the folder. I absolutely freaked out. Is this a virus >

Can't read the full file name. Is that just a plist file?

I also noticed the system firmware has changed from 1.44 to 9144.0.6.9 is that normal ?

It's covered in the readme file

 

[Stex]

after install I had a relocated items folder popup. I found this in the folder. I absolutely freaked out. Is this a virus >

The following is what I got in a readme file within the "Relocated Items" folder specifically referencing the group.system_default file. Not sure if you ended up with a different readme addressing the -- YES -- strange file you ended up with in there.

"During the last macOS upgrade or file migration, some of your files couldn’t be moved to their new locations. This folder contains these files.

Configuration files

These configuration files were modified or customized by you, by another user, or by an app. The modifications may be incompatible with the recent macOS upgrade. The modified files are in the Configuration folder, organized in subfolders named for their original locations.

To restore any of the custom configurations, compare your modifications with the configuration changes made during the macOS upgrade and combine them when possible.

Configuration files with the suffix "system_default" were edited or customized, but the changes were allowed to remain installed. The system_default version of the file is provided to demonstrate what the Apple supplied version of this file would look like. It is recommended that you compare the two and evaluate whether you wish to integrate any changes Apple may have made to the default version."

Did you have a readme file from Apple with something along the lines of the above?

 

[basslik]

Thanks folks. I read a lot of stuff and might have overlooked.

It was only one file in the relocation (com.apple.CoreGraphics.p...NPORN)

I flipped out when I saw the file. I wonder how that file got on my computer. My Mac is strictly used for audio and I was shocked that file popped up.

Anyhow I installed OC 0.6.9 and did it how I saw it being described changing the script (C), and the true to false. disabled SIP as well. When I rebooted I didn't get the graphics acceleration.

When I redid it according to Martin with just moving the folders to the EFI without changing the script as shown on his video the video acceleration worked >?

I started over with a clean install of Mojave and I'll do Martin's video version since that seemed to do trick.

Also can to direct me to the readme file regarding the BootRom number change, thank you all so much.

 

[kittonian]

Hi all. I've got a cMP upgraded with dual X5690 processors and the Pixlas mod, running Big Sur 11.2.2 with a Sapphire RX 5700XT (8GB) using Martin Lo's OC 0.6.9.

With previous versions of OC and Big Sur I wasn't having many issues but now I am getting kernel panics (read: black screen out of nowhere, full system shutdown/restart) whenever I am using graphics intensive applications like Cinema 4D R23 or ArchiCAD 24. It doesn't happen too often in ArchiCAD (once in a great while) but constantly with C4D. Draw a spline? Kernel panic. Reboot and draw the same spline? No problem. Do something else? Kernel panic. Rinse, repeat.

ArchiCAD is pretty stable most of the time but C4D kernel panics out of the blue constantly making it unusable. It's not a repetitive situation either, meaning I can be doing a task, get a kernel panic, restart, and then do the exact same task with no issue.

As cMP's cannot be updated beyond 11.2.3 at the moment and the combo installer is no longer available to update 11.2.2 to 11.2.3 (nor do I believe there is anything graphics related in that update) I am pretty stuck. I am a 3D designer and literally cannot work in C4D anymore. If anyone can help I would sure appreciate it.

 

[tsialex]

Hi all. I've got a cMP upgraded with dual X5690 processors and the Pixlas mod, running Big Sur 11.2.2 with a Sapphire RX 5700XT (8GB) using Martin Lo's OC 0.6.9.

With previous versions of OC and Big Sur I wasn't having many issues but now I am getting kernel panics (read: black screen out of nowhere, full system shutdown/restart) whenever I am using graphics intensive applications like Cinema 4D R23 or ArchiCAD 24. It doesn't happen too often in ArchiCAD (once in a great while) but constantly with C4D. Draw a spline? Kernel panic. Reboot and draw the same spline? No problem. Do something else? Kernel panic. Rinse, repeat.

ArchiCAD is pretty stable most of the time but C4D kernel panics out of the blue constantly making it unusable. It's not a repetitive situation either, meaning I can be doing a task, get a kernel panic, restart, and then do the exact same task with no issue.

As cMP's cannot be updated beyond 11.2.3 at the moment and the combo installer is no longer available to update 11.2.2 to 11.2.3 (nor do I believe there is anything graphics related in that update) I am pretty stuck. I am a 3D designer and literally cannot work in C4D anymore. If anyone can help I would sure appreciate it.

Downgrade to Catalina is your answer. Also a clean install of 11.2.3, you still can download it, but you will be vulnerable to the security exploits.

 

[kittonian]

Downgrade to Catalina is your answer. Also a clean install of 11.2.3, you still can download it, but you will be vulnerable to the security exploits.

Downgrade to Catalina is not an answer. Octane X requires Big Sur and that is the render engine I use. As I said, previous Big Sur and OC versions didn't seem to have this issue, but honestly I don't know for sure which ones specifically. A clean install doesn't resolve the issue either. The OpenGL and Watchdog errors that cause kernel panics when running an RX 5700XT with an Ultrawide 4k display are well documented, but seem to be related specifically to OC running on the later Big Sur revisions.

 

[tsialex]

Downgrade to Catalina is not an answer. Octane X requires Big Sur and that is the render engine I use. As I said, previous Big Sur and OC versions didn't seem to have this issue, but honestly I don't know for sure which ones specifically. A clean install doesn't resolve the issue either. The OpenGL and Watchdog errors that cause kernel panics when running an RX 5700XT with an Ultrawide 4k display are well documented, but seem to be related specifically to OC running on the later Big Sur revisions.

So, you are in dire straits. If you need Octane X, 11.2.3 and it's drivers problems is the end of the road for you at this moment. Maybe it's time to start to think on building a hackintosh or upgrading to a 2019 Mac Pro.

Big Sur after 11.3 is not reliably with MacPro5,1 and after 3 months with a lot of eyes looking we still don't have a hint of what is the real cause of the crashes, just hunches here and there.

 

[kittonian]

So, you are in dire straits. If you need Octane X, 11.2.3 and it's drivers problems is the end of the road for you at this moment. Maybe it's time to start to think on building a hackintosh or upgrading to a 2019 Mac Pro.

Big Sur after 11.3 is not reliably with MacPro5,1 and after 3 months with a lot of eyes looking we still don't have a hint of what is the real cause of the crashes, just hunches here and there.

I am looking for advise regarding what may have changed in OC and what I might be able to modify to rectify this situation. I am not looking to build a hackintosh or pay $10k+ for a 2019 MP that is already obsolete.

We do have a pretty big hint as to what the issue is. It has to do with a race condition embedded in the 11.3+ code that may or may not have been intentional by apple's engineers. That is what is causing the hard drive corruption, especially with NVMe based machines. Lots of eyes are indeed looking at possible solutions to the problem and I expect we will have something within the next month or two.

 

[tsialex]

I am looking for advise regarding what may have changed in OC and what I might be able to modify to rectify this situation. I am not looking to build a hackintosh or pay $10k+ for a 2019 MP that is already obsolete.

We do have a pretty big hint as to what the issue is. It has to do with a race condition embedded in the 11.3+ code that may or may not have been intentional by apple's engineers. That is what is causing the hard drive corruption, especially with NVMe based machines. Lots of eyes are indeed looking at possible solutions to the problem and I expect we will have something within the next month or two.

Look, we have been reading source and disassembling code for 3 months trying to find a reason for the crashes, this is not near and no we don't have a hint, just hunches that a quirk removed somewhere is causing a race condition. NVMe has noting to do with the issue, it's a consequence.

Open a GitHub issue directly on acidanthera bug tracker. Here is not the correct place for it.

 

[kittonian]

Look, we have been reading source and disassembling code for 3 months trying to find a reason for the crashes, this is not near and no we don't have a hint, just hunches that a quirk removed somewhere is causing a race condition. NVMe has noting to do with the issue, it's a consequence.

Open a GitHub issue directly on acidanthera bug tracker. Here is not the correct place for it.

Pretty sure that here is exactly the place to ask this question and I'm not sure why you feel the need to be so hostile. This is a thread directly related to AMD GPUs and OC running mostly on legacy cMP machines. I get that you don't have anything to offer in regards to my issue, but perhaps someone else might.

 

[tsialex]

Pretty sure that here is exactly the place to ask this question and I'm not sure why you feel the need to be so hostile. This is a thread directly related to AMD GPUs and OC running mostly on legacy cMP machines. I get that you don't have anything to offer in regards to my issue, but perhaps someone else might.

I'm not being hostile, I'm presenting the facts. Anyway, maybe you are lucky and someone that also have a similar problem will find your report here and open a issue.

 

[basslik]

I'm not being hostile, I'm presenting the facts. Anyway, maybe you are lucky and someone that also have a similar problem will find your report here and open a issue.

OH boy. You spent your entire valuable time helping Alex. Great point as well Alex, maybe someone might be able to chime in with a similar problem. Might try googling as well. For some weird problem with my Mac I actually found cool stuff that wasn't manifesting here too.

Hey Alex I'm up and running great now on OC 0.6.9, Martin video made it easy.

I have a question: When I purchased my Sapphire RX580 that wasn't Mac'ed out. But when I installed High Sierra and Mojave I did get the boot screen?

 

[tsialex]

When I purchased my Sapphire RX580 that wasn't Mac'ed out. But when I installed High Sierra and Mojave I did get the boot screen?

Nope. OpenCore can provide it if your GPU firmware correctly supports GOP. If it's a mining GPU or a card that was modified in the past with gaming firmware, even if the card is one of the supported, won't work.