Jump to content

Werner

Administrators
  • Posts

    5896
  • Joined

  • Last visited

Everything posted by Werner

  1. Neither of these is good advice. dd does not verify written data and balena etcher has known issues, hence it is not recommended either. Either use Armbian Imager (https://docs.armbian.com/User-Guide_Getting-Started/) or USBimager (https://gitlab.com/bztsrc/usbimager). Both are known to work.
  2. Hi, welcome. Syncing forums and tags with supported boards is (still) a manual job and from time to time I either cannot keep up or miss things. Like in this case. I'll fix this later and then move appropriately. Until then feel free to state your question in "Beginners" using the "other" tag. Cheers
  3. BalenaEtcher has known issues and therefore not recommended. Use Armbian Imager or USBimager. Also verify that the downloaded image is good by utilizing the checksum. https://docs.armbian.com/User-Guide_Getting-Started/#download-and-verification https://github.com/armbian/imager https://bztsrc.gitlab.io/usbimager/
  4. Which device? which armbian version? nobody here has a second sight. from the screenshot you aren't even using armbian or at least nothing official.
  5. I'd start by comparing the device tree on a working and non-working image.
  6. Probably a new product. Images are not compatible unless specifically marked as such.
  7. https://docs.armbian.com/User-Guide_Getting-Started/#vendor-current-edge-or-legacy
  8. The related PR states this was tested. @Efe Çetin can you confirm this still works as expected?
  9. https://debug.armbian.de
  10. unsupported build environment. As per documentation Noble is supported only. there are a few others "whitelisted" known mostly to work in the scripts, Zena hasn't yet. Check if your user has access to docker (usermod -aG docker yourusername) and check if docker run hello-world runs properly.
  11. Probably because nobody had use for those until today. Feel free to send a PR adding whats missing.
  12. https://www.armbian.com/download/ https://github.com/armbian/os/releases https://github.com/armbian/community/releases
  13. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  14. diy image and you get it immediately
  15. no clue. needs testing. perhaps it just works. kernel sources are the same as rpi os.
  16. Werner

    Odroid M2 16G

    There is none. Its csc device. Community supported. You are community
  17. You can set conditions on which branch uses which uboot. Like this: https://github.com/armbian/build/blob/9aa6e1e29ec2d397bbe223bebaa93bd13ef79818/config/boards/orangepi5-max.csc#L21 If the BRANCH is edge, then use mainline uboot, specifically this tag.
  18. You can create an extension including something like unset armbian_kernel_config__force_pa_va_48_bits_on_arm64
  19. Hi While I thiknk your approach should have worked, a quick search revealed that something similar is done for a different family. Perhaps try this way:https://github.com/armbian/build/blob/9aa6e1e29ec2d397bbe223bebaa93bd13ef79818/patch/kernel/archive/filogic-6.16/patches.armbian/0007-build.sh-add-additional-build-script-config-defconfi.patch#L1909
  20. Related answer: https://forum.armbian.com/topic/57601-missing-headers-for-618-kernel/#findComment-232075
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines