Igor

Administrators
  • Content Count

    10679
  • Joined

  • Last visited

Everything posted by Igor

  1. Good. I would only add a link to search where it is mentioned. Perhaps to the general armbian.com/search
  2. You didn't understand correctly. We don't want to have anything to do with the hardware you are making. For free support, apply here: but since we have no resources to support your business or hobby, chances are none. If you support Armbian, that we can hire help, we will help you.
  3. It adjust packaging to meet our packaging format which is slightly different than Debian's. At most important that its alright.
  4. Great! Perhaps mention - in a proper tone - that they are entering trial mode with certain limitations for one week and what to do to speed things up?
  5. On most recent image this should be correct since max CPU speed in the user land was bumped to 2.4 https://github.com/armbian/build/commit/6c26c35344f283ba282a2f0adba05203440ae928#diff-e23e978e7f10e4dd5d02692593354d0b Edit /etc/default/cpufreqspeed and adjust.
  6. We always need full logs armbianmonitor -u Even with them its usually hard to determine the root of the problem.
  7. You certainly need to read your support contract first: https://github.com/armbian/build#support Better hw support and less surprises you will have with stock legacy 4.9.y kernel, which is supported by hardware maker and they will always say "yes" even they are unable to fix all problems. Even less problems you will have if you freeze kernel (armbian-config -> system) and update only non hardware specifics components / package base. If you want modern kernel, this is the minimal price to pay.
  8. We don't support 3.4.y kernel builds anymore which means there are no more updates.
  9. Also I started: for archive in $(find ${STARTDIR} -name '*.xz'); do xz -tv $archive [[ $? -ne 0 ]] && exit 1 [[ $(sha256sum $archive | cut -d" " -f1) != $(cat ${archive}.sha | cut -d" " -f1) ]] && exit 1 done on our archive to see if the problem is at our side.
  10. No, I think the exact problem is as I describe it, but I don't plan to dig into that anytime soon. You can also later fix our scripts and save us some hassle
  11. Search for "Archived versions" on that page. Impossible to miss. At least I though so until now
  12. Latest images are indeed corrupted - also decompressing is failing. I picked random older version from the archive and decompress alright, SHA is correct. Well, good that we have it but ... here we go again
  13. I am just pointing out that the problem is known and you should probably be able to find this topic on your own. Now I merged your topics here. Nothing more to say about.
  14. Then you file a bug https://github.com/armbian/config and go official way. Armbian supports native or containerised (Docker) install. https://docs.nextcloud.com/ Welcome also to fix the bug.
  15. Now read this thread and urls on that issue If we had a solution, it would already be build-in.
  16. If not found, needs to be fixed. Here are some clues to work with: https://github.com/armbian/build/issues/2207
  17. https://docs.armbian.com/Process_Contribute/ https://docs.armbian.com/Developer-Guide_Build-Preparation/
  18. Then start your exploration at download pages. There you will find links to all images that are available. Make sure to click on "Check other download options" before adding on your support dept If you don't find your desired combination, its always possible to build one. We are in the middle of upgrading our download infrastructure and some direct links might currently be misplaced. filename.sha https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-integrity
  19. Igor

    Odroid C4

    I see, then this is a bug. Thanks.
  20. In case if it doesn't work, check here: https://github.com/armbian/build/tree/master/packages/extras-buildpkgs/hostapd/debian and build from sources. But its possible that noscan need some code adjustment due to upstream changes: https://w1.fi/cgit/hostap/
  21. Igor

    Odroid C4

    You mean a clean image has that problem?
  22. It's a known bug https://armbian.atlassian.net/browse/AR-439 noted 3 days ago. No need to worry about.
  23. This WiFi chip is significantly better, but still in case of kernel upgrades, troubles can occur. We need that wireless radio department pick this up. Other than this: [115085.411230] w1_master_driver w1_bus_master1: Attaching one wire slave 00.269000000000 crc 3d [115085.420397] w1_master_driver w1_bus_master1: Family 0 for 00.269000000000.3d is not registered. things looks normal. Which can only give me a suspicion that somethings else caused that wifi fails. Kernel 5.8.y is not here very long and something would be wrong if there were no problems Try the same with older images (5.4.y) kernel.