Re: [OpenWrt-Devel] dhcpv6.script being triggered a lot
On 02.10.2013 07:35, Nathan Hintz wrote: Hi Steven: netifd eventually crashed: Tue Oct 1 21:57:58 2013 daemon.notice netifd: wan6 (1382): Segmentation fault Could this be due to continuing to call system_add_address(dev, a_new); without ever calling system_del_address(dev, a_old);? Hmm strange, I tested this fix and fired multiple rounds of RAs at it but couldn't reproduce this segfault. Also calling system_add_address just sends a netlink control-message to the kernel and does not allocate anything which must be deallocated later (same goes for _handle_subnet_route) so this shouldn't be causing this. -Steven ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] dhcpv6.script being triggered a lot
On Wed, 02 Oct 2013 08:21:33 +0200 Steven Barth cy...@openwrt.org wrote: On 02.10.2013 07:35, Nathan Hintz wrote: Hi Steven: netifd eventually crashed: Tue Oct 1 21:57:58 2013 daemon.notice netifd: wan6 (1382): Segmentation fault Could this be due to continuing to call system_add_address(dev, a_new); without ever calling system_del_address(dev, a_old);? Hmm strange, I tested this fix and fired multiple rounds of RAs at it but couldn't reproduce this segfault. Also calling system_add_address just sends a netlink control-message to the kernel and does not allocate anything which must be deallocated later (same goes for _handle_subnet_route) so this shouldn't be causing this. -Steven I searched for a core file, but didn't find one. Any suggestions for how I can help debug this if it happens again? It may be completely unrelated to your changes; although I haven't seen any crashes in 'netifd' in quite some time. I've reverted to the previous 'netifd' for now, but I will try it again tomorrow evening when I get home from work to see if it crashes again. -- Nathan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [Patch] kernel: add vmxnet3 module
support VMware ethernet adapters Signed-off-by: Dirk Neukirchen dirkneukirc...@web.de --- package/kernel/linux/modules/netdevices.mk | 16 1 file changed, 16 insertions(+) diff --git a/package/kernel/linux/modules/netdevices.mk b/package/kernel/linux/modules/netdevices.mk index 9c808e1..1db45f8 100644 --- a/package/kernel/linux/modules/netdevices.mk +++ b/package/kernel/linux/modules/netdevices.mk @@ -742,3 +742,19 @@ define KernelPackage/gianfar/description endef $(eval $(call KernelPackage,gianfar)) + + +define KernelPackage/vmxnet3 + SUBMENU:=$(NETWORK_DEVICES_MENU) + TITLE:=VMware VMXNET3 ethernet driver + DEPENDS:=@PCI_SUPPORT + KCONFIG:=CONFIG_VMXNET3=y + FILES:=$(LINUX_DIR)/drivers/net/vmxnet3/vmxnet3.ko + AUTOLOAD:=$(call AutoLoad,35,vmxnet3) +endef + +define KernelPackage/vmxnet3/description + Kernel modules for VMware VMXNET3 ethernet adapters. +endef + +$(eval $(call KernelPackage,vmxnet3)) -- 1.8.1.2 smime.p7s Description: S/MIME Cryptographic Signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] AsiaRF build, no images output
On Wed, Oct 2, 2013 at 8:24 AM, jonsm...@gmail.com jonsm...@gmail.com wrote: There are several things broken on the AsiaRF build. 1) The build system has broken for things with hyphens in the name 2) The rt5350 ethernet switch will not function unless VLAN tagging is turned on. I looked at the switch problem for quite a while and can't figure out what is going on. Thread on the issue... http://thread.gmane.org/gmane.comp.embedded.openwrt.devel/20384 This patch will get it going again. -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] package/index: fix index creating when building without signing
Signed-off-by: Alexander Couzens lyn...@fe80.eu --- package/Makefile | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/package/Makefile b/package/Makefile index bac7001..f82654c 100644 --- a/package/Makefile +++ b/package/Makefile @@ -130,16 +130,16 @@ ifndef CONFIG_OPKGSMIME_PASSPHRASE endif $(curdir)/index: FORCE + @echo Generating package index... + @(cd $(PACKAGE_DIR); \ + $(SCRIPT_DIR)/ipkg-make-index.sh . 21 Packages \ + gzip -9c Packages Packages.gz ) ifeq ($(call qstrip,$(CONFIG_OPKGSMIME_KEY)),) @echo Signing key has not been configured else ifeq ($(call qstrip,$(CONFIG_OPKGSMIME_CERT)),) @echo Certificate has not been configured else - @echo Generating package index... - @(cd $(PACKAGE_DIR); \ - $(SCRIPT_DIR)/ipkg-make-index.sh . 21 Packages \ - gzip -9c Packages Packages.gz ) @echo Signing package index... @(cd $(PACKAGE_DIR); \ openssl smime -binary -in Packages.gz \ -- 1.8.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] package/index: fix index creating when building without signing
Sorry about the fuzz and thanks for the patch. Applied in r38287. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] AsiaRF build, no images output
Progress, thanks! I now have the sysupgrade image, but no factory image. I noticed that factory images aren't generated for a few of the other ramips boards as well. On Wed, Oct 2, 2013 at 5:24 AM, jonsm...@gmail.com jonsm...@gmail.comwrote: There are several things broken on the AsiaRF build. 1) The build system has broken for things with hyphens in the name 2) The rt5350 ethernet switch will not function unless VLAN tagging is turned on. This patch will get it going again. On Wed, Oct 2, 2013 at 12:59 AM, Michel Stempin michel.stem...@wanadoo.fr wrote: I had a similar issue with another board: it looks like the OpenWrt build system doesn't like board names containing a dash sign (-), try renaming it. Le 2 oct. 2013 à 03:30, Shawn Lewis shle...@gmail.com a écrit : I'm not getting factory/sysupgrade images for the ramips asiarf target. If I build the default target profile I get all the other ramips images. If I manually select Asiarf AWM002-EVB I get vmlinux and other precursors to the actual image, but no flashable factory/sysupgrade images. Tried from trunk as of yesterday evening PST: svn://svn.openwrt.org/openwrt/trunk@38267 and svn://svn.openwrt.org/openwrt/trunk@37561 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] AsiaRF build, no images output
On Wed, Oct 2, 2013 at 3:05 PM, Shawn Lewis shle...@gmail.com wrote: Progress, thanks! I now have the sysupgrade image, but no factory image. I noticed that factory images aren't generated for a few of the other ramips boards as well. Just start the board with the UART connected and pick update the system image (choice 2 I think). There is only only image. Make sure you have Luci enabled in the build. If you get tired of entering your IP address. Pick 4. printenv setenv ipaddr x saveenv reset Messing with choices 8 and 9 on the menu will give you heart burn. You can do it but be prepared with a JTAG. On Wed, Oct 2, 2013 at 5:24 AM, jonsm...@gmail.com jonsm...@gmail.com wrote: There are several things broken on the AsiaRF build. 1) The build system has broken for things with hyphens in the name 2) The rt5350 ethernet switch will not function unless VLAN tagging is turned on. This patch will get it going again. On Wed, Oct 2, 2013 at 12:59 AM, Michel Stempin michel.stem...@wanadoo.fr wrote: I had a similar issue with another board: it looks like the OpenWrt build system doesn't like board names containing a dash sign (-), try renaming it. Le 2 oct. 2013 à 03:30, Shawn Lewis shle...@gmail.com a écrit : I'm not getting factory/sysupgrade images for the ramips asiarf target. If I build the default target profile I get all the other ramips images. If I manually select Asiarf AWM002-EVB I get vmlinux and other precursors to the actual image, but no flashable factory/sysupgrade images. Tried from trunk as of yesterday evening PST: svn://svn.openwrt.org/openwrt/trunk@38267 and svn://svn.openwrt.org/openwrt/trunk@37561 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] AsiaRF build, no images output
I should be using the sysupgrade image then? On Wed, Oct 2, 2013 at 12:09 PM, jonsm...@gmail.com jonsm...@gmail.comwrote: On Wed, Oct 2, 2013 at 3:05 PM, Shawn Lewis shle...@gmail.com wrote: Progress, thanks! I now have the sysupgrade image, but no factory image. I noticed that factory images aren't generated for a few of the other ramips boards as well. Just start the board with the UART connected and pick update the system image (choice 2 I think). There is only only image. Make sure you have Luci enabled in the build. If you get tired of entering your IP address. Pick 4. printenv setenv ipaddr x saveenv reset Messing with choices 8 and 9 on the menu will give you heart burn. You can do it but be prepared with a JTAG. On Wed, Oct 2, 2013 at 5:24 AM, jonsm...@gmail.com jonsm...@gmail.com wrote: There are several things broken on the AsiaRF build. 1) The build system has broken for things with hyphens in the name 2) The rt5350 ethernet switch will not function unless VLAN tagging is turned on. This patch will get it going again. On Wed, Oct 2, 2013 at 12:59 AM, Michel Stempin michel.stem...@wanadoo.fr wrote: I had a similar issue with another board: it looks like the OpenWrt build system doesn't like board names containing a dash sign (-), try renaming it. Le 2 oct. 2013 à 03:30, Shawn Lewis shle...@gmail.com a écrit : I'm not getting factory/sysupgrade images for the ramips asiarf target. If I build the default target profile I get all the other ramips images. If I manually select Asiarf AWM002-EVB I get vmlinux and other precursors to the actual image, but no flashable factory/sysupgrade images. Tried from trunk as of yesterday evening PST: svn://svn.openwrt.org/openwrt/trunk@38267 and svn://svn.openwrt.org/openwrt/trunk@37561 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] AsiaRF build, no images output
On Wed, Oct 2, 2013 at 4:38 PM, Shawn Lewis shle...@gmail.com wrote: I should be using the sysupgrade image then? /openwrt/bin/ramips/openwrt-ramips-rt305x-awm002-evb-8M-squashfs-sysupgrade.bin On Wed, Oct 2, 2013 at 12:09 PM, jonsm...@gmail.com jonsm...@gmail.com wrote: On Wed, Oct 2, 2013 at 3:05 PM, Shawn Lewis shle...@gmail.com wrote: Progress, thanks! I now have the sysupgrade image, but no factory image. I noticed that factory images aren't generated for a few of the other ramips boards as well. Just start the board with the UART connected and pick update the system image (choice 2 I think). There is only only image. Make sure you have Luci enabled in the build. If you get tired of entering your IP address. Pick 4. printenv setenv ipaddr x saveenv reset Messing with choices 8 and 9 on the menu will give you heart burn. You can do it but be prepared with a JTAG. On Wed, Oct 2, 2013 at 5:24 AM, jonsm...@gmail.com jonsm...@gmail.com wrote: There are several things broken on the AsiaRF build. 1) The build system has broken for things with hyphens in the name 2) The rt5350 ethernet switch will not function unless VLAN tagging is turned on. This patch will get it going again. On Wed, Oct 2, 2013 at 12:59 AM, Michel Stempin michel.stem...@wanadoo.fr wrote: I had a similar issue with another board: it looks like the OpenWrt build system doesn't like board names containing a dash sign (-), try renaming it. Le 2 oct. 2013 à 03:30, Shawn Lewis shle...@gmail.com a écrit : I'm not getting factory/sysupgrade images for the ramips asiarf target. If I build the default target profile I get all the other ramips images. If I manually select Asiarf AWM002-EVB I get vmlinux and other precursors to the actual image, but no flashable factory/sysupgrade images. Tried from trunk as of yesterday evening PST: svn://svn.openwrt.org/openwrt/trunk@38267 and svn://svn.openwrt.org/openwrt/trunk@37561 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ar71xx: fix WLAN 5 GHz LED init on dir-825-c1
Fixes the 5 GHz LED. The same function has no effect on the 2.4 GHz LED at all, so we might as well remove it. Signed-off-by: Sebastian Kemper sebastian...@gmx.net --- Now all LEDs are finally working in OpenWrt. diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-dir-825-c1.c b/target/linux/ar71xx/files/arch/mips/ath79/mach-dir-825-c1.c index af9805a..9c4c1a8 100644 --- a/target/linux/ar71xx/files/arch/mips/ath79/mach-dir-825-c1.c +++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-dir-825-c1.c @@ -217,8 +217,7 @@ static void __init dir825c1_setup(void) ath79_register_leds_gpio(-1, ARRAY_SIZE(dir825c1_leds_gpio), dir825c1_leds_gpio); - ap9x_pci_setup_wmac_led_pin(0, 13); - ap9x_pci_setup_wmac_led_pin(1, 32); + ap9x_pci_setup_wmac_led_pin(0, 0); dir825c1_generic_setup(); } ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] broadcom-diag: fix 'autoload' number of diag.ko
On 09/22/2013 06:39 PM, Nathan Hintz wrote: Change the autoload number from '5' to '05' so the module loads earlier (as intended). Signed-off-by: Nathan Hintz nlhi...@hotmail.com --- package/kernel/broadcom-diag/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/kernel/broadcom-diag/Makefile b/package/kernel/broadcom-diag/Makefile index 617aac1..d27b395 100644 --- a/package/kernel/broadcom-diag/Makefile +++ b/package/kernel/broadcom-diag/Makefile @@ -18,7 +18,7 @@ define KernelPackage/diag DEPENDS:=@TARGET_brcm47xx TITLE:=Driver for router LEDs and Buttons FILES:=$(PKG_BUILD_DIR)/diag.ko - AUTOLOAD:=$(call AutoLoad,5,diag,1) + AUTOLOAD:=$(call AutoLoad,05,diag,1) endef define KernelPackage/diag/description Thank you for the patch, it was applied in r38293. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] brcm47xx: add support for ipv6 in default network config
On 09/22/2013 09:04 AM, Nathan Hintz wrote: Modify /etc/init.d/netconfig to use UCI defaults for building the default network config, which includes appropriate defaults for IPV6. Signed-off-by: Nathan Hintz nlhi...@hotmail.com Hi, Thank you for the patch, I applied this patch in r38294 with some little modifications, I renamed eth0 to switch0 and removed old switch support. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
