2022-11-23 firmware file changes break DBDC on mt7916 #720
Comments
|
This is not an issue. We just limited it to 2+5GHz or 2+6GHz for new version. If you want to do 5+6GHz then you should stick to the previous version. Are you using AisaRF device? |
|
Is there any way to bring it back in newer firmware? Why was this limited? In my opinion this is a regression. |
|
Is there any way to bring it back in newer firmware? Why was this limited?
In my opinion this is a regression.
Yes, I agree. This is definitely a regression.
… —
Reply to this email directly, view it on GitHub
<#720 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOA2CNI67Q3ERUAM7Y7SOLWOAPLTANCNFSM6AAAAAATCVFBKI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Yes, an AW7916-NPD. To note, I was attempting to transmit on 2+5 or 2+6; I wasn't aware that the hardware was actually capable of 5+6, nor did I attempt it. I did attempt only running a 5GHz and then only a 6GHz PHY, and neither were able to transmit or receive on the new firmware in those bands, although the driver did not notice any issues whatsoever. |
|
Try this. I know the 0x191 of AsiaRF is wrong. |
|
Oh my god. I have been going crazy for a few days trying to setup hostapd with 2+5Ghz Wifi on a AW7916-NPD, because 5Ghz would just not work. Linux version: hostapd version: firmware versions: 2.4 Ghz hostapd config5 Ghz hostapd configWhich starts up fine on 2.4Ghz. I can see the SSID on my Mac and it has the right channel width, but 5Ghz just does not send any beacon frames. I was going crazy trying to find a solution. If anybody needs any debugging, please let me know what to do to try this. |
|
Did you find solutions for not working 5 Ghz in AW7916-NPD?, I am also experiences it! [EDIT] |
|
@trippleflux No, I am waiting on an answer from the maintainers of the mediatek driver. Since this seems to be either a driver problem or a hardware problem with the AsiaRF AW7916-NPD. If it is a hardware problem, then I am going to send the board back. If it is a driver problem I hope we will see a fix soon. Since I am not using OpenWRT but a vanilla Debian install, it is a bit harder for me to go back or forward in the repo here, but it is essentially the same code here and in the kernel and firmware repos. |
|
@NotANormalNerd On OpenWrt the firmware is located @ /lib/firmware/mediatek , I have just replaced the firmware files with mt7915_* , mt7916_* & mt7986_* and reboot, now I can uses and settings the 5 Ghz part of AW7916-NPD. But I agree that newer or newest firmware files need to support AW7916-NPD |
|
Did you guys try my change above? The eeprom of AsiaRF is wrong. |
|
Just finished compiling & deploying latest OpenWrt snapshot for x86_64, based on your pointer, here is my patch : But the ssid shown as "Hidden Network" on Windows 11, the replacing with old firmware workaround is doesn't work anymore. Client is Intel AX210 [EDIT] |
|
@trippleflux So, is it working now? |
|
Yes with old firmware but no with newest firmware, it was old firmware with your code, I was wrongly assumed that it was newest firmware, with newest firmware I am still getting the non-working 5 Ghz. |
|
I think this is most likely device issue. I'll check around. |
|
Please report this issue to AsiaRF because I don't thin any issues on my devices. Or, can you modify code to make flow go with ret = mt7915_eeprom_load_default(dev); then fallback to use default.bin to replace eeprom. |
|
Same problem here. I run a Unielec MT7623, MT7915 runs fine but the MT7916 wont do 5Ghz. Sys log looks normal, last thing i see in the log is that the DFS scan was successfull. According to luci IF is up and running. Snap build from yesterday. Edit: MT7915 AsiaRF AW7915-NPD, MT7916 AsiaRF AW7915-NPD Edit2: reverting the drivers back worked for me. 5ghz with 160mhz works perfect. |
|
@ryderlee1110 if this is an EEPROM issue and it's now affecting devices from multiple vendors, we will need a generic workaround in the driver. Especially since this shows up as a regression with newer firmware. |
|
Reported to AsiaRF, thanks for looking into these, any patches is welcome to test out. |
|
Try to use default bin to rule out eeprom issue. |
|
Please help to test if this patch works, thanks. https://gist.github.com/csyuanc/42f97e65c22e7dd21b99097fe1b96b14 |
|
@ryderlee1110 Thanks @csyuanc !, great work, now newest firmware files working fine. |
|
Thanks, having the same issue. Applied the patch 5GHz now work fine but it remove the 6GHz support. How to get the 6GHz support back? Edit: |
|
I didn't test 6 Ghz before, only 5 Ghz, ping @csyuanc @ryderlee1110 @nbd168 |
|
Testing the latest mediatek firmware files from here, looks like it haven't been fixed yet. Probably we are 'doomed' to use those old firmware files. |
|
@NotANormalNerd |
|
No sadly I haven't gotten it to work yet. I did have not yet have go at it, since there was no real change here. P.S: I also got a Banana Pi R3, which also has some Mediatek chips, but works wonderful for my purposes. |
|
New patches by Carson has been posted in here, but I've seems cannot quite figuring it out to use it properly, the patches are originally targeting kernel 5.19. My AsiaRF 7916 being detected as the following by hwinfo : From the patches notes and codes, since in OpenWrt the firmware files located in /lib/firmware/mediatek I need to create the following file in my /lib/firmware/mediatek/fwcfg-mmio-0000:05:00.0.txt or with content : Here is the patches for mt76 incase anyone wanted to test it (Updated 2nd time ). 0001-wifi-mt76-mt7916-Support-per-radio-configuration-firmware-file.patch |
|
With above patches, it seems that 5G is working fine with newest firmware files but still 6G is still broken : |
|
@trippleflux that's surprising, I could manually apply the code changes from the patch found on patchworks on my kernel (a 6.2-rc4 from wireless-next) and successfully use the latest firmware from the linux-firmware repository in the 6GHz band. |
|
@florisch w00t Thanks for the confirmation, I am also doing manual merge and created that patch file for mt76, so I must be doing something wrong during that merge, would you mind if you share your applied code changes from mt7915/eeprom.c, I've meant the whole changed mt7915/eeprom.c file. Also OpenWrt is currently using kernel 5.15, I am not really sure to which that I need to apply on the patch file, either this repo or the kernel. Especially these lines : |
|
@ivankexko |
|
@trippleflux as requested in #720 (comment) here is the full eeprom.c after applying the patch that allow me to use 6GHz. The lines you mentioned seems identical. |
|
@florisch thank you, indeed that's identical, probably it's only problematic with OpenWrt, still trying to narrow it down. |
|
Hi all, Finally we've made some modifications on the calibration parts to let 5+6 work on band1. Please note that if you want to do peak performance tests, we still recommend modifying the eeprom band1 config to 5g or 6g only. |
|
Is it supposed to work without patches with the above-noted firmwares? Because with today's snapshot (though with none of the above patches), I cannot get either an AW7915-NPD or an AW7916-NPD to work correctly on it's "second" radio no matter what firmware I use. Both radios show up, and appear to be more or less correctly identified. I say more or less because while the 7915 displays as expected, the 7916 appears as "Generic 802.11". But with both cards the first 2.4ghz radio is identified as as 802.11axbgn, and the second 5ghz radio as 802.11acaxn. However any time I try and scan with the card's "second" radio, it (like the first radio) displays only 2.4GHz stations. In 22.03.3 scan works as expected on both radios. With the latest snapshot I have used the firmware that came with it, along with this firmware:
and this firmware:
This is on an MT7622 device, which has its own built-in radio. My /etc/config/wireless is: |
|
@VA1DER |
Yes. And verified in dmesg by the firmware date that they have been loaded. For example, this firmware mt7916_test_fw.zip produces: |
|
@VA1DER @csyuanc @florisch |
Yes, I originally tried this firmware. I can get it to work in AP mode, but not in client and scanning does not work on the second radio. With the old firmware, does scanning on the second radio work for you? How about with new firmware the patches? |
With my attached firmware, no additional patches are needed.
|
|
@csyuanc Because for me, after selecting CA/Canada as the country and save apply, and selected 6G channel, Max Transmit Power listed as 255 dBm : And 6G AP SSID doesn't shows up |
|
I use OpenWrt-21.02, but sync backports and mt76 version with OpenWrt trunk. |
|
@csyuanc |
|
I have tested the proposed firmware (HW/SW Version: 0x8a108a10, Build Time: 20230202144915a) and I can't see any performance or functional difference between this new firmware and the v21111230 firmware from linux-firmware (i.e. the one before 2022-11-23). I tested:
I did not test 2.4 GHz or DFS channels. And i can't find any 255 dBm weirdness in iw phy/iw dev. My setup is:
|
EDIT: Apologies, disregard this. The firmware seems to work fine. My problem was that I still had a kernel module installed that had the patch when I thought I had reverted.. Device: Banana Pi BPI-R64 v1.2 Have tried with and without this patch: https://gist.github.com/csyuanc/42f97e65c22e7dd21b99097fe1b96b14 What is needed to get 6GHz to appear in LuCI? |
|
I can confirm that a fresh snapshot from 03-31-2023 ( I've tested 160Mhz on channel 100 with DFS and it works as expected with great performance. Below is the results of me sitting 5 feet line of sight from the AP. $ iperf -c 192.168.1.71
------------------------------------------------------------
Client connecting to 192.168.1.71, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[ 1] local 192.168.1.53 port 44362 connected with 192.168.1.71 port 5001 (icwnd/mss/irtt=14/1448/1502)
[ ID] Interval Transfer Bandwidth
[ 1] 0.0000-10.0337 sec 1.61 GBytes 1.38 Gbits/sec |
|
|
|
@Batchyx |
|
@ibrtuyima I just used wpa_supplicant from git and set |
|
Hi is there any solutions for the current 23.05 stable release? |
|
has there been any updates to this I am trying to get wifi 6 bands to work |
|
@thyTwilightGoth @jayjar291 This has been fixed a long time ago. For me 6Ghz is working on a AW7916-NPD on OpenWRT 23.05. You need to use WPA3 SAE (CCMP) & Management Frame protection. But then everything is working fine. Check your logs. |
|
@NotANormalNerd What did you do to make it working? Is it detected as Generic MAC80211 or MediaTek device? Does DBDC work as well? |
|
It doesn't matter if it is recognized as generic or not, that is just a txt file that maps the PCIe ID to the names. The chip you are using is not in that file yet, that is why it is generic. DBDC works wothout problems for me on 23.05. What does your log say? Here is my setup: https://dennis.schmalacker.cloud/posts/openwrt-mikrotik-rbm11g-setup/ |
|
@NotANormalNerd this is what I have for my wireless config and it still does not show up on any wifi 6 or 6e devices and I have not found any obvious errors in the system or kernel logs |
|
also, this is a tri-band card is there any way to enable the third band? I am hoping that I can run 1 2.4g, 5g, and a 6g band |
|
@jayjar291 Just grepping for hostapd: Also the MT7916 is a dual band chip, but supports either 5 Ghz or 6 Ghz. You are also missing the channel selection Did you install the correct firmware?
|
|
@NotANormalNerd yes I've installed the correct firmware. I have also set the country code to US. And whenever I select the 6GHz band the channel selector disappears. What package are you using for wpa3? I've installed the wpad-basic-openssl package |
|
Try setting the country to CA. Also like NotANormalNerd said, you can't use all 3 bands at once. The second band is either 5ghz or 6ghz, not both at the same time. |
Hi there,
Recent (Nov 2022) changes to MT7916 firmware files, e.g. in linux-firmware commit cdf9499cf6706b73935a139bb5e76777a87674fe (link), break DBDC for me.
This manifests as being unable to transmit or receive from the 5/6GHz PHY on my AW7916-NPD (mt7916) through any manner. For example, stock hostapd is pointed at the card with this configuration:
... but despite not seeing any warnings when running
wifi, no beacons are sent.Tested on Extreme Networks AP3825i (mpc85xx) running OpenWrt current snapshot (r21523-4609228432).
Also tested using this board on OpenWrt 22.03.2,
kmod-mt76package version5.10.146+2022-09-06-d7054646-4.Reverting to firmware files from before linux-firmware's cdf9499cf6706b73935a139bb5e76777a87674fe fixes the issue.
The text was updated successfully, but these errors were encountered: