Overview & identity
The checked header identifies 10d3 as 82574L and the PCI table selects the 82574 board implementation. It does not identify the card manufacturer or its port count.
- Curated identifiers
pci 8086:10d3
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 source contains 82574-specific interrupt and PHY handling inside e1000e. Those implementation paths justify checking the exact kernel build and runtime messages, not applying a generic Intel workaround.
e1000e— 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:10d3] and Kernel driver in use. e1000e 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: e1000e.
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
A link flap, a transmit watchdog and a PCIe error are different observations. Compare their timestamps and the switch port before attributing every interruption to the controller model.
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/e1000e/hw.h
Reviewed upstream source
E1000_DEV_ID_82574L; line 28 - Upstream Linux: drivers/net/ethernet/intel/e1000e/netdev.c
Reviewed upstream source
PCI_VDEVICE(INTEL, E1000_DEV_ID_82574L); line 7877 - Upstream Linux: Documentation/networking/device_drivers/ethernet/intel/e1000e.rst
Project or distribution documentation
Intel Gigabit Linux driver; line 7