Jump to content

Gigabit on Banana Pi


gvfarns

Recommended Posts

I know Banana pi had issues in the past connecting at gigabit speeds.  I thought that was a fixed problem, though.  I did a fresh Jessie server install today and it still connects at 100 megabit.  Is there a user action that must be taken?

 

According to http://linux-sunxi.org/LeMaker_Banana_Pi the GMAC wasn't supported in the community kernel but should be in later kernels.  Is this still an issue?  How does one set GMAC_TX_DELAY to 3?  Is that a config file thing or a patch that needs to be applied? 

 

Are other Banana Pi owners just living with 100 megabit speeds?

 

A bit of system information:

~> uname -a
Linux bananapi 4.6.3-sunxi #7 SMP Tue Jul 5 16:23:41 CEST 2016 armv7l GNU/Linux
~> dmesg | grep Link
[   22.504469] sun7i-dwmac 1c50000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
~> sudo ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes:   10baseT/Half 10baseT/Full 
                       100baseT/Half 100baseT/Full 
                       1000baseT/Half 1000baseT/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
                       100baseT/Half 100baseT/Full 
                       1000baseT/Half 1000baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
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
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: external
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x0000003f (63)
      drv probe link timer ifdown ifup
Link detected: yes
 

 

Link to comment
Share on other sites

I did a fresh Jessie server install today

 

Using mainline 4.6.3 kernel -- so no need to dig into history what happened years ago with legacy kernel :)

 

We know that a few A20 boards were affected by connection issues (some, especially the Lime2 using an RT8211CL PHY, needed fixes that broke Ethernet on other A20 boards): See https://groups.google.com/forum/#!searchin/linux-sunxi/stmmac$204.6/linux-sunxi/e99UH22Utic/H-5um50VOwAJ for details.

 

According to your ethtool output it's a simple negotiation problem (that might also be caused by broken cables -- GbE uses all 4 cable pairs while Fast Ethernet just 2) so I would check that first:

Link partner advertised link modes:  10baseT/Half 10baseT/Full 
                                    100baseT/Half 100baseT/Full 
Link to comment
Share on other sites

Thanks so much for the idea.  The device is only about a foot from a relatively new switch and using a new cat6 cable, but I'll swap it out when I get home and see.  Another thing to note is that the mii-tool output disagrees with ethtool's assertion that gigabit is being advertised.  Not sure where these two programs differ in terms of their evaluative capability.

~> sudo mii-tool -v
eth0: negotiated 100baseTx-FD, link ok
  product info: vendor 00:07:32, model 17 rev 5
  basic mode:   autonegotiation enabled
  basic status: autonegotiation complete, link ok
  capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
Either way, it seems like this isn't a known/obvious issue, so I'll push forward with investigating for hardware defects.  Probably try running bananian as well just to be sure it's not a software issue.
 
Thanks.
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