Search the Community

I am trying to install Ambian on to the BananaPi-M7 to eMMC using option 6. there is no option for NVME / M2 SSD. I had a failed install as the uSDCard image was 256GB larger than the eMMC, so it balked. I tried a 128GB uSDCard, followed by a 64GB uSDCard, but got the same error each time even on the 64GB one. I seem to have two partitions on the eMMC, mmcblk0boot0, and mmcblk0boot2 now,. I am not sure if they were on the boards eMMC originally or what the boot sequence for the board is If the Masked ROM tries to boot the uSDCard if present and if that fails it boots the eMMC ? Do I clear mmcblk0 and try again with the 64GB uSDcard ? Or is mmcblk0 required to boot mmcblk1 ? I have done an :- https://paste.armbian.com/ehanixecoh Also ``` aaronngray@bananapim7:~$ lsblk -a NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ram0 1:0 0 4M 0 disk loop0 7:0 0 0B 0 loop loop1 7:1 0 0B 0 loop loop2 7:2 0 0B 0 loop loop3 7:3 0 0B 0 loop loop4 7:4 0 0B 0 loop loop5 7:5 0 0B 0 loop loop6 7:6 0 0B 0 loop loop7 7:7 0 0B 0 loop mmcblk1 179:0 0 59.7G 0 disk └─mmcblk1p1 179:1 0 59.1G 0 part /var/log.hdd / mmcblk0 179:32 0 115.3G 0 disk mmcblk0boot0 179:64 0 4M 1 disk mmcblk0boot1 179:96 0 4M 1 disk zram0 252:0 0 15.5G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk nvme0n1 259:0 0 1.8T 0 disk ```

Hi, First of all thanks for this awesome product, BananaPi M7 is really great in many ways! Only one last thing appears to be broken on our project, I'm having connection troubles from IoT in 2.4Ghz against BananaPi setup as an AP.I'm using the latest up to date armbian server image $ uname -a Linux bananapim7 6.1.75-vendor-rk35xx #1 SMP Tue Nov 12 08:48:32 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux $ cat /etc/*release # PLEASE DO NOT EDIT THIS FILE BOARD=bananapim7 BOARD_NAME="Banana Pi M7" BOARDFAMILY=rockchip-rk3588 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=26d182157 LINUXFAMILY=rk35xx ARCH=arm64 BOOT_SOC=rk3588 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image KERNEL_TARGET=edge,current,vendor KERNEL_TEST_TARGET=vendor,current FORCE_BOOTSCRIPT_UPDATE= FORCE_UBOOT_UPDATE= OVERLAY_DIR="/boot/dtb/rockchip/overlay" VENDOR="Armbian" VENDORDOCS="https://docs.armbian.com" VENDORURL="https://www.armbian.com" VENDORSUPPORT="https://forum.armbian.com" VENDORBUGS="https://www.armbian.com/bugs" BOOTSCRIPT_FORCE_UPDATE="no" BOOTSCRIPT_DST="boot.cmd" VERSION=24.11.1 REVISION=24.11.1 IMAGE_UUID=14f1a719-8726-4abf-a76a-d0c4da1658c6 # PLEASE DO NOT EDIT THIS FILE BOARD=bananapim7 BOARD_NAME="Banana Pi M7" BOARDFAMILY=rockchip-rk3588 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=26d182157 LINUXFAMILY=rk35xx ARCH=arm64 BOOT_SOC=rk3588 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image KERNEL_TARGET=edge,current,vendor KERNEL_TEST_TARGET=vendor,current FORCE_BOOTSCRIPT_UPDATE= FORCE_UBOOT_UPDATE= OVERLAY_DIR="/boot/dtb/rockchip/overlay" VENDOR="Armbian" VENDORDOCS="https://docs.armbian.com" VENDORURL="https://www.armbian.com" VENDORSUPPORT="https://forum.armbian.com" VENDORBUGS="https://www.armbian.com/bugs" BOOTSCRIPT_FORCE_UPDATE="no" BOOTSCRIPT_DST="boot.cmd" VERSION=24.11.1 REVISION=24.11.1 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=24.04 DISTRIB_CODENAME=noble DISTRIB_DESCRIPTION="Ubuntu 24.04 LTS" PRETTY_NAME="Armbian 24.11.1 noble" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" PRIVACY_POLICY_URL="https://www.armbian.com" UBUNTU_CODENAME=noble LOGO="armbian-logo" ARMBIAN_PRETTY_NAME="Armbian 24.11.1 noble" The wireless config seems to be alright: $ iwconfig ... wlan0 IEEE 802.11 ESSID:"" Mode:Master Channel:34 Access Point: Not-Associated Bit Rate:1.2005 Gb/s Tx-Power:32 dBm Retry min limit:7 RTS thr:off Fragment thr:off Power Managementmode:All packets received Link Quality=5/5 Signal level=-2 dBm Noise level=-99 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 $ iw wlan0 info Interface wlan0 ifindex 4 wdev 0x1 addr b8:2d:28:5a:56:f6 type managed wiphy 0 channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz txpower 31.00 dBm $ iw ap0 info Interface ap0 ifindex 16 wdev 0x4 addr ba:2d:28:5a:56:f6 ssid XXXXXXXX type AP wiphy 0 channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz txpower 31.00 dBm The interface is correctly setup: $ ip a ... 16: ap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether ba:2d:28:5a:56:f6 brd ff:ff:ff:ff:ff:ff inet 10.1.0.1/8 brd 10.255.255.255 scope global noprefixroute ap0 valid_lft forever preferred_lft forever inet6 fe80::be9a:7773:f8dc:f9fa/64 scope link noprefixroute valid_lft forever preferred_lft forever $ nmcli con show NAME UUID TYPE DEVICE XXXXXXXX 7c89f803-bd17-42e1-8134-e2f6f33edc28 wifi ap0 ... I'm able to connect to my AP using my laptop (the only differences I see is that I'm using a 5Ghz capable network card even if 2.4Ghz is setup in nmcli config...) But the IoT equipement keep being deauthenticated with messages like: $ sudo dmesg ... [ 2279.531130] [dhd] __dhd_add_sta: Adding STA 00:XX:XX:XX:70:90 [ 2279.535314] [dhd] [ap0] wl_ext_iapsta_link : [A] connected device 00:XX:XX:XX:70:90 [ 2279.536101] [dhd] dhd_update_sta_chanspec_info: updated chanspec:0x1001 for STA:00:XX:XX:XX:70:90 [ 2279.536133] [dhd] [ap0] wl_notify_connect_status_ap : new sta event for 00:XX:XX:XX:70:90 [ 2279.537036] [dhd] CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set A quick google search led me to this line in wl_cfg80211.c driver -> https://android.googlesource.com/kernel/msm/+/9a5104b845c1558cc204abfe97c120d14677baa5/drivers/net/wireless/bcmdhd/wl_cfg80211.c#6928 It appear to be a question about params->sta_flags_mask not set, as NL80211_STA_FLAG_AUTHORIZED is set to 0 in include files Question: Where are set the struct station_parameters ? How could it be modified ? Reproduce steps script: #!/bin/bash HOTSPOT="XXXXXXXX" AP_PASS="XXXXXXXX" AP_IFACE="ap0" # Setup iface sudo iw dev wlan0 interface add $AP_IFACE type __ap # Setup HotSpot sudo nmcli con add type wifi con-name $HOTSPOT ssid $HOTSPOT sudo nmcli con modify $HOTSPOT 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.channel 1 ipv4.method shared sudo nmcli con modify $HOTSPOT wifi-sec.key-mgmt none sudo nmcli con modify $HOTSPOT wifi-sec.wep-key-type 1 sudo nmcli con modify $HOTSPOT wifi-sec.wep-key0 $AP_PASS sudo nmcli con modify $HOTSPOT ifname $AP_IFACE sudo nmcli con modify $HOTSPOT ipv4.address 10.1.0.1/8 sudo nmcli con modify $HOTSPOT ipv4.gateway 10.1.0.1 sudo nmcli con up $HOTSPOT Thanks for your help !

I downloaded and flashed the three images of Armbian 24.8.1 (Noble GNOME, Ubuntu 22.04 Jammy and Debian 12 Bookworm) on the Banana Pi M7, connected to the computer via serial console. The three images are these: Armbian_24.8.1_Bananapim7_noble_vendor_6.1.75_gnome-kisak_desktop.img Armbian_24.8.1_Bananapim7_jammy_vendor_6.1.75_kde-neon-kisak_desktop.img Armbian_24.8.1_Bananapim7_bookworm_vendor_6.1.75_cinnamon-backported-mesa_desktop.img For each image, I booted and logged the board output. The board fails to successfully boot and instead gets stuck in a boot loop. I then mounted the armbi_root partition and edited the file armbi_root/boot/armbianEnv.txt to set verbosity=7, in the hope of getting more useful information from the kernel. I retried booting the board, and I observed the same boot loop, but this time with more kernel logs. The serial outputs of the failed boots are here: Armbian 24.8.1 Noble GNOME: noble.log (see attached files) Armbian 24.8.1 Ubuntu 22.04 Jammy: jammy.log (see attached files) Armbian 24.8.1 Debian 12 Bookworm: bookworm.log (see attached files) I’m not sure why the kernel decides to reboot everytime, but I’m sharing the information in case it is useful to someone. (see original post) noble.log jammy.log bookworm.log

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

I am trying to work out how to add a 2560x1400 mode to the ViewSonic 32" 2560x1440 (16:9) display configuration that is not listed on the display settings configuration and should be there. Any tips on updating the configuration file, locally and then as a patch to Armbian please ?

Hi, I am wondering if people have tried the Banana-Pi M7 board with `armbian monitor -m` and `stress --cpu 8` in different ssh or window terminals, both with bare board, with metal case, and also with different kernels ? I have had temperature issues with Banana-Pi M3 RockChip boards, and am wondering if M7's suffer the same.

I am interested in hardware video support and wether ffmpeg has hardware support on the RK3588 and Mali G610MC4 GPU. And was wondering if someone whould be interested in giving me the output of a few tests for me please ? ``` ffmpeg -hide_banner -encoders ``` ``` ffmpeg -hide_banner -decoders ``` ``` ffmpeg -hide_banner -hwaccels ``` Many thanks in advance.

The ap6275p WiFi hotspot fails to open. The ap6275p itself supports the ap mode. image：Armbian_24.5.5_Bananapim7_bookworm_vendor_6.1.75_cinnamon_desktop.img sudo create_ap -m nat wlan0 enP2p33s0 armsom armsom-jack --no-virt --freq-band 5 Failed to get phy interface ERROR: Your adapter does not support AP (master) mode We used joshua-Riek/ubuntu-rockchip's ubuntu system which supports ap and has been connected normally

Hello, I'm looking to buy an ARM SBC with: Bluetooth Connection for monitor x3 CPU: x86 AMD Graphics integrated LAN x2 Mobo: I'm unsure on mini pc mobos, but needed? Power Ram: 16-32GB preferred Storage: small is fine 32GB-256GB, nothing large like 1TB USB for mouse USB for spare Wi-Fi for hotspot I usually use Raspberry Pi 5, however the Bananapi-M7 appears to have dual port, although I haven't confirmed the other requirements I need. The question is which OS do I download please? as per https://www.armbian.com/bananapi-m7/