D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: DRobbieD on August 23, 2011, 03:23:01 PM
-
Hi there,
I have a new D-link DIR-655 revision B1 with firmware v2.00. Since the v2.00 firmware seems not very stable I upgraded to the latest firmware I could find on http://www.dlinktw.com.tw/support. So I installed the v.2.02WW_B08. Because the webinterface is not always very responsive I started a syslog. I noticed a lot of the following user warnings. Is this normal? Since the warnings seems to come from the kernel they worry me.
2011-08-24 00:16:49 User.Warning 192.168.2.1 Aug 24 00:16:14 kernel: [ 5779.810000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
2011-08-24 00:16:53 User.Warning 192.168.2.1 Aug 24 00:16:18 kernel: [ 5783.660000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
2011-08-24 00:16:54 User.Warning 192.168.2.1 Aug 24 00:16:19 kernel: [ 5785.160000] Inteference detected
2011-08-24 00:16:55 User.Warning 192.168.2.1 Aug 24 00:16:19 kernel: [ 5785.160000] rx_clear=99, rx_frame=0, tx_frame=0
2011-08-24 00:17:15 User.Warning 192.168.2.1 Aug 24 00:16:39 kernel: [ 5805.490000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
2011-08-24 00:17:19 User.Warning 192.168.2.1 Aug 24 00:16:44 kernel: [ 5809.570000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
2011-08-24 00:17:27 User.Warning 192.168.2.1 Aug 24 00:16:52 kernel: [ 5817.830000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
2011-08-24 00:17:40 User.Warning 192.168.2.1 Aug 24 00:17:05 kernel: [ 5831.000000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
-
After logging for one day I notice also a lot of other strange warning/errors. Does anybody know if it are serious warnings/errors? Am I the only one having these kind of message? Some messages I have seen in other topics that cause some problems.
Local0.Debug 192.168.2.1 Jul 11 17:49:52 udhcpc[122]: open bandwidth_tmp.txt fail
User.Debug 192.168.2.1 Jul 11 17:46:53 kernel: [ 4325.990000] UDP: bad checksum.
Daemon.Error 192.168.2.1 Jul 11 17:43:23 miniupnpd[337]: [truncated] m
User.Warning 192.168.2.1 Jul 11 16:52:13 kernel: [ 1046.070000] ->bad
User.Warning 192.168.2.1 Jul 11 16:39:27 kernel: [ 280.310000] Inteference detected
User.Warning 192.168.2.1 Jul 11 16:39:27 kernel: [ 280.310000] rx_clear=99, rx_frame=0, tx_frame=0
Daemon.Error 192.168.2.1 Jul 11 16:36:59 miniupnpd[337]: chain MINIUPNPD not found
Daemon.Error 192.168.2.1 Jul 11 16:36:33 miniupnpd[337]: wsccmd is ready (after init upnp stack) ...
Daemon.Error 192.168.2.1 Jul 11 16:35:24 miniupnpd[337]: could not open lease file: /tmp/upnp_portmapping_rules
Local0.Error 192.168.2.1 Jul 11 16:35:02 udhcpd[147]: max_leases value (254) not sane, setting to 98 instead
Local0.Error 192.168.2.1 Jul 11 16:35:02 udhcpd[147]: Cannot background in uclinux (yet)
-
What browser are you using? Do other browsers exhibit the same thing? Try Opera or FF? I use Opera mainly. Good experiences.
-
What browser are you using? Do other browsers exhibit the same thing? Try Opera or FF? I use Opera mainly. Good experiences.
Yea, that looks like a firmware issue. B1=Asian market addition(compared to B), and you installed 2.03NA, which is for North American hardware. I would contact D-link to be sure.
-
Could you explain the difference between B1 vs B?
I read on other topics that the B(1) revsion was a year already in Asia available. Should these not have been brought to the European market? Or was that not suppose to? The box certainly looks for the european market, text on the box is english/french/dutch/german/spanish/polish etc. There is even a statement about the Wifi Mhz spectrum range for area 1 and 2 with a map of Europe.
The firmware installed is the v.2.02WW_B08 from the taiwan site. Is WW the NA version then?
I primarily use Firefox latest version for browsing, sometime I do use IE because some sites work better like office outlook mail web access. And on my mobile (HTC Desire) I use the default Webkit.
-
Well I just googled it and now I am not sure either. Hmmm. Either way, your having a firmware issue, and you loaded NA (North American) firmware onto hardware that at the very least isn't NA. I think that is your issue. Maybe try the Europe board? (http://forums.dlink.com/index.php?board=175.0)