Hello-
Thought I should report this, since there was so much discussion and
confusion on tracker https://dev.openwrt.org/ticket/11862 causing a
lot of work for some folks here.
root@HACKEDBOXII.'':~# cat /etc/banner
___ __
| |.-.-.---
I'm sorry, i said ath9k in the subject but the above seems more likely
to be ath10k.
On Thu, Jul 9, 2015 at 7:03 PM, camden lindsay
wrote:
> Hello-
>
> Thought I should report this, since there was so much discussion and
> confusion on tracker https://dev.openwrt.org/ticket
Thank you for noting this, Roman.
c
On Fri, Jul 10, 2015 at 10:55 PM, Roman Yeryomin wrote:
> On 10 July 2015 at 05:07, camden lindsay
> wrote:
>> I'm sorry, i said ath9k in the subject but the above seems more likely
>> to be ath10k.
>>
>> On Thu, Jul
Seems back up now...
On Sat, Feb 13, 2016 at 12:46 AM, Jakub Jančo wrote:
> Accessible:
> $ host wiki.openwrt.org
> wiki.openwrt.org has address 188.40.166.25
>
> Not accessible:
> $ host openwrt.org
> openwrt.org has address 78.24.191.177
> openwrt.org mail is handled by 10 mail.openwrt.org.
>
>
I use an intel 7260 with few or no problems.
I'm wondering if this line has something to do with your crashing problems
'[ 23.187368] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-7260-17.ucode failed with error -2'
I'll try to remember to look tonight at my dmesg to see what it looks l
259] iwlwifi :02:00.0: L1 Enabled - LTR Disabled
On Mon, Nov 30, 2015 at 4:05 PM, camden lindsay
wrote:
> I use an intel 7260 with few or no problems.
> I'm wondering if this line has something to do with your crashing problems
> '[ 23.187368] iwlwifi :04:00.0: Dire
Adrian-
I have a C7V2 and can do some testing on it if you'd explain exactly what
you're looking for... I don't quite follow what is needed in the above
thread. Something about looking at PCI paths before and after an upgrade
from one version to another...
Camden
On Mon, Apr 22, 2019 at 4:45 AM
Hmmm; well, i've got this; Fresh 'firstboot' on an archer c7 V2, following
version info:
root@LEDE:~# cat /etc/openwrt_*
DISTRIB_ID='LEDE'
DISTRIB_RELEASE='SNAPSHOT'
DISTRIB_REVISION='r3189-12db207'
DISTRIB_CODENAME='reboot'
DISTRIB_TARGET='ar71xx/generic'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTI
I believe you have to use logread-
https://wiki.openwrt.org/doc/howto/log.essentials
On Wed, Dec 28, 2016 at 10:53 PM, Tymon wrote:
> Hi all,
>
>Why can't I find the /var/log/dmesg file under openwrt (the busybox
> built-in tool 'dmesg' is work fine) ???
>
>Any hint will be appr
I was seeing >400 on the old wndr3700v2 with r29614
http://www.c-j-l.net/Home/computers/netgear_vs_buffalo_router
On Fri, Aug 29, 2014 at 1:25 PM, Weedy wrote:
> On 29 Aug 2014 15:26, "Daniel Petre" wrote:
> >
> > Hello,
> > is there any OpenWrt compatible gigabit router that can do more than
Another thought-
Are you reading the version number from the chip themselves (hardware)?
How does the current openwrt bootlog identify them? Same way?
On Tue, Oct 7, 2014 at 5:51 PM, Aaron Z wrote:
> On Tue, Oct 7, 2014 at 7:06 PM, Robert P. J. Day
> wrote:
> > finally, given that this board
ASCII (If i'm not wrong the only character in it not ASCII is the
'MAINTAINER:=' field)
This will break build for anyone enabling oldpackages in their
feeds.conf(.default)
thanks
Camden
On Thu, Dec 11, 2014 at 12:49 PM, Robert P. J. Day
wrote:
> On Thu, 11 Dec 2014, camden linds
+1
On Tue, Apr 7, 2015 at 12:47 PM, Hartmut Knaack wrote:
> That Doodle poll turned out to be spamed/trolled, and everyone could even
> change or delete other votes. Since this was just communicated over this
> mailing list, and subscribers are at least basically verified, why not
> have a
> goo
What device is this?
What version of OpenWRT are you running?
There is a bug open here: https://dev.openwrt.org/ticket/7502
On Sun, Jun 23, 2013 at 1:08 PM, Tomislav Požega
wrote:
> cannot access router even in failsafe mode, most likely due to roboswitch
> errors
>
> someone else reported exa
I am by no means an expert, but i recently did up/downgrades from 12.09 to
trunk and back (after finding 12.09 would oom during boot) using the
suggestions here:
http://wiki.openwrt.org/doc/howto/generic.sysupgrade#free.up.ram
In addition to that, i spent quite some time figureing out what all
pr
Hello-
Has something changed with options during build required to have the
firewall scripts in the base image?
I built an image from trunk this morning to upgrade my router.
I am not doing anything special in make menuconfig other than setting
target system and profile.
But once i do an mtd wri
I found this must have been an error on my part.
I cleared everythign out and re-synced.
Somehow OpenWrt C Firewall had been cleared in my .config.
Sorry for the disturbance.
Camden
On Sun, Nov 17, 2013 at 11:24 AM, camden lindsay <
camden.lindsay+open...@gmail.com> wrote:
> Hel
Hello, John
I'm no expert, but think there should be some additional information, if
you could include it.
--Are you upgrading using luci, or using sysupgrade?
If using luci, could you show the output of:
uci show luci.flash_keep
If using sysupgrade, could you show output of:
cat /etc/sysupgrad
rmally skimming over the svn output is enough to keep
> on top of things.
>
> Your "seed config" should be top level changes only. Do not add deps, just
> the packages you want in the final image. jow/mbm/nbd have done a very good
> job of making the build system resolve deps.
&
I'm no expert, but you could try running hostapd in debug mode and 'Capture
Management Traffic' to see what you can find:
See http://wiki.openwrt.org/doc/devel/debugging
On Tue, Jan 28, 2014 at 4:59 AM, omggo wrote:
> Hi all,
>
> I've come up against an issue with my "MyNet n600" on both the
It sounds like you have to re-configure the switch, to have the port
that is currently 'wan' on the same vlan as the LAN.
see http://wiki.openwrt.org/doc/uci/network/switch
On Mon, Feb 17, 2014 at 2:04 PM, jonsm...@gmail.com wrote:
> On Mon, Feb 17, 2014 at 4:48 PM, Hartmut Knaack wrote:
>> jon
Look forward to not having to fight the spam-captcha issue as much anymore heh.
Thank you for your efforts, Jow.
On Tue, Mar 4, 2014 at 3:26 AM, Jo-Philipp Wich wrote:
> Hi.
>
>> It is really annoying that dev.openwrt.org frequently gives "504 Gateway
>> Time-out" or "502 Bad Gateway" errors. Du
22 matches
Mail list logo