[OpenWrt-Devel] Error building trunk r24289
Hello, I'm new to this list, and OpenWRT in general so please bear with me. I just got a shiny new WNDR3700 after the the circa 2003 hardware running my Smoothwall finally gave up. I'm building trunk with V=99 and it dies with an error. How do I find out more about the particular cause of this error? Is there a way to build just the sub-component that is failing? make[1]: *** [/home/wrtdev/openwrt/trunk/staging_dir/target-mips_uClibc-0.9.31/stamp/.tools_install_nnnyn] Error 2 make[1]: Leaving directory `/home/wrtdev/openwrt/trunk' make: *** [world] Error 2 What's the best way to get more detail here? I search above for errors further up and didn't see any. Thanks, -JR ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Error building trunk r24371
On Fri, Dec 10, 2010 at 5:26 AM, Alexey Loukianov wrote: > Try to "make dirclean" your buildtree, or create a fresh new symlinked > build > sandbox with help of symlink-tree.sh script. Chances are high the error > would > went away. > > No more automake errors. Now it's dying at: make[6]: *** No rule to make target `-lltdl', needed by `collectd'. Stop. I had this error before, it went away I thought, now it's back. Cheers, -JR ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] enable video4linux2 in ffmpeg
Enable v4l2 (and other) "input devices" that were previously disabled to support capture directly from UVC-style cameras. There is no way to re-enable individual "input devices" after a "--disable-devices" argument is supplied to ./configure as is done with decoders, encoders, muxers, parsers, and protocols. Thus do not disable "devices" to begin with. Signed-off-by: J. Ryan Earl svn diff feeds/packages/ffmpeg/Makefile Index: feeds/packages/ffmpeg/Makefile === --- feeds/packages/ffmpeg/Makefile (revision 24626) +++ feeds/packages/ffmpeg/Makefile (working copy) @@ -209,7 +209,6 @@ $(if $(CONFIG_FFMPEG_IPV6),,--disable-ipv6) \ \ --disable-bsfs \ - --disable-devices \ --disable-encoders \ $(FFMPEG_CONFIGURE_ENCODERS) \ --disable-decoders \ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] enable video4linux2 in ffmpeg
Enable v4l2 (and other) "input devices" that were previously disabled to support capture directly from UVC-style cameras. There is no way to re-enable individual "input devices" after a "--disable-devices" argument is supplied to ./configure as is done with decoders, encoders, muxers, parsers, and protocols. Thus do not disable "devices" to begin with. Rev package. svn diff feeds/packages/ffmpeg/Makefile Index: feeds/packages/ffmpeg/Makefile === --- feeds/packages/ffmpeg/Makefile (revision 24626) +++ feeds/packages/ffmpeg/Makefile (working copy) @@ -9,7 +9,7 @@ PKG_NAME:=ffmpeg PKG_VERSION:=0.5.2 -PKG_RELEASE:=4 +PKG_RELEASE:=5 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 PKG_SOURCE_URL:=http://ffmpeg.org/releases/ @@ -209,7 +209,6 @@ $(if $(CONFIG_FFMPEG_IPV6),,--disable-ipv6) \ \ --disable-bsfs \ - --disable-devices \ --disable-encoders \ $(FFMPEG_CONFIGURE_ENCODERS) \ --disable-decoders \ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] package: mjpg-streamer - add separate package for wwwdemo files and aprop. config option to the config file and init script
On Sat, Dec 18, 2010 at 7:55 AM, Alexey Loukianov wrote: > Currently mjpg-streamer lacks any web user interface installed aboard with > it. > This patch introduces new package with the demo www web interface shipped > with > the mjpg-streamer and introduces new config option "wwwdir" (commented out > by > default) where one may specify what directory should mjpg-streamer use as > its > wwwroot. > > -- > Best regards, > Alexey Loukianov mailto:mooro...@mail.ru > System Engineer,Mob.:+7(926)218-1320 > *nix Specialist > As a note: without the optional www files "http:///?action=stream" will give you the stream even though "http:///" will display a "not-found" error. -JR ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] r24920 and others: ath9k: DMA failed to stop in 10 ms
On Tue, Jan 11, 2011 at 1:35 PM, John Clark wrote: > I have seen this message emited by the resulting OpenWRT package for my > Atheros AP83 based system. > > I had been using a snapshot of OpenWRT from March 2010, which did not have > this problem. However > for any of the kernels I have tried, 2.6.32.27, 2.6.36, 2.6.37, all have > this error message. > > In addition, when I use Station mode and associate two devices that are > running OpenWRT, I get incredibly > flaky iperf numbers, with packet losses going up to 10% on a 10 mbs stream. > Whereas when I use > a non-OpenWRT station, with an OpenWRT AP, I get almost no loss on the 10 > mbs stream, and can > get up to 30-40 mbs with 'some loss'. > > So, the question is, what has happened since last March with the linux > ath9k driver support? What's the exact error? I've see something similar in my dmesg: ath: Failed to stop TX DMA in 100 msec after killing last frame However, I get great performance regardless. Able to pull 150 mbit/s actual in a 2x2 MIMO configuration. -JR ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] r24920 and others: ath9k: DMA failed to stop in 10 ms
On Wed, Jan 12, 2011 at 11:54 AM, John Clark wrote: > Roback, Joe schrieb: > >> I would agree, lately, I am seeing a bunch of these in my logs: >> >>ath: Failed to stop TX DMA in 100 msec after killing last frame >>> >> >> but my 802.11n 40MHz performance has been the best its been in 6 months >> ;-) >> >> >> On Tue, 11 Jan 2011 16:35:10 -0600, "J. Ryan Earl" >> wrote: >> >>> >>> >>> What's the exact error? I've see something similar in my dmesg: >>> >>> ath: Failed to stop TX DMA in 100 msec after killing last frame >>> >>> However, I get great performance regardless. Able to pull 150 mbit/s >>> actual >>> in a 2x2 MIMO configuration. >>> >> > > Are you two using 'station' mode and associating with a OpenWRT AP. Because > I'm getting abysmal performance. > Running iPerf in UDP mode, frequently gives 10% packet loss at 10 mbs... > > Theplatform I'm using is pretty close to the Atheros AP83 reference design. > I also have tested with a non-OpenWRT > station, and get much better performance. It is in "Access Point" mode. I measured throughput not with iperf, but by transferring data from a server on the LAN-side to an associated wireless device (a laptop in my case with a Intel 5100 AGN card) and inspecting the network traffic on both ends of the transport. I would suggest generating the traffic outside of OpenWRT so as to not impose any additional overhead that could affect your performance results. -JR ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] user.info sysinit: RTNETLINK errors
I have some log snips below from a WNDR3700v2. I'm curious what is causing the following errors, it seems to happen one time and never again. This is from r26504: Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: Invalid argument Mar 27 02:54:00 OpenWrt user.info sysinit: We have an error talking to the kernel Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: Invalid argument Mar 27 02:54:00 OpenWrt user.info sysinit: We have an error talking to the kernel Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: Invalid argument Mar 27 02:54:00 OpenWrt user.info sysinit: We have an error talking to the kernel Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: Invalid argument Mar 27 02:54:00 OpenWrt user.info sysinit: We have an error talking to the kernel Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: Invalid argument Mar 27 02:54:00 OpenWrt user.info sysinit: We have an error talking to the kernel Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: No such file or directory Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: Invalid argument Mar 27 02:54:00 OpenWrt user.info sysinit: We have an error talking to the kernel Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: Invalid argument Mar 27 02:54:00 OpenWrt user.info sysinit: We have an error talking to the kernel Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: Invalid argument Mar 27 02:54:00 OpenWrt user.info sysinit: We have an error talking to the kernel Mar 27 02:54:00 OpenWrt user.info sysinit: RTNETLINK answers: Invalid argument Mar 27 02:54:00 OpenWrt user.info sysinit: We have an error talking to the kernel Mar 27 02:54:00 OpenWrt user.notice ifup: Allowing Router Advertisements on wan (eth1) dmesg follows: Linux OpenWRT 2.6.37.6 #1 Wed Apr 6 23:51:41 CDT 2011 mips GNU/Linux root@gate:~# dmesg Linux version 2.6.37.6 (wrtdev@openwrt-dev) (gcc version 4.3.3 (GCC) ) #1 Wed Apr 6 23:51:41 CDT 2011 prom: fw_arg0=0006, fw_arg1=a3f6bfb0, fw_arg2=a3f6c450, fw_arg3=0010 MyLoader: sysp=5554, boardp=5554, parts=5554 bootconsole [early0] enabled CPU revision is: 00019374 (MIPS 24Kc) Atheros AR7161 rev 2, CPU:680.000 MHz, AHB:170.000 MHz, DDR:340.000 MHz Determined physical RAM map: memory: 0400 @ (usable) Initrd not found or empty - disabling initrd Zone PFN ranges: Normal 0x -> 0x4000 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0: 0x -> 0x4000 On node 0 totalpages: 16384 free_area_init_node: node 0, pgdat 802c3460, node_mem_map 8100 Normal zone: 128 pages used for memmap Normal zone: 0 pages reserved Normal zone: 16256 pages, LIFO batch:3 pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 pcpu-alloc: [0] 0 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 Kernel command line: board=WNDR3700v2 mtdparts=spi0.0:320k(u-boot)ro,128k(u-boot-env)ro,1024k(kernel),14848k(rootfs),64k(art)ro,15872k@0x7(firmware) rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200 PID hash table entries: 256 (order: -2, 1024 bytes) Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entr
