回复 5#hua519
不知你是否已经解决,找到一点东西供你参考:
For the people, who do not have their WLAN working, after the upgrade or even so before the upgrade, please follow the steps below:
A common issue for many people on a router exists, where the AP stays off and only comes online by using "echo NVS_TFTP_LOAD 0" > /proc/ticfg/env". However, this can create issues on the environment side and the solution itself is temporary too. The actual issue is a corrupted WLAN EEPROM, which needs to be fixed:
- Extract WEB (Wireless Environment Builder) somewhere in a directory and open it up.
- Fill up the information it asks for.
- If you do not have a TWNET ID, go to your router's system logs. They can be found in Status->SystemLog. Browse them and find the line where it says:
"Failed to get DIE ID from wlan driver. Cannot validate EEPROM Image"
....
....
"Setting bootloader env NVS_TFTP_LOAD to 1"
- Look for a string similar to this:
"Retrieving EEPROM image file nvs_5e015cf4a901151d.bin from TFTP Server"
"ERROR: TFTP of file : nvs_5e015cf4a901151d.bin failed"
- there, the string next to "nvs_" is your TWNETID i.e.5e015cf4a901151d.
- copy it the WEB and click on "get router details" or "build environmen"t. it should work and after a while, it will ask you that it can send the script directly to the router. Do so, and let the router reboot after that. You're done, once the Router comes back online, go check your environment now and marvel over the wrong settings reported by RUC, now corrected.
I hope this will help many people. Things that can help RouterTech guys enhance the firmware and tools.