Laptop network-adapter lifecycle reference

Adapter and interface are different objects

The adapter is a hardware or virtual function represented through a bus and driver relationship. The network interface is a host-software abstraction with identity, properties, and state. One adapter can have multiple representations over time or alongside virtual layers.

Laptop power adds another boundary

Internal adapters can participate in sleep, wake, radio, and platform-power relationships. Firmware and embedded controllers can contribute to those transitions, while a host driver exposes the adapter to the network stack. Power state is not interchangeable with package state.

Packets and link events have owners

A driver exchanges commands, data, and link events with an adapter. The network stack interprets packets above that boundary, while a wireless or wired medium supplies link conditions below it. A lifecycle page should state which layer owns each observation.

Package succession is recorded

Installation metadata, version fields, hardware identifiers, interface state, and runtime status can describe different points in the adapter’s lifecycle. A retained package record does not establish that it is active, and an interface state does not identify every package component.

Questions and answers