Banana Pi M5 not booting into the desktop

[Badger]

Logs: https://paste.armbian.com/kasujazuwo

 

Hi,

I've been looking to run the desktop version of Armbian on the M5 however it will not start (blank screen, no signal). I can see the Debian Icon at startup, and the Armbian Icon at shutdown.

startx does not bring it up, however sudo startx will but I'm not sure if this is the best way.

 

I have tested:

Armbian_22.11.3_Bananapim5_bullseye_current_6.1.4_gnome_desktop.img

Armbian_22.11.3_Bananapim5_bullseye_current_6.1.4_cinnamon_desktop.img

and both are the same.

 

Any ideas are appreciated!

Thanks.

 

 

[SoSie]

It seems to be a alsa issue according to this post https://forum.odroid.com/viewtopic.php?t=41546
I am still on the previous armbian on my side using archive having booting or screen issues : https://imola.armbian.com/archive/bananapim5/archive/

[Badger]

Hi SoSie,

 

Thanks for your message, that is what I did in the end - I went back to:

Armbian_22.08.7_Bananapim5_bullseye_edge_5.19.16_gnome_desktop.img

 

and is booting into the desktop now, but I'm sure I still had those errors in dmesg 🤔

 

I thought it was due to a permissions problem, but didn't know where to look..

[Badger]

Hi,

 

I have just tested Armbian_23.02.2_Bananapim5_bullseye_current_6.1.11_gnome_desktop and it also has the same problem.

 

Thanks..

[R.]

I have no problem with any of the Bananapi images, but can’t get any of the Armbian one booting.

Armbian_22.08.7_Bananapim5_bullseye_edge_5.19.16_gnome_desktop.img

 

Also gives me a black screen. 
 

I am also having trouble with images as well. (Gnome desktops) 6x and all 5x kernels.

 

I’ll connect via serial soon. To see what’s going on. My blue and red lights are solid (not flashing but on ) lcd gets an HDMI signal but black screen. I’ve switched cables and tried multiple screens. 
 

Armbian usually always boots well for me.

 

I find it hard to believe any of the images are bootable of an SD, am I missing something here ?

 

Edited October 21, 2023 by R.

[c0rnelius]

This should correct the audio issue.

 

Run as root `sudo su` and only choose one.

# ANALOG
amixer -c 0 set 'TOACODEC OUT EN' 'on'
amixer -c 0 set 'TOACODEC SRC' 'I2S B'
amixer -c 0 set 'TDMOUT_B SRC SEL' 'IN 0'
amixer -c 0 set 'FRDDR_A SRC 2 EN' 'on'
amixer -c 0 set 'FRDDR_A SINK 1 SEL' 'OUT 0'
amixer -c 0 set 'FRDDR_A SINK 2 SEL' 'OUT 1'
amixer -c 0 set 'FRDDR_A SINK 3 SEL' 'OUT 2'
amixer -c 0 set 'ACODEC' '85%'
alsactl store

# HDMI
amixer -c 0 set 'TOHDMITX' 'on'
amixer -c 0 set 'TOHDMITX I2S SRC' 'I2S B'
amixer -c 0 set 'TDMOUT_B SRC SEL' 'IN 0'
amixer -c 0 set 'FRDDR_A SRC 2 EN' 'on'
amixer -c 0 set 'FRDDR_A SINK 1 SEL' 'OUT 0'
amixer -c 0 set 'FRDDR_A SINK 2 SEL' 'OUT 1'
amixer -c 0 set 'FRDDR_A SINK 3 SEL' 'OUT 2'
amixer -c 0 set 'ACODEC' '85%'
alsactl store