<?xml version="1.0"?>
<rss version="2.0"><channel><title>Banana PI M2S Latest Topics</title><link>https://testforum.armbian.com/forum/234-banana-pi-m2s/</link><description>Banana PI M2S Latest Topics</description><language>en</language><item><title>Xorg problem with recent kernels? (Resolved)</title><link>https://testforum.armbian.com/topic/60407-xorg-problem-with-recent-kernels-resolved/</link><description><![CDATA[<p>
	With the most recent minimal Debian image, Armbian_26.2.1_Bananapim2s_trixie_current_6.18.15_minimal.img on my A311D, I hit a problem with Xorg. Instead of starting up into dwm via lightdm's autologin, all I got was the blank blinking cursor screen. Working through it with an LLM, the resolution worked out to be adding a stanza to Xorg.conf.
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">Section "ServerFlags"
    Option "AutoAddGPU" "false"
EndSection</span></pre>

<p>
	 
</p>

<p>
	Is this the correct solution? Is this known or understood? I know nothing about any of this. I presume it's related to how the devices look to Xorg via the kernel, but I have no understanding beyond that level, if that's even correct.
</p>
]]></description><guid isPermaLink="false">60407</guid><pubDate>Fri, 19 Jun 2026 00:43:42 +0000</pubDate></item><item><title>Problems with recent images</title><link>https://testforum.armbian.com/topic/60392-problems-with-recent-images/</link><description><![CDATA[<p>
	Hello!
</p>

<p>
	 
</p>

<p>
	I recently ran updates on the old M2S I won from here, and that appeared to break my OS, so I went back to try reinstall. And that's where I hit a snag. For some reason, after booting, the kernels refuse to see the partitions on the SD card. /dev/mmcblk0 exists, but none of the subpartitions, and so the boot process cannot find the partition it's supposed to boot from.
</p>

<p>
	 
</p>

<p>
	Neither
</p>

<p>
	Armbian_25.5.1_Bananapim2s_trixie_current_6.12.32_minimal.img.xz
</p>

<p>
	nor
</p>

<p>
	Armbian_26.2.1_Bananapim2s_trixie_current_6.18.15_minimal.img.xz
</p>

<p>
	get me past this issue.
</p>

<p>
	 
</p>

<p>
	I've tried changing the power supply, debug with LLMs, but nothing appears to be working. Any suggestions?
</p>
]]></description><guid isPermaLink="false">60392</guid><pubDate>Wed, 17 Jun 2026 18:50:14 +0000</pubDate></item><item><title>gpio serial port(uart-a) not working</title><link>https://testforum.armbian.com/topic/43562-gpio-serial-portuart-a-not-working/</link><description><![CDATA[<p>
	Hello everyone,
</p>

<p>
	 
</p>

<p>
	I'm currently working on a bananaPi M2S and trying to set up serial communication through the <abbr title="General purpose input/output">GPIO</abbr> port on my device. I am using the provided overlay for UART-A. The overlay seems to work as it registers the serial device, as indicated by the dmesg output:
</p>

<p>
	bash
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">[ 0.000277] printk: console [tty1] enabled 
[ 0.734433] ff803000.serial: ttyAML0 at MMIO 0xff803000 (irq = 14, base_baud = 1500000) is a meson_uart 
[ 0.734458] printk: console [ttyAML0] enabled 
[ 0.735241] ffd24000.serial: ttyAML6 at MMIO 0xffd24000 (irq = 15, base_baud = 1500000) is a meson_uart 
[ 0.735395] serial serial0: tty port ttyAML6 registered 
[ 2.663304] systemd[1]: Created slice Slice /system/serial-getty. 
[ 3.140660] systemd[1]: Found device /dev/ttyAML0. </span></pre>

<p>
	 
</p>

<p>
	However, the device /dev/ttyAML6 does not appear in the /dev folder.
</p>

<p>
	 
</p>

<p>
	Here are the steps I've taken so far:
</p>

<p>
	 
</p>

<ul>
	<li>
		Loaded the UART-A overlay.
	</li>
	<li>
		Verified registration through dmesg logs, which show that ttyAML6 is indeed registered.
	</li>
</ul>

<p>
	 
</p>

<p>
	What I've checked:
</p>

<ul>
	<li>
		I ran ls /dev/ttyAML* and /dev/tty* but didn't find ttyAML6.
	</li>
</ul>

<p>
	 
</p>

<p>
	Questions:
</p>

<p>
	 
</p>

<p>
	Is there a known issue with this overlay or an additional step I'm missing to make the device node appear in /dev?
</p>

<p>
	Are there specific udev rules I need to add or modify to automatically create the device node?
</p>

<p>
	 
</p>

<p>
	Any help or pointers would be greatly appreciated!
</p>

<p>
	Thank you in advance!
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">43562</guid><pubDate>Wed, 07 Aug 2024 13:30:37 +0000</pubDate></item><item><title>No Armbian images are working</title><link>https://testforum.armbian.com/topic/42695-no-armbian-images-are-working/</link><description><![CDATA[<p>
	Good day!
</p>

<p>
	 
</p>

<p>
	I have a Banana pi m2s with Amlogic A311D, 4GB RAM and 16GB <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr>.
</p>

<p>
	Official images from Banana pi work on this device (both <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr> and SD card).
</p>

<p>
	The problem is when I try to install Armbian on SD card - using BalenaEtcher on Windows / Disk tool on Ubuntu Mate:
</p>

<p>
	- the m2s either doesn't boot (when Armbian is written on <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr> memory)
</p>

<p>
	- or m2s boots from <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr> storage (when Armbian is written on SD Card)
</p>

<p>
	 
</p>

<p>
	SD card has boot priority over <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr> and works fine with official .img from bananapi.
</p>

<p>
	 
</p>

<p>
	I see all written files on SD card after using Balena Etcher. The difference from official images is that boot folder in official images is seperate FAT32 partition. And in Armbian there is no seperate boot partition. But as I understood from reading forums, that shouldn't be a problem.
</p>

<p>
	 
</p>

<p>
	Strange that is doesn't want to boot Armbian (no information on screen and blue led is not blinking). I tried different images from older ones to newer, with and without desktop... No result.
</p>

<p>
	Also tried changing armbianEnv.txt in part of .<abbr title="Device tree blob">dtb</abbr> to use. For example .<abbr title="Device tree blob">dtb</abbr> of odroid n2l, that generally may work (tested in official banana pi images) - but still Armbian doesn't start.
</p>

<p>
	 
</p>

<p>
	Please help.
</p>

<p>
	 
</p>

<p>
	Thank you!
</p>
]]></description><guid isPermaLink="false">42695</guid><pubDate>Sat, 20 Jul 2024 21:36:42 +0000</pubDate></item><item><title>Using USB 3?</title><link>https://testforum.armbian.com/topic/30236-using-usb-3/</link><description><![CDATA[<p>
	The USB-C port and lsusb results suggest to me that this board should support USB 3 under Armbian, but I have no earthly idea how I would succeed at this.
</p>

<p>
	 
</p>

<p>
	My first, naive attempt used the PinePhone docking bar. This looked like it might work as it passed power through to the M2S, and it also powered the WD Passport HDD I used to test, but no devices appeared. Is there a better fit? Perhaps the PinePhone device only works with Pine devices?
</p>

<p>
	 
</p>

<p>
	This would be better posted on the official Banana Pi forum, but I'm apparently IP banned despite having never posted there. This is an Armbian system, so I reckon it's not too off-topic to ask here.
</p>
]]></description><guid isPermaLink="false">30236</guid><pubDate>Fri, 15 Sep 2023 17:19:19 +0000</pubDate></item><item><title>Missing build?</title><link>https://testforum.armbian.com/topic/29327-missing-build/</link><description><![CDATA[<p>
	On the page <a href="https://www.armbian.com/bananapi-m2s/" rel="external nofollow">https://www.armbian.com/bananapi-m2s/</a> I tried to download the Bookworm XFCE build at the link <a href="https://redirect.armbian.com/region/NA/bananapim2s/Bookworm_current_xfce" rel="external nofollow">https://redirect.armbian.com/region/NA/bananapim2s/Bookworm_current_xfce</a> but that link gives a 404 error. EU mirror worked. Where should I report this?
</p>
]]></description><guid isPermaLink="false">29327</guid><pubDate>Thu, 20 Jul 2023 21:18:04 +0000</pubDate></item><item><title>Initial support for Bananapi M2S</title><link>https://testforum.armbian.com/topic/25134-initial-support-for-bananapi-m2s/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	This is my first try to add a board to armbian build system.
</p>

<p>
	I got a <abbr title="Banana Pi"><abbr title="Banana Pi">BPI</abbr></abbr> M2S since several months, but only had time recently to investigate on this promising <abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr>.
</p>

<p>
	I made a PR here, if somebody wants to try it: <a href="https://github.com/armbian/build/pull/4597" rel="external nofollow">https://github.com/armbian/build/pull/4597</a>
</p>

<p>
	The main improvements are to be done for the <abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr> file, since I'm not an expert about such file definition. Only 1 ethernet of the Gbit ports is wo<abbr title="Rockchip"><abbr title="Rockchip">rk</abbr></abbr>ing, since I copy the config from vim3 that share the same hardware for it.
</p>

<p>
	I didn't try to customize u-boot and I use the one for radxa zero2 that wo<abbr title="Rockchip"><abbr title="Rockchip">rk</abbr></abbr>s to launch armbian on the board.
</p>

<p>
	armbianmonitor -u is here: <a href="https://paste.armbian.com/piyuqajeye" rel="external nofollow">https://paste.armbian.com/piyuqajeye</a>
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">25134</guid><pubDate>Tue, 20 Dec 2022 18:27:23 +0000</pubDate></item></channel></rss>
