i don’t know which ath driver needed for this card…so you need to build/use kernel with all. Imho i have only ath9k and ath10k included.
I guess it’s ath5k,but i’m not sure
edit: i added ath5k with pci to 4.19-main, you can download binary from github releases
Sorry Frank, I’ve just realised that you’ve wrote! On your github page I didn’t find it only 4.14 kernel! Could you please give me a link? Thank you very much!
just change the branch to 4.19-main…4.14 is only name of repo and default branch
It’s working Frank! 
Now I must thinking about how should I do with 2,4 ghz & 5 ghz AP config regarding nftables! 
But it’s another story!
(in a meanwhile I was able to prepare a basic nft-fw) 
Has somebody recognized overheating problem on Bpi-r2? I bought a case, can’t apply, because of high temperature! Without case it’s between 41 C and 50 C. With the plastic overlay it gets between 50 C and 59 C depending from CPU utilization! I’ve already put heatsink on CPU, ram, emmc. Another source of issue is the wlan card, it’s hot and powertop shows 100% usage independent from CPU!
You mean internal wifi card (mt6625l)? How did you measure its utilization? My test-r2 has official plastic case and no heatsinks…noticed no increased temperature. Which kernel do you use? How long after bootup does it take to reach this temps? Do you have much traffic on wifi when you hit this issue?
Not the internal, it’s an old atheros! The name of the app is powertop, and before last tab can I see! After half an hour occurs. Kernel is 4.19.62. Not as much traffic on wlan!
Maybe try newer kernel? I guess it’s a deiver issue which maybe fixed later
Is it possible to load firmware at boot time? I think just this two lines :
wmt_loader
stp_uart_launcher -p /etc/firmware &
Kernel is 4.19, debian 10 buster. I’m planning a schedule of wifi AP, for example between 22:00 and 06:00 turn it off. Furthermore it would be nice to make AP “reboot-proof”, so after an unplanned system reboot it could run again!
Take a look at my wifi.sh on github…i call it via rc.local so it gets configured on bootup
For wifi-ap sheduling you can kill hostapd on 22:00 and start it on 6:00 via cronjob
I’ve been using your script and it’s perfect!
Unfortunately, rc.local doesn’t seem getting it configured at startup! I’ve tried it several times, but no idea! 
On buster (maybe stretch too) you need to create/enable systemd-service for rc.local
Working again, as I expected!
It’s great!
Thank you Frank!
But I slightly modified the wmt_loader script and placed it in the init.d directory. Then turned it on as a service. And when the system starts, the wifi starts and works.
Hi all, here is just a warning to end-users: be really thorough in visual inspection the moment you receive the board. Make sure to paitiently look at each and every square centimeter for misplaced SMD components as s*it happens and you might get a board like I got, check the attached picture below:
It is a typical case of misplaced component by pick-n-place machine. What is funny is the fact I wasn’t experiencing any major problems with WiFi on this particular BPiR2 board (well, expect for usual problems all users have related to the poor quality of the driver). I’m capable of fixing this one myself thx to my experience with smd soldering and the fact I’ve got required tools standing by ready to be used on my second work desk. Chances are that some other end-user won’t be that lucky. So I repeat once again: inspect the board as thorough as possible the moment you receive it. It might be easier to RTM it for exchange than trying to find some local shop to do a fix for you.
Hey guys. I’m newbie in openwrt, and just tested latest RC on my bpi-r2.
Working good, but there is no wifi enabled on it =(
Could you please help me to enable WiFi module on it because I’m a dumb =)
R2 wifi driver (mt6625l) is not available in official openwrt. You can get it on my repo (www.github.com/frank-w/bpi-r2-4.14) and try to integrate into your openwrt source
@frank-w thank you for help!! Does repo( www.github.com/frank-w/bpi-r2-4.14 ) has any diff with patching kernel? Or maybe short manual where I can get driver sources?
It depends on kernel-version you are using. Basicly i have 3 commits per -main branch for wifi-driver (driver folder itself, including it, changes outside) followed by maybe fixes. So better use these 3 commits from 1 version higher that your kernel version.
E.g. if you use 5.10 you take a look into 5.11-main. As i normally do not update the non-lts branches you will find these commits easily
https://github.com/frank-w/BPI-R2-4.14/commits/5.11-main
maybe include the other fixes added to this tree
