Search the Community

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. Section "ServerFlags" Option "AutoAddGPU" "false" EndSection 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.

Hello! 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. Neither Armbian_25.5.1_Bananapim2s_trixie_current_6.12.32_minimal.img.xz nor Armbian_26.2.1_Bananapim2s_trixie_current_6.18.15_minimal.img.xz get me past this issue. I've tried changing the power supply, debug with LLMs, but nothing appears to be working. Any suggestions?

Dear Community, I'll build a Developer Team specially for Banana Pi Boards!" GPIO Libarys I started updating/modifing the old GPIO-Libarys, so they can be used on the latest builds! I want to build a Team, for GPIO-Libary Development, for porting these Libarys: WiringPi-Node WiringPi-PHP WiringPi-Perl WirinigPi-Ruby gpiozero rpi-gpio Updating and modifying these: RPi.GPIO BPI-WiringPi2-Python BPI-WiringPi2 At the end, all currently working GPIO Libarys are: luma.oled RPi.GPIO BPI-WiringPi BPI-WiringPi2 BPI-WiringPi2-Python Armbian Build System for Banana Pi I started building the build-system for full banana pi support! Anyone who would like to join the developer-team, just pn me, post in this thread, or contact me on github or discord!" I created a GIthub-Organisation for this project and a Discord Server. A Domain & VPS Server is commin Monday!" Goals: Support ONLY for Banana Pi Boards Board Determiner Script which exports Board-Infos, required by gpio-libs (usual located at: /var/lib/bananapi) APT-Mirror Archive Hosted by our project-teams vps-server! ( Mirror stores all latest gpio-libarys we specially build for using on latest builds and other packages we'll develope in future) Added APPGROUPS: Pentesting, TV-Box, Server-Side, Game Desk & Development Revised menu for selecting extensions and other additional items Revised config menu Adding additional build options A Web-Based Project-Server Hosted Build-System will be build and available on the project-page, where you can build images remotely, according to you settings made in the WebInterface, with live progress & build-log + downloading compressed own image-release. A publish option will be added to, where you can upload your builded image to any Cloud/Storage we provide. Revised device trees According to APPGROUPS and Enabled Extensions: I2C, SPI, UART are enabled in the gpio_develope extension, and all requirements for gpio-programming are pre-installed, the gpio libs are pre-installed too. If you have some Ideas, what we could add or which wishes we can make true, just reply in this post, or contact us. Github Organisation Discord greetz, hexzhen3x7

Hi, I'm working with an armbian installed on a Banana Pi M2S and I'm having problems using GPIOX_12, GPIOX_13 and GPIOX_4, because the Wifi/Bluetooth drivers are introducing garbage data by default into them and making it difficult to use them for communication in my project. I need to know how to disable these drivers from the kernel so that they don't interfere with the UART communication that I'm creating on those pins, since they are enabled by default and take control of the port automatically (even without having any module connected). Question: Is there any way to disable them in the kernel during the image building process? For the moment I won't use those drivers since I'll be installing a Wifi module via USB later. I'm building the armbian image from the repository using these build variables: ./compile.sh build BOARD=bananapim2s BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=jammy EXTENSIONS=preset-firstrun Any help or pointers would be very appreciated. Thank you very much in advance!

Hello everyone, I'm currently working on a bananaPi M2S and trying to set up serial communication through the GPIO 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: bash [ 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. However, the device /dev/ttyAML6 does not appear in the /dev folder. Here are the steps I've taken so far: Loaded the UART-A overlay. Verified registration through dmesg logs, which show that ttyAML6 is indeed registered. What I've checked: I ran ls /dev/ttyAML* and /dev/tty* but didn't find ttyAML6. Questions: Is there a known issue with this overlay or an additional step I'm missing to make the device node appear in /dev? Are there specific udev rules I need to add or modify to automatically create the device node? Any help or pointers would be greatly appreciated! Thank you in advance!

Good day! I have a Banana pi m2s with Amlogic A311D, 4GB RAM and 16GB emmc. Official images from Banana pi work on this device (both emmc and SD card). The problem is when I try to install Armbian on SD card - using BalenaEtcher on Windows / Disk tool on Ubuntu Mate: - the m2s either doesn't boot (when Armbian is written on emmc memory) - or m2s boots from emmc storage (when Armbian is written on SD Card) SD card has boot priority over emmc and works fine with official .img from bananapi. 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. 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. Also tried changing armbianEnv.txt in part of .dtb to use. For example .dtb of odroid n2l, that generally may work (tested in official banana pi images) - but still Armbian doesn't start. Please help. Thank you!