Build: [pine64][dev] fixed the link speed is not

[kometchtech]

issue
experiencing the symptoms cannot be fixed 100 M Ethernet speed, as the result of ethtool.
# ethtool -s eth0 autoneg on speed 100 duplex full

# 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:  100baseT/Full                                   
        Advertised pause frame use: No                                          
        Advertised auto-negotiation: Yes                                        
        Link partner advertised link modes:  10baseT/Half 10baseT/Full          
                                             100baseT/Half 100baseT/Full        
                                             1000baseT/Half 1000baseT/Full      
        Link partner advertised pause frame use: Symmetric                      
        Link partner advertised auto-negotiation: Yes                           
        Speed: 1000Mb/s                                                         
        Duplex: Full                                                            
        Port: MII                                                               
        PHYAD: 1                                                                
        Transceiver: external                                                   
        Auto-negotiation: on                                                    
        Current message level: 0x00000000 (0)                                   

        Link detected: yes

env

# cat /etc/os-release                                              
NAME="Ubuntu"                                                                   
VERSION="16.04.1 LTS (Xenial Xerus)"                                            
ID=ubuntu                                                                       
ID_LIKE=debian                                                                  
PRETTY_NAME="Ubuntu 16.04.1 LTS"                                                
VERSION_ID="16.04"                                                              
HOME_URL="http://www.ubuntu.com/"                                               
SUPPORT_URL="http://help.ubuntu.com/"                                           
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"                              
UBUNTU_CODENAME=xenial 

# uname -a                                                         
Linux pine64 4.7.0-pine64 #1 SMP PREEMPT Sat Aug 27 21:17:52 JST 2016 aarch64 ax

the build environment is as follows.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.5 LTS
Release:        14.04
Codename:       trusty

[zador-blood-stained]

Pine64 support in mainline is still experimental, and H3/A64 Ethernet driver is probably not complete, so it's normal that is doesn't support some features (and I'm not sure what driver revision is used in this kernel tree).

[martinayotte]

My PineA64 has the networking working fine, but defaulted to 100Mb/s, probably because it is currently connected to a 100Mb/s switch.

[kometchtech]

Official u-boot problem, has confirmed that 1Gbps is not stable.
Easy it is still connected to the 100Mbps switch.

[ThomasKaiser]

Just FYI: I get pretty constant 435 Mbits/sec in Pine64 -> client direction and 620 Mbits/sec with slight fluctuations in the other direction. With 4.7 -- with 3.10.102 it's 906 and 940 Mbits/sec instead.

[kometchtech]

@ThomasKaiser

Thanks for the info.

When trying to communicate at 1 GB/s, and have a problem that I use is Pine64 plus this Ethernet and packet loss is.

_What will it take to get the Ethernet port working? http://forum.pine64.org/showthread.php?tid=1844_

[zador-blood-stained]

ethtool problem is most likely caused by H3/A64 Ethernet driver in mainline not having such features yet, so there is nothing we can do.

As for packet loss - it is possible that your board is defective: http://forum.armbian.com/index.php/topic/1917-armbian-running-on-pine64-and-other-a64h5-devices/page-2#entry15173

[ThomasKaiser]

Mikhail's right, please check your board with legacy image, if there packet losses happen too but the whole thing can be cured with ethtool there, then your board most probably is defective. In case you have a forum account at pine64.org please send TL Lim a PM and ask for refund/return.

Using their forum to discuss the Ethernet problem is useless since there are a few guys active constantly censoring everything they don't understand. Watch what happened to post 60 for example. Before:

And after:

(clarkss12 might have a 2 GB Pine64+ and uses old Android/RemixOS images that do not contain the fix for the integer overflow, that's why Ethernet seems to be broken with Android but not in Linux -- see link to our forum where I tried to list the 6 different Ethernet 'problems' currently known)

[amc2002]

The moderator in that forum is totally and completely out of control.

[ThomasKaiser]

The moderator in that forum is totally and completely out of control.

He clearly don't know what he's doing (censorship, preventing any progress), but he did it again. Before:

And now:

Please note that my post was N° 74 before and after he censored it is now N° 75. That means that he restored another post he deleted before in the meantime. He deleted several post (not only) of mine and edited the relevart parts of others away. And while he might get the idea that he's playing a dangerous game he continues to play it. Really sad.

Since it's confirmed that at least on one Pine64+ the GbE symptoms are related to PSU/voltage (see here or here or this as the most extreme example since with mainline kernel using the wrong PSU means no access to the GbE PHY at all and not just errors it would be great if Pine64+ users that do not use any Fast Ethernet work-arounds (destroying their cables, using ethtool to force 100 Mbits/sec) start to measure PHY_VDD33 in idle mode and when some load is generated eg using iperf3.

Regarding test point please see Armbian forum. @kometchtech are you able to do some measurements and report back in the forum? (I fear it's not possible to try to do anything useful in pine64 forum as long as this person is enabled to censor everything away that's beyond his imagination)

[kometchtech]

@ThomasKaiser

Thank you for information.

Since English is not good, for it does not have confidence you are able to read well, may be the recognition that I use the armbian image of mailline kernel is to understand, and may if it is possible to apply a load more than 5.2V Is not it?

Then, the benchmark using the iperf, do you report to Armbian forum?

Best regards .

[ThomasKaiser]

This specidic Ethernet issue can be considered a hardware flaw that needs physical replacement of the affected boards. Please check the appropriate thread in Pine64 forum and ask their for refund/replacement.