I have a couple Netgear WAX202 AP/routers that I have installed 22.03.02. On one it is working great without issues. On the other wireless is not showing up. On the unit that is not working in the dmesg output I see errors with the wireless card but I am not sure if anything can be done to initialize it so it works. I did have both units set up and working with the Netgear firmware so at one point both units were working fully. Here is what I see from the console. Any help to getting the wifi working would be appreciated.
root@OpenWrt:/tmp# ubus call system board
{
"kernel": "5.10.146",
"hostname": "OpenWrt",
"system": "MediaTek MT7621 ver:1 eco:3",
"model": "Netgear WAX202",
"board_name": "netgear,wax202",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "22.03.2",
"revision": "r19803-9a599fee93",
"target": "ramips/mt7621",
"description": "OpenWrt 22.03.2 r19803-9a599fee93"
}
}
root@OpenWrt:/tmp# dmesg | grep 7915
[ 3.828253] pci 0000:02:00.0: [14c3:7915] type 00 class 0x000280
[ 15.602184] mt7915e_hif 0000:01:00.0: enabling device (0000 -> 0002)
[ 15.620340] mt7915e 0000:02:00.0: enabling device (0000 -> 0002)
[ 15.878770] mt7915e 0000:02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20211222184017a
[ 16.214681] mt7915e 0000:02:00.0: WM Firmware Version: ____000000, Build Time: 20211222184052
[ 16.254042] mt7915e 0000:02:00.0: WA Firmware Version: DEV_000000, Build Time: 20211222184111
[ 16.372890] mt7915e 0000:02:00.0: eeprom load fail, use default bin
[ 16.379356] mt7915e 0000:02:00.0: Direct firmware load for mediatek/mt7915_eeprom_dbdc.bin failed with error -2
[ 16.389427] mt7915e 0000:02:00.0: Falling back to sysfs fallback for: mediatek/mt7915_eeprom_dbdc.bin
[ 16.502920] mt7915e: probe of 0000:02:00.0 failed with error -12
root@OpenWrt:/tmp#
Good question, I did not think to check to see if it was there. Is the folder path just /mediatek? I will say that after doing the conversion I did an upgrade with the same version to try and refresh things and it did not help.
Am I reading this correct? Either the file is not there or the system is referencing the wrong file.
root@OpenWrt:/# find / -type d -name mediatek
/lib/firmware/mediatek
/rom/lib/firmware/mediatek
root@OpenWrt:/# cd /lib/firmware/mediatek/
root@OpenWrt:/lib/firmware/mediatek# ls
mt7915_rom_patch.bin mt7915_wa.bin mt7915_wm.bin
root@OpenWrt:/lib/firmware/mediatek# ls /rom/lib/firmware/mediatek/
mt7915_rom_patch.bin mt7915_wa.bin mt7915_wm.bin
root@OpenWrt:/lib/firmware/mediatek# dmesg | grep 7915
[ 3.828253] pci 0000:02:00.0: [14c3:7915] type 00 class 0x000280
[ 15.602184] mt7915e_hif 0000:01:00.0: enabling device (0000 -> 0002)
[ 15.620340] mt7915e 0000:02:00.0: enabling device (0000 -> 0002)
[ 15.878770] mt7915e 0000:02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20211222184017a
[ 16.214681] mt7915e 0000:02:00.0: WM Firmware Version: ____000000, Build Time: 20211222184052
[ 16.254042] mt7915e 0000:02:00.0: WA Firmware Version: DEV_000000, Build Time: 20211222184111
[ 16.372890] mt7915e 0000:02:00.0: eeprom load fail, use default bin
[ 16.379356] mt7915e 0000:02:00.0: Direct firmware load for mediatek/mt7915_eeprom_dbdc.bin failed with error -2
[ 16.389427] mt7915e 0000:02:00.0: Falling back to sysfs fallback for: mediatek/mt7915_eeprom_dbdc.bin
[ 16.502920] mt7915e: probe of 0000:02:00.0 failed with error -12
root@OpenWrt:/lib/firmware/mediatek#
frollic
December 18, 2022, 6:54pm
5
compared to the working one ?
No differences I can see other than the firmware loaded.
Working
root@OpenWrt:~# working
-ash: working: not found
root@OpenWrt:~# dmesg | grep 7915
[ 3.854753] pci 0000:02:00.0: [14c3:7915] type 00 class 0x000280
[ 16.153945] mt7915e_hif 0000:01:00.0: enabling device (0000 -> 0002)
[ 16.172035] mt7915e 0000:02:00.0: enabling device (0000 -> 0002)
[ 16.437075] mt7915e 0000:02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20211222184017a
[ 16.772100] mt7915e 0000:02:00.0: WM Firmware Version: ____000000, Build Time: 20211222184052
[ 16.810345] mt7915e 0000:02:00.0: WA Firmware Version: DEV_000000, Build Time: 20211222184111
root@OpenWrt:~# ls /lib/firmware/mediatek/
mt7915_rom_patch.bin mt7915_wa.bin mt7915_wm.bin
root@OpenWrt:~#
Non-working
root@OpenWrt:~# dmesg | grep 7915
[ 3.828253] pci 0000:02:00.0: [14c3:7915] type 00 class 0x000280
[ 15.602184] mt7915e_hif 0000:01:00.0: enabling device (0000 -> 0002)
[ 15.620340] mt7915e 0000:02:00.0: enabling device (0000 -> 0002)
[ 15.878770] mt7915e 0000:02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20211222184017a
[ 16.214681] mt7915e 0000:02:00.0: WM Firmware Version: ____000000, Build Time: 20211222184052
[ 16.254042] mt7915e 0000:02:00.0: WA Firmware Version: DEV_000000, Build Time: 20211222184111
[ 16.372890] mt7915e 0000:02:00.0: eeprom load fail, use default bin
[ 16.379356] mt7915e 0000:02:00.0: Direct firmware load for mediatek/mt7915_eeprom_dbdc.bin failed with error -2
[ 16.389427] mt7915e 0000:02:00.0: Falling back to sysfs fallback for: mediatek/mt7915_eeprom_dbdc.bin
[ 16.502920] mt7915e: probe of 0000:02:00.0 failed with error -12
root@OpenWrt:~#
This indicates broken hardware. For comparison, here is what a fully working WAX202 should produce:
# dmesg | grep 7915
[ 0.479157] clocksource: Switched to clocksource GIC
[ 3.857599] pci 0000:02:00.0: [14c3:7915] type 00 class 0x000280
[ 15.241447] mt7915e_hif 0000:01:00.0: enabling device (0000 -> 0002)
[ 15.259580] mt7915e 0000:02:00.0: enabling device (0000 -> 0002)
[ 15.519612] mt7915e 0000:02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20211222184017a
[ 15.855413] mt7915e 0000:02:00.0: WM Firmware Version: ____000000, Build Time: 20211222184052
[ 15.890014] mt7915e 0000:02:00.0: WA Firmware Version: DEV_000000, Build Time: 20211222184111
Look - no eeprom load fail. The /lib/firmware/mediatek/mt7915_eeprom_dbdc.bin does not exist and should not exist on this router.
Thanks patrakov. I was wondering if that was the issue. It was working prior to the OpenWrt flash. What is the easiest way to flash the WAX202 back to the stock firmware? TFTP? I would like to see if it works there.
I don't know. The git commit that introduced support for this device mentions both TFTP and NMRP. I'd suggest that you try both, but starting with NMRP.
StanL
January 27, 2023, 8:09pm
10
Any luck restoring the stock firmware?