• Content Count

  • Joined

  • Last visited

About Igor

  • Rank
    Embedded member

Profile Information

  • Gender
  • Location

Recent Profile Visitors

18342 profile views
  1. Absolutely. And no messing up with SWAP https://forum.armbian.com/search/?q=zram&fromCSE=1 https://www.ansible.com/
  2. I already explained in my 1st reply. copy https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-firstlogin#L297-L304 exchange $realusername with your username and paste.
  3. That is expected. Later on a timer starts which delete this file: https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-firstlogin#L318-L319 We figured out that it's best to provide autologin only at first run. If you want to have it always, you have to enable it manually by creating such file or that used to work fine via armbian-config, but it needs to be checked and fixed if it doesn't work anymore.
  4. Solution is still the same. Someone has to enable it back, build kernel(s), fix possible problems and submit a patch. We are full for months ahead. https://docs.armbian.com/Process_Contribute/ https://github.com/armbian/build#support Armbian is free software and provides best effort help through community forums. If you can't find answer there and/or with help of general project search engine and documentation, consider hiring an expert.
  5. I think I tried that. Or copy config if not exists: [[ ! -f "${homedir}"/.config/htop/htoprc ]] && cp /etc/skel/.config/htop/htoprc "${homedir}"/.config/htop/htoprc File origin for PR: https://github.com/armbian/build/blob/master/packages/bsp/common/etc/NetworkManager/dispatcher.d/80-update-htop-and-offload-tx
  6. Could be broken ... don't know. Check here: https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-resize-filesystem Probably initial image size need to be set higher since resize can fail if image is filled up to 100%. https://github.com/armbian/build/blob/master/lib/debootstrap.sh#L399-L406 unless you were adding some packages on top?
  7. Need to check armbian-config, but you can try this in the mean time: https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-firstlogin#L297-L304
  8. According to your logs, not really: It's not very well tested upgrade path - if you are coming from some old build, a clean install is recommended. But that solo doesn't explain this odd behaviour. I am having one Cubietruck in the quality assurance lab and it performs within expectations, #28 https://users.armbian.com/igorp/2021-01-14_23.53.13.html Perhaps firewall rules are responsible for speed downgrade? They eat CPU and if there is a lot on CPU, network speed goes down. Allwinner A20 is not very powerful device.
  9. Without logs its hard to tell what happens. Connect serial console, HDMI console, connect to interrnet via wireless and run armbianmonitor -u Armbian use Network Manager to config networking and its pretty easy to use. So far those upgrades didn't make troubles. They are usually minor, but upgrades from Stretch to Buster could be troublesome. My orangepiplus2e test device is running Ubuntu based Armbian, so its not completely the same, but it performs as expected http://ix.io/2Mba Initial locales are set based on your location. Keyboard is added,
  10. This board is not supported but we still keep it in the autotest facility - I can't check which card is used, but board performs normally - it can be used http://ix.io/2M8V
  11. https://docs.armbian.com/Process_Contribute/ Make sure to test before.
  12. What is wrong with that application? It tells you that you need to supply logs, do that, ... if you don't, you don't need to do anything. No logs, no bug. But since @zerkalica already provided needed data and I also managed to confirm, bug exists. Who will fix this one? Don't know. We are overbooked.
  13. We have to save resources from IMO unimportant cosmetical problems and especially on a dirty private kernels / dead ends. This is probably some smallest problem there and especially when we can provide better community supported modern hardware interface / kernel. Which I highly recommend it to you. Any support request is a direct financial blow for us and there is a big line of people waiting and hoping we will focus on the bug they have problem with. Also not all bugs are a part of our area of (best effort) support https://github.com/armbian/build#support Since you don't support
  14. Have you made all round internet research if there is perhaps some bug in BTRFS with kernel 5.10.y? Try at least some BTRFS image with older kernel (change BRANCH=current to BRANCH=legacy) to narrow the problem down. This tells very little. There is output/debug folder for some more data ... did you use recommended host setup? Did you study https://docs.armbian.com/Developer-Guide_Build-Preparation/