Jump to content

NanoPi Neo 2 LTS: net I/O speed tests, etc.


esbeeb

Recommended Posts

Another weird quirk that I wanted to mention: about 1 boot in 5, the Ethernet will autonegotiate at only 100Mbit, not 1000 Mbit, as it should.  Rebooting is all it takes to get it to renegotiate properly.  I've changed the GbE cable a couple of times, as well as using different ports on my Fritzbox WiFi router.  Nothing helped.  So I'm pretty sure it's the fault of the NanoPi Neo2 itself.

 

I would catch this problem when I noticed that none of my OMV file transfers would go faster than 12 MB/sec, when I knew I could normally get 12-40MB/sec.

 

The ethtool command would indeed verify that the Ethernet got negotiated at only 100Mbit.  After a reboot, I would check again, and it would be 1000Mbit.

Link to comment
Share on other sites

Does grepping your kernel log for "NIC Link is" reveal an unusual number of entries?

 

I experienced odd behaviour when connecting to/through a FritzBox (using multiple devices over Ethernet) a while back.  When devices connected to any port set to "Green Mode" the link would seem to drop frequently when idle.  The link would come up again when traffic arrived at either end, but a bunch of security protocols timed-out in the process and some applications failed in strange ways.

 

Saturating the link would result in a transfer stall followed by the link going down and then coming back up in 100Mbps mode.  Continued saturation would even cause it to go down and come back up at 10Mbps... but at that point data transfer stopped.  Software resetting of the link failed to restore it to 1Gbps — it required the power cycling of either the FritzBox or the device.

 

For some utterly unfathomable reason, the link was least stable on Port 4.  Port 3 was half as unstable.  Port 2 was about 1/10th as unstable.  Port 1 was completely stable.  However, since all local traffic had to use at least two LAN ports I ended up with instability regardless of whether I was on the sending or receiving end.

 

Forcing all four LAN ports into "Power Mode" — regardless of whether they needed to be there or not — solved the problem.

Edited by tim0
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines