Jump to content

Werner

Administrators
  • Posts

    5160
  • Joined

  • Last visited

Everything posted by Werner

  1. Which is exactly the same as armbian-config but with code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } sed 's/armbian/orangepi/g'
  2. https://docs.armbian.com/Developer-Guide_Welcome/#command-line-syntax-has-changed This also kind of applies here: https://zuckerbude.org/armbian-using-kernel-config/
  3. Hi, Armbian by itself does not accept new boards without funding/agreement. However anybody can contribute code via pull request and add community support for it. https://docs.armbian.com/Process_Contribute/
  4. moved. question is too unspecified.
  5. do-release-upgrade most likely will not allow you to update to Noble until this date. None. Lunar is EOL, repository has been removed.
  6. Make sure to - write SPI during the mentioned armbian-install process - that /boot directory has been populated on the NVMe. If not mount and copy files from sd manually there.
  7. Install matching rootfs package for your hw, whatever it might be.
  8. Yeah cpufrequtils is deprecated. The way to go today seem to use linux-cpupower. No idea though how well this works on SBCs.
  9. If you want to upgrade the userspace flavor on top (like Jammy to Noble for example) it is indeed recommended to start from scratch. If you want to upgrade the Armbian core components like firmware, kernel and boot-loader, these upgrades are shipped as regular apt package.
  10. For Armbian updates regular code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } apt update && apt upgrade will be sufficient. If you however want to change your userspace (like Jammy to Noble) this is out of scope of Armbian and upstream tools (like do-release-upgrade in case of Ubuntu) have to be used. Armbian firmware and userspace are two pair of shoes. Armbian cannot handle userspace upgrades by itself simply due to lacking of both human and financial resources for development and testing lots of various scenarios. This is also the reason why doing this is not recommended and therefore entirely unsupported by us.
  11. mainline support in 6.8 is to be considered experimental at most. Breaking is likely since it is bleeding edge. Feel free to use an image from earlier release. I hope at some point things get rebased on 6.10-rc where lots of new stuff hit mainline.
  12. Maybe. However nothing we could do anything about.
  13. https://archive.armbian.com If it is not there its gone.
  14. Odd. It is enabled in config:https://github.com/armbian/build/blob/aa2d4696cac76148d01977f63cc831e492c0f7a2/config/kernel/linux-rk35xx-legacy.config#L2945 Have you installed armbian-firmware-full? Maybe just the firmware is missing.
  15. Tried with code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } modprobe rtw89?
  16. For Ubuntu to say: code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } do-release-upgrade One thing to mention is that code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } do-release-upgrade usually does not work until the first point release. So retry once Ubuntu 24.04.1 has been released. Currently expected for August 15, 2024
  17. Try this: https://github.com/armbian/build/pull/6694#pullrequestreview-2096146300
  18. This is a command provided by userspace and has nothing to do with Armbian. Armbian related packages will be installed - if available (not the case for Lunar. non-LTS upstream userspaces are unsupported in general by Armbian) - and if firmware is unfrozen https://docs.armbian.com/User-Guide_FAQ/#can-i-upgrade-my-userspace-like-buster-to-bullseye-or-focal-to-jammy
  19. known issue https://github.com/armbian/build/issues/6568
  20. yes, it is. 5.2V to .3 seems to be a reasonable value.
  21. Voltage might be an issue. Most SBCs while rated for 5 volts prefer slight overvoltage, last but not least to compensate for voltage loss across wiring, connectors and the PCB itself. Even PSU sold by xunlong in combination with the OPi5, also while rated for 5v actually outputs about 5.2V. I verified this on an OPi5 month ago by measuring at the voltage source which was between 5.2 and 5.3 volts and the USB-A connector on the board which dropped to 5.0 volts when putting on a heavy CPU load. Since the PSU itself has way more than enough power voltage there were constant. Now think about what happens when your PSU only outputs barely enough wattage. Not only the voltage drop mentioned earlier will be there but also the voltage will break down at PSU level which increases the overall voltage drop to a (from a electronics perspective) crazy level. So if your input voltage is 5 volts only it will drop below this and malfunctioning is VERY likely then. I'd test this on the 5+ 32G model if I had one. But mine has 16G memory only.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines