I don't think anything changed, so, yeah.
Actually it has changed, you can now boot windows from startup disk with SIP enabled. So yeah it changed...
I don't think anything changed, so, yeah.
Actually it has changed, you can now boot windows from startup disk with SIP enabled. So yeah it changed...
Oh, nice! At least something. Did you look at updates for Windows BootCamp boot manager?
First of all I would like to thank very much @tsialex for the very good help and support he gave me preparing the new firmware for my MAC PRO Mid 2010 with the latest updates, version 138.0.0.0.0, with the NVMe boot and also the MAC PRO hardware descriptor from Base_20 (MID 2010) to the mid-2012 Base_21 one, and sent it to me just for burn it in my firmware chip.
This morning I was able to record the new firmware and it worked perfectly.
I installed the HIGHPoint SSD7101A card with 4 NVMe blades Samsung 960 EVO 500G to start RAID0 performance tests with 2, 3 and 4 blades, as well as performance with only 1 NVMe without RAID.
I did not get the performance I expected, and I think this is due to the highPoint's ability to manage the PCIe 2.0 slot (the HighPoint card is PCIe 3.0).
Results in MAC OSX 10.13.6 using RAID0 created by MAC OSX DISKUTIL. Slot 2
With 1 NVMe I achieved the following results:
Read: 2609.7
Write: 1925.8
With 2 NVMe in RAID0 I got the following results:
Read: 4301.3
Write: 3305.2
With 3 NVMe in RAID0 I got the following results:
Read: 4703.8
Write: 3846.1
With 4 NVMe in RAID0 I got the following results:
Read: 4793.5
Write: 3646.0
I was able also to boot from NVMe in both version 10.13 and version 10.14
NOTE:
If I create the RAID through the proprietary software of the HighPoint controller the performance gets a little better, but with the proprietary software installed I do not have visibility of the NVMe blade by MAC OSX only from RAID0.
More specifically .. my idea is to use 1 blade to boot and the other 3 as RAID0, in case I use the highpoint proprietary software I can not see the NVMe blade that I would use to boot and with that I can not install MAC OSX, so all tests was made using distil for RAID0 creation.
I would like to enphasize that without the very good support received from @tsialex will be impossible for me to change my firmware to the lates version.
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 3,46 GHz
Number of Processors: 2
Total Number of Cores: 12
L2 Cache (per Core): 256 KB
L3 Cache (per Processor): 12 MB
Memory: 128 GB
Boot ROM Version: 138.0.0.0.0
SMC Version (system): 1.39f11
SMC Version (processor tray): 1.39f11
you know any fix for why I get this message?View attachment 781020
I'll check the windows side in a little while. I doubt anything hit there...
UPDATE:
Okay, I checked. Once you boot into windows you are stuck there until you do a PRAM reset. Of course if you are using BootRunner, or a similar app., there's no problem. Just use their boot selector as an alternative to "Startup Disk" and you don't need to go through that hassle.
@marcoscc has a Highpoint 7101a and I reconstructed his BootROM, 138.0.0.0.0 with NVMe EFI module from MP61.0124.B00.hello sir, sorry bother you with an old topic, but i need to know your evo 960 boot mac pro or not? it's not ahci, but nvme, if you did boot with it, which pcie adapter do you use please? thank you so much.
you know any fix for why I get this message?
All PCIe drives are external to the Mac Pro firmware. Upgrade to 138.0.0.0.0, enable trim, then test again.Hi! first of all, I would like to thank everybody for all the information you guys posted in this and other posts. You guys are awesome.
I have a couple of questions, I got a Lycom and a Samsung 970, followed the GDoc tutorial and made the NVMe as a bootable drive. I haven't installed this new flash yet(138). Everything works flawlessly, excepting a couple of details:
1. I can't make the R/W speed past 800 MB. I've installed the PCI in the slot 3, so I'm not sure what I'm doing wrong there.
2. and not that important, my mac shows the NVMe as an external drive.
Does anybody have had these issues? thanks in advance!
All PCIe drives are external to the Mac Pro firmware. Upgrade to 138.0.0.0.0, enable trim, then test again.
I don't think anything changed, so, yeah.
I have to investigate that, didn’t have time to look at this, but I think it’s possible.Hey tsialex, do you believe FileVault could be enabled via a terminal command for those of us that have GPU's which support boot screens?
2. and not that important, my mac shows the NVMe as an external drive.
hello sir, sorry bother you with an old topic, but i need to know your evo 960 boot mac pro or not? it's not ahci, but nvme, if you did boot with it, which pcie adapter do you use please? thank you so much.
I have to investigate that, didn’t have time to look at this, but I think it’s possible.
Hey tsialex, do you believe FileVault could be enabled via a terminal command for those of us that have GPU's which support boot screens?
I haven’t tested this in Mojave, but this may be of use to you.
http://www.mactricksandtips.com/2014/01/check-enable-and-disable-filevault-from-terminal.html
This too could be disabled in Mojave, you’ll just have to test.
You get the message because Bootcamp Assistant isn’t supported on the cMP with updated firmware/macOS.
I'm confused by this exchange. I trashed my old Bootcamp Win 7 partition 3 months ago. Does this mean I can't install Win 10 using Bootcamp Assistant anymore? I just started up Bootcamp Assistant (from HS) and didn't get any message saying it couldn't be used with 2010 Mac Pro anymore. Can you clarify please?
Actually it has changed, you can now boot windows from startup disk with SIP enabled. So yeah it changed...
View attachment 781014
Legacy Windows?
If yes, then AFAIK, this startup disk selector always work regardless SIP status.
I'm confused by this exchange. I trashed my old Bootcamp Win 7 partition 3 months ago. Does this mean I can't install Win 10 using Bootcamp Assistant anymore? I just started up Bootcamp Assistant (from HS) and didn't get any message saying it couldn't be used with 2010 Mac Pro anymore. Can you clarify please?
No, it wasn’t working here with SIP enabled with non-EFI GPU.
Bootcamp Assistant is not required at the beginning for cMP users, and not the best way for us as well (even if it can work).
Since we can install multiple hard drives. It's so much better to install an independent hard drive that dedicated for Windows.
Simply install that hard drive (better to remove all other hard drives as well just to avoid accidentally pick the wrong drive to format during installation). Hold "C" to boot from the Windows 10 installation disc. Then flow the on screen instruction to install Windows natively.
[doublepost=1536806530][/doublepost]
Storage, that should be SIP / EFI GPU independent, but can be affected by those NTFS software.
Are you running Mojave with firmware 138.0.0.0.0 with SIP enabled and a non-EFI GPU?
All PCIe drives are external to the Mac Pro firmware. Upgrade to 138.0.0.0.0, enable trim, then test again.