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

[tsialex]

Hi,
I tested both the delta update AND a clean install by downloading it from my second MacPro still with high Sierra (it won't let you download it if you're running Mojave) and none of them offer to install 140.0.0.0.
I even downgraded my BootRom to pre-mojave build (89.something) and the full installer brought me back to 138.0.0.0.

The full installer for 10.14.1 and the RecoveryHDMeta.pkg both have 140.0.0.0.0.

Delta updates don't upgrade or have Mac Pro 5,1 firmware, only the full installer or the Recovery update.

You have to do one of these options to install 140.0.0.0.0:

• install 10.14.1 from scratch,
• download and open Mac App Store full installer for 10.14.1 (~6GB download),
• manually install with 10.14.1 RecoveryHDMetaDmg.pkg. Instructions in this post, use the current RecoveryHDMetaDmg.pkg (~450MB download).

 

[Leborgne23]

Oh, I just checked the version of my full installer and it's still 10.14
The info page on the App Store mentioned 10.14.1 but I guess I downloaded it too early.
Will do it again and let you know.
[doublepost=1540982938][/doublepost]Well, now the App Store on 10.13.6 downloads a 15MB file called install macOS Mojave that is not the full installer.
How did you get it ?

 

[tsialex]

Oh, I just checked the version of my full installer and it's still 10.14
The info page on the App Store mentioned 10.14.1 but I guess I downloaded it too early.
Will do it again and let you know.
[doublepost=1540982938][/doublepost]Well, now the App Store on 10.13.6 downloads a 15MB file called install macOS Mojave that is not the full installer.
How did you get it ?

You can use installinstallmacos.py to download the full installer, or you can download the RecoveryHDMetaDmg.pkg.

 

[Leborgne23]

Running 140.0.0 now, the "mini full installer" took care of the EFI update. The delta installer took me to 10.14.1
thanks Tsialex.

 

[csd]

+1 for the RecoveryHDMeta method for upgrading to 140.0.0.0. As noted by others, you have to wait till you hear the long beep when powering on before releasing the power button. If you let go of the button after the flashing power light it won't take the upgrade.

I then used the installmacos.py method do download the 18B75 version of 10.14.1 to perform a fresh install onto my hitherto unbootable NVMe SSD. Seems to work perfectly so I'll be ordering a 1TB 970 EVO to replace my 500 GB SATA SSD.

/csd

 

[Leborgne23]

Tsialex, my boot time with a Samsung 970 NVME on a dual 3.33 ghz MP5.1 is about 45 seconds total.
Is that normal ? if not, what would you do to optimise it ?

 

[tsialex]

Tsialex, my boot time with a Samsung 970 NVME on a dual 3.33 ghz MP5.1 is about 45 seconds total.
Is that normal ? if not, what would you do to optimise it ?

Perfectly normal. POST on a Mac Pro checks all the RAM and all PCIe devices before booting.

 

[Leborgne23]

Ok !
Have you noticed a difference between your single CPU and your dual ? should be less things to check on the first one.

 

[tsialex]

Ok !
Have you noticed a difference between your single CPU and your dual ? should be less things to check on the first one.

RAM quantity is different, I have more PCIe cards and disks with my single one so I can't directly compare one with another.

 

[the_zee]

No go with GTX-680 with 10.14.1. We need to report this exhaustively with Apple.

Is it clean 10.14.1 install or update? I just did an update from 10.14.0 to 10.14.1 this morning with flashed GTX 680 with no issues.

 

[tsialex]

Is it clean 10.14.1 install or update? I just did an update from 10.14.0 to 10.14.1 this morning with flashed GTX 680 with no issues.

Clean install via USB, createinstallmedia usb-key.

 

[Leborgne23]

RAM quantity is different, I have more PCIe cards and disks with my single one so I can't directly compare one with another.

Ok thanks !

 

[PianoPro]

Lots of strangeness tonight.

Problem 1 -

The firmware update did not quite work as described by Apple. In my case (and there are other reports) it was not enough to hold the power button until the LED flashes per the Apple instructions. I did that first, and the firmware was not updated and the system booted back to Mojave with no update of any kind.

I then repeated the process but held the power button until the long beep, which comes after the LED flashes, and that worked to both update the Firmware to 140 and update my 10.14.1 Beta to the released 10.14.1 version.

Problem 2 -

But a Binwalk of the 140 Boot ROM now showed 2 XML files that hadn't been there with the 138 firmware.

Your xml files are for documenting purposes after upgrade and they will disappear later just like they did on mine. ...

And indeed they did disappear. I'm not sure exactly when but apparently after a couple of reboots. They are gone now and the BootROM appears completely normal.

Problem 3 -

But before I did the PRAM reset I also couldn't boot back into Windows using a Bless tool script, or the Startup Disk Preference Pane. After the PRAM reset both of those functions worked normally again to boot into Windows.

Problem 4 -

However, the Win 10 BootCamp control panel no longer works at all after the 140 firmware update, and there is a Win 10 bluetooth driver problem. I tried reinstalling the bootcamp drivers but that only fixed the problem until I booted back into Win 10 a 2nd time. I'm going to delete the drivers and reinstall next.

EDIT + Deleting and reinstalling BootCamp 6 drivers fixed the Win 10 problems but I did have to re-enter the Bluetooth Link Keys for my Magic Mouse.

Well 7 AM here, not bad for a wasted night of work.

 

[crjackson2134]

Lots of strangeness tonight.

Problem 1 -

The firmware update did not quite work as described by Apple. In my case (and there are other reports) it was not enough to hold the power button until the LED flashes per the Apple instructions. I did that first, and the firmware was not updated and the system booted back to Mojave with no update of any kind.

I then repeated the process but held the power button until the long beep, which comes after the LED flashes, and that worked to both update the Firmware to 140 and update my 10.14.1 Beta to the released 10.14.1 version.

Problem 2 -

But a Binwalk of the 140 Boot ROM now showed 2 XML files that hadn't been there with the 138 firmware.

View attachment 799879



And indeed they did disappear. I'm not sure exactly when but apparently after a couple of reboots. They are gone now and the BootROM appears completely normal.

View attachment 799872

Problem 3 -

But before I did the PRAM reset I also couldn't boot back into Windows using a Bless tool script, or the Startup Disk Preference Pane. After the PRAM reset both of those functions worked normally again to boot into Windows.

Problem 4 -

However, the Win 10 BootCamp control panel no longer works at all after the 140 firmware update, and there is a Win 10 bluetooth driver problem. I tried reinstalling the bootcamp drivers but that only fixed the problem until I booted back into Win 10 a 2nd time. I'm going to delete the drivers and reinstall next.

I've flashed my firmware (different versions testing) roughly 30 times now. I have found that the most reliable way for a first flash success is to do an NVRAM/SMC reset immediately prior to starting the process. Then the Apple recommend method works nearly every time. I had MANY instances that were similar to yours, and after I started doing the resets, the problem vanished. YMMV

 

[bsbeamer]

Problem 1 -

The firmware update did not quite work as described by Apple. In my case (and there are other reports) it was not enough to hold the power button until the LED flashes per the Apple instructions. I did that first, and the firmware was not updated and the system booted back to Mojave with no update of any kind.

I then repeated the process but held the power button until the long beep, which comes after the LED flashes, and that worked to both update the Firmware to 140 and update my 10.14.1 Beta to the released 10.14.1 version.

I've held the power button until the beep/chime on every firmware update on this 5,1. Right or wrong on my part, this has been successful for every firmware update that I've been prompted for. Some people say they do not hear the beep. This 140 firmware update took longer to beep after light blink than many previous, but I still waited (anxiously).

Vaguely remember doing the same for G5 and either 1,1 or 1,2 back in the day. One of those was stuffed in a sound isolation case and could not rely on seeing a light, so always waited for the beep/chime.

 

[pablito1972]

Clean install via USB createinstallmedia usb-key.

i just tried updating my cMP 4.1->5.1 with GTX680 an

Is it clean 10.14.1 install or update? I just did an update from 10.14.0 to 10.14.1 this morning with flashed GTX 680 with no issues.

Hi,
this doesn't work for me. Neither clean install of 10.14.1, nor with the RecoveryHDMetaDmg.pkg. Always get the message that a Metal capable GPU is needed. Full installation of 10.14 worked as it came out. Hope Apple does correct it shortly.

regards

 

[Earl Urley]

Not to sound super ridiculous, but I find that if I hold the power button and let go three seconds after hearing the beep, I don't have issues. I just updated a 4,1 flashed to 5,1 with a Mac Edition EVGA 680GTX and the App Store 10.4.1 6 GB installer this way.

 

[chris_140187]

I cannot update my boot rom to 140.0.0.0 as both the full 10.14.1 installer and RecoveryHDMeta.pkg refuse to install on my 4,1->5,1 complaining about no metal card found and FileVault on. I have the sapphire pulse rx580 and FileVault is 100% off. I suspect there might be a bug with those packages as my cMP updated to 10.14.1 just fine using System Preferences -> Software update, without the boot rom update that is

I've got the same problem...5,1 (2012) Sixcore with Vega 64...Do you have a solution?

 

[AliGT83]

I fl

I've got the same problem...5,1 (2012) Sixcore with Vega 64...Do you have a solution?

i flashed the boot rom manually using rom tool and @tsialex help

 

[the_zee]

Clean install via USB, createinstallmedia usb-key.

Yep, just tried that as well and its NO GO. Although, update from High Sierra through App Store to 10.14.1 went with no problems... I do remember having similar issues with a 7950 card when the Mojave just came out, the createinstallmedia I created in the day release refused to install with 7950, and a few weeks later I created the media again and everything suddenly started working.

 

[tsialex]

Not to sound super ridiculous, but I find that if I hold the power button and let go three seconds after hearing the beep, I don't have issues. I just updated a 4,1 flashed to 5,1 with a Mac Edition EVGA 680GTX and the App Store 10.4.1 6 GB installer this way.

I usually go 5 seconds after the power led stops blinking, usually is the same moment that shows the white screen on my monitor.

 

[itadampf]

tnxs to @tsialex there are now three more Mac Pro 4,1 that are reborn as 5,1

 

[bugout]

Anything new in the new beta?

 

[Leborgne23]

Hi Tsialex,
Do you have any idea why installmacos.py fails to create the disk image after being done downloading ?
Here's the error message

Command '['/usr/sbin/installer', '-pkg', './content/downloads/35/53/091-93471/ff5kp0aiow1d87t494xp5twbugymnlvz16/091-93471.English.dist', '-target', '/private/tmp/dmg.lP3myO']' returned non-zero exit status 1
Product installation failed.

 

[tsialex]

Hi Tsialex,
Do you have any idea why installmacos.py fails to create the disk image after being done downloading ?
Here's the error message

Command '['/usr/sbin/installer', '-pkg', './content/downloads/35/53/091-93471/ff5kp0aiow1d87t494xp5twbugymnlvz16/091-93471.English.dist', '-target', '/private/tmp/dmg.lP3myO']' returned non-zero exit status 1
Product installation failed.

Usually incomplete downloads, you have to remove the contents directory.
[doublepost=1541008268][/doublepost]

Anything new in the new beta?

CDN that I'm connected is lazy as hell, nothing on the SUCatalog yet.