4

After poring over available Z170 motherboards I have been become confused when it comes to NVMe compatibility. Can you please clarify if my assumptions are correct or wildly misguided.

Consider motherboard X. It has an M.2 slot which supports "SSD and PCIe (3.0 x4)" mode. It has no U.2 connector, and there is no mention anywhere in the specs or manual of NVMe. Assumption: NVMe support is not guaranteed but it's a BIOS issue rather than a hardware drawback, i.e. it could be possible with a BIOS revision.

Consider motherboard Y. It has an M.2 slot which supports "SSD and PCIe (3.0 x4)" mode. It does have a U.2 connector but there is no mention, as above, in the specs or manual of NVMe. Assumption: NVMe support is implicit at least via the U.2 connector because you can't get U.2 drives that aren't NVMe. It follows that NVMe is supported for M.2 drives, too, akin the the assumption below.

Consider motherboard Z. It has an M.2 slot which supports "SSD and PCIe (3.0 x4)" mode. It does have a U.2 connector, and states in the advertising blurb that you can use NVMe drives via the U.2 connector, but fails to say anything about the M.2. Assumption: M.2 NVMe devices are equally compatible, due to the fact the the M.2 socket uses the same PCIe channels as the U.2.

The Samsung SM951 is available as AHCI and NVMe - both use PCIe which perhaps is what fuels my misunderstanding. In the above examples, X, Y and Z are based on the specifications of three real Z170 motherboards from the same manufacturer; I am relying on the consistency of their wording to get my head round this, which may or may not be a good idea.

CharlieHanson
  • 188

1 Answers1

11

NVMe support on the motherboard is only about the firmware (BIOS/UEFI). That's because NVMe is not a physical connector or electronic transmission protocol like PCI Express. Instead, it is a way to talk to the SSD controller, much like AHCI is way to talk to the SATA HBA (or backwards-compatible PCIe SSDs).

It is also only about booting. After that, the operating system takes over.

With M.2/U.2, there are two types of connections:

  • SATA (supported by U.2 ports and M.2 slots keyed B or M)
  • PCIe (supported by U.2 ports and M.2 slots keyed A, B, E or M)

A SATA M.2/U.2 SSD interfaces with an external (not on the SSD but on the mainboard) SATA HBA (Host Bus Adapter) using the SATA protocol. The operating system typically talks to the SATA HBA using AHCI. Everything works the same as when connecting a SATA drive to a SATA port. With U.2, you are even using a regular SATA cable.

A PCIe M.2/U.2 SSD on the other hand comes in two varieties. It has an equivalent to the SATA HBA built-in. The host can talk to this controller using one of two standard:

  • AHCI (none available with U.2, but still possible)
  • NVMe

An AHCI controller has limited performance. However, it offers the best compatibility because virtually all (but very old) firmware already supports AHCI. As such, you can boot from such SSDs no problem. (Provided the SSD itself isn't somehow limited in that regard.)

The NVMe specification is more suitable for non-rotational drives like SSDs and offers better performance by reducing overhead and whatnot. However, until relatively recently, mainboard firmware did not support this standard and could not boot from NVMe SSDs. You could still access them from your operating system, provided appropriate drivers were available.

Wikipedia has a great image on this topic:

asdf
(Just ignore that it's apparently only about SATA Express/U.2, M.2 is mostly equivalent in this case.)

tl;dr: All NVMe SSDs use a PCI Express connection. As such, they appear the same to the BIOS, whether connected via U.2, M.2 or a full-size PCI Express slot.

However, having an M.2 or U.2 slot does not guarantee in any way that the firmware can boot from NVMe storage devices.

The manufacturer could provide a NVMe-boot-capable firmware later, yes.

user219095
  • 65,551