Jump to content

SteeMan

Moderators
  • Posts

    1441
  • Joined

  • Last visited

Posts posted by SteeMan

  1. I think your real question is why hasn't Rockchip put in the effort to get these drivers into mainline linux?  It isn't the goal of Armbian to be the repository of large amounts of unmaintained code.  The goal is really to bring mainline linux to devices.  But that assumes that everyone else is working to bring various bits and pieces from custom linux forks to mainline linux.  While sometimes it is necessary to temporarily host code that has been ported to mainline, but not yet incorporated upstream, most of the efforts should be to get the code into upstream mainline linux.

     

  2. It reports it is full, probably because it is full.  The last set of commands @going suggested you run are to try to figure out what has filled up the storage.  du -s  will be your tool in looking as where the storage is being used.  Google for how others use this command for this purpose.

  3. It looks like that box is using an amlogic s805 cpu (which is a very old 32 bit cpu). The amlogic s905 was their move to 64 bit cpu.

    There isn't any currently active work that I am aware of to support this cpu anytime recently.

     

    There is a very old thread dedicated to this cpu:

     

  4. 31 minutes ago, Victorhtf said:

    EDIT: After post my reply I tried to use the exactly same DTB as you said. And it worked.

    The reason this would work is that you really have a s905L2 cpu.  This wouldn't be the first time that a TV Box vendor and/or parts supplier changed the markings on a chip to give the impression it is something else.

  5. GPT is something the Armbian build framwork supports, not currently the default, but here is a list of boards that use it:

    grep -i gpt *

    armsom-sige7.csc:IMAGE_PARTITION_TABLE="gpt"
    armsom-w3.csc:IMAGE_PARTITION_TABLE="gpt"
    bananapir2pro.csc:IMAGE_PARTITION_TABLE="gpt"
    fxblox-rk1.wip:IMAGE_PARTITION_TABLE="gpt"
    hinlink-h28k.csc:IMAGE_PARTITION_TABLE="gpt"
    hinlink-h88k.csc:IMAGE_PARTITION_TABLE="gpt"
    hinlink-ht2.csc:IMAGE_PARTITION_TABLE="gpt"
    indiedroid-nova.csc:declare -g IMAGE_PARTITION_TABLE="gpt"
    jp-tvbox-3566.tvb:IMAGE_PARTITION_TABLE="gpt"
    khadas-edge2.conf:declare -g IMAGE_PARTITION_TABLE="gpt"
    mangopi-m28k.csc:IMAGE_PARTITION_TABLE="gpt"
    mixtile-blade3.wip:declare -g IMAGE_PARTITION_TABLE="gpt"
    nanopct6.wip:IMAGE_PARTITION_TABLE="gpt"
    nanopi-r5c.csc:IMAGE_PARTITION_TABLE="gpt"
    nanopi-r5s.wip:IMAGE_PARTITION_TABLE="gpt"
    nanopi-r6s.conf:IMAGE_PARTITION_TABLE="gpt"
    odroidm1.conf:IMAGE_PARTITION_TABLE="gpt"
    orangepi3b.csc:IMAGE_PARTITION_TABLE="gpt"
    orangepi5.conf:IMAGE_PARTITION_TABLE="gpt"
    orangepi5-plus.conf:IMAGE_PARTITION_TABLE="gpt"
    panther-x2.csc:IMAGE_PARTITION_TABLE="gpt"
    quartz64a.csc:IMAGE_PARTITION_TABLE="gpt"
    quartz64b.csc:IMAGE_PARTITION_TABLE="gpt"
    radxa-e25.wip:IMAGE_PARTITION_TABLE="gpt"
    rock-3a.conf:IMAGE_PARTITION_TABLE="gpt"
    rock-5a.wip:IMAGE_PARTITION_TABLE="gpt"
    rock-5b.conf:IMAGE_PARTITION_TABLE="gpt"
    rock-5-cmio.csc:IMAGE_PARTITION_TABLE="gpt"
    station-m2.csc:IMAGE_PARTITION_TABLE="gpt"
    station-m3.csc:IMAGE_PARTITION_TABLE="gpt"
    station-p2.csc:IMAGE_PARTITION_TABLE="gpt"
    xiaomi-elish.conf:IMAGE_PARTITION_TABLE="gpt"

  6. 28 minutes ago, Werner said:

    Usually the filesystem expands itself across the whole sdcard on first boot...odd.

    That was my thought as well, odd.

     

    @Jedge  Can you reproduce the problem?  As Werner stated, on first boot the filesystem on the SD card is supposed to be expanded to take up the entire card.  Do you have smaller SD cards you could try, curious if the card size is triggering an issue.

  7. I just want to add a few comments to this whole dtb overlay discussion.

     

    First I want to thank all of you involved in this discussion.  You all have different view points and I think are tackling a very difficult problem to which there is no perfect solution.  What comes out of this discussion should be applied to the other soc families as well, as they all suffer from some form of this issue as there is no standard in place that works for all use cases well.  From what I have seen, good minds are thinking this through and I expect a good result to follow.

     

    The reason I am commenting at all, is because in my role as forum moderator, the basic question: "How do I enable feature x on my board" is one of, if not the most commonly asked question by end users of the forum.  And when the answer is 'just write a dtb overlay', you have lost 95% of those users as they do not have the skills/knowledge to do that.  The status of the dtb overlay's across Armbian supported and community maintained boards is poor.  There is no standardization from family to family or board to board.  And no testing of what does exist to ensure that it works.  Now I'm not saying that all of this needs to be solved in what comes out of this design discussion.  I'm just saying from my perspective as a moderator that this is an area that can use some attention, and in doing so, please try to make the end result usable by the typical end user of an sbc, trying to do common things.  I realize also that I'm saying this when I only use these boards as servers and don't personally need any of the functionality the overlays provide.  But as a forum moderator, I see the mismatch between what is being done and some common use cases that end users are looking for.

  8. On 1/14/2024 at 5:12 PM, sam_uk said:

    Because the other thread was in the wrong place, so it got locked.

    The other thread got locked because your post was inappropriate.  Unless you intend to develop and maintain the Armbian support for this board, there isn't any reason to post this information here.  Igor in your other post pointed you to the following link: https://docs.armbian.com/Process_Contribute/

     

    If you intend to develop Armbian support for this new board, and wish to use this thread as a place to document your work, then this is an appropriate use of the forums.  If not this post will eventually get locked as well, as you aren't asking any question to be addressed by users of the forum.

     

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines