Aciel

What's going on with 'Armbian_21.02.3_Nanopct4_focal_current_5.10.21_mate_desktop.img'? There is no /boot contents at all.

I have also noticed the same thing. I downloaded MATE image and there was nothing in /boot Only the XFCE image has /boot contents.

@Igor I flashed the 19.11.3 (kernel 4.4.192) image and it booted right away (I didn't hold the boot button) and I get to the console. Set user account, etc and I'm in desktop. Now the diagnostic part about what is wrong with the new images. When I flashed the 19.11.7 (kernel 4.4.208), this is what my blkid said (sda = sdcard Armbian is flashed to) # blkid /dev/loop0: TYPE="squashfs" /dev/mmcblk0: PTUUID="b811ee1f" PTTYPE="dos" /dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="LIBREELEC" LABEL="LIBREELEC" UUID="2211-5513" TYPE="vfat" PARTUUID="b811ee1f-01" /dev/mmcblk0p2: LABEL="STORAGE" UUID="a321c910-4860-4321-bec0-31d20884f00c" TYPE="ext4" PARTUUID="b811ee1f-02" /dev/sda1: PTUUID="02f47b31" PTTYPE="dos" PARTUUID="cf28ecd8-01" /dev/sdb1: LABEL="Aciel" UUID="4E1AEA7B1AEA6007" TYPE="ntfs" PARTUUID="51e1ebcd-01" # Here is the one from 19.11.3 (kernel 4.4.192): # blkid /dev/loop0: TYPE="squashfs" /dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="LIBREELEC" LABEL="LIBREELEC" UUID="2211-5513" TYPE="vfat" PARTUUID="b811ee1f-01" /dev/mmcblk0p2: LABEL="STORAGE" UUID="a321c910-4860-4321-bec0-31d20884f00c" TYPE="ext4" PARTUUID="b811ee1f-02" /dev/sdb1: LABEL="Aciel" UUID="4E1AEA7B1AEA6007" TYPE="ntfs" PARTUUID="51e1ebcd-01" /dev/mmcblk0: PTUUID="b811ee1f" PTTYPE="dos" /dev/sda1: UUID="dd3833fd-2ea5-411b-a48d-91968fe7241f" TYPE="ext4" PARTUUID="cf28ecd8-01" # 19.11.7 = creating dos partition and unable to boot 19.11.3 = creates ext4 partition and it boots normally

Did the exact thing, no result. Board turns on (red light is there) but it won't boot from sdcard. Will the try last image that worked for me now.

I tried with holding the boot button then power up the board, and kept holding the boot button for like 10 secs = Still won't boot. I'll re-try 19.11.3 (kernel 4.4.192) image now and post result.

Yes. No, I only hold the power button ~2secs when 1st starting the board and it always boot from sdcard (worked with 19.11.3). I do the same to boot my LibreELEC SDCard. No card, power on boots Android from eMMC. Tried 2 different SDCards, but same behaviour.

I'm having booting issues with the new Bionic Desktop image i.e 19.11.7. It won't boot at all. Black screen with no signal. Sdcard green light flashes only once after 5 secs of starting and then nothing. Last image worked was 19.11.3 (kernel 4.4.192). 4.4.198 didn't boot either, so I flashed now 19.11.7 (kernel 4.4.208) and it fails as well. I waited over 25 mins for it to boot.

I have tried disabling the desktop from the SSH as well, but as soon as I close the session the network connectivity dies right away. Then I have to hook up a keyboard to access the board. Yes, I know there are cli only images there, but sometimes I use the desktop to browse, watch videos, listen to music etc as well through vnc. I forgot the mention before that I'm using Armbian Bionic Desktop (19.11.3) image.

I have recently flashed the Armbian on my T4 and I'm really loving it. There is 1 thing I need little help with, when I disable the GUI through the armbian-config that network connectivity dies right away. 1. Logging into the desktop and then disable GUI, it goes to empty black screen = No connectivity and no access to SSH 2. With GUI already disabled before boot, lands on tty1 (haven't logged in on terminal) = No connectivity and no access to SSH - as soon as I login on tty1, connectivity and SSH is available. How can this be fixed? I want to run the board headless and don't want to login on the terminal either.