Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Just to add to Earl's post, my Mac Pro 5,1 was also in need to reinstalling 10.3.5 since my old boot drive developed errors. Got a new hard drive, reinstalled using a fresh download as well has resulted in me going from microcode 0 prior to the issue to now having microcode 25 while still showing 087 as my firmware.
 
A new beta is out. Perhaps we have a new EFI ?

Possible, the microcode revision guidance is just updated

https://www.intel.com/content/dam/www/public/us/en/documents/sa00115-microcode-update-guidance.pdf
[doublepost=1530649635][/doublepost]
fresh download of full 10.3.5 installer, microcode 31 bootrom MP51.0087.B00

Were you with 0087.B00 before? Or is this your first upgrade to 0087.B00? I want to know if the installer will tell you the firmware upgrade again despite with the same BootROM version.
 
I was at 0085.B00 before on Mojave PB. Downloaded the 10.3.5 full installer yesterday and started the install to move to 87 on Mojave.
 
So, I've been on 0087 for a while with microcode 0

I just downloaded the full installer and did a fresh install over my existing APFS 10.13.5 (tired it several times) from a USB Thumb drive boot.

End result is no change here. No firmware update, no microcode update.

So how do I now update the the corrected 0087 with proper microcode?
 
So, I've been on 0087 for a while with microcode 0

I just downloaded the full installer and did a fresh install over my existing APFS 10.13.5 (tired it several times) from a USB Thumb drive boot.

End result is no change here. No firmware update, no microcode update.

So how do I now update the the corrected 0087 with proper microcode?

1) we need a little bit more info to confirm if Apple really release a new firmware with the exact same BootROM version number.

2) Did you ever dump and backup your 0085.B00 firmware? If yes, use ROMTool to flash that back into your Mac, then the latest installer will ask you to upgrade to 0087.B00 (the new one?) again.
[doublepost=1530652091][/doublepost]
I was at 0085.B00 before on Mojave PB. Downloaded the 10.3.5 full installer yesterday and started the install to move to 87 on Mojave.

Just download the 10.13.5 full installer again, extracted the 0087.B00 from the installer, still no microcode in there.

Can you post a screenshot of your OS microcode confirmation with OS version and BootROM version please?
[doublepost=1530652190][/doublepost]
A new beta is out. Perhaps we have a new EFI ?

I am with the PB, not DP.

The firmware still 0085.B00 in the latest PB (I downloaded that just 5min ago), and microcode version still 15.
 
1) we need a little bit more info to confirm if Apple really release a new firmware with the exact same BootROM version number.

2) Did you ever dump and backup your 0085.B00 firmware? If yes, use ROMTool to flash that back into your Mac, then the latest installer will ask you to upgrade to 0087.B00 (the new one?) again.

No, I didn’t backup the 0085.
 
No, I didn’t backup the 0085.

Then you can edit the firmware file's name in the installer to something like MP51_0087_01B_LOCKED, the installer should ask your to perform the firmware update.

But up to this moment, I can't see the microcode version 31 in the latest 10.13.5 full installer.
 
^^^^Do you have another storage device with an OS on it. Update that one to 10.13.5, that should update the FW. But, if it's still missing microcode, not much point.

Lou
 
1) we need a little bit more info to confirm if Apple really release a new firmware with the exact same BootROM version number.

2) Did you ever dump and backup your 0085.B00 firmware? If yes, use ROMTool to flash that back into your Mac, then the latest installer will ask you to upgrade to 0087.B00 (the new one?) again.
[doublepost=1530652091][/doublepost]

Just download the 10.13.5 full installer again, extracted the 0087.B00 from the installer, still no microcode in there.

Can you post a screenshot of your OS microcode confirmation with OS version and BootROM version please?
[doublepost=1530652190][/doublepost]

I am with the PB, not DP.

The firmware still 0085.B00 in the latest PB (I downloaded that just 5min ago), and microcode version still 15.
machdep.cpu.max_basic: 11
machdep.cpu.max_ext: 2147483656
machdep.cpu.vendor: GenuineIntel
machdep.cpu.brand_string: Intel(R) Xeon(R) CPU W3680 @ 3.33GHz
machdep.cpu.family: 6
machdep.cpu.model: 44
machdep.cpu.extmodel: 2
machdep.cpu.extfamily: 0
machdep.cpu.stepping: 2
machdep.cpu.feature_bits: 188838921972218879
machdep.cpu.extfeature_bits: 5034215680
machdep.cpu.signature: 132802
machdep.cpu.brand: 0
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 POPCNT AES PCID
machdep.cpu.extfeatures: SYSCALL XD 1GBPAGE EM64T LAHF RDTSCP TSCI
machdep.cpu.logical_per_package: 32
machdep.cpu.cores_per_package: 16
machdep.cpu.microcode_version: 31
machdep.cpu.processor_flag: 0
machdep.cpu.mwait.linesize_min: 64
machdep.cpu.mwait.linesize_max: 64
machdep.cpu.mwait.extensions: 3
machdep.cpu.mwait.sub_Cstates: 4384
machdep.cpu.thermal.sensor: 1
machdep.cpu.thermal.dynamic_acceleration: 1
machdep.cpu.thermal.invariant_APIC_timer: 1
machdep.cpu.thermal.thresholds: 2
machdep.cpu.thermal.ACNT_MCNT: 1
machdep.cpu.thermal.core_power_limits: 0
machdep.cpu.thermal.fine_grain_clock_mod: 0
machdep.cpu.thermal.package_thermal_intr: 0
machdep.cpu.thermal.hardware_feedback: 0
machdep.cpu.thermal.energy_policy: 0
machdep.cpu.arch_perf.version: 3
machdep.cpu.arch_perf.number: 4
machdep.cpu.arch_perf.width: 48
machdep.cpu.arch_perf.events_number: 7
machdep.cpu.arch_perf.events: 4
machdep.cpu.arch_perf.fixed_number: 3
machdep.cpu.arch_perf.fixed_width: 48
machdep.cpu.cache.linesize: 64
machdep.cpu.cache.L2_associativity: 8
machdep.cpu.cache.size: 256
machdep.cpu.tlb.inst.small: 64
machdep.cpu.tlb.inst.large: 7
machdep.cpu.tlb.data.small: 64
machdep.cpu.tlb.data.large: 32
machdep.cpu.tlb.shared: 512
machdep.cpu.address_bits.physical: 36
machdep.cpu.address_bits.virtual: 48
machdep.cpu.core_count: 6
machdep.cpu.thread_count: 12
machdep.cpu.tsc_ccc.numerator: 0
machdep.cpu.tsc_ccc.denominator: 0machdep.cpu.thread_count: 12
machdep.cpu.tsc_ccc.numerator: 0
machdep.cpu.tsc_ccc.denominator: 0
 
Last edited:
Then you can edit the firmware file's name in the installer to something like MP51_0087_01B_LOCKED, the installer should ask your to perform the firmware update.

But up to this moment, I can't see the microcode version 31 in the latest 10.13.5 full installer.

I’ll wait until I see proof of microcode updates. If I knew for a fact this would give me Apple’s official microcode Fix I’d do it. I think I’ll wait until it’s verified.
[doublepost=1530654373][/doublepost]
^^^^Do you have another storage device with an OS on it. Update that one to 10.13.5, that should update the FW. But, if it's still missing microcode, not much point.

Lou

4 in fact, but none of the resulted in an updated firmware. My machine is already at 0087, so Apple would have to increase or change the version number for an update to be recognized.

I’m quite positive that changing the file name in the installer myself (as h9826790 suggests) would accomplish a forced FW update, but I’ll wait until I know the microcode is updated.
 
machdep.cpu.max_basic: 11
machdep.cpu.max_ext: 2147483656
machdep.cpu.vendor: GenuineIntel
machdep.cpu.brand_string: Intel(R) Xeon(R) CPU W3680 @ 3.33GHz
machdep.cpu.family: 6
machdep.cpu.model: 44
machdep.cpu.extmodel: 2
machdep.cpu.extfamily: 0
machdep.cpu.stepping: 2
machdep.cpu.feature_bits: 188838921972218879
machdep.cpu.extfeature_bits: 5034215680
machdep.cpu.signature: 132802
machdep.cpu.brand: 0
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 POPCNT AES PCID
machdep.cpu.extfeatures: SYSCALL XD 1GBPAGE EM64T LAHF RDTSCP TSCI
machdep.cpu.logical_per_package: 32
machdep.cpu.cores_per_package: 16
machdep.cpu.microcode_version: 31
machdep.cpu.processor_flag: 0
machdep.cpu.mwait.linesize_min: 64
machdep.cpu.mwait.linesize_max: 64
machdep.cpu.mwait.extensions: 3
machdep.cpu.mwait.sub_Cstates: 4384
machdep.cpu.thermal.sensor: 1
machdep.cpu.thermal.dynamic_acceleration: 1
machdep.cpu.thermal.invariant_APIC_timer: 1
machdep.cpu.thermal.thresholds: 2
machdep.cpu.thermal.ACNT_MCNT: 1
machdep.cpu.thermal.core_power_limits: 0
machdep.cpu.thermal.fine_grain_clock_mod: 0
machdep.cpu.thermal.package_thermal_intr: 0
machdep.cpu.thermal.hardware_feedback: 0
machdep.cpu.thermal.energy_policy: 0
machdep.cpu.arch_perf.version: 3
machdep.cpu.arch_perf.number: 4
machdep.cpu.arch_perf.width: 48
machdep.cpu.arch_perf.events_number: 7
machdep.cpu.arch_perf.events: 4
machdep.cpu.arch_perf.fixed_number: 3
machdep.cpu.arch_perf.fixed_width: 48
machdep.cpu.cache.linesize: 64
machdep.cpu.cache.L2_associativity: 8
machdep.cpu.cache.size: 256
machdep.cpu.tlb.inst.small: 64
machdep.cpu.tlb.inst.large: 7
machdep.cpu.tlb.data.small: 64
machdep.cpu.tlb.data.large: 32
machdep.cpu.tlb.shared: 512
machdep.cpu.address_bits.physical: 36
machdep.cpu.address_bits.virtual: 48
machdep.cpu.core_count: 6
machdep.cpu.thread_count: 12
machdep.cpu.tsc_ccc.numerator: 0
machdep.cpu.tsc_ccc.denominator: 0machdep.cpu.thread_count: 12
machdep.cpu.tsc_ccc.numerator: 0
machdep.cpu.tsc_ccc.denominator: 0

Thanks, can you double check what's your OS build number now?

I extracted the BootROM from the installer, it's nothing there. I wonder if Apple use the software way to inject the microcode at the OS level, and it's actually a quiet update without changing the OS version (but the build number may be changed).
 
Thanks, can you double check what's your OS build number now?

I extracted the BootROM from the installer, it's nothing there. I wonder if Apple use the software way to inject the microcode at the OS level, and it's actually a quiet update without changing the OS version (but the build number may be changed).

If this were the case, wouldn’t my freshly downloaded and installed copy from earlier today have updated my microcode? It’s still at 0.
 
If this were the case, wouldn’t my freshly downloaded and installed copy from earlier today have updated my microcode? It’s still at 0.

It should, I still have no idea why he has version 31.

It will be good if he can dump the firmware and open that bin file by Apple Microcode Tool. So that we can know if the microcode is stored inside the firmware or OS
 
  • Like
Reactions: crjackson2134
Thanks, can you double check what's your OS build number now?

I extracted the BootROM from the installer, it's nothing there. I wonder if Apple use the software way to inject the microcode at the OS level, and it's actually a quiet update without changing the OS version (but the build number may be changed).

10.14 beta (public) 18A314k but as I said, this was the already the previously installed Mojave OS with 0085.B00. I downloaded the full installer for 110.13.5 created a USB installer and ONLY ran the install to the point of flashing the firmware.
 
10.14 beta (public) 18A314k but as I said, this was the already the previously installed Mojave OS with 0085.B00. I downloaded the full installer for 110.13.5 created a USB installer and ONLY ran the install to the point of flashing the firmware.

Thanks, so it seems the microcode is injected at the OS level, and only available in the latest 10.14 PB. I will test that later, thanks for your info.
 
  • Like
Reactions: crjackson2134
Today's Mojave DP3 still has MP51_0085_00B_LOCKED.fd from June 9.
Screen Shot 2018-07-03 at 23.17.26.png
Screen Shot 2018-07-03 at 23.18.46.png
 
I really hope that when High Sierra 10.13.6 is released, it provides a firmware that will fix this whole 0087 microcode mess.

I’m also a little concerned that my Flashed HD7970 may not work OOTB with the normal release (no work-around) version of Mojave. If this is the last officially supported version for my Mid 2012 MacPro, I want everything to work properly without any hacks. This is why 10.13.6 firmware needs to be righteous in my opinion.
 
I really hope that when High Sierra 10.13.6 is released, it provides a firmware that will fix this whole 0087 microcode mess.

I’m also a little concerned that my Flashed HD7970 may not work OOTB with the normal release (no work-around) version of Mojave. If this is the last officially supported version for my Mid 2012 MacPro, I want everything to work properly without any hacks. This is why 10.13.6 firmware needs to be righteous in my opinion.

Screen Shot 2018-07-04 at 00.24.37.png


Mojave DP3 now installs without resorting to startosinstall on HD7870. According to the DP3 release notes, that was a bug.

Resolved -> When attempting to install macOS Mojave on Mac Pro mid 2010 and mid 2012 models you might see an error message ‘This version of macOS 10.14 cannot be installed on this computer.

MojaveDP3_AboutthisMac.png
 
Last edited:
I notice that in the section containing the typical cMP aftermarket CPUs (bottom of page 17), The W3690 is conspicuously missing?

I notice that as well. However, if you check the old document, W3690 is always placed on another section because its code name is Gulftown but not Westmere EP.

And in the last document, it indicated that the microcode development of Gulftown is stopped. May be this is the reason why it's now completely removed.

However, it seems the W3690 can utilise the Westmere EP's microcode without any issue.

When we update the microcode, as long as we updated the microcode for CPUID 206C2, the W3690 will able to utilise the new microcode automatically.
 
  • Like
Reactions: Synchro3 and frou
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.