Search the Community

I had another distro and power button nicely shut down the system and it doesn't with armbian. I have read some things about it but I'm not even sure if they apply to this board or they are updated, about acpi events, logind and AR100, and I've read the official schematics of the board. It seems the button is connected to ADC pins. I installed acpid but acpi_listen reports nothing. But evtest does! root@bananapim5:~# evtest /dev/input/by-path/platform-adc_keys-event Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100 Input device name: "adc_keys" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 259 (BTN_3) Properties: Testing ... (interrupt to exit) Event: time 1687334663.436476, type 1 (EV_KEY), code 259 (BTN_3), value 1 Event: time 1687334663.436476, -------------- SYN_REPORT ------------ Event: time 1687334663.948482, type 1 (EV_KEY), code 259 (BTN_3), value 0 Event: time 1687334663.948482, -------------- SYN_REPORT ------------ Is there a way to tell the system that this is event is an acpi event or a driver would be needed? I don't think I can make a real driver but I think I could get read the event from /dev/input/by-path/platform-adc_keys-event with python or something. If I can't I could always wrap evtest and make it do the reading. Thanks!

When I try to do "apt upgrade" on a brand new SD Card that has been just flashed I get a "kernel panic". This is the whole error: https://paste.debian.net/1283664 And this is the armbianmonitor -U log: https://paste.debian.net/1283662/ The board runs fine with debian with 4.9.x kernel supplied by manufacturer. Armbian is the second image I try because I need a newer kernel. I'll try to find one that is less new. Thank you for your support! EDIT: I tried again without wifi and it worked flawlessly. I can't make it crash with a wired connection. I used the same wifi plug with Debian and I never had an error but maybe there's a bug in the driver in this image or something... Oh! it's there in the kernel panic. [ 555.599414] Call trace: [ 555.601829] ODM_RA_TxRPT2Handle_8188E+0x110/0x390 [r8188eu] [ 555.607435] rtl8188eu_recv_tasklet+0x364/0x3a0 [r8188eu] [ 555.612782] tasklet_action_common.constprop.0+0x13c/0x150 It's indeed something with the wifi plug. It's a TP-LINK WN725N

Could someone with a BPI-M5 confirm whether it has crypto extensions? Could you run `cryptsetup benchmark` or `openssl speed aes-128-cbc`? Thanks!

u-boot from Armbian_23.02.0-trunk_Bananapim5_sid_edge_6.2.0-rc3_minimal.img hangs if I try to boot with my USB hard disk connected. I replaced it with u-boot from Armbian_22.08.7_Bananapim5_bullseye_edge_5.19.16.img and that one works fine. U-Boot 2022.10-armbian (Feb 12 2023 - 17:20:43 +0000)bpi-m5 Model: Banana Pi BPI-M5 SoC: Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2) DRAM: 3.8 GiB Core: 384 devices, 27 uclasses, devicetree: separate MMC: sd@ffe05000: 0, mmc@ffe07000: 1 Loading Environment from nowhere... OK In: serial Out: serial Err: serial Net: eth0: ethernet@ff3f0000 Autoboot in 2 seconds starting USB... Bus usb@ff500000: Register 3000140 NbrPorts 3 Starting the controller USB XHCI 1.10 scanning bus usb@ff500000 for devices... error in inquiry If I unplug the USB hard disk then also the newer u-boot works fine: scanning bus usb@ff500000 for devices... 4 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found

Hi, Banana Pi M5 here. Really thanks so much by your generous work with Armbian software. I did a try with: Armbian 23.02.2 Jammy XFCE Armbian 23.02.2 Bullseye XFCE Armbian 22.11.3 Jammy XFCE Armbian 22.08.7 Jammy XFCE But only 22.08.7 loads desktop. The others versions does not load desktop after Armbian logo load screen, but I can login through SSH. I'm not proficiency with computers, I used Linux from many years ago but as an entry user, it's only a hobby, so excuse me if this problem is solved, but I don't find a solution in forum neither the Internet and I'm with these problems for months. Does anyone know how to solve the issue with screens? Other details: Power sources used with BPI-M5: - AC/DC Adaptor Model DSM-0530 (5V 3A) supplied with BPI-M5. - Original raspberry foundation AC adapter Model KSA-15E-051300HE (5.1V 3.0A) supplied with RPI-4B. SD cards: - SanDisk Ultra 64GB (never issues with RPI-4B neither Windows) - Kingston Canvas Select Plus 32GB (never issues with RPI-4B neither Windows) I'm trying Linux flavors because I like Ubuntu a lot for different applications, and I would like to use Kodi too. In Armbian 22.08.7 I thought that Kodi did not have GPU acceleration because options menus were really slow at 1080, but then I saw in the changelog that I was wrong trying v22.08.1 because Armbian included BPI-M5 support on Armbian 22.11.1, so I would like to give it a try. Thanks so much

Hi! Using the vanilla ARMBIAN image 23.02.2_Bananapim5_bullseye_current_6.1.11_minimal Enabling the provided uartA and uartC dtbos fails. Here is the output from the boot process, as captured via the Serial Debug interface: 238 bytes read in 3 ms (77.1 KiB/s) Applying kernel provided DT overlay meson-uartA.dtbo failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND 238 bytes read in 3 ms (77.1 KiB/s) Applying kernel provided DT overlay meson-uartC.dtbo failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC It seems that this image provides invalid dtbos, likely not properly built alongside the same kernel image. I'm happy to help debug this as I have a system at the ready.

Hello, I know this is a forbidden question, I will adress specially to @chewitt and @Igor. Why I dare to do this? Because today, it is the fist time I managed to run Libreelec (LE) nighly https://test.libreelec.tv/11.0/Amlogic/bananapi-m5/ and have the somehow the same suffering with boot and so on and as I did not give up, I shot the last bug preventing LE to boot. I don't want to register in every forum for each pack , christian forgive me I will put the explanation here. The last image suffer from a missing link..in /flash as it is all momified in squashfs , this need extra skills. wget https://ftp.halifax.rwth-aachen.de/libreelec/LibreELEC-AMLGX.arm-11.0.1-bananapi-m5.img.gz gunzip LibreELEC-AMLGX.arm-11.0.1-bananapi-m5.img partx -a LibreELEC-AMLGX.arm-11.0.1-bananapi-m5.img losetup -a /dev/loop0 mount /dev/loop0p1 /media/LIBREELEC cp /media/LIBREELEC/SYSTEM . unsquashfs SYSTEM cd squashfs-root/flash #here is the missing killing link ln -s .. SYSTEM cd - mksquashfs squashfs-root/ -noappend -comp zstd -Xcompression-level 15 cp SYSTEM /media/LIBREELEC/ umount /dev/loop0p1 Then use gparted to wipe out the sdcard, and use dd dd if=LibreELEC-AMLGX.arm-11.0.1-bananapi-m5.img of=/dev/mmcblck1 bs=1M Boot and ENJOY!

Armbian_22.08.7_Bananapim5_bullseye_edge_5.19.16_gnome_desktop Hello, I'm trying to rotate the desktop from landscape to portrait. Trying to do this in the display settings in the desktop does not work correctly as it only uses the top half of the screen. What does work is to rotate using xrandr: xrandr -o right I'm trying to do this automatically on start up so I have written a script to call from lightdm.conf The script: #!/bin/sh xrandr -o right exit 0 The parts in lightdm.conf [Seat:*] that I've edited: display-setup-script=/home/badger/screen.sh session-setup-script=/home/badger/screen.sh This works for the login screen, however it does not rotate the display. Any ideas how to do this? Thanks.

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.

Hello, The mission: to change display resolution for "None-1" ('unknown display') - when no physical screen/display/monitor is attached. Machine: Banana Pi M5 (Bpi M5). I use it as a headless machine (without any monitor connected) and access it via a remote control/share screen application (such as: Teamviewer). The problem: the display is very small as the resolution is set to 720 X 576. I couldn't find any way or method to define/change the resolution in such a case. How can this be done? I'll appreciate any assistance you can provide. Thanks in advance! This is the information of the machine and Armbian version installed: BOARD=bananapim5 BOARD_NAME="Banana Pi M5/M2P" BOARDFAMILY=meson-sm1 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=b475b12 VERSION=22.11.4 LINUXFAMILY=meson64 ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image BRANCH=current

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.

This week I installed Armbian on three BananaPi M5s. The OS ran fine from SD card, but once installed to emmc (using armbian-config) the system booted with a message that the file space available was zero. In the case of one of the boards I found an 8GB .img file in /media/my userid/. I assumed it was a copy of the 8GB SD card, and I deleted it. The system is fine now. But in the case of the other two I have yet to determine what is consumbing all the file space. There are two empty directoris in /media (mmcboot and mmcroot). Any idea what is causing this and more importantly how to fix the two existing systems? Thanks, Paul

Hello, I got a BPIM5 with rtl8822cs board and a BPIM2+ with internal wifi chip for home automation. I started my project (vpn gateway) with the ubuntu server distribution on BPIM5. I had a lot of instability of the wifi driver (lost of station in AP mode) and and the board crashed every two, three days. I switches to ARMBIAN with the last Armbian 22.11.3 Bullseye with Linux 6.1.4-meson64. This software seems to work fine on M2+ and wifi is fine and stable. So I tried to move my M5 to the same level. The M5 boot on sd card, I move it on MMC memory and the board boot . Unfortunatly the wifi board (rtl8822cs sdio) is not recognized at boot . Does the driver and overlays file available somewhere for the M5 board and the WIFI sdio board ? Thanks for your help Gerard

Hello, When we install armbian cinnammon, the eth0 ip is set default to 192.168.0.8. I cloned the installation and then the cloned conflicts with the source so I though to use armbian-config to change the IP adress. The ipv4 changed but I noticed warnings in/var/log/syslog : IPv6: eth0: IPv6 duplicate address.. It seems armbian-config does not update ipv6 or? What should be do, disable ipv6? I read it is not recommended at all.

Hi, I am new to Armbian and I am working with the Jammy Minimal CLI image (9 Jan 2023) in a Banana Pi M5. I need to configure the w1 to the pin GPIOA_14 and I have tried adding the following to /boot/armbianEnv.txt: overlays=w1-gpio param_w1_pin=GPIOA_14 But it does not work. How should I configure it? Thanks

Hello All, To all striking with sdcard issues , I have a good news today! NORMAL AND FIGHTING WAY Normally you put your sdcard on a adapter on a big computer you have flashed with a working and booting sbc to be able to flash the emmc and then you copy the .img.xz you have downloaded on it , put the card in the sbc and boot on it to have access to the dd command from there. Unfortunately the result will depend on your sdcard quality, I experienced many bad block so I get bored. Yesterday have a flash, LET'S TAKE THE BUNNY HIGHWAY! I found a way faster and safer to do it to circonvent the sdcard: tempfs! On the desktop computer, a linux machine, I download the images for the sbc wget https://imola.armbian.com/archive/bananapim5/archive/Armbian_22.08.7_Bananapim5_jammy_edge_5.19.16_cinnamon_desktop.img.xz wget https://imola.armbian.com/archive/bananapim5/archive/Armbian_22.08.7_Bananapim5_jammy_edge_5.19.16_cinnamon_desktop.img.xz.sha I retrieved the size du -h Armbian_22.08.7_Bananapim5_jammy_edge_5.19.16_cinnamon_desktop.img.xz 1,3G Armbian_22.08.7_Bananapim5_jammy_edge_5.19.16_cinnamon_desktop.img.xz I issued with the USER=pi created during the first boot install on the sbc, for me HOST=bananapim5 a ssh session, ip maye change depending on your setting in armbian_first_run.txt if you have set a static ip. Mine is 192.168.0.8 sosie@rainbow:~$ ssh pi@192.168.0.8 I tried the ubuntu tutorial to create tmpfs at a size a little bigger than the image .img.xz I want to flash #create the target directory for tempfs sudo mkdir /media/virtuelram #let only user access to their own temp files with the sticky bit sudo chmod 1777 /media/virtuelram #mount to have size M or g for gigas vitual drive sudo mount -t tmpfs -o size=1.5g tmpfs /media/virtuelram Exit to transfer the img.xz files by sftp IN THE BUNNY HIGHWAY ^o^ exit sosie@rainbow:~$ sftp pi@192.168.0.8 cd /media/virtualram mget Arm*.xz.* exit Now you are hundred percent to pass the exam (without cheating), the proof : sosie@rainbow:~$ ssh pi@192.168.0.8 cd /media/virtualram sha256sum -c Armbian_22.08.7_Bananapim5_jammy_edge_5.19.16_cinnamon_desktop.img.xz.sha Armbian_22.08.7_Bananapim5_jammy_edge_5.19.16_cinnamon_desktop.img.xz: Success The flash size is around 16go, we see can locate the EMMC, it's mmcblk1 , real size is 14.6Go USER@HOST:/media/virtuelram$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk0 179:0 0 59,5G 0 disk <== SDCARD 64Go └─mmcblk0p1 179:1 0 58,9G 0 part / mmcblk1 179:32 0 14,6G 0 disk <== EMMC └─mmcblk1p1 179:33 0 14,6G 0 part mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk Now the fun part: sudo apt install xzcat pv dd sudo xzcat Armbian_22.08.7_Bananapim5_jammy_edge_5.19.16_cinnamon_desktop.img.xz | pv | dd of=/dev/mmcblk1 bs=10M status=noxfer

Hello, I want to transfer .img files to bananapi. These weight gigabytes. I notice the eth0 interface was wrongly set up to 100Mbp/s I used ethtool to set it up correctly pi@Liberty:~$ sudo ethtool eth0 | grep -i speed Speed: 100Mb/s sudo ethtool -s eth0 autoneg on speed 1000 duplex full pi@Liberty:~$ sudo ethtool eth0 | grep -i speed Speed: 1000Mb/s Now I thought the sftp limitation of 1Mb/s was over, it is not. Are there ucap / bandwith limitation settings in Armbian? if so how to remove it? Thanks, SoSie

Hello, i have an Issue with my Touchscreen on my Banana Pi running Armbian Bullseye. The colors are not correct ... everything shows with a ?brown / red? touch and the Position are not correct ... Top 5 pixel border and bottom 5 pixel cut. I check the display ... it works fine when i plugin on my desktop pc ... so the hardware should be fine. Is there maybe anyone who can help me with that? I haven´t found a solution for this by myself or by google around. System: Banana PI M5 with prebuild Armbian 22.11 Bullseye CLI on internal MMC directly downloaded from the Armbian Website -> https://www.armbian.com/bananapi-m5/ Sunfounder 7" Touchscreen connected over HDMI and USB -> https://www.sunfounder.com/collections/touchscreens/products/7inch-ips-touchscreen AspectRatio: 16:9 Resolution 1024x600 Color 16.7M Chip on the Back (Maybe important): RTD2513A To Me: I have a some experience with Linux based systems (I use Arch on my Desktop and Notebook) but in this particular case i have no idea how to fix this or how to begin to debug. Thanks, dkleber89

Hello I've tried to install the newest Armbian image "Armbian_22.08.7_Bananapim5_jammy_edge_5.19.16_cinnamon_desktop.img.xz" Copied with Balena Etcher to SDcard. Attached a serial tty cable and started with card in SD-Slot. Unfortunately it stops while booting. Please can anybody help me ? Here is the serial log:

Recently i've download and installed Armbian_22.08.7_Bananapim5_bullseye_edge_5.19.16_minimal.img into Banana Pi M5 board. Initial setup run smoothly. After run the reboot command the system stop halfway. Can I know how to solve this problem? I have copy the error message below. Thanks. U-Boot 2022.07-armbian (Oct 18 2022 - 07:30:35 +0000)bpi-m5 Model: Banana Pi BPI-M5 SoC: Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2) DRAM: 3.8 GiB Core: 385 devices, 27 uclasses, devicetree: separate MMC: sd@ffe05000: 0, mmc@ffe07000: 1 Loading Environment from nowhere... OK In: serial Out: serial Err: serial Net: eth0: ethernet@ff3f0000 Autoboot in 2 seconds switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 8147 bytes read in 3 ms (2.6 MiB/s) ## Executing script at 08000000 U-boot default fdtfile: amlogic/meson-sm1-bananapi-m5.dtb Current variant: 161 bytes read in 2 ms (78.1 KiB/s) Current fdtfile after armbianEnv: amlogic/meson-sm1-bananapi-m5.dtb Mainline bootargs: root=UUID=d0c122f6-b8a9-4650-94c2-77c85521b2d8 rootwait rootfstype=ext4 splash=verbose console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=79a75e49-01 libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=memory swapaccount=1 19116246 bytes read in 838 ms (21.8 MiB/s) mmc fail to send stop cmd ** fs_devread read error - block Failed to load '/boot/Image' ** fs_devread read error - block Failed to mount ext2 filesystem... Can't set block device libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! ** fs_devread read error - block Failed to mount ext2 filesystem... Can't set block device ** fs_devread read error - block Failed to mount ext2 filesystem... ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 19116182 Bytes = 18.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... ** No partition table - mmc 0 ** Couldn't find partition mmc 0:1 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:1 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:1 No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image ** No partition table - mmc 0 ** Couldn't find partition mmc 0:1 switch to partitions #0, OK mmc1(part 0) is current device ** No partition table - mmc 1 ** Couldn't find partition mmc 1:1 MMC Device 2 not found no mmc device at slot 2 starting USB... Bus usb@ff500000: Register 3000140 NbrPorts 3 Starting the controller USB XHCI 1.10 scanning bus usb@ff500000 for devices... 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device Speed: 100, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.0.156 (12 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-ba-df-83-51-8d-a0 Speed: 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A8009C Speed: 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A8009 Speed: 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A800 Speed: 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A80 Speed: 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A8 Speed: 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A Speed: 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0 Speed: 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C Speed: 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default-arm-meson-u200 Speed: 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default-arm-meson Speed: 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default-arm Speed: 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default Speed: 100, full duplex *** ERROR: `serverip' not set Config file not found Speed: 100, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.0.156 (2 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET Speed: 100, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.0.156 (2 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET

I tried the 5.10 images. Both Jammy and Buster. Both just give a black display, but the display does wake up(background LED is on) All LED's stay on. With sid 5.19 it boots normally. Blue LED flashes. Display works.