Jump to content

Igor

Administrators
  • Posts

    14425
  • Joined

  • Last visited

Posts posted by Igor

  1. Chromium for ARM has history of instability and lately it was working quite OK which was one of points that we start using it. I doubt it's related to any changes within Armbian. First we need to reproduce this error on other builds: Pine64, C2, ... than if the problem manifest there to, contact package maintainer. We don't have any intention or resources to fix Chromium bugs. 

    If this is so, I would suggest rolling this package back or upgrade to fixed version when available.

     

  2. 13 minutes ago, Hamish said:

    That being said, I am not asking for support, nor am I complaining about this shitty device, I  just am asking what specific development work - if done (by others - not by you) - would change the default status of this hardware driver back to "enabled"


    Apologise for my misunderstanding and mistreatment. There is so much frustration surrounded this chip, that I don't even try to think.

     

    I can only wish you luck.

  3. 2 hours ago, Hamish said:

    what would is needed to re-enable the driver in standard armbian builds


    There are no standard Armbian builds for Orange pi Zero with kernel 4.x and you are obviously not a developer, whom this build is made for. Topic regarding this shitty wireless driver and related questions forced us to abandon support for it. We already throw into this problem insane amount of our time - it looks we hit the bottom long time ago - and all we get is negative reaction. Sorry, we only do our best to make this peace of shitty hardware work. We did not made it and you did not bought it from us.

  4. We are not clairvoyant or mind readers :P Please describe your setup as best as possible so we know what your operating environment is like.

     

    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 and attach a picture, where it stops.

    3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem.

  5. Very slow for system operations, good enough for storing photos and video. Small files random write speed mater and not every SD card can handle this:


    Your SD:

                                                        random    random
        kB  reclen    write  rewrite    read    reread    read     write
    102400       4      751      720     7118     7114     6195      724
    102400      16     7028     7701     9874    10425     9888       62

    Samsung EVO32

    102400       4     2886     3256     7620     7627     7625     3419
    102400      16     9870    10306    14685    14672    14687     9314
    Do the math. If you compare those numbers further to some SSD drive, things looks even more bizarre.

    If you want to understand more about this issue, read this topic:
    https://forum.armbian.com/index.php?/topic/954-sd-card-performance

    Get proper SD card or use some workaround - freeze kernel packages that it won't upgrade since your SD card is not ready for small files manipulation in decent time. Upgrade is stress for system and you need to have solid SD card to make hassle free upgrades.

  6. 18 minutes ago, Carlos Rodrigues said:

    Its a toshiba Excercia 8GB


    This tells absolutely nothing (due too huge numbers of fakes and I need to google around and trust 3rd party tests), while running this:

    iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2

    does. 

    There is a walk around - just kill the kernel headers compilation process and continue.

  7. 1 hour ago, ssuloev said:

    Hey Igor

     

    build went fine  BUT...  I am unexpectedly missing /boot/overlay folder in the resulting image.. 

    Where should I look at ? 

    Seems like it is handled by add-overlay-compilation-support.patch ?

     

    Thanks

     


    Well, if you removed all patches, you can't expect the same functionality :) There is a lot of added value in there, more than what 4.12 brings. 

     

    Some patches will need adjustment if you go up and down on kernel and we do that each time when version is jumped. I am afraid no other way

  8. 16 minutes ago, hook said:

    Hm, you are right.

     

    Server A is on 4.11.6-sunxi; while

    Server B is on 4.11.6-sunxi

     

    Where would I have to check if the package is indeed frozen (and how to unfreeze it)? I honestly don’t remember doing it myself.


    Now I am confused. :unsure: 4.11.6 should have temperature readings fixed, at least kernel from our repository ... if you are using your own build, rebuild it, install, reboot. 

     

    BTW: Freezing / unfreezing can be simply done in armbian-config

  9. Hmm. 

    Spoiler
    
     _     _                  ____  
    | |   (_)_ __ ___   ___  |___ \ 
    | |   | | '_ ` _ \ / _ \   __) |
    | |___| | | | | | |  __/  / __/ 
    |_____|_|_| |_| |_|\___| |_____|
                                    
    
    Welcome to ARMBIAN 5.31 stable Ubuntu 16.04.2 LTS 4.11.5-sunxi   
    System load:   0.19 0.10 0.05   Up time:       15 days
    Memory usage:  18 % of 1001MB   IP:            
    CPU temp:      38°C           
    Usage of /:    50% of 117G      Battery:       98% charging  
    
    [ 0 security updates available, 1 updates total: apt upgrade ]
    Last check: 2017-07-05 00:00
    
    [ General system configuration: armbian-config ]
    Last login: Wed Jul  5 12:52:36 2017 from 
    
    root@lime2:~# 

     

     

    This is Lime in front of me. Perhaps you have frozen kernel packages to prevent their upgrade?

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines