Installed the new firmware revision successfully on a genuine mac pro 5,1 with an rx560! I do get the 5gt/s!
FYI edit: this is a sapphire pulse version as well
FYI edit: this is a sapphire pulse version as well
Attachments
Last edited:
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 upgraded to dp7 today and did not see a firmware upgrade screen pop up on a 5,1 with a rx470. Is the new firmware on a full download or upgrade? I’ll check when I get back to my desk.
Yes, same here. Can confirm that with non-EFI cards there is absolutely no video during the FW flash (which makes sense) but otherwise the sequence is exactly the same as before once you hold down the power button (flashing LED, long beep, chime, open CD tray, close CD tray, chime).
Agree that we all still need to report no HDMI audio for the 560/580 (that one would be so easy for Apple to fix) and of course no ability to use FV2, which may indeed be required for cMPs in a business setting.
As usual I don't think it's in the upgrade. Have to download the full DP7 installer.
I downloaded it from ddosdudes patcher as a full mojave installer, not as an update.
One of the two same part numbers that Apple shipped, yep. You can change the part number by editing the BIOS btw, there's an excellent post somewhere by @h9826790 which runs through how.is this one of the ones with the Same BIOS PN that apple shipped with the eGPU dev kits or?
while other RX 580s (and even some Pulse RX 580s which had diffrent PNs) have to make do with a generic frame-buffer, is that screen shot on the latest Mojave Beta or? im trying to work out if Apple is giving more RX 580s proper frame-buffer personalities
PS can you run CL!ng and post the Device to host and host to device results?
And yes, running latest Mojave DP7.
Seems that Apple enabled 5GT/s for more cards, HD 7870:
![Screen Shot 2018-08-13 at 17.38.30.png]( "Screen Shot 2018-08-13 at 17.38.30.png")
Thanks. The 5,1 is still running on 0085. I'll upgrade the rescued 2009 when I get home from the office and will attempt to inject NVMe, if there is still room. Hopefully the added microcodes didn't take up too much space.
Has anyone looked to see if NVMe support was added to the package?
I don't think so, but it would be a Godsend. I was tempted to try it, but I don't have another Mac or the skillset and tools needed to recover from a bricked machine.
Agreed. If Apple included NVMe.ffs as part of the ROM would be IDEAL. Having a second mac to test/hack on at the house helps in these situations. Although, If I did end up bricking it, I have a spare 4,1 logic board that I need to send back. So in effect my backup mac has a backup incase its firmware gets bricked.
Really Off Topic:
If I had bought a MP6,1, I'd be red with anger today… Apple is supporting MP5,1 much better than the trashcan.
If I had bought a MP6,1, I'd be red with anger today… Apple is supporting MP5,1 much better than the trashcan.
I would love to install this also, but alas I am not a dev and I don't want to pay out for the privilege for a beta. I wonder how long till the final public release is out. must say though looking good for us Mac Pro users!
thumbs up to apple
thumbs up to apple
Let's hope this is a foreshadowing of the 7,1.
Well the nMP's deficiencies can't really be addressed via firmware, right? I mean they already got native NVMe booting and I think Apple also fixed the earlier problem it had displaying 4K boot screens.
In terms of just sheer longevity though, yes the third-gen cMP is a champ--especially the 4,1. Shipped with Leopard and able to officially run Mojave with few compromises.
Apple needs at least to resolve the APFS + NTFS (BootCamp) KP/corruption on shutdown on MP6,1 with NVMe. People are loosing data and that could be addressed via firmware/updates.
you can get it with the ddosdudes patcher tool!I would love to install this also, but alas I am not a dev and I don't want to pay out for the privilege for a beta. I wonder how long till the final public release is out. must say though looking good for us Mac Pro users!
thumbs up to apple
Apple released Mojave Public Beta 6, same release as Developer Preview 7.
Last edited:
Thanks, I'll get it when I can reboot. At least that way I can install without fussing around with the firmware.
I'm so tempted to try the NVMe payload, but I'm gonna wait until I know if it's safe for not.
I'm so tempted to try the NVMe payload, but I'm gonna wait until I know if it's safe for not.
BTW I noticed that in CPU Z with the new BootROM its reporting a full 32768 MB of RAM previously it would show 32760 MB
I wonder if Apples tweaked some memory allocation/address space setups.
it would be interesting to hear from the people running 4+ Modern GPUs in a Mac Pro 5,1 if they can now boot (I Know before if you had 4+ modern GPUs in a Mac Pro it would fail to post due to a lack of IO address space)
I wonder if Apples tweaked some memory allocation/address space setups.
it would be interesting to hear from the people running 4+ Modern GPUs in a Mac Pro 5,1 if they can now boot (I Know before if you had 4+ modern GPUs in a Mac Pro it would fail to post due to a lack of IO address space)
Apple build 138.0.0.0.0 BootROM on July 30:
Checked for SSN, HWC, SON and LBSN, still at the usual places.
[doublepost=1534197653][/doublepost]Apple revamped the firmware a lot btw. Lots of new spaces, some things become compressed, etc.
Code:
Apple ROM Version
Model: MP51
EFI Version: 138.0.0.0.0
Date: Mon Jul 30 06:22:43 2018
Build Type: ReleaseChecked for SSN, HWC, SON and LBSN, still at the usual places.
[doublepost=1534197653][/doublepost]Apple revamped the firmware a lot btw. Lots of new spaces, some things become compressed, etc.
Somebody, @handheldgames?, posted about the firmware microcode space. On 138.0.0.0.0 there is LESS space available than MP51.0089.B00.
138.0.0.0.0:
![BootROM 138.0.0.0.0 microcodes.png]( "BootROM 138.0.0.0.0 microcodes.png")
MP51.0089.B00:
![MP51_0089_microcodes.png]( "MP51_0089_microcodes.png")
138.0.0.0.0:
MP51.0089.B00: