Jump to content

SteeMan

Moderators
  • Posts

    1845
  • Joined

  • Last visited

Everything posted by SteeMan

  1. Then that is the thread you should be asking your question, not starting a new thread.
  2. Have you followed the instructions in the official rk322x thread: The link to builds you included above is some archived stuff, not current.
  3. Known Issue: https://forum.armbian.com/topic/30245-cant-boot-with-2305-or-later-builds-on-s905x2-g12a-or-s905x3-sm1
  4. Yes, u-boot-s905x-s912 is correct for an s905w based board. Your original post said u-boot-s905x2-s912 which doesn't exist
  5. Also the contribute/PR process as documented in the Armbian Docs: https://docs.armbian.com/Process_Contribute
  6. There is a reason the FAQ I pointed you to says not to expect to be able to get wifi or bluetooth working. I don't have wifi on any of the boxes I own.
  7. sudo apt install armbian-firmware-full
  8. My only thoughts on your dtb questions, is that as long as you are using a meson-gxl-s905x-* one you should be fine. I wouldn't worry about making modifications as you test different permutations.
  9. Make sure you have installed armbian-firmware-full. The default builds only include a trimmed down set of firmware that is intended to cover the common ones, but to save space doesn't include all the firmwares available in mainline linux kernel. That may solve your problem. If you haven't already, I would suggest you open the box and see what wifi/bluetooth chip you have on your board. Then you need to make the dtb file match what hardware you have.
  10. I'm assuming this is as typo, since that file doesn't exist.
  11. The TX3 comes in a lot of different versions. What cpu does yours have? List the steps you have taken to try your install? (u-boot.ext version, dtb). If you are testing with an SD card, what storage you have internally is irrelevant.
  12. Moved to new post
  13. You first need to realize that the dtb is a binary output of the dtc command. You start by looking at the source dts files, that can be found in the kernel source. dTc compiles the dts files (and included dtsi files) into the final dtb binary
  14. Getting a correct dtb is one of the most complex things to do. To do it correctly you really need to know in detail every physical aspect of the board, all the components and how they are wired together. You really need the complete board design information to do this. Otherwise you are just guessing. This is a very difficult task. The information is out there to learn how to do this, but expect to invest many weeks of time learning. But if you are up for a challenge...
  15. Your question has nothing to do with Armbian. Please ask for help in forums that either deal with your device or with Android.
  16. @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.
  17. This is not an Armbian build. Where did you download this from?
  18. 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.
  19. 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.
  20. What you did to force the script to select the proper devices looks good.
  21. 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
  22. 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?
  23. 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.
  24. 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)
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines