Jump to content

Werner

Administrators
  • Posts

    4476
  • Joined

  • Last visited

Posts posted by Werner

  1. On 11/29/2020 at 10:52 PM, TRS-80 said:

    flowchart

    You have to think more like somebody who has not that much knowledge. This form guides step by step. You dont have to keep track of your path in a chart. Also I think having it in that way it is also more user-friendly (https://en.wikipedia.org/wiki/Don't_Make_Me_Think).

     

    As stated I used Google forms for this implementation because it was handy, not because I like it much. Ideally there would be some kind of integration into our places where to post issues and this form needs to be used in order to be allowed to open a report. Have no clue about how to do that atm though

  2. 2 minutes ago, Hammy said:

    After 24h running the new firmware on Armbian 21.02.0-trunk Buster with Linux 5.9.11-sunxi I got the following:

     

    [7789.126960] xradio WRN: BH: missed 9 consecutive interrupts!
    [ 7798.343147] xradio WRN: BH: missed 10 consecutive interrupts!
    [ 8168.424968] xradio WRN: BH: missed 11 consecutive interrupts!
    [ 8317.727378] xradio WRN: BH: missed 12 consecutive interrupts!
    [ 8458.633587] xradio WRN: BH: missed 13 consecutive interrupts!
    [ 8875.000177] xradio WRN: BH: missed 14 consecutive interrupts!
    [ 9703.025621] xradio WRN: BH: missed 15 consecutive interrupts!
    [11029.338694] xradio WRN: BH: missed 16 consecutive interrupts!
    [11698.845312] xradio WRN: BH: missed 17 consecutive interrupts!
    [11830.943440] xradio WRN: BH: missed 18 consecutive interrupts!

    [...]

     

    and:

    [14108.446345] wlan0: XXX tries to chanswitch to same channel, ignore
    [14108.446708] wlan0: cannot understand ECSA IE operating class, 11, ignoring

     

    This did not happen with the old version?

  3. I think I have minor brain damage or something, does not want to work as straight and focused as I would like but I try to collect something anyways. Or this topic is so extensive that I don't know where to start...probably both :lol:

     

     

    6 hours ago, Igor said:

    What we can do about?

    I think one issue is the decentralization that evolved over the years.

    • Forums (Boards, userspace and build script (Build framework forums))
    • Jira (read-only for the public)
    • Github issues

    I  know this makes partially sense since at least Github issues covering different topics. I will not go into more detail here. The point is that  either try to centralize issue management in whatever way or create a better guidance for users where and how to report.

    I was thinking about some kind a Q&A forum that guides through. This will a) communicate info and b) reduce invalid bug reports (missing armbianmonitor, upstream bugs, wrong forums/place....)

     

     

    Hi. This forum will guide you through all necessary steps to create a proper issue report at the right place containing all necessary information. It will also guide you through steps to do in advance to avoid trivial mistakes. Please read the steps careful and double-check your stuff. Avoidable issue reports due to negligence will be marked as invalid. Abusing will make your permission to create issues being revoked.

     

    • Do you have an issue while building Armbian or with Armbian running on a single board computer?
      • Issue building

        • 1. Make sure you read the docs: https://docs.armbian.com/Developer-Guide_Build-Preparation/

        • 2. start over with a clean git clone
          Also make sure to clear your ccache: sudo ccache -C

        • 3. if some download fail retry later once again before continuing

        • 4. Go to https://github.com/armbian/build/issues/new and create an issue mentioning the information asked for in the issue template

      • Issue running

     

    and so on...

     

  4. I split the topic at this point since I just wanted to showcase a bit what the software is capable of doing with a bit of playing. As stated and mentioned we already have multiple places for issues  (which is an issue by itself but needs to be discussed in a/the other topic) and could at max replace the bug tracker  forums here to get slightly more organized.

    But even that won't happen since the necessary license costs money and it is I think not worth atm if we dont consider do more with it like integrate the whole homepage as well as the docs into it which will most likely not happen either.

  5. If somebody has a chance to test new firmware blob for XR819 feedback would be appreciated :love:

    Simply grab the fw_xr819.bin from the PR below, replace your current one and reboot. Check if Wi-Fi still works as expected or ideally even better.

    The file is located here: /usr/lib/firmware/xr819/

     

    https://github.com/armbian/firmware/commit/aff348fa9eef0fcc97d4f2bb7304f0862baffc20

     

    If in doubt create a backup of your current firmware bin.

  6. This does not answer the question.

     

    8 minutes ago, Werner said:

    OpenVPN config

    Try to get such files from them to use native OpenVPN client

    Those files usually look something like this:

     

    client
    dev tun
    proto udp
    ; Cert
    remote-cert-tls server
    cipher AES-256-CBC
    ;Host
    resolv-retry infinite
    ;auth
    auth-user-pass filename
    auth-nocache
    keepalive 10 30
    
    auth SHA384
    
    remote some.server.com 1194
    
    remote-random
    
    persist-key
    persist-remote-ip
    nobind
    
    sndbuf 0
    rcvbuf 0
    
    verb 2
    
    key-direction 1
    
    ....

     

     

    As this is is not an issue specific to Helios64 I move this to p2p.

  7. Also interesting to see. This board, or better to say their image suffering from a similar issue like the first H6 images: constant load on one core for no reason. loadavg is ALWAYS 1 or higher...

    At least they could reduce it. On H6 3 of 4 cores had always 100% load :lol:

     

    Also shutdown leads into reboot.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines