SFP OEM SFP-2.5G-T kernel PHY?

Yes, I can test that. I’m using bpi-r3

Ok, but these days I’m quite busy, but within a couple of days I’ll have one ready. Will let you know here.

I’ve added the patch here:

Add another module, SFP-2.5G-T-R-RM (BPI store) · ericwoud/linux@f259247 (github.com)

1 Like

@Stat_headcrabed @clo :

New images are generated here:

https://www.woudstra.mywire.org/images

Or if you only want the kernel:

https://www.woudstra.mywire.org/repo/aarch64

linux-bpir64-git-6.7.9.bpi.xxxxxxxxxxx.aarch64.pkg.tar.xz file. It is an archlinux package, but also a simple archive you can extract the linux image and modules from.

1 Like

Seems working correctly:

[  259.254593] sfp sfp-2: module OEM              SFP-2.5G-T-R-RM  rev 1.0  sn 2401050130       dc 240105  
[  259.303890] hwmon hwmon1: temp1_input not attached to any thermal zone
[  264.200000] mt7530-mdio mdio-bus:1f lan4: switched to phy/2500base-x link mode
[  265.369926] mt7530-mdio mdio-bus:1f lan4: PHY [i2c:sfp-2:11] driver [RTL8221B-VB-CG 2.5Gbps PHY (C45)] (irq=POLL)
[  272.759918] mt7530-mdio mdio-bus:1f lan4: No phy led trigger registered for speed(100)
[  272.860118] mt7530-mdio mdio-bus:1f lan4: Link is Up - 100Mbps/Full - flow control rx/tx
[  272.868285] brlan: port 6(lan4) entered blocking state
[  272.873418] brlan: port 6(lan4) entered forwarding state
[  296.599435] mt7530-mdio mdio-bus:1f lan4: Link is Down
[  296.604701] brlan: port 6(lan4) entered disabled state
[  315.159919] mt7530-mdio mdio-bus:1f lan4: No phy led trigger registered for speed(1000)
[  315.260114] mt7530-mdio mdio-bus:1f lan4: Link is Up - 1Gbps/Full - flow control rx/tx
[  315.268103] brlan: port 6(lan4) entered blocking state
[  315.273235] brlan: port 6(lan4) entered forwarding state
[  347.007322] mt7530-mdio mdio-bus:1f lan4: Link is Down
[  347.012707] brlan: port 6(lan4) entered disabled state
[  366.119920] mt7530-mdio mdio-bus:1f lan4: No phy led trigger registered for speed(1000)
[  366.220108] mt7530-mdio mdio-bus:1f lan4: Link is Up - 1Gbps/Full - flow control rx/tx
[  366.228097] brlan: port 6(lan4) entered blocking state
[  366.233232] brlan: port 6(lan4) entered forwarding state
[  413.478011] mt7530-mdio mdio-bus:1f lan4: Link is Down
[  413.639945] brlan: port 6(lan4) entered disabled state
[  417.559916] mt7530-mdio mdio-bus:1f lan4: No phy led trigger registered for speed(2500)
[  417.670114] mt7530-mdio mdio-bus:1f lan4: Link is Up - 2.5Gbps/Full - flow control rx/tx
[  417.678274] brlan: port 6(lan4) entered blocking state
[  417.683410] brlan: port 6(lan4) entered forwarding state

And if you want a tested-by:

Tested-by: Shengyu Qu <[email protected]>

Thanks!

Could you try changing advertisement to 1000mbps and lower 0x28 I believe, with ethtool?

Check if interface switching also works…

Well your image didn’t include ethtool… and I’m not sure how to configure to use pppoe to connect to the internet :joy:

Connect wan port to your router.

pacman -Sy ethtool

Where wan is either wan port or eth1, depending which image you used.

cat /etc/systems/network/*.nft
1 Like

Well, the problem is your image doesn’t include ppp package so that I cannot connect to internet…

You do not need to replace your router. You can cascade the routers.

Connect the wan port of the R3 to a lan port of your active router that uses PPP to connect to the internet.

Image bpir3-sdmmc-rtnosfp.img has wan port as wan, bpir3-sdmmc-rt.img has eth1 sfp port as wan.

It uses DHCP to get an IP from your active router and then the R3 will have internet access. Just like connecting any other client on a lan port

Sadly I have only one router😞 I also tried to create a hotspot using my phone, but it cannot connect to my phone for unknown reason (hostapd already stopped and wlan interface is manually enabled )

One option is to use the fhroot functionality of my buildR64arch build script. On pc/laptop with sdcatd inserted

git clone https://github.com/ericwoud/buildR64arch.git
cd buildR64arch
./build.sh -a
./build.sh

@ericwoud Btw, on some 10gbaset sfp+ module’s fixup implementation, connector type is also corrected, maybe you could also add that to your fixup?

I actually removed it after experiencing trouble with it at some time… On the newer patch set.

1 Like

Emmm… What happens when you set that to rj45?

I believe this affects validating the connection between phy and mac.

I do set the port to TP in the patch-set, but it needs to be done here:

net: phy: realtek: add rtl822x_c45_get_features() to set supported ports · ericwoud/linux@066e06b (github.com)

The patch-set from my stable branch is not the latest. The latest is branch net-next-realtek-phy-v4. I’ll see if I can update it in the rolling-stable branch, when I have some time for it.

…I cannot connect to your ftp server…

:: Synchronizing package databases...
 ericwoud                                                          32.1 KiB  18.9 KiB/s 00:02 [######################################################] 100%
 core                                                             229.1 KiB  70.6 KiB/s 00:03 [######################################################] 100%
 extra                                                              9.2 MiB  1440 KiB/s 00:07 [######################################################] 100%
 alarm                                                             57.3 KiB   129 KiB/s 00:00 [######################################################] 100%
 aur                                                               10.2 KiB  5.76 KiB/s 00:02 [######################################################] 100%
error: failed retrieving file 'ericwoud.db' from ftp.woudstra.mywire.org : Failed to connect to ftp.woudstra.mywire.org port 21 after 10002 ms: Timeout was reached
error: target not found: peekpoke-git
error: target not found: ssh-fix-reboot
error: target not found: hostapd-launch
headcrab@debian:~/code/buildR64arch$ ping ftp.woudstra.mywire.org
PING ftp.woudstra.mywire.org (128.242.250.155) 56(84) bytes of data.
^C
--- ftp.woudstra.mywire.org ping statistics ---
13 packets transmitted, 0 received, 100% packet loss, time 12281ms

I’m just trying it now, it seems to be ok. Maybe my internet provider had trouble, but this doesn’t happen very often.

Edit:

It would seem I have been moved my Ip number

Reply from 84.106.48.54

It has been resolved automatically by dhclient

I’ll make sure ethtool and i2c-tools are included in the next image…

1 Like

@clo @Stat_headcrabed

I’ve created a fresh archlinuxarm image for the R3, it includes the latest patch-set for the module.

https://www.woudstra.mywire.org/images/

Or you could just use the old image and update the linux-bpir64-git package.

If you could both test your module with this patchset also, that would be great!

This patch-set is very different from the one you tried before, but the result should be the same. It is this version I’ll be trying to upstream soon again.

New image still works nicely. And speed manual override by ethtool also works:

[root@bpir3 ~]# ethtool -s lan4 speed 100 duplex full autoneg on

[  359.425270] mt7530-mdio mdio-bus:1f lan4: Link is Down
[  359.649321] brlan: port 6(lan4) entered disabled state
[  363.639281] mt7530-mdio mdio-bus:1f lan4: No phy led trigger registered for speed(100)
[  379.079286] mt7530-mdio mdio-bus:1f lan4: No phy led trigger registered for speed(100)
[  379.079642] mt7530-mdio mdio-bus:1f lan4: Link is Up - 100Mbps/Full - flow control rx/tx
[  379.095369] brlan: port 6(lan4) entered blocking state
[  379.100511] brlan: port 6(lan4) entered forwarding state