CodingBox Q&A Ask question

Questions tagged “intel-x520-da2”

5 questions
15 30 50 per page
1vote
2comments
88views

Three Intel-branded AFBR-703SDZ-IN2 SFP+ failures in three months between an Aruba S2500 and an X520-DA2

In a home lab with an Aruba S2500 PoE switch and an Intel X520-DA2, three of thirteen cheaply bought Intel AFBR-703SDZ-IN2 SFP+ modules (around 15 USD each) failed within three months: links dropped with dark activity LEDs, two on the switch side and one on the NIC side. Warm and cold reboots…

2votes
1 answer
86views

Synology RS3614xs+ with an Intel X520-DA2: allow_unsupported_sfp ignored until set in the DSM-specific modules.conf keys

A Synology RS3614xs+ with a supported Intel X520-DA2 rejected the wrongly ordered SFP+ modules as unsupported. Putting options ixgbe allowunsupportedsfp=1 into /etc/modules.conf had no effcet, and even when the kernel log showed ixgbe: allowunsupportedsfp Enabled the driver still reported failed to…

3votes
1 answer
228views

Fixing no carrier with Flypro 10GBASE-T SFP+ on a Dell-branded X520-DA2 under Debian and FreeBSD/OPNsense

A Dell-branded Intel X520-DA2 with Flypro 10GBASE-T SFP+ modules showed no carrier (or no interface at all) on Debian and on FreeBSD-based OPNsense because the card rejects unapproved modules. The post collects the per-OS fixes and the permanent EEPROM approach. Hardware involved: Dell-branded…

1vote
1 answer
310views

XCP-ng with X520-DA2 and Finisar SFP+: allow_unsupported_sfp must be set per port on the kernel command line

An XCP-ng host with an Intel X520-DA2 and Finisar SFP+ transceivers logged failed to load because an unsupported SFP+ or QSFP module type was detected. insmod with allowunsupportedsfp=1 failed with Unknown symbol in module; options ixgbe allowunsupportedsfp=1 in /etc/modprobe.d/ixgbe-options.conf…

1vote
1 answer
143views

Proxmox VE 6: X520-DA2 fails to load because an unsupported SFP+ or QSFP module type was detected

On Proxmox VE 6.0 (kernel 5.0.18-1-pve, ixgbe 5.1.0-k) an Intel X520-DA2 exposed ens1f0/ens1f1 but any inserted thirrd-party SFP+ module produced failed to load because an unsupported SFP+ or QSFP module type was detected, and the driver had to be reloaded to detect module changes at all. Hardware…