Igor

Administrators
  • Content Count

    8945
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Everything posted by Igor

  1. It's normal. We use modern kernel (mainline + hundreds of patches) where features are ported step by step. This process is slow, expensive and its not finished ... some features are never ported and there is nothing we can do about. If you need this - use old kernel with all the bugs and without any support or invest into R&D. Third option is waiting. If feature exists, but its not enabled do some research how to enable it.
  2. Updated to 4.4.8 https://invisioncommunity.com/release-notes/448-r89/
  3. Modern kernel code - when you use armbian-config way of installing kernel sources (on Debian Buster or Ubuntu Bionic based Armbian) - you only need to go to the source directory and run "make zImage|Image" and you are done. In some case some wireless drivers might have issues with compilers ... but don't take this feature as granted yet.
  4. All you need to do is: apt install wireguard-tools modprobe wireguard
  5. Copy / paste in action With an exception of wireless it should just work with a normal image ... but I couldn't find/see which wireless chip is used?
  6. This does not give you any warranty for functioning. Hardware is almost always failed at some point/somewhere when its released by hardware folks. By default. Software is searching and fixing defects and make it possible that you some day run (fairly stable) Linux distribution (or something similar) on it. Pine64 folks are hardware designers in 1st place, sellers in 2nd and are poor at software support. Its not just their fault to be fair, but also from users which expects/demands top quality but are not willing to pay for that. This is not industrial hardware but yet another development board for masses where software support maturity is leveraged mainly to community. They (Pine64) are already working with other projects ...
  7. /etc/update-motd.d/10-armbian-header: line 25: /usr/bin/toilet: cannot execute binary file: Exec format error /etc/update-motd.d/30-armbian-sysinfo: line 171: /usr/bin/tr: cannot execute binary file: Exec format error /etc/update-motd.d/30-armbian-sysinfo: line 171: /usr/bin/uptime: cannot execute binary file: Exec format error /etc/update-motd.d/30-armbian-sysinfo: line 189: /usr/bin/tr: cannot execute binary file: Exec format error It looks like file system corruption ... which can be caused by many things. There are at least three different boards hw revisions, many different eMMCs ...
  8. There are changes http://ppa.launchpad.net/mutlaqja/libgphoto2/ubuntu/dists/bionic/ dated few days ago. Your problems started then?
  9. Hardware design and sales market? There are "me too" projects, upgrades, some new exotics, fine tuning and some adventures like Pinephone. Software side of this market still has years to fix all half working stuff that is already on the market. Some features waits for years (power management on H3 for example, video acceleration on Allwinner is not implemented yet, opensource mali drivers are not there yet ...) From our POW its busy like hell while financing software support anyway goes mainly from other sources or is not paid at all ... since board makers claim to operate below or at zero profit. Cash raised with Kickstarter is not near enough to fund such projects, but its a nice add-on. Yes, it looks that way. Probably not much difference from S905X3 with older chips which are well supported by now.
  10. Do you use the same version of Ubuntu?
  11. What is your system time when you try to install packages?
  12. Special Armbian build script engine know-how is not needed for this challenge. Relevant code location was already added in my previous post. The rest - solving the actual problem - has to be done manual first, then a patch (all four of them to solve for other kernels too) has to be modified. When your modified patch is adjusting post install scripts properly, you submit changes to the code. Take your time. If I put this task on my 2do list it will surely take months - a year - never. I rather help you to solve it even this represent more work.
  13. Is 3rd party software which you are trying to use on Armbian build for arm/arm64 ? If not, its normal that it fails.
  14. This is correct way but it can fail in case of: - hardware defects (bad SD card, failed powering = very common) - broken packages This you need to ask Docker specialists, but I don't think you need to do anything ... Docker engine upgrade could be broken, who know? Not an Armbian issue.
  15. Yes, if not found in the release documentation. And it will remain this way until you/somebody submit fix to the build code. Good thing is that after this RFC there are less files to adjust: https://github.com/armbian/build/blob/arm64/lib/compilation-prepare.sh#L20-L42 https://github.com/armbian/build/tree/arm64/patch/misc
  16. yes. I wrote the possible name (check with lsmod) and a link to the manual. Read them.
  17. It works well with Armbian while here with Odroid N2 there are some other kernel related troubles. Not just with ZRAM. We will release modern kernel, where this works as expected, soon.
  18. It's installed by default but it doesn't support mainline kernel. Why? Because its completely different, certain advanced power management features are not yet ported yet and someone has to invest a lot of time to develop completely new tool. Until there is no tool, there is not possible to do this in a simple manner. Disable in armbian-config -> hardware and blacklist wireless module (name is xradio_wlan or something)
  19. Still waiting for a MAC/Vagrant user that would write what shell be done and send a pull request to the documentation.
  20. Its also written in FAQ and the download pages and in "Getting started" ...
  21. IHMO u-boot bumping is not that critical and can wait for next major release. Time for proper testing, not just for adjusting patches, is missing component I would like to start following this if there will be no major oppositions to the plan ... I am probably travelling in the early December. In any case its busy month for all.
  22. You already sort out patches? Then we can perhaps squeeze this in by the end of the month?