Jump to content

Werner

Administrators
  • Posts

    5666
  • Joined

  • Last visited

Other groups

Management Contributor/Maintainer

Profile Information

  • Gender
    Male
  • Location
    Federal republic of Germany

Contact Methods

  • Website URL
    https://github.com/EvilOlaf
  • Github
    EvilOlaf
  • Discord
    werner

Recent Profile Visitors

39795 profile views
  1. This is part of https://github.com/armbian/build/pull/8777/files And there are no changes at our end. So I assume the issue was introduced in mainline?
  2. moved to staging
  3. just noticed current kernel is broken. I assume because of upstream changes. looks like similar what I've fixed for meson64 6.18-rc7. Got it, will send pr Of course this does not explain why the image wasn't correctly assembled at all... Looking good: https://paste.armbian.de/ohagifufem ls -l|grep Odr -rw-rw-r-- 1 root root 142 Dec 2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.sha -rw-rw-r-- 1 root root 19751 Dec 2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.txt -rw-rw-r-- 1 root root 322026836 Dec 2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.x
  4. Because this is not Armbian. This is a fork which uses the name Armbian without permission. We do not support 3rd party forks.
  5. May I ask why you do this fsck? Is there a problem with the image like not booting?
  6. This is not recommended. https://docs.armbian.com/User-Guide_Getting-Started/#flash-to-sd-card
  7. While having this sent to mainline would be overall best, the faster approach in the mean time would be to send a patch via PR to this location to have it included into Armbian kernel packages: https://github.com/armbian/build/tree/main/patch/kernel/archive/rockchip64-6.18
  8. At this time we do not have plans to support it. However anyone is free to step up and provide support with a pull request. We'll happily review. Perhaps chainxs will do this since they're an active volunteer contributor already
  9. When support for Raspberry Pis has been added there was no model 5 yet. With the intention to only support the flagship the board configuration was added as rpi4b.conf. Since then support was extended across all models from 3 and up. However renaming a board config file is an issue. I already had the idea to address that but gave up on it: https://github.com/armbian/build/pull/7881 tl;dr: rpi4b image will work on all models from 3 to 5. https://www.armbian.com/rpi4b/
  10. Try to select CSC/EOS/TVB or use EXPERT=yes
  11. moved to staging
  12. No. This fork uses the name Armbian without permission and they do not contribute to the core development process. Instead they trick you into thinking that you'd get any sort of support here at our place whatsoever.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines