After reverting to old stock V1.0.0.68 and doing an additional reset, I was able to get 5GHz to broadcsst intermittently by playing with the R9000's wifi button. About every other boot came up unconnectable, so kept rebooting and waiting 5 minutes to see if 60GHz light came on. Only on the boots where it did, I could activate 5GHz briefly by pressing the wifi button once to disable and again to enable. But the 5Ghz would only stay active for about 25 seconds, then go down for a few minutes then come back for about 25 seconds, and repeat. During the 25 seconds ON, I was able to brefly connect a client on 5GHz! Still not quite workable, and no sign of 2.4GHz at all.
I then updated to latest stock V1.0.5.28, and now it booted into a connectable state more relaibly but the 5GHz was up for only 5-10 seconds so I wasn't able to even briefly connect.
I then flashed and fiddled more with latest Voxel V1.0.4.52HF, which wouldn't light the 5GHz LED at all and showed no sign of actual broadcasts (other than probably 60G).
I just reloaded dd-wrt r47097. No 5GHz at all, but possibly just due to nonfunctional wifi button. No 60GHz either, but I think that's just not yet supported.
Revisited calibration data paying better attention to case, and sucessfully restored different backup of calibration data. Spoiler: Unfortunately, it made no detectable difference to my wifi issues on dd-wrt, but I'll try again with stock.
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:~# md5sum /tmp/ART*
d27c350769de9a266321b754c0ef07d4 /tmp/ART-bak.backup
ac330e636b011e13463106e250ab5a2c /tmp/ART.backup
root@DD-WRT:~# mtd -r write /tmp/ART-bak.backup ART
Success!!! After restoring backup of cal data above, I did a GUI reset, then a 7-second reset button reset, then put it in TFTP mode and flashed to oldest stock again. To my amazement, it booted right up with working 5GHz (and 60GHz if I'm to believe the LEDs). Still no 2.4GHz, but that's more likely hardware so I'll leave that for another day. It's been up with continuous 5GHz for over 20 minutes now. Knock on wood, but it sure looks like my 5GHz is fixed on at least old stock firmware after restoring the on-unit cal data backup!
Edits: I guess I was so excited that I made too many typos, now fixed. _________________ 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 17:20; edited 2 times in total
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 (?)
I'm not sure if second to last command worked since no output, but when I ran last command for good measure it says that the flash_erase command was not found. This is on current dd-wrt r47097.
I haven't seen a way to run CLI (e.g., from telnet) on stock. Is there one?
I've heard there's a way to enable telnet on Voxel, but haven't spotted it yet. _________________ 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 19:32; edited 1 time in total
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Fri Jul 30, 2021 19:22 Post subject:
How do you think Netgear devices retain all of the information including the default SSIDs and passwords, etc. when you flash to DD-WRT? The partition "netgear".
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Fri Jul 30, 2021 19:31 Post subject:
So, in DD-WRT, you could try mtd -r erase netgear and see how that turns out. But again, that partition is relevant to DD-WRT. Otherwise, Netgear devices would get all the usual DD-WRT default settings for wireless and not the settings from stock firmware.
The ART partition(s) are used to write "netgear". Use strings in DD-WRT; that is another option. Anyhow, do what you wish. Not my router, not my monkeys, not my circus. And I am not going to try and find posts that are likely now missing in the R7800 or R9000 threads. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Last edited by kernel-panic69 on Fri Jul 30, 2021 19:35; edited 1 time in total
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Fri Jul 30, 2021 19:37 Post subject:
We're talking about the R9000, thanks for mucking up continuity of my edit. Perhaps art is used to write nvram on R7800, whichever. But that is the partition that must be wiped out to fix wifi on the R9000, which is what is being discussed. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Fri Jul 30, 2021 20:23 Post subject:
He did it on DD-WRT. This restoration has to be done with stock / Voxel as best I understand it. Anyhow, mine is still on a shelf and I haven't touched it yet, but I am going to tinker with it in the next week to see if I get any joy. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
http://routerlogin.net/debug.htm is where you enable telnet.
Ah, thanks! Unfortunately, that's the Netgear site-based big-brother interface that's unreachable unless already logged into the router by wifi (and, of course, connected to the Internet). Otherwise it's inacessible with an error message that you must be logged in via wireless! Is there some way to enable telnet on stock locally and most importantly without wifi?
Immediately after my attempted erase of netgear partition (as posted above), I tftp flashed from dd-wrt directly to latest stock. After playing with wifi button, 5G started working for half a minute at a time every 2-3 minutes, and I was finally able to briefly login to latest stock via wifi for up to 2-1/2 minutes at a time if I immediately turned OFF/ON the wifi button as soon as it automatically disabled. When I tried disabling any radio or WPS in advanced wireless, I always got the error message "WPS process in progress, please apply the settings later" and eventually the WPS settings greyed out.
I then webflashed from latest stock directly to oldest stock, and low and behold 5G is working solid again! I'm just afraid to reboot it now... Can anyone think of any pertinent testing while 5G is up? It's currently offline, but I might be able to move it without losing power to access the Internet and hopefully reach the hosted debug page while on wifi to enable telnet.
EDIT #1: There is something a little odd, though. When I connect via 5G wifi the 5G LED flashes as expected for wifi traffic. But when I turn off the PC wifi and connect to the R9000 by cable, both the used lan port LED and the 5G LED flash for just the wired LAN traffic, while the 60G LED stays solid. If I disconnect the LAN cable then both the 5G and 60G LEDs are solid without any flashing.
EDIT #2: I've just downloaded all 24 stock firmwares that blkt posted on first page. If I do make the effort to enable telnet on oldest stock via wireless and Internet, should that setting survive stock firmware updates? I'm thinking of going through them in sequence to find where wireless breaks.
EDIT #3: I noticed that the default SSID NETGEARxx last two digits changed for all three radios, as did the stock wifi password, so now both are different than printed on the router sticker! I guess my ART-bak partition might have been from or for a different unit, and perhaps I successfully erased the netgear partion the first time so reverting to stock re-poplated it from the different restored ART. I'll have to try restoring the original ART at some point to see what difference it makes. _________________ 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: 14126 Location: Texas, USA
Posted: Sat Jul 31, 2021 1:26 Post subject:
That URL works whether connected by wire or wireless. Now, if you know the router's IP address, you can use that with the appended 'debug.htm' as well. The only way you won't be able to use that URL is if you improperly set a static IP on your client device AFAIK. I don't recall Voxel killing that URL, but hey... anything is possible. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net