Jump to content

SteeMan

Moderators
 View Profile  See their activity

  • Posts

    1446

  • Joined

  • Last visited

 Content Type 

Everything posted by SteeMan

  1. SteeMan
    @JuFe00 That is a fork of Armbian not Armbian. They use the Armbian name without permission. They do not contribute to Armbian development nor do they participate in these forums. If you have questions about their builds, you need to ask on their support/forums, we can't help here with software we know nothing about.
  2. SteeMan
    This is not an Armbian build. Where did you download this from?
  3. SteeMan
    You should test performance for your use cases. Moving to emmc isn't going to make any real difference in performance, so if it isn't performing well enough for your use cases, it isn't going to get better.
  4. SteeMan
    I don't know. Those scripts are written very differently so the bug you ran into on ddbr may or may not appear for the install script.
  5. SteeMan
    What you did to force the script to select the proper devices looks good.
  6. SteeMan
    Yes those are the dtb files to try. But you shouldn't expect that you are going to have all of the hardware work on these boxes. For example, of the boxes I own, I don't have working wifi on any of them. Just so your expectations are set correctly, please read it you haven't already: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
  7. SteeMan
    Yes. Unless you have the uboot skills to figure out what the aiden rom uboot setup is doing and figure out how to merge the multiboot code into that process. On the performance side of things, have you tried running from a good quality SD card?
  8. SteeMan
    You need to find and restore the original manufacturer's firmware to get back to where you started from. When you say armbian from usb was too slow, what exactly was slow? Running from emmc isn't going to make much if any speed difference. I'm not sure what you are expecting for performance from this.
  9. SteeMan
    what is the output of lsblk?
  10. SteeMan
    Try changing the following line in the script: runfrom=$(lsblk | grep / | grep -oE '(mmcblk[0-9]|sda[0-9])') to runfrom=$(lsblk | grep / | grep -oE '(mmcblk[0-9]|sda[0-9])' | uniq)
  11. SteeMan
    Well, ddbr is a bash shell script. I think you may just need to dig in and debug what is going on. The script is parsing the output of lsblk.
  12. SteeMan
    That is the uboot output. That has nothing to do with ddbr. And yes that is expected output from uboot since linux can't read the android partition table. What is the error/log you are getting from ddbr?
  13. SteeMan
    If you can see /dev/mmcblk1 while running armbian off of your sd you have emmc. You say that ddbr can't detect emmc, what messages/log from your run of ddbr can you provide?
  14. SteeMan
    I would warn against installing to emmc. That should be the last thing you do. First get your environment working as you want then once everything works correctly you may want to install to emmc. Running off of emmc doesn't give you any benefits along the lines you are thinking.
  15. SteeMan
    That is a generalization that isn't true. I have s905x3 boxes that work. So it may be an issue with your specific box not having a dtb that is compatible in the newer builds. What box do you have?
  16. SteeMan
    I pointed to that reference as it answers your question about the mapping between glx, gxbb and s905x, etc. As this thread points out the current builds do not work on s905x3. But that is a different issue than what I was pointing out to you.
  17. SteeMan
    This is explained in the FAQ instructions: https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus
  18. SteeMan
    Moved
  19. SteeMan
    Also, what image of Armbian are you trying?
  20. SteeMan
    Can you capture a pic of the boot messages you are seeing?
  21. SteeMan
    There is no such cpu. Can you specify the cpu you have? There are many different versions of boxes labeled tx3 mini, so you need to be specific. Pictures of the motherboard would also be helpful.
  22. SteeMan
    Known issue see the above thread
  23. SteeMan
    Moved
  24. SteeMan
    You need to find the correct Android firmware for your device and reinstall it according to the instructions for that firmware (usually USB burning tool)
  25. SteeMan
    The first full paragraph in the instructions says: Note: 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 attempting the install. coreelec changes the boot environment in ways that are incompatible with these Armbian builds.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept