Jump to content

Werner

Administrators
  • Posts

    5628
  • Joined

  • Last visited

Everything posted by Werner

  1. Probably because nobody implemented this yet. Feel free to do so and send a PR.
  2. Use edge or vendor for more features. current will stick to 6.12 LTS kernel which will receive fixes only.
  3. Using screen is sufficient. No settings besides baud rate (115200 for any Allwinner) need adjustments. As mentioned above make sure your serial device is correct. If you are unsure, simply - unplug - run sudo dmesg -ew - plug in and check output in the terminal with the command above. Also make sure wiring is correct. Ground to ground and rx/tx crossed.
  4. You don't have to trust/use torrents to download Armbian. All images are available via http/s download as well. We cannot do anything against people (ab)using torrent protocol for non-legal things nor can we control where these torrents spread/end up if this is your main concern. If you are concerned that an images you have downloaded is non-geniune run a check before proceeding with installation: https://docs.armbian.com/User-Guide_Getting-Started/#download-and-verfication
  5. I'd say start with the device tree. Maybe it is just not enabled? KDE 6 DE was introduce when it still was beta and I assume this never changed. Feel free to send a PR to make it stable.
  6. https://github.com/armbian/build/blob/9ff15f78966871bd737f0c8cbd23ee9fdb767b8d/lib/functions/host/prepare-host.sh#L48-L58 setting locale seem to fail. For the BTF thing either give the vm more memory (>8G), disable or enforce it as mentioned in the image and risk getting OOM killed.
  7. Radxa is probably using Allwinner bsp kernel while Armbian is using mainline. Latter barely has any support for the A523/T527 SoC pushed to already. It will take a few years to have it matured decently. You can try to incorporate vendor kernel. Start here:https://github.com/armbian/build/blob/main/config/sources/families/sun55iw3.conf and https://github.com/armbian/build/blob/main/config/boards/radxa-cubie-a5e.csc
  8. wrong. auto-login is enabled on serial and hdmi only. ssh default login is always root/1234
  9. Armbian has exactly zero in common with Android. Flashing from Android isn't supported either. https://docs.armbian.com/User-Guide_Getting-Started/
  10. Try with a fresh image on sdcard. If there are SPI or eMMC and a way to disable them hardware-wise (I don't know this board) disable those. Check if it boots. If there is no output at all with the fresh image the board might be damaged.
  11. moved Why follow some random 3rd party text when there is a documentation available? https://docs.armbian.com/User-Guide_Getting-Started/ Insufficient information. Which exact image? Try connect via ssh. If it works -> code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbianmonitor -u If not: https://debug.armbian.de
  12. A few days ago jammy and bullseye were moved to eol. While upstream may support these userspaces a few more years, Armbian does not have the resources to support more than the most current stable releases of Debian and Ubuntu, which are Bookworm and Noble at this time. You can still select them to build when passing EXPERT=yes switch to ./compile.sh but do not ask for support if something breaks. You are on your own.
  13. Why? Will cause recompilation on every build This does not exist anymore IIRC. Non-standard docker image can cause rebuild since it is now based on Noble. This is not needed since it is default behavior. Also unneeded since default is yes already.
  14. Great. Just to avoid cross-contamination. You are sure you have the Orange Pi 3 and not the Orange Pi 3 LTS model? Background: OrangePi naming scheme is kind a ridiculous, makes no sense often enough and introduces confusion. In this particular case they switch to a different PHY chip which I think was migitated by Armbian but not sure if they still have separate images. Seems like a similar topic already exists: https://forum.armbian.com/topic/34024-cannot-attach-to-phy-after-upgrade-to-202381/
  15. Hi KDE Plasma is not an officially supported DE, therefore hidden behind code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } EXPERT=yes switch. May work, maybe not. No support for it, just like for any user-built image. Example without interactive menu including all available app groups: ./compile.sh build BOARD=orangepi5-plus BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers chat desktop_tools editors internet multimedia office programming remote_desktop' DESKTOP_ENVIRONMENT=kde-plasma DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base EXPERT=yes KERNEL_CONFIGURE=no RELEASE=bookworm
  16. Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  17. Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  18. This is not Armbian. This fork is using the name Armbian without permission nor do they contribute to the core development process. Ask at their repo for help. We cannot and will not support any forks whatsoever.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines