Yes, I carefully did that each time. The DosDude1 patcher must have partially worked, to inject the ‘apfsjumpstart’ code (which I assume on the 3,1 wasn’t included in the last official firmware update), but then is causing an error each time for me and not injecting the apfs.ffs as well, which it’s supposed to do.Did you put the mac in program mode by holding the power button down from a cold start until you hear the strange tone? Then run the patcher?
Yes, I made sure SIP was disabled. Sadly, it’s not ‘usually’ working for me for some reason. Thanks for replying, though.It usually works, try with an older System and sip off.
I made quite a few 3.1 with APFS Patcher.Yes, I made sure SIP was disabled. Sadly, it’s not ‘usually’ working for me for some reason. Thanks for replying, though.
I’d already applied that Apple firmware patch a few weeks ago. I’m glad the DosDude1 patcher worked for you several times. I so wish it had for me too.I made quite a few 3.1 with APFS Patcher.
maybe you miss a Firmware Update?
Mac Pro EFI Firmware Update 1.3 - Apple Support
This update fixes several issues to improve the stability of Mac Pro (Early 2008) computers.support.apple.com
While I wait to see if anyone can upload a working or alternative apfs.ffs file I can patch my 3,1 ROM with, I'm going to try the DriverXXXX non-ROM-modification route. I've added an apfs.efi to an EFI folder and followed the instructions in post #86 eg. setbootvar Driver0080 1 "apfs.efi" /Volumes/EFI*/*_bay2/../drivers/apfs.efi, then setdriverorder etc.I’d already applied that Apple firmware patch a few weeks ago. I’m glad the DosDude1 patcher worked for you several times. I so wish it had for me too.
While I wait to see if anyone can upload a working or alternative apfs.ffs file I can patch my 3,1 ROM with, I'm going to try the DriverXXXX non-ROM-modification route. I've added an apfs.efi to an EFI folder and followed the instructions in post #86 eg. setbootvar Driver0080 1 "apfs.efi" /Volumes/EFI*/*_bay2/../drivers/apfs.efi, then setdriverorder etc.
Subsequently, I also found an 'ApfsDriverLoader-64.efi' file which is supposed to be successful (over the apfs.efi file?). If I want to load this with 'setbootvar' and not the apfs.efi I've already set, rather than renaming it (not sure if this will screw things up), is there a Terminal command to delete or overwrite a boot variation string for a specific Driver ('Driver0080' etc) already set?
I've Googled all sorts of 'delete setbootvar', 'clear setbootvar' etc and nothing Mac-centric is found. Is it as simple as resetting PRAM 3-4 times? But wouldn't setbootvar be set in NVRAM, so it's there permanently...until you do something opposite to remove the instructions? Any suggestions would be welcome.
You can overwrite Driver0080 or you can make a Driver0081 and update DriverOrder to include only Driver0081. I've got a dozen Driver#### variables, but my DriverOrder includes only a couple that I'm currently using.While I wait to see if anyone can upload a working or alternative apfs.ffs file I can patch my 3,1 ROM with, I'm going to try the DriverXXXX non-ROM-modification route. I've added an apfs.efi to an EFI folder and followed the instructions in post #86 eg. setbootvar Driver0080 1 "apfs.efi" /Volumes/EFI*/*_bay2/../drivers/apfs.efi, then setdriverorder etc.
Subsequently, I also found an 'ApfsDriverLoader-64.efi' file which is supposed to be successful (over the apfs.efi file?). If I want to load this with 'setbootvar' and not the apfs.efi I've already set, rather than renaming it (not sure if this will screw things up), is there a Terminal command to delete or overwrite a boot variation string for a specific Driver ('Driver0080' etc) already set?
I've Googled all sorts of 'delete setbootvar', 'clear setbootvar' etc and nothing Mac-centric is found. Is it as simple as resetting PRAM 3-4 times? But wouldn't setbootvar be set in NVRAM, so it's there permanently...until you do something opposite to remove the instructions? Any suggestions would be welcome.
sudo nvram -d $efiguid:Driver0080
There are four approaches to get NVMe booting. Three of them are without BootROM modification.
PCIe NVMe (with built-in OPROM):
- Samsung 950 Pro - Bootable
- Intel 750 Series- Bootable
Samsung 950 Pro is not compatible with Macs when installed directly to a PCIe slot (i.e. not via a Thunderbolt adapter/connection), after POST the OpROM totally locks the Mac, happens even with MP3,1 and MP4,1 default firmwares and MP5,1 before or after 140.0.0.0.0, but I never tested with a MP1,1/2,1. This is long know and reported by me personally on the PCIe Blade thread.There might be a fifth way. Some early NVMe drives came with EFI drivers in their option ROM:
The source is this page about getting HP servers to boot from NVMe.
Re: NVMe PCIe SSD boot support in Z820
I spent considerable time researching my PCIE NVME SSD to boot on my Z620 so hopefully I can clear up the mis-information posted by folks claiming it cannot boot in NVME as it certainly can, however, only on specific drives. They are correct in stating HP does not support the configuration and...h30434.www3.hp.com
The issue is also mentioned here:
Use NVMe on boards that does not have native support...
We all know that ever since P67 we can put a NVMe drive onto the motherboard, and the OS will see it as a storage device. However in order to boot from NVMe you generally need a newer motherboard with UEFI-level NVMe support... Or do you? Do you have any solution to boot from NVMe on an older mac...linustechtips.com
There seems to be a confusion. The HP thread is about booting in UEFI mode. The Linus thread assumes booting in CSM legacy mode. Maybe the ROM has both UEFI and BIOS rom images.
I tried to see if anyone had successfully used a Samsung 950 Pro in a unflashed Mac Pro. All the posts are from before the time macOS gained NVMe drivers, or confuse SM951 with Samsung 950 Pro. Only the later one has the option ROM.
P.S. - I ordered a 128 GB Apple SSUBX drive and a 12+16 pin to PCIe x4 adapter for my Mac Pro 1.1. The SSUBX uses the AHCI protocol, so it should be bootable on a Mac Pro 1,1 and work in El Capitan.
P.P.S - What on earth was "SATA Express"?
SATA Express meets the '09 Mac Pro - Bootable NGFF PCIE SSD
** SPRING 2015 Update ** ================================= The PCIe flash marketplace for the cMP continues to expand with the addition of multiple SSD's compatible with the cMP. April 2015 Pricing $300 - Lycom DT-120 M.2 Adapter with Samsung 256GB SM951. (1500MB/s) - fast at a lower cost. $500...forums.macrumors.com
I know that HighPoint (not to be confused with Hewlett-Packard) has some NVMe cards with firmware that may make them bootable in computers that don't have an NVMe driver. It was already mentioned in this thread #101There might be a fifth way. Some early NVMe drives came with EFI drivers in their option ROM:
The source is this page about getting HP servers to boot from NVMe.
Re: NVMe PCIe SSD boot support in Z820
I spent considerable time researching my PCIE NVME SSD to boot on my Z620 so hopefully I can clear up the mis-information posted by folks claiming it cannot boot in NVME as it certainly can, however, only on specific drives. They are correct in stating HP does not support the configuration and...h30434.www3.hp.com
The issue is also mentioned here:
Use NVMe on boards that does not have native support...
We all know that ever since P67 we can put a NVMe drive onto the motherboard, and the OS will see it as a storage device. However in order to boot from NVMe you generally need a newer motherboard with UEFI-level NVMe support... Or do you? Do you have any solution to boot from NVMe on an older mac...linustechtips.com
There seems to be a confusion. The HP thread is about booting in UEFI mode. The Linus thread assumes booting in CSM legacy mode. Maybe the ROM has both UEFI and BIOS rom images.
I tried to see if anyone had successfully used a Samsung 950 Pro in a unflashed Mac Pro. All the posts are from before the time macOS gained NVMe drivers, or confuse SM951 with Samsung 950 Pro. Only the later one has the option ROM.
P.S. - I ordered a 128 GB Apple SSUBX drive and a 12+16 pin to PCIe x4 adapter for my Mac Pro 1.1. The SSUBX uses the AHCI protocol, so it should be bootable on a Mac Pro 1,1 and work in El Capitan.
That page seems to be using the term SATA Express incorrectly. It's supposed to be a connector that can do either two SATA or one PCIe. In the case of PCIe, the device can be AHCI or NVMe and has two PCIe lanes (since each SATA connector only has one SATA lane)P.P.S - What on earth was "SATA Express"?
SATA Express meets the '09 Mac Pro - Bootable NGFF PCIE SSD
** SPRING 2015 Update ** ================================= The PCIe flash marketplace for the cMP continues to expand with the addition of multiple SSD's compatible with the cMP. April 2015 Pricing $300 - Lycom DT-120 M.2 Adapter with Samsung 256GB SM951. (1500MB/s) - fast at a lower cost. $500...forums.macrumors.com
Added mention of FixPCIeLinkRate.efi to first post. It has a dual purpose of showing the pci device tree like pcitree.sh does.
I'm currently attempting to add some Thunderbolt stuff to it as a third feature.
I can't explain the results.I have recently purchased an Ableconn PEXM2-130 to which I added two SK hynix Gold P31 1TB NVMe SSDs, and have formatted one of them APFS for use in my Mac partitions, and the other NTFS for when I boot into Windows through Boot Camp.
I plan to post this setup in more detail on the PCIe SSDs - NVMe & AHCI thread, but before I do, I have a question for @joevt here:
I have used the EFI driver at #106 with RefindPlus to set the PCIe slot speeds to their maximums. This doubled my read speeds on the Mac side, but only slightly increased my write speeds.
(Mac, before and after EFI driver)
View attachment 2004761
Conversely, read speeds only slightly increased in Windows, but write speeds doubled!
(Windows, before and after EFI driver)
View attachment 2004762
Any ideas as to why this may be happening? ?♂️
I can't explain the results.
I think you should start by standardizing your tests. Stick with the default 5 tries of 1 GiB each.
Does HFS+ change the results?
You can also try ATTO Disk Benchmark to see how the performance changes with different transfer sizes.
@joevt ... are you actually still looking to instead separate the Link Rate fix by itself so that those that just want this can have a simple lean driver?Added mention of FixPCIeLinkRate.efi to first post. It has a dual purpose of showing the pci device tree like pcitree.sh does.
I'm currently attempting to add some Thunderbolt stuff to it as a third feature.
Yes. I've been working on other stuff though. I'll work on this tomorrow.@joevt ... are you actually still looking to instead separate the Link Rate fix by itself so that those that just want this can have a simple lean driver?
Ok, check here: https://github.com/joevt/joevtApps@joevt ... are you actually still looking to instead separate the Link Rate fix by itself so that those that just want this can have a simple lean driver?
Do you know if the Mac Pro supports booting from a PCIe SSD out of the box?
Would flashing a modified BootROM help?
Thanks!