08-20-2016, 04:03 AM
Having intermittent issues with my PINE64 2G Ethernet as well on 1Gb.
It works most of the time... but sometimes it's really slow on the tx side. I've also seen it unable to acquire an IP address automatically. Swapping ports on my router seems to kick it into life again usually. It's okay at this precise moment but it'll probably throw a wobbly at some stage. I'll try and post more info when it is having one of its moments.
The only interesting thing I've noticed is that my router (Asus N56U running Padavan's firmware) reports FCS errors (whatever they are). It's done this on multiple ports that the PINE64 has been connected to whereas the other two plugged into another switch and modem report none. I dunno if this is relevant to your efforts at all... I did of course blame the cable before the forum made me aware of the issues with the PINE64 and Gb ethernet. Swapping it around with a couple of others had the same results... worked for a bit and then threw a wobbly a day or two down the line.
Compared to another port connected to another Gbit switch in my flat through 15m or so of CAT6. I noticed we have "FC TX/RC" here.
My main use of the PINE64 is a Samba server sharing an attached USB HDD so I tend to notice the poor throughput.
Doesn't look like there's a poll option for "works most of the time but not all ways" but I'll add the info to it and try to help to the best of my ability (not much to speak of). Let me know how else I can help.
It works most of the time... but sometimes it's really slow on the tx side. I've also seen it unable to acquire an IP address automatically. Swapping ports on my router seems to kick it into life again usually. It's okay at this precise moment but it'll probably throw a wobbly at some stage. I'll try and post more info when it is having one of its moments.
Code:
yuki_n@aoba:~$ uname -a
Linux aoba 3.10.102-2-pine64-longsleep #66 SMP PREEMPT Sat Jul 16 10:53:13 CEST 2016 aarch64 GNU/Linux
yuki_n@aoba:~$ sudo ifconfig eth0
eth0 Link encap:Ethernet HWaddr 36:c9:e3:f1:b8:05
inet addr:192.168.20.7 Bcast:192.168.20.255 Mask:255.255.255.0
inet6 addr: fe80::34c9:e3ff:fef1:b805/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5666217 errors:0 dropped:0 overruns:0 frame:0
TX packets:6714105 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6494935317 (6.0 GiB) TX bytes:6641734676 (6.1 GiB)
Interrupt:114
yuki_n@aoba:~$ 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
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: external
Auto-negotiation: on
Link detected: yes
yuki_n@aoba:~$ iperf -c mashiro
------------------------------------------------------------
Client connecting to mashiro, TCP port 5001
TCP window size: 22.5 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.20.7 port 51133 connected with 192.168.20.6 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 611 MBytes 512 Mbits/sec
yuki_n@aoba:~$The only interesting thing I've noticed is that my router (Asus N56U running Padavan's firmware) reports FCS errors (whatever they are). It's done this on multiple ports that the PINE64 has been connected to whereas the other two plugged into another switch and modem report none. I dunno if this is relevant to your efforts at all... I did of course blame the cable before the forum made me aware of the issues with the PINE64 and Gb ethernet. Swapping it around with a couple of others had the same results... worked for a bit and then threw a wobbly a day or two down the line.
Code:
Port Link : 1000 Mbps, Full Duplex, FC OFF
MIB Counters
----------------------------------------
ifInOctets : 4483548236
ifOutOctets : 73064230
etherStatsMcastPkts : 36667
etherStatsBcastPkts : 4463
etherStatsFragments : 0
etherStatsDropEvents : 0
etherStatsUndersizePkts : 0
etherStatsOversizePkts : 0
etherStatsCollisions : 0
dot3StatsFCSErrors : 6840
dot3StatsSymbolErrors : 0
dot3ControlInUnknownOpcodes : 0
dot3InPauseFrames : 0
dot3OutPauseFrames : 0Compared to another port connected to another Gbit switch in my flat through 15m or so of CAT6. I noticed we have "FC TX/RC" here.
Code:
Port Link : 1000 Mbps, Full Duplex, FC TX/RX
MIB Counters
----------------------------------------
ifInOctets : 304624413
ifOutOctets : 9667946372
etherStatsMcastPkts : 126449
etherStatsBcastPkts : 14319
etherStatsFragments : 0
etherStatsDropEvents : 0
etherStatsUndersizePkts : 0
etherStatsOversizePkts : 0
etherStatsCollisions : 0
dot3StatsFCSErrors : 0
dot3StatsSymbolErrors : 0
dot3ControlInUnknownOpcodes : 0
dot3InPauseFrames : 0
dot3OutPauseFrames : 0My main use of the PINE64 is a Samba server sharing an attached USB HDD so I tend to notice the poor throughput.
Doesn't look like there's a poll option for "works most of the time but not all ways" but I'll add the info to it and try to help to the best of my ability (not much to speak of). Let me know how else I can help.