Overview & identity
10fb is named 82599_SFP in the driver header. The pair does not determine whether an actual board has one or two ports, nor the identity of a fitted transceiver.
- Curated identifiers
pci 8086:10fb
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
ixgbe maps this entry to board_82599. The driver documentation describes 82599 optics restrictions and back-to-back speed considerations; transceiver acceptance is distinct from PCI support.
ixgbe— 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:10fb] and Kernel driver in use. ixgbe 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: ixgbe.
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 supported PCI ID does not guarantee that arbitrary optical modules or DAC cables are accepted. PCIe LnkSta describes the host-side connection and must not be read as the Ethernet link rate.
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/ixgbe/ixgbe_type.h
Reviewed upstream source
IXGBE_DEV_ID_82599_SFP ; line 31 - Upstream Linux: drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
Reviewed upstream source
PCI_VDEVICE(INTEL, IXGBE_DEV_ID_82599_SFP); line 106 - Upstream Linux: Documentation/networking/device_drivers/ethernet/intel/ixgbe.rst
Project or distribution documentation
82599-BASED ADAPTERS; line 38