MP 1,1-5,1 Mac Pro 5,1 doesn't wake up from sleep after 10.14.6/firmware upgrade

[DanVez]

Hello!

I got a "new" Mac Pro 3 weeks ago. It's a mid 2010 model. (confirmed by serial number). It comes with 10.13.6 already installed. Since my goal was to upgrade it to 10.14.6, I've bought a Nvidia K5000 flashed with an original Apple OEM rom. The video cards runs fine, exactly like the version sold by Apple 10 years ago.

2 days ago, I installed the k5000, then installed Mohave on a spare partition (to keep HS just in case) . The firmware upgrade went well and Boot ROM is now at 144.0.0.0.0, SMC (system and CPU tray) are at 1.39f11. Mohave installation went also well, no issue. Then I rebooted.

The Mac ran OK, except that I have a serious issue with the sleep/wake up mode (with Mohave AND HSierra). Now it's impossible to wake up the Mac after it went to sleep. I know the necessary steps to find/isolate the source of sleep/wake up problem (Well, I always managed to solve this kind of issue a my full time job where I support Mac since many years).

The sequence of event is this one:

I suspend using Apple menu/Suspend. (But I could also let it go to sleep by itself or program it to sleep at hh:mm),
After a few seconds, fan + HD stop then the front LED light starts to pulse slowly as usual (enter sleep mode)
Then I hit the space bar or click the mouse to wake up de the Mac.
I heard a "click" the LED start to stay on permanently, but HD and fans don't start, of course no video signal.
I need to press and hold the start button until de Mac Shut down.
Then if I press the button to start it again, most of the time, nothing happen.
To make it starts, I need to hold the start button for about 10 sec, then I heard a "click (coming from the PS I or the top right of the backplane board, it seems to reset the PS), Then I press the start button again and it starts.

At first, I thought that the problem was related to the video cards(since it's a new device). So I switch back to the Radeon 4970 and 10.13.6. But it didn't solve the issue.

Then I removed pcie card, SSD and kept just 1 HD + actual ram (32G). Same issue. I also tried a GT-640 video cards since it doesn't need to be connected to the Mainboard and can run with the PCIe power only. Same issue.

I double checked all Power management parameters. Power Nap, hibernation and everything else is set correctly. Since usually this type of problem is related to SMC, I reset it (many times), reset NVRAM, PRAM and also RTC. I installed a fresh battery on the mainboard. Also check if any diagnosis led was "on" inside of the Mac. I've read the tech service manual and can't find any clue about how to solve this issue.

Since the problem now exist in High Sierra and was absent before, the only possible conclusion is that it's related to the firmware update. Or maybe to the Power Supply (but it would be a strange coincidence that it failed just after the upgrade). Also, in 2-3 occasion, when I tried to put the Mac asleep, it didn't work. The screen went blank for 1 sec and came back on. I rapidly tried a second time and then it went to sleep.

So, it seems that the SMC doesn't do it's job correctly. I also remember that at my full time job a similar issue happened. One of our Mac Pro refused to start just after we upgraded it to 10.13.6. The Mac was sent to an Apple certified repair center. It came back 2 week later with a note saying "Bad video cards". I was sceptical that the card caused this issue. Maybe they also replaced others parts, I don't know.

Since it's not possible to downgrade the firmware, I have no way to know for sure if it's related to it or not. If revert to an old firmware would solve the issue, then I would know that it's related to it.

I have a spare Mac Pro. So I can switch parts between both if needed, and I will probably try to replace the power supply this week, just to see. But to have an hardware failure just after a firmware/system upgrade would be a very strange coincidence.

I tried every trick I know to solve this issue without success. How could I check the integrity of the SMC firmware ?

Any help would be appreciated.

Thank to all!

DanVez

 

[Macschrauber]

You can back up the Firmware with RomTool (very important) and flash the mp51.fd extracted of the 10.14.6 Installer to isolate the problem to the firmware. Serial and Hardware IDs are gone but thats just a test run.

I doubt but you can try.

 

[tsialex]

SMC firmware is immutable, Apple never updated it and it's not available anywhere.

The SMC H8S micro-controller, a secure micro-controller that can not be dumped at all, was programmed back during manufacture process and is never updated again. Since no one outside Apple have the firmware code for 1.39f11 SMC, or 1.39f5 for early-2009 Mac Pros, even if it was possible to corrupt the SMC firmware, we'd never know.

Your problem is not related to the SMC firmware at all.

 

[DanVez]

Thanks for your reply!

At least I can eliminate this possibility (firmware). So it's a good news. I think that I've tried all the known software solution possible. So maybe it's hardware related. Are you're saying that there is only 2 SMC firmware version. (1.39f5 for 2009 and I.39f11 for 2010) ? So, If I need a new backplane board, then it would be a way to be sure that I got the right one by checking the SMC Rom's version, right ?

Thanks!

 

[tsialex]

Thanks for your reply!

At least I can eliminate this possibility (firmware). So it's a good news. I think that I've tried all the known software solution possible. So maybe it's hardware related. Are you're saying that there is only 2 SMC firmware version. (1.39f5 for 2009 and I.39f11 for 2010) ? So, If I need a new backplane board, then it would be a way to be sure that I got the right one by checking the SMC Rom's version, right ?

Thanks!

Yes, 99% of the time, part numbers are enough to buy it correctly. Unfortunately Apple downgraded some mid-2010/mid-2012 single CPU trays and backplanes to repair early-2009 Mac Pros back in the day.

 

[DanVez]

It's now obvious that the problem is not related to the SMC firmware. But could it be related to the Boot ROM firmware update ? I suppose that a corrupted firmware would not allow the Mac to start and run correctly, But I would be curious to know what you think about it. Assuming it's not firmware related, then it can only be related to the system or a minor hardware failure. The issue happens with 10.13.6 and 10.14 and also on another fresh installation of 10.13.6. (Nvram/pram zapped between each restart). So it's probably not related to the system config. But I will clone the disk of another MacPro running 10.11.6 and try it, juste to confirm that it's not system software related.

 

[tsialex]

It's now obvious that the problem is not related to the SMC firmware. But could it be related to the Boot ROM firmware update ? I suppose that a corrupted firmware would not allow the Mac to start and run correctly, But I would be curious to know what you think about it. Assuming it's not firmware related, then it can only be related to the system or a minor hardware failure. The issue happens with 10.13.6 and 10.14 and also on another fresh installation of 10.13.6. (Nvram/pram zapped between each restart). So it's probably not related to the system config. But I will clone the disk of another MacPro running 10.11.6 and try it, juste to confirm that it's not system software related.

It's very uncommon the BootROM to cause sleep problems, from four or five hundreds of dumps that I inspected, I've only found maybe five cases of corruption that caused sleep problems. It's very improbable, but sh_t happens.

You can always backup your BootROM, flash the 144.0.0.0.0 MP51.fd from 10.14.6 and eliminate the possibility, or dump it and I'll take a look.

Btw, it's not to just open ROMTool and dump it, you have to follow certain instructions and dump from completely vanilla macOS. If you want to, I can send instructions by PM.

 

[DanVez]

Sorry for the slow reply, no spare time for 2 days, overload of work at my full-time job.

Your help is very appreciated. I solved a lot of different issues with Mac in all those years but I've never had to dump the BootROM. I also never extracted a BootRom from a system installer disk (while I can guess how to do it). So I will need some instructions, just to be on the safe side and avoid bricking this Mac Pro.

When I discovered the wake up problem, my first idea was to reinstall the previous firmware. But my understanding is that It's not possible to downgrade firmware on a MacPro. So I thought that it should be worth reinstalling the same firmware. But to be honest I can't see how a partially corrupted firmware could allow a Mac to boot.

So, yes I would be glad if you could send me (PM) the instructions needed to reinstall and also dump the firmware. I would like to learn how to do it. Also, I didn't discuss about it first, but system installers for 10.13.6 and 10.14.6 are not easy to find these days. Can't get them from the AppleStore and the backup of these installers that I have on USB key seems to be corrupted. I was forced to download it from the DosDude website. I also did a clean install of 10.13.6 on a new partition from the recovery mode. This one is a clean installation for sure (in my book). I'm tempted to cloned the disk of my production Mac Pro still running 10.11.6 (old devices linked to this Mac) and give it a try it in this "new" Mac to see what will happen.

Thank you VERY much!

Dan

p.s. email turnaround could still be slow for the next 2 days.

 

[tsialex]

Sorry for the slow reply, no spare time for 2 days, overload of work at my full-time job.

Your help is very appreciated. I solved a lot of different issues with Mac in all those years but I've never had to dump the BootROM. I also never extracted a BootRom from a system installer disk (while I can guess how to do it). So I will need some instructions, just to be on the safe side and avoid bricking this Mac Pro.

When I discovered the wake up problem, my first idea was to reinstall the previous firmware. But my understanding is that It's not possible to downgrade firmware on a MacPro. So I thought that it should be worth reinstalling the same firmware. But to be honest I can't see how a partially corrupted firmware could allow a Mac to boot.

So, yes I would be glad if you could send me (PM) the instructions needed to reinstall and also dump the firmware. I would like to learn how to do it. Also, I didn't discuss about it first, but system installers for 10.13.6 and 10.14.6 are not easy to find these days. Can't get them from the AppleStore and the backup of these installers that I have on USB key seems to be corrupted. I was forced to download it from the DosDude website. I also did a clean install of 10.13.6 on a new partition from the recovery mode. This one is a clean installation for sure (in my book). I'm tempted to cloned the disk of my production Mac Pro still running 10.11.6 (old devices linked to this Mac) and give it a try it in this "new" Mac to see what will happen.

Thank you VERY much!

Dan

p.s. email turnaround could still be slow for the next 2 days.

PM sent.

 

[bedheaad]

Hello!

I got a "new" Mac Pro 3 weeks ago. It's a mid 2010 model. (confirmed by serial number). It comes with 10.13.6 already installed. Since my goal was to upgrade it to 10.14.6, I've bought a Nvidia K5000 flashed with an original Apple OEM rom. The video cards runs fine, exactly like the version sold by Apple 10 years ago.

2 days ago, I installed the k5000, then installed Mohave on a spare partition (to keep HS just in case) . The firmware upgrade went well and Boot ROM is now at 144.0.0.0.0, SMC (system and CPU tray) are at 1.39f11. Mohave installation went also well, no issue. Then I rebooted.

The Mac ran OK, except that I have a serious issue with the sleep/wake up mode (with Mohave AND HSierra). Now it's impossible to wake up the Mac after it went to sleep. I know the necessary steps to find/isolate the source of sleep/wake up problem (Well, I always managed to solve this kind of issue a my full time job where I support Mac since many years).

The sequence of event is this one:

I suspend using Apple menu/Suspend. (But I could also let it go to sleep by itself or program it to sleep at hh:mm),
After a few seconds, fan + HD stop then the front LED light starts to pulse slowly as usual (enter sleep mode)
Then I hit the space bar or click the mouse to wake up de the Mac.
I heard a "click" the LED start to stay on permanently, but HD and fans don't start, of course no video signal.
I need to press and hold the start button until de Mac Shut down.
Then if I press the button to start it again, most of the time, nothing happen.
To make it starts, I need to hold the start button for about 10 sec, then I heard a "click (coming from the PS I or the top right of the backplane board, it seems to reset the PS), Then I press the start button again and it starts.

At first, I thought that the problem was related to the video cards(since it's a new device). So I switch back to the Radeon 4970 and 10.13.6. But it didn't solve the issue.

Then I removed pcie card, SSD and kept just 1 HD + actual ram (32G). Same issue. I also tried a GT-640 video cards since it doesn't need to be connected to the Mainboard and can run with the PCIe power only. Same issue.

I double checked all Power management parameters. Power Nap, hibernation and everything else is set correctly. Since usually this type of problem is related to SMC, I reset it (many times), reset NVRAM, PRAM and also RTC. I installed a fresh battery on the mainboard. Also check if any diagnosis led was "on" inside of the Mac. I've read the tech service manual and can't find any clue about how to solve this issue.

Since the problem now exist in High Sierra and was absent before, the only possible conclusion is that it's related to the firmware update. Or maybe to the Power Supply (but it would be a strange coincidence that it failed just after the upgrade). Also, in 2-3 occasion, when I tried to put the Mac asleep, it didn't work. The screen went blank for 1 sec and came back on. I rapidly tried a second time and then it went to sleep.

So, it seems that the SMC doesn't do it's job correctly. I also remember that at my full time job a similar issue happened. One of our Mac Pro refused to start just after we upgraded it to 10.13.6. The Mac was sent to an Apple certified repair center. It came back 2 week later with a note saying "Bad video cards". I was sceptical that the card caused this issue. Maybe they also replaced others parts, I don't know.

Since it's not possible to downgrade the firmware, I have no way to know for sure if it's related to it or not. If revert to an old firmware would solve the issue, then I would know that it's related to it.

I have a spare Mac Pro. So I can switch parts between both if needed, and I will probably try to replace the power supply this week, just to see. But to have an hardware failure just after a firmware/system upgrade would be a very strange coincidence.

I tried every trick I know to solve this issue without success. How could I check the integrity of the SMC firmware ?

Any help would be appreciated.

Thank to all!

DanVez

I recently have had very similar issues with my Mac Pro 5,1. I am curious if the BootRom dump worked or if you were able to figure out the solution to your issues? I've checked numerous things (mostly hardware) and was mostly leaning towards a failing power supply at the moment.

Differences in my events: the not waking from sleep issue did not occur with the OS update. I ran 10.14 for a while with no issue. It just happened one day and has continued.

I ran a RAM test (Rember), which returned all OK after running for about a day or so. Curiously, after the test was done, the Mac Pro ran perfectly for about a day - waking from sleep correctly. Then returned to the no waking problem.

 

[DanVez]

Hello Bedheaad!

Yes, I solved the issue. It was a power supply failure, exactly like you've guessed. In my case, the fact that I upgraded the OS was a pure coincidence. The PS failed in the 2-3 days following the upgrade and I thought I was OS related. If you heard a click sound when you try to reactivate the Mac and nothing happen, then you have exactly he same issue. The power management circuitry in these PS and seems prone to failure.

Have a nice day!

Daniel

 

[bedheaad]

Hello Bedheaad!

Yes, I solved the issue. It was a power supply failure, exactly like you've guessed. In my case, the fact that I upgraded the OS was a pure coincidence. The PS failed in the 2-3 days following the upgrade and I thought I was OS related. If you heard a click sound when you try to reactivate the Mac and nothing happen, then you have exactly he same issue. The power management circuitry in these PS and seems prone to failure.

Have a nice day!

Daniel

Much appreciated! Yes, it has the click. Now to hunt down a decent psu.