Jump to content

Igor

Administrators
  • Posts

    13843
  • Joined

  • Last visited

Everything posted by Igor

  1. If you use our build and you upgrade/change kernel via armbian-config you don't need to worry about that. https://github.com/armbian/build/blob/development/config/bootscripts/boot-espressobin.cmd#L22-L23 Mainline uses different DT name (armada-3720- espressobin.dtb) and it could be aligned once but now is as is. Mainline kernels have much higher quality standards than vendor kernels which are usually full of dirty tricks and quick patches. Usually, vendor kernels have more special advantages but I think there are no more reasons (advantages) to stay on a kernel 4.4.y anymore.
  2. What is consing? You have a kernel version in a filename. "default" = old kernel, which is 4.4.something for this board "next" = new kernel, which is 4.14.something for this board If you want to upgrade your default 4.4 to 4.14 you need to switch branches. Manually or with armbian-config.
  3. We promote 4.14.y simply because it is a better choice now. Click on area rounded with red color ... to see other (older) choices.
  4. Correct. There is no NAND support in the modern kernel. You use it only with old kernel builds ... Jessie and Xenial. Kernel 3.4.y is too old for Bionic or Stretch.
  5. With a clean image. Not via upgrade. Well, even I think I fixed something, this might not always be true. Sometimes some vital part is somehow lost in the commit phase. Will check. The same. I am not sure everything already works as expected. I haven't check any upgrades yet except installing a desktop on top of the latest CLI image. I agree. Let's plan this for next.
  6. Are you holding a boot key? Images should work. I'll check them again when I am back to the office.
  7. The modern kernel has a different way of setting hw features. Use armbian-config and/or read this: https://docs.armbian.com/User-Guide_Allwinner_overlays/
  8. Blacklist in-kernel driver and search around for more recent known to work drivers (sources), install headers and compile the module. Repeat until you find a working one. When you find a good working one, we can once replace them with those shipped with the kernel. Ideally: send a patch against kernel source.
  9. You have to boot the board first. Usually, it's not just kernel and u-boot, but up to few other (pre)loaders. Packages optimization is a fairly simple task. If our default package base is a too much, use PACKAGE_LIST_RM parameter when building an image to remove what you might not need. https://github.com/armbian/build/blob/development/lib/configuration.sh#L219-L222
  10. Our build system downloads most used compilers but to tell you which exactly is appropriate for Hikey board u-boot/kernel sources ... no idea. You can try to play around this way: 1. Define a board config https://github.com/armbian/build/tree/development/config/boards 2. Define a source config https://github.com/armbian/build/tree/development/config/sources Check this example for RK3328 ... https://github.com/armbian/build/blob/development/config/sources/rk3328.conf#L32-L43 default branch, kernel 4.4.y need to have a version higher or equal than 6.3 KERNEL_USE_GCC='> 6.3' while kernel dev branch 4.17.y needs KERNEL_USE_GCC='> 7.0' ... u-boot and atf have their own settings. We know that This board is aarch64 (https://github.com/armbian/build/blob/development/config/sources/rk3328.conf#L1) and this way systems knows which compiler to choose. Sometimes trial and error is the fastest way. We use those: I hope you will find those hints useful.
  11. Well, you need to start with an image. If you start with CLI, you should have more desktop install options now. If not ... then I need to run rebuild again. Desktop versions should be installed by default. That's good. Uninstalling should be possible from armbian-config menu ... but BT icon could remain there. On your 1280x1024 monitor? Well, probably it doesn't have this resolution and pick 1st appropriate one. Still better than having some complete invalid. Anything is possible but do we need to mess up with changing this? It can look ugly if not done properly. Yes, I noticed those problems but dunno what's the problem atm.
  12. Good! Kernel power the board(s) low-level functions. Not bash scripts (Dietpi). Its Armbian kernel in both cases. https://stackoverflow.com/questions/12132260/what-is-the-difference-between-shell-kernel-and-api
  13. Nothing obvious in the logs. Is your USB hub self powered?
  14. BTW. C2 boots with 2018.03 (with additional patch) but needs more testing. Dunno if everything is ok.
  15. The most important information is missing: armbianmonitor -u .... also refference to Dietpi is useless. Which kernel, that are you using on RPi, is good with the card. Try changing governor: nano /etc/default/cpufrequtils GOVERNOR=performance service cpufrequtils restart And also try older kernel 3.4.113 ...
  16. O.K. I can only put this to the known bug list for now. Most likely settings got messed up. Better just use 4.14.y until this is fixed - you can run the latest image but only downgrade kernel. If you have time and knowhow to investigate, here are working sources for reference http://apt.armbian.com/pool/main/l/linux-source-4.14.14-next-cubox/
  17. There are no known upgrade problems with BananaPi boards. You will need to provide more/all possible data, verbose serial logs, ... Can you try the same on another (good) SD card?
  18. Understand. But what did you run before, exactly which kernel? I know that we have 4.16.8 now. Can you run armbianmonitor -u to see logs of the working system.
  19. On which kernel? If I understand correctly ... Cubox booted to new system fine, only audio was missing?
  20. Yes. But also a normal build can be upgreaded to latest beta build. Wrote on mobile
  21. You can try to boot manually but later you need to downgrade u-boot. I am already fixing things in the repository. http://apt.armbian.com/pool/main/l/linux-u-boot-cubox-i-next/ .35 = ok .38 = broken
  22. https://docs.armbian.com/User-Guide_Allwinner_overlays/
  23. That was added. I rebuilt nightly images almost for all boards. To test build system features and that anyone with any board can join testing. Images have to be browsed on dl.armbian.com Also remade: - Espressobin - C2 - Cubox (due to the bug in NEXT u-boot)
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines