V1.0-210702 is R4’s firmware version? If so, that’s not mainline kernel but SDK. Have you tried firmware here?
No, sorry for not describing in more detail. This is the firmware dfp-34x-2c2, the firmware version for bpi-r4 is the latest, snapshot, I also tried 21.02 from sinovoip.
So both version of openwrt firmware won’t work on r4 + sfp? Can you post dmesg message that generated after module plugged in?
Okay, tomorrow I’ll start new attempts to run sfp dfp-34x-2c2 and throw the dmseg logs here.
Please bear in mind that Luleey module is not the same as the Anddear module. The one from the Andear shop has the yt8821 on it, and so for we have not been successful in communicatiing with the phy on the module.
Thank you very much.
Just to add, regular 1.25gbit SFP works for me on the latest master.
Can I find that here?:
No it’s some specific ones that ISPs in my country provide, this is the non-complete list:
I tested 2 different brands and they get detected at correct speeds, and PPPoE works out of box after.
Wake on Lan does not work if I connect the PC to Banana SFP 10GBe RJ-45, but it works through regular LAN ports.
Wakeonlan outgoing (to wake pc from r4) or the opposite direction?
From RPi (Wi-Fi) → banana R4 → PC.
Is your sfp bridged (port from rpi and pc)?
Wakeon lan only works in same lan-segment (ethernet broadcast).
But independ from this,please create separate thread with this specific problem
Today i checked dfp-34x-2c2 on bpi-r4 on latest snaphot firmware, no connect. Logs -
root@OpenWrt:~# ethtool -m eth2
Identifier : 0x03 (SFP)
Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID)
Connector : 0x01 (SC)
Transceiver codes : 0x00 0x00 0x00 0x02 0x22 0x00 0x01 0x00 0x00
Transceiver type : Ethernet: 1000BASE-LX
Transceiver type : FC: intermediate distance (I)
Transceiver type : FC: Longwave laser (LC)
Transceiver type : FC: Single Mode (SM)
Encoding : 0x01 (8B/10B)
BR, Nominal : 1300MBd
Rate identifier : 0x00 (unspecified)
Length (SMF,km) : 20km
Length (SMF) : 20000m
Length (50um) : 0m
Length (62.5um) : 0m
Length (Copper) : 0m
Length (OM3) : 0m
Laser wavelength : 1310nm
Vendor name : OEM
Vendor OUI : 00:00:00
Vendor PN : STICK
Vendor rev :
Option values : 0x00 0x1a
Option : RX_LOS implemented
Option : TX_FAULT implemented
Option : TX_DISABLE implemented
BR margin, max : 0%
BR margin, min : 0%
Vendor SN : XPON23021675
Date code : 230222
root@OpenWrt:~# ethtool eth2
Settings for eth2:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseX/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 1000baseX/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: Unknown!
Duplex: Unknown! (255)
Auto-negotiation: on
Port: FIBRE
PHYAD: 0
Transceiver: internal
Current message level: 0x000000ff (255)
drv probe link timer ifdown ifup rx_err tx_err
Link detected: no
root@OpenWrt:~# dmesg | grep sfp
[ 10.844756] sfp sfp1: Host maximum power 3.0W
[ 10.849634] sfp sfp2: Host maximum power 3.0W
[ 11.162515] sfp sfp1: module OEM STICK rev sn XPON23021675 dc 230222
root@OpenWrt:~#
And check on BPI-R4-BE1350-WIFI_MP4_0-SDK-20240620 firmware, connect OK. Logs -
root@OpenWrt:~# dmesg | grep sfp
[ 54.163536] sfp sfp@1: SM: enter empty:down:down event dev_up
[ 54.169273] sfp sfp@1: SM: exit empty:up:down
[ 54.263514] sfp sfp@0: SM: enter present:down:down event dev_up
[ 54.269438] sfp sfp@0: tx disable 1 -> 0
[ 54.273391] sfp sfp@0: SM: exit present:up:wait
[ 54.329449] sfp sfp@0: SM: enter present:up:wait event timeout
[ 54.349677] sfp sfp@0: probing phy device through the [MDIO_I2C_NONE] protocol
[ 54.362633] sfp sfp@0: SM: exit present:up:link_up
root@OpenWrt:~# dmesg | grep sfp
[ 54.163536] sfp sfp@1: SM: enter empty:down:down event dev_up
[ 54.169273] sfp sfp@1: SM: exit empty:up:down
[ 54.263514] sfp sfp@0: SM: enter present:down:down event dev_up
[ 54.269438] sfp sfp@0: tx disable 1 -> 0
[ 54.273391] sfp sfp@0: SM: exit present:up:wait
[ 54.329449] sfp sfp@0: SM: enter present:up:wait event timeout
[ 54.349677] sfp sfp@0: probing phy device through the [MDIO_I2C_NONE] protocol
[ 54.362633] sfp sfp@0: SM: exit present:up:link_up
root@OpenWrt:~# ethtool eth2
Settings for eth2:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseX/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 1000baseX/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 1000baseX/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Current message level: 0x000000ff (255)
drv probe link timer ifdown ifup rx_err tx_err
Link detected: yes
root@OpenWrt:~# ethtool -m eth2
Identifier : 0x03 (SFP)
Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID)
Connector : 0x01 (SC)
Transceiver codes : 0x00 0x00 0x00 0x02 0x22 0x00 0x01 0x00 0x00
Transceiver type : Ethernet: 1000BASE-LX
Transceiver type : FC: intermediate distance (I)
Transceiver type : FC: Longwave laser (LC)
Transceiver type : FC: Single Mode (SM)
Encoding : 0x01 (8B/10B)
BR, Nominal : 1300MBd
Rate identifier : 0x00 (unspecified)
Length (SMF,km) : 20km
Length (SMF) : 20000m
Length (50um) : 0m
Length (62.5um) : 0m
Length (Copper) : 0m
Length (OM3) : 0m
Laser wavelength : 1310nm
Vendor name : OEM
Vendor OUI : 00:00:00
Vendor PN : STICK
Vendor rev :
Option values : 0x00 0x1a
Option : RX_LOS implemented
Option : TX_FAULT implemented
Option : TX_DISABLE implemented
BR margin, max : 0%
BR margin, min : 0%
Vendor SN : XPON23021675
Date code : 230222
root@OpenWrt:~#
What i need to create working connection on latest snapshot, maybe i need some patch?
Diff both firmwares, dmesg and ethtool, then apply proper patches on sfp.c according to your board, it’s not an issue with your module, just missing snapshot detection.
Good afternoon. Thanks for the answer. What do you mean by going to the corresponding patch? I see the difference that the snapshot image cannot determine the Speed option - Speed: Unknown!, and also cannot determine the Duplex option - Duplex: Unknown! (255). Should I somehow change them or set them manually?
You are probably missing this patch:
That seems not the issue. The stick works correctly at 1gbps mode.
So there’s nothing wrong in dmesg… I’ll do some tests on my r3 later to check if it also exists on r3 + snapshot. Also @frank-w did you see anything might possibly related to this issue?
Thanks for the answer. Maybe need to force bpi-r4 to work at 1000mb, and also change duplex to full duplex, or also disable autoneg?