• Content Count

  • Joined

  • Last visited

  1. So.. guys, i see here that you also have a problem of boot getting stuck very early in the process. my v7 board is stuck here TIM-1.0 WTMI-devel-18.12.1-e6bb176 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 1.155V more often than not (i'd say s a 70% chance of getting stuck here). Once it boots it is relatively stable with Buster. How did you solve this issue? Also, i do have the same problem of CPU not working higher than 800MHz.
  2. Thank you. i also tried to re-image the using ubuntu. when i boot with default kernel root@ESPRESSOBIN-SRV-02:~# uname -a Linux ESPRESSOBIN-SRV-02 4.19.20-mvebu64 #5.75 SMP PREEMPT Fri Feb 8 09:54:18 CET 2019 aarch64 aarch64 aarch64 GNU/Linux it works relatively ok, but if i upgrade to latest one using apt-get upgrade (or dist-upgrade), the kernel always crash on boot. specifically, that would be Linux kernel, version 4.19.41-mvebu64
  3. every second boot, there is a kernel crash: Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 4.19.20-mvebu64 ( (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #5.75 SMP PREEMPT Fri Feb 8 09:54:18 CET 2019 [ 0.000000] Machine model: Globalscale Marvell ESPRESSOBin Board [ 0.000000] earlycon: ar3700_uart0 at MMIO 0x00000000d0012000 (options '') [ 0.000000] bootconsole [ar3700_uart0] enabled Loading, please wait... starting version 232 Begin: Loading essential drivers ... done. Begin
  4. as per title... i have 2 boards running armbian (Debian version). Even if the mac addresses on /boot/armbianEnv.txt are set differently, all nic cards of both boards, have the same exact mac address, specifically f0:ad:4e:03:64:7f this of course creates a lot of problems because i cannot connect my 2 boards in the same network here is armbianmonitor from the 1st board - here is the same for the 2nd board - apparently i am not the only one