• Content Count

  • Joined

  • Last visited

About Igor

  • Rank
    Embedded member

Profile Information

  • Gender
  • Location

Recent Profile Visitors

16465 profile views
  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.