Werner

  • Posts

    2646
  • Joined

  • Last visited

Posts posted by Werner

  1. Hard to tell without digging deeper which is only possible with serial connection. (that is true for all ARM single board computers btw.)

    Pickup an USB UART adapter. They are dirt cheap and extremely helpful in debugging boot failures.

     

    While waiting on that thing to arrive you can check the Kobol wiki and disable the eMMC via jumper and write a fresh image to an sd card and boot from that to make sure the unit itself is fine.

  2. Depending how situation will come out the bug tracker forums could be shrinked and a few merged (for example do whole forum for sunxi/64 family which saves us two subforums or merge whole rk family) and create a new one for unsupported/csc/wip and simply move stuff there? This would reduce the amount of tags for these boards.

    However on truly supported boards we rely on user info like armbianmonitor which often enough is the case that users refuse to give this info.

     

    Btw. for common bug trackers (which are not necessarily based on forums software but Mantis or Bugzilla) it is not uncommon to mark bugs as invalid. Our issue I guess is that they are branded kind a visible in comparison to other threads where bug tracking software has tags like "new" or "triaged" or whatever. However to keep those tags accordingly will create work/pressure on us while marking a thread as solved can user do themselves atm.

  3. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs).  With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported.  Your report is invalid for one or more of the following reasons (non-exhaustive list):

     

    • it is for an unsupported board or image (CSC/EOS/WIP/edge)
    • it is for software that is not supported (such as userspace modules installed on top of the core operating system)
    • it has been logged in the wrong forum (for example requests for help that are not actual bug reports)
    • it lacks requested data (armbianmonitor output)
    • it could have been easily solved by a quick search and/or reading documentation

     

    Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)

  4. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs).  With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported.  Your report is invalid for one or more of the following reasons (non-exhaustive list):

     

    • it is for an unsupported board or image (CSC/EOS/WIP/edge)
    • it is for software that is not supported (such as userspace modules installed on top of the core operating system)
    • it has been logged in the wrong forum (for example requests for help that are not actual bug reports)
    • it lacks requested data (armbianmonitor output)
    • it could have been easily solved by a quick search and/or reading documentation

     

    Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)

  5. H616 has been added to Bug Tracker forums for existing sunxi64 family.

    Take note that this SoC is still kind a semi-supported:

    Quote
    • Legacy kernel based images are using improved and updated stock kernel. If you care that things works (wireless, Bluetooth, CPU frequency scaling, power off, reboot, …) but it uses proprietary boot loader and it comes without our support, use it.
    • Mainline kernel has experimental support only

     

  6. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs).  With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported.  Your report is invalid for one or more of the following reasons (non-exhaustive list):

     

    • it is for an unsupported board or image (CSC/EOS/WIP/edge)
    • it is for software that is not supported (such as userspace modules installed on top of the core operating system)
    • it has been logged in the wrong forum (for example requests for help that are not actual bug reports)
    • it lacks requested data (armbianmonitor output)
    • it could have been easily solved by a quick search and/or reading documentation

     

    Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)

  7. I usually do the noob way finding the trigger files for LEDs :P

    du -a /sys | grep led | grep trigger

     

    I don't know what trigger is needed for mmc but heartbeat is self-explaining. echo heartbeat > trigger

     

     

  8. The size requirements have been updated.

     

    Since we now share images with various desktop environments as well the size of all torrents have now grown to around 500GB.

    To become future-proof again the free space requirement has been raised to 1TB.

     

    For those who did not notice yet. It became rather simple to become an Armbian http/s mirror as well if you do not like torrent stuff: https://github.com/armbian/mirror