Which fixes? I only try to upstream dts for r4,so basicly not much difference to current openwrt state. Network stack needs some driver patches first before ethernet/switch dts can be added.
Must have been my wishful thinking then, I’d simply hoped that these commits after 2024-10-25 (plus the two UART/efuse ones by Miłecki) contained a good chunk of the fixes. I take it they don’t?
Honestly I’m probably too bad at using git to get a grasp of your WIP/pending changes, I haven’t found a way to get something useful out of github’s compare, either. Would be neat to get an actual list of commits/diffs to work through so as to apply manually to OpenWrt (at least after 6.12).
The patches i posted are mainly patches adding basic support,only slightly changed to get accepted for mainline. There is no network part yet,also no sfp. Maybe i add sfps in next round,but without full network part (which is much work) it will not work.
The mt76 patch is for a bootup issue. Not related to tx limitation.
Good morning, now I have this 10GB xgs-pon 8311 WAS-110, I have chosen the web version that has openwrt firmware and it is very easy to manage the data that you have to enter, the banana pi does not recognize it,
I can only guess that the sfp takes some time to get ready like most of gpon/xpon modules,so you will need a quirk to let kernel wait for module init and then access eeprom
Good afternoon and thank you very much @franco-w the truth is that I had it for more than 5 minutes and I couldn’t access it and it still didn’t detect it.
so I bought the converter and in 30 seconds, it accesses the banana pi.
I will continue using this method, until more people have this type of xgs-pon and it can be solved.
Good afternoon, I’ve been reading that link but I’m not clear on how to do it. If you have to solder, I’m not good at that, my pulse is a real disaster, if you have to touch the core, I have no idea how to do it.
That’s why, since it’s working great for me and from what I’ve read, the XGS-PON won’t be able to get any more out of the speeds it’s giving me, I’ll be stuck for now.
If someone finally implants the eeprom like mine, I always go through those threads in case there’s any progress, I’ll try the image out of curiosity.
But the price of the XGS-PON is too high to have to do any hardware correction, which is still not clear to me.
Hi,
I have a R4 with 2 sftp in eth1 and eth 2. Both are sftp from fs.com
[ 14.444465] sfp sfp2: module FS SFP-GE-BX rev A0 sn F2130219083 dc 220922
[ 14.473257] sfp sfp1: module FS SFP-GE-BX rev A0 sn G2340772262 dc 240122
Partner link of eth1 is also a fs.com module. eth2 is connection to ISP.
Every time I reboot the router, eth1 connects, eth2 wont connect. The log fills up with:
[ 284.064453] mtk_soc_eth 15100000.ethernet eth2: Link is Down
[ 284.072404] mtk_soc_eth 15100000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
The ethtool shows:
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: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
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: yes
So everything looks fine, link detected, partner adv. But no sigar.
After giving the next commands:
ethtool -s eth2 autoneg off
ethtool -s eth2 autoneg on
the sfp works without any problems.
I am running OpenWRT 24.10 trunk:
Linux bpir4 6.6.83 #0 SMP Tue Mar 25 08:52:55 2025 aarch64 GNU/Linux
In other threats I saw the suggestion ‘Force Link’, however this wont do the job.
After reboot eth2 is not connecting.
Yes, looks like it.
I dont think it is a BPIR4 problem, but a SFP problem.
I had the same issue when plugged-in an original FS switch.
I shall drop a question at FS.