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

pl1984

Suspended
Oct 31, 2017
2,230
2,645
Old CPUs back in the computer. Everything worked perfectly immediately. So, what are my options? How can I determine which CPUs work? Is it possible to replace the daughterboard of the 2009 with a 2010 (since the firmware is updated) and that would allow me to use CPUs with an IHS, right?
My recommendation from post #15:

If it does then I would consider installing the x5690 CPUs in pairs. Unfortunately this could result in having to do it three times (something like CPU X and Y, if that doesn't work than X and Z, and if that doesn't work than Y and Z). Unless you know someone else with a dual 4,1 to test on.

Unless you know one of the three CPUs is bad (the one you sliced some of the components on) then you'll have to get additional CPUs. Is it possible to exchange the CPUs with the seller?
 

fhturner

macrumors 6502a
Nov 7, 2007
631
413
Birmingham, AL & Atlanta, GA
I used it when I first got the computer, so I know it worked before. I can check pins later today. I didn't know to count the turns when I originally removed the heat sink so I am going with finger tightened.

No need to count the turns when using delidded CPUs— just tighten down until the screws stop. I recommend a 2-pass, criss-cross pattern, first pass using about 7-8 "twists" of the wrist, then the remaining 5-10 twists on the 2nd pass until tight.

When I'm in doubt, I install the CPU on a single board, run AHT and use it a for a day.

On a recent build for 2 clients' dual processor MP4,1s, I actually bought a single-CPU tray for testing the replacement CPUs *before* delidding them (since the single-CPU configs have IHS). They are pretty inexpensive, compared to the rest of the machine and X5690s...got one for around $70. This way I could be sure I didn't get a bad CPU, then delid it, install, then wonder if I damaged it when delidding or installing. So, in order to help your process here, you might want to think about that little extra investment to help you get it right...if you wind up needing add'l X5690s OR want to try tsialex's technique of reattaching IHS for testing.
 

thagek

macrumors newbie
Oct 22, 2020
8
0
To only do a test, yes, but since the 2009 logic board has the 1.39f5 SMC and the 2010 CPU tray has the 139f11, the fans will work at full RPM full time.
Hello, I am having a same issue on both Mac Pros. They were just fine for over 2 years without any issues. Recently, I tried to mess with open core, Radeon 580 w/metal for Mojave, and USB 3.0 pcie on one of my good running 5.1, 3.46Ghz. One night, I tried to open up logic pro and some sampling error made the screen to freezed, so I had to shut it down. And then it wouldn't boot anymore, so I pulled 3.33 tray from another mac pro and it was successfully rebooted. So again I open up logic pro and same error happened and wouldn't reboot just like 3.46 tray. So I thought somehow all CPUs were fried. Stupidly, I did same to on my other Mac Pro, result were the same, error from Logic pro they all dead. A day later, I installed 2.66 on both trays, and they all work just fine. I was very confused and want to find out what is going on. So I tried to install all of the 3.33 and 3.46 cpu individually just on CPU A slot, strangely they all boot and work as one cpu with 4 slots of RAM. When I did same test individually on CPU B slot, boot screen stuck on apple logo, and all fan spin at max speed. Now I really puzzled.
 

tsialex

Contributor
Jun 13, 2016
13,455
13,602
Hello, I am having a same issue on both Mac Pros. They were just fine for over 2 years without any issues. Recently, I tried to mess with open core, Radeon 580 w/metal for Mojave, and USB 3.0 pcie on one of my good running 5.1, 3.46Ghz. One night, I tried to open up logic pro and some sampling error made the screen to freezed, so I had to shut it down. And then it wouldn't boot anymore, so I pulled 3.33 tray from another mac pro and it was successfully rebooted. So again I open up logic pro and same error happened and wouldn't reboot just like 3.46 tray. So I thought somehow all CPUs were fried. Stupidly, I did same to on my other Mac Pro, result were the same, error from Logic pro they all dead. A day later, I installed 2.66 on both trays, and they all work just fine. I was very confused and want to find out what is going on. So I tried to install all of the 3.33 and 3.46 cpu individually just on CPU A slot, strangely they all boot and work as one cpu with 4 slots of RAM. When I did same test individually on CPU B slot, boot screen stuck on apple logo, and all fan spin at max speed. Now I really puzzled.
When I have to diagnose a dual CPU Mac Pro with similar problems, I always start installing a known working single CPU tray and test everything to be absolutely sure that the Mac Pro is working perfectly and the problems are located with just the dual CPU tray.

First thing is to remove all cards, all disks, do a 3-times consecutively clear NVRAM and boot a disk with a known working completely vanilla install of a MP5,1 supported macOS release, then run AHT/ASD. Only after all the tests are done, you look at the CPU tray.

After getting sure that you have a working Mac Pro, you have to track what is causing the CPU tray problems, some times all the weirdness is because you caused socket pin damage when you changed the CPUs. Look at the socket with strong illumination from very different angles using a magnification glass. It's extremely difficult, but not impossible, to re-align the socket pins. If it's not the socket pin damage, then you can't do anything else yourself and it's time to get a replacement tray or try to find someone that can diagnose and repair it.
 
Last edited:

thagek

macrumors newbie
Oct 22, 2020
8
0
When I have to diagnose a dual CPU Mac Pro with similar problems, I always start installing a known working single CPU tray and test everything to be absolutely sure that the Mac Pro is working perfectly and the problems are located with just the dual CPU tray.

First thing is to remove all cards, all disks, do a 3-times consecutively clear NVRAM and boot a disk with a known working completely vanilla install of a MP5,1 supported macOS release, then run AHT/ASD. Only after all the tests are done, you look at the CPU tray.

After getting sure that you have a working Mac Pro, you have to track what is causing the CPU tray problems, some times all the weirdness is because you caused socket pin damage when you changed the CPUs. Look at the socket with strong illumination from very different angles using a magnification glass. It's extremely difficult, but not impossible, to re-align the socket pins. If it's not the socket pin damage, then you can't do anything else yourself and it's time to get a replacement tray or try to find someone that can diagnose and repair it.
Thank you, I clear NVRAM 3 times with working tray the pair of 2.66, but I skipped the AHT/ASD cause I don't have one (I might have to dig around attic). It fixed the one stubborn ram slot, but still not booting when both 3.46 CPU sockets are on the tray. And again I tested CPU A still boots both 3.46 individually. Yes, I checked all the pins and they all looking good. What else could it be?
 

tsialex

Contributor
Jun 13, 2016
13,455
13,602
Thank you, I clear NVRAM 3 times with working tray the pair of 2.66, but I skipped the AHT/ASD cause I don't have one (I might have to dig around attic). It fixed the one stubborn ram slot, but still not booting when both 3.46 CPU sockets are on the tray. And again I tested CPU A still boots both 3.46 individually. Yes, I checked all the pins and they all looking good. What else could it be?
Xeon 2nd QPI link failure?
 

thagek

macrumors newbie
Oct 22, 2020
8
0
I will try it, thank you.
Tested with pair of 2.66 both trays, all passed on both MacPros. Install 3.46 none of them boot. Could that be Boot Rom version 144.0.0.0? This was the last update I did on both MacPros before this happen.
 

tsialex

Contributor
Jun 13, 2016
13,455
13,602
Tested with pair of 2.66 both trays, all passed on both MacPros. Install 3.46 none of them boot. Could that be Boot Rom version 144.0.0.0? This was the last update I did on both MacPros before this happen.
The only chance of the BootROM be causing this is if you someway damaged the BootROM during the upgrade process, corrupting the microcode area. Since it's working with the original Xeons, I doubt that is being caused by the BootROM.
 

thagek

macrumors newbie
Oct 22, 2020
8
0
The only chance of the BootROM be causing this is you someway damaged the BootROM during the upgrade process, corrupting the microcode area. Since it's working with the original Xeons, I doubt that is being caused by the BootROM.
I am really appreciated your help. Now I am thinking to get logic board on ebay and see that would turn things around. If not, definitely the trays are not upgradable, well not anymore.
 

tsialex

Contributor
Jun 13, 2016
13,455
13,602
I am really appreciated your help. Now I am thinking to get logic board on ebay and see that would turn things around. If not, definitely the trays are not upgradable, well not anymore.
You can always backup/dump the SPI flash contents with ROMTool, save it securely, then use ROMTool to flash the generic MP51.fd from 10.14.6 full installer:

Code:
Install\ macOS\ Mojave/Install\ macOS\ Mojave.app/Contents/Resources/Firmware/MP51.fd

It's enough for boot your Mac Pro, diagnose it but not for iCloud/iMessage/FaceTime login, so use it for diagnostics purposes only and after your tests, you flash the original dump back.
 

thagek

macrumors newbie
Oct 22, 2020
8
0
You can always backup/dump the SPI flash contents with ROMTool, save it securely, then use ROMTool to flash the generic MP51.fd from 10.14.6 full installer:

Code:
Install\ macOS\ Mojave/Install\ macOS\ Mojave.app/Contents/Resources/Firmware/MP51.fd

It's enough for boot your Mac Pro, diagnose it but not for iCloud/iMessage/FaceTime login, so use it for diagnostics purposes only and after your tests, you flash the original dump back.
Mojave was installed but, some of my old programs not loading, so downgrade it back to High Sirera.
 

tsialex

Contributor
Jun 13, 2016
13,455
13,602
Mojave was installed but, some of my old programs not loading, so downgrade it back to High Sirera.
I'm honestly falling to see what you downgrading to HighSierra has anything to it. If you deleted the 10.14.6 installer, just get it again from the Mac App Store, then use Pacifist to extract the generic firmware upgrade image.
 

thagek

macrumors newbie
Oct 22, 2020
8
0
Ok, You lost me there my friend. I search ROMTool and downloaded, but I don't know what does it do, or how to use it. It is asking me the password. I put my screen login password, but no luck.
 

tsialex

Contributor
Jun 13, 2016
13,455
13,602
Ok, You lost me there my friend. I search ROMTool and downloaded, but I don't know what does it do, or how to use it. It is asking me the password. I put my screen login password, but no luck.
ROMTool password is "rom", but if you don't know how to use it or completely understand the process, please don't even try.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.