DSL-2640T updated like a charm
Well, it seems that did not help as well. The AP is down again today when I turned on the router. I double checked the EEPROM values that were working and now they don't. The issue is, even the defragged mtd3 has duplicate values and I ran the script twice or thrice. Is that the reason why it is happening or is this possibly a partition corruption issue?
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
Probably a corrupt mtd3. I am not aware of any tool that can clean up a corrupt mtd3 partition, so you're a bit stuck there.
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.
what about that thread i referenced before? and what if i use the tiupgrade utility or the dlink-firmware fix utility with the "corrupted image mode" option checked?thechief wrote:Probably a corrupt mtd3. I am not aware of any tool that can clean up a corrupt mtd3 partition, so you're a bit stuck there.
Well, I'd agree with mstombs here. The reason is that normally one needs to set NVS_TFTP_LOAD to 0, such that when the router boots, it should not look for the EEPROM. The issue with my router is something strange. Even if I leave that setting to 1, the AP comes to life at random boots. What could be affecting it? Power, less voltage or a hardware failure?
Definitely worth checking/swapping the PSU, they can fail.
I can now also explain why your env cleaned itself up - the router code automatically defrags the env area if it fails to write - found this in the kernel code that handles the writing of to ticfg/env
older adam2 has similar using fixenv.
I can now also explain why your env cleaned itself up - the router code automatically defrags the env area if it fails to write - found this in the kernel code that handles the writing of to ticfg/env
Code: Select all
/* write the variable/value pair to flash */
if(adam2_env_set_variable(pvar, pval) != 0)
{
printk(KERN_WARNING "Defragginig environment variable region.\n");
adam2_env_defrag();
if( adam2_env_set_variable(pvar, pval) != 0 )
printk(KERN_ERR "Failed to write %s to environment variable region.\n", pvar);
}
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
Check the wireless card and ensure that it is well seated (i.e., not a loose connection). This will require opening up the router, and will probably invalidate any warranty that you might have left.
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
What you really need is a clean mtd3 from someone with the same router. But that is not an easy option. The person would first need to reset to factory defaults, then backup the mtd3 partition, download it to hard disk, and send to you. You will then need to copy it over your current mtd3, and then reset the WLAN_EEPROM* variables to the correct ones for your router (from you backed up environment).
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
Upload the image to the router's /var directory (you can use WinSCP). Telnet to the router, and run this command (assuming the file is called "mt33.bin"):
and hope for the best. Reboot the router, and then restore the correct WLAN_EEPROM* variables.
Code: Select all
cp /var/mtd3.bin /dev/mtdblock/3
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.
got that. one question though, should i use WEB to restore the values or the ones that were in my env from the original firmware, before using WEB or rebuilding them?thechief wrote:Upload the image to the router's /var directory (you can use WinSCP). Telnet to the router, and run this command (assuming the file is called "mt33.bin"):and hope for the best. Reboot the router, and then restore the correct WLAN_EEPROM* variables.Code: Select all
cp /var/mtd3.bin /dev/mtdblock/3
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
The saved working values should be the starting point.
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.