Jump to content

SteeMan

Moderators
 View Profile  See their activity

  • Posts

    1811

  • Joined

  • Last visited

 Content Type 

Everything posted by SteeMan

  1. SteeMan
    When you say "doesn't work as expected", what exactly isn't working?
  2. SteeMan
    If you are using kernel 6.13 you are using the 'edge' kernel (i.e. development kernel). You likely want to use a 'current' build which will be a 6.12 kernel.
  3. SteeMan
    I don't believe this dtb has ever existed in any armbian build. All references I see to it (via web search) are from non-armbian builds. The dtb isn't in the mainline kernel and thus not in the armbian builds. You could try other meson-sm1-* dtbs that do exist and see if any work for your box, or you could grab a dtb from elsewhere and try it with your armbian build (note you will need a dtb compatible with mainline linux, not one for an android linux).
  4. SteeMan
    @brentr Isn't it the case that apt upgrade will only download the new u-boot files, but you have to run armbian-config to actually install the new u-boot to your installation media.
  5. SteeMan
    In addition to the overlay_prefix what is the value of the overlays parameter in your armbianenv.txt? Perhaps post your entire armbianenv.txt file
  6. SteeMan
    I don't know. I do not have that issue with my tx3-mini boxes. You would likely need use a usb uart connector to capture the boot log and report it back here, https://www.youtube.com/watch?v=UpVMO7gbnYM 1.2 GHz is the rated clock speed of these CPUs. Some android boxes will overclock or just lie about the speed. I haven't experienced this problem. You will need to provide more details.
  7. SteeMan
    I should ask, what image are you working with?
  8. SteeMan
    It is in the fat32 partition on the sd card. The issue seems to be that that partition is created in such a way that windows can't see it, even though it is a windows formatted partition.
  9. SteeMan
    Please read this first:
  10. SteeMan
    moved to the correct forum
  11. SteeMan
    This is not an Armbian build. Please do not post information here that isn't about Armbian. Ophub is a fork of Armbian. They use the Armbian name without permission. They do not contribute to Armbian development nor do they participate in these forums. Content related to their work shoud be discussed in their forums not here.
  12. SteeMan
    Do you have a non-windows machine to use? There may be an incompatibility with the partition type and windows.
  13. SteeMan
    If your emmc isn't working you won't be able to run the aml-s9xx-tvbox Armbian builds. Those builds use the original boxes uboot on emmc to boot from. So you need an intact working emmc with the original android uboot working.
  14. SteeMan
    FYI. Using armbian-config will limit you to compatible kernels for your current distribution.
  15. SteeMan
    You didn't answer the question from Werner above. What are you trying to do? meson (i.e. Amlogic cpus) and sunxi (i.e. Alwinner cpus) are completely different kernels designed for different CPU families from different CPU manufacturers. You can only use the kernel built for your CPU.
  16. SteeMan
    Replacing /boot is not the same. You also have to make sure that the contents of the kernel modules are present for the kernel you are loading (i.e. /lib/modules)
  17. SteeMan
    Moved post to proper forum
  18. SteeMan
    This board is not supported by Armbian. It is a Community Maintained board. Which means that the Armbian infrastructure is used to build automated untested builds and make them available for use. Thus that message.
  19. SteeMan
    The instructions don't say install, they say run. Running from SD card may/will change the boot environment on the mmc and prevent armbian from booting. If you have ever *run* another distribution on the box armbian may not run. You need to reinstall the original android firmware to reset things back to what armbian expects.
  20. SteeMan
    Read the part about having run *any* other distribution on your box before trying the armbian builds.
  21. SteeMan
    While normally we discourage references to ophub as they are a fork of Armbian but continue to use the Armbian name without permission for their fork. They also don't contribute back to Armbian nor do they participate in these forums, I think your post is helpful. It would really be nice if someone were to dig into this and submit a PR back to Armbian to bring the support into the base code that is maintained here.
  22. SteeMan
    Moved to the correct forum (community support). This is not a supported board. Adjusted the tag to reflect the correct board.
  23. SteeMan
    Change title to reflect the real question and moved to the appropriate forum
  24. SteeMan
    But the answer to your followup question is: config/sources/families/include/sunxi64_common.inc
  25. SteeMan
    Why did you title this thread Raspbian if this isn't about a rpi4 or rpi5 device? Maybe you need to explain a bit more about what you are trying to do. The Armbian builds for RPI devices pretty much use the standard raspbian sources. But the sunxi builds have like a hundred patches applied and that is a lot of work to port all those patches.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept