Some owners of TP-Link 1043, me too, have trouble with same things like region regulatory for example. Brainslayer wrote to 1-st of us, that it happens because flashing wrong image of Buffalo to TP-Link routers. May be in the the TP-Link directory of FTP is wrong image? I don't know...
OK, I'm wrong. I saw the Buffalo images - all about 17-18 MB. The TP-Link image less than 8 MB. I don't know why Brainslayer wrote about flashing wrong image to TP-Link...
This is what I did:
1. download backup off all settings.
2. downloaded factory-to-ddwrt image
3. flashed image with erasing all previous settings
4. reloaded settings from backup
Now I wait...
Works great for over 4 days, no wifi issues!
Before I would get wifi issues after 12-24 hours...
UPDATE:
It failed this evening on 6th day after first 5 days working ok...
I connect to router via ssh as root user and when I tryp "dmesg" I see these log messages:
<3>[542878.060000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
<3>[542878.080000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Last edited by valent on Tue Apr 02, 2013 20:14; edited 1 time in total
Joined: 23 Jan 2012 Posts: 24 Location: Osijek, Croatia
Posted: Tue Apr 02, 2013 20:10 Post subject:
Shocker580 wrote:
They have some error in logs.. we don't ..
I get this errors via ssh terminal after I type "dmesg":
<3>[542878.060000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
<3>[542878.080000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Joined: 23 Jan 2012 Posts: 24 Location: Osijek, Croatia
Posted: Tue Apr 02, 2013 20:42 Post subject:
Just saw same issue in dmesg log as in openwrt bug, this is from my wr1043nd running ddwrt:
<3>[542878.060000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
<3>[542878.080000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Joined: 23 Jan 2012 Posts: 24 Location: Osijek, Croatia
Posted: Wed Apr 03, 2013 7:15 Post subject:
Has anybody tried this "german firmware" workaround? [1]
Here is what this guy has done:
"What worked for me is get it back to TP-Link Factory, flash the German FW, then flash BrainSlayers v24-sp2 (12/31/12) build 20453. There is both a factory to DD-WRT and a ‘final’ DD-WRT version. Go here: http://www.dd-wrt.com/site/support/other-downloads
and find them here: Downloads › others › eko › BrainSlayer-V24-preSP2 › 2013 › 01-01-2013-r20453 › tplink_tl-wr1043nd"
Has anybody tried this "german firmware" workaround? [1]
Here is what this guy has done:
"What worked for me is get it back to TP-Link Factory, flash the German FW, then flash BrainSlayers v24-sp2 (12/31/12) build 20453. There is both a factory to DD-WRT and a ‘final’ DD-WRT version. Go here: http://www.dd-wrt.com/site/support/other-downloads
and find them here: Downloads › others › eko › BrainSlayer-V24-preSP2 › 2013 › 01-01-2013-r20453 › tplink_tl-wr1043nd"
Take the last version for your 1043. It seems like usage wrong version of FW. The address after burning should be 192.168.1.1 Images with this error (bad address) was fixed I think.
Posted: Wed Aug 21, 2013 16:17 Post subject: Still Getting This With Latest Version
I'm still getting this with (I believe) the latest version.
For a bit of background, I'm replacing a BT Infinity Homehub (brand new) because I do quite a lot of poking around on Linux, so I often grab ISOs down via legal torrents using Transmission. I noticed that unless I reduced the number of total peers to 250, and restricted my torrent download speed to about 1Mbs (which isn't ideal, esp not with Infinity), the HH would often hang up with these symptoms - the WLAN SSID would be visible, but you couldn't connect to it until you power-cycled the HH.
I got the 1043, brand new, last night, 30-30-30ed it and put DD-WRT v24-sp2 (07/24/13) std - build 22118 on it - this is the latest build, isn't it, and isn't a testing build? While it has been more stable than the HH, I found that when I opened up the torrent limits to 1000 then down to 500 peers, it was still hanging, though not so readily as the HH. Going back to 250 peers I found I could leave the torrent client bandwidth unlimited and it mostly was ok, though it has still failed a couple of times, once on fairly low download speed/number of peers (my test torrents were almost done).
I've tried the above fix with the antenna settings (TX-1+3, RX-1+2) and I'll see how I get one and report back. For anyone trying to test this, finding a few (5-10) well seeded legal torrents (open source software ISOs are ideal) is a good way of hammering it.
Cheers - MH
