• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map





Everything posted by Igor

  1. There is some movement upstream https://www.debian.org/vote/2019/vote_002
  2. And what changed "today"? Only logs (armbianmonitor -u) can give valuable information.
  3. The procedure is very simple and 99% of people does not have problems. This 1st login experience can be improved a little bit but not much. You need to: - login somehow (this could be done automatic but we would need to sacrifice some security) - change root password (this should be done by repeating password. no other go) - username creation. (well, this could be shortened by not asking for extra fields, but username and Name is a must to get from you) You have troubles with latest image but older is working OK? Builds are manually tested only for supported boards ... new release is coming this week. Perhaps you shell try that. 3328 chips are well support but expect that not everything works. Especially when it comes to Chromium and multimedia support.
  4. armbian-firmware = minimal blobs that are needed that on-board wireless function + few popular ones = https://github.com/armbian/firmware - full = + everything else https://kernel.googlesource.com/pub/scm/linux/kernel/git/firmware/linux-firmware.git You can install one of those, while source package, headers and armbian-config are optional. Also armbian-firmware if your will not be running any wireless. Kernel = image + dtb package. Those are the core.
  5. If you started with a desktop image - all you need is to follow instructions. If you miss one point (creating a user) you won't get a desktop ... and you are on your own to fix it. Start with latest desktop image and read & respond to 1st login procedure.
  6. How is this possible? We haven't put out a kernel upgrade yet. At least not on a stable kernel branch. Nightly or development builds are for testings only and anything can happen there. This board does not have anyone that would acknowledge this issue and since board is also among "not supported" ones upgrades are never tested. Why this board doesn't have attention? Because we already support too many of them. Start with research is your best go. First would be to use our kernel with upstream device tree blob ... which can also be a solution.
  7. We have absolutely no control over Debian packages located at debian.org. Wrong forum/place you are reporting this problem -> perhaps Debian armhf maintainers?
  8. Perhaps driver authors or fbtft maintainer? https://github.com/prius0304/fbtft---SSD1322/blob/master/fb_ssd1322.c#L175 https://github.com/notro/fbtft/wiki
  9. The problem might be here. Branch default is legacy kernel version 3.4.y which is EOL. Features which you need might not be supported and we are also officially ditching it next week. NEXT is 4.19.y which will be upgraded to 5.3.y soon.
  10. Which image do you use (is there a desktop in the name?), did you create normal user in the process? (if not its normal you have no desktop) ... and where are your logs (armbianmonitor -u).
  11. That is correct procedure. Have you reboot? Version is the same anyway. Did you check build date ... what have you changed?
  12. Try this version https://dl.armbian.com/odroidc2/Debian_buster_dev_minimal_nightly.7z
  13. Start with R&D, perhaps here: https://wiki.debian.org/NetworkConfiguration
  14. Mine works. Perhaps there is some problem with an upstream Debian repository you are getting updates from. No idea. It looks beyond Armbian - I am unable to recreate.
  15. Did you try with some other SD card?
  16. 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.
  17. Updated to 4.4.8 https://invisioncommunity.com/release-notes/448-r89/
  18. 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.
  19. All you need to do is: apt install wireguard-tools modprobe wireguard
  20. 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?
  21. 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 ...
  22. /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 ...