Hi all. Just an FYI I installed the developer beta of Catalina on my Mac Pro 6,1, and the BIOS is now reporting as 130.0.0.0.0.
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.
NVMe with ST-NGFF2013-C; Vega Internal GPU; Mac Pro 2013 (6,1)
- Thread starter CodeJingle
- Start date
- Sort by reaction score
Ok guys... after the last keynote it seems that I have to full upgrade my Mac Pro 6.1 for one last time...
It is a 6-Core model with 64GB Ram, 512GB SSD and the D500 graphics (OS 10.14.5)
My everyday work: photoshop PSB files with about 7-15GB size... so filters, smartobjects, objects transforms and save processes let me wait ways to often...
What is the best I can do for the best possible work experience with my good old trash can?
It is a 6-Core model with 64GB Ram, 512GB SSD and the D500 graphics (OS 10.14.5)
My everyday work: photoshop PSB files with about 7-15GB size... so filters, smartobjects, objects transforms and save processes let me wait ways to often...
What is the best I can do for the best possible work experience with my good old trash can?
These are some massive files right there - Photoshop might well just be struggling with wrangling all that data internally, limited by its own architecture. Some users report that the 2015 versions are more responsive than newer iterations for large data sets.
Unless your computer is stalling because of scratch files or hitting the system memory cap I don't think there is an upgrade available that solves these problems.
I'd look into splitting elements up into multiple files to ease the load. Can't you commit finished elements to 'proxies' and keep a live version in another file for the case that you have to touch them again?
Unless your computer is stalling because of scratch files or hitting the system memory cap I don't think there is an upgrade available that solves these problems.
I'd look into splitting elements up into multiple files to ease the load. Can't you commit finished elements to 'proxies' and keep a live version in another file for the case that you have to touch them again?
BootROM 131.0.0.0.0 for MP6.1 released with 10.14.6 DP2
10.14.6 DP2 EFI Version table for non BridgeOS Macs:
(All Macs had firmware upgrades except MP5,1)
Code:
$IBIOSI$ MP61.88Z.F000.B00.1905251553
Copyright (c) 2005-2019 Apple Inc. All rights reserved.
Apple ROM Version
Model: MP61
EFI Version: 131.0.0.0.0
Built by: root@saumon
Date: Sat May 25 15:53:29 PDT 2019
Revision: 131 (B&I)
ROM Version: F000_B00
Build Type: Official Build, Release
Compiler: Apple clang version 3.0 (tags/Apple/clang-211.10.1) (based on LLVM 3.0svn)10.14.6 DP2 EFI Version table for non BridgeOS Macs:
(All Macs had firmware upgrades except MP5,1)
| Mac: | EFI version: |
|---|---|
| IM13,1 | 286.0.0.0.0 |
| IM14,1 | 138.0.0.0.0 |
| IM14,2 | 138.0.0.0.0 |
| IM14,3 | 138.0.0.0.0 |
| IM14,4 | 198.0.0.0.0 |
| IM15,1 | 229.0.0.0.0 |
| IM16,1 | 228.0.0.0.0 |
| IM16,2 | 228.0.0.0.0 |
| IM17,1 | 168.0.0.0.0 |
| IM18,1 | 173.0.0.0.0 |
| IM18,3 | 173.0.0.0.0 |
| IM19,1 | 220.270.076.0.0 |
| MB10,1 | 176.0.0.0.0 |
| MB8,1 | 182.0.0.0.0 |
| MB9,1 | 182.0.0.0.0 |
| MBA5,1 | 258.0.0.0.0 |
| MBA6,1 | 116.0.0.0.0 |
| MBA7,1 | 187.0.0.0.0 |
| MBP10,1 | 256.0.0.0.0 |
| MBP10,2 | 279.0.0.0.0 |
| MBP11,1 | 155.0.0.0.0 |
| MBP11,2 | 155.0.0.0.0 |
| MBP11,4 | 193.0.0.0.0 |
| MBP12,1 | 185.0.0.0.0 |
| MBP13,1 | 234.0.0.0.0 |
| MBP13,2 | 257.0.0.0.0 |
| MBP13,3 | 257.0.0.0.0 |
| MBP14,1 | 196.0.0.0.0 |
| MBP14,2 | 196.0.0.0.0 |
| MBP14,3 | 196.0.0.0.0 |
| MBP9,1 | 227.0.0.0.0 |
| MM6,1 | 279.0.0.0.0 |
| MM7,1 | 243.0.0.0.0 |
| MP5,1 | 144.0.0.0.0 |
| MP6,1 | 131.0.0.0.0 |
No changes. You need the original SSD installed at its place to do the firmware upgrade.
What are the potential issues with _not_ having the latest boot ROM? I'm using the Angelshark carrier board and have already verified that I don't get an EFI updated with the original SSD installed in this board; removing it and reinstalling the original SSD would be a huge pain.
As is I'm running 10.14.5 with no problem with 127.0.0.0...
As is I'm running 10.14.5 with no problem with 127.0.0.0...
Without the new microcodes with side channel mitigations, you are vulnerable to all MDS attacks.
127.0.0.0.0 is from October 5 last year, Apple implemented a lot of security corrections in the firmware since then.
Hm. Can you provide a link to the description of the security changes in new Mac Pro 6,1 firmware? Apple's own page on MDS attacks only mentions disabling hyper-threading, while noting there are no known exploits using these attack vectors.
It does seem odd that Apple would make the application of firmware updates both invisible-- there's no notification that the update has been applied, or, in my case, not been applied-- as well as putting arbitrary restrictions on it, like "will only work with original Apple SSD."
It does seem odd that Apple would make the application of firmware updates both invisible-- there's no notification that the update has been applied, or, in my case, not been applied-- as well as putting arbitrary restrictions on it, like "will only work with original Apple SSD."
(I tried to update my previous reply, but the board won't let me, insisting that it's spam.)
Well, I went ahead and backed up the original SSD (which wasn't my boot drive), removed the Angelshark board, reinstalled the original SSD, ran the 10.14.5 installer, verified I now had bootrom 130.0.0.0, reinstalled the Angelshark board, restored the original content of the SSD. Nice way to kill a morning...
Well, I went ahead and backed up the original SSD (which wasn't my boot drive), removed the Angelshark board, reinstalled the original SSD, ran the 10.14.5 installer, verified I now had bootrom 130.0.0.0, reinstalled the Angelshark board, restored the original content of the SSD. Nice way to kill a morning...
I agree with your previous statement - this is an arbitrary (and absurd) restriction. Is there a good explanation as to why the OEM SSD is necessary?
And guess what? It looks like you'll have to do it all over again once 10.14.6 is released.
Has anyone update the firmware of a Samsung 970 PRO, without access to a windows machine?
edit 2:
found actually some useful instructions on this very forum:
https://forums.macrumors.com/threads/blade-ssds-nvme-ahci.2146725/page-35#post-27385884
edit: it was actually a 970 EVO, sorry for the spam, but it would be cool to actually know how to upgrade the fw without windows.
Has anyone update the firmware of a Samsung 970 PRO, without access to a windows machine?
Also I can't find the firmware on the Samsung website, there is one for the 960 PRO but not 970, I've seen on youtube videos a higher version of firmware that I've on mine tho.
https://www.samsung.com/semiconductor/minisite/ssd/download/tools/
I've this version of fw: 1B2QEXP7
edit 2:
found actually some useful instructions on this very forum:
https://forums.macrumors.com/threads/blade-ssds-nvme-ahci.2146725/page-35#post-27385884
edit: it was actually a 970 EVO, sorry for the spam, but it would be cool to actually know how to upgrade the fw without windows.
Has anyone update the firmware of a Samsung 970 PRO, without access to a windows machine?
Also I can't find the firmware on the Samsung website, there is one for the 960 PRO but not 970, I've seen on youtube videos a higher version of firmware that I've on mine tho.
https://www.samsung.com/semiconductor/minisite/ssd/download/tools/
I've this version of fw: 1B2QEXP7
Last edited:
This is what 'bootcamp' is for - those apps that don't exist on Apples but do run on Windows.
Add a Windows root, and install Magician. Like magic, all will be fixed.
I played with it briefly on my laptop. It's going to break a LOT of things: deprecated 32 bit apps aside, the way it bundles a read-only system volume and your data (on a separate volume) inside an APFS container, which the Finder makes appear as a single volume, just like always, is going to create problems with anything that relies on path names.
I'm sure it's all for the best, but the upgrade is going to be sufficiently nasty-- for me, at least-- that I'll wait until a stable release version is out.
Hi there (the following is a cross posting - hope that this is cool):
Wanted to ask the community for a double check on my plan of upgrade.
I have a Mac Pro 2013 (spec down below) and I'm attempting to install:
Intel 660p M.2 2280 2TB NVMe PCIe 3.0 x4 3D NAND Internal Solid State Drive (SSD) SSDPEKNW020T8X1
(Amazon Link: https://www.amazon.com/gp/product/B07GCLLKDC/ref=ppx_yo_dt_b_asin_title_o03_s01?ie=UTF8&psc=1)
Sintech NGFF M.2 nVME SSD Adapter Card for Upgrade MacBook Air(2013-2016 Year) and Mac PRO(Late 2013-2015 Year)
(Amazon Link: https://www.amazon.com/gp/product/B07FYY3H5F/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1)
My computer is running Mojave and I have a Mojave bootable USB stick in the wings waiting.
Do I need the Kapton tape or not? (My sintech appears Black - not the Green version).
My Computer specs:
Model Identifier: MacPro6,1
Processor Name: 6-Core Intel Xeon E5
Processor Speed: 3.5 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Hyper-Threading Technology: Enabled
Memory: 32 GB
Boot ROM Version: 130.0.0.0.0
SMC Version (system): 2.20f18
Illumination Version: 1.4a6
Thanks in advance for the input.
Wanted to ask the community for a double check on my plan of upgrade.
I have a Mac Pro 2013 (spec down below) and I'm attempting to install:
Intel 660p M.2 2280 2TB NVMe PCIe 3.0 x4 3D NAND Internal Solid State Drive (SSD) SSDPEKNW020T8X1
(Amazon Link: https://www.amazon.com/gp/product/B07GCLLKDC/ref=ppx_yo_dt_b_asin_title_o03_s01?ie=UTF8&psc=1)
Sintech NGFF M.2 nVME SSD Adapter Card for Upgrade MacBook Air(2013-2016 Year) and Mac PRO(Late 2013-2015 Year)
(Amazon Link: https://www.amazon.com/gp/product/B07FYY3H5F/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1)
My computer is running Mojave and I have a Mojave bootable USB stick in the wings waiting.
Do I need the Kapton tape or not? (My sintech appears Black - not the Green version).
My Computer specs:
Model Identifier: MacPro6,1
Processor Name: 6-Core Intel Xeon E5
Processor Speed: 3.5 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Hyper-Threading Technology: Enabled
Memory: 32 GB
Boot ROM Version: 130.0.0.0.0
SMC Version (system): 2.20f18
Illumination Version: 1.4a6
Thanks in advance for the input.
As far as I know, nobody's tried this SSD-- or any of the new QLC drives-- in a Mac Pro 6,1. I use Samsung Evo SSDs (in an Amfeltec Angelshark board) with no problem, and they provide about twice the sequential performance of the original Apple drive.
Let us know how it works. From the photo of the adapter you're using I don't think Kapton tape will be necessary.
Let us know how it works. From the photo of the adapter you're using I don't think Kapton tape will be necessary.
Hi there, wanting to report back. The install worked well, knock on wood. It has been a solid 48 hours - and the Mac Pro is fully restored with the new drive without issue....I'm using said computer to write this response.
I don't know why, but I put Kapton tape around the SinTech adaptor....Only when I inserted this into the computer, I realized that this was probably a complete waste as there's nothing to short against.
UPDATE: Was asked if SMART was supported - looking and it is NOT Supported.
I don't know why, but I put Kapton tape around the SinTech adaptor....Only when I inserted this into the computer, I realized that this was probably a complete waste as there's nothing to short against.
UPDATE: Was asked if SMART was supported - looking and it is NOT Supported.
Last edited:
10.16 DP3 has a new MP6,1 BootROM:
10.15 DP3 EFI Version table for non BridgeOS Macs:
(Almost all Catalina supported Macs had firmware upgrades, most got two versions over)
Code:
$IBIOSI$ MP61.88Z.F000.B00.1906132222
Copyright (c) 2005-2019 Apple Inc. All rights reserved.
Apple ROM Version
Model: MP61
EFI Version: 132.0.0.0.0
Built by: root@saumon
Date: Thu Jun 13 22:22:30 PDT 2019
Revision: 132 (B&I)
ROM Version: F000_B00
Build Type: Official Build, Release
Compiler: Apple clang version 3.0 (tags/Apple/clang-211.10.1) (based on LLVM 3.0svn)10.15 DP3 EFI Version table for non BridgeOS Macs:
(Almost all Catalina supported Macs had firmware upgrades, most got two versions over)
| Mac: | EFI version: |
|---|---|
| IM13,1 | 287.0.0.0.0 |
| IM14,1 | 139.0.0.0.0 |
| IM14,2 | 139.0.0.0.0 |
| IM14,3 | 139.0.0.0.0 |
| IM14,4 | 199.0.0.0.0 |
| IM15,1 | 230.0.0.0.0 |
| IM16,1 | 229.0.0.0.0 |
| IM16,2 | 229.0.0.0.0 |
| IM17,1 | 170.0.0.0.0 |
| IM18,1 | 175.0.0.0.0 |
| IM18,3 | 175.0.0.0.0 |
| IM19,1 | 1022.0.0.0.0 |
| MB10,1 | 178.0.0.0.0 |
| MB8,1 | 183.0.0.0.0 |
| MB9,1 | 184.0.0.0.0 |
| MBA5,1 | 259.0.0.0.0 |
| MBA6,1 | 117.0.0.0.0 |
| MBA7,1 | 188.0.0.0.0 |
| MBP10,1 | 257.0.0.0.0 |
| MBP10,2 | 280.0.0.0.0 |
| MBP11,1 | 156.0.0.0.0 |
| MBP11,2 | 156.0.0.0.0 |
| MBP11,4 | 194.0.0.0.0 |
| MBP12,1 | 186.0.0.0.0 |
| MBP13,1 | 236.0.0.0.0 |
| MBP13,2 | 259.0.0.0.0 |
| MBP13,3 | 259.0.0.0.0 |
| MBP14,1 | 198.0.0.0.0 |
| MBP14,2 | 198.0.0.0.0 |
| MBP14,3 | 198.0.0.0.0 |
| MBP9,1 | 228.0.0.0.0 |
| MM6,1 | 280.0.0.0.0 |
| MM7,1 | 244.0.0.0.0 |
| MP6,1 | 132.0.0.0.0 |
RE: I'm so sorry to ask, I just couldn't find them myself - could you show the link to these firmware updates. Thanks.
You most likely have to be a registered apple developer to receive the Catalina DP3 that includes the firmware update.
I haven't installed it yet since I'm not home. You can also wait for the public beta.