**** BEGIN LOGGING AT Mon Jul 08 02:59:59 2013 Jul 08 07:13:40 luka r37191 trunk/target/ linux/lantiq/patches-3.9/0010-NET-MIPS-lantiq-update-etop-driver-for-devicetree.patch linux/lantiq/patches-3.8/0026-NET-MIPS-lantiq-update-etop-driver-for-devicetree.patch * lantiq: etop enable gbit port0 Jul 08 08:41:59 juhosg r37192 trunk/target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c * ar71xx: fix for wrong eth0 mac assignment on Netgear WNDAP360 Jul 08 08:42:00 juhosg r37193 trunk/target/linux/ar71xx/image/Makefile * ar71xx: fix partition layout on Netgear WNDAP360 Jul 08 08:42:01 juhosg r37194 trunk/target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wr841n-v8.c * ar71xx: disable JTAG on TL-WR841N-v8/MR3420v2 Jul 08 08:42:02 juhosg r37195 trunk/target/ linux/generic/config-3.9 linux/generic/config-3.10 * linux: refresh kernel configs with kconfig.pl Jul 08 08:43:23 juhosg r37196 packages/net/ tstat tstat/Makefile * packages: add tstat Jul 08 08:46:44 wigyori r37197 trunk/tools/ Makefile bc bc/Makefile * [tools] add bc as required by kernels 3.9+ Jul 08 09:03:18 blogic r37198 trunk/package/ (18 files in 8 dirs) * lantiq: move dsl tools to package/network/config Jul 08 09:03:23 blogic r37199 trunk/package/ system/ubox/files/fstab.default system/ubox/Makefile * ubox: add a uci-default script for fstab generation Jul 08 09:03:28 blogic r37200 trunk/target/linux/ramips/modules.mk * ralink: add i2c-ralink kmod info Jul 08 09:03:32 blogic r37201 trunk/package/kernel/linux/modules/i2c.mk * kernel: unbreal of_i2c selection Jul 08 09:03:38 blogic r37202 trunk/target/linux/ramips/patches-3.9/0153-i2c-MIPS-adds-ralink-I2C-driver.patch * ralink: unbreak ralink i2c support Jul 08 15:47:54 build #284 of rb532 is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/284 Jul 08 15:49:46 build #284 of ppc44x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/284 Jul 08 16:05:58 uhm, is it possible to specify for a package to look for libuClibc++.so.0 in.. lets say /var/lib ? i have a router with brcm47xx that has a squashfs ro and i can only write in /var Jul 08 16:06:20 tried to compile iperf on this laptop, moved it over the router and of course it complains about libuClibc++.so.0 Jul 08 16:06:51 LD_LIBRARY_PATH=/var/lib:/usr/lib:/lib /var/bin/program Jul 08 16:07:42 cool, now it says "/var/test/iperf: symbol 'stderr': can't handle reloc type 0x7e Jul 08 16:07:42 " Jul 08 16:07:52 different uclibc abi Jul 08 16:08:09 yep, its a zte router firmware with old stuff Jul 08 16:08:22 then you need to build iperf with an old openwrt Jul 08 16:08:43 it's not running openwrt, it has some libraries in /lib but i suspect they are pretty old Jul 08 16:08:54 old openwrt to get an older uclibc Jul 08 16:09:18 oook, let me try, thanks Jul 08 16:09:28 alternatively you can install openwrts libc as well Jul 08 16:09:43 to /varlib Jul 08 16:09:47 it's libuClibc-0.9.29.so Jul 08 16:09:57 hmm Jul 08 16:10:40 kamikaze 8.09 has this version Jul 08 16:29:47 thanks! i'm gonna let it compile here and try it later, have a wonderful evening! Jul 08 16:36:33 blogic r37203 trunk/target/linux/ramips/patches-3.9/0159-NET-MIPS-add-ralink-SoC-ethernet-driver.patch * ralink: vlan offloading is causing problems. disable it Jul 08 16:36:43 blogic r37204 trunk/package/base-files/files/etc/init.d/boot * base-files: add 2 missing variable defines Jul 08 16:36:51 blogic r37205 trunk/package/system/procd/files/procd.init * procd: remove obseleted procd.init file Jul 08 16:37:00 blogic r37206 trunk/package/ system/procd/files/log.init system/procd/Makefile * procd: update to latest git revision Jul 08 18:25:25 what is the plan for moving kernel to 3.10? ar71xx still on 3.8.13 since months ;-) Jul 08 18:25:55 why do you need 3.10? Jul 08 18:31:00 build #314 of atheros is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/314 Jul 08 19:33:03 need? need? when did that have anything to do with using new kernels??? ;-) Jul 08 20:22:43 hi Jul 08 20:22:59 blogic: which values do i have to set to get procd to log to a file? Jul 08 20:23:26 i have this in /etc/config/system Jul 08 20:23:29 option log_file "/var/log/messages" Jul 08 20:23:29 option log_size 16000 Jul 08 20:23:33 option log_file /var/log/message Jul 08 20:23:39 optio size 64 Jul 08 20:23:45 log_size is KB Jul 08 20:23:53 that works for me Jul 08 20:23:58 oops Jul 08 20:24:03 option log_size 64 Jul 08 20:25:05 but in which file? Jul 08 20:25:08 /etc/config/system? Jul 08 20:25:19 yes Jul 08 20:25:23 in the system section Jul 08 20:25:37 it seems it ignores it here Jul 08 20:25:44 http://wiki.openwrt.org/doc/uci/system Jul 08 20:25:55 typo ? Jul 08 20:26:11 the same config worked before with syslog and klog Jul 08 20:26:23 is option log_type file Jul 08 20:26:27 also needed? Jul 08 20:26:39 nope Jul 08 20:26:50 okay Jul 08 20:26:52 log_file and log_size are needed Jul 08 20:27:02 and a current trunk from 3-4 hours ago Jul 08 20:27:02 how can i restart procd? Jul 08 20:27:07 you cant Jul 08 20:27:10 i compiled a few mintues ago Jul 08 20:27:13 why would you want to ? Jul 08 20:27:20 /etc/init.d/log start Jul 08 20:27:22 to test the new config Jul 08 20:27:45 /etc/init.d/log start Jul 08 20:28:12 doesnt work Jul 08 20:28:18 the file isnt even created Jul 08 20:29:16 blogic how can i find out whats going wrong? Jul 08 20:29:34 check the crystal ball :) Jul 08 20:29:40 gimme a sec to test Jul 08 20:29:47 :) Jul 08 20:31:26 hmm the values are read correctly inside the init file Jul 08 20:31:27 echo ${log_file} ${log_size} Jul 08 20:31:31 gives me Jul 08 20:31:33 /var/log/messages 16000 Jul 08 20:31:42 log_size is still KB Jul 08 20:31:49 ypu want a 16MB log file ? Jul 08 20:32:02 yes im logging on a hd Jul 08 20:32:12 /sbin/logread -f -F /var/log/messages -S 16000 Jul 08 20:32:15 try that manually Jul 08 20:33:18 the file is created but still empty Jul 08 20:33:33 logger foo Jul 08 20:33:40 now it works Jul 08 20:33:44 try to generate a log event to be filled Jul 08 20:33:53 so you had a typo somewhere? Jul 08 20:33:57 but why doesnt it work when i start the init script? Jul 08 20:34:20 ask the crystal ball or debug it ;) Jul 08 20:34:26 maybe braces are a problem? Jul 08 20:34:29 it works very well here Jul 08 20:34:50 where do you see braces ? Jul 08 20:34:56 and i assume oyu mean brackets Jul 08 20:35:15 braces are he things you have in your mouth to adjust your teeth Jul 08 20:35:34 braces and brackets are the same word in german but not in english Jul 08 20:35:43 Jul 08 20:35:52 i ment quotes Jul 08 20:36:24 ps |grep log Jul 08 20:36:28 1438 root 1264 S /sbin/logread -f -F /var/log/messages -p /var/run/logread.1.pid -S Jul 08 20:36:44 it started like this from the init file Jul 08 20:36:44 /sbin/logread -f -F /var/log/messages -p /var/run/logread.1.pid -S 16000 Jul 08 20:37:00 at least ps w shows this Jul 08 20:37:12 ps caps the line aftre X chars Jul 08 20:37:23 ps caps the line after X chars Jul 08 20:37:37 yeah ps w gives the full output Jul 08 20:38:02 oh ok Jul 08 20:38:12 gimme a sec, i just flashed a none working test image Jul 08 20:38:22 let me fix the bg so i have a unit i can try to reproduce htis on Jul 08 20:38:31 you are running on a ar71xx unit i assume ? Jul 08 20:38:39 yes Jul 08 20:42:19 blogic: when i start it without the -p it works with it, it doesnt Jul 08 20:42:34 oh Jul 08 20:47:42 tripolar: and /var/run exists ? Jul 08 20:47:52 yes Jul 08 20:48:04 the file is also created Jul 08 20:48:18 but somehow the log isn't written to the file Jul 08 20:48:36 this is in combination with extroot ? Jul 08 20:48:40 or pivotroot ? Jul 08 20:48:43 ext Jul 08 20:48:52 using overlayfs ? Jul 08 20:48:52 i meant pivot Jul 08 20:48:55 ok Jul 08 20:49:01 let me try that Jul 08 20:49:05 ermmm Jul 08 20:49:16 the extroot has the latest logread on it ? Jul 08 20:49:23 i think so Jul 08 20:49:33 logread belong to which package? Jul 08 20:49:37 procd Jul 08 20:49:44 yes Jul 08 20:50:09 as procd opkg list |grep procd Jul 08 20:50:09 procd - 2013-07-08-725e6bbbe403a950c0ddcd23cb521ffefa705c7d Jul 08 20:52:11 blogic: probably you can say something useful about it... About the lantiq vgv7519 (vrx288) I have 2 gpio leds, they should act like link/tx/rx status from the 2 internal ethernet PHY's Jul 08 20:52:39 I saw something in UCI system config, but it is possible to configure the netdev in the device tree config? Jul 08 20:53:05 ? Jul 08 20:53:12 yes, no yes ? ;) Jul 08 20:53:20 you are mixing stuff Jul 08 20:53:33 1) phy leds, 2) uci, 3) netdev in OF Jul 08 20:53:36 as always ;)... trying again Jul 08 20:53:50 the 2 leds are on gpio 7 and 44... Jul 08 20:54:09 using UCI I should be able to configure them to act as link/tx/rx... Jul 08 20:54:25 the question is if it is possible to configure it in the device tree (dts file) Jul 08 20:54:33 yes Jul 08 20:54:42 you can set the default trigger in the OF i think Jul 08 20:54:57 actually netdev trigger might not support that yet Jul 08 20:55:01 blogic removing the -p stuff from the init.d/file works too Jul 08 20:55:16 tripolar: ok Jul 08 20:55:17 /etc/init.d/log Jul 08 20:56:54 in the linux 3.8.13 device tree documentation, only the triggers backlight, default-on, hartbeat, ide-disk and timer are documented... Jul 08 20:57:16 The_Lizard: netdev trigger is a openwr trigger i think Jul 08 20:57:32 So it can be specified as well... Jul 08 20:57:43 any idea how to specify the network interface parameters etc? Jul 08 20:58:23 no Jul 08 20:59:27 I will try to figure out something ;) Jul 08 21:00:05 Anything else: I have a patch for the dual nor flash, it is a change that combines the old code with the physmap code... Jul 08 21:01:02 ok Jul 08 21:01:04 show me Jul 08 21:01:10 ... please Jul 08 21:01:54 http://pastebin.com/KSbmgb6s Jul 08 21:02:16 KanjiMonster has already taken a look at it as well... Jul 08 21:08:27 Is it possible to flush the uci configuration that is in /etc/config? so that a new file is generated? Jul 08 21:10:56 blogic: a reboot fixed the problem Jul 08 21:11:12 i dont know what was wrong before Jul 08 21:12:11 tripolar: weird Jul 08 21:12:15 yeah Jul 08 21:12:30 tell me if it returns please Jul 08 21:12:30 i feels like windo$ ;) Jul 08 21:12:34 i will Jul 08 21:12:37 thx ! Jul 08 21:12:48 i just tried on a pivot root and it worked Jul 08 21:12:48 thanks for your help Jul 08 21:12:51 weird stuff Jul 08 21:22:41 i will go now - have a nice evening blogic Jul 08 21:29:33 blogic: I have another issue... The system seems to have started correctly, but I'm still unable to get network communication Jul 08 21:29:49 The link goes up when a cable is connected, but pinging to the host machine fails... Jul 08 21:30:06 when you ping the unit, doe irq counters increase ? Jul 08 21:30:11 cat /proc/interrupts Jul 08 21:30:22 I have no idea, should test that... Jul 08 21:30:43 please paste /proc/interrupts Jul 08 21:31:10 It will take a few minutes, re-flashing the board ;) Jul 08 21:31:15 sure Jul 08 21:31:25 tripolar: and he returns Jul 08 21:31:30 blogic: another reboot and the problem is again here Jul 08 21:31:39 i can only read the log with logread Jul 08 21:32:21 ok Jul 08 21:32:25 will retry it tomorrow Jul 08 21:32:27 hmm it logs wrong Jul 08 21:32:31 its in the file Jul 08 21:32:41 ... but ? Jul 08 21:32:48 but it put it before the logs that where allready in the file Jul 08 21:33:06 Mon Jul 8 23:32:08 2013 ftp.info sshd[1315]: Found matching RSA key: 04:47:59:bd:7f:db:2c:43: Jul 08 21:33:09 6e:40:15:34:45:a6:b1:d4 Jul 08 21:33:12 Mon Jul 8 23:32:08 2013 ftp.info sshd[1315]: Postponed publickey for root from 192.168.1.3 port 53397 ssh2 [preauth] Jul 08 21:33:15 Mon Jul 8 23:32:08 2013 ftp.info sshd[1315]: Found matching RSA key: 04:47:59:bd:7f:db:2c:43:6e:40:15:34:45:a6:b1:d4 Jul 08 21:33:18 Mon Jul 8 23:32:08 2013 ftp.info sshd[1315]: Accepted publickey for root from 192.168.1.3 port 53397 ssh2 Jul 08 21:33:21 Mon Jul 8 23:22:54 2013 ftp.info sshd[1322]: Found matching RSA key: 04:47:59:bd:7f:db:2c:43:6e:40:15:34:45:a6:b1:d4 Jul 08 21:33:24 the last line was the first line before Jul 08 21:33:39 funky Jul 08 21:33:51 it is truncating and not appending Jul 08 21:33:58 ok, i will fix that tomorrow Jul 08 21:34:02 thanks for etsting ! Jul 08 21:34:12 it prepands it Jul 08 21:34:22 and it doesnt append it to the end of the file Jul 08 21:34:22 yes, a truncate Jul 08 21:35:00 i thought truncate means "stutzen" Jul 08 21:35:46 O_TRUNC If the file already exists and is a regular file and the open mode allows writing (i.e., is O_RDWR or O_WRONLY) it will be truncated to length 0. If the file is a FIFO or terminal device file, the O_TRUNC flag is ignored. Otherwise the effect of O_TRUNC is unspecified. Jul 08 21:35:53 that should reset the file Jul 08 21:35:55 but it does not Jul 08 21:36:01 so i will check whats wrong tomorrow Jul 08 21:36:12 okay Jul 08 21:36:34 really weired Jul 08 21:36:49 when i find some time i will fix it Jul 08 21:37:10 flashing is done, lets check the irq counter... Jul 08 21:37:40 and you mean pinging from computer to device right? Jul 08 21:38:05 blogic: wouldnt just the remove of O_TRUNC fix it? Jul 08 21:38:16 okay it will then just replace the file on every reboot Jul 08 21:39:05 blogic: i think it should be O_APPEND Jul 08 21:39:38 yeah replace O_TRUNC with O_APPEND Jul 08 21:39:43 that should fix it Jul 08 21:40:06 O_APPEND Jul 08 21:40:06 The file is opened in append mode. Before each write(2), the file Jul 08 21:40:09 offset is positioned at the end of the file, as if with lseek(2). Jul 08 21:40:25 yes Jul 08 21:41:09 i love open source :) Jul 08 21:48:04 blogic: http://pastebin.com/ZuhVYNQq Jul 08 21:48:27 72: 211 icu vrx200_rx Jul 08 21:48:27 73: 13 icu vrx200_tx Jul 08 21:48:30 looks good Jul 08 21:49:36 they both increase a bit when trying to transmit/receive data... Jul 08 21:49:43 what could then be the problem? Jul 08 21:50:09 do the ifconfig counters increase ? Jul 08 21:50:14 I do get link up/down events when a cable is attached Jul 08 21:50:26 you said that already Jul 08 21:50:31 russell--: re: 3.10, it's certainly doable Jul 08 21:50:39 yes, there are sent and received packets (on both br-lan and eth0) Jul 08 21:50:52 and what does wireshark say ? Jul 08 21:50:52 I also have nas0, it only has tx packets Jul 08 21:51:04 loopback has a lot of rx and tx packets Jul 08 21:51:05 swalker: /me is lazy or i'd have tried it already Jul 08 21:51:27 didn't even think about that * facepalm * Jul 08 22:00:47 Very clear from wireshark... Jul 08 22:00:59 Ping from device -> computer works Jul 08 22:01:14 the device fails in receiving traffic\ Jul 08 22:04:37 blogic: any ideas? Jul 08 22:20:01 blogic: I'm going to bed, plz post if you have any ideas, will read it tomorrow... thanks for the help! Jul 08 22:20:12 the led blinking works for eth0 :) Jul 08 22:20:34 now find out if it is possible to map it to the physical port... (not the entire interface) Jul 08 22:33:48 build #270 of sibyte is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/270 Jul 08 22:51:39 build #272 of xburst is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/272 Jul 08 23:10:15 wigyori r37207 trunk/target/linux/imx23/config-default * imx23: add gpio_sysfs support Jul 08 23:26:05 build #271 of ixp4xx is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/271 Jul 09 02:12:02 build #305 of ramips is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/305 **** ENDING LOGGING AT Tue Jul 09 03:00:00 2013