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

[tsialex]

Maybe we can't get to the bottom of the SecureBoot multiple certificates question immediately, but I think that we can get there.

I have a spreadsheet that I have being inputing data since the start, initially just to control what I was doing, later to find descriptor relation with build dates. From now on I'll start to include IASInstallPhaseList and SecureBoot certificates present.

These are what I'll input from now on:

BIOS:
Override version:
SSN:
HWC:
SON:
LBSN:
BD:
Build Date:
Model:
Apple Refurbished:
Original Backplane:
IASInstallPhaseList:
SecureBoot:
Date of inspection:

Most of these can be parsed, some not. I'll recheck every previous BootROM dump with time, more than 80 Mac Pros now.

 

[Squuiid]

more than 80 Mac Pros now.

 

[waimtrp]

Not sure if this card will work with PCIe 2.0, someone will need to bite the bullet.

Anandtech has a article about the PCIe switch used by this card https://www.anandtech.com/show/13022/asmedia-preps-asm2824-pcie-30-switch

i can confirmed it work with cMP 4,1/5,1 , i order one and it arrived today , tested it with my 4,1>5,1 , installed to the x16 lane slot , show running at x4 8GT/s , i only have SM951 to test, and even with only one SSD installed, the speed is faster then the x4 adapter i used before , tested with RAID 0 SM951, speed is close to the 7101A , very happy now .
[doublepost=1539780329][/doublepost]

Found this - http://www.sybausa.com/index.php?route=product/product&path=64_188_148&product_id=992

Retailing for $214 on NewEgg

2 slots with half the lanes as the HighPoint/PLX PEX8747 .. not sure if it is supported by the mac pro so someone needs to order and test it.

View attachment 793369
View attachment 793370

Edit: Adding more links

https://www.reddit.com/r/hardware/comments/9ga7lj/first_available_dual_nvme_m2_pcie_adapter_with/

confirmed this card work

 

[tsialex]

i can confirmed it work with cMP 4,1/5,1 , i order one and it arrived today , tested it with my 4,1>5,1 , installed to the x16 lane slot , show running at x4 8GT/s , i only have SM951 to test, and even with only one SSD installed, the speed is faster then the x4 adapter i used before , tested with RAID 0 SM951, speed is close to the 7101A , very happy now .
[doublepost=1539780329][/doublepost]
confirmed this card work

Seems working since you got more than one blade working, thanks for that. How much throughput you got from just one blade? How about fan noise?

Seems a card much more reasonable to buy.

 

[waimtrp]

Seems working since you got more than one blade working, thanks for that. How much throughput you got from just one blade? How about fan noise?

Seems a card much more reasonable to buy.

sorry to attach the screen shot for one blade , fan noise is acceptable

 

[tsialex]

sorry to attach the screen shot for one blade , fan noise is acceptable

Seems you got all the SM951-AHCI throughput from one blade, nice! Thanks again for buying the card and testing it.

 

[phoenix.factory]

Hi,

just in case this would help in any way, here is the binwalk output of my 2009 5.1 cMP. Bootrom available if wanted.
As far as i understand, it seams clean. Successful upgrade to 140.0.0.0.0 a couple of days ago alreday.

DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 UEFI PI firmware volume
16524 0x408C UEFI PI firmware volume
24972 0x618C CRC32 polynomial table, little endian
35787 0x8BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
49948 0xC31C UEFI PI firmware volume
524288 0x80000 UEFI PI firmware volume
540812 0x8408C UEFI PI firmware volume
549260 0x8618C CRC32 polynomial table, little endian
560075 0x88BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
574236 0x8C31C UEFI PI firmware volume
1048576 0x100000 UEFI PI firmware volume
1114112 0x110000 UEFI PI firmware volume
1343511 0x148017 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume

 

[Spacedust]

Where to get Romtool to check the Bootrom?

 

[vgoutis]

Where to get Romtool to check the Bootrom?

See previous post #1783

 

[Spacedust]

Thanks. I got it ;-) Now I will try to dump my rom and run binwalk on it.

 

[Pval]

Offtopic, moved to 'Blade SSDs - NVMe & AHCI'

 

[waimtrp]

Seems you got all the SM951-AHCI throughput from one blade, nice! Thanks again for buying the card and testing it.

Yes, SM951 AHCI model , i don't have NVMe blade to test, but NVMe should be more faster ?

 

[tsialex]

i can confirmed it work with cMP 4,1/5,1 , i order one and it arrived today , tested it with my 4,1>5,1 , installed to the x16 lane slot , show running at x4 8GT/s , i only have SM951 to test, and even with only one SSD installed, the speed is faster then the x4 adapter i used before , tested with RAID 0 SM951, speed is close to the 7101A , very happy now .
[doublepost=1539780329][/doublepost]
confirmed this card work

Could you please PM me the SystemReport/SPX of your Mac with the Syba card? I want to check more info about it. I'll PM you. Thx!
[doublepost=1539788285][/doublepost]

Yes, SM951 AHCI model , i don't have NVMe blade to test, but NVMe should be more faster ?

A HighPoint SSD7101A with one 970PRO 512GB gets around 3200MB/s.

 

[Spacedust]

tsialex I'm sending you PM with my dump

 

[tsialex]

10.14.1DP4 is out in the wild.

Let's check for new BootROM updates, maybe MP6,1 get a new one this week

[doublepost=1539797834][/doublepost]MP5,1 didn't had updates, same from DP3:

$IBIOSI$ MP51.88Z.F000.B00.1809191555
Apple ROM Version
  Model:        MP51
  EFI Version:  140.0.0.0.0
  Date:         Wed Sep 19 15:49:52 2018
  Build Type:   Release

[doublepost=1539797870][/doublepost]Pacifist got a update

 

[OneyedK]

I've got a cMP 4,1>5,1

Built date: 090521090521

Base_18 Descriptor

Binwalk of my 138 rom shows only one xml entry:
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 UEFI PI firmware volume
16524 0x408C UEFI PI firmware volume
24972 0x618C CRC32 polynomial table, little endian
35787 0x8BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
49948 0xC31C UEFI PI firmware volume
524288 0x80000 UEFI PI firmware volume
540812 0x8408C UEFI PI firmware volume
549260 0x8618C CRC32 polynomial table, little endian
560075 0x88BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
574236 0x8C31C UEFI PI firmware volume
1048576 0x100000 UEFI PI firmware volume
1114112 0x110000 UEFI PI firmware volume
1209297 0x1273D1 XML document, version: "1.0"
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume

Should I worry or be happy?

 

[tsialex]

I've got a cMP 4,1>5,1

Built date: 090521090521

Base_18 Descriptor

Binwalk of my 138 rom shows only one xml entry:
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 UEFI PI firmware volume
16524 0x408C UEFI PI firmware volume
24972 0x618C CRC32 polynomial table, little endian
35787 0x8BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
49948 0xC31C UEFI PI firmware volume
524288 0x80000 UEFI PI firmware volume
540812 0x8408C UEFI PI firmware volume
549260 0x8618C CRC32 polynomial table, little endian
560075 0x88BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
574236 0x8C31C UEFI PI firmware volume
1048576 0x100000 UEFI PI firmware volume
1114112 0x110000 UEFI PI firmware volume
1209297 0x1273D1 XML document, version: "1.0"
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume

Should I worry or be happy?

You have the infamous IASInstallPhaseList.plist on your NVRAM volume (XML document, version: "1.0"), probably caused by a unsuccessful macOS install.

You can have incorrect HardwareIDs and checksums, this ones need to be checked with a BootROM dump inspection.

Descriptor Base_18 is the second oldest one, lots of updates with ports configuration and sensor resolution from Base_18 to Base_21.

 

[OneyedK]

You have the infamous IASInstallPhaseList.plist on your NVRAM volume (XML document, version: "1.0"), probably caused by a unsuccessful macOS install.

You can have incorrect HardwareIDs and checksums, this ones need to be checked with a BootROM dump inspection.

Descriptor Base_18 is the second oldest one, lots of updates with ports configuration and sensor resolution from Base_18 to Base_21.

Auch! If you find the time, would you be so kind to correct the rom for me? Thanks!!!

 

[kings79]

. I have a lot of BootROMs to correct, I can correct yours but not immediately. I'll PM you.

We all owe you alot of credit Alex. Thank you for helping us all.

 

[flashgauden]

cMP 4,1>5,1 138.0.0.0.0
Running macOS 10.14 and on separate drive Win 10 1803

Build date 090210090210p
override-versionBase_17

Binwalk
DECIMAL HEXADECIMAL DESCRIPTION
-------------------------------------------------------------------------------
0 0x0 UEFI PI firmware volume
16524 0x408C UEFI PI firmware volume
24972 0x618C CRC32 polynomial table, little endian
35787 0x8BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
49948 0xC31C UEFI PI firmware volume
524288 0x80000 UEFI PI firmware volume
540812 0x8408C UEFI PI firmware volume
549260 0x8618C CRC32 polynomial table, little endian
560075 0x88BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
574236 0x8C31C UEFI PI firmware volume
1048576 0x100000 UEFI PI firmware volume
1114112 0x110000 UEFI PI firmware volume
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume

 

[tsialex]

cMP 4,1>5,1 138.0.0.0.0
Running macOS 10.14 and on separate drive Win 10 1803

Build date 090210090210p
override-versionBase_17

Binwalk
DECIMAL HEXADECIMAL DESCRIPTION
-------------------------------------------------------------------------------
0 0x0 UEFI PI firmware volume
16524 0x408C UEFI PI firmware volume
24972 0x618C CRC32 polynomial table, little endian
35787 0x8BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
49948 0xC31C UEFI PI firmware volume
524288 0x80000 UEFI PI firmware volume
540812 0x8408C UEFI PI firmware volume
549260 0x8618C CRC32 polynomial table, little endian
560075 0x88BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
574236 0x8C31C UEFI PI firmware volume
1048576 0x100000 UEFI PI firmware volume
1114112 0x110000 UEFI PI firmware volume
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume

Normal, no SecureBoot certificates or IASInstallPhaseList.plist trashing your NVRAM.

 

[JedNZ]

I installed binwalk on my dual-CPU cMP and have provided the results of my BootRoms for both my cMP below. Are these results of value/interest to you @tsialex?

cMP 2009 4,1>5,1 – 6-Core (single CPU) – MacOS 10.13.6
Build Year 2009, Build Week 47, Production Nr. 740
Previous BootRom: MP51.0084.B00
Current BootRom: MP51.0089.B00
Note: It has never had the 87 BootRom installed.

This cMP was my original cMP 4,1 that I upgraded to 5,1 and upgraded to X5680.
It has had Win10 running on it on a separate SSD (it's now installed in my dual-CPU cMP). Still confused over whether it's legacy or not.
It has also had the dual-CPU (12-Core X5680) tray installed from my other cMP a couple of times.

MP51.0084.B00.bin
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 UEFI PI firmware volume
16524 0x408C UEFI PI firmware volume
24972 0x618C CRC32 polynomial table, little endian
35787 0x8BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
49948 0xC31C UEFI PI firmware volume
524288 0x80000 UEFI PI firmware volume
540812 0x8408C UEFI PI firmware volume
549260 0x8618C CRC32 polynomial table, little endian
560075 0x88BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
574236 0x8C31C UEFI PI firmware volume
1048576 0x100000 UEFI PI firmware volume
1114112 0x110000 UEFI PI firmware volume
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume

MP51.0089.B00.bin
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 UEFI PI firmware volume
16524 0x408C UEFI PI firmware volume
24972 0x618C CRC32 polynomial table, little endian
35787 0x8BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
49948 0xC31C UEFI PI firmware volume
524288 0x80000 UEFI PI firmware volume
540812 0x8408C UEFI PI firmware volume
549260 0x8618C CRC32 polynomial table, little endian
560075 0x88BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
574236 0x8C31C UEFI PI firmware volume
1048576 0x100000 UEFI PI firmware volume
1114112 0x110000 UEFI PI firmware volume
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume


cMP 2009 4,1>5,1 – 12-Core (Dual CPU)– MacOS 10.13.6
Build Year 2009, Build Week 49, Production Nr. 13
Previous BootRom: MP51.0084.B00 (sorry, didn't save a copy of the BootRom)
Current BootRom: MP51.0089.B00
Note: It has never had the 87 BootRom installed.

This is the second cMP 4,1 I purchased and has been upgraded to 5,1 with dual-X5680 - it's my primary machine.
It has Win10 installed on a separate SSD (in Bay1) which I boot into occasionally. Still confused over whether it's legacy or not.
It has had the 6-Core CPU tray from my other cMP in it on a couple of occasions.

MP51.0089.B00.bin
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 UEFI PI firmware volume
16524 0x408C UEFI PI firmware volume
24972 0x618C CRC32 polynomial table, little endian
35787 0x8BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
49948 0xC31C UEFI PI firmware volume
524288 0x80000 UEFI PI firmware volume
540812 0x8408C UEFI PI firmware volume
549260 0x8618C CRC32 polynomial table, little endian
560075 0x88BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
574236 0x8C31C UEFI PI firmware volume
1048576 0x100000 UEFI PI firmware volume
1114112 0x110000 UEFI PI firmware volume
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume

I mention the fact that I have swapped the CPU trays between the machines mainly to test when one of my X5680s was fried in my dual-CPU machine last year.

I have had my Windows HDD/SSD installed in both machines over the years. I don't know how to check if I have multiple certificates etc (sorry, don't know how to check this).

I originally installed Win7 on a 1TB spinner on my single-CPU cMP via an ISO (downloaded from Microsoft) burned onto a CD. I then upgraded by DVD to Win8.1 (I have previously posted my issues with doing all of this - quite a nightmare).
I then moved the Win8.1 from the spinner to a Samsung 850 EVO SSD using Paragon's Hard Disk Manager (copies all partitions without changing them) but had Windows activation issues due to the hardware change (CPU tray number different?). I sorted this out with Microsoft by phone, and then later upgraded for free to Win10 by direct download.

I mention my Win history just in case this helps you work out what causes the multiple certificates. Maybe you could analyse my BootRoms to see if it provides any clues.

 

[tsialex]

I installed binwalk on my dual-CPU cMP and have provided the results of my BootRoms for both my cMP below. Are these results of value/interest to you @tsialex?

cMP 2009 4,1>5,1 – 6-Core (single CPU) – MacOS 10.13.6
Build Year 2009, Build Week 47, Production Nr. 740
Previous BootRom: MP51.0084.B00
Current BootRom: MP51.0089.B00
Note: It has never had the 87 BootRom installed.

This cMP was my original cMP 4,1 that I upgraded to 5,1 and upgraded to X5680.
It has had Win10 running on it on a separate SSD (it's now installed in my dual-CPU cMP). Still confused over whether it's legacy or not.
It has also had the dual-CPU (12-Core X5680) tray installed from my other cMP a couple of times.

MP51.0084.B00.bin
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 UEFI PI firmware volume
16524 0x408C UEFI PI firmware volume
24972 0x618C CRC32 polynomial table, little endian
35787 0x8BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
49948 0xC31C UEFI PI firmware volume
524288 0x80000 UEFI PI firmware volume
540812 0x8408C UEFI PI firmware volume
549260 0x8618C CRC32 polynomial table, little endian
560075 0x88BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
574236 0x8C31C UEFI PI firmware volume
1048576 0x100000 UEFI PI firmware volume
1114112 0x110000 UEFI PI firmware volume
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume

MP51.0089.B00.bin
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 UEFI PI firmware volume
16524 0x408C UEFI PI firmware volume
24972 0x618C CRC32 polynomial table, little endian
35787 0x8BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
49948 0xC31C UEFI PI firmware volume
524288 0x80000 UEFI PI firmware volume
540812 0x8408C UEFI PI firmware volume
549260 0x8618C CRC32 polynomial table, little endian
560075 0x88BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
574236 0x8C31C UEFI PI firmware volume
1048576 0x100000 UEFI PI firmware volume
1114112 0x110000 UEFI PI firmware volume
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume


cMP 2009 4,1>5,1 – 12-Core (Dual CPU)– MacOS 10.13.6
Build Year 2009, Build Week 49, Production Nr. 13
Previous BootRom: MP51.0084.B00 (sorry, didn't save a copy of the BootRom)
Current BootRom: MP51.0089.B00
Note: It has never had the 87 BootRom installed.

This is the second cMP 4,1 I purchased and has been upgraded to 5,1 with dual-X5680 - it's my primary machine.
It has Win10 installed on a separate SSD (in Bay1) which I boot into occasionally. Still confused over whether it's legacy or not.
It has had the 6-Core CPU tray from my other cMP in it on a couple of occasions.

MP51.0089.B00.bin
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 UEFI PI firmware volume
16524 0x408C UEFI PI firmware volume
24972 0x618C CRC32 polynomial table, little endian
35787 0x8BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
49948 0xC31C UEFI PI firmware volume
524288 0x80000 UEFI PI firmware volume
540812 0x8408C UEFI PI firmware volume
549260 0x8618C CRC32 polynomial table, little endian
560075 0x88BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
574236 0x8C31C UEFI PI firmware volume
1048576 0x100000 UEFI PI firmware volume
1114112 0x110000 UEFI PI firmware volume
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume

I mention the fact that I have swapped the CPU trays between the machines mainly to test when one of my X5680s was fried in my dual-CPU machine last year.

I have had my Windows HDD/SSD installed in both machines over the years. I don't know how to check if I have multiple certificates etc (sorry, don't know how to check this).

I originally installed Win7 on a 1TB spinner on my single-CPU cMP via an ISO (downloaded from Microsoft) burned onto a CD. I then upgraded by DVD to Win8.1 (I have previously posted my issues with doing all of this - quite a nightmare).
I then moved the Win8.1 from the spinner to a Samsung 850 EVO SSD using Paragon's Hard Disk Manager (copies all partitions without changing them) but had Windows activation issues due to the hardware change (CPU tray number different?). I sorted this out with Microsoft by phone, and then later upgraded for free to Win10 by direct download.

I mention my Win history just in case this helps you work out what causes the multiple certificates. Maybe you could analyse my BootRoms to see if it provides any clues.

Both Macs have normal binwalk outputs, without SecureBoot certificates or IASInstallPhaseList.plist trashing your NVRAM.

Maybe could be interesting to check if you have any problem with your hardwareIDs or with checksums and update both your Macs to Base_21 hardware descriptor, I can PM you instructions but I doubt that I can check yours this week, since yours seems fine and some people here have multiple certificates in the NVRAM volume, one even have both the SecureBoot and IASInstallPhaseList - this one is unfortunate…

 

[JedNZ]

I'm not intending to update to 10.14 or 140.0.0.0 anytime soon @tsialex, so will leave you to help those who really need your awesome help first. Really impressed with how much work you're doing to help our community members. I don't understand it all, but I'm trying to stay up to date with these exciting developments. Over here in NZ we'd call you a "bloody legend, mate".

 

[tamarro]

Just checked all my saved MP5,1 ROMs and I have also this "XML document, version: "1.0" line in each of them. Is there any easy way to get rid of this potential threat?