Jump to content

Werner

Administrators
  • Posts

    5812
  • Joined

  • Last visited

Everything posted by Werner

  1. 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/
  2. 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.
  3. I'd start by comparing the device tree on a working and non-working image.
  4. Probably a new product. Images are not compatible unless specifically marked as such.
  5. https://docs.armbian.com/User-Guide_Getting-Started/#vendor-current-edge-or-legacy
  6. The related PR states this was tested. @Efe Çetin can you confirm this still works as expected?
  7. https://debug.armbian.de
  8. 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.
  9. Probably because nobody had use for those until today. Feel free to send a PR adding whats missing.
  10. https://www.armbian.com/download/ https://github.com/armbian/os/releases https://github.com/armbian/community/releases
  11. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  12. diy image and you get it immediately
  13. no clue. needs testing. perhaps it just works. kernel sources are the same as rpi os.
  14. Werner

    Odroid M2 16G

    There is none. Its csc device. Community supported. You are community
  15. 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.
  16. You can create an extension including something like unset armbian_kernel_config__force_pa_va_48_bits_on_arm64
  17. 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
  18. Related answer: https://forum.armbian.com/topic/57601-missing-headers-for-618-kernel/#findComment-232075
  19. There are no header packages for each and every trunk version to save resources. Most simple solution is probably DIY an image with INSTALL_HEADERS=yes to have them shipped with the image.
  20. Feel free to reach out and become a partner: https://www.armbian.com/partners/
  21. https://docs.armbian.com/Developer-Guide_Build-Switches/ Check for ARTIFACT_IGNORE_CACHE diy packages are locally cached. automated packages from the CI are stored online in ghcr. not only this, also the status of build framework internals (like stuff in https://github.com/armbian/build/tree/main/lib/functions) since they also can alter a package. "development" should be sufficient.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines