Jump to content

Werner

Administrators
 View Profile  See their activity

  • Posts

    5831

  • Joined

  • Last visited

 Content Type 

Everything posted by Werner

  1. Werner
    ha extension is not a part of the framework. Copy from here https://github.com/armbian/os/tree/main/userpatches/extensions
  2. Werner
    I suggest to get a better heatsink and/or thermal paste/glue. Next I would at the device tree if there are thermal points defined. Perhaps they are missing. You can use the dtc tool to decompile the device tree from /boot. Output values might be in hex instead of decimal, so just in case you wonder.
  3. Werner
    Applying kernel provided DT overlay rockchip-rk3588-orangepi-5-pro-disable-leds.dtbo Meaning the overlay was applied successful. If it does not work, perhaps this means some pin definitions or whatever differ from opi sources vs ours.
  4. Werner
    Related to Again, you are using the wrong image. You cannot assume an image for the opi5+ works for the opi5b. Those are different boards.
  5. Werner
    wrong image. you cannot simply use an image for board X and assume it works on board Y
  6. Werner
    moved to staging
  7. Werner
    Attach debug serial console so you can follow u-boot logs and get an idea what the overlay is not applied.
  8. Werner
    None of these images will most likely work. https://docs.armbian.com/User-Guide_FAQ/#why-no-universal-image
  9. Werner
    This is quite old. Isn't there anything more recent? Perhaps this was fixed at some point already.
  10. Werner
    booting from sd should work even with proper mtd in place. Get usb uart adapter and provide boot logs.
  11. Werner
    Feel free to reach out and become a partner: https://www.armbian.com/partners/ @Bruno Santos
  12. Werner
    Armbian default login and password is always root and 1234. If this does not work, the image is not genuine.
  13. Werner
    I don't know, perhaps the author knows. Try. If it doesn't work, then fe's wiki is misleading.
  14. 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).
  15. 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.
  16. Werner
    moved
  17. 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
  18. Werner
    moved to tvboxes
  19. 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/
  20. 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.
  21. Werner
    moved
  22. Werner
    I'd start by comparing the device tree on a working and non-working image.
  23. Werner
  24. Werner
    Probably a new product. Images are not compatible unless specifically marked as such.
  25. Werner
    https://docs.armbian.com/User-Guide_Getting-Started/#vendor-current-edge-or-legacy
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept