Dear list,
for some time now we had the issue that the sysupgrade command did not work.
So here is the output of my first attempt to sysupgrade 3.10.18-1 to 3.10.21-1:
root@nacktmulle:~# sysupgrade -d 60 -n -v
/home/persistent/cerowrts/3.10.21-1/3.10.21-1-sysupgrade.bin
killall: watchdog: no
I have the regrettable problem of mostly testing the 5ghz channel due
to interference issues on the 2ghz band.
What I am seeing in the last several releases of the 3.8.x and 3.10
series is after tons of traffic and multiple days of uptime a DMA tx
error which you can see via the logread or dmesg
On Wed, Dec 11, 2013 at 11:58 AM, Stephen Hemminger
step...@networkplumber.org wrote:
Has anyone seen wireless failing after several days with 3.10.17-3?
I'm running 3.10.21-1, which I installed late last week.
I've had the router's wireless go catatonic several times, and there are
error
Hi List, hi Dave,
On Dec 11, 2013, at 19:41 , Dave Taht dave.t...@gmail.com wrote:
I have the regrettable problem of mostly testing the 5ghz channel due
to interference issues on the 2ghz band.
What I am seeing in the last several releases of the 3.8.x and 3.10
series is after tons of
Yes, those are the error messages I saw in my log.
It is wonderful you seem to be able to trigger them at will.
- Jim
On Wed, Dec 11, 2013 at 3:41 PM, Sebastian Moeller moell...@gmx.de wrote:
Hi List, hi Dave,
On Dec 11, 2013, at 19:41 , Dave Taht
Hi Dave,
so I tried to upgrade to 3.10.23-1 to test the wether the ath TX DMA error
would be gone. But alas, I can connect to the router via wifi after the upgrade
(I did the upgrade twice, once from the GUI and once from the common line). So
I am switching back to 3.10.21-1 for the time
thank you for trying. In the olde days I was usually in the same place
as the lab and could far more easily test a build. These days I seem
only to be able to do the compile and integration steps in the wee
hours days or weeks before I get time to get into the lab, and I am,
as always, grateful
I have the same problem. I cannot connect to wireless clients via g or n.
The clients do not receive DHCP ipv4 addresses.
Regression to 3.10.21-1 solves the problem, as you say.
On 11/12/13 23:18, Sebastian Moeller wrote:
Hi Dave,
so I tried to upgrade to 3.10.23-1 to test the wether the ath
