Werner

  • Posts

    2646
  • Joined

  • Last visited

Everything posted by Werner

  1. Use Spoiler next time when posting large stuff.
  2. https://docs.armbian.com/User-Guide_Fine-Tuning/#how-to-toggle-verbose-boot
  3. Put a serial console to it and check output. If necessary set verbosity to 7 in /boot/armbianEnv.txt
  4. Userspace upgrades (like Buster to Bullseye or Bionic to Focal) were never actively supported by Armbian.
  5. https://github.com/armbian/build/pull/3115 Test with all userspaces (Buster, Bullseye, Focal...) and give feedback if issue is solved. I do not have time to do that.
  6. Maybe some of that is useful: https://docs.armbian.com/Hardware_Allwinner-H3/
  7. Duplicate https://forum.armbian.com/topic/18840-armbian-on-cloudnetgo-cr19-rk3399-tv-box/?tab=comments#comment-128064
  8. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs). With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported. Your report is invalid for one or more of the following reasons (non-exhaustive list): it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)
  9. Because Buster is a Debian Release and Focal is a Ubuntu release. From Armbian's point of view they are identical since our images share the same kernel and u-boot package.
  10. duplicate https://forum.armbian.com/topic/18831-r99-box/?do=getLastComment
  11. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs). With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported. Your report is invalid for one or more of the following reasons (non-exhaustive list): it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)
  12. Split into new topic since has nothing to do with the existing one. Make sure to read the pinned topics and FAQ in this section.
  13. Glad you could figure it out. I have added a note regarding this to the documentation: https://github.com/armbian/documentation/commit/6b9bceedb28ff3b3d0590b21e9ca4a52487bb22b
  14. About forum operational status:https://status.armbian.com/785767245 No idea where your issues come from. About SPI: Maybe you need to set additional parameters:https://docs.armbian.com/User-Guide_Armbian_overlays/#notes-regarding-spi-and-i2s-overlays
  15. I have split the related posts into a new topic. I understand the issue now. I guess something like this needs to be implemented: https://askubuntu.com/questions/533786/how-to-generate-linux-tools-packages-for-customized-kernel However due to lack of ressources and low demand we rely on external help for such implementation like we do on most other user wishes. Also make sure to check https://docs.armbian.com/User-Guide_FAQ/
  16. code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } modprobe code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } usbip_core usbip_host to get them loaded and use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } lsmod to make sure they are there.
  17. Yeah, would also not make much sense to backport those to 5.10 since 5.15 will probably be next LTS release and is only a few month ahead and probably will include those patches already.
  18. Hm cannot remember that I had such issues...but also cannot remember if I ever launched a program that required root @NicoD can you confirm such behavior? Btw best method providing information about your system: Providing logs
  19. Yes, Bullseye will be supported while Buster phases out but may take a few additional month to get things prepared.
  20. Those USB-C connectors on SBCs are often for power supply only. Probably the same for R1+ http://www.orangepi.org/Orange Pi R1 Plus/
  21. usbip is enabled as module. https://github.com/armbian/build/blob/6d82498bec2ab95c80b125d7543f70bd2dc480c6/config/kernel/linux-meson64-current.config#L6713
  22. Moved to Common issues / peer to peer technical support