gaara

Same thing here: # systemctl stop bluetooth.service # hciattach /dev/ttyS1 bcm43xx 115200 bcm43xx_init Flash firmware /etc/firmware/ap6212/4343A0.hcd Set Controller UART speed to 115200 bit/s Device setup complete # hciconfig hci0 up # hciconfig -a hci0: Type: BR/EDR Bus: UART BD Address: 43:43:A0:12:1F:AC ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:478 acl:0 sco:0 events:17 errors:0 TX bytes:331 acl:0 sco:0 commands:17 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'BCM4343A0 26MHz AP6212_CL1-0027' Class: 0x000000 Service Classes: Unspecified Device Class: Miscellaneous, HCI Version: 4.1 (0x7) Revision: 0x3b LMP Version: 4.1 (0x7) Subversion: 0x2122 Manufacturer: Broadcom Corporation (15) # hcitool scan Scanning ... 84:00:D2:6B:40:ED Xperia ray # hciconfig dev hci0: Type: BR/EDR Bus: UART BD Address: 43:43:A0:12:1F:AC ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:2356 acl:0 sco:0 events:52 errors:0 TX bytes:733 acl:0 sco:0 commands:43 errors:0 For blueman, no device detected. I had to do sudo usermod -G bluetooth -a <username> and reboot to have a window "No adapter found" when cliking on "Setup New Device". Before this usermod I havn't any window... Weird that scanning works in terminal but not with blueman...

Ah ok, I was using v5.10 No matter, solved !

Ok guys, I've found a solution. It was the firmware and the files in the /lib/firmware/ap6212 Here is a procedure: 1) Download the firmware git clone https://github.com/BPI-SINOVOIP/BPI_WiFi_Firmware or git clone https://github.com/jrspruitt/FriendlyARM_NanoPi_Buildroot_Ext.git 2) Rename nvram_ap6212.txt to nvram.txt: mv ~/BPI_>WiFi_Firmware/ap6212/nvram_ap6212.txt ~/BPI_>WiFi_Firmware/ap6212/nvram.txt 3) Copy the ap6212 folder into /lib/firmware folder sudo cp -r ~/BPI_>WiFi_Firmware/ap6212 /lib/firmware Then, sudo ifconfig wlan0 up should work

Thanks lvmc, here some results $ iw list Wiphy phy0 Band 1: Frequencies: * 2412 MHz [1] (20.0 dBm) * 2417 MHz [2] (20.0 dBm) * 2422 MHz [3] (20.0 dBm) * 2427 MHz [4] (20.0 dBm) * 2432 MHz [5] (20.0 dBm) * 2437 MHz [6] (20.0 dBm) * 2442 MHz [7] (20.0 dBm) * 2447 MHz [8] (20.0 dBm) * 2452 MHz [9] (20.0 dBm) * 2457 MHz [10] (20.0 dBm) * 2462 MHz [11] (20.0 dBm) * 2467 MHz [12] (20.0 dBm) * 2472 MHz [13] (20.0 dBm) * 2484 MHz [14] (20.0 dBm) Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps (short preamble supported) * 5.5 Mbps (short preamble supported) * 11.0 Mbps (short preamble supported) * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps max # scan SSIDs: 10 max scan IEs length: 2048 bytes Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP (00-0f-ac:4) * CMAC (00-0f-ac:6) Available Antennas: TX 0 RX 0 Supported interface modes: * IBSS * managed * AP * P2P-client * P2P-GO software interface modes (can always be added): valid interface combinations: * #{ AP } <= 1, #{ managed } <= 3, #{ P2P-client, P2P-GO } <= 2, #{ IBSS } <= 1, total <= 4, #channels <= 2 Supported commands: * new_interface * set_interface * new_key * start_ap * set_bss * join_ibss * set_pmksa * del_pmksa * flush_pmksa * remain_on_channel * frame * frame_wait_cancel * set_wiphy_netns * set_channel * tdls_oper * connect * disconnect Supported TX frame types: * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0 xe0 0xf0 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0 xf0 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0 xe0 0xf0 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd 0 0xe0 0xf0 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0x e0 0xf0 Supported RX frame types: * IBSS: 0xd0 * managed: 0x40 0xd0 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * P2P-client: 0x40 0xd0 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 Device supports T-DLS. and $ iw wlan0 info Interface wlan0 ifindex 5 type managed wiphy 0

Ok, I post some lines, maybe Igor could solve this $ sudo ifconfig wlan0 up SIOCSIFFLAGS: Operation not permitted $ dmesg | tail [ 188.147991] dhd_open: Exit ret=-1 [ 188.150497] dhd_open: Enter ee710800 [ 188.150580] Dongle Host Driver, version 1.201.34.2 (r491657) [ 188.150602] Compiled in drivers/net/wireless/bcmdhd on May 31 2016 at 18:59:58 [ 188.150650] wl_android_wifi_on in 1 [ 188.150700] wl_android_wifi_on in 2: g_wifi_on=0 [ 188.150743] wifi_platform_set_power = 1 [ 188.150776] ======== PULL WL_REG_ON HIGH! ======== [ 188.150813] [wifi_pm]: set wl_reg_on 1 ! Maybe a firmware issue... More diagnostics: $ rfkill list all 0: sunxi-bt: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmfmac-wifi: Wireless LAN Soft blocked: no Hard blocked: no $ sudo lshw -C network *-network:0 DISABLED description: Wireless interface physical id: 7 logical name: wlan0 serial: 00:90:4c:11:22:33 capabilities: ethernet physical wireless configuration: broadcast=yes driver=wl driverversion=0 multicast=yes wireless=IEEE 802.11 *-network:1 description: Ethernet interface physical id: 8 logical name: eth0 serial: 1a:63:b4:9c:f2:c5 size: 100Mbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonego tiation configuration: autonegotiation=on broadcast=yes driver=sunxi_geth driverversion=SUNXI Gbgit driver V1.1 duplex=full ip=192.168.2.5 link=yes multicast=yes port=MII speed=100Mbit/s *-network:2 DISABLED description: Wireless interface physical id: 9 logical name: p2p0 serial: 00:90:4c:33:22:11 capabilities: ethernet physical wireless configuration: broadcast=yes driver=p2p driverversion=0 multicast=yes wireless=IEEE 802.11bg

Ok, thanks for your answer. So I have made a clean install. After update/upgrade, modprobe bcmdhd works well. But no wifi detected by Wicd Network Manager. So I tried: $ iwconfig lo no wireless extensions. tunl0 no wireless extensions. wlan0 IEEE 802.11 Access Point: Not-Associated Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 invalid crypt:0 invalid misc:0 eth0 no wireless extensions. p2p0 IEEE 802.11bg ESSID:off/any Mode:Managed Access Point: Not-Associated Retry long limit:7 RTS thr:off Fragment thr:off Power Management:on $ lsmod Module Size Used by mali_drm 2732 1 drm 178255 2 mali_drm mali 123208 0 ump 29379 3 mali bcmdhd 648477 0 $ iwlist wlan0 scan wlan0 Interface doesn't support scanning. I suppose p2p0 is BT, I'm not sure.

Hi all ! Sinovoip just send me a free sample of a new board, BPi M2 plus. - H3 SoC - eMMC (7.3 Go) -Inboard Wifi+BT ( chipset AP6212 ) Very good, thanks to them ! So I have installed Armbian (here), but the wifi doesn't work yet. I have found the driver source, (http://www.mediafire.com/download/68vvpim3k3po0ur/support_ap6212.rar) but I think I must recompile all Armbian to try if this driver works. Some questions: 1) Can I compile Armbian with a Ubuntu 16.04 x64 desktop, or 14.04 is better ? 2) If so, does a source is available somewhere (and maybe a tutorial? XD ) ? I have look the Igor's repo, but I think sun8i is not available at this day. Thanks for all lights

Wow thanks for your answers. I didn't know the bin file wasn't used for Armbian. So, I tried to set this lines, with stoping the autoboot: setenv overscan_x 20 setenv overscan_y 20 saveenv reset I tried also setenv overscan_x 200 setenv overscan_y 200 saveenv reset (After "saveenv", I can see some lines that MMC(0) is modified.) But no changes. However I see at the boot: ..onnected: Setting up a 1920x1080 hdmi console (overscan 0x0) (I can't see the beginning) Does the overscan has not been saved ? Edit: I found a solution, with this lines: setenv video-mode sunxi:1920x1080-24@60,monitor=hdmi,overscan_x=50,overscan_y=50 saveenv reset Thanks you very much to help me, now I must to calibrate this

Hi all, First, thanks to Igor for his job with Armbian: Scripts, compilations etc. Very apprecied so far. I own an Orange Pi 1 based on A20 SoC. Armbian kernel 4.4.1 is installed, no problem. (I have used the Igor's script to upgrade it) But I'm trying to change the bin file in /boot/bin, it seems to not work, no change if I set screen0_output_mode = 5 In orangepi.fex Of course, I'm using the bin2fex & fex2bin exec on my desktop (Kubuntu 16.04 x64), and I copy the new bin file in /boot/bin/orangepi.bin The goal is to change the first resolution, because I would like to solve this problem (see the photo, the display exceeds) on my DIY tablet. Have you an idea to solve it (the bin file problem, or the size screen in general) ? Thanks!