Pine A64+ Gigabit issue...

[rhkean]

I have 1 Pine64+ 2GB that has this problem. Another one that is working perfectly fine with the same powersupply, SD-card, ethernet cable and switch.
ATM i attached a USB network card as a workaround, its stable, but does only 100mbit...that raspberry feeling ......
Tried another switch, to no avail.

The issue reminds me of my Odroid-c1, I bought it way back when it was just released. Their gigabit port was also flakey. In the end it was fixed via patched to the kernel. Difference is that everyone had the same issue. I have the problem on 1 pine only.

Anyway ....I noticed in the thread that a lot of people have the problem after starting apt-get commands, while monitoring current consumption i saw the current spike well above 1A (idle @ 0.3A), so the load apt-get is generating might indeed cause a power issue.

I'll try powering from the euler connector tomorrow. since IIRC micro-USB connectors are only rated to 1.8A, I'll update later

I had just hypothesized with someone else that it might be a hardware issue and was going to test with another board this week.

thank you

[waldo]

...

I had just hypothesized with someone else that it might be a hardware issue and was going to test with another board this week.

thank you

I can't think of any other reason for the difference in behavior between the two boards but a hardware difference/fault.
That being said, I hope that the working boards are actually working on the margin of what's acceptable, and that its just a recalibration problem in the driver/kernel.

http://forum.pine64.org/showthread.php?t...9#pid15449
"For reliable Gigabit networking (1000Mbit operation), several sunxi devices require an important tweak that adjusts the relative timing of the clock and data signals to the PHY, in order to compensate for differing trace lengths on the PCB."

thinking out-loud; this could mean that there is a marginal error on some of the boards in the timing of the 4 extra wires used in GbEthernet vs FastEthernet. Which it appears can be fixed with some tweaking .... I'm not ready to give up yet on this wonky eth port

[amc2012]

...

I had just hypothesized with someone else that it might be a hardware issue and was going to test with another board this week.

thank you

I can't think of any other reason for the difference in behavior between the two boards but a hardware difference/fault.
That being said, I hope that the working boards are actually working on the margin of what's acceptable, and that its just a recalibration problem in the driver/kernel.

http://forum.pine64.org/showthread.php?t...9#pid15449
"For reliable Gigabit networking (1000Mbit operation), several sunxi devices require an important tweak that adjusts the relative timing of the clock and data signals to the PHY, in order to compensate for differing trace lengths on the PCB."

thinking out-loud; this could mean that there is a marginal error on some of the boards in the timing of the 4 extra wires used in GbEthernet vs FastEthernet. Which it appears can be fixed with some tweaking .... I'm not ready to give up yet on this wonky eth port

Yay! Please don't give up! It's killing me that I replaced my Pi for this specifically for the gigabit ethernet and it doesn't work.

[waldo]

Yay! Please don't give up! It's killing me that I replaced my Pi for this specifically for the gigabit ethernet and it doesn't work.

==> was a bit stoned while thinking out loud, the timing is between the processor and the PHY so the 4 extra wire storry is BS
But still ... rest could be true

Mainline kernel and GbE were what drew me in, GbE is what worries me most atm.

[niall]

Same problem here Limiting to 100mb helps a little but not much

Gigabit broadband connection.

2016-07-17 13:40:25 Testing against netperf.bufferbloat.net (ipv4) with 20 simultaneous sessions while pinging www.google.com (30 seconds)
....................................
Download: 21 mb/s
Latency: (in msec, 34 pings, 0.00% packet loss)
Min: 9.210
10pct: 9.290
Median: 10.700
Avg: 11.144
90pct: 12.700
Max: 16.500
.................................
Upload: 4 mb/s
Latency: (in msec, 33 pings, 0.00% packet loss)
Min: 17.900
10pct: 19.200
Median: 22.400
Avg: 22.748
90pct: 26.400
Max: 29.100

Gigabit Lan

iperf 3.0.7
Linux pine64 3.10.102-2-pine64-longsleep #66 SMP PREEMPT Sat Jul 16 10:53:13 CEST 2016 aarch64 GNU/Linux
Time: Sun, 17 Jul 2016 13:17:08 GMT
Connecting to host 192.168.2.146, port 5201
Cookie: pine64.1468761428.687924.13b7d8ea178
TCP MSS: 1448 (default)
[ 4] local 192.168.2.86 port 54341 connected to 192.168.2.146 port 5201
Starting Test: protocol: TCP, 1 streams, 131072 byte blocks, omitting 0 seconds, 100 second test
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 3.71 MBytes 31.1 Mbits/sec 27 4.24 KBytes
[ 4] 1.00-2.00 sec 3.39 MBytes 28.4 Mbits/sec 29 2.83 KBytes
[ 4] 2.00-3.00 sec 1.58 MBytes 13.3 Mbits/sec 10 12.7 KBytes
[ 4] 3.00-4.00 sec 2.31 MBytes 19.3 Mbits/sec 14 12.7 KBytes
[ 4] 4.00-5.00 sec 2.28 MBytes 19.1 Mbits/sec 28 9.90 KBytes