Kinda upset at the lack of response to GBe issues

[yusijs]

I have one of those ciscos spare, I'll give it a couple more tries tomorrow I reckon and post back.

[Kelson]

ok good luck.. not saying it's that issue, but it might.

[yusijs]

I'm willing to try anything tbh - if I get it to work, you get 5 points! 5 points to gryffindor!

[Kelson]

oh btw you showing 2 configuration showing 10/100 etc.. all checked.
You should just try 1000 only in autoneg or without autoneg without any other speed checked.

[yusijs]

I know - auto neg and 10/100 gives 100mbps speed, autoneg and all speeds give 0.1-1.5mbps

[longsleep]

I received the board from @androsch, plugged it in, tested - works fine.

iperf2 pine64 is server

Code:

root@pine64:~# iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[  4] local 192.168.1.29 port 5001 connected with 192.168.1.232 port 40359
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec   320 MBytes   267 Mbits/sec

iperf2 pine64 is client

Code:

root@pine64:~# iperf -c 192.168.1.232
------------------------------------------------------------
Client connecting to 192.168.1.232, TCP port 5001
TCP window size: 22.5 KByte (default)
------------------------------------------------------------
[  3] local 192.168.1.29 port 39981 connected with 192.168.1.232 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec   813 MBytes   682 Mbits/sec

So no problem of the board itself and this is probably true for all the other non working 1000M reports here. The reason is something else / external to the Pine64. The switch, the cable, the psu, and a combination of those together with the Pine64. So its up to you folks which have the issue to find out what triggers it (start by replacing the switch).

[androsch]

Really interesting, so will again try other power supply and try all my possible switches again.

Even all other computers with GB Lan work fine in my network, but seems Pine64 is special here.

At least its approved its no faulty board or ethernet hardware.

Thanks to longsleep for testing!

Gesendet von meinem XT1032 mit Tapatalk

[amc2012]

I have had about 15-20 gigabit ethernet devices connected to my network over the past few years. Linux, FreeBSD, Windows. None of them have ever exhibited this kind of problem connecting to my switch (an old Netgear 16-port Gigabit switch). I will swap out the Netgear for another switch and test it out tomorrow, since someone else in another thread mentioned an unmanaged Netgear as their connection point as well.

[fneves]

I received the board from @androsch, plugged it in, tested - works fine.

iperf2 pine64 is server

Code:

root@pine64:~# iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[  4] local 192.168.1.29 port 5001 connected with 192.168.1.232 port 40359
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec   320 MBytes   267 Mbits/sec

iperf2 pine64 is client

Code:

root@pine64:~# iperf -c 192.168.1.232
------------------------------------------------------------
Client connecting to 192.168.1.232, TCP port 5001
TCP window size: 22.5 KByte (default)
------------------------------------------------------------
[  3] local 192.168.1.29 port 39981 connected with 192.168.1.232 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec   813 MBytes   682 Mbits/sec

So no problem of the board itself and this is probably true for all the other non working 1000M reports here. The reason is something else / external to the Pine64. The switch, the cable, the psu, and a combination of those together with the Pine64. So its up to you folks which have the issue to find out what triggers it (start by replacing the switch).

Mine works fine in Linux with your kernel but not on android.

[yusijs]

Thanks for runnimg your tests longsleep. I'm still a bit confused at why everything else works, but I'll try what Kelson suggested once I can find the time.