Mechano

The distributions for this SBC don't boot due to errors to thermal device. I saw some messages in the forum where has be told that disabling thermal check the distribution works. Can you blacklist or disable thermal sensors check?

Finally a good compromise and readability of this nice 3.5" small HDMI screen with Banana Pi M5 console only (no X.org). I remember it's a physical resolution of 480x320 with an EDID range of resolutions from 720x480 to 1920x1080. The smallest resolution I can get with Banana Pi M5 is 720x480@60hz that you can see in the picture. Raspberry Pi 3B can do 640x360@85hz and has better character sharpness.

I've discovered more about this beaviour... If you have Ubuntu Jammy on eMMC and want to boot another OS from microSD it has to be another Ubuntu with mmcblk1 root disk set somewhere, that overrides the boot priority. If you try to boot a RaspiOS for Banana it has set mmcblk0 and will not boot.

You're right, in fact I see that part gets ignored and its works anyway.

I've found 2 workarounds... The firs one: Change setenv line into boot.cmd with 480p@60 and recompile the boot.scr with the line you find at the end of the file boot.cmd. And add this line to armbianEnv.txt extraargs=video=HDMI-A-1:720x480M@60 fbcon=rotate:0 I've left rotate to change if I need (values 0, 1, 2, 3). Another workaround I used before find this one was to set a particular resolution of 896x504@87hz it's divisible /8 and permit on this display to see the login. With Raspberry Pi 3B I can set 640x360 and is perfect for this display with linux text console.

On my Banana Pi M5 Armbian Jammy has a strange device name assignment. BPi-M5 has internal 16GB eMMC normally named mmcblk0 and microSD named mmcblk1. Normally it boots from SD and if you install an OS like Raspberry OS for BPi into eMMC, you're still able to boot from SD another OS because RaspiOS maps device correctly. But when Armbian (i.e. Jammy) is installed into eMMC it changes eMMC device to mmcblk1 and SD to mmcblk0, and It prevents SD to boot. And if the eMMC OS corrupts and doesn't boot the SBC bricks and TTL connection is needed to erase boot record. To change OS it's necessary a command to delete boot record and SD on mmblk1 will boot again: dd if=/dev/zero of=/dev/mmcblk1 bs=512 count=1 But the OS on eMMC has to boot and be in good working conditions. Also another guy with Orange Pi has noticd this behaviour: https://forum.armbian.com/topic/9987-sd-card-not-booting-but-works-on-another-emmc-boot-up/ It's important to change this behaviour and do it like RaspiOS.

Into /boot/armbianEnv.txt I've this line: extraargs=drm_kms_helper.edid_firmware=HDMI-A-1:edid/720x480.bin video=HDMI-A-1:720x480M@60 fbcon=rotate:0 The fbcon=rotate=x permit you to rotate, the items available are 0, 1, 2, 3.

Hi there! I've installed Armbian 23.02.0 Jammy on my Banana Pi M5. And I'm using 3.5" display with HDMI interface. The screen has a native 480x320 resolution, but accept a range from 640x480 to 1920x1080. On resolutions over 800x480 is not readable, so I'm able to change resolution with the following line in /boot/armbianEnv.txt extraargs=video=HDMI-A-1:800x480M@87 fbcon=rotate:0 with lower resolutions 800x480 to 640x480 (60 to 87hz) the screen has an offset down of one character line so ther's a blank line up and I don't see login and shell input command down. Looking at 16:9 resolutions I see all the text with the minimum of 896x504 I don't know how to set overscan and screen offset up 1 character line with 800x480 o 720x480. Every help will be appreciated.