Overview & identity
The device constant names 100e as 82540EM. Subsystem IDs, the enclosing PCI topology and whether the system is virtual still matter when identifying an actual board.
- Curated identifiers
pci 8086:100e
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 e1000 PCI table includes 100e. e1000e is a different driver family and is not the candidate established by this table; use the bound-driver field before diagnosing missing modules.
e1000— kernel driver/module candidate
Firmware
No host payload established here
No host-loaded firmware filename was established for this profile in the reviewed driver sources. EEPROM/NVM on the adapter is separate from files installed in the operating system.
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.
Check the PCI function and bound driver
lspci -nnk -s BDFReplace BDF with the domain:bus:device.function address. Look for [8086:100e] and Kernel driver in use. e1000 in Kernel modules is only a candidate, not proof of binding.
Identify the network interface driver
ethtool -i INTERFACEReplace INTERFACE with the real interface name. Driver and bus-info connect this interface to its device. A displayed firmware-version is adapter information; it does not prove a file was loaded. Candidate: e1000.
Compare supported modes with the current link
ethtool INTERFACESupported/advertised link modes describe capability or negotiation offers. Speed, Duplex and Link detected describe the current link, not measured throughput. An unsupported query is a limitation of the interface/driver.
Separate PCIe transport from Ethernet speed
sudo lspci -vv -s BDFElevated access may be needed. Root can expose the full PCI configuration. If PCIe capabilities exist, compare LnkCap with LnkSta: maximum and negotiated PCIe speed/width are different from Ethernet speed. Legacy PCI or virtual functions may omit these fields.
Limitations & related issues
Guest-reported gigabit capability can reflect an emulated adapter and says nothing about host uplink throughput. A live link also does not establish DHCP, routing or DNS operation.
These guides are linked for relevant observations, not as known defects of every device in this family.
- Ethernet has no carrier or repeatedly loses link · First documented next step
- Network transmit queue watchdog or hardware hang · First documented next step
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.
- Upstream Linux: drivers/net/ethernet/intel/e1000/e1000_main.c
Reviewed upstream source
INTEL_E1000_ETHERNET_DEVICE(0x100E); line 30 - Upstream Linux: drivers/net/ethernet/intel/e1000/e1000_hw.h
Reviewed upstream source
E1000_DEV_ID_82540EM ; line 389 - Upstream Linux: Documentation/networking/device_drivers/ethernet/intel/e1000.rst
Project or distribution documentation
ethtool interface; line 434