Ethernet Slow Download

[amc2012]

Please try setting the speed to 100 mb/s
sudo ethtool  -s  eth0  speed  100  duplex  full
also, use cat6 cable.....

It's not a solution and I wanted to make sure no one else thought it was such. That's all. I am still willing to do any testing and provide feedback on any proposed *solutions* to the issue.

Its not only a solution-- its the ONLY solution at this point in time.  My entire network is 10/100.  10/100 is not crippled -- its fully functional and is of much preferred to 'down'.

-- snip --

That said,  some folks are experimenting with timings.  They are not having much success.   Also, not all boards are having this issue. It may be related to parts issue at one point in the manufacturing process (some parts came from a different source for a time).

I hear you, but I do video and audio editing, so I have had a gigabit network for a very long time now. The PINE is my only remaining wired device that doesn't do gigabit, with the exception of my security camera DVR. The entire reason I bought the PINE was because it had a gigabit interface. 

I have followed the threads on timings pretty closely. I tried some of the suggestions and I think it's safe to say that those parameters are best used for fine tuning other network issues. They do not affect what you correctly state has to be a hardware issue. I saw the post about how a specific chip was sourced from another location to try to get the orders out, but I also saw the one where someone was able to identify they had two boards with the SAME sourced chip and one worked and the other didn't. 

It seems this may be a manufacturing issue at this point that's triggered by something in the environment. Someone else sent in their board to longsleep and it worked fine in that environment. So it certainly looks like right now the issue is manufacturing+environment. I'm not hopeful for a solution at this point. I hope at some point that PINE agrees to replace the faulty boards. I've been using tech for decades now and have never encountered an issue like this. Usually it's clearly hardware or clearly environment. This strange mix is just bizarre.