thesign

Thanks for your reply @tkaiser Afterall it took me several month to realize that the M2+ is a useless piece of hardware. Guess you realized this ways faster ;-) I won't buy any new M2+ board and most likely shred my existing ones.

The other day I literally burned my fingers when trying to figure out why my mostly idle bpi-m2+ did not respond. Unfortunately I forgot to throttle the CPU/RAM with the h3consumption tool. Which settings would you recommended for a M2+ in order to avoid overheating? To my surprise the overheating also happened without high loads.

I agree with @tkaiser that the M2+ board could have been better engineered. :-D It seems to me that the Raspberry Pi remains to be the only affordable hardware with proper software support; wonder if they are going to release a gigabit version soon. I have a naive question regarding my initial request: @zador.blood.stained in order to port the chunk of netfilter changes back to the legacy kernel: should I diff the corresponding directories in the armbian sources folder against the official Linux kernel repo (tagged with 3.7)? Or do I need to diff against a "different" kernel source? P.S: Sorry for the late replies, It seems I never receive any notifications for updates on this forum thread.

I am not sure if i brought up a painful subject in my question regarding the vanilla/mainline kernel? I guess @tkaiser and @Igor can't also wait for the vanilla kernel to be completed ;-) In the meantime I will try my best to backport the (niche) features from Kernel 3.7. Any pointers to helpful documentation are more than welcome.

I am using the latest Armbian version with a legacy kernel on my M2+ board. The Armbian forum has already been a great source of help. Now I am facing a new issue: - for my setup the IPv6 NAT netfilter module is required, which was introduced in Kernel 3.7 So in my understanding I have two options: a) backport the kernel module(s) to the legacy Kernel by customizing the armbian build process switch to the mainline Kernel The mainline kernel for H3 boards seems to lack support for Gigabit ethernet and in general still remains no recommended for potential overheating problems? Thus, I guess I have to get working on the Kernel module backports. Do you have any pointers for me? Is this issue better placed in another sub-forum? thank you guys!

Fixed the device naming issue with udev and thanks @tkaiser for the nmtui/nmcli advice - will update my skills to 2017

A simple copy of the *a1 files was enough. I will dive into udev rules as network manager is not an option - for my headless setup.

Short update I managed to get the WiFi on the revised board running again. Turns out there are firmware files for the revised AP6212 chip: https://github.com/BPI-SINOVOIP/BPI-files/tree/master/others/brcm/lib/firmware/ap6212 Once the firmwarefiles *1.* are copied to the firmware folder everything works again. The only minor issue I still have to fix is that the wlan interface now is wlan1 instead of wlan0. Any suggestions on how to "correctly" name the wlan interface are appreciated.

BTW: I could send you one of the boards to Slovenia - in case you want to debug the WiFi chip hands-on?

This is the "old" working board: http://imgur.com/a/P3XPA This is board revision I face problems with: http://imgur.com/a/XBUcY As you can see, the revision / board version did not change - what changed is the revision of the WiFi chip.

Hi Igor, It seems that the boards feature a different revision of the WiFi chip. Is there anything I could do to help get it running again? best, Markus

Hi there, Recently you helped me to setup a WiFI AP on Armbian and a bananapim2p board: https://forum.armbian.com/index.php/topic/2395-access-point-mode-with-ap6212-on-armbian-521/ The current problem I am facing: the dhd module on armbian 5.25 does not on my bananapim2p boards. To be precise: I have one bananapi m2p where the dhd module loads perfectly on armbian 5.25, I created an image of this board's emmc and flashed the emmc of two different m2p boards. The dhd config file looks like: cat /etc/modprobe.d$ cat /etc/modprobe.d/dhd.conf options dhd op_mode=2 firmware_path=/lib/firmware/ap6212/fw_bcm43438a0_apsta.bin With the modprobe configuration the m2p boards hang on boot (raising network interface ...) and boot perfectly if a remove the module configuration. I am also not able to manually load the dhd module: [ 363.081480] dhd_wifi_platform_load: Enter [ 363.978718] dhd_conf_set_chiprev: chip=0xa9a6, chiprev=1 [ 363.978999] dhd_conf_set_conf_path_by_nv_path: config_path=/lib/firmware/ap6212/config.txt [ 363.979090] dhd_conf_read_config: Ignore config file /lib/firmware/ap6212/config.txt [ 363.982876] dhd_attach(): thread:dhd_watchdog_thread:57e started [ 363.983230] dhd_attach(): thread:dhd_dpc:57f started [ 363.983286] dhd_dpc_thread: set dpc_cpucore 0 from config.txt [ 363.983559] dhd_attach(): thread:dhd_rxf:580 started [ 363.983637] dhd_deferred_work_init: work queue initialized [ 363.984789] dhd_conf_read_config: Ignore config file /lib/firmware/ap6212/config.txt [ 363.984862] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/ap6212/fw_bcm43438a1.bin [ 363.984915] dhdsdio_download_firmware: set use_rxchain 0 [ 363.984952] dhdsdio_download_firmware: set txglomsize 40 [ 363.987065] dhdsdio_download_code_file: Open firmware file failed /lib/firmware/ap6212/fw_bcm43438a1.bin [ 363.987123] _dhdsdio_download_firmware: dongle image file download failed [ 363.987251] dhd_bus_start: failed to download firmware /lib/firmware/ap6212/fw_bcm43438a1.bin [ 363.987300] dhdsdio_probe: dhd_bus_start failed [ 363.987413] dhd_wlfc_deinit():3301, Already disabled! [ 364.040146] dhd_detach(): thread:dhd_watchdog_thread:57e terminated OK [ 364.040219] dhd_detach(): thread:dhd_rxf:580 terminated OK [ 364.040240] dhd_dpc_thread: Unexpected up_cnt 0 [ 364.040282] dhd_detach(): thread:dhd_dpc:57f terminated OK [ 364.080411] dhd_os_prealloc: failed to alloc memory, section: 7, size: 0bytes [ 376.080202] dhd_wifi_platform_load_sdio: sdio_register_driver timeout or error [ 376.081002] dhd_module_init: Failed to load the driver, try cnt 0 [ 376.081147] dhd_module_init: Failed to load driver max retry reached** [ 376.081189] dhd_module_init: Exit err=-62 Do you have any idea how I could further debug this issue? It would be great if I could give back to the amazing armbian project, by helping to fix this issue - in case anybody else faces similar issues.

Oh my ...! I sure hope it does not require me to start desoldering components - i have to get an antenna first to check if additional hardware hacks are required.

Hi all, I can confirm that the autoloading conf as proposed by Igor et al. works. Thank you ever so much for your prompt replies! Right now the WiFi signal is pretty low, I am experimenting with different settings - and this is a topic for yet another post if I do not solve it. Thank you guys!

Wow, your support is amazing guys! While Igor answered, I tried tkaiser's suggestion - and it did not work. Another thing I tried (because I do not yet understand how dhd works) is to add the op_mode option to /lib/firmware/ap6212/config.txt - which did not change anything.

Hi Igor, I tried manually loading the dhd module with the op_mode=2, however the WiFi module did not switch into AP mode -> resulting in no accessible WiFi access point. My attempts to persist the op_mode=2 module settings in /etc/modules, where unsuccessful (failure on boot). Thus, my question: Which release changed the WiFi driver / daemon? Do you think its worth using a older armbian release until e.g. https://github.com/igorpecovnik/lib/issues/484is sorted out? markus

Hi there, I pulled the latest changes from github and created a fresh Debian Jessie Armbian Image for my BananaPi M2+. Specifically, I run: BOARD=bananapim2plus BOARD_NAME="Banana Pi M2+" VERSION=5.21 LINUXFAMILY=sun8i BRANCH=default ARCH=arm Through a lot of debugging and googeling, I found that the latest armbian Image uses a different BCM driver (https://github.com/igorpecovnik/lib/issues/484). Now I face the following issue: In order to use AP6216 with hostapd in access point mode, I added "bcmdhd op_mode=2" to /etc/module. I tried a number of things, e.g. using dhd instead of bcmdhd but without success? Any ideas where I can configure AP6216 in op_mode=2 (access point mode) with the new driver? Or any ideas where I can find additional documentation? The access point mode is an important feature for me, so I am also considering using an older armbian version. With which release tag, did the new BCM driver got introduced? thx, markus