Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by SteeMan

  1. 19 hours ago, robertoj said:

    I was expecting it that the user overlays appear in the armbian-config utility... but my dtbo didnt show in the system>hardware selection options... is this normal?

    It depends on what you mean by normal.  Currently the OVERLAY_PREFIX for this board is set to: OVERLAY_PREFIX="sun50i-h616" as the overlays are currently being shared between the h616 and h618.  So if you rename the overlay with that prefix it should be picked up by armbian-config.

  2. Try a different SD card.  I've seen with recent kernels that  a lot of SD cards that I have are no longer are working, especially 64G and larger cards.  It you have a high quality 16G or 32G SD card try that.  I don't have this board so my suggestion may be completely wrong but it would be interesting to hear your results.

  3. 6 hours ago, Khadas said:

    didn't understand if the current official Armbian for S905 soc supports eMMC flashing, I read somewhere that it's not supported yet but I'm not sure.

    It depends.  Generally if you follow the installations instructions posted in the FAQ section on this site, then yes it is supported in most cases.  The one case that is known not to work is for the first generation of the s905 CPUs.  Chips labeled s905.  The second, third and beyond generations should be fine.  So the s905x (w,d,l, etc), s905x2, etc should work.  Just the first gen s905 is known not to work.

  4. It sounds to me as if you may have used armbian-config to copy the root filesystem to emmc, but didn't copy the boot environment over.  So you may have had a working environment with boot from SD, but everything else on emmc.  Then when you forced the change of the boot uuid, you now have a broken system as there may not be a boot environment installed on emmc.  But since I don't know the exact options you used in armbian-config this is only a guess.


  5. Updates to the website can be a manual process for many things.  And with any manual process, there are bound to be many mistakes.  The most accurate info for any board is to look in the board config file.  The board maintainer is automatically maintained from a database of maintainer information.

    $ grep BOARD_MAINTAINER orangepizero2.conf
    BOARD_MAINTAINER="krachlatte AGM1968"

  6. 27 minutes ago, Stephen Graf said:

    would like to have a clear statement of how the orangepizero2 and orangepizrto3 are going to be treated going forward. 

    The answer to this question will likely come out of the 24.02 release planning meeting: https://forum.armbian.com/topic/33605-armbian-2402-release-planning

    The approval of the developer community is a requirement for standard support of a board.  I would suggest you attend this meeting.


    One thing you may not be aware of that is in the background is the relationship (or lack thereof) between Armbian and Orange Pi.  You might notice that they were not mentioned in the Vendor Appreciation section in today's Armbian Leaflet #18.


    Along with having a maintainer for a board to be supported, it also needs:

    For a SBC to be considered supported:

    - must be beneficial to the Armbian project

    - Armbian team must confirm and agree upon all supported boards statuses


    Currently I would say the lack of a relationship between Armbian and Orange Pi will make it difficult to demonstrate how the added support workload is beneficial to the Armbian project. (my opinion, not official statement)


    29 minutes ago, Stephen Graf said:

    Currently the orangepizero2 is a supported board, although how it got that way I can't figure out.  So little of it was working until this round of development over the last few months. There is no maintainer listed at present.

    The zero 2 currently has two maintainers listed.



  7. It works for me.  When I mount that image I have a fully populated armbi_boot partition.


    blind@xps13:~$ cd /media/blind/armbi_boot/
    blind@xps13:/media/blind/armbi_boot$ ls -l
    total 77808
    -rw-r--r-- 1 blind blind      800 Nov 29 21:56 aml_autoscript
    -rw-r--r-- 1 blind blind     1536 Nov 29 21:56 armbian_first_run.txt.template
    -rw-r--r-- 1 blind blind    38518 Nov 29 21:56 boot.bmp
    -rw-r--r-- 1 blind blind     8075 Nov 29 21:40 boot.cmd
    -rw-r--r-- 1 blind blind     8147 Nov 29 22:02 boot.scr
    drwxr-xr-x 2 blind blind     4096 Nov 29 21:56 build-u-boot
    -rw-r--r-- 1 blind blind   250358 Nov 27 06:26 config-6.1.63-current-meson64
    drwxr-xr-x 3 blind blind     4096 Nov 29 21:50 dtb
    -rw-r--r-- 1 blind blind      174 Nov 29 21:56 emmc_autoscript
    drwxr-xr-x 2 blind blind     4096 Nov 29 21:56 extlinux
    -rw-r--r-- 1 blind blind 27433472 Nov 27 06:26 Image
    -rw-r--r-- 1 blind blind 22787439 Nov 29 22:06 initrd.img-6.1.63-current-meson64
    -rw-r--r-- 1 blind blind      537 Nov 29 21:56 s905_autoscript
    -rw-r--r-- 1 blind blind  4317699 Nov 27 06:26 System.map-6.1.63-current-meson64
    -rw-r--r-- 1 blind blind   609247 Nov 29 21:56 u-boot-s905
    -rw-r--r-- 1 blind blind   740080 Nov 29 21:56 u-boot-s905x2-s922
    -rw-r--r-- 1 blind blind   646455 Nov 29 21:56 u-boot-s905x-s912
    -rw-r--r-- 1 blind blind 22787503 Nov 29 22:06 uInitrd

  8. On 2/2/2024 at 4:55 PM, pixdrift said:

    I understand your viewpoint @Gunjan Gupta, but I respectfully disagree with this approach. The amount of burden (managing more board specific overlay files) put onto developers in Armbian is far better than the impact that including all boards has on the user experience (UX) for (potentially inexperienced) end users using armbian-config. I can't think of a good reason for anyone developing a product to intentionally make the experience worse for users to save a small amount of time (and disk space) for developers.

    When you have been involved with Armbian for a length of time (and read a few of igor's rants 🙂 ) you will realize why what was said here will not be received well by many within Armbian.

    It isn't that what you are saying isn't a reasonable comment.  The problem is that Armbian is under resourced by probably an order of magnitude.  Discussions are continually occurring on how the project can survive let alone move forward.  Many of those conversations involve discussing how more can be done with less resources, ways to cut features/scope to make what exists manageable.  So by you saying to "put [more work] onto developers in Armbian is far better than ..." you are hitting a nerve.  In the current environment that will never pass muster.  Any proposed solution needs to maintain or reduce developer work in the long term.  So any feature suggestion is going to be measured first against that metric, then secondarily by the merits of that feature. 


    This whole dtd discussion is fundamentally a request for a new feature for Armbian.  Regardless of the merits of your focus on the end user experience, that isn't the way Armbian has handled dtbs in any of the existing boards that are supported.  I'm not saying that what exists is good or desireable, but it is what it is.  Can it be improved, sure.  Can it be improved and at the same time not increase maintenance costs going forward, maybe.


  9. 26 minutes ago, Pszemek said:

    but it seems that the computer doesn't recognize any new devices

    What do you mean by this?  You have the usb burning tool running when you plug the male usb to male usb cable into the tv box correct?  And also you are not connecting the tv box to power, but letting it be powered from the usb cable?

  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines