05-04-2016, 01:56 AM
Thanks for all your information, which helped me a lot, to understand some more dependencies.
I can confirm, that setting the cpu-clock to performance is a big step in reducing the seen problems.
Furthermore I figured out, that at least my PINE(512) behaves like described in some of the above linked discussions: After cold boot the network performance is ways better, than after a warm restart. The numbers above are all after cold boot. Running for some time, the rates go down by est. 20%-30%
Unfortunately I see almost no reaction in setting tx-delay and rx-delay in /boot/pine/sun50i-a64-pine64.dtb.
I have started with the dts file from http://github.com/longsleep/build-pine64...noplus.dts and changed the TX and RX values from <0x00000000> to 0x5, later to 0xF0, 0xF00, up to 0xF0000000 and detected no measurable difference.
To avoid any confusion, I deleted the "sun50i-a64-pine64-plus.dtb" file in /boot/pine64, so that I have only the following files in the directory:
I would have expected rendering my network unusable, setting RX and TX to such high values. So I wonder, why that has no measurable influence.
Can it be, that the PINE512 needs an slightly different network device description, as it has a different NIC on board? One thought is, that this section is not used and the interface is just configured with some default values.
I have also observed, that the PINE(512) does not setup random MAC addresses like described in the forums. I can delete /usr/local/sbin/pine64_eth0-mackeeper.sh and delete the "ethaddr=xxxx" line in the /boot/uEnv.txt file. The PINE(512) starts always with the same MAC.
I can confirm, that setting the cpu-clock to performance is a big step in reducing the seen problems.
- The local download rate (wget of an local http URL) rises from the range [100KB/sec..1.5MB/sec] to the range [5MB/sec..10MB/sec].
- The retry rate (as seen in iperf3 ) goes down from 400-600 retries per session to below 100.
- The maximal delay of an echo roundtrip (my script) goes down from 10 sec. to 2 sec.
Furthermore I figured out, that at least my PINE(512) behaves like described in some of the above linked discussions: After cold boot the network performance is ways better, than after a warm restart. The numbers above are all after cold boot. Running for some time, the rates go down by est. 20%-30%
Unfortunately I see almost no reaction in setting tx-delay and rx-delay in /boot/pine/sun50i-a64-pine64.dtb.
I have started with the dts file from http://github.com/longsleep/build-pine64...noplus.dts and changed the TX and RX values from <0x00000000> to 0x5, later to 0xF0, 0xF00, up to 0xF0000000 and detected no measurable difference.
To avoid any confusion, I deleted the "sun50i-a64-pine64-plus.dtb" file in /boot/pine64, so that I have only the following files in the directory:
- sun50i-a64-pine64.dtb
- pine64noplus.dts
- Image
Code:
cd /boot/pine64
rm sun50i-a64-pine64.dtb
dtc -I dts -O dtb pine64noplus.dts > sun50i-a64-pine64.dtb
cd /
umount /boot # make sure, filesystem is clean!
shutdown -P now
#unplug power cable
#unplug network cable
#reconnect power
#after 10 sec reconnect network
Can it be, that the PINE512 needs an slightly different network device description, as it has a different NIC on board? One thought is, that this section is not used and the interface is just configured with some default values.
I have also observed, that the PINE(512) does not setup random MAC addresses like described in the forums. I can delete /usr/local/sbin/pine64_eth0-mackeeper.sh and delete the "ethaddr=xxxx" line in the /boot/uEnv.txt file. The PINE(512) starts always with the same MAC.