Maybe a miscommunication or false terminologyThis don't exist at all, only SATA M.2 to plain SATA.
BTW, SFF8639 adapters work because the U2 SAS cable also has the PCIe signals.
Maybe a miscommunication or false terminologyThis don't exist at all, only SATA M.2 to plain SATA.
BTW, SFF8639 adapters work because the U2 SAS cable also has the PCIe signals.
This is for a B-key (SATA) M.2 blade. You can't even insert a M-key (PCIe AHCI/NVMe) blade.Maybe a miscommunication or false terminology
It says for both actually in the product description, but if not this card then another. Point being they exist. But I have since learned that that's not a solution either, regardless. It's just a bit misleading when everyone's talking about Nvme's when it could be any hard drive - the issue persists regardless.This is for a B-key (SATA) M.2 blade. You can't even insert a M-key (PCIe AHCI/NVMe) blade.
Sorry, but they don't. How do you convert PCIe signals from the M.2 blade to the Mac Pro SATA interface?!?It says for both actually in the product description, but if not this card then another. Point being they exist. But I have since learned that that's not a solution either, regardless. It's just a bit misleading when everyone's talking about Nvme's when it could be any hard drive - the issue persists regardless.
Nope, 11.2.3 is still the most recent MP5,1 compatible Big Sur release.Hi. Does anyone know if with the launch of BS 11.4, is it now safe to update the Mac Pro 5,1 to 11.4 or should we stay on BS 11.2.3 for now?
greetz,
Willem
So what about 2.5" SATA SSDs? But like I said according to my research, it doesn't seem to make a difference, either.Sorry, but they don't. How do you convert PCIe signals from the M.2 blade to the Mac Pro SATA interface?!?
M.2 is a format, this format have two main standards, M-key and B-key. M-key blades require a M.2 PCIe interface, B-key blades require a SATA M.2 interface. You can't use a B-key adapter with a M-key blade, they don't even connect.
You can only use a format adaptor to connect a B-key M.2 blade to the Mac Pro SATA ports.
Works fine up to 11.2.3, for details of the problem read the first post below:So what about 2.5" SATA SSDs? But like I said according to my research, it doesn't seem to make a difference, either.
It doesn't matter. The issue is still there.So what about 2.5" SATA SSDs?
It depends on the DSDT/SSDT of the iMac. But it certainly can be modified.This would be really interesting to use VBIOS versions expecting an DP connected internal LCD on LVDS based systems like the iMac10,1 and before. Can this really work out? Or do I only see what I would like to be true here?
Thanks ! I was following the "Big Sur on unsupported Macs" thread but since I have a MP5,1, I was pointed to this threadNope, 11.2.3 is still the most recent MP5,1 compatible Big Sur release.
Read the first post here:
![]()
Mac OS 11.3 has broken support for older Mac Pros
macOS Big Sur 11.3 Beta 3 has broken Mac Pro's early-2009 to mid-2012 ability to boot reliably into macOS. It's still possible to boot 11.3/11.4, but the process requires multiple restarts and a connection has been made between PCIe devices, especially storage related devices and USB controller...forums.macrumors.com
Any type of storage will have issues with macOS 11.3+. Latest functional version is 11.2.3. Does this help?So what about 2.5" SATA SSDs?
There exists USB to NVMe Bridge Chips (such as the JMicron JMS583). Some of the enclosures that can do this also support SATA devices using a USB to SATA bridge.How do you convert PCIe signals from the M.2 blade to the Mac Pro SATA interface?!?
M.2 is a format, this format have two main standards, M-key and B-key. M-key blades require a M.2 PCIe interface, B-key blades require a SATA M.2 interface. You can't use a B-key adapter with a M-key blade, they don't even connect.
You can only use a format adaptor to connect a B-key M.2 blade to the Mac Pro SATA ports.
I'm still on Mojave without opencore. So does this mean there is no way for me to upgrade to Big Sur and opencore?It doesn't matter. The issue is still there.
This has being asked multiple times on the last page. No, you can't use any Big Sur release after 11.2.3 reliably with a MP5,1, including this week beta of 11.5.I'm still on Mojave without opencore. So does this mean there is no way for me to upgrade to Big Sur and opencore?
If you want the last version, it is not possible. You can download 11.2.3, which works with OpenCore from apple via link here: https://mrmacintosh.com/macos-big-sur-full-installer-database-download-directly-from-apple/ That said, I would wait to the problem has been resolved and stay on Mojave or Catalina to get security updates.I'm still on Mojave without opencore. So does this mean there is no way for me to upgrade to Big Sur and opencore?
Use this setting for SIP:***************
SOLVED
***************
It was my own mistake. WinClone 9 was not able to unmount the internal partition from that boot SSD and so it shows up that error. I boot up from an external SSD and all was fine restored.
Hello together,
I am looking for some advice. I'm running the OpenCore 0.6.9 Package from Martin Lo with macos Catalina 10.15.7 Build 19H1030. I also running Windows 10 Pro 64 Bit latest Updates as UEFI Install via OpenCore BootManager - all fine. Today I made a Image via WinClone 9 because I want to move Windows to the internal drive Samsung EVO 860 SSD 1 TB via OWC Accelsior S.
I made a 200 GB Partition in the backyard of the disk (see picture disk.jpg) as I had this structure before on the other disk. Now I try to restore the Windows Image from WinClone 9 to the disk and then I got an error which I did not expect because it shoud not be shown - but see for yourself:
SIP is disabled
View attachment 1782600
WinClone 9 Restore Error
View attachment 1782601
Disk Structure
View attachment 1782602
Any hint is very welcome...
<key>csr-active-config</key>
<data>fwgAAA==</data>
nvram csr-active-config
csr-active-config %7f%08%00%00
If you want the last version, it is not possible. You can download 11.2.3, which works with OpenCore from apple via link here: https://mrmacintosh.com/macos-big-sur-full-installer-database-download-directly-from-apple/ That said, I would wait to the problem has been resolved and stay on Mojave or Catalina to get security updates.
Yes, you will also miss the security fixes applied by Apple on latest versions.So I basically can install with older version of Big Sur.
Alex will via Clone to NVMe for a boot drive work for 11.2.3Works fine up to 11.2.3, for details of the problem read the first post below:
![]()
Mac OS 11.3 has broken support for older Mac Pros
macOS Big Sur 11.3 Beta 3 has broken Mac Pro's early-2009 to mid-2012 ability to boot reliably into macOS. It's still possible to boot 11.3/11.4, but the process requires multiple restarts and a connection has been made between PCIe devices, especially storage related devices and USB controller...forums.macrumors.com
I didn't understood what you really asking above.Alex will via Clone to NVMe for a boot drive work for 11.2.3
Or use Clonezilla.It´s able to clone everything. I use it in drives with a windows or Linux partitions.I didn't understood what you really asking above.
If you want to clone your 11.2.3 boot disk using an app that support BigSur cloning like the current version of CCC, yes. Don't matter if it's a NVMe/AHCI/SATA/USB.