Ok, thanks. That’s correct, 2010 is on 10.14.4 and 2009 is on El Capitan.
Muito obrigado cara
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
Muito obrigado cara
IMO... The changes look positive. Changes to AppleGraphicsPolicy , APFSJumpStart, SataController and SmbiosMisc lines up with addressing the issue @crjackson2134 has been battling against for some time. Now if Apple can get MS to clean up their EFI mess.... Has anyone thought of entering bugs @ microsoft in Redmond WA for the EFI disaster they are causing??
Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin shasum from MP51.007F.B03 to 144.0.0.0.0:
Someone with IDA Pro license should take a look on the exact function of the table that Apple has been changing with 138/139/144.0.0.0.0.
Code:
741777e4655c55e60c89f71d96ca71064858f674 ./7F/MP51_007F_03B_LOCKED.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674 ./83/MP51_0083_00B_LOCKED.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674 ./84/MP51_0084_00B_LOCKED.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674 ./85/MP51_0085_00B_LOCKED.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674 ./87/MP51_0087_00B_LOCKED.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674 ./89/MP51_0089_00B_LOCKED.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
e57e098eb14b6448c7d225155977b53faa8434a7 ./138/MP51.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
ab6c04d2d19908ad545c272566cf2b916fa028d1 ./139/MP51.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674 ./140/MP51.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674 ./141/MP51.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674 ./142/MP51.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
e57e098eb14b6448c7d225155977b53faa8434a7 ./144/MP51.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.binSomeone with IDA Pro license should take a look on the exact function of the table that Apple has been changing with 138/139/144.0.0.0.0.
Last edited:
We actually got contact by Apple regrading on this issue. I only know the other group still put this project on hold since last time I talked to them. I have no idea why.
I wonder if they can improve Mac Pro itself boot time. It tooks nearly 15 seconds to see anything on screen. PC's start much faster.
Wouldn't count on it. If any improvements, they're likely accidental or coincidence vs. actually trying to improve boot times. If you have NVMe system drive, it will slow boot down but easily makes up for it with system operation. Personally cannot complain about the boot times on my authentic MP5,1 with NVMe and RX580 in Mojave. Find it slightly faster than High Sierra. I basically turn this machine on/off once per day at most, so it's not a big deal.
It is my understanding that this is due to more system memory. My 16GB 2009 Mac Pro takes about 10 seconds to get the chime, while my 2GB 2007 Mac mini takes about 2.
Last edited:
It's that, and a little more...
Simply put, the more hardware you have to detect and initialize (memory, PCIe, Storage, etc...), the longer it will take the cMP to boot. Some hardware won't necessarily increase the boot times, but it's a general rule of thumb.
Don't expect the BootROM to have a great affect on that...
Hi,
i think I have a general problem in updating firmware.
Mac Pro 4.1>5.1 (currently on 140.0.0.0) w Sappire Radeon7950 mac edition (original)...
But i can‘t install 10.14.4 from a stick. It says fw update required... but the machine did not shut down... manual sutdown does not the trick... even pressing the the button until sound produces just a normal startup with no fw update
any ideas?!
i think I have a general problem in updating firmware.
Mac Pro 4.1>5.1 (currently on 140.0.0.0) w Sappire Radeon7950 mac edition (original)...
But i can‘t install 10.14.4 from a stick. It says fw update required... but the machine did not shut down... manual sutdown does not the trick... even pressing the the button until sound produces just a normal startup with no fw update
any ideas?!
Last edited by a moderator:
Know that thread... the machine was on 10.14. just changed HDD to NVMe SSD... 10.14.0 will install w/o problems... but fw will not be updated - hopefully that will be solved with the final of 10.14.5 realy want to try the 144.0.0.0 for faster apfs startup...
Continuing from #3307, #3308, #3311, #3314, #3355, #3360.
Improvements:
Note: this BootROM showed above is the one sent with every matt card, so it's a "public" one cloned numerous times. No personal hardwareIDs here.
[doublepost=1556965185][/doublepost]BTW, more info about the matt clones here: #19
Improvements:
- hardwareID LBSN/MLB + BuildDate
- hardwareID HWC
- hardwareID override-version / Base_xx
Note: this BootROM showed above is the one sent with every matt card, so it's a "public" one cloned numerous times. No personal hardwareIDs here.
[doublepost=1556965185][/doublepost]BTW, more info about the matt clones here: #19
the machine was on Mojave:
Boot ROM Version 140.0.0.0.0
SMC Version (system) 1.39f5
SMC Version (processor tray) 1.39f5
Don't make a diff if you already are on Mojave, you still have to download and run the full installer for the current Mojave version, 10.14.4 is the current one, from macOS to upgrade the firmware to BootROM 141.0.0.0.0. USB firmware upgrades don't work.
10.14.0 installer don't ask for a firmware upgrade because it's BootROM is 138.0.0.0.0 and you already have 140.0.0.0.0. 10.14.4 needs 141.0.0.0.0, so it asks you to upgrade the BootROM.
Read the first post of this thread and the first post of MP5,1: What you have to do to upgrade to Mojave, all info you need are in these two first posts.
Last edited:
Problem solved:
I had to put the switch to PC Mode on the GPU... don't now why, but after that the update ran nomally...
Last edited:
Why Apple include NVMe EFI modules with Macs that you can't connect a M.2 blade, like late-2012 Mac mini?
MP6,1 dumps usually have more problems than MP5,1, no news here. MemoryConfig is stored differently than MP5,1, just noticed this for the 1st time.
A tool for MP6,1 NVRAM clean up would be a good idea in the future.
MP3,1 has a different BootBlock and MemoryConfig, but most things are the same:
[doublepost=1557020918][/doublepost]Btw, I only have three dumps from MP6,1s and it's not enough for testing. If you have a MP6,1 and want binwalk support for it, please dump the SPI flash with ROMTool and get in touch with me.
MP6,1 dumps usually have more problems than MP5,1, no news here. MemoryConfig is stored differently than MP5,1, just noticed this for the 1st time.
A tool for MP6,1 NVRAM clean up would be a good idea in the future.
MP3,1 has a different BootBlock and MemoryConfig, but most things are the same:
[doublepost=1557020918][/doublepost]Btw, I only have three dumps from MP6,1s and it's not enough for testing. If you have a MP6,1 and want binwalk support for it, please dump the SPI flash with ROMTool and get in touch with me.
Last edited:
I was going to comment on the NVMe thing but i was not sure if you where referring to just 2009-2010 Mac or every Pre 2013 Mac without a PCIe SSD built in
on the 2011-2012 macs its for thunderbolt, if someone plugs in a thunderbolt SSD, more and more of them are NVMe based these days and people will want to boot from them from time to time
on the 2011-2012 macs its for thunderbolt, if someone plugs in a thunderbolt SSD, more and more of them are NVMe based these days and people will want to boot from them from time to time
Yep, that explains the NVMe EFI module for Macs that are Thunderbolt capable, but don't have a PCIe connection like Mini late-2012.I was going to comment on the NVMe thing but i was not sure if you where referring to just 2009-2010 Mac or every Pre 2013 Mac without a PCIe SSD built in
on the 2011-2012 macs its for thunderbolt, if someone plugs in a thunderbolt SSD, more and more of them are NVMe based these days and people will want to boot from them from time to time
So since now we now which part is responsive for the RAM configuration, maybe it would be easier to bypass the 8 slots limitation on the xserve
No, nothing changed. This was always known, it's the memory configuration for each DIMM, not the EFI module responsible for doing the setup or reading the NVRAM after that.
Yes, makes sense that every Mac with Thunderbolt can boot from NVMe.
Hi @tsialex, i couldnt send you a DM so ill try here.
i have a MP6,1
3,5 GHz 6-Core Intel Xeon E5
and MP5,1 Mid 2010
2 x 3.33 GHz 6-Core Intel Xeon
(which have win 7 and 10 on it (bios mode)) and wanted to share SPI dumps with you.
my SPI is MX25L3205D on cMP and dumped to a bin file.
but for MP61 where is this chip located? which one is right one?
@tsialex Can you please point me where to seek for the dimm slot config?
Here is a difference between the two roms with the MemoryConfig explicitly defined.
googling for module description I have only found out that SaveMemoryConfig is responsiblefor writing the config to nvram, while MemorySubClass reads the currently installed DRAM config. So the only possible MemoryConfig -aware module in the firmware is the UncoreInitPeim. But inside the module is the hex config which I barely able to understand as you might see
.Since MP5,1 ROM successfully boots up on XS3,1 with the only issue being the 8 out of 12 RAM slots operational, I suppose that is easier fixing that isuue rather then trying adding the microcode etc. I currently have two quadcore logicbords to test with, and a dualcore logicboard on the way, and since I recently purchased a CH341a I am not afraid of bricking at least on of the mobo during such severe tests...
[doublepost=1557061222][/doublepost]
According to this, it is the second option you might choseHi @tsialex, i couldnt send you a DM so ill try here.
i have a MP6,1
3,5 GHz 6-Core Intel Xeon E5
and MP5,1 Mid 2010
2 x 3.33 GHz 6-Core Intel Xeon
(which have win 7 and 10 on it (bios mode)) and wanted to share SPI dumps with you.
my SPI is MX25L3205D on cMP and dumped to a bin file.
but for MP61 where is this chip located? which one is right one?