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.
MP5,1: Return of the microcodes (MP51.0089.B00) **OBSOLETE**
- Thread starter tsialex
- Start date
-
- Tags
- mp51.0089.b00
- Sort by reaction score
- Status
I also have had no problems with APFS. Everything seems OK with all my Macs updated to High Sierra and running it on all SSDs
if you're using an Apricorn PCIe product, clone the drive to HFS+ formatted SSD (or via another drive then back to SSD) with Carbon Copy Cloner. Then use HFS+ in Apricorn and re-test. Unsure if their firmware supports APFS properly. Had NUMEROUS issues with APFS in my machine with majorly reduced write speeds back around 10.13.2.
I tried this now, but also with High Sierra installated in HFS+...no results! With the SSD alone it works, but when I put the SSD on Apricorns...nothing happens
It's like a power down isuue, because if I work with another system disc, sometimes i see the alert "the (SSD) disc has not been ejected correctly"
Was worth a shot... only thing you could try is another PCIe slot and double check to make sure it's seated properly in the slot to have full pin contact. Cleaning out the slot and pins on card would help if it's extremely dusty inside the machine.
Believe Apricorn stopped making the DUO X2, and assume the SOLO X2's that can be found are leftover stock or used units.
Believe Apricorn stopped making the DUO X2, and assume the SOLO X2's that can be found are leftover stock or used units.
Looks like BootChamp has now broke for me too as well
the only change between my last report on this and now was I updated to 10.13.6... so it might be a 10.13.6 bug rather then a BootROM issue (before I was on 10.13.5 but with the 0089 BootROM and I had no issues with boot champ) where you running 10.13.5 or 6 when the issue showed up?
Hi tsialex,
What's the best way to update to 31 using ucupdate? Do I need the actual microcode file?
Thanks
10.13.6. I never try BootChamp with 0089.B00 and 10.13.5, so, no idea if that make the difference.
I'm trying to understand how to do it too. My home Mac Pro had 31, my work Mac Pro still has 30.
More people received 31, was not just me. I'm thinking Apple was testing 31 on one of the last 10.13.6 betas and on Mojave betas. I'll have to investigate more.
The Intel website microcode site changed the format of the microcodes, so no more microcode.dat for forcing the update with xucode, I've asked the author of xucode to take a look on the new Intel format, maybe he can update his tool to it.
Perhaps we just need to get the microcode.dat from Mojave and copy it on 10.13.6.
Hello!
I downloaded BootChamp once more and installed it over the old BootChamp (Drag and drop it into the program folder.) Now my BootChamp works again.
Ofcourse do I have SIP disable.
BootChamp v 1,7
HS 10.13.6 MP51_0089_B00_NVMe.bin
/Per
I downloaded BootChamp once more and installed it over the old BootChamp (Drag and drop it into the program folder.) Now my BootChamp works again.
Ofcourse do I have SIP disable.BootChamp v 1,7
HS 10.13.6 MP51_0089_B00_NVMe.bin
/Per
On a side note, has anyone else noticed a slowdown in GUI performance since this new firmware was released?
My OS GUI felt much snappier to me before the firmware update. Maybe it's my imagination, but I'm disappointed with the perception anyway.
My OS GUI felt much snappier to me before the firmware update. Maybe it's my imagination, but I'm disappointed with the perception anyway.
everything is fine on my end... specs are in my sig
My cMP also feel more or less the same. Very responsive with the RX580.
Hello!
I downloaded BootChamp once more and installed it over the old BootChamp (Drag and drop it into the program folder.) Now my BootChamp works again.
BootChamp v 1,7
HS 10.13.6 MP51_0089_B00_NVMe.bin
/Per
Thanks for providing this work around. Will test this in few days.
Hi!
I’ve noticed that the wake-up time has increased from 5 to 10 sec. Otherwise it is responsive as it should.
/Per
I’ve noticed that the wake-up time has increased from 5 to 10 sec. Otherwise it is responsive as it should.
/Per
Apple released yesterday, yes Sunday, a new version of 10.13.6. Seems that's the build for the new MacBook Pros, 17G2112.
I'm downloading now to check the Firmware folder.
[doublepost=1531715637][/doublepost]
Weird, Apple downgraded the BootROM again?!? What's going on?
Edit: since it's a build specific for the 2018 MacBook Pros, Apple could have based the image on a earlier version of the tree or something along the lines. Maybe they just not upgraded the Firmware for a Mac that it's not supported by this build/supposed to run it.
I'm downloading now to check the Firmware folder.
[doublepost=1531715637][/doublepost]
Weird, Apple downgraded the BootROM again?!? What's going on?
Edit: since it's a build specific for the 2018 MacBook Pros, Apple could have based the image on a earlier version of the tree or something along the lines. Maybe they just not upgraded the Firmware for a Mac that it's not supported by this build/supposed to run it.
Last edited:
The firmware thing is becoming a nuisance. It makes it hard to have confidence with all the jumping around on versions.
Maybe it's not a downgrade thing, since it's a build specific for the 2018 MacBook Pros, Apple could have based the image on a earlier version of the tree or something along the lines.
Let's see what's going to be the firmware on Mojave Developer Preview 4.
Ah, so it was the 10.13.6 update that broke it. 10.14 beta broke it too for me, but it didn’t matter because I still had 10.13.5 as my main install.
Perhaps we should submit bug reports saying something like “Boot Camp can no longer boot from Startup Disk in System Preferences.” So it would be a Startup Disk bug. Mine is on a separate disk. I’m not sure if that makes a difference. Of course no reason to state anything about the BootChamp app since Apple wouldn’t support that.
If a microcode update fails / gets interrupted / is a mismatch... Does that brick your CPU or are there recovery options?
Some problems are solved with the Firmware Restoration CD, but if it's something more serious, you have to desolder the SPI Flash memory and reprogram it with a SPI Flash Programmer.
I had to do that =(
This is what I think as well.
[doublepost=1531719745][/doublepost]
And Apple never says cMP support UEFI Windows either. AFAIK, the start up disk selection still works for legacy Windows installation.
Of course we can still submit bug report. But that’s basically ask for extra function more than a bug report.
For anyone else troubleshooting - this didn't do anything for me.Hello!
I downloaded BootChamp once more and installed it over the old BootChamp (Drag and drop it into the program folder.) Now my BootChamp works again.
BootChamp v 1,7
HS 10.13.6 MP51_0089_B00_NVMe.bin
/Per
Unfortunately, sudo bless didn't work either - apparently it's because my copy of windows 10 is installed in EFI mode.
Resetting the NVRAM (command-option-P-R) got my Mac to boot directly into windows 10. Unfortunately, I forgot this also resets SIP and disables the NVIDIA web driver.
Once I managed to get SIP re-disabled and the NVIDIA drivers reinstalled, I found out that restarting via Bootchamp still makes the Mac boot from the wrong volume (no boot device found screen).On top of that, all of my sound devices except my c-media USB device have disappeared. That's... unfortunate.
So I think my next course of action is to wipe my boot drive clean and reinstall MacOS, then look into using rEFInd as my boot manager. Overall though, keeping these things running is such a pain in the butt I might as well be running a hackintosh
- Status