Maybe if you used the commands for the R9000 and not the R7800, you would get some luck?
Thanks for the hint @kernel-panic69!
For "nvram", yesterday I'd also tried "nvram erase && reboot". Either seems to work, but I've actually been doing both consecutively just to be sure.
For "wlan", it must be a different command. I'd just flashed to voxel again, but will try a few other possibilities such as "ath" once I reflash to dd-wrt (since no CLI with stock or voxel, AFAIK).
the normal error pattern is that the two QCA9984 radios are defective and give no sign of life from itself
you could get the 60Ghz radio to work, but you need a 60Ghz antenna for the QCA9005 card and you can usually only get that by cannibalizing any old notebooks or dock with WiGig.
Thanks @ho1Aetoo! I've skimmed all but will have to read more thoroughly later.
While WWTK's R9000 discussion (including dd-wrt reporting WIL6210 on ath0 as 5GHz instead of 60GHz) is interesting, that's not the issue I'm having. In dd-wrt, the 5GHz wifi radio is properly showing for me on QCA9984. Just to be clear, none of the radio LEDs stay on in dd-wrt, but the 60G (only) LED now stays on in voxel and stock.
As for getting the fan to operate, when I tried yesterday to use Netgear's hosted big-brother interface, I got an error message that I couldn't connect to that unless connected to the R9000 via wifi (rather than ethernet)! Catch-22! When I tried on stock f/w simply accessing debug.htm locally (192.168.1.1/debug.htm), the page was unresponsive.
At the bottom of https://wiki.dd-wrt.com/wiki/index.php/Netgear_R9000, it says: "Also note that the SFP+ modules do get hot. I would change the fan threshold parameters to make sure that your R9000 fans stay on 24/7. They aren't loud and could help keep mobo and CPU speeds in check during the incoming summer months while transferring files at 10 gb/sec in your new VLAN." Unfortunately, I found no mention as to how to accomplish that other than potentially Netgear's hosted interface (only once wifi is working).
I'll dig out the infrared pyrometer and measure actual internal chip temperatures once I've finished reading these links and exhausted a few other less invasive possibilities. _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
msoengineer says that his fan is working and I think he has set the temperature via WebIF > Tab > Service.
Thanks! The GUI fan ON/OFF temperature settings in Services/Services worked, so I've now confirmed that the fan operates properly (at least at seemingly slow speed).
Still trying to find commands to manually bring radios up and down.
In the linked thread, Brainslayer mentioned that
Quote:
another possible cause could be if the nvram var "noath10k" is set to 1
I can't find the variable "noath10k" in my nvram backup, so does that mean that it's necessarily 0 or should I specifically set it to 0?
Not sure if pertinent, but the 10G LED is always ON despite that I don't have any SFP+ module installed (I'm only using the 1G ethernet port so far). _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
Some observations with this particular R9000 when running various firmwares:
On latest dd-wrt (r47090), 2.4GHz and 60GHz LEDS are always OFF; 5GHz LED flashes ON/OFF once about 25 seconds into boot sequence, but then stays OFF. Wireless button LED (second from last towards right side) is either always ON or always OFF, every other reboot (as is the 10G LED - either both ON or both OFF). Oh, and on the reboots when the 10G and wireless LEDs are both ON, I can connect via ethernet cable; but when they're both OFF, I can't connect (static or DHCP address).
Does anyone have 60GHz working on dd-wrt? Could I use a Ka-band (39G?) WWAN antenna for a client's qca9005 60G WLAN?
On latest stock (V1.0.5.28), 2.4GHz is always OFF, 5GHz is sometimes OFF but never broadcasting, and 60GHz is always ON but haven't confirmed broadcast yet.
On latest Voxel (V1.0.4.52HF), all three radios are ON, but seemngly no broadcasts on at least 2.4GHz and 5GHz. _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
It looks like my R9000 has its current (possibly corrupt) calibration data as well as a backup.
I copied both and they have different hashes.
Trying to install the backup, but mtd is read-only:
Code:
root@DD-WRT:~# cat /proc/mtd
dev: size erasesize name
mtd0: 001e0000 00020000 "u-boot"
mtd1: 00120000 00020000 "u-boot-env"
mtd2: 00140000 00020000 "ART"
mtd3: 00140000 00020000 "ART.bak"
mtd4: 00440000 00020000 "kernel"
mtd5: 02800000 00020000 "rootfs"
mtd6: 006c0000 00020000 "ddwrt"
mtd7: 02c40000 00020000 "linux"
mtd8: 04480000 00020000 "netgear"
mtd9: 12c00000 00020000 "plex"
mtd10: 05780000 00020000 "reserve"
mtd11: 00080000 00020000 "crashdump"
mtd12: 00380000 00020000 "language"
mtd13: 00120000 00020000 "nvram"
mtd14: 00120000 00020000 "pot"
root@DD-WRT:~# dd if=/dev/mtd2 of=/tmp/art.backup
2560+0 records in
2560+0 records out
root@DD-WRT:~# dd if=/dev/mtd3 of=/tmp/art-bak.backup
2560+0 records in
2560+0 records out
root@DD-WRT:~# mtd -r write /tmp/art-bak.backup art
Could not open mtd device: art
Can't open device for writing!
root@DD-WRT:~# uboot
-sh: uboot: not found
root@DD-WRT:~# dmesg / logread
...
[ 2.628377] READ DNI CMDLINE!
[ 2.631338] dni_cmdline: Alpine nand flash:1920k(u-boot)ro,1152k(u-boot-env)ro,1280k(ART),1280k(ART.bak),
4352k(kernel),40960k(rootfs),45312k@0x580000(linux),70144k(netgear),307200k(plex),89600k(reserve),
512k(crashdump),3584k(language),1152k(nvram),1152k(pot)
[ 2.654153] 14 cmdlinepart partitions found on MTD device Alpine nand flash
[ 2.661098] Creating 14 MTD partitions on "Alpine nand flash":
[ 2.666927] 0x000000000000-0x0000001e0000 : "u-boot"
[ 2.672409] 0x0000001e0000-0x000000300000 : "u-boot-env"
[ 2.678175] 0x000000300000-0x000000440000 : "ART"
[ 2.683348] 0x000000440000-0x000000580000 : "ART.bak"
[ 2.688860] 0x000000580000-0x0000009c0000 : "kernel"
[ 2.694359] 0x0000009c0000-0x0000031c0000 : "rootfs"
[ 2.700096] mtd: partition "rootfs" set to be root filesystem
[ 2.706001] magic 73717368 vs 73717368
[ 2.709828] mtd: partition "ddwrt" created automatically, ofs=2B00000, len=6C0000
[ 2.717388] 0x000002b00000-0x0000031c0000 : "ddwrt"
[ 2.722788] 0x000000580000-0x0000031c0000 : "linux"
[ 2.728465] 0x0000031c0000-0x000007640000 : "netgear"
[ 2.734512] 0x000007640000-0x00001a240000 : "plex"
[ 2.742077] 0x00001a240000-0x00001f9c0000 : "reserve"
[ 2.748256] 0x00001f9c0000-0x00001fa40000 : "crashdump"
[ 2.753948] 0x00001fa40000-0x00001fdc0000 : "language"
[ 2.759571] 0x00001fdc0000-0x00001fee0000 : "nvram"
[ 2.764918] 0x00001fee0000-0x000020000000 : "pot"
[ 2.770493] libphy: Fixed MDIO Bus: probed
...
root@DD-WRT:~# kmod-mtd-rw
-sh: kmod-mtd-rw: not found
root@DD-WRT:~# opkg install kmod-mtd-rw
-sh: opkg: not found
root@DD-WRT:~# opkg_install kmod-mtd-rw
-sh: opkg_install: not found
root@DD-WRT:~# opkg_install_cmd kmod-mtd-rw
-sh: opkg_install_cmd: not found
root@DD-WRT:~# opkg update
-sh: opkg: not found
root@DD-WRT:~# u-boot
-sh: u-boot: not found
root@DD-WRT:~#
...
root@DD-WRT:/jffs# ipkg update
-sh: ipkg: not found
Any alternate suggestions on how to restore the backup copy of calibration data to mtd2?
Or might the router already be switching calibration data sets between reboots? _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Thu Jul 29, 2021 15:08 Post subject:
I don't think it's a cal data issue, but it could be as stated in the other thread. I am going to dig out the R9000 and tftp it back to stock and then install Voxel and see if I can revive my wi-fi per the instruction which does not necessarily apply to dd-wrt, unless dd-wrt has the ngmtd binary installed (?)... if I can revive mine, I can try to provide information to see if there was a hardware revision that broke things as noted in the other thread. Please don't expect that I mean that I am going to drop everything this very second and do this
Thanks all for the hints! I actually received my qca9005 today. I'll get back to dd-wrt and probably swap cal data once I see if 60 GHz works on stock/Voxel. I've got mismatched antenna connectors to deal with at the moment...
EDIT: (Cal data backups removed) _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
Last edited by o2bad455 on Fri Jul 30, 2021 22:37; edited 4 times in total
P.S. You can't use 'art' for 'ART'. Capitalization does matter...
Oops, does that mean I didn't really capture the cal data? Or do you just mean for:
Code:
md5sum /tmp/ART*
I guess I'm probably OK since I only referenced mtd to grab them, and just used "art" for naming my own files. Either way, I'll keep that in mind for next time, thanks! _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
