Jump to content

Werner

Administrators
  • Posts

    5685
  • Joined

  • Last visited

Everything posted by Werner

  1. Set verbosity to 7 in armbianEnv.txt to get an idea about what happens after "Starting kernel..."
  2. Make sure the file is there and name is correct
  3. Werner

    Tech news feed

    Only if you hand over the Arab money: https://song.link/s/6X0U1NIujkYExpcho01OXG
  4. https://zuckerbude.org/armbian-using-kernel-config/
  5. Once this is merged, more recent SoC code can be rebased on top:https://github.com/armbian/build/pull/9049
  6. Never heard of that spelling "ip_tables". Anyway should be built in: https://github.com/armbian/build/blob/4e027a40d6d38d5e9072577a7e47b110914a843d/config/kernel/linux-qcs6490-edge.config#L421
  7. If that doesn't do it, try the main integration branch which for once combines all branches and for the other is actually meant to be used by megi iirc:https://codeberg.org/megi/linux/commits/branch/orange-pi-6.18
  8. First step is to cleanup and bump the sunxi patchset to 6.18. This is a major blocker. Once that is done. Patches for more recent Allwinner SoCs can be added. I started doing that but it is extremely exhausting. I have no clue how the-going managed to maintain that for that long... must be sort of masochistic or something lol. https://github.com/EvilOlaf/build/tree/sunxi-6.18
  9. Not an Armbian uboot binary. Also we started to drop vendor uboot in favor of mainline.
  10. Perhaps this one? https://www.youtube.com/watch?v=yhZahmbb03Q
  11. I never mentioned any solution. Moving your post to an appropriate location is a forum moderation task and the post was FYI only. I don't have this board nor do I know how to fix it.
  12. There are none. https://docs.armbian.com/User-Guide_Networking/#networking
  13. IIRC stuff for rock2a/f was sent to upstream uboot too. Try adding a condition to use mainline uboot as well. You can check various rockchip based boards which also have this in their board config file.
  14. 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?
  15. moved to staging
  16. 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
  17. Because this is not Armbian. This is a fork which uses the name Armbian without permission. We do not support 3rd party forks.
  18. May I ask why you do this fsck? Is there a problem with the image like not booting?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines