I’ve been trying for a while to get an MTK MT7615 (the one from here) on my banana pi R2.
I’ve already checked this thread for help. That thread mentions mt7615e_rf.bin, and later mt7615e_cr4.bin, mt7615e_n9.bin and mt7615e_rom_patch.bin. The first one I’ve never found it anywhere, so I guess it’s a typo or has been renamed. As for the rest, I’ve tried copying them to /lib/firmware/mediatek, /lib/firmware with zero success (not even any relevant change in dmesg) both in debian 9 and 10.
I’ve also tried to modprobe mt76 with and without the firmware, again, with zero success.
If your dmesg does not return anything for mt76 you have no driver or it is not loaded…
You can try to find it in /lib/modules/$(uname -r)/kernel/drivers/net/wireless/mediatek if there is any
As i said,4.14 does not have mt7615 driver (see my tree)
Mainline 5.4 does contain mt7615 driver (my repo uses different folder because i added newer version with mt7622 wifi driver,but mainline mt76 folder is still there)
Which exact 5.4 kernel do you have? From my repo or anywhere else? Imho 5.4 i shipped with debian 10 image had not the driver included
Yes, the mt76 is there (/lib/modules/5.4.58-bpi-r2-main/kernel/drivers/net/wireless/mediatek/mt76_new/mt76.ko), but loading does nothing (no change in lspci or lshw, or dmesg).
For both versions I’m using your images, but I’ve stopped trying on the 4.14 since it doesn’t have the driver. The image is the one from your repo, downloaded this evening.
Exact kernel version:
# uname -a
Linux bpi-r2 5.4.58-bpi-r2-main #146 SMP Sun Aug 16 15:42:09 CEST 2020 armv7l GNU/Linux
Still no dmesg, wlan interface, or noticeable change after copying the firmware files, modprobing, rebooting… (in any order).
you do not need the eeprom-patch as it currently only for testing (increasing tx power, change mac and similar).
but you need newer version, to include mt7615 driver, as i do not see mt7615e.ko, current r2 defconfig on 5.4-main branch contains the CONFIG_MT7615E=m option, i do not know on which kernel-version i had added it (commit a9d427b51647 on nov 19 2020, i guess 5.4.78), but you can use precompiled kernels from github-releases (you do not need to compile by yourself)
Debs in 5.4 do not change uEnv.txt as this change was only done in my own debs (now modified linux way is used to support source debs to). You have to add new kernel to your uEnv.txt manually. Path have not changed (it is defined in uboot,not linux)
/boot/bananapi/bpi-r2/linux/uEnv.txt (if mmcblk0p1 is mounted to /boot)
i have pushed 5.10-main tree, i hope i have added all important…also added code for eeprom-override (if you want to test this too)…travis builds currently, takes approx. 1 hour to complete and upload to github-releases
but i have not yet merged the deb-patches, so they do not contain right kernel-file…have removed the debs from first build and pushed again with pack_deps patch…currently it is not compatible with out-of-tree-build, but enough for travis build
Yes, I did try a few days ago. But then a bunch of work came and I didn’t have time to try again.
The dbdc file did exist, but echoing 1 to it did not create another wireless interface. If I remember correctly, both 2.4 and 5GHz worked ok individually, but I couldn’t manage to get both of them working at the same time on the same interface.
Then after some tries, I couldn’t manage to get neither the 2.4 nor 5GHz bands individually either, probably because of the reboot bug. After stopping the bpi for a while, I did try again, but I couldn’t configure the region and every band would be marked as “No IR” (I think it was IR), so hostapd wouldn’t start.
However, all of this was with the 5.10 from two weeks ago. I did notice a few days ago that the one I downloaded was missing, so I guess there was something wrong with it? I’ll try again with a new image and the 5.10 that’s on github releases at the moment.
PS: I’ve also noticed that the wifi board (well, at least the IC) gets as hot as 80ºC even when it’s not in use or the driver isn’t loaded. Any suggestion on how to lower its power from software? Perhaps a heatsink?