• Content Count

  • Joined

  • Last visited

About tibo

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, Thanks for the message. Finally I had been able to rebuilt armbian like it was end of December twisting the vagrant files and forcing a tag for the kernel 4.19 (presently the branch 4.19.y doesn't built at all). Right now I cannot test if the last fixes about pine64so (https://github.com/janwillies/u-boot/commits/v2019.01-sopine-spi) merged by ... you works for pine64-lts boards. If it seems to not work I will open a dedicated thread. Thank again for the support. Best regards
  2. Hi, The Armbian Build no more works with Pine 64 LTS using the configuration: BOARD="pine64so" BRANCH="next" RELEASE="stretch" And appending to /boot/armbianEnv.txt: fdtfile=allwinner/sun50i-a64-sopine-baseboard.dtb I saw, a dedicated DTB is now available for LTS: /boot/dtb/allwinner/sun50i-a64-pine64-lts.dtb. I tested adapting to /boot/armbianEnv.txt: fdtfile=allwinner/sun50i-a64-pine64-lts.dtb Unfortunately the issue is the same: the booting process is failing. The Ethernet plug is blinking but Linux didn't boot. I also used the images (with the kernel "next") published on https://dl.armbian.com/pine64so but no ones work, changing or not the fdtfile file. Last time I build images it was end of December 2018 and the images worked (with the fix). So, I getted the state of the Armbian Build repository around end of December, but built images are still don't work. On my side the "debugging" is ... very difficult: HDMI doesn't work and UART as well. So I do not know what happen during the boot. Someone know if I can recover the state of Armbian Build of end of December (with all dependencies)? Someone know if the current images from https://dl.armbian.com/pine64s are working with Sopine? Thank for your help! Best regards
  3. Hi, I'm not sure if it is the right place, however I spent a couple of days to figure out how to boot a pine64-lts board using the Armbian build. I guess it can be also the case for the pine64-sopine boards. Finally, with the following configuration and an additional step it works!!! The Armbian configuration: BOARD="pine64so" BRANCH="next" RELEASE="stretch" As far I understood, even if pine64so is selected, the Armbian build selects the DTB of Pine64+ boards. So uboot is lost when it tries to locate the kernel ... To fix it, the file /boot/armbianEnv.txt can be manually edited forcing the DTB to use: fdtfile=allwinner/sun50i-a64-sopine-baseboard.dtb The boards are only used in a Docker Swarm clusters, so I cannot confirm if screens, keyboards or others are working fine. Best regards