• Content Count

  • Joined

  • Last visited

  1. Hello martinayotte, thanks for the fast reply. I modified the file /boot/armbianEnv.txt with verbosity=7 and console=serial as suggested. I used putty on an other device. This is connected to the UART0 on cubietruck (4 pin header close to the USB ports). I think, that this is the serial-debug. Right? No luck. The kernel is not starting. The output is still the same. See attachment. armbianEnv.txt log_from_putty_with_verbosity=7_console=serial.txt
  2. On my cubietruck I have tried the Armbian_5.75_Cubietruck_Debian_stretch_next_4.19.20. For me it looks that u-boot loads the files, but the kernel will/can not start. Attached the output from the console. Rarly I get some additional output on the console like "Uncompressing Linux... done, booting the kernel." but nothing happens, or some wild output from wrong instructions which leads to a reset. I have also tried "Armbian_5.59_Cubietruck_Ubuntu_xenial_default_3.4.113_desktop" to exclude some mainline / legacy kernel issues. But no luck. With some older versions (e.g. 5.20) I ha
  3. I have an similar issue. I am using an Cubietruck. It works fine with an older NAND image. I am trying to start ARMBIAN (different versions, e.g. Armbian_5.75_Cubietruck_Debian_stretch_next_4.19.20) from a SD card (2 different ones). I have also used different power supplies. The last message on HDMI and Console is "starting kernel" but nothing happens. Sometimes with an reboot sometimes not. Also an USB mouse and keyboard will not activated. So I assume the kernel is not started. So I reboot to the old installation. After that I can read and manipulate some files. So I as