Jump to content

Igor

Administrators
  • Posts

    14652
  • Joined

  • Last visited

Posts posted by Igor

  1. I made another test with exact same image: http://sprunge.us/aGEB + iperf test. I switched ports, first time was gigabit, second fast Ethernet.

    Spoiler
    
    [ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
    [  4]   0.00-1.00   sec  11.7 MBytes  98.0 Mbits/sec  110    266 KBytes       
    [  4]   1.00-2.00   sec  11.1 MBytes  92.8 Mbits/sec   54    215 KBytes       
    [  4]   2.00-3.00   sec  11.3 MBytes  94.9 Mbits/sec   27    168 KBytes       
    [  4]   3.00-4.00   sec  11.2 MBytes  93.8 Mbits/sec    0    187 KBytes       
    [  4]   4.00-5.00   sec  10.8 MBytes  90.7 Mbits/sec    6    153 KBytes       
    [  4]   5.00-6.00   sec  11.4 MBytes  95.3 Mbits/sec    0    177 KBytes       
    [  4]   6.00-7.00   sec  10.8 MBytes  90.8 Mbits/sec    0    191 KBytes       
    [  4]   7.00-8.00   sec  11.1 MBytes  93.3 Mbits/sec    0    205 KBytes       
    [  4]   8.00-9.00   sec  1.49 MBytes  12.5 Mbits/sec    2    202 KBytes       
    [  4]   9.00-10.00  sec  0.00 Bytes  0.00 bits/sec    1    202 KBytes       
    - - - - - - - - - - - - - - - - - - - - - - - - -
    [ ID] Interval           Transfer     Bandwidth       Retr
    [  4]   0.00-10.00  sec  90.9 MBytes  76.2 Mbits/sec  200             sender
    [  4]   0.00-10.00  sec  90.9 MBytes  76.2 Mbits/sec                  receiver
    
    [ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
    [  4]   0.00-1.00   sec  12.7 MBytes   106 Mbits/sec    0    691 KBytes       
    [  4]   1.00-2.00   sec  11.2 MBytes  94.4 Mbits/sec    0   1.34 MBytes       
    [  4]   2.00-3.00   sec  11.2 MBytes  94.1 Mbits/sec    0   1.78 MBytes       
    [  4]   3.00-4.00   sec  11.5 MBytes  96.4 Mbits/sec    0   1.95 MBytes       
    [  4]   4.00-5.00   sec  11.4 MBytes  95.3 Mbits/sec    0   2.02 MBytes       
    [  4]   5.00-6.00   sec  10.7 MBytes  90.0 Mbits/sec    0   2.04 MBytes       
    [  4]   6.00-7.00   sec  11.8 MBytes  99.0 Mbits/sec    0   2.05 MBytes       
    [  4]   7.00-8.00   sec  10.6 MBytes  89.0 Mbits/sec    0   2.06 MBytes       
    [  4]   8.00-9.00   sec  11.7 MBytes  98.4 Mbits/sec    0   2.06 MBytes       
    [  4]   9.00-10.00  sec  11.0 MBytes  92.1 Mbits/sec    0   2.07 MBytes       
    - - - - - - - - - - - - - - - - - - - - - - - - -
    [ ID] Interval           Transfer     Bandwidth       Retr
    [  4]   0.00-10.00  sec   114 MBytes  95.5 Mbits/sec    0             sender
    [  4]   0.00-10.00  sec   114 MBytes  95.5 Mbits/sec                  receiver

     


    My board is Orange Pi Zero 1.1 as you can see on the pic. My zero works with zero problems. Change cables, inspect PCB, which version is yours?

    20170619_144739.jpg20170619_144714.jpg

  2. 2 hours ago, rufik said:

    Ups, Lime2 price is about 55 euro, so somehow expensive when compared to $25 for NanoPi Air...

     

    Lime2 (and some other boards) has what you asked for: battery backup, while Air does not have that and its probably wrong board for this job?, regardless of the price and small / sexy size. Why bother with price difference? If this would be a commercial project, imagine how much money you saved by choosing the right board for the job at the very early start :) If you need battery backup, options gets limited.

  3. 42 minutes ago, blaster_56 said:

    i'v test your image, writing it with live linux, same problem about ethernet, wifi work very well but ethernet is not working, it didnt take the dhcp and dont working in static IP, link is ok from ethtool, ethernet cable work with my computer.

     

    If you have network problems with all images and also with preinstalled Android, that makes me think on rare hardware issues, which we can't help much. I have seen bad soldering causing them - check your PCB for possible defects. Try once again with Zero - network stack is exactly the same and board must works - with image for it.

     

    I can assure you that network in our images works (this is a very basic condition for development images too, unless broken) - I made a test on the image which I propose you for download. Just to make sure.

  4. Granted! Thank you.

     

    Some more general thoughts:

    We have a very strong spam protection, so you won't have much job dealing with robots, but human creations which sometimes are spam. Since our moderator team got stronger now, we can keep forum in better condition - keeping posts on topics, which was somehow neglected.

     

    Our job is also to limit down repeated questions the best way possible with as little impact as possible - with tools mentioned above and procedures which should be summed above. You have right for post editing - use it to update "Moderator duties", when we come up with something to add. I'll do so, but sometimes I won't be able to react promptly. Don't edit other people posts unless it's really necessary.

     

    And remember we need to stay humble. We are all just people with ability to make certain moves, which shall be in common interest. Authority will be needed in case of troubles.

     

    Prohibiting (ban) and deleting content should be last option - if warnings does not produce any effect - our forum is in general very good in this manner - we issued one temporal ban and currently we don't have banned users. 

  5. 5 hours ago, Stanislav Sinyagin said:

    I can help with Perl or shell scripting, if needed


    Help is welcomed and needed. Of course.

     

    On any of those three major projects:

    - build engine https://github.com/armbian/build (shell)

    - configuration utility https://github.com/armbian/config (shell)

    - general documentations https://github.com/armbian/documentation (text)

     

    Start something simple to get you going - configuration utility needs some fine touch / adding new features rework into cleaner code, than proceed to hard nuts :)

  6. 6 minutes ago, martinayotte said:

    Since he was the OP, he still had the right to change the thread title from "dwmac-sun8i" to "problems-with-orange-pc" within minutes after I said that he hijacked the thread ...


    That was me :) ... since I cut those posts out and move them under new topics.

  7. What shall moderators do on our forum.

     

    Basics:

     

    - job should be invisible

    - spam control and clean up (rare)

    - approve posts from new users (daily)

    - Warning: editing topic tittle change it's URL
    - move topic to appropriate forum (rare) (tick "Leave a link to the new location" - it deletes auto in 30 days

    • recognise and tag tutorials & researches. Move them into "Research Guides & Tutorials"

    - merge, pin and lock topics (rare, with caution)
    - cut and move posts to new topics (rare, with caution)


    Intermediate:

     

    - Warn User for:

    • spamming, 
    • inappropriate language,
    • signature violation,
    • abusive behaviour,
    • topic bumping.

     

    Stop being a moderator:

    - when you don't want

    - on multiple complains

     

    To study and add more:
    https://bubbajuju.com/forum-moderating/

  8. A20 boards are generally just fine, while R1 ... we all know it's shitty by design and If we had EOS section since start, it would be already long gone simply because it sucked so much of our time, more than any other board, without any point & value.

     

    There are four images for R1 for download - all are working now - I remake last image with last working mainline kernel (4.9.7) and that's all. EOS means we will officially not deal anymore with the board, but this does not prohibit anyone to make moves. Kernel updates will continue to run out so their is still hope for the board.

    I also added two A10 boards there too. Why? They are working O.K., they are stable, but make just enough troubles on upgrades. Do we need to deal with them? No. They are rare and we don't have more than one sample around.

     

    9 minutes ago, Tido said:

    no one ever beside TK complained


    Well, I would complain too, but it doesn't make any good :)

     

    Quote

    Launch --- Due in 149 Days (or when it is ready)

     

    and please put that somewhere were we can see that, like here (it is already written just needs a link to the lines above) 

        Countdown instead of frozen numbers ?


    Yes, I'll update and make it more visible asap. In any case nothing major before September.

  9. 31 minutes ago, blaster_56 said:

    I'm not the only one who face this kind of problem, i can garantee you that the Debian Jessie Image was not tested and Ethernet Driver is corrupted. (version 5.25 and 5.30)


    There are lots of problems with experimental kernel which is this topic about and which we don't support.

     

    If you have Opi PC+ and you want Debian Jessie: https://dl.armbian.com/orangepipcplus/Debian_jessie_default.7z (tested!)

  10. 4 hours ago, zador.blood.stained said:

    IMO every release. U-boot has ~2 months release cycle, kernel has ~2-2.5 months release cycle and current Armbian release cycle is much longer, so we may have to adjust it on the fly.


    OK, than next release should be planned for Sep 11, 2017, followed by Nov 13, 2017, ... the same dates as u-boot release date.
     

    26 minutes ago, zador.blood.stained said:

    Also should we hide "dev" kernel target in the build script unless EXPERT=yes is set and move all boards which only have a dev kernel target to WIP section?

     

    Yes, why not. 

  11. 8 minutes ago, debianxfce said:

    Armbian is based on Debian that has ARM support for many CPUs.


    Surely, aarch64 package base and our standard custom work on top of Debian is more or less o.k. / matured, but most problems on those boards are below userspace - on u-boot and kernel level. Standard arm64 Debian / Ubuntu kernel most likely won't even boot.

     

    Within Armbian we would also like to provide clean building process, starting with boot loader. Here some code cleaning / fixing is needed or workaround.

  12. 4 hours ago, Stanislav Sinyagin said:

    I'm fine with experimental status, but just wondering, how did 4.10.3-sun8i memorize the MAC address, and why 4.11.3-sun8i does not?


    Don't know. The main problem with development kernel(s) is that is difficult to stay on track to understand changes. Each question might lead into deep investigation which is not possible.

    I know one important detail - current network driver is deprecated / not good for mainline / half broken and somebody is working on a new one. Getting to know why the problem is present in current kernel is therefore pure waste of time. This issue is a school example, why support for WIP is pointless.

    You can try with workarounds to set MAC until things are solved.

     

    More or less updated status can be found here: http://linux-sunxi.org/Linux_mainlining_effort


    We have some general troubles and changes with nightly builds. Repository will be rebuilt daily, while images weekly.

     

    &Thanks!

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines