Joined: 16 Nov 2015 Posts: 6435 Location: UK, London, just across the river..
Posted: Sun Oct 25, 2020 23:42 Post subject:
boixa wrote:
Hi, my r9000 has also not working 2,4 and 5ghz. What can I do to help solve this problem? I've benn looking into the netgear forums, and read that there are loads of r9000 with the same problems. I tried all the firmware I could get hold of. But no way to make the radios work. the ad wifi works under stock Firmware.
Right now flashed dd-wrt with the images found on the main Page. I ordered a usb to TTL with 5v and 3,3v. What do i have to use 3,3 or 5?
Thx for the Help
Luis
many R9000 with faulty radios...its there week point, there is a good batch and bad one...i guess, as i also had one faulty and sold it to a friend...
if radios are not working, under stock firmware, your best move is, to get another DDWRT supported router, preferably good one with good either x3 stream or x4 stream radios (antennas) and run it as a WAP, wired to one of the LAN ports on R9000, that's how my friend is running it at the moment...
you can have a look at Archer C7 v2 or v3 or v4 for this WAP mode...but any other DDWRT supported router will do... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55779 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
did you manage to kill your calibration data? your kernel log shows that all your wifi cards are not present on the pci bus. this is not just strange. this looks like a broken hardware unless there is a new r9000 hardware revision which is unknown to me
i have the most recent r9000 dd-wrt firmware installed on mine. its working
another possible cause could be if the nvram var "noath10k" is set to 1
My R9000 project is showing one rather than two qca9984 radios, but even that one "Radio is Off" in Status/Wireless.
If/when we manage to kill our calibration data on an R9000, how can we restore it?
My nvram backup doesn't have "noath10k". Should I add it and set to 0? _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
Welcome to the leaky boat! I've shared "ART" calibration data before, but that wasn't the issue. I think something's getting corrupted elsewhere, possibly from an errant memory leak, hardware reset pin glitch, or internal race condition.
I'm not sure how to copy the whole 512 MB NAND flash (much less any hidden persistent registers and/or NOR flash), and I've yet to see an R9000 memory map. But I think a full NAND read and write can probably be done from a serial console (where pins seem to already exist on the R9000's main board, so soldering might not be needed).
I've found that a relatively safe and easy reset that's apparently more thorough than either a GUI reset or a 7-second reset pin reset can be achieved by a 2-step process including:
1) First, resetting nvram and netgear partition via telnet/cli:
2) Second, flashing from DD-WRT to stock Netgear or Voxel flavored firmware.
For the flash part of that reset, I've had hit or miss reset results by TFTP flashing from DD-WRT to oldest Netgear firmware (v1.0.0.68), and suspect that the reset pin is causing corruption. I'm not sure if there's any way to TFTP flash without touching that pin.
I've had noticeably better reset results for the the flash part of that reset by GUI flashing from DD-WRT to stock Netgear, but that requires a bin flash file rather than an img flash file. Kong released such a bin on 2017 February 21st, which flashes from DD-WRT to stock Netgear v1.0.1.36 via DD-WRT GUI. I'm not sure if other bin files exist to other stock versions or how to make a bin from another img (perhaps there are headers and checksums to deal with).
Unfortunately, although I can get 5G working by the above hacks in various stock Netgear releases (or presumably Voxel if I had an appropriate bin), something usually goes wrong on the very next flash to anything, so I've yet to make it all the way back to DD-WRT with 5G intact.
EDIT: There are apparently two hardware versions of R9000. Early versions with FCC ID PY316... apparently had bluetooth while later versions with FCC ID PY317... apparently did not. Per the label, mine's the later non-bluetooth version. _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
If not hardware failure it is possible something corrupted which normally requires back to netgear for repair.
So I understand where this is going to have full flash dumps to compare 100% working to radio failure units.
But unfortunately this isn't enough just before flashing back to DD-WRT. 5G still never works on the rebound.
But what I posted above was also correct. That is, on at least my later non-Bluetooth hardware version R9000, this is the command that I used from a DD-WRT ssh session:
Code:
mtd erase netgear
It definitely erased some part of flash and output confirmation messages, and seemed to be required to get 5G working if I then immediately flash to stock via GUI (e.g., using Kong's 2017-02-21 back-to-stock bin), FWIW _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
Mine is the older one with bluetooth; wifi has never recovered; still on Voxel. Something definitely corrupted the sh*t out of something or it's hardware failure. _________________ "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
I had played in the linked thread with the MAC addresses and then wondered why they are not restored by a factory reset or nvram erease
BS then told me that on some routers device specific data are stored exclusively in the nvram
and an erase only deletes unimportant data but not such as the MAC addresses
Last edited by ho1Aetoo on Thu Sep 23, 2021 6:39; edited 1 time in total
MAC addresses should be able to be read back from the chips...do we have a way to do it without opening up the router? If we can get the MAC addresses, we can use a Hex editor to write it in to the binary.img
Besides MAC addresses, what other pertinent data is stored in NVRAM that possibly could not be written back for a NIB R9000?
It's 3:30am for me... the new posts and firmware attempts starts in February 2021 of that thread. They are making strides. I was just reading through the thread but will look at trying the firmware tomorrow.
Joined: 16 Nov 2015 Posts: 6435 Location: UK, London, just across the river..
Posted: Thu Sep 23, 2021 10:57 Post subject:
inewton888 wrote:
It's 3:30am for me... the new posts and firmware attempts starts in February 2021 of that thread. They are making strides. I was just reading through the thread but will look at trying the firmware tomorrow.
in that thread that firmware for R9000 hosted in myopenrouter.com is crap and they discuss it...
so far there is no "working" OpenWRT firmware for R9000 nor better than DDWRT...and probably wont be soon... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55779 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913