rajprakash

  • Posts

    13
  • Joined

  • Last visited

Reputation Activity

  1. Like
    rajprakash reacted to zador.blood.stained in Module 8192cu.ko not working in Armbian >= 5.14   
    It is expected since the only way to keep out-of-tree modules during kernel upgrades is DKMS, and it doesn't work properly due to kernel upgrade scheme that is used in Armbian.
  2. Like
    rajprakash reacted to tkaiser in OPI Zero - Incoming SSH - Can't connect   
    Bummer says it all. What an attitude. I get sooooo sick of this! Unbelievable!
     
    When ping works but SSH through Ethernet not then most probably the board is stuck in u-boot! You won't believe it but we test the stuff we provide. So if you want to do more than just complaining then grab a serial console and provide the boot log so we can reproduce the issue IF there is one and it's not just the usual issue called insufficient power supply (Zero uses Micro USB which is known to cause problems) or broken burning process or SD card.
     
    Why do you hijack a thread about Wi-Fi related problems when you've not been able to even configure WI-Fi since your installation does not even boot?!
     
    I'm out from now on!
  3. Like
    rajprakash reacted to tkaiser in New unofficial Orange Pi forum   
    Yeah, we definitely 'need' more fragmentation. If I look at http://orangepi.club/forumdisplay.php?fid=4 and https://github.com/SvenKayser/Sambooca-Kernel-H3/commits/sun8i I already got the idea, thanks.
     
    Why on earth should be an Armbian forum be needed somewhere else? There IS already one and that's this one here! What's wrong with trying to concentrate development efforts in one place?
  4. Like
    rajprakash reacted to tkaiser in Orange Pi Zero went to the market   
    And now I'm pretty confused. When I did some performance/consumption tests a while back I tested with various Raspberries and got sysbench results as follows: RPi Zero: 915s, RPi B+: 1311s, RPi 2: 192s and RPi 3: 120 seconds. The latter result is confirmed eg by this RPi 2 with RPi 3 comparison.
     
    So how on earth is it possible that $7 Orange Pi Zero outperforms even RPi 3 and needs only 117.5 seconds?!
     
    macbookpro-tk:~ tk$ ssh orangepizero.local
    tk@orangepizero.local's password: 
      ___                               ____  _   _____              
     / _ \ _ __ __ _ _ __   __ _  ___  |  _ \(_) |__  /___ _ __ ___  
    | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | |   / // _ \ '__/ _ \ 
    | |_| | | | (_| | | | | (_| |  __/ |  __/| |  / /|  __/ | | (_) |
     \___/|_|  \__,_|_| |_|\__, |\___| |_|   |_| /____\___|_|  \___/ 
                           |___/                                     
     
    Welcome to ARMBIAN Ubuntu 16.04.1 LTS 4.9.0-sun8i 
    System load:   0.22            Up time:       29 min
    Memory usage:  11 % of 241Mb  IP:            192.168.83.162
    Usage of /:    16% of 4.0G   
     
    Last login: Fri Nov 11 14:58:56 2016 from 192.168.83.91
    tk@orangepizero:~$ uname -a
    Linux orangepizero 4.9.0-sun8i #4 SMP Fri Nov 11 13:03:52 CET 2016 armv7l armv7l armv7l GNU/Linux
    tk@orangepizero:~$ lsb_release -c
    Codename: xenial
    tk@orangepizero:~$ cat /etc/armbian-release 
    # PLEASE DO NOT EDIT THIS FILE
    BOARD=orangepizero
    BOARD_NAME="Orange Pi Zero"
    VERSION=5.24
    LINUXFAMILY=sun8i
    BRANCH=dev
    ARCH=arm
    tk@orangepizero:~$ sysbench --test=cpu --cpu-max-prime=20000 --num-threads=4 run
    sysbench 0.4.12:  multi-threaded system evaluation benchmark
     
    Running the test with following options:
    Number of threads: 4
     
    Doing CPU performance benchmark
     
    Threads started!
    Done.
     
    Maximum prime number checked in CPU test: 20000
     
     
    Test execution summary:
        total time:                          117.5139s
        total number of events:              10000
        total time taken by event execution: 469.8815
        per-request statistics:
             min:                                 46.72ms
             avg:                                 46.99ms
             max:                                288.34ms
             approx.  95 percentile:              46.77ms
     
    Threads fairness:
        events (avg/stddev):           2500.0000/0.71
        execution time (avg/stddev):   117.4704/0.04