Jump to content

Werner

Administrators
  • Posts

    5181
  • Joined

  • Last visited

Everything posted by Werner

  1. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  2. From these logs I cannot see any recent packages installed. Everything seems to be 23.02 which cannot be supported.
  3. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  4. Is the code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-firmware-full package installed? If not please do so via apt, reboot and retry.
  5. supposedly not a powering issue. moved.
  6. https://debug.armbian.de
  7. Those ratings don't necessary have to mean anything. A proper 2A supply can be better than a crappy 4A one. A good PSU keeps the voltage constant up to its rating and then shuts off due to over-current protection. The voltage of a poor PSU will start to break down under load, often long before its max current rating is reached. The result is having weird issues with your board. At customer grade sector its a matter of luck to get something proper. The only way to be certain, if you cannot do measurements by yourself to verify, is picking up something industrial grade. Also most SBCs like being fed with slight overvoltage. About ~5.2 volts at the source. Last but not least to compensate for losses across wiring and connectors. Some PSUs already do that. Even when labeled 5 volts measurements usually show something between 5.1 and 5.4 volts. Depending on quality like described above this breaks down under load or is kept constant.
  8. https://docs.armbian.com/User-Guide_FAQ/#why-is-there-no-image-for-board-with-bookwormjammynobletrixie-and-minimalclignomekdexfce-with-vendorlegacycurrentedge-kernel
  9. Yes this is some generic issue. We're still investigating. Since this is an issue with the build framework please refer to the proper bug report here: https://github.com/armbian/build/issues/7054
  10. clear your code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } cache directory and retry
  11. Not sure why this post should be a PSU issue. Moved.
  12. No idea if these are even exposed. Anyway check the datasheet for the board. I guess there is some schematic for it around on the web.
  13. https://github.com/armbian/linux-rockchip/pull/217
  14. Logs excerpts are usually useless. Provide logs as suggested from the build output: Try to build from main instread (I assume you tried 24.05 branch)
  15. Check your /etc/sudoers file to change sudo behavior. ????
  16. opi5pro is wip, therefore moved to staging. website falsely claims it is supported.
  17. Would make more sense if the wiringop maintainers change to /etc/armbian-release since orangepi images are based on Armbian. They forked the framework years ago, did "sed s/armbian/orangepi/g" across the whole code and added hacks to make their boards somehow work.
  18. Pre-made images for download are compressed while building an image by yourself is not by default. use xz to compress it and you should get to your desired ~250M
  19. have you removed 10-dhcp-all-interfaces.yaml:?
  20. I don't know. Not my department. Just passing information. If you want to dive into how things work (and can do improvements) everything is there: https://github.com/armbian
  21. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. Doesn't look like a kernel that came from Armbian.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines