Jump to content

Werner

Administrators
 View Profile  See their activity

  • Posts

    5819

  • Joined

  • Last visited

 Content Type 

Everything posted by Werner

  1. Werner
    Armbian default login and password is always root and 1234. If this does not work, the image is not genuine.
  2. Werner
    I don't know, perhaps the author knows. Try. If it doesn't work, then fe's wiki is misleading.
  3. Werner
    You can try the following: After writing to nvme and spi do NOT reboot but mount the nvme drive to a random directory and check in /boot/armbianEnv.txt if the UUID matches the one from the nvme. If not, correct it (check blkid).
  4. Werner
    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.
  5. Werner
    moved
  6. Werner
    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
  7. Werner
    moved to tvboxes
  8. Werner
    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/
  9. Werner
    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.
  10. Werner
    moved
  11. Werner
    I'd start by comparing the device tree on a working and non-working image.
  12. Werner
  13. Werner
    Probably a new product. Images are not compatible unless specifically marked as such.
  14. Werner
    https://docs.armbian.com/User-Guide_Getting-Started/#vendor-current-edge-or-legacy
  15. Werner
    The related PR states this was tested. @Efe Çetin can you confirm this still works as expected?
  16. Werner
    https://debug.armbian.de
  17. Werner
    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.
  18. Werner
    Probably because nobody had use for those until today. Feel free to send a PR adding whats missing.
  19. Werner
    https://www.armbian.com/download/ https://github.com/armbian/os/releases https://github.com/armbian/community/releases
  20. Werner
    Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  21. Werner
    diy image and you get it immediately
  22. Werner
    no clue. needs testing. perhaps it just works. kernel sources are the same as rpi os.
  23. Werner

    Odroid M2 16G

    Werner replied to Kasnoa's topic in Rockchip

    There is none. Its csc device. Community supported. You are community
  24. Werner
    moved
  25. Werner
    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.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept