Jump to content

SteeMan

Moderators
  • Posts

    1998
  • Joined

  • Last visited

Posts posted by SteeMan

  1. 1 hour ago, blue-v said:

    Or asked the other way round: Is there a known fix in the newer versions that addresses this problem?

    This question is irrelevant.  No one really knows the answer.

     

    1 hour ago, Igor said:

    Did you try the same with latest image?

    What Igor is really saying, is if you want anyone to spend their time helping with this, you need to reproduce on current code.  If this was a common problem, it would already be fixed as many others would report something like this.  So it is either something due to your older code, or something specific to your environment.  Those are difficult to diagnose, and when you are asking people to volunteer their time to help you, they are only going to do that, if it is a reasonable to do and you have done everything to narrow the scope of the problem to something reproduceable by someone else.

     

    My first thought is based on the lack of information provided, but is a common cause of mysterious errors, and that is power issues.  How is all of this hardware powered?  SBCs are notorious for having poor power supplies and under load have voltage drops that cause mysterious problems (especially with usb devices drawing some of that power).

  2. @andersonpersan Could you do some tests for me?  Since I can't reproduce the problem (the newest images work on my s905x boxes, including multiple TX3 mini's and X96 mini's), i'm not able to solve the problem.

    Since you have found that an older build is working for you, I would request that you try a couple of things to see we can figure out what isn't working in your case for the latest builds.

    Since you have already installed to emmc, the first test I would ask is to now try to boot a new build from an sd card with the old build in emmc. (The boot logic should boot from SD card first, before emmc)

  3. 15 minutes ago, Jaume Palomer García said:

    device info HW

     

    this is the app, here you can find the exact name of the board inside your android box.

    A note that cheap android tv boxes are known to report fake data to the os.  The best think to do is to open the box and directly inspect the board/chips.  But even then, some manufacturers will alter the markings on their chips to falsify the board makeup.  The goal for TV box manufacturers it so produce the lowest price box, so corners are cut everywhere.  That is why it is impossible to support these boxes well, as any two boxes can have different internal components.

  4. On 4/25/2023 at 12:04 PM, Thibault DESAULES said:

    The current version (Armbian 23.02 Jammy Kernel 6.1.y, Size: 579Mb, Release date: Feb 27, 2023)

    There is a bug in armbian-install in this version that will likely cause your scenario to fail.  You can manually fix/verify the issue by looking at the armbianEnv.txt file installed on the nvme drive and look for the uuid of the drive.  It should be prefixed with UUID= (compare to the armbianEnv.txt on your sd card).  Or you can use a nightly image which will already contain the fix to armbian-install and retry.

  5. @tepo  The Banana PI M2 Zero is not supported by Armbian maintainers.  It is "Community Support" status, which means that it is available for the public at large to support.  There is currently no one in the community that has stepped up to say they will be a maintainer for that board.  So the board is languishing for lack of support by anyone interested enough to contribute.

    Armbian is first and foremost a platform for building images for the many different Arm based boards that are out there.  But with limited resources (both people and money) only a handful of boards get officially supported by the project.  The majority end up supported (or not supported) by the community of volunteers interested in the particular boards.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines