Dennis HilkLinux diagnosticsDE

Chipsets & PCIe

Intel Sunrise Point MEI function

A checked Management Engine host interface: driver binding does not reveal every firmware client or management feature.

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 source constant MEI_SPT is 0x9d3a and the mei_me table uses it for the Sunrise Point interface. The PCI pair identifies the host interface, not an exact motherboard or an enabled remote-management service. Different firmware clients share the underlying interface.

Curated identifiers
pci 8086:9d3a

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

mei_me is the checked PCI candidate, with the MEI core exposing /dev/meiX interfaces for client communication. Client availability depends on firmware and policy. A bound driver or visible device node does not prove that Intel AMT is provisioned, that every client exists, or that a userspace account may access it.

  • mei_me — kernel driver/module candidate
  • mei — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Device/revision dependent

MEI communicates with firmware clients, as documented by the kernel API. That is not a universal external firmware image request for the PCI host interface. The exact installed platform firmware and exposed client set are not established by the device ID.

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 MEI 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 registered MEI interface objects

ls -l /sys/class/mei

This normally needs no sudo and only lists existing sysfs objects. It shows registered MEI interfaces, not the availability of all firmware features or permission to use a client. Correlate the object path with BDF on a multi-interface system.

Read current-boot controller messages

journalctl -k -b --no-pager

Read mei_me initialization and reset messages before attributing a client application failure to the PCI host. Journal access may require local group membership; failure to read it is not controller failure.

Limitations & related issues

This profile performs no client connection, provisioning or firmware update. A device-node permission error and a host-interface initialization failure are different findings. The checked family does not establish the installed Management Engine firmware version.

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.