MP 1,1-5,1 MacPro5,1: BootROM thread | 144.0.0.0.0

[octoviaa]

Yes. I launch the installer and it tells me to update my firmware (I'm currently on 140). Then I hit the "Shut Down" button and wait for the machine to power off. Afterwards I hold down the power button until I hear a long beep and the machine powers up again. But then it's just a black screen. Waited like 20 minutes and then forced a reboot.

Hi Eneco,
You did 'forced a reboot' which might make the firmware update failed.

Below are the sequences for me when updating the firmware:
1. Click shutdown in the firmware update dialog
2. Computer shutdown automatically (by closing all open apps)
3. Press the power-button AND KEEP PRESSING until the power light is blinking rapidly and you hear the long chime (pressing a second or two longer won't harm you, so you can try that just to be safe)
4. Computer start-up and DVD DRIVE open, AT THIS STEP THE FIRMWARE IS BEING UPDATED PLEASE WAIT PATIENTLY.
* Black screen nothing is visible (as I do not have Mac EFI metal supported GPU, I'm using RX570), just wait
5. Computer restart, DVD-ROM closed, THIS MEANS THE FIRMWARE UPDATE IS FINISHED.
6. You can logged in to your macos, check the firmware is 144 then continue with OS UPDATE.

 

[Eneco]

Hi Eneco,

You mentioned you hit the shutdown button, which is not required, which might caused the firmware update failed.
If I recall correctly, once the prompt to update firmware comes up, you just need to click 'shutdown' in the prompt dialog.

The computer will shutdown by itself (DO NOT shutdown by pressing the shutdown button), in-fact it will turn on by itself too, so what it does is a restart.

Below are the steps happened to me:
1. Click shutdown (or is it restart?) in the firmware update dialog
2. Computer shutdown automatically (by closing all open apps)
3. Computer start-up and DVD DRIVE open, AT THIS STEP THE FIRMWARE IS BEING UPDATED PLEASE WAIT PATIENTLY.
Black screen nothing is visible aside from the

Thanks for your input. I clicked the "Shut Down" prompt within the update window and did not manually power off the machine. I may have phrased that wrong and corrected my post, but I did exactly what you described. Nevertheless I'm stuck with a black screen afterwards.

 

[KevinClark]

Hello I see impossible to boot on windows since the last bootrom on Mac Pro with 10.14.5 View attachment 837081

 

[octoviaa]

Thanks for your input. I clicked the "Shut Down" prompt within the update window and did not manually power off the machine. I may have phrased that wrong and corrected my post, but I did exactly what you described. Nevertheless I'm stuck with a black screen afterwards.

Sorry I don't have a better suggestion right now other than the 'lame' one which is to wait longer (may be 1 hour)?
Or if you're using Display Port, try to unplug it as stated by tsialex in the first page of this forum (though mine (4K Monitor) work without unplug).

 

[h9826790]

Apple already put the blame on Intel about the lack of microcodes…

View attachment 836987

I wonder how can the Late 2010 cMP is affected, but not the Early 2012 cMP.

 

[octoviaa]

Hello I see impossible to boot on windows since the last bootrom on Mac Pro with 10.14.5 View attachment 837081

Mine work fine.
Windows installed in separate SSD in CSM mode.
How about open another thread and ask for help?

 

[JedNZ]

I successfully updated from 140.0.0.0.0 to 144.0.0.0.0 using the directions on the macOS 10.14.5 full installer.

My system:
macOS installed on Samsung 850 SSD sitting in an Accelsior S PCI SATA III Adapter; my User data on a Fusion Drive (Samsung 960 NVMe blade in a cheap PCI adapter, paired with a WD spinner in direct connect bay); two USB external drives connected to USB 3.0 ports (USB 3.0 PCI adapter); USB 2.0 hub with printer, USB mic, USB speakers and Magic Trackpad and Apple numeric keyboard connected to USB 2.0 rear port on cMP; and my R9 380X GPU via DP to Samsung 28” 4K monitor.

So maybe that answers any questions as to whether I could upgrade from 140.0.0.0.0 to 144.0.0.0.0 firmware and upgrade from macOS 10.14.3 to 10.14.5:
With my boot drive being an SSD in a PCI adapter; and
User data on a NVMe/Spinner in Fusion drive; and
Connected via DP to 4K monitor.

It all worked for me with all my hardware attached - I didn’t unplug or uninstall any hardware to make it work. Hope that helps anyone with a similar setup.

Update: actually I did have an issue - I was stuck on 2560x1440 resolution. Neither System Preferences > Displays or SwitchResX showed any resolutions higher than 2560x1440. I reset my NVRAM (Cmd+Opt+P+R - hold that for 3 restarts), and then also disabled SIP, then reset SMC, turned my screen off, reset DisplayPort from 1.2 to 1.1 back to 1.2, unplugged DP cable a couple of times, and a few other things and couldn't get 4K (3840x2160) to show up. Then after enabling SIP again all of a sudden 4K resolutions showed back up again. Hmmm. I also notice that 3840x2160 64Hz is no longer showing - only 60Hz. Not sure if it disappeared after upgrading to macOS 10.14.5, or at some other time before that as I haven't had to look/change anything for a while.

 

[chrfr]

I simply don't understand why I should download the full installer, that I already have, from a different source again? What's the point? Why should this one work and Apple's official version doesn't? Is this a modified version? If so, what's the difference?

There is no need to download the full installer from anywhere else in order to update your Boot ROM.

 

[bsbeamer]

MAS does not work for some people. And it appears once you’re “on the list” you’re “stuck” on the list for the small installer. This past update, the small installer I was fed did NOT include the BootROM update. Occasionally they have been included in the past but it’s not 100% every time.

Use the script, follow the instructions. It’s clearly laid out. Process did not magically change for the update. Not sure what the extra confusion is about, but seems to happen with every update. Read and follow the directions. They work.
[doublepost=1557924723][/doublepost]

I wonder how can the Late 2010 cMP is affected, but not the Early 2012 cMP.

I’m guessing this is a PR move to not include anything from 2012 on the vulnerability list. Makes it seem this is for 2010 era machines only as it stands. Those are nearly a decade old and should be upgraded - this is a good excuse to include them. Including any 2012 era machines makes this “look bad” especially since no one is running out to replace MP5,1 with an outdated 2013 6,1 model at this time.

Do wonder what support route can be taken with Apple support to either confirm this, or at least officially inquire. I’m on an official MP5,1 mid 2012 model. Have the original single CPU tray (if it’s needed to open a case). Should be an officially supported machine with exact RX580 GPU recommendation.

 

[PowerMike G5]

Hmm ... interesting. I'm using a Samsung 970 EVO, but after I hold the power button to bring up the firmware update I just get a black screen and that's it.

I'm having this exact same problem. Using the Samsung 970 EVO as well. I do have a SM951 AHCI SSD I can try later today to see if this NVME module is the problem.

 

[tsialex]

I'm having this exact same problem. Using the Samsung 970 EVO as well. I do have a SM951 AHCI SSD I can try later today to see if this NVME module is the problem.

It's not. My main disk is a 970 Pro installed in a SSD7101-A. Never had any problems flashing BootROMs and I probably flash in a week more than a normal Mac Pro user will flash in a lifetime.
[doublepost=1557930397][/doublepost]

I’m guessing this is a PR move to not include anything from 2012 on the vulnerability list. Makes it seem this is for 2010 era machines only as it stands. Those are nearly a decade old and should be upgraded - this is a good excuse to include them. Including any 2012 era machines makes this “look bad” especially since no one is running out to replace MP5,1 with an outdated 2013 6,1 model at this time.

Do wonder what support route can be taken with Apple support to either confirm this, or at least officially inquire. I’m on an official MP5,1 mid 2012 model. Have the original single CPU tray (if it’s needed to open a case). Should be an officially supported machine with exact RX580 GPU recommendation.

I don't have a mid-2012, only a backplane that can't be used for opening a a support ticket (long history), but since you have, maybe you should open a radar asking for clarification about the mid-2012 microcode support just to see what Apple answers.

 

[PowerMike G5]

It's not. My main disk is a 970 Pro installed in a SSD7101-A. Never had any problems flashing BootROMs and I probably flash in a week more than a normal Mac Pro user will flash in a lifetime.

Yeah this problem is really perplexing me. I've never had any issue with all the 1.xx firmwares. Same procedure each time.

I'm having the exact issue Eneco is having... constant black screen after the beep.

I've even tried completely wiping my SSD, reinstalling the OS, then firmware updating. Still getting the same issue.

I don't know what else to do but try other hardware I have laying around to see. Unless you have insight that I'm not thinking of.

 

[tsialex]

Yeah this problem is really perplexing me. I've never had any issue with all the 1.xx firmwares. Same procedure each time.

I'm having the exact issue Eneco is having... constant black screen after the beep.

I've even tried completely wiping my SSD, reinstalling the OS, then firmware updating. Still getting the same issue.

I don't know what else to do but try other hardware I have laying around to see. Unless you have insight that I'm not thinking of.

Did you tried with another GPU? I'm seeing a lot of people with Vega having trouble updating. Maybe it's unrelated, but it's something to test.

 

[PowerMike G5]

Did you tried with another GPU? I'm seeing a lot of people with Vega having trouble updating. Maybe it's unrelated, but it's something to test.

Unfortunately I only have a Vega FE on me at the moment.

I'll try the other SSD with all my PCIe cards removed next and report on that. But if it's the GPU, then I'll have to find another unit somehow to try.

 

[Pressure]

Unfortunately I only have a Vega FE on me at the moment.

I'll try the other SSD with all my PCIe cards removed next and report on that. But if it's the GPU, then I'll have to find another unit somehow to try.

Worked fine with PCIe SSD and VEGA FE here.

 

[trifero]

NVME-Boot-Time in my 5.1 with 10.14.4 und Kryo-Card is painfully slow (55-60 seconds). Anybody with the same configuration/problem can report if the new Firmware accelerates Boot-Time?
Thx

"Painfully" ok. Once you booted, everything gos fluid?

 

[fatespawn]

NVME-Boot-Time in my 5.1 with 10.14.4 und Kryo-Card is painfully slow (55-60 seconds). Anybody with the same configuration/problem can report if the new Firmware accelerates Boot-Time?
Thx

No real difference for me. From first chime to desktop is about 60 seconds. Isn't a function of how many PCIe cards you have installed doing a self check? I was having an issue with every 5 or 6 times cold booting resulted in a hang... we'll see if 144.x.x.x fixes that.

So, I can report that 144.x.x.x and 10.14.5 were successfully installed in my machine (from an NVMe boot drive if anyone is curious). See my sig for hardware config.

 

[crjackson2134]

I was having an issue with every 5 or 6 times cold booting resulted in a hang... we'll see if 144.x.x.x fixes that.

I’ve had the same problem for months on end. v144.0.0.0.0 fixed this completely on my cMP. If your booting issue was caused by firmware, this should fix it.

 

[tsialex]

Apple just released the first DP for 10.14.6 (18G29g):

Still 144.0.0.0.0 for MP5,1:

$IBIOSI$ MP51.88Z.F000.B00.1904121248‰
Apple ROM Version
  Model:        MP51
  EFI Version:  144.0.0.0.0
  Date:         Fri Apr 12 12:43:00 2019
  Build Type:   Release

MP6,1 still has 130.0.0.0.0:

$IBIOSI$ MP61.88Z.F000.B00.1904121119
Copyright (c) 2005-2019 Apple Inc.  All rights reserved.
Apple ROM Version
  Model:        MP61
  EFI Version:  130.0.0.0.0
  Built by:     root@saumon
  Date:         Fri Apr 12 11:19:25 PDT 2019
  Revision:     130 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, Release
  Compiler:     Apple clang version 3.0 (tags/Apple/clang-211.10.1) (based on LLVM 3.0svn)

No firmware updates whatsoever for 10.14.6 DP1 with non BridgeOS Macs.

10.14.6 DP1 EFI Version table for non BridgeOS Macs:

Mac:	EFI version:
IM13,1	285.0.0.0.0
IM14,1	137.0.0.0.0
IM14,2	137.0.0.0.0
IM14,3	137.0.0.0.0
IM14,4	197.0.0.0.0
IM15,1	228.0.0.0.0
IM16,1	227.0.0.0.0
IM16,2	227.0.0.0.0
IM17,1	166.0.0.0.0
IM18,1	172.0.0.0.0
IM18,3	172.0.0.0.0
IM19,1	220.260.170.0.0
MB10,1	175.0.0.0.0
MB8,1	181.0.0.0.0
MB9,1	181.0.0.0.0
MBA5,1	257.0.0.0.0
MBA6,1	115.0.0.0.0
MBA7,1	186.0.0.0.0
MBP10,1	255.0.0.0.0
MBP10,2	278.0.0.0.0
MBP11,1	153.0.0.0.0
MBP11,2	153.0.0.0.0
MBP11,4	192.0.0.0.0
MBP12,1	184.0.0.0.0
MBP13,1	233.0.0.0.0
MBP13,2	256.0.0.0.0
MBP13,3	256.0.0.0.0
MBP14,1	194.0.0.0.0
MBP14,2	194.0.0.0.0
MBP14,3	194.0.0.0.0
MBP9,1	226.0.0.0.0
MM6,1	278.0.0.0.0
MM7,1	242.0.0.0.0
MP5,1	144.0.0.0.0
MP6,1	130.0.0.0.0

 

[MarkC426]

I wonder how can the Late 2010 cMP is affected, but not the Early 2012 cMP.

All the ‘news’ articles I have read say all intel cpu’s back to 2011 (newer ones having fixes).
Does this mean EVERY intel cpu that has been in a macpro is affected, or just ones from 2011 onwards?

Edit
My cpu IS listed in the table (on page 1, not shown) on page 140 from tsialex.

 

[tsialex]

Edited the original 10.14.6 DP1 post with all info.

 

[MisterAndrew]

I’ve had the same problem for months on end. v144.0.0.0.0 fixed this completely on my cMP. If your booting issue was caused by firmware, this should fix it.

V144 didn’t improve my machine’s boot time. Still painfully slow.

 

[MisterAndrew]

I know what it is, but I’ll let you guys report on it.

 

[tsialex]

Edited the original 10.14.6 DP1 post with all info.

 

[MarkC426]

So.....do we really need to be worried about this vulnerability?
Will safe browsing and common sense not be key.

It’s a big pain in the butt if I have to disable ht, as I do rendering.