Jump to content

SteeMan

Moderators
 View Profile  See their activity

  • Posts

    2035

  • Joined

  • Last visited

 Content Type 

Posts posted by SteeMan

    X96 mini not boot armbian corectly

    in Amlogic CPU Boxes

    Posted

    Can you attach the file instead of cutting and pasting the contents.  I am looking at the lines in your screen capture that say:

    Ignoring unknown command:

    Ignoring unknown command:

    Ignoring unknown command:

    Ignoring unknown command:

    Ignoring unknown command: FDT

    Ignoring unknown command: APPEND

     

    It seems as if it is ignoring all the lines of your extlinux.conf file.  Is there anything you see that looks unusual?  Did you edit the file on a windows machine (perhaps windows CR/LF characters) - just making a guess.

     

    0

    Cards on the table: Which boxes have working WiFi?

    in General Chat

    Posted

    4 hours ago, balbes150 said:

    (ssv6051 or ssv6252

    Adding to what balbes150 said, there is no support of these chips in mainline modern kernels.  Obviously there is support (poor if you look at the source code) in legacy kernels and therefore Android.  But the focus of Armbian is mainline and therefore from the perspective of Armbian, these chips are completely unsupported and really unsupportable.

    0

    Armbian on CloudnetGo CR19 RK3399 TV Box

    in General Chat

    Posted

    @xoodoo  Please read the following FAQ post:  https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first

     

    While the above posted thread on rk3399 support will give you information on the status of the rk3399, the latest balbes150 build with rk3399 support can be found here: https://users.armbian.com/balbes150/arm-64/

     

    I installed and ran the above build on a Magicsee M6 Max rk3399 box.  I don't know about the box you linked to above, but you can try the different u-boots and dtb files and you may find something that will work for you.

    0

    Allwinner H6

    in Allwinner CPU Boxes

    Posted

    @Crypto_Dino. Also, the instructions you linked to are at least two years old. Many items listed there have changed.  For example the uenv.txt file is no longer used and instead the boot process uses the standard extlinux.conf file.

    Unfortunately I don't have much familiarity with H6 based tv boxes so I'm not able to provide a set of directions for you.

    0

    Help needed with S905X3 Ninkbox N8 plus

    in Amlogic CPU Boxes

    Posted

    You say you have followed the instructions.  Have you explicitly followed this note from the instructions:. Note2: If you have previously run other distributions on the box such as coreelec the below installation will not work. You will need to restore the original android firmware before attemping the install. coreelec changes the boot environment in ways that are incompatible with these armbian builds.

    0

    Allwinner H6

    in Allwinner CPU Boxes

    Posted

    While there are other differences, based on what you have described the biggest difference for you is that the "arm-64" builds are no longer maintained.  Those builds from October 2020 are the last that will be made.  Whereas the "aw-h6-tv" builds are being currently maintained by balbes150 and are current with the latest kernel patch releases.

    0

    Can anyone explains what are the steps for making a TV box works with armbian?

    in General Chat

    Posted

    This comment is likely superceeded by balbes and jock's posts, but I wanted to just provide my thoughts on the android dtb issues. 

    The way I like to think about dtbs is they are glue code between the kernel and the hardware.  We often think of them only from the perspective of the hardware, which once a box is built the hardware doesn't change (although boxes can change over the course of different manufacturing runs providing different board revisions).  But the kernel is an evolving code base and even though the hardware may be fixed, the dtb glue may need to change over time as the kernel code changes.  Thus technically dtbs are kernel version specific (but in practice the changes in the kernel generally are not significant over smaller periods of time).

    However....  When it comes to android kernels two factors come into play, one is that android kernels tend to be highly forked/patched from mainline kernels and second, android kernels tend to be based off very old kernels.  So for example an android 4.4 based kernel is really a 5 year old kernel, and a lot has changed in the kernel over a 5 year period.

    Also, making this more complex is that fact that sbc/tv box support has only been added to mainline kernels fairly recently.  So older android or legacy kernels that were supported were highly patched kernels.

    Armbian is generally focused on current mainline kernels (after all that is where the future support will all take place), and therefore a 5.10/5.12 kernel is very different in how it supports sbc/tv box hardware than a 4.4/4.x legacy/android kernel. 

    The end result is to not expect an android dtb to work with a mainline kernel.  That doesn't mean that there isn't a lot to be learned from an older dtb file, but the process is much more complicated than simply getting the old andoird dtb and using it on a mainline kernel and expecting it to work.

    1
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept