I got it running by following this step https://wiki.archlinux.org/index.php/Banana_Pi.
But I don’t think it is useful, Ethernet not working, HDMI not working. Need some hacks.
I can only see it through TTL / Serial console.
Feel free to post an update on this topic, guys.
I tried this without success, what should be the correct command?:
[root@bpi-m2z alarm]# iw dev wlan0 connect "foxy" key 0:12345678901234567890
key must be [d:]index:data where
'd:' means default (transmit) key
'index:' is a single digit (0-3)
'data' must be 5 or 13 ascii chars
or 10 or 26 hex digits
for example: d:2:6162636465 is the same as d:2:abcde
or psk:data <AKM Suite> <pairwise CIPHER> <groupwise CIPHER> where
'data' is the PSK (output of wpa_passphrase and the CIPHER can be CCMP or GCMP
for example: psk:0123456789abcdef PSK CCMP CCMP
The allowed AKM suites are PSK, FT/PSK, PSK/SHA-256
The allowed Cipher suites are TKIP, CCMP, GCMP, GCMP-256, CCMP-256
Whoa. Great work here.
What kernel did you use?
Did you compiled the newest kernel by using bpi-tool?
And what did you do to make ethernet working?
To connect the WiFi you can install ‘wifi-menu’ and just run it. You’ll know what to do.
Here is the explanation for the accident and the experiments:
Built one Archlinux Image with my kernel and Archlinux rootfs
removed the Archlinux kernel
booted fine and worked fine until i had to do a system upgrade (was forced to get some new packages, so i thought)
During the system upgrade the Archlinux detected a new kernel and upgraded and got in control of the board
I can now suppose it is the stock kernel running with my DTB.
Everything works except:
thermal throttling
DVFS
That makes one be very careful when putting a lot of load on the board.
The best thing would be to prevent Archlinux to upgrade the kernel or create a kernel package (or point it to somewhere else) but that is for the experienced Archlinux builder/kernel dev and this was my first ride with Archlnux (newbie here).
BTW, the kernel running is the Cibieboard2 kernel.
Did you just remove by deleting it or replacing with something else?
Where did you get the DTB files?
I used Arch Linux for my daily driver (Laptop and Servers)
But I i’m really new to this U-Boot, zImage/uImage, and DTB files.
I want to try to mod some DTB file from DTS but it’s so hard to find the documentation.
Did you use this step to build it?
So basically we only need one additional DTB files (for BPI M2Z / P2Z) and based on your experience, the one included in your image (bananapi-zero-ubuntu-base-minimal) is able to make ethernet working.
The rest of it just the matter of installing and configuring the **bootloader**
CMIIW
I can't thank you enough, Dude.
Gonna try it soon and post the update here!
to be precise, DTB and u-boot and /boot partitions are from my ubuntu image. Rootfs and kernel are from Archlinux. But if you use Archlinux u-boot just follow their rules and point to my DTB!
lrwxrwxrwx 1 root root 20 Jan 15 2018 boot.scr -> bpi-m2-zero_boot.scr
-rw-r--r-- 1 root root 1255 Nov 24 2018 bpi-m2-zero_boot.scr
lrwxrwxrwx 1 root root 26 Jun 19 12:12 bpi-m2-zero.dtb -> bpi-m2-zero-v4.dtb_4.20.17
-rw-r--r-- 1 root root 25727 Jun 22 16:35 bpi-m2-zero-v4.dtb_4.20.17
drwxr-xr-x 2 root root 36864 Ago 4 19:06 dtbs
-rw-r--r-- 1 root root 6554663 Ago 4 19:07 initramfs-linux.img
-rw-rw-r-- 1 alex alex 982455 Jan 17 2018 initrd.img
drwx------ 2 root root 16384 Nov 5 2017 lost+found
-rwxr-xr-x 1 root root 6795824 Ago 2 15:46 zImage
I followed this tutorial for every step.
Extracted DTB file from here then rename it to sun8i-h2-plus-bananapi-m2-zero.dtb to /boot/dtbs/
I got ethernet working but wifi is not detected.
But wifi is not working, still figuring out, currently cosidering to manually compile DTB files.
Soon after I do #pacman -Syu which is full upgrade, I lost ethernet and HDMI display after reboot. I have to use TTL to get to the screen.
I tried to replace few 43430 related files and it doesn’t work.
So I replace whole /lib/firmware/brcm directory with files I extracted from here
then WiFi is working. Not as I expected but It’s fine since other image can’t make it better (Signal start loosing if the board is too far from AP)
[alarm@alarm ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ba:52:27:8b:f6:0f brd ff:ff:ff:ff:ff:ff
inet 192.168.99.1/24 brd 192.168.99.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::b852:27ff:fe8b:f60f/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 18:93:7f:35:4d:f2 brd ff:ff:ff:ff:ff:ff
[alarm@alarm ~]$ dmesg | grep brc
[ 10.300791] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 10.340332] usbcore: registered new interface driver brcmfmac
[ 10.395701] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.sinovoip,bananapi zero.txt failed with error -2
[ 10.549858] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 10.550060] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 10.551164] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2016 11:30:56 version 7.45.77.h8.4 FWID 01-ee8a6268
Too far I mean more than 15cm.
I worked with 802.11b/g/n device for years and I think this is not normal.
But that is not my concern right now. I’ll be fine even if I have to put my phone closer to the board so my P2Z could get enough hotspot signal.
Are you using the Phone as a modem? (tethering or something like that) ?
Just a little info i can remember while testing the board with Wifi against another board with Wifi and had some low speed and sometimes a temporary loss of signal. I did not pay attention after i tested the boards from a wired PC and that was fine.
Try to ping from a wired board and see if you get a good signal or just ssh to it.