Hi All,
small update, I have a hunch that comment 3 of
https://dev.openwrt.org/ticket/13958
might be relevant for us:
additional 2cents: turns out i had mount-utils installed, whose
/usr/bin/mount had different output than the busybox one. this broke the
function rootfs_type() in
Also, while I haven't tested this. After reboots I got an IP a good bit
faster than previous builds (IE without the long timeout in fixdaemons),
it's possible that the dnsmasq (at least) startup issue is fixed in
3.10.18...
--
David P.
On Thu, Nov 14, 2013 at 8:56 PM, Richard E. Brown
Hi Sebastian,
Thanks for looking at this. So it seems that keeping the configuration when
using sysupgrade caused the problem.
I now begin to understand why Dave recommends against using the keep
configuration setting for sys upgrade :) there is just too much in flux for
it to work for all
Hi Richard,
On Nov 12, 2013, at 06:47 , Richard E. Brown richb.hano...@gmail.com wrote:
I used the sysupgrade process to upgrade my primary router from 3.7.5-2
firmware to 3.10.18-1.
- I initially goofed, and installed the wrong build firmware (I installed the
WNDR3800 image on a
After your helpful writeup as an ADSL user, I am expanding on the
previous remarks I made. SM is making his contribution as I write.
For several years, I have been with Telefonica O2 as an ISP. This
network gave subscribers a dynamic ipv4 address which did not change
unless the gateway WAN
On Nov 12, 2013, at 4:11 AM, Sebastian Moeller moell...@gmx.de wrote:
- Had to enable and set AQM parameters, since they’re saved differently
from the QoS settings in the 3.7.5-2 firmware. Set parameters to ~ 90% of
link speeds
Just curious, did you specify overhead and
Hi All,
it turns out that not being able/willing to read can make you do busy work. It
seems I forgot to add firmware as device to my mtd invocation… I guess I
would never have tried the GUI if I had gotten the mtd command right the first
time :)
best
Sebastian
On Nov 13, 2013, at
On Nov 12, 2013, at 4:11 AM, Sebastian Moeller moell...@gmx.de wrote:
- The kernel.log shows lots of the stack traces below: 2-5 per second on a
long-term basis.
These look quite weird, the error is a slow patch warning from
hfsc_schedule_watchdog . But, hfsc is the queuing
I used the sysupgrade process to upgrade my primary router from 3.7.5-2
firmware to 3.10.18-1.
- I initially goofed, and installed the wrong build firmware (I installed the
WNDR3800 image on a WNDR3700v2 router.) The symptoms were that the router
worked, but not very well. Speedtest was gave
