Hi Hanno,
Le 16/01/2014 04:18, Hanno Schupp a écrit :
Thank you John and Michel for taking the time to explain. Much appreciated.
Based on your comments and some research I found a resolution to the issue that
in the end is quite simple.
Glad you found a solution to your problem!
Whether
Found the bug I was searching for. Depending on the time dnsmasq needs
to stop, procd might already start a new process while the old process is
still exiting.
Can be reproduced if a sleep 1 is added in the exiting function of dnsmasq
and /etc/init.d/dnsmasq restart is executed.
Not sure whats
we are used to apply 'oops=panic panic=10' to our kernel-cmdline,
but doing this with mpc85xx seems not to work:
user@build:~/openwrt$ grep 'CONFIG_CMDLINE='
target/linux/mpc85xx/config-3.10
CONFIG_CMDLINE=console=ttyS0,115200 oops=panic panic=10
root@box$ cat /proc/cmdline
Hi Bastian,
what cmdline is shown in the bootlog ?
John
On 16/01/2014 11:48, Bastian Bittorf wrote:
we are used to apply 'oops=panic panic=10' to our kernel-cmdline,
but doing this with mpc85xx seems not to work:
user@build:~/openwrt$ grep 'CONFIG_CMDLINE='
* Alexander Couzens lyn...@fe80.eu [16.01.2014 11:48]:
This enables wget argument -T TIMEOUT.
Otherwise a wget will timeout after ~2 minutes.
but to make it clear, the timeout does not work always.
the busybox-people are aware of this, but there is no
fix yet. this means: if you script
Hi,
support for ath10k cards was added a while ago to OpenWrt. Unfortunately, the
actual 802.11ac support was never added (patches on the mailing lists were
just ignored). This is a rather unpleasant situation when trying to get some
11ac test hardware working.
I've picked up the patches and
From: Matti Laakso malaa...@elisanet.fi
This patch introduces 802.11ac support to base-files, mac80211 and hostapd. The
split of VHT160 in two 80 MHz bands is not yet supported, since it requires an
additional user supplied parameter for the channel of the second band.
Signed-off-by: Matti
* John Crispin j...@phrozen.org [16.01.2014 12:16]:
what cmdline is shown in the bootlog ?
the same like in '/proc/cmdline':
[0.00] Kernel command line: console=ttyS0,115200
bye, bastian
___
openwrt-devel mailing list
Hi!
I'm trying to run OpenWRT on a Buffalo WZR-D1800H ( see Wiki
http://wiki.openwrt.org/toh/buffalo/wzr-d1800h)
Currently I'm able to run the initramfs image via tftp boot. The following
drivers work:
-wl (1bgn, 11an, no 11ac which I do not care)
-bgmac
-usb
So most important parts work :-)
Thanks! Now I don't need to spend my weekend on this like I was about to!
I see one issue:
+
+ vht_cap=0
+ for cap in $(iw phy $dev info | awk -F [()] '/VHT
Capabilities/ { print $2 }'); do
+ vht_cap=$(($vht_cap | $cap))
+
From: Matti Laakso malaa...@elisanet.fi
This patch introduces 802.11ac support to base-files, mac80211 and hostapd. The
split of VHT160 in two 80 MHz bands is not yet supported, since it requires an
additional user supplied parameter for the channel of the second band.
Signed-off-by: Matti
Hi,
On Tue, Jan 14, 2014 at 03:46:00PM +0100, Michel Stempin wrote:
Well, one can relatively easily debrick by flashing directly to the
serial chip with some external device such as ftdi board or raspberrypi.
Yes, provided you did a backup of the partitions first thing:)
That's the first
Le 16/01/2014 15:32, Paul Fertser a écrit :
Hi,
On Tue, Jan 14, 2014 at 03:46:00PM +0100, Michel Stempin wrote:
Well, one can relatively easily debrick by flashing directly to the
serial chip with some external device such as ftdi board or raspberrypi.
Yes, provided you did a backup of the
On Thu, 16 Jan 2014 12:18:28 +0100
Bastian Bittorf bitt...@bluebottle.com wrote:
[0.00] Kernel command line: console=ttyS0,115200
It's defined within the device tree.
best,
lynxis
--
Alexander Couzens
mail: lyn...@fe80.eu
sip/jabber: lyn...@c-base.org
mobile: +4915123277221
On 16/01/2014, at 9:43 pm, Michel Stempin michel.stem...@wanadoo.fr wrote:
Hi Hanno,
Le 16/01/2014 04:18, Hanno Schupp a écrit :
Thank you John and Michel for taking the time to explain. Much appreciated.
Based on your comments and some research I found a resolution to the issue
Le 16/01/2014 22:22, Hanno Schupp a écrit :
On 16/01/2014, at 9:43 pm, Michel Stempin michel.stem...@wanadoo.fr wrote:
Hi Hanno,
Le 16/01/2014 04:18, Hanno Schupp a écrit :
Thank you John and Michel for taking the time to explain. Much appreciated.
Based on your comments and some
2014/1/16 Sven Eckelmann s...@open-mesh.com:
From: Simon Wunderlich si...@open-mesh.com
The current version of the driver includes a lot of bug fixes necessary to get
802.11ac connections working at all. These patches also need a never firmware
to work correctly.
Signed-off-by: Simon
We don't need to kill any processes in failsafe, because we are already at
a low memory footprint. This patch fix also sysupgrade in failsafe. sysupgrade
in failsafe was broken because it kills all processes. It also kills the lock
which keeps the device in rescue modus and prevent procd from
On 16/01/2014 22:22, Hanno Schupp wrote:
I hear what you say, but OpenWrt is already supplying bootloaders as part of
the buildroot process for other platforms, most notably ar71xx. So why not
for ramips? From the outside it seems there seems to be no better reason than
individual dev's
hi lynxis,
i just added a slightly tweaked version of the patch to my merge tree
John
On 17/01/2014 03:49, Alexander Couzens wrote:
We don't need to kill any processes in failsafe, because we are already at
a low memory footprint. This patch fix also sysupgrade in failsafe. sysupgrade
in
20 matches
Mail list logo
