On Sun, Feb 28, 2021, at 9:44 AM, Doug H. wrote:
And you did ask for ethtool output while working:
I just realized that the ethtool output from the Pi side had only the single 100Full as advertised. It still needed a reboot after some tests to lock them both to 100Full. I ended up rolling that back but the Pi still needed a reboot to fully change, so the post reboot output is:
$ s ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbag Wake-on: d Current message level: 0x00000007 (7) drv probe link Link detected: yes
Since this is a change, I will go ahead and reboot to make sure the issue is still there and that the new kludge/fix still works.