FS 2.5GBase-T SFP not working with Turris Omnia

[ju2wheels]

Hi all, im trying to get the FS 2.5GBase-T SFP working with the Turris Omnia but I am not having any luck. I was hoping it would have been as simple as plugging it in and maybe changing the WAN interface in LUCI to use the new device instead of the eth2 interface but I cannot even see a new device show up when I plug it in.

All I see is the following lines in dmesg:

[  561.558926] mvneta f1034000.ethernet eth2: Link is Down
[  561.642127] mvneta f1034000.ethernet eth2: PHY [f1072004.mdio-mii:01] driver [Marvell 88E1510] (irq=POLL)
[  561.642410] mvneta f1034000.ethernet eth2: configuring for phy/sgmii link mode
[  561.792159] mvneta f1034000.ethernet eth2: PHY [f1072004.mdio-mii:01] driver [Marvell 88E1510] (irq=POLL)
[  561.792380] mvneta f1034000.ethernet eth2: configuring for phy/sgmii link mode
[  565.991230] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
[  565.991255] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
[  626.324210] mvneta f1034000.ethernet eth2: Link is Down
[  626.501905] mvneta f1034000.ethernet eth2: PHY [f1072004.mdio-mii:01] driver [Marvell 88E1510] (irq=POLL)
[  626.502164] mvneta f1034000.ethernet eth2: configuring for phy/sgmii link mode

Googling the Marvell driver it is for a transceiver so im confused why it would be showing up as eth2 when WAN port is already eth2.

Sorry if my terminology is a bit off, I know my around a server but not low level networking setup like this.

Is it possible to get this working, is there anything else I should check (ifconfig -a returns no new interfaces when the SFP is connected)? Alternatively is there any other supported SFP transceiver I could get that would basically allow me to connect the 2.5G port of my cable modem to get the faster speeds?

Thanks,

[AreYouLoco]

Your SFP wont show up as another interface. Its either SFP or copper for WAN (eth2) and you have to switch a file in boot for it to use SFP. Please insert SFP reboot and show the output of:

dmesg | grep -E "sfp|eth2"

To see if your SFP is detected

[ju2wheels]

Theres nothing new except basically what I posted yesterday:

# dmesg | grep -E "sfp|eth2"
[    1.805446] mvneta f1034000.ethernet eth2: Using hardware mac address d8:58:d7:00:34:81
[   20.327502] mvneta f1034000.ethernet eth2: PHY [f1072004.mdio-mii:01] driver [Marvell 88E1510] (irq=POLL)
[   20.327703] mvneta f1034000.ethernet eth2: configuring for phy/sgmii link mode
[   24.486870] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
[   24.486895] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready

The only thing that happens is the WAN port loses its IP while the SFP is connected after reboot.

[ju2wheels]

If I could get the Turris Rtrom01-rtsf-10g SFP+ adapter would this be likely to work with the Turris Omnia? If so what are the other steps that would be required to set it up (since you mention theres another config file somewhere)?

[vcunat]

Just nit: when you repeatedly write “WLAN”, you mean the wired “WAN”, right? (“WLAN” is normally used for wireless)

[ju2wheels]

Yea typo on my part, my bad, I was referring to wired WAN everywhere here. Corrected.

[tac2]

Seek and you will find

Using the Turris RTROM01-RTSF-10G SFP with Turris Omnia

Dear Members, I recently bought a Turris RTROM01-RTSF-10G type SFP for use with my Turris Omnia, because I read that it was supported out of the box on my Omnia. I currently have TurrisOS 5.3.10 installed. When I plug the SFP into the slot and unplug the Ethernet cable from the WAN port and plug it into the SFP (the device on the other side is 1G capable currently), and reboot Omnia, ethtool will say that there is no link on eth2 and that the port type is still MII. Then if I unplug the Ethe…

Not shure if the step with linking /boot/dtb is needed now in TOS 6 though

(I have no omnia so I can not test)

[ju2wheels]

OK so it should work, now ill have to see where I can get one that will actually ship it to the US.

I am on the latest 6.x AFAIK, ill check that later and see what it has in there for device tree stuff.

Thanks

[ju2wheels]

OK I finally got this working. This FS Generic Compatible 2.5GBASE-T SFP Copper RJ-45 module does indeed work: https://www.fs.com/products/139650.html

I dont know if it would have done it automatically or not but based on the comment above, I relinked the default device tree symlink and then rebooted and it worked without further changes to setup after that:

cd /boot/
rm dtb
ln -s armada-385-turris-omnia-sfp.dtb dtb
reboot

After reboot:

# dmesg | grep -i -e sfp -e eth2
[    1.823696] mvneta f1034000.ethernet eth2: Using hardware mac address d8:58:d7:00:34:81
[   11.812748] sfp sfp: Host maximum power 3.0W
[   12.137957] sfp sfp: module FS               SFP-2.5G-T       rev 1.0  sn G2230090032      dc 220711  
[   12.147352] mvneta f1034000.ethernet eth2: switched to inband/2500base-x link mode
[   20.454622] mvneta f1034000.ethernet eth2: configuring for inband/2500base-x link mode
[   24.735381] mvneta f1034000.ethernet eth2: Link is Up - 2.5Gbps/Full - flow control rx/tx
[   24.735412] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready

This was using TurrisOS 6.2.3 .