Pine A64+ Gigabit issue...

[rhkean]

I would give the 3.5A PSU a try first (Pine64 won't exceed 1A with normal 'workloads' but the real problem are voltage drops mostly caused by USB cables with insufficient gauge ratings -- never try anything above AWG 20)

Well that didn't fix it.
This is the power supply:  http://www.amazon.com/Extra-Charger-HP-C...B00OPEW1I6

this is the what I did (on gigabit):
* new ubuntu image
* log in as ubuntu
* sudo su -
* apt-get update
* 20 minutes later, It's still on Hit 6 of 8.

this is the what I did (on 100mbps):
* new ubuntu image
* log in as ubuntu
* sudo su -
* apt-get update
* 8 hits, 15 seconds or so...


I'm not sure that I have any decent, non-usb wall warts lying around that I can use for power...

Have you run the kernel and uboot update scripts?

ummm... no.  that would be redundant.

Simon's pine64_update_uboot.sh script just downloads the simpleimage-pine64-latest.img.xz, pulls out the boot0 and uboot sections and writes them to the uSD card.  since that file (dated 2016/04/23) is the same one that was used to create the xenial-pine64-bsbkernel-20160424.img.xz (dated 2016/04/24) Ubuntu img, then this script (IN THIS INSTANCE) wouldn't be changing anything on the uSD card.

The same thing applies to the kernel script.

both his latest kernel and uboot image were used to build his lates ubuntu image.


UPDATE:  ran both to confirm:
also verified that the fix_whatever hasn't changed.  It hasn't.  It only updates the alsa issue.

Code:

[sudo] password for ubuntu:
root@localhost:~# bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_uboot.sh)
Checking for update ...
You are already on the latest version - no update required.
root@localhost:~# bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_kernel.sh)
Checking for update ...
You are already on the latest version - no update required.
root@localhost:~# bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_fix_whatever.sh)
Applying various fixes ...
Done.
root@localhost:~#

[tkaiser]

Interesting observation: http://forum.pine64.org/showthread.php?t...22#pid8522

[rhkean]

you know... I just thought about it... I've got some 7805 1.5A voltage regulators in my bread-boarding stuff....

If I can find a working 12V wall-wart, I bread-board out a 5V supply that should be nice and clean.

-rob

[frewind]

Hi,

my A64+ give me the following across my network

Client connecting to 192.168.0.30, TCP port 5001
TCP window size: 22.5 KByte (default)
------------------------------------------------------------
[  3] local 192.168.0.213 port 59343 connected with 192.168.0.30 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  1.06 GBytes   914 Mbits/sec

[lenny.raposo-pine64.pro]

frewind is yours the A64+ 1gb or 2gb?

[frewind]

frewind is yours the A64+ 1gb or 2gb?

2gb, hope this information is helping...

[lenny.raposo-pine64.pro]

yes it is helpful frewind.

Networking equipment wise (routers switches) what are you running?

[frewind]

yes it is helpful frewind.

Networking equipment wise (routers switches) what are you running?

The A64+ is connected to one of these On Networks switches, that then connects to a NETGEAR GS108UK 8-Port Gigabit switch in the loft, the remote fedora server is off that switch.

[amc2012]

Mine's going to a Netgear as well, an old 16-port. Wish I could get to it right now, but I can't get to the wiring closet tonight. I believe it's a GS516T. I will update this thread when I can get to it. Past that is a T-Mobile RT-AC68U connected to an Actiontec FiOS router in bridge mode.

[waldo]

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