Re: [LEDE-DEV] LEDE Wiki Teambuilding

NameFunction == Martin Tippmann (m...@i3o.de ), Jan-Tarek Butt t...@ring0.de Infrastructure / I could take care of nginx, caching, let's encrypt, mysql, php, memcache whatever. Thomas Endt,

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

On Sat, Sep 24, 2016 at 12:14 AM, Dennis Schneck wrote: > Hello Martin, > sorry all is fine! Wireless works now! > Thanks a lot! great, have fun with your freed VGV7510KW22 :-) ___ Lede-dev mailing list

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

  Hello Martin, sorry all is fine! Wireless works now! Thanks a lot!   Have a nice weekend!         Gesendet: Samstag, 24. September 2016 um 00:09 Uhr Von: "Dennis Schneck" An: "Martin Blumenstingl" Cc: lede-dev@lists.infradead.org

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

Hi Martin, sorry but no wifi device there   [   10.415927] PCI: Enabling device :00:0e.0 ( -> 0002) [   10.420379] rt2800pci :00:0e.0: failed to load eeprom property [   10.426368] ieee80211 phy0: rt2x00lib_request_eeprom_file: Info - Loading EEPROM data from 'RT3062.eeprom'. [  

[LEDE-DEV] [PATCH 1/2] ramips: do not "local" variables outside of a function

Older busybox versions allowed using the local keyword outside of functions, whereas 1.25.0 (which was introduced in 06fa1c46fc32) do not allow this anymore (leading to the following error when executing the script: "file: local: line nn: not in a function"). Signed-off-by: Martin Blumenstingl

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

On Sat, Sep 24, 2016 at 12:04 AM, Dennis Schneck wrote: > Hi Martin, > > i fixed the file: /etc/hotplug.d/firmware/10-rt2x00-eeprom like you told > > root@lede:~# FIRMWARE="RT3062.eeprom" sh > /etc/hotplug.d/firmware/10-rt2x00-eeprom > 256+0 records in > 256+0 records out >

[LEDE-DEV] [PATCH 0/2] fix "local" keywords in firmware hotplug scripts

Currently the initialization of the RT3062F wifi chip fails on VGV7510KW22 because the updated busybox shell does not like the usage of the "local" keyword outside of functions. This was reported by Dennis Schneck (see [0]): > root@lede:~# FIRMWARE="RT3062.eeprom" sh >

[LEDE-DEV] [PATCH 2/2] lantiq: do not "local" variables outside of a function

Older busybox versions allowed using the local keyword outside of functions, whereas 1.25.0 (which was introduced in 06fa1c46fc32) do not allow this anymore (leading to the following error when executing the script: "file: local: line nn: not in a function"). Signed-off-by: Martin Blumenstingl

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

Hi Martin, i fixed the file: /etc/hotplug.d/firmware/10-rt2x00-eeprom like you told root@lede:~# FIRMWARE="RT3062.eeprom" sh /etc/hotplug.d/firmware/10-rt2x00-eeprom 256+0 records in 256+0 records out whats next ?   Thanks Gesendet: Freitag, 23. September 2016 um 23:33 Uhr Von: "Martin

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

On Fri, Sep 23, 2016 at 11:28 PM, Dennis Schneck wrote: >> ah, could you please try that again with: >> FIRMWARE="RT3062.eeprom" sh /etc/hotplug.d/firmware/10-rt2x00-eeprom > > root@lede:~# FIRMWARE="RT3062.eeprom" sh > /etc/hotplug.d/firmware/10-rt2x00-eeprom >

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

> ah, could you please try that again with: > FIRMWARE="RT3062.eeprom" sh /etc/hotplug.d/firmware/10-rt2x00-eeprom root@lede:~# FIRMWARE="RT3062.eeprom" sh /etc/hotplug.d/firmware/10-rt2x00-eeprom /etc/hotplug.d/firmware/10-rt2x00-eeprom: local: line 60: not in a function rt2x00 eeprom: board

Re: [LEDE-DEV] O2 Box 6431 Install LEDE without open the Device ?

On Wed, Sep 21, 2016 at 8:26 PM, Dennis Schneck wrote: > Hi, > is i right that the Image: > lede-lantiq-xrx200-VGV7510KW22BRN-squashfs-factory.bin > is the right to Flash it on a O2 6431. > > Is there another way to Flash the Firmware > without open the Device an solder

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | owsip or alternative ?

On Fri, Sep 23, 2016 at 10:24 PM, Daniel Golle wrote: > Hi again, > > On Fri, Sep 23, 2016 at 10:06:36PM +0200, Dennis Schneck wrote: >> >> >> Sorry : mean asterisk-13.x instead of asterisk-1.8.x >> Hi Daniel, >> sorry about my poor english. >> >> Do I understand right,

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

On Fri, Sep 23, 2016 at 9:57 PM, Dennis Schneck wrote: > > Hi Daniel, > please see the attached files. what do you get when you run: FIRMWARE="RT3062.eeprom" /etc/hotplug.d/firmware/10-rt2x00-eeprom Last time I used my VGV7510KW22 I was using brnboot (according to your log

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | owsip or alternative ?

  Hi Daniel,   i can send you the hardware if it helps       Gesendet: Freitag, 23. September 2016 um 22:24 Uhr Von: "Daniel Golle" An: "Dennis Schneck" Cc: lede-dev@lists.infradead.org Betreff: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | owsip or alternative ?

Hi again, On Fri, Sep 23, 2016 at 10:06:36PM +0200, Dennis Schneck wrote: > > > Sorry :  mean asterisk-13.x instead of asterisk-1.8.x > Hi Daniel, > sorry about my poor english. >   > Do I understand right, that it can be work with asterisk-1.8.x it can work with asterisk-1.8.x, because we got

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

Hi Dennis, [ 10.350649] rt2800pci :00:0e.0: Direct firmware load for RT3062.eeprom failed with error -2 you are lacking the EEPROM which is supposedly stored in some awkward place (like the stock-firmware's rootfs). it might also be an *actual* eerpom on the wifi-module, i saw that before

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

Hi Daniel, please see the attached files. Thanks Dennis     Gesendet: Freitag, 23. September 2016 um 21:49 Uhr Von: "Daniel Golle" An: "Dennis Schneck" Cc: lede-dev@lists.infradead.org Betreff: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | owsip or alternative ?

  Hi Daniel, sorry about my poor english.   Do I understand right, that it can be work with asterisk-1.8.x but need a additional package that is not yet available  ?   Thanks Dennis   Gesendet: Freitag, 23. September 2016 um 21:02 Uhr Von: "Daniel Golle" An: "Dennis

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

On Fri, Sep 23, 2016 at 08:14:03PM +0200, Dennis Schneck wrote: > > > Hello, > i use the o2 box 6431 / VGV7510KW22 with LEDE r1640. > But the wireless did not work. >   > The Kernel Module: rt2800 is loaded > but there is no wlan interface. weird. please post your kernel log and the output

[LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | owsip or alternative ?

  Hello, i use the o2 box 6431 / VGV7510KW22 with LEDE r1640. Like to use my SIP Accout with the 3x FXS Ports (Analog Phone / TAE Ports)   I read about owsip but can not find a package. Is there a simular package for lede ? Thanks     Thanks Dennis  

Re: [LEDE-DEV] persistent /var (or /data)?

On Fri, Sep 23, 2016 at 07:43:59PM +0200, Bastian Bittorf wrote: > * Daniel Golle [23.09.2016 19:19]: > > [...] > > > On Android and other embedded systems, this whole issue is solved by > > having a designated volume mounted on /data, usually backed by a > > partition on

[LEDE-DEV] [PATCH netifd 6/7] vlandev: Rework 8021ad/8021q detection based on vlandevice type

Signed-off-by: Hans Dedecker --- vlandev.c | 13 - 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/vlandev.c b/vlandev.c index b065c27..7e46251 100644 --- a/vlandev.c +++ b/vlandev.c @@ -20,14 +20,12 @@ #include "system.h" enum { -

[LEDE-DEV] [PATCH netifd 1/7] device: Move the different device type registrations to the device type file

While at it; make device_types static if only used in the device type file Signed-off-by: Hans Dedecker --- alias.c | 2 -- bridge.c | 5 + device.c | 15 +-- device.h | 2 -- macvlan.c | 7 ++- tunnel.c | 5 - vlandev.c | 7 ++- 7

[LEDE-DEV] [PATCH netifd 5/7] vlandev: Register 8021ad and 8021q s device types

Fixes creation of vlan 8021ad/8021q devices by UCI due to device handlers rework Signed-off-by: Hans Dedecker --- vlandev.c | 17 ++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/vlandev.c b/vlandev.c index becaed8..b065c27 100644 ---

[LEDE-DEV] [PATCH netifd 7/7] device: Drop device down event during device release if device gets active again

Fixes a race condition as the device can be active again; due to a device_claim; by the logic behind the set_state device type function. In this case the down event cannot be sent anymore as it would bring down the interface(s) referencing the device. This can be the case for an aliased device

[LEDE-DEV] [PATCH netifd 4/7] tunnel: Use tunnel as device type name

Fixes creation of tunnel devices by UCI due to device handlers rework Signed-off-by: Hans Dedecker --- tunnel.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tunnel.c b/tunnel.c index 32f3613..3fa3e21 100644 --- a/tunnel.c +++ b/tunnel.c @@ -90,7 +90,7

[LEDE-DEV] [PATCH netifd 3/7] macvlan: Use macvlan as device type name

Fixes creation of macvlan devices by UCI due to device handlers rework Signed-off-by: Hans Dedecker --- macvlan.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/macvlan.c b/macvlan.c index 01a48cd..021d394 100644 --- a/macvlan.c +++ b/macvlan.c @@ -254,7

[LEDE-DEV] [PATCH netifd 2/7] bridge: Make bridge_device_type static

Signed-off-by: Hans Dedecker --- bridge.c | 2 +- device.h | 1 - wireless.c | 2 +- 3 files changed, 2 insertions(+), 3 deletions(-) diff --git a/bridge.c b/bridge.c index 98e237b..8e6c9a6 100644 --- a/bridge.c +++ b/bridge.c @@ -80,7 +80,7 @@ static void

[LEDE-DEV] [PATCH] initramfs: Escape colons in depfile

Special characters are problematic in depfiles, but we can fix colons easily. Reported-by: Florian Fainelli Signed-off-by: Michal Marek --- scripts/gen_initramfs_list.sh | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

Re: [LEDE-DEV] gen_initramfs_list.sh escaping problem or stale dependency file?

On 2016-09-19 22:00, Florian Fainelli wrote: > On 09/13/2016 12:24 AM, Michal Marek wrote: >> On Mon, Sep 12, 2016 at 05:12:15PM -0700, Florian Fainelli wrote: >>> Hi, >>> >>> I have a root filesystem embedding filenames that look like these: >>> >>> /lib/data/: >>> >>> these are essentially files