Does mt7986_eeprom_mt7976_dbdc.bin exist?
Here is from 23.05.2:
ls /lib/firmware/mediatek
mt7986_eeprom_mt7975_dual.bin mt7986_eeprom_mt7976_dual.bin mt7986_rom_patch_mt7975.bin mt7986_wm.bin mt7986_wo_0.bin
mt7986_eeprom_mt7976_dbdc.bin mt7986_rom_patch.bin mt7986_wa.bin mt7986_wm_mt7975.bin mt7986_wo_1.bin
Yes:
BusyBox v1.36.1 (2023-11-14 13:38:11 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 23.05.2, r23630-842932a63d
-----------------------------------------------------
root@OpenWrt:~# logread -e TAG
root@OpenWrt:~# logread -e err
Tue Nov 14 13:38:21 2023 kern.info kernel: [ 1.130711] mt7530-mdio mdio-bus:1f: no interrupt support
Tue Nov 14 13:38:21 2023 kern.warn kernel: [ 10.030890] mt798x-wmac 18000000.wifi: Direct firmware load for mediatek/mt7986_eeprom_mt7976_dbdc.bin failed with error -2
Tue Nov 14 13:38:31 2023 daemon.warn odhcpd[1975]: No default route present, overriding ra_lifetime!
root@OpenWrt:~# ls /lib/firmware/mediatek
mt7986_eeprom_mt7975_dual.bin mt7986_eeprom_mt7976_dual.bin mt7986_rom_patch_mt7975.bin mt7986_wm.bin mt7986_wo_0.bin
mt7986_eeprom_mt7976_dbdc.bin mt7986_rom_patch.bin mt7986_wa.bin mt7986_wm_mt7975.bin mt7986_wo_1.bin
root@OpenWrt:~#
However with 23.05.2 Luci interface is extremely slow. Takes 10 seconds or more to load each page and WiFi also does not work, although the file is there.
In today's snapshot version the file isn't there, WiFi also does not work and LuCi is very snappy:
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt SNAPSHOT, r25598-a6991fc7d2
-----------------------------------------------------
root@OpenWrt:~# ls /lib/firmware/mediatek
mt7986_rom_patch.bin mt7986_wa.bin mt7986_wm_mt7975.bin mt7986_wo_1.bin
mt7986_rom_patch_mt7975.bin mt7986_wm.bin mt7986_wo_0.bin
yesterday's snapshot for TUF-AX6000:
→ cd build_dir/target-aarch64_cortex-a53_musl/root-mediatek/lib
user git[master+?] ../root-mediatek/lib
→ find . -iname "mt*"
./firmware/mediatek/mt7986_wm.bin
./firmware/mediatek/mt7986_rom_patch.bin
./firmware/mediatek/mt7986_rom_patch_mt7975.bin
./firmware/mediatek/mt7986_wo_0.bin
./firmware/mediatek/mt7986_wm_mt7975.bin
./firmware/mediatek/mt7986_wo_1.bin
./firmware/mediatek/mt7986_wa.bin
./modules/6.1.82/mt76-connac-lib.ko
./modules/6.1.82/mt7915e.ko
./modules/6.1.82/mt76.ko
Official 23.05.3 is ok too on my device.
[ 14.671103] mt798x-wmac 18000000.wifi: HW/SW Version: 0x8a108a10, Build Time: 20221012174648a
[ 14.671103]
[ 15.036085] mt798x-wmac 18000000.wifi: WM Firmware Version: ____000000, Build Time: 20221012174725
[ 15.203817] mt798x-wmac 18000000.wifi: WA Firmware Version: DEV_000000, Build Time: 20221012174937
[ 15.350030] mt798x-wmac 18000000.wifi: eeprom load fail, use default bin
[ 15.356787] mt798x-wmac 18000000.wifi: Direct firmware load for mediatek/mt7986_eeprom_mt7976_dbdc.bin failed with error -2
[ 15.367899] mt798x-wmac 18000000.wifi: Falling back to sysfs fallback for: mediatek/mt7986_eeprom_mt7976_dbdc.bin
Probably @GPereira's device has no correct factory partition and caldata_extract_ubi script fails.
Is there a bin file with the contents of that partition? We should write about it in the future device's wiki page.
Meanwhile, I've returned my device to the reseller and asked for a replacement. Let's see how it works when the new one arrives.
I am working on a wiki page for this router. Contributions are welcome: https://openwrt.org/toh/asus/rt-ax59u
Please start with installation section, all generic methods don't work with release image
Hi!
Are you trying to flash the kernel initramfs image through ASUS firmware update panel?
@frollic how did you generate that trx file?
Can we use the kernel initramfs image instead?
@remittor have a TRX file generator, but there's one linked to in the git commit.
Btw, this device is support in stable now - https://firmware-selector.openwrt.org/?version=23.05.3&target=mediatek%2Ffilogic&id=asus_rt-ax59u
Hi,
I'm on the latest Firmware V3.0.0.4.388_33147
Tried "simple installation" by remittor's openwrt-23_tuf-ax4200-initramfs.trx via ASUS firmware update panel - unsuccessful
sysupgrade by SSH - unsuccessful
mtd write by SSH - unsuccessful
Downgraded to 3.0.0.4.388.31345, same story:
openwrt-23_tuf-ax4200-initramfs.trx - Firmware upgrade unsuccessful
sysupgrade: not found
mtd: not found
Definitely doing wrong steps
Well, you obviously can't use the initramfs for the AX4200 to flash AX59U, don't you need the initramfs that's in the Git commit that @frollic linked to in OpenWrt support for Asus RT-AX59U - #18 by frollic?
So the only way yet is to use serial.
@remittor can you share your TRX file generator? Are these trx files the same as the initramfs bin file available in the firmware selector? Can we just use the bin file?
If we indeed depend on that TRX file to migrate from OEM to OpenWrt, I am not confident that a random Google Drive stays ok in years to come. Can we have something generated from the current OpenWrt version?
How is this handled in other ASUS models?
That's not what the git commit says.
We don't, but it makes life easier.
Why ?
You can sysupgrade to whatever version directly afterwards.
It's even in the git commit.
You must use TRX-image for AX59U router!
Also look this: Asus TUF AX4200 support - #223 by remittor
Similar.
No. This is a special initramfs image that is inside a special TRX-container.
I tried to add support for generating TRX-images to the official repository, but I encountered very strange behavior from the OpenWRT maintainers.
Therefore, most likely there will be no official support for TRX-images 