Hi I’ve recently got the clearfog Octeon Base.
I’ve managed to successfully install ubuntu following the build script. and successfully got network connectivity of both eth ports. however i’m struggling with the SFP.
I notice in dmesg i get unknown/supported module. It is a cisco Ethernet 1Gb module.
"
[ 508.372850] sfp sfp-eth@0: module CISCO-AVAGO ABCU-5710RZ-CS4 rev sn AGM141021W7 dc 100311
[ 508.372863] sfp sfp-eth@0: Unknown/unsupported extended compliance code: 0x01
[ 508.615842] mvpp2 f2000000.ethernet eth0: PHY [i2c:sfp-eth@0:16] driver [Marvell 88E1111] (irq=POLL)
"
I can configure the eth0 port with IP, however ip link shows the interface as down.
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 2048
link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.50/24 brd 192.168.1.255 scope global eth0
valid_lft forever preferred_lft forever
I have found ixgbe related content regarding intel drivers and unsupported modules, but nothing regarding marvell.
Has anyone had success with getting cisco SFP working with marvell drivers.
hi,
did you try to enable the interface with
ip link set dev eth0 up
and can you provide the results of:
ethtool eth0
ethtool -m eth0
dmesg | grep -E 'mvpp|sfp|eth|arvell'
There are multiple points of failure. Maybe your sfp module is unsupported or your device tree file is broken.
hi thanks for the reply,
Yes i had tried to enable the interface using “ip link set dev eth0 up”, unfortunately it remains down. I do think it is related to the SFP support, as i say in first message, i’ve found similar threads relating to intel chipset where it seems possible to allow unsupported sfps, but i can’t find anything similar relating to marvell.
I’ve tried another SFP (same make unfortunately) still the same.
“How To Fix The Unsupported SFP+ Issue in Linux ? - ServerAdminz Blog | Who Knows Server Better Than Adminz?”
Thanks again - all help is appreciated.
the results of the commands:
ethtool eth0
root@localhost:~# ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 1000baseT/Full
1000baseX/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 1000baseT/Full
1000baseX/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 22
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Link detected: no
ethtool -m eth0
Identifier : 0x03 (SFP)
Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID)
Connector : 0x00 (unknown or unspecified)
Transceiver codes : 0x00 0x00 0x00 0x08 0x00 0x00 0x00 0x00 0x01
Transceiver type : Ethernet: 1000BASE-T
Transceiver type : Extended: 100G AOC or 25GAUI C2M AOC with worst BER of 5x10^(-5)
Encoding : 0x01 (8B/10B)
BR, Nominal : 1300MBd
Rate identifier : 0x00 (unspecified)
Length (SMF,km) : 0km
Length (SMF) : 0m
Length (50um) : 0m
Length (62.5um) : 0m
Length (Copper) : 100m
Length (OM3) : 0m
Laser wavelength : 16652nm
Vendor name : CISCO-AVAGO
Vendor OUI : 00:17:6a
Vendor PN : ABCU-5710RZ-CS4
Vendor rev :
Option values : 0x00 0x10
Option : TX_DISABLE implemented
BR margin, max : 0%
BR margin, min : 0%
Vendor SN : AGM141021WC
Date code : 100312
dmesg | grep -E ‘mvpp|sfp|eth|arvell’
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] Kernel command line: console=ttyS0,115200 earlycon=uart8250,mmio32,0xf0512000 root=/dev/mmcblk1p1 rootwait r1
[ 0.632087] mv_xor_v2 f0400000.xor: Marvell Version 2 XOR driver
[ 0.638516] mv_xor_v2 f0420000.xor: Marvell Version 2 XOR driver
[ 0.644988] mv_xor_v2 f0440000.xor: Marvell Version 2 XOR driver
[ 0.651427] mv_xor_v2 f0460000.xor: Marvell Version 2 XOR driver
[ 0.658045] mv_xor_v2 f26a0000.xor: Marvell Version 2 XOR driver
[ 0.664448] mv_xor_v2 f26c0000.xor: Marvell Version 2 XOR driver
[ 0.940722] mvpp2 f2000000.ethernet: using 8 per-cpu buffers
[ 2.869265] sfp sfp-eth@0: Host maximum power 2.0W
[ 2.876688] mvpp2 f2000000.ethernet: using 8 per-cpu buffers
[ 2.902101] mvpp2 f2000000.ethernet eth0: Using firmware node mac address 00:51:82:11:22:00
[ 2.913185] mvpp2 f2000000.ethernet eth1: Using firmware node mac address 00:51:82:11:22:01
[ 2.923059] mvpp2 f2000000.ethernet eth2: Using firmware node mac address 00:51:82:11:22:02
[ 6.940819] br0: port 1(eth1) entered blocking state
[ 6.940838] br0: port 1(eth1) entered disabled state
[ 6.940966] device eth1 entered promiscuous mode
[ 7.009125] mvpp2 f2000000.ethernet eth1: PHY [f212a200.mdio-mii:01] driver [Marvell 88E1510] (irq=POLL)
[ 7.010312] mvpp2 f2000000.ethernet eth1: configuring for inband/sgmii link mode
[ 7.012064] br0: port 2(eth2) entered blocking state
[ 7.012081] br0: port 2(eth2) entered disabled state
[ 7.012187] device eth2 entered promiscuous mode
[ 7.077074] mvpp2 f2000000.ethernet eth2: PHY [f212a200.mdio-mii:00] driver [Marvell 88E1510] (irq=POLL)
[ 7.077128] mvpp2 f2000000.ethernet eth2: configuring for phy/rgmii-id link mode
[ 7.081592] br0: port 2(eth2) entered blocking state
[ 7.081602] br0: port 2(eth2) entered forwarding state
[ 7.081629] br0: port 1(eth1) entered blocking state
[ 7.081634] br0: port 1(eth1) entered forwarding state
[ 7.964336] br0: port 1(eth1) entered disabled state
[ 7.964445] br0: port 2(eth2) entered disabled state
[ 344.423631] sfp sfp-eth@0: module CISCO-AVAGO ABCU-5710RZ-CS4 rev sn AGM141021WC dc 100312
[ 344.423645] sfp sfp-eth@0: Unknown/unsupported extended compliance code: 0x01
[ 4411.292854] mvpp2 f2000000.ethernet eth2: Link is Up - 100Mbps/Full - flow control rx/tx
[ 4411.292881] br0: port 2(eth2) entered blocking state
[ 4411.292887] br0: port 2(eth2) entered forwarding state
[ 4493.212107] mvpp2 f2000000.ethernet eth2: Link is Down
[ 4493.212156] br0: port 2(eth2) entered disabled state
[ 6095.432780] mvpp2 f2000000.ethernet eth0: configuring for inband/10gbase-r link mode
[ 6095.546971] mvpp2 f2000000.ethernet eth0: switched to inband/sgmii link mode
[ 6095.676858] mvpp2 f2000000.ethernet eth0: PHY [i2c:sfp-eth@0:16] driver [Marvell 88E1111] (irq=POLL)
[ 6399.147760] sfp sfp-eth@0: module removed
[ 6400.613861] sfp sfp-eth@0: module CISCO-AVAGO ABCU-5710RZ-CS4 rev sn AGM141021WC dc 100312
[ 6400.613872] sfp sfp-eth@0: Unknown/unsupported extended compliance code: 0x01
[ 6400.856858] mvpp2 f2000000.ethernet eth0: PHY [i2c:sfp-eth@0:16] driver [Marvell 88E1111] (irq=POLL)
Hi unfortunately I’ve still not had much luck with this.
Has anybody else used SFP’s with the board and marvell drivers and know which are compatible?
I assume it must have been tested, so there are known makes that are supported SFP’s?
kind regards
Just as an update and FYI - I decided to purchase an alternative SFP. It seems to work and be compatible, so another SFP to add to the list.
Ubiquiti UF-RJ45-1G - F-RJ45-1G U-Fiber RJ45 SFP Transceiver Module
It’s a pity Marvell don’t have the option like intel to allow “unknown” SFP’s. I’m also surprised CISCO is “unknown” (well actually i shouldn’t be that surprised considering it’s CISCO).
This is not a Marvell issue. These are agreed upon decisions for SFP+ hotplugging using the phylink layer in the mainline network maintainers team. We have already worked on various patches to try to support SFP modules that have incorrect eeproms, some even have non-standard eeprom access. These include not just NICs, but also GPON, and VDSL modules. The truth is that without properly programmed eeproms even generic quirks are inconsistent with their success. For this reason mainline has decided to focus on only supporting properly programmed eeproms.
Glad you were able to get your new SFP module working.