• Before reporting problems with your board running Armbian, check the following:

    • 1. Check power supply, check SD card and check other people experiences   06/23/17

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information   06/24/17

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

Bananapi M2 and Gigabit Ethernet
0

4 posts in this topic

Recommended Posts

If the A31s is anything like the gigabit on the A20, it's limited to around 400mbit due to internal bus limitations.

Share this post


Link to post
Share on other sites
31 minutes ago, chrisf said:

If the A31s is anything like the gigabit on the A20, it's limited to around 400mbit due to internal bus limitations

 

Nope, for A20 (BananaPi M1) performance see here and for the M2 just search for 'iperf' in this thread there: 

 

'Funny': By searching for M2 iperf results I stumbled accross this here again: https://groups.google.com/d/msg/linux-sunxi/sMMqCjUfoLE/RXYJwz0U_C4J

 

Share this post


Link to post
Share on other sites

I just ran iperf3 as server on an XU4

All boards are running at max speed via cpu-freq

Cubietruck

[  4] local 10.0.0.10 port 47340 connected to 10.0.0.17 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.01   sec  64.1 MBytes   534 Mbits/sec    0    264 KBytes
[  4]   1.01-2.00   sec  63.2 MBytes   532 Mbits/sec    0    362 KBytes
[  4]   2.00-3.00   sec  64.0 MBytes   538 Mbits/sec    0    516 KBytes
[  4]   3.00-4.03   sec  62.2 MBytes   508 Mbits/sec    0    690 KBytes
[  4]   4.03-5.02   sec  62.5 MBytes   530 Mbits/sec    0    690 KBytes
[  4]   5.02-6.01   sec  63.6 MBytes   537 Mbits/sec    0    887 KBytes
[  4]   6.01-7.01   sec  52.5 MBytes   442 Mbits/sec    0    990 KBytes
[  4]   7.01-8.02   sec  48.8 MBytes   404 Mbits/sec    0    990 KBytes
[  4]   8.02-9.01   sec  47.5 MBytes   401 Mbits/sec    0    990 KBytes
[  4]   9.01-10.03  sec  48.8 MBytes   404 Mbits/sec    0    990 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.03  sec   577 MBytes   483 Mbits/sec    0             sender
[  4]   0.00-10.03  sec   577 MBytes   483 Mbits/sec                  receiver

HC1

[  4] local 10.0.0.18 port 53228 connected to 10.0.0.17 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec   111 MBytes   935 Mbits/sec    0    417 KBytes
[  4]   1.00-2.00   sec   113 MBytes   944 Mbits/sec    0    417 KBytes
[  4]   2.00-3.00   sec   112 MBytes   941 Mbits/sec    0    417 KBytes
[  4]   3.00-4.00   sec   112 MBytes   941 Mbits/sec    0    437 KBytes
[  4]   4.00-5.00   sec   112 MBytes   943 Mbits/sec    0    437 KBytes
[  4]   5.00-6.00   sec   112 MBytes   941 Mbits/sec    0    437 KBytes
[  4]   6.00-7.00   sec   112 MBytes   940 Mbits/sec    0    437 KBytes
[  4]   7.00-8.00   sec   112 MBytes   940 Mbits/sec    0    437 KBytes
[  4]   8.00-9.00   sec   112 MBytes   940 Mbits/sec    0    437 KBytes
[  4]   9.00-10.00  sec   112 MBytes   942 Mbits/sec    0    437 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  1.10 GBytes   941 Mbits/sec    0             sender
[  4]   0.00-10.00  sec  1.09 GBytes   940 Mbits/sec                  receiver

What's wrong with my A20 based Cubietruck? It's running Armbian 5.32 with 4.8.4 kernel

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

0

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.