Overview & identity
16d7 is the BCM57414 table entry. The same driver contains separate NPAR identities, so this exact physical-function pair must not be treated as a complete description of every partition.
- Curated identifiers
pci 14e4:16d7
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
bnxt_en supplies Ethernet operation; additional RDMA support is a separate layer. A loaded core network driver does not demonstrate that a desired RDMA configuration exists or is working.
bnxt_en— kernel driver/module candidate
Firmware
Device/revision dependent
This profile does not establish an external firmware filename. Adapter firmware reported by the driver, its API compatibility and OEM provisioning are distinct from installing a generic OS firmware bundle.
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 [14e4:16d7] and Kernel driver in use. bnxt_en 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: bnxt_en.
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
Do not map every Broadcom link failure to tg3 firmware advice. Firmware/API negotiation, port partitions and the media path need the exact bnxt_en startup messages and adapter context.
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/broadcom/bnxt/bnxt.c
Reviewed upstream source
PCI_VDEVICE(BROADCOM, 0x16d7); line 168 - Upstream Linux: drivers/net/ethernet/broadcom/Kconfig
Reviewed upstream source
config BNXT; line 207