Jump to content

SteeMan

Moderators
  • Posts

    1387
  • Joined

  • Last visited

Posts posted by SteeMan

  1. You apparently didn't read the FAQ post carefully as this is addressed:

     

    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.

  2. An external usb wifi adapter should generally work.  The key being that the linux kernal has the required driver/module to support that usb driver.  Generally any common wifi adapter will have linux kernel support.  I would avoid trying to get the cheapest usb wifi adapter you can find, as those are more likely in my experience to not have linux support.

     

    Making sure that I am providing a complete answer to your question, the lack of support for the internal wifi on TV boxes is unrelated to support for any specific usb wifi adapter.

  3. All the 'install multiboot' process is doing (whether through the reset button or update app) is running the uboot script aml_autoscript located in /boot in the image.  If you can get into uboot via a serial interface you can run these commands directly.  They are setting uboot environment variables to tell the boot process to look for armbian before trying to boot the android partition.

  4. What you are reporting doesn't make sense.  There isn't anything that should be preventing the android os from booting after you enable multiboot.  Let alone needing to reinstall the android firmware.  When you say the 'backup and restore thing' what exactly are you doing?

  5. (Moved post to a more appropriate location)

    You will need to provide more information than just a screen shot.  Lets start with the TV Box you have, what dtb you are using, etc.  I think I saw in another thread you mention that you are sucessfully running a box from the SD card, so I'm not sure what your actual problem is.

  6. Assuming the label is correct this is an s905x cpu (would have to remove the heat sink from the CPU to be 100% certain).

    Then you should use:  u-boot-s905x-s912 and try all the meson-gxl-s905x-* dtbs (but start with meson-gxl-s905x-nexbox-a95x).

    Don't worry about the install to emmc yet, make sure everything else is running fine first.  But if you eventually do want to try it would be: install-aml.sh

  7. It could be either CPU.  Manufacturers produce many varients of a tv box over time, changing the components to what's cheapest at the moment.  So two identically labeled tv boxes can have different components.  I would recommend opening the box and looking at the physical CPU to get your answer.

  8. 13 hours ago, MX10.AC2N said:

    How can we solve this problem with the / boot partition in FAT during updates??

    Thank again..

    You should report that as a bug to the maintainer of the code you are onstalling.  I have reported (and submitted patches) for similar issues in Armbian code.  

  9. TV boxes are not supported by the Armbian project.  Thus you posted this originally in the wrong forum.  I moved your post to the TV Box forums.

    You don't mention much in the way of useful debugging information, like what build are you using.  But I would recommend reading through the threads in this forum for your cpu and you should find help there.

  10. 13 hours ago, Massive Box said:

    So I wonder if I could just erase the boot partition on my eMMC

    Do not do that as you will brick your box.  Amlogic based TV Boxes only boot from emmc (except in rare cases).

     

    20 hours ago, Massive Box said:

    I've found in my armbian-config settings an "Edit boot.ini script", which currently shows this:

    image.png.d31ee8aa6d2019967d20b75bb22ebb57.png

    Could this be the way?

    No.  boot.ini isn't even used by the balbes multiboot process.

     

    I asked earlier if you could boot from an sd card (as that should work since you originally booted that way before installing on emmc).  Again, I will repeat myself, don't expect to be able to boot from usb, that doesn't work on many amlogic based boxes.

     

     

    13 hours ago, Massive Box said:

    the Windows utility I'm running in a Virtual Box with USB passthrough

    What utility are you running?

  11. OK, now  that you have the latest build, I would recommend that you start over.  Reinstall a fresh android firmware and then try again.  Because you used an old build, that caused you to set uboot variables that are not correct for the latest build.

    Also, it looks like you are using either the wrong dtb or the wrong u-boot.ext.  Since the dtb you mentioned above is for an s905x cpu (meson-gxl-s905x-p212.dtb) but you are using the s905x2 uboot.ext (rename u-boot-s905x2-s912 to u-boot.ext)

     

  12. I'm still not understanding what instructions you are using nor what build you are using.

    I want to correct a couple of items in your previous post.  You don't seem to be looking at the correct aml_autoscript as the 20.10_xxx_5.9.0 build doesn't have a line like setenv bootfromnand 0.

    You mention modifying boot.ini, but that isn't a step that needs to be done. 

    So again, I ask, what build are you using and what instructions are you trying to follow?

    Finally, if you have a working console that you can access the u-boot command line from, then you should be able to just enter the commands one by one as they appear in the aml_autoscript file.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines