08-06-2016, 05:46 PM
(08-06-2016, 05:25 PM)MarkHaysHarris777 Wrote:(08-06-2016, 04:40 PM)amc2012 Wrote:(08-06-2016, 01:10 PM)MarkHaysHarris777 Wrote: Please try setting the speed to 100 mb/s
sudo ethtool -s eth0 speed 100 duplex full
also, use cat6 cable.....
That's what most of us did at the very beginning to get *some* functionality out of this thing.
But I have a RaspberryPi I can use if I want fast ethernet.
I bought the PINE so I'd have gigabit speeds. I don't want to cripple it to make it work.
Hope they fix this soon.
I am not entirely sure what your post implies.
... but I don't like the tone. "They" are some of us; and 'they' are working their butts off to iron out some of the kinks in this system. It is not helpful to needle people with useless pedantic rhetoric. Either you're part of the solution or you're part of the problem (you decide) because we could use help-- programming, testing, documentation, &c. Most of the people working on this are volunteers, devoting their resources and energies (not to mention their intellectual prowess) to provide a good experience for everyone else. Encouragement is good, needling is bad.
Whoa there, brah. Calm down. Perhaps you missed all the earlier posts where I tested different switches, different cables, posted my results with testing the different tx-delay and rx-delay parameters and generally tried to be helpful to anyone trying to work on the issue. I've been active in just about every thread involving this issue. I have also offered in just about every thread to do testing on this and offer logs, whatever is needed, and have posted my results when doing so. I even posted my router and switch models, hoping we could all come to some conclusion.
So if I'm a little snappy because someone re-posted as a solution the only *workaround* that's worked for us, I apologize. 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.