MP 1,1-5,1 Possible to damage a video card with NVRAM reset?

[sablackman]

MacPro 5,1
OpenCore 0.79
Radeon RX 560 video card

Updated to MacOS 12.4 today. Had/have issues where my internal SSD’s aren’t showing. Initially just shutdown, unplugged power for 60 seconds and then restarted. Drives showed up initially after that. However, upon a second restart, no drives. Decided to do a deep NVRAM reset. Restarted, held down cmd+option+P+R until it rebooted with those keys down 3 times. From that point on, I have only one of 3 monitors showing a video signal.

Plug and unplugged monitors. Swapped around the various monitors to the inputs (Dual-DVI, HDMI, mini display). Nothing resurrected the inputs that weren’t working. Booted into my Big Sir SSD and the same issue is occurring, which leads me to believe it’s something other than Monterey 12.4.

So is it conceivable that the NVRAM reset did damage? Are there other things potentially going on here that I need to consider?

I acknowledge I may not be providing all the necessary information for a meaningful troubleshoot suggestion from the forum, so happy to provide more detail as needed.

 

[h9826790]

MacPro 5,1
OpenCore 0.79
Radeon RX 560 video card

Updated to MacOS 12.4 today. Had/have issues where my internal SSD’s aren’t showing. Initially just shutdown, unplugged power for 60 seconds and then restarted. Drives showed up initially after that. However, upon a second restart, no drives. Decided to do a deep NVRAM reset. Restarted, held down cmd+option+P+R until it rebooted with those keys down 3 times. From that point on, I have only one of 3 monitors showing a video signal.

Plug and unplugged monitors. Swapped around the various monitors to the inputs (Dual-DVI, HDMI, mini display). Nothing resurrected the inputs that weren’t working. Booted into my Big Sir SSD and the same issue is occurring, which leads me to believe it’s something other than Monterey 12.4.

So is it conceivable that the NVRAM reset did damage? Are there other things potentially going on here that I need to consider?

I acknowledge I may not be providing all the necessary information for a meaningful troubleshoot suggestion from the forum, so happy to provide more detail as needed.

Check you OC setting.

Sounds like there are multiple OC copies on different drives.

So, when you perform NVRAM reset, your cMP changed to boot from another OC copy on one of the drive. And that copy has a config that haven't enable multi monitors support yet.

 

[sablackman]

I’ll check that. 90% sure I removed any prior versions of OC on any internal drives. Been booting solely off of a thumb drive since 0.76. When booting now, I can clearly see the thumb drive actively working prior to the boot picker appearing. But - still - you’re right it’s absolutely important that I validate that.

You’re reference to enabling mult-monitor support is intriguing. I don’t recall ever doing anything to enable multi-monitors. Having multiple monitors has already just worked for me. So I will also validate whether I need to make adjustments to the config.plist to ensure multi-monitor support is enable correctly.

Thank you for your quick response!

 

[sablackman]

Verified: No other instances of OC running in any EFI partitions any on drives other than OC thin drive.

 

[h9826790]

I’ll check that. 90% sure I removed any prior versions of OC on any internal drives. Been booting solely off of a thumb drive since 0.76. When booting now, I can clearly see the thumb drive actively working prior to the boot picker appearing. But - still - you’re right it’s absolutely important that I validate that.

You’re reference to enabling mult-monitor support is intriguing. I don’t recall ever doing anything to enable multi-monitors. Having multiple monitors has already just worked for me. So I will also validate whether I need to make adjustments to the config.plist to ensure multi-monitor support is enable correctly.

Thank you for your quick response!

Check this setting

 

[sablackman]

Thanks again. Is there a unique BoardProduct that I should be using for my monitors or am I using the exact string that Martin used in the video? If unique, can you direct me on where to obtain that? I search of the forum didn't return those details based on my search for "BoardProduct"

 

[h9826790]

The idea is simple.

At the very beginning, we use the iMac Pro board ID to activate GPU HWAccel in Mojave (Mac Pro 7,1 is not supported in Mojave).

But then, in newer macOS, using iMac Pro board ID may cause some ports on the graphic card disabled (because the iMac Pro use internal monitor).

Therefore, in newer macOS, we can change that iMac Pro board ID to the Mac Pro 7,1 board ID. Whatever graphic card installed into the Mac Pro 7,1, all ports should work.

Since you said both Big Sur and Monterey has the same issue, therefore, you better check if you are using the iMac Pro board ID. If yes, change that to the Mac Pro 7,1 board ID as per the video shows.

 

[sablackman]

Sorry - been traveling - just not getting to this.
So this seemed to solve my monitor issue. To be clear, what I did was change this

<dict>
<key>ARTFrequency</key>
<integer>0</integer>
<key>BoardProduct</key>
<string>Mac-27AD2F918AE68F61</string>

and this

<dict>
<key>BIOSReleaseDate</key>
<string></string>
<key>BIOSVendor</key>
<string></string>
<key>BIOSVersion</key>
<string>9144.0.7.9.0</string>
<key>BoardAssetTag</key>
<string></string>
<key>BoardLocationInChassis</key>
<string></string>
<key>BoardManufacturer</key>
<string></string>
<key>BoardProduct</key>
<string>Mac-27AD2F918AE68F61</string>

from 7BA5B2D9E42DDD94 to 27AD2F918AE68F61

And all monitors are now functioning as expected.

Thank you!!

 

[sablackman]

So now to my next issues (and maybe I should add this to a new thread)

The monitor fix above was applied and works as expected on both my 12.4 instance and my 11.6 instance. However, in 12.4 (since I updated last week from 12.2 to 12.4) none of my drives are appearing except the boot drive.

My Monterey 12.4 boot drive is a Samsung 970 EVO 1TB. The Big Sur boot drive is on a Samsung 970 EVO Plus 2TB drive. My other drives consist of a Samsung 860 EVO 1TB drive and a mix of other spinning WD drives.

Prior to the move from 12.2 to 12.4, all drives functioned and appeared as expected. But after the 12.4 update Only the 12.4 boot drive appears. And that includes the 8GB SanDisk Cruzer thumb drive that houses OC.

So I'm puzzled as to why this other drives are not appearing in Monterey 12.4.

Are there appropriate troubleshooting steps I need to take to track down those drives issues?

EDIT:

I should also add, that when I restart into Monterey I get the "You shut down your computer because of a problem message" every time - despite the fact that shutdowns and restarts are done properly. Each shutdown or restart happens as expected with no need to force anything.