04-29-2016, 08:32 AM
(04-29-2016, 08:05 AM)Manilow Wrote: I installed the debian image (longsleep 20160421), as that seems to be the only viable option for the 512MB version.
All OS images here are based on longsleep's work and he prepared a simple method to update all these images so they can benefit from latest fixes. I don't understand why this important information is not featured in the download section in the wiki.
Code:
bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_uboot.sh)
bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_kernel.sh)
bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_fix_whatever.sh)Regarding the Ethernet problems. None of the devs that do the real work here experienced these problems so far (only the integer overflow issue affecting the 2GB boards that has been fixed by longsleep within a few days 4 weeks ago). Since you're the first here not only whining but using the right equipment what about putting a pcap trace online so that others are able to look through?
And just a thought: When you install on both machines iperf or iperf3 and then connect Pine64 <--> Pine64+ directly. Do you also get duplicate packets and how does performance look like (+85 Mbits/sec is what should be expected)