• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map






Everything posted by Igor

  1. It's a bug in Ubuntu user land - I didn't investigate further: https://bugs.launchpad.net/command-not-found/+bug/1824000
  2. Do you have Ubuntu "Focal" or Debian "Buster" ? Change that to "buster"
  3. There is an error in PPA handlind under Debian -> you need to replace focal with buster in /etc/apt/sources.list.d/ Then run apt update and upgrade again. But remember this is just a suggestion - I don't know if it will help.
  4. I made a quick install on a device that I am doing some other tests. Orangepi Lite 2, which is also ARM64 and there are no issues. Openhab is installed from armbian-config in no time and works. Perhaps try also Bionic build. I can check on the exact hardware in next days if this will not help. If this is not a hardware issue, there is little we can help. We only provide a base where this application can work.
  5. No, we were thinking about that, but never got there to start working on that. For a few people that maintain this, its low priority.
  6. - which image exactly? (Link!) - how good is your power supply? - can you provide serial console logs? Me to. You are not reading and understanding what a label "for testing only" means. At this stage, we simply can't guarantee more than that. Besides, check software licence before complaining. Here is a quick summary how support goes: https://github.com/armbian/build#support We are not there yet, since this board is not supported yet. Will be soon, but right now, it is not. Edit: Moved to development forums since "Board not start" section is for stable builds only.
  7. Chromium is a larger project than Armbian. If bug is there ... there is little we can do about. You can try to: - compile from sources - https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-beta
  8. I tested Debian Buster Desktop on A64 board - which is almost identical - and Chromium works perfectly fine. Out of the box. Do you perhaps try to run Chromium with root username?
  9. This is quite normal. I need 12 minutes for the same task together with SD writing and verifying - fastest desktop class hardware, native building. But the biggest problem is exactly Debian package manager - which is slow / uses only one core and if we stick to Debian there is nothing we can do about. At least not without serious investment into the core.
  10. We are just a small step away from embedded world. Where stuff is compiled from sources in 100% of cases. Not just kernel, everything. You are lucky that you have near to some everyday Linux experience. Get fresh original image https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity you will be few hours faster. https://github.com/armbian/build#support
  11. It is build with armbian tools and its similar, but different enough that we don't support it. If you need some modules, you can enable them. Your contribution will be accepted in case it doesn't break anything, but we have no resources to do this instead of you.
  12. - describe what you are doing - show your userpatches/config-example.conf (I assume you are using that default one) - what is your build hardware?
  13. Igor

    Pinebook Pro

    This script was made by/for people that start Unix in 90" or later. Close enough A few tips: - use mainstream repository https://github.com/armbian/build at least for the 1st time. - https://github.com/armbian/build#build-parameter-examples First example is the key you are missing. PinebookPRO is in the CSC/WIP section. - support for Vagrant (method I never used) is not the best. I suggest native or Docker. In case you get into the troubles, supply logs (output/debug) here https://forum.armbian.com/forum/12-armbian-build-framework/ Booting from SD card, running nand-sata-install and installing to BTRFS should get you there. It is also possible to create SD card with ready made BTRFS or even with LUKS ... but not recommended for 1st time build. I don't know how good and how bug-free those features are but consider software support for Pinebook PRO as experimental, fragile ... but developing fast.
  14. The problem is (probably - log too short) in MAC address changing. Try to find out hot to fix MAC with the driver and check if our fixes are present: /etc/NetworkManager/conf.d/10-override-wifi-random-mac-disable.conf [connection] wifi.mac-address-randomization=1 [device] wifi.scan-rand-mac-address=no They are effective with many (probably all) on-board wireless chips. We don't try to fix problems in 3rd party hardware so you are on your own - worst case = talk to driver maintainer, check different driver, get different WiFi dongle. Also delete stuff in /etc/NetworkManager/system-connections
  15. AFAIK none. Just kernel is not very well tested, but if it works for you ... keep it up. The same goes for Stretch.
  16. Mine is shortly clocked down to 1Ghz due to functional thermal throttling. A heat sink is mandatory if you want to run it at 1.6 - 1.8
  17. We have to fixate sources to certain commit ID https://armbian.atlassian.net/browse/AR-178 and this will help a lot with making a build (more) 'stable'. In general also with dealing more with (auto) testings and by polishing this release process over and over again. We can set a date for 1st RC0, but IMO further should be upon release leader to decide. There are always potential 3rd party show stoppers. His limits are already set with the release borders and has to come out with a 'stable' release by the end of the release month. We could perhaps define minimal standards for that? "All images must boot and if there is a problem we were not able to fix, write it down"? My 2c
  18. Yes, forgot. https://github.com/armbian/build/commit/24013582eba4ad3300d0996cf9afa3dde8513327
  19. Agree. Some bugs must be present, otherwise life would be too simple Need to investigate why this is happening. Did you install header manually "apt update; apt install linux-headers-current-sunxi" ? or via armbian-config?
  20. It works fine on Nanopineo2black image since yesterday. (tested) The reason for discrepancy is here. Neo2 uses different config / DT.
  21. This is not the case. He only need to update since we have updated DVFS table in 5.4.y with enabled 1150Mhz.
  22. Next kernel v5.97 is not very stable. Power cycle instead reboot helps (try few times) and when you (hopefully) get your system back, do this: https://forum.armbian.com/topic/12210-armbian-1911y-release-notes/
  23. Pine64 does not provide enough power for HDD. Use powered HUB in between.
  24. - do you have rootfs on that drive? - why don't you use supplied tools? (nand-sata-install) - logs logs logs
  25. This is a bug, somewhere in ATF / boot loader areas. Hard to say why it doesn't proceed ... needs to be investigated by someone that have: knowledge, time, hardware, ... IIRC I have seen this kind of behaviour on some other board, but don't recall what is the exact cause ... Let's wait for some clues and ideas.