Gigabit Ethernet issue and Android update

[sledride]

Hello,

Just flashed my SD card to the 20160428 of the Android 5.1.1 image and having the same issue as everyone else with Ethernet when connect to gigabit. My connection speed is very very slow or doesn't work at all. Is there any fix to this other than connect to 100Mbit switch?

I see that there is a newer version of Android 5.1.1 released - 20160505. Is there way to update to this release over the internet rather than having to re-flash the SD card?

Device: Pine64 2GB without Wi-Fi / Bluetooth

Thanks and looking forward to be able to actually use this Pine64.

[Luke]

Hello,

Just flashed my SD card to the 20160428 of the Android 5.1.1 image and having the same issue as everyone else with Ethernet when connect to gigabit. My connection speed is very very slow or doesn't work at all. Is there any fix to this other than connect to 100Mbit switch?

I see that there is a newer version of Android 5.1.1 released - 20160505. Is there way to update to this release over the internet rather than having to re-flash the SD card?

Device: Pine64 2GB without Wi-Fi / Bluetooth

Thanks and looking forward to be able to actually use this Pine64.

Its a known issue with the 3.10.65 BSP kernel. Work is done to correct this problem. For now either use a 100mbit is the quick workaround. 
Follow this thread:
http://forum.pine64.org/showthread.php?t...t=Ethernet
OTA updates are coming. 
  

[tllim]

Hello,

Just flashed my SD card to the 20160428 of the Android 5.1.1 image and having the same issue as everyone else with Ethernet when connect to gigabit. My connection speed is very very slow or doesn't work at all. Is there any fix to this other than connect to 100Mbit switch?

I see that there is a newer version of Android 5.1.1 released - 20160505. Is there way to update to this release over the internet rather than having to re-flash the SD card?

Device: Pine64 2GB without Wi-Fi / Bluetooth

Thanks and looking forward to be able to actually use this Pine64.

Its a known issue with the 3.10.65 BSP kernel. Work is done to correct this problem. For now either use a 100mbit is the quick workaround. 
Follow this thread:
http://forum.pine64.org/showthread.php?t...t=Ethernet
OTA updates are coming. 
  

The OTA updates will be released once we fixed the 720p boot up logo screen.

[VeeKayB1]

You can use an old router (with 100 Mb ports) from a few years ago and change the settings to make it behave as a switch.  I did this with my old D-Link router.
There are general instruction on Youtube.   Try google for more detailed instructions.

Basically you need to:
1. Turn off WIFI
2. Disable DHCP
3. Set Router IP address so i won't conflict with your other router(s).
4. Disable DNS



 
Hope this helps.

[tkaiser]

Its a known issue with the 3.10.65 BSP kernel. Work is done to correct this problem. For now either use a 100mbit is the quick workaround. 
Follow this thread:
http://forum.pine64.org/showthread.php?t...t=Ethernet

At the end of this very same thread the real state of this issue is outlined: http://forum.pine64.org/showthread.php?t...24#pid9024

1) This is NOT 'a known issue with the 3.10.65 BSP kernel'

2) exactly nobody is 'working' on this since the few people that could solve this are curious whether this problem is related to underpowering situations (keep in mind that it can't be a software issue since most users aren't affected of the reported 'slowness')

3) you should keep in mind that the so called 'bug tracker' over at pine64.pro is a trash can in reality. Everybody can throw in whatever he likes and it will rot there forever (Allowing to list hardware issues as software bugs is somewhat... ahem...)

4) Several users that experience this problem have been asked in the forums to try to verify underpower issues. No one got back to us so far (most probably since they use workarounds now and wait for a 'patch')

5) By recommending workarounds like 'use 100 mbit' you ensure that the issue won't be resolved anytime soon

Great work done to prevent solving problems so far.

[Luke]

Its a known issue with the 3.10.65 BSP kernel. Work is done to correct this problem. For now either use a 100mbit is the quick workaround. 
Follow this thread:
http://forum.pine64.org/showthread.php?t...t=Ethernet

At the end of this very same thread the real state of this issue is outlined: http://forum.pine64.org/showthread.php?t...24#pid9024

1) This is NOT 'a known issue with the 3.10.65 BSP kernel'

2) exactly nobody is 'working' on this since the few people that could solve this are curious whether this problem is related to underpowering situations (keep in mind that it can't be a software issue since most users aren't affected of the reported 'slowness')

3) you should keep in mind that the so called 'bug tracker' over at pine64.pro is a trash can in reality. Everybody can throw in whatever he likes and it will rot there forever (Allowing to list hardware issues as software bugs is somewhat... ahem...)

4) Several users that experience this problem have been asked in the forums to try to verify underpower issues. No one got back to us so far (most probably since they use workarounds now and wait for a 'patch')

5) By recommending workarounds like 'use 100 mbit' you ensure that the issue won't be resolved anytime soon

Great work done to prevent solving problems so far.

1) Perhaps you are right [edit] in respect to it being related to the kernel, but it is a Known issue nonetheless. I am only relaying the knowledge I've got on the subject matter; I'm not an expert.
2) People are examining the issue. 
3) Disagree - Lenny's site it is an effort to pool together knowledge, information and resources. Among others, also to solve issues and bugs. If you take issue with the quality, why don't you contribute in some meaningful way, perhaps help sort the issue topics ?
4) Lets hope they return with some info eventually.
5) Would you rather that s/he suffers from slow network in the meanwhile ?

[sledride]

[quote pid='9326' dateline='1463069986']

Its a known issue with the 3.10.65 BSP kernel. Work is done to correct this problem. For now either use a 100mbit is the quick workaround. 
Follow this thread:
http://forum.pine64.org/showthread.php?t...t=Ethernet

At the end of this very same thread the real state of this issue is outlined: http://forum.pine64.org/showthread.php?t...24#pid9024

1) This is NOT 'a known issue with the 3.10.65 BSP kernel'

2) exactly nobody is 'working' on this since the few people that could solve this are curious whether this problem is related to underpowering situations (keep in mind that it can't be a software issue since most users aren't affected of the reported 'slowness')

3) you should keep in mind that the so called 'bug tracker' over at pine64.pro is a trash can in reality. Everybody can throw in whatever he likes and it will rot there forever (Allowing to list hardware issues as software bugs is somewhat... ahem...)

4) Several users that experience this problem have been asked in the forums to try to verify underpower issues. No one got back to us so far (most probably since they use workarounds now and wait for a 'patch')

5) By recommending workarounds like 'use 100 mbit' you ensure that the issue won't be resolved anytime soon

Great work done to prevent solving problems so far.

[/quote]

tkaiser, those were my exact thoughts after reading this thread: http://forum.pine64.org/showthread.php?t...24#pid9024.

Sounds like no one really knows what the issue is and no one has any dates or timeline on when (or if) it will be fixed. Hopefully the main developers are not the ones on this thread. 

I had high hopes for the Pine64, looks like it may become a paper weight... Back to Pi3.

[rahlquist]

[quote pid='9326' dateline='1463069986']

Its a known issue with the 3.10.65 BSP kernel. Work is done to correct this problem. For now either use a 100mbit is the quick workaround. 
Follow this thread:
http://forum.pine64.org/showthread.php?t...t=Ethernet

At the end of this very same thread the real state of this issue is outlined: http://forum.pine64.org/showthread.php?t...24#pid9024

1) This is NOT 'a known issue with the 3.10.65 BSP kernel'

2) exactly nobody is 'working' on this since the few people that could solve this are curious whether this problem is related to underpowering situations (keep in mind that it can't be a software issue since most users aren't affected of the reported 'slowness')

3) you should keep in mind that the so called 'bug tracker' over at pine64.pro is a trash can in reality. Everybody can throw in whatever he likes and it will rot there forever (Allowing to list hardware issues as software bugs is somewhat... ahem...)

4) Several users that experience this problem have been asked in the forums to try to verify underpower issues. No one got back to us so far (most probably since they use workarounds now and wait for a 'patch')

5) By recommending workarounds like 'use 100 mbit' you ensure that the issue won't be resolved anytime soon

Great work done to prevent solving problems so far.

tkaiser, those were my exact thoughts after reading this thread: http://forum.pine64.org/showthread.php?t...24#pid9024.

Sounds like no one really knows what the issue is and no one has any dates or timeline on when (or if) it will be fixed. Hopefully the main developers are not the ones on this thread. 

I had high hopes for the Pine64, looks like it may become a paper weight... Back to Pi3.

I think you completely missed tkaiser's point. 

The linux kernels have no issue with speed. Every person I have asked "so what are you hooking the pine to" has yet to answer. Here are some quick iperf numbers from mine this morning.

Code:

##My pine to my linux media server, both connected to the same Rosewill etherswitch. Pine on 5' cat5e, server on home made 20' cat5e
root@pine64:~# iperf -c 192.168.0.45 -t 20 -i 5 -f m
------------------------------------------------------------
Client connecting to 192.168.0.45, TCP port 5001
TCP window size: 0.02 MByte (default)
------------------------------------------------------------
[  3] local 192.168.0.219 port 35261 connected with 192.168.0.45 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 5.0 sec   551 MBytes   925 Mbits/sec
[  3]  5.0-10.0 sec   549 MBytes   921 Mbits/sec
[  3] 10.0-15.0 sec   550 MBytes   924 Mbits/sec
[  3] 15.0-20.0 sec   549 MBytes   921 Mbits/sec
[  3]  0.0-20.0 sec  2200 MBytes   922 Mbits/sec
##My pine out over the internet to a hosted server of mine (server domain changed to protect the innocent)
root@pine64:~# iperf -c CHANGEDNAMEHERE.com -t 20 -i 5 -f m -u
------------------------------------------------------------
Client connecting to CHANGEDNAMEHERE.com, UDP port 5001
Sending 1470 byte datagrams
UDP buffer size: 0.20 MByte (default)
------------------------------------------------------------
[  3] local 192.168.0.219 port 57171 connected with CHANGEDIPHERE port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 5.0 sec  0.63 MBytes  1.05 Mbits/sec
[  3]  5.0-10.0 sec  0.63 MBytes  1.05 Mbits/sec
[  3] 10.0-15.0 sec  0.63 MBytes  1.05 Mbits/sec
[  3] 15.0-20.0 sec  0.63 MBytes  1.05 Mbits/sec
[  3]  0.0-20.0 sec  2.50 MBytes  1.05 Mbits/sec
[  3] Sent 1785 datagrams
[  3] WARNING: did not receive ack of last datagram after 10 tries.
## My linux media server also connecting to my server on the web
[root@corgi ~]# iperf -c CHANGEDNAMEHERE.com -t 20 -i 5 -f m -u
------------------------------------------------------------
Client connecting to CHANGEDNAMEHERE.com, UDP port 5001
Sending 1470 byte datagrams
UDP buffer size: 0.20 MByte (default)
------------------------------------------------------------
[  3] local 192.168.0.45 port 56507 connected with CHANGEDIPHERE port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 5.0 sec  0.63 MBytes  1.05 Mbits/sec
[  3]  5.0-10.0 sec  0.63 MBytes  1.05 Mbits/sec
[  3] 10.0-15.0 sec  0.63 MBytes  1.05 Mbits/sec
[  3] 15.0-20.0 sec  0.63 MBytes  1.05 Mbits/sec
[  3]  0.0-20.0 sec  2.50 MBytes  1.05 Mbits/sec
[  3] Sent 1785 datagrams
[  3] WARNING: did not receive ack of last datagram after 10 tries.

At this time there is nothing wrong with the kernels as far as Ethernet. I am not even on the latest I am on  3.10.101-0-pine64-longsleep.

Until someone who has the slowness issue can prove there is an issue with the kernel, we should stop blamint it.  We do have proof that at least for some of us it works fine. If its broken for you, you need to show people, answer detailed questions and be willing to do some homework before anyone can willynilly blame anything. For all we know you have a patch cable with bad noise, a broken wire in it, a dirty connection anything.
[/quote]

[VeeKayB1]

Both PC windows and Pine64 2G are connected (hard wire) to the same TP-LINK  1Gbit router 

D:\DownLoads\iperf-3.1.2-win32>iperf3 -p 5201 -c 192.168.1.26 -t 20 -i 5 -f m
Connecting to host 192.168.1.26, port 5201
[  4] local 192.168.1.18 port 59010 connected to 192.168.1.26 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-5.01   sec   126 KBytes  0.21 Mbits/sec
[  4]   5.01-10.01  sec  0.00 Bytes  0.00 Mbits/sec
[  4]  10.01-15.00  sec  0.00 Bytes  0.00 Mbits/sec
[  4]  15.00-20.01  sec  0.00 Bytes  0.00 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-20.01  sec   126 KBytes  0.05 Mbits/sec                  sender
[  4]   0.00-20.01  sec  1.43 KBytes  0.00 Mbits/sec                  receiver

iperf Done.


100Mbit connection using a different router

D:\DownLoads\iperf-3.1.2-win32>iperf3 -p 5201 -c 192.168.1.26 -t 20 -i 5 -f m
Connecting to host 192.168.1.26, port 5201
[  4] local 192.168.1.18 port 59025 connected to 192.168.1.26 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-5.00   sec  44.0 MBytes  73.8 Mbits/sec
[  4]   5.00-10.01  sec  49.7 MBytes  83.2 Mbits/sec
[  4]  10.01-15.01  sec  47.7 MBytes  80.1 Mbits/sec
[  4]  15.01-20.01  sec  47.8 MBytes  80.2 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-20.01  sec   189 MBytes  79.3 Mbits/sec                  sender
[  4]   0.00-20.01  sec   189 MBytes  79.3 Mbits/sec                  receiver

iperf Done.