Dennis HilkLinux diagnosticsDE

Chipsets & PCIe

Intel client VMD controller

A table-backed Intel VMD controller profile that keeps the controller and downstream storage separate.

Editorial source review: Share public profileOpen in the identification tool
On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

The reviewed table maps 9a0b and 467f through VMD_FEATS_CLIENT. These are curated controller IDs, not a determination of the installed laptop or disk. The remapped hierarchy can make storage addresses differ from assumptions about a conventional motherboard root port.

Curated identifiers
pci 8086:9a0b pci 8086:467f

A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.

Driver & binding

The checked candidate is vmd, while downstream NVMe devices need their own driver binding. Changing a platform storage mode would change enumeration and potentially boot assumptions, so this explorer only records the existing hierarchy. Driver presence in the installed root and in the boot initramfs are separate observations.

  • vmd — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

No host payload established here

The checked VMD source defines controller features and a PCI hierarchy but no generic external firmware blob for these IDs. Platform firmware determines existing enumeration/storage policy. No host-loaded filename established here does not mean the motherboard or attached disks are firmware-free.

Inspect firmware packaging on your distribution

Read-only diagnostics

Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.

Read this function and its bound driver

lspci -nnk -s BDF

Replace BDF with the address of the Intel client VMD controller function. The summary normally needs no sudo. Numeric ID and the “driver in use” observation are stronger evidence than a descriptive name or candidate-module list.

Confirm the PCI driver owner

readlink /sys/bus/pci/devices/BDF/driver

Use a full domain:bus:slot.function BDF. This normally needs no sudo and only reads a symlink. The last component is the bound driver; no link records an unbound/absent function, not a missing software package.

Read the remapped PCI domains

lspci -D -t

This read-only tree normally needs no sudo. Retain domain numbers when locating controllers and downstream endpoints. A visible VMD parent is not the NVMe driver binding and is not proof that the root filesystem can be found during boot.

Read current-boot controller messages

journalctl -k -b --no-pager

Correlate VMD initialization and subsequent nvme/device discovery with the boot failure sequence. Journal access may require local group membership; failure to read it is not controller failure.

Limitations & related issues

The controller IDs do not establish RAID policy, an exact NVMe model or whether the boot image contains the required driver. No BIOS storage-mode change, unbinding, rescan or write is performed; a reported missing disk still needs its own device and boot evidence.

These guides are linked for relevant observations, not as known defects of every device in this family.

Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab

References

Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.