Jump to content

SteeMan

Moderators
  • Posts

    1654
  • Joined

  • Last visited

Posts posted by SteeMan

  1. The Armbian and CoreElec systems have different and conflicting booting scripts.  When you enable multiboot (the toothpick) you are storing the uboot environment script on emmc and this then gets used for future boots for all media (emmc, sd, usb).  So you can't just install various different OSs and expect them to work as they all depend on the uboot environment stored on emmc for the system to know how to boot them.  Basically you can't do what you are attempting to do on an amlogic based box.  In fact due to the incompatabilities between CoreElec and Armbian, it is required that if you install/attempt to install CE, that you will need to restore your box to an original android firmware in order to get it back into a state that Armbian will again work on it.

     

  2. 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.

     

  3. 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.

  4. @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.

  5. @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.

  6. 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.

  7. 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.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines