Overview & identity
1521 is named I350_COPPER in the reviewed header. Different I350 media identities and virtual functions must not be inferred from this physical-function pair.
- Curated identifiers
pci 8086:1521
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 igb table maps this identifier to the shared board_82575 implementation. The source separately handles I350 RSS/SR-IOV interaction; a driver-family name does not reveal enabled virtualization features.
igb— 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:1521] and Kernel driver in use. igb 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: igb.
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
Inspect each port and its interface independently. A virtual function can inherit link information from its physical function, and physical-card features do not automatically apply to a guest.
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/igb/e1000_hw.h
Reviewed upstream source
E1000_DEV_ID_I350_COPPER; line 38 - Upstream Linux: drivers/net/ethernet/intel/igb/igb_main.c
Reviewed upstream source
PCI_VDEVICE(INTEL, E1000_DEV_ID_I350_COPPER); line 73 - Upstream Linux: Documentation/networking/device_drivers/ethernet/intel/igb.rst
Project or distribution documentation
support for SR-IOV; line 49