I'm using a Banana Pi BPI-F3 with Armbian-unofficial 24.11.0-trunk sid. I'm able to connect to the Banana Pi by connecting an ethernet cable between my (Ubuntu) laptop and the board, and using the "shared with other computers" IPv4 setting in the Ubuntu network manager. On the Banana Pi, I can see that it's able to complete DNS queries (e.g. running ping will resolve the address associated with a hostname), and I can connect to my laptop from the Banana Pi over the LAN just fine. However, I can't get it to connect to anything outside of my laptop, and the packets the Pi sends out don't seem to be forwarded onto the broader network. When I run Wireshark, I can see that packets for ping google.com are being received by my laptop's ethernet interface, but they seem to be getting dropped. Running route -n on the Banana Pi yields: Is there anything else I can try to get a working internet connection?

I built a cyberdeck using a Banana Pi M2 Zero and an Ampripper 3000 wired to a battery. I don't know if it's even possible but: how can I see the battery percentage? As I said, the /sys/class/power_supply/ directory is empty.

"documentation" on Banana Pi Zero M2 is so chaotic it's even funny. goal: get PWM working. so I installed armbian, waited a week till my usb OTG cable came (because you'll just fail default SSH into it), configured ssh and followed steps in here to install modified wiring pi -- gpio utility. I can confirm setting pin L/H works. next step is to verify PWM works, so here fun begins. pinout looks to be the same as on Raspberry Pi and so they claim: I designed my board with last RPI 0 I had and I was using pin GPIO 12 (wiringPi 1) so I did:

# gpio mode 1 pwm
the pin you choose is not surport hardware PWM
you can select PA6 for PWM pin
or you can use it in softPwm mode

so as you can read it's not 'surpot' and I should try PA6. no idea what is PA6 so I was searching and found this on-the-topic thread . so I set :

# gpio mode 7 pwm
you choose the hardware PWM:1

and it informed me I have choosen PWM:1 whatever that should mean. (1 being on?) sure enough I tried to set duty cycle and waited to see my led come on, but just like the gentleman in the foermentioned thread I got:

# gpio pwm 7 100
val pwmWrite 0 <= X <= 1024
Or you can set new range by yourself by pwmSetRange(range

error that doesn't change with ducy cycle value I input it with. next best bet I found got me to adding pwm overlay, activating pwm, setting period and duty cycle. commands passed without an error but LED did not light up. as suggested at the begginging of the tread in limitations, my PWM line is now connected to GPIO 15 (UART_TXD) **--is this correct??**. this is my armbianEnv.txt

# cat /boot/armbianEnv.txt 
verbosity=1
bootlogo=false
console=both
disp_mode=1920x1080p60
overlay_prefix=sun8i-h3
rootdev=UUID=986b3dcb-01f8-4965-8a16-03b55c7341fd
rootfstype=ext4
overlays=i2c0 pwm w1-gpio
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

and I just have noticed i2c0 and w1-gpio were added to overlays probably by armbian-config utility so that might be ok. but if you ask me:

root@bananapim2zero:~# ls /boot/dtb/ | grep pwm
root@bananapim2zero:~# ls /boot/dtb-6.1.11-sunxi/ | grep pwm

shows no such overlay so I don't know. at the end, I would like to make sense of all that abbreviations as: PA, all the GPIO pin names listed in here mean, I mean there seem st be some logic in there, but I just don't know why are there two separate tables that prefix those names once with CON2- then CON3- following P{0-24} like there would be two different GPIOs? Why and what is UART _jumper_? and mainly: how do I get PWM work? i2c and w1 to follow. I'm sure answers will shed light to many more lost ones looking for RPI replacement. Thanks!

I've cracked my head on this for a while. I can't ssh into my banana pi m2 zero(I don't have a mini-usb cord, I'm trying to boot wirelessly for the first time). I get 100% packet loss every time I try to ping it. I know it connected to the wifi. I'm using this armbian release: https://www.armbian.com/banana-pi-m2-plus/ Here's what I've done: 1. I made a blank ssh file in /boot 2. In the sshd_config file I set PermitRootLogin and PasswordAuthentication to yes 3. I added a before.rules file in etc/ufw/ it has this inside:

# Allow all incoming traffic
-A ufw-before-input -j ACCEPT

# Allow all outgoing traffic
-A ufw-before-output -j ACCEPT

# Allow all forwarded traffic
-A ufw-before-forward -j ACCEPT

# Allow SSH connections
-A ufw-before-input -p tcp --dport 22 -j ACCEPT

COMMIT

4. I made sure no other machine is using port 22 5. sudo systemctl start ssh 6. When I do nmap , I get:

Starting Nmap 7.80 ( https://nmap.org  ) at 2023-01-03 19:25 EST
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 5.03 seconds

P.S.: I've been editing the OS with a linux vm and I remember yesterday I was able to ping it with no packet loss(I think) but couldn't ssh into it. I don't remember what I did to break it though :P What I listed is what I currently did to the

I'm trying to get the WiFi working on a Banana PI M2M using the mainline kernel. The device tree definition of the banana pi m2m is very incomplete sun8i-r16-bananapi-m2m.dts I successfully managed to get SPI working but I am now struggling to get the WiFi drivers working as they should. The banana pi M2M uses the AP6212 chip which from the looks of it uses a BRCM4329 chip. The AP6212 is connected through the SDIO1 to the allwinner A33, PL6 is connected WL_PMU_EN and PL7 is connected to WL-WAKE-AP. (https://drive.google.com/file/d/0B4PAo2nW2KfndHY1VF9UWXl2Rm8/view?usp=sharing) I've modified the dts with the following:

&mmc1 {
        pinctrl-names = "default";
        pinctrl-0 = ;
        vmmc-supply = ;
        mmc-pwrseq = ;
        bus-width = ;
        non-removable;
        status = "okay";

        brcmf: wifi@1 {
                reg = ;
                compatible = "brcm,bcm4329-fmac";
                interrupt-parent = ;
                interrupts = ;  /* PL7 */
                interrupt-names = "host-wake";
        };
};

I've enabled in the kernel 80211, the bcrm-fmac driver and brcm-fmac-sdio. In buildroot I've added the wireless-regdb package. I've also copied from the bananapi official image (kernel 3.4) the /lib/firmware/brcm to get the firmware and config. At the point I can load the driver with modprobe but I get a timeout issue and not too sure where to look from here...

# modprobe brcmfmac
[   67.440758] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   67.513578] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   67.595615] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
# [   68.745996] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[   69.767856] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50

My guess (but it's really just a guess) is that i'm missing some steps to properly wake up the wifi chip but measuring on the board it looks like the different rails are at the right level. Has anyone by any chance got a recent kernel working with the different drivers on a banana pi m2m? Thanks for any answers or tips!

I'm using Banana Pi with Armbian, and when I connect my board to TV with HDMI cable, on TV's screen appears Mode not supported. My ***armbianEnv.txt*** looks like:

verbosity=1
logo=disabled
console=both
disp_mode=1024x768p50e
overlay_prefix=sun7i-a20
rootdev=UUID=da7fde2c-8e42-4cb9-a8f2-20692463ff4e
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

I don't get TCP/IP communication running on my Banana PI R1 on the switch ports (i.e., not the separate LAN port which shows up as eth0, which is working). It runs "Debian GNU/Linux 9.8", upgraded from an Armbian image with Debian 8 . This is my /etc/network/interfaces file: allow-hotplug eth0 iface eth0 inet dhcp # Local loopback auto lo iface lo inet loopback # Router ports auto lan1 iface lan1 inet static address 192.168.12.253 netmask 255.255.255.0 network 192.168.12.0 broadcast 192.168.12.255 gateway 192.168.12.253 dns-search greatsoft.local auto lan2 iface lan2 inet static address 192.168.13.253 netmask 255.255.255.0 network 192.168.13.0 broadcast 192.168.13.255 gateway 192.168.13.253 dns-search greatsoft.local auto lan3 iface lan3 inet static address 192.168.14.253 netmask 255.255.255.0 network 192.168.14.0 broadcast 192.168.14.255 gateway 192.168.14.253 dns-search greatsoft.local auto lan4 iface lan4 inet static address 192.168.15.253 netmask 255.255.255.0 network 192.168.15.0 broadcast 192.168.15.255 gateway 192.168.15.253 dns-search greatsoft.local After boot, ifconfig reports these lines (lo0/wlan0 omitted): eth0: flags=4163 mtu 1500 inet 192.168.1.113 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::47:aff:fec1:f535 prefixlen 64 scopeid 0x20 ether 02:47:0a:c1:f5:35 txqueuelen 1000 (Ethernet) RX packets 4581 bytes 816911 (797.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2392 bytes 294521 (287.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 49 lan1: flags=4099 mtu 1500 inet 192.168.12.253 netmask 255.255.255.0 broadcast 192.168.12.255 ether 02:47:0a:c1:f5:35 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lan2: flags=4099 mtu 1500 inet 192.168.13.253 netmask 255.255.255.0 broadcast 192.168.13.255 ether 02:47:0a:c1:f5:35 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lan3: flags=4099 mtu 1500 inet 192.168.14.253 netmask 255.255.255.0 broadcast 192.168.14.255 ether 02:47:0a:c1:f5:35 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lan4: flags=4163 mtu 1500 inet 192.168.15.253 netmask 255.255.255.0 broadcast 192.168.15.255 inet6 fe80::47:aff:fec1:f535 prefixlen 64 scopeid 0x20 ether 02:47:0a:c1:f5:35 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 13 bytes 1070 (1.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 The output of "ip -d link show" is (lo0/wlan0 omitted): 2: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 02:47:0a:c1:f5:35 brd ff:ff:ff:ff:ff:ff promiscuity 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 3: lan2@eth0: mtu 1500 qdisc noqueue state LOWERLAYERDOWN mode DEFAULT group default qlen 1000 link/ether 02:47:0a:c1:f5:35 brd ff:ff:ff:ff:ff:ff promiscuity 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 switchid 00000000 4: lan3@eth0: mtu 1500 qdisc noqueue state LOWERLAYERDOWN mode DEFAULT group default qlen 1000 link/ether 02:47:0a:c1:f5:35 brd ff:ff:ff:ff:ff:ff promiscuity 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 switchid 00000000 5: lan4@eth0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 02:47:0a:c1:f5:35 brd ff:ff:ff:ff:ff:ff promiscuity 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 switchid 00000000 6: wan@eth0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 02:47:0a:c1:f5:35 brd ff:ff:ff:ff:ff:ff promiscuity 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 switchid 00000000 7: lan1@eth0: mtu 1500 qdisc noqueue state LOWERLAYERDOWN mode DEFAULT group default qlen 1000 link/ether 02:47:0a:c1:f5:35 brd ff:ff:ff:ff:ff:ff promiscuity 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 switchid 00000000 For example, if I connect a cable on the lan 4 port and give the connected system an IP address of 192.168.15.250 with netmask 255.255.255.0, ping from Banana PI says: From 192.168.15.253 icmp_seq=1 Destination Host Unreachable arp -n shows Address HWtype HWaddress Flags Mask Iface 192.168.15.250 (incomplete) lan4 It is unclear to me why communication fails. I guess there must be anything missing. Does anybody have a hint for me? https://www.armbian.com/lamobo-r1/

I'm running a basic application on Orange-Pi DVK with Gstreamer-1.4.0. While running the application it throws this error: AL lib: (WW) alc_initconfig: Failed to initialize backend "pulse" AL lib: (EE) ALCplaybackAlsa_reset: snd_pcm_hw_params(self->pcmHandle, hp) failed: File descriptor in bad state While running on Ubuntu (running on VMware), it works well. Why is this not running properly on the Development kit (Orange-Pi) and how can I resolve this?

I am trying to install a Ralink wifi adapter in Armbian. I have look this here but it did not lsusb Bus 004 Device 003: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter OS Version: Armbian 5.35 Bananapi Ubuntu xenial default 3.4.113 lsmod Module Size Used by bnep 14360 2 disp_ump 850 0 mali_drm 2611 1 drm 214553 2 mali_drm cpufreq_userspace 3540 0 mt7601Usta 806104 0 spidev 6339 0 mali 112222 0 ump 61778 4 mali,disp_ump a20_tp 3294 0 8021q 18659 0 garp 6084 1 8021q stp 2028 1 garp llc 5421 2 stp,garp sunxi_ir 4044 0 hidp 17740 0 rfcomm 58820 0 hci_uart 25074 0 bluetooth 265449 10 bnep,hidp,hci_uart,rfcomm ifconfig eth0 Link encap:Ethernet HWaddr 02:d5:03:c2:82:df inet addr:192.168.1.31 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::d5:3ff:fec2:82df/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1696 errors:0 dropped:0 overruns:0 frame:0 TX packets:1358 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1542624 (1.5 MB) TX bytes:244546 (244.5 KB) Interrupt:117 Base address:0x8000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:112 errors:0 dropped:0 overruns:0 frame:0 TX packets:112 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8956 (8.9 KB) TX bytes:8956 (8.9 KB) iwconfig lo no wireless extensions. eth0 no wireless extensions. bond0 no wireless extensions. dmesg output here

I have a Banana Pi running some custom Arch distribution by Ryad. I plugged in a cheap wifi dongle with the Ralink RT5370N chipset. Under /etc/systemd/network: 10-eth0.network [Match] Name=eth0 [Network] DHCP=yes RouteMetric=10 20-wlan0.network [Match] Name=wlan0 [Network] DHCP=yes RouteMetric=20 Whenever I plug in the wireless usb card, I have trouble "SSHing" into the thing. Existing secure shell sessions continue to work normally. What would cause this? networkctl (before plugging in) IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 ether routable pending 3 tunl0 tunnel off unmanaged 3 links listed. networkctl (after plugging in–takes a long time to respond) IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier pending 2 eth0 ether routable pending 3 tunl0 tunnel off pending 4 wlan0 wlan off configuring 4 links listed. wireless_tools is installed. lsmod yields the following possibly relevant results: rt5370sta 673082 0 rt2800usb 13632 0 rt2800lib 48613 1 rt2800usb rt2x00usb 11127 1 rt2800usb rt2x00lib 42474 3 rt2x00usb,rt2800lib,rt2800usb mac80211 247524 3 rt2x00lib,rt2x00usb,rt2800lib

I have a bananapi **pro** and run armbian on it. I tried stable, testing and experimental (in that order) all with the same result. When I try cryptsetup luksOpen /dev/sda1 ext_crypt I get Enter passphrase for /dev/sda1: device-mapper: reload ioctl on failed: No such file or directory Failed to setup dm-crypt key mapping for device /dev/sda1. Check that kernel supports aes-xts-plain64 cipher (check syslog for more info). syslog: May 4 20:53:19 localhost kernel: [78739.635960] device-mapper: table: 254:0: crypt: Error allocating crypto tfm May 4 20:53:19 localhost kernel: [78739.635973] device-mapper: ioctl: error adding target to table I may want to add: The device in question (/dev/sda1) was luks formated and used on a bananapi (plain, not pro) before. Do I have to compile my own kernel? Why is it, that I cannot open this device?