I just picked up a gorgeous 2012 5,1 Server. I'm waiting for my new X5675s before I get it up and running; do you have an example of this model for your bootROM collection? I'm gonna have to have you magic up a 140.0.0.0.0 anyway...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 MacPro5,1: BootROM thread | 144.0.0.0.0
- Thread starter tsialex
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I just picked up a gorgeous 2012 5,1 Server. I'm waiting for my new X5675s before I get it up and running; do you have an example of this model for your bootROM collection? I'm gonna have to have you magic up a 140.0.0.0.0 anyway...
I have one but it's corrupted, so I can't trust it.
Send me the dump in the same PM thread of your previous one, I'll check it. Thx, Daniel.
Just put in my tracking number into a Parcel app...my CPUs are being delivered TODAY. So I should have that bootROM headed your way by tomorrow.
Hi tsialex,
Thank you for all your contributions to the Mac community! Perhaps my ROMs be of use.
I have multiple EFI-booting installs (Mac, Windows, Linux) and CSM-booting installs (Windows, Linux).
I got the machines used a few years back and both had FW 84 and upgraded processors from stock (W3565, W3670). One is a 4,1 -> 5,1 upgrade, the other a 5,1. Both are now running x5680s.
I upgraded to 89 to run High Sierra / APFS and had saved the bins from each upgrade.
The 2010 would not boot EFI Windows 10 after the 89 update.
I did not attempt to boot EFI Windows 10 on the 2009 after the 2010 showed issues.
EFI Linux Mint 18.2 showed a screen before starting GRUB along the lines of "searching for APFS volumes" which was new with the 89 firmware on the 2010. I will try to get a screenshot of the exact message when it appears again and also see if it also occurs on the 2009.
I have been cautious with my Mac Pro's after seeing your findings and having to reinstall Windows. I am holding off on 138/140 & Mohave until I receive an MVC metal -capable graphics card and am confident my machines not having any corruptions.
Here are the results of the binwalk:
Toms-Mac-Mini
esktop $ binwalk Mac\ Pro\ 2009\ FW\ 0084.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
1183814 0x121046 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1249350 0x131046 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Toms-Mac-Miniesktop $ binwalk Mac\ Pro\ 2009\ FW\ 0089.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
1183814 0x121046 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Toms-Mac-Miniesktop $ binwalk Mac\ Pro\ 2010\ 0084\ RomDump.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
1191555 0x122E83 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1257091 0x132E83 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343511 0x148017 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Toms-Mac-Miniesktop $ binwalk Mac\ Pro\ 2010\ 0089\ RomDump.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
1188789 0x1223B5 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1254325 0x1323B5 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343511 0x148017 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Thank you for all your contributions to the Mac community! Perhaps my ROMs be of use.
I have multiple EFI-booting installs (Mac, Windows, Linux) and CSM-booting installs (Windows, Linux).
I got the machines used a few years back and both had FW 84 and upgraded processors from stock (W3565, W3670). One is a 4,1 -> 5,1 upgrade, the other a 5,1. Both are now running x5680s.
I upgraded to 89 to run High Sierra / APFS and had saved the bins from each upgrade.
The 2010 would not boot EFI Windows 10 after the 89 update.
I did not attempt to boot EFI Windows 10 on the 2009 after the 2010 showed issues.
EFI Linux Mint 18.2 showed a screen before starting GRUB along the lines of "searching for APFS volumes" which was new with the 89 firmware on the 2010. I will try to get a screenshot of the exact message when it appears again and also see if it also occurs on the 2009.
I have been cautious with my Mac Pro's after seeing your findings and having to reinstall Windows. I am holding off on 138/140 & Mohave until I receive an MVC metal -capable graphics card and am confident my machines not having any corruptions.
Here are the results of the binwalk:
Toms-Mac-Mini
esktop $ binwalk Mac\ Pro\ 2009\ FW\ 0084.binDECIMAL 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
1183814 0x121046 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1249350 0x131046 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Toms-Mac-Mini
esktop $ binwalk Mac\ Pro\ 2009\ FW\ 0089.binDECIMAL 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
1183814 0x121046 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Toms-Mac-Mini
esktop $ binwalk Mac\ Pro\ 2010\ 0084\ RomDump.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
1191555 0x122E83 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1257091 0x132E83 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343511 0x148017 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Toms-Mac-Mini
esktop $ binwalk Mac\ Pro\ 2010\ 0089\ RomDump.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
1188789 0x1223B5 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1254325 0x1323B5 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343511 0x148017 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
I sent you a PM, yours could be a good example of NVRAM problems.Hi tsialex,
Thank you for all your contributions to the Mac community! Perhaps my ROMs be of use.
I have multiple EFI-booting installs (Mac, Windows, Linux) and CSM-booting installs (Windows, Linux).
I got the machines used a few years back and both had FW 84 and upgraded processors from stock (W3565, W3670). One is a 4,1 -> 5,1 upgrade, the other a 5,1. Both are now running x5680s.
I upgraded to 89 to run High Sierra / APFS and had saved the bins from each upgrade.
The 2010 would not boot EFI Windows 10 after the 89 update.
I did not attempt to boot EFI Windows 10 on the 2009 after the 2010 showed issues.
EFI Linux Mint 18.2 showed a screen before starting GRUB along the lines of "searching for APFS volumes" which was new with the 89 firmware on the 2010. I will try to get a screenshot of the exact message when it appears again and also see if it also occurs on the 2009.
I have been cautious with my Mac Pro's after seeing your findings and having to reinstall Windows. I am holding off on 138/140 & Mohave until I receive an MVC metal -capable graphics card and am confident my machines not having any corruptions.
Here are the results of the binwalk:
Toms-Mac-Mini
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
1183814 0x121046 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1249350 0x131046 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Toms-Mac-Mini
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
1183814 0x121046 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Toms-Mac-Mini
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
1191555 0x122E83 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1257091 0x132E83 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343511 0x148017 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Toms-Mac-Mini
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
1188789 0x1223B5 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1254325 0x1323B5 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343511 0x148017 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Hi tsialex,
Thank you for all your contributions to the Mac community! Perhaps my ROMs be of use.
I have multiple EFI-booting installs (Mac, Windows, Linux) and CSM-booting installs (Windows, Linux).
I got the machines used a few years back and both had FW 84 and upgraded processors from stock (W3565, W3670). One is a 4,1 -> 5,1 upgrade, the other a 5,1. Both are now running x5680s.
I upgraded to 89 to run High Sierra / APFS and had saved the bins from each upgrade.
The 2010 would not boot EFI Windows 10 after the 89 update.
I did not attempt to boot EFI Windows 10 on the 2009 after the 2010 showed issues.
EFI Linux Mint 18.2 showed a screen before starting GRUB along the lines of "searching for APFS volumes" which was new with the 89 firmware on the 2010. I will try to get a screenshot of the exact message when it appears again and also see if it also occurs on the 2009.
I have been cautious with my Mac Pro's after seeing your findings and having to reinstall Windows. I am holding off on 138/140 & Mohave until I receive an MVC metal -capable graphics card and am confident my machines not having any corruptions.
Here are the results of the binwalk:
Toms-Mac-Mini
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
1183814 0x121046 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1249350 0x131046 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Toms-Mac-Mini
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
1183814 0x121046 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343538 0x148032 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Toms-Mac-Mini
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
1191555 0x122E83 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1257091 0x132E83 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343511 0x148017 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Toms-Mac-Mini
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
1188789 0x1223B5 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1254325 0x1323B5 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343511 0x148017 bzip2 compressed data, block size = 100k
1376256 0x150000 UEFI PI firmware volume
Have you tried:
Whenever it failed to boot EFI Windows?
You're actually missing out on some pretty crucial security updates to the CPU microcode by not updating. I'd recommend 089 at a minimum.Haha I'm aware of that- since I don't have any real need to boot off of NVME or anything like that, I'm really in no rush right now. I'll get around to it at some point
Yes. PRAM reset had no effect.
I then successfully updated to 0140 BootROM reconstructed by tsialex.
No change for Windows. It freezes right after choosing the drive in the boot screen. (Cursor lockup, etc.)
A similar EFI Windows setup (10.0.16299.431) on the 2009 booted fine with 0089 and tsialex's 0140 BootROM.
I have seen this when it tries to boot EFI as CSM or maybe vice versa.
I saw the lockup on both machines right after boot screen when booting from Windows Installer USB if the drive is not created "just right." Posts in other forums implied Windows not liking the new microcodes. Others showed the latest Windows update causing issues. It could be many things. I also replaced the SATA cables running to the ODD drive cage when this first occurred so the old cables may have corrupted the install.
I will reinstall Windows later and see what shows up.
Attached is the screen from Linux EFI booting after BootROM 0089.
This is probably not new info, but I hadn't come across something like it on these forums.
Did you try 3 times normally Windows offers repair solutions where you can choose safe mode. Sometimes I have video driver issue with same symptoms after the 3rd attempt I go to safe mode and reinstall the drivers. Just force shutdown and restart 3 times and see if it offers Windows repair. What revision is Windows do you know by any chance?
All know MP5,1 BootROM versions:
** betas
- MP51.007F.B00
- MP51.007F.B01
- MP51.007F.B02
- MP51.007F.B03
- MP51.0082.B00 **
- MP51.0083.B00 **
- MP51.0084.B00
- MP51.0085.B00
- MP51.0087.B00
- MP51.0089.B00
- 138.0.0.0.0
- 139.0.0.0.0 **
- 140.0.0.0.0 **
** betas
Last edited:
Don't get me wrong, but this is unrelated to the BootROM thread, let's get on topic here.
Please ask your question in the correct thread: Blade SSDs - NVMe & AHCI
there was a 0082? guessing that was some sort of internal build?
as the first public BR update after B03 was 0083 in one of the High Sierra DPs.
It’s a beta one, probably internal or limited release. This one was listed sometime ago into one of the efiflashers, like MP51.007F.B0[0,2].
Hi, De-lidded my X5680's, went very well. With a paint stripper.
I want to use the CPU's one by one in socket A. How do I do that? Can I remove CPU "B" and its memory and leave the cooling tower off?
I know that I can use my 2009 cMP with 1 cpu, but my question is: what have I to remove to use only CPU A?
Do I remove the memory for the B CPU, can I leave the heatsink for CPU B off?
Obviously I have to remove CPU B, but what to do with the heatsink? Just leave it off?
Memory and heatsink. Fans will go full blast. Just use it for checking the processor.
Do not put anything on the socket if no CPU at there, you don’t want anything accidentally touch the pins and bend them.
