Jump to content

SteeMan

Moderators
  • Posts

    1438
  • Joined

  • Last visited

Posts posted by SteeMan

  1. It would be helpful if you provided any information on what your box is, what build you are using, what steps you have taken to get to the install point you have.  If the keyboard isn't working it would imply that you don't have working usb support, which would likely indicate you are not using a compatible dtb for your system. But with absolutely no information provided that is just a guess.

  2. I was going to say much the same as hexdump.  My recommendation if you want to learn this is to start by understanding the existing infrastructure that has been put in place over the last few years to get what is currently working.  Once you build an understanding of why things are done the way they are, then you will have a good understanding on how you can help move things forward.

     

    To repeat some of what hexdump said above, you should start by understanding how the multiboot process works (and why it is necessary).  Basically build an understanding of what all the files in the /boot directory are doing and why they are needed to make a successful boot.

  3. @Sameer9793 I have a few amlogic boxes so I do have an interest, but limited technical knowhow at the moment, which is why I help out as a forum moderator.  I can answer some basic questions and perhaps provide you some guidance.  But this conversation really has nothing to do with this topic, so please open a new thread if you have some questions to ask.

  4. @Sameer9793 for context this is something balbes150 posted in a different thread this morning:

     

    "AML = shit. These chips are designed exclusively for Android. . Running Linux =  constant problem. Therefore, I refuse to work with these chips."

     

    And this is after balbes spent about 4 years of his time working with amlogic CPUs.  He has moved on to supporting other CPUs and has no interest in helping with amlogic CPUs/tv boxes.

  5. @Saru  I see you have asked in a couple of different threads the question about boards that have good support for gpu acceleration.  Unfortunately there really isn't any board that I am aware of that has very good support for gpu acceleration.  The biggest issue is the state of opensource gpu support for arm chips.  The closed source drivers exist and generally work OK, and are what android uses.  But the open source drivers are still a work in process.  The drivers are improving constantly and as they do, the integrations to other software and the specific boards take place.

  6. I hadn't heard of volumio before you mentioned it.  I see that it packages/repackages balbes150's work.  But it is ancient code - from 2018 and using kernel 3.14.  This will be incompatible with the Armbian (assuming you have 5.9 kernel installed on emmc) as well.  The scripts changed a lot over time.  You can't mix and match different boot scripts.  Unless you know otherwise, assume that you can't install/use more than one os.

    The only recommended way to switch is to revert the box to an original android firmware, and then use the os you are trying to install's installation instructions.  All of the 'install linux on amlogic tvbox' scripts are assuming you are starting from a clean android box, not something whose environment has been messed with by other installation scripts.

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

     

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

     

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

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

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines