**** BEGIN LOGGING AT Sun Jun 30 02:59:58 2013 Jun 30 05:44:51 any dev around just to point me how to build an image with lspci? Jun 30 06:40:34 build #209 of octeon is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/209 Jun 30 06:49:59 <[mbm]> Devastator: opkg update; opkg install pciutils Jun 30 06:50:56 [mbm] is there a way to integrate lspci to an image? Jun 30 06:56:31 <[mbm]> sure, if you're compiling your own image just select it in menuconfig Jun 30 06:57:38 yep, I just can't find it, shouldn't it be under Utilities? Jun 30 06:59:23 <[mbm]> make sure you've installed the extra packages (make package/symlinks) Jun 30 07:08:02 yes!! thanks! Jun 30 07:56:14 nbd r37093 trunk/toolchain/binutils/ patches/2.19.1 Makefile patches/2.21.1 Config.in * binutils: remove some unused obsolete versions Jun 30 07:56:19 nbd r37094 trunk/toolchain/binutils/patches/ 2.23.1/400-mips_no_dynamic_linking_sym.patch 2.22/600-mips_no_dynamic_linking_sym.patch * binutils: stop generating the useless _DYNAMIC_LINKING symbol on mips Jun 30 07:56:23 nbd r37095 trunk/toolchain/gcc/ patches/4.8-linaro/880-no_java_section.patch patches/4.8.0/880-no_java_section.patch patches/4.6-linaro/880-no_java_section.patch patches/4.6.3/880-no_java_section.patch * gcc: add a patch to get rid of useless java class sections Jun 30 07:56:26 nbd r37096 trunk/toolchain/uClibc/patches-0.9.33.2/210-mips_use_pic_crt1.patch Jun 30 07:56:27 uClibc: use position independent code for crt1, slightly reduces size of all executables Jun 30 08:30:46 build #318 of at91 is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/318 Jun 30 10:45:56 nbd r37097 trunk/package/ (31 files in 3 dirs) * mac80211: update to wireless-testing 2013-06-27, fix ATH_USER_REGD handling Jun 30 11:23:46 ping Kaloz Jun 30 11:28:08 is there a way to backup the complete mtd chip? with uboot and all other stuff? Jun 30 11:28:59 or do i have to dd every /dev/mtdblock* manually? Jun 30 11:32:29 I don't think so, but usually you don't need all mtdblock* as some are overlapping (e.g. linux/firmware usually covers kernel, rootfs and rootfs_data) Jun 30 11:58:16 Hi all, I have a board with dual nor flash, but only one is detected (while they are both detected in u-boot), Can anyone assist me? Jun 30 12:00:18 The_Lizard: what target? Jun 30 12:00:43 http://wiki.openwrt.org/toh/arcadyan/vgv7519 Jun 30 12:04:53 In u-boot, some ebu (external bus unit) had to be configured to make second flash available Jun 30 12:05:39 I have no idea if something similar has to be done for openWRT or that I just have to configure the second flash somewhere Jun 30 12:09:30 KanjiMonster but how can i make a clomplete backup of the fash chip? Jun 30 12:09:59 tripolar: I meant there is no other way than backing up mtdblock* until you got everything covered Jun 30 12:10:18 okay Jun 30 12:15:17 KanjiMonster: do you have any idea on how I should achieve this? Jun 30 12:15:54 The_Lizard: not specifically Jun 30 12:16:10 look at the uboot code, replicate that for the lantiq target Jun 30 12:16:27 or check what needs to be done to achive the same Jun 30 12:17:44 The problem is that I have no idea where to find the code in the openwrt tree... Jun 30 12:19:25 target/linux/lantiq/patches-* Jun 30 12:19:42 well, only part of it Jun 30 12:20:16 the extracted code is in build_dir/target-*/linux-*/linux-*/arch/mips/lantiq/ Jun 30 12:20:29 ok, so the patches are actually the code... Jun 30 12:32:39 The_Lizard: the patches patch the kernel code (part of lantiq support already comes from the linux tarball) Jun 30 12:35:45 I am using a lantiq tree from daniel schwierzeck, so there is some more support for it Jun 30 12:35:56 I start to understand how it works... Jun 30 12:36:10 now finding the pieces to make it work ;) Jun 30 12:36:55 the best case is submitting these patches upstream to linux-mips ;-) Jun 30 12:37:06 (while submitting it to openwrt) Jun 30 12:42:28 Does openwrt use code from the u-boot tree (or are they completely separate?) Jun 30 12:43:14 completely separate Jun 30 12:43:43 well, it uses code from the u-boot tree for building u-boot and its utilities ;) Jun 30 12:44:31 blogic: I just stumbled on the pcf857x support you added in r36180 in package/kernel/moduls/other.mk. That one was already existing in package/kernel/linux/i2c.mk since r28334. Jun 30 12:44:54 In my tree, I see a vr9.dtsi file with the following lines: Jun 30 12:44:54 ltq_ebu_regs Jun 30 12:45:25 ebu0: ebu@E105300 { compatible = "lantiq,ebu-xway"; Jun 30 12:45:45 but I have no idea where I should find any code related to it's initialisation Jun 30 12:46:07 I guess I should be looking for the ebu driver Jun 30 12:48:14 The_Lizard: in theory it should be described in Documentation/devicetree/bindings/ in the kernel Jun 30 12:52:16 i mean package/kernel/linux/moduls/ both times ;) Jun 30 12:52:59 ok, thanks Jun 30 13:11:27 jogo r37098 trunk/target/ (105 files) * bcm63xx: update patches Jun 30 13:11:36 jogo r37099 trunk/target/ (32 files) * bcm63xx: make smp kernels boot on older SoCs Jun 30 13:11:39 jogo r37100 trunk/target/ linux/brcm63xx/image/Makefile linux/brcm63xx/smp/config-default linux/brcm63xx/config-3.9 linux/brcm63xx/generic/config-default * bcm63xx: enable all SoCs for both subtargets Jun 30 13:11:41 jogo r37101 trunk/target/ (9 files) * bcm63xx: Improve CFE version mod patch. Jun 30 13:11:44 jogo r37102 trunk/target/ linux/brcm63xx/patches-3.9/534-board_hw556.patch linux/brcm63xx/patches-3.9/801-ssb_export_fallback_sprom.patch linux/brcm63xx/patches-3.9/535-board_rta770w.patch * brcm63xx: Fixes and additions to the GPIO assignment of Huawei HW556 leds Jun 30 13:11:48 jogo r37103 trunk/ (103 files in 10 dirs) * kernel: update linux 3.9 to 3.9.8 Jun 30 13:20:09 Thanks KanjiMonster, I have 2 idea's to try to fix it... Jun 30 13:20:41 Then I have another question, as it is a new board, What components do I have to write to the flash to make openwrt happy? Jun 30 13:21:51 I have my uboot from 0 to 0x40000, at 0x60000 is the uboot storage, and from 0x80000 - 0x800000 is the rest of the flash Jun 30 13:22:12 additional to this first 8MB is another 8 MB chip Jun 30 13:23:30 from what I see from the flash.layout wiki, I need the kernel (I guess it is the uImage from the build), a squashFS image and a JFFS2 image and some mtd4 part (I don't know what it is..) Jun 30 13:32:24 The_Lizard: usually it's just kernel as uImage + appended rootfs Jun 30 13:32:54 and if you look at the buffalo mach code in ar71xx, you should see some examples on how to treat two flashes as one Jun 30 13:39:46 build #297 of ramips is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/297 Jun 30 14:07:31 build #276 of rb532 is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/276 Jun 30 14:15:55 build #276 of ppc44x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/276 Jun 30 14:18:27 KanjiMonster: Openwrt doesn't seem to mess-up the ebu configuration so both flash devices should be detectable... Can you point me a bit further where to look in the buffalo code? Jun 30 14:19:48 is it the dev-m25p80 code??? Jun 30 14:20:59 is this memory mapped flash or spi flash? Jun 30 14:21:08 yes, that one Jun 30 14:22:25 I don't think it is spi flash (http://www.eonssi.com/upfile/p2010610151847.pdf) Jun 30 14:23:45 nbd: did you intend to remove https://dev.openwrt.org/browser/packages/utils/mdadm with r37060? Jun 30 14:26:27 i intended to remove it in a later commit (keeping trunk and packages in separate git trees) Jun 30 14:26:28 just didn't get around to it yet Jun 30 14:27:17 nbd r37104 packages/utils/mdadm * mdadm: remove from /packages, it is in /trunk now Jun 30 14:29:47 blogic: i sent a new patch to the ml to add fs_check functionality to block Jun 30 14:30:09 it alos removed a newline that was not removed in my last patch Jun 30 14:30:54 blogic: http://paste.debian.net/13436/ Jun 30 14:43:02 updated openwrt/upstream, https://home.comcast.net/~sdwalker/uscan/index.html Jun 30 14:50:50 nbd r37105 trunk/package/kernel/mac80211/Makefile * mac80211: use a new tarball with updated backport code Jun 30 15:28:35 KanjiMonster: It is still not working, do i need to configure both flashes in the dts file for the probing to work correctly? Jun 30 15:28:52 if so, is there an example with 2 nor flashes? Jun 30 15:51:00 I'm seeing "Invalid RF chipset 0xfced detected" on Ralink RT5350F, as I'm new to porting devices, can it be caused by wrong flash layout mapping? Jun 30 15:51:42 it detects the RT chipset properly, but gives this bogus RF Jun 30 15:53:11 brb, I'm gonna flash an image with lspci to give more info Jun 30 16:03:21 nbd r37106 trunk/package/utils/busybox/config/miscutils/Config.in Jun 30 16:03:21 busybox: disable the watchdog utility by default (procd handles watchdog devices) Jun 30 16:19:48 is enabling pciutils enough to get lspci working? I get "pcilib: Cannot open /proc/bus/pci" "lspci: Cannot find any working access method." Jun 30 16:36:23 Devastator: maybe you should try it on a router that actually has PCI ;) Jun 30 16:36:38 heheh Jun 30 16:37:04 sorry, I'm struggling for hours to discover why this bogus chipset id Jun 30 16:37:30 what openwrt version is this? Jun 30 16:37:39 trunk, I'm porting the device Jun 30 16:37:54 trunk? could you be a bit more specific? Jun 30 16:38:32 sure, r37080 Jun 30 16:41:02 i think i found the bug Jun 30 16:42:32 Devastator: update to latest trunk, then apply this patch on top: http://nbd.name/rt5350.patch Jun 30 16:42:35 then try again Jun 30 16:42:45 alright! Jun 30 16:44:01 even if it gets the whole thing further, you probably still have an issue with your eeprom data for the wifi device Jun 30 16:44:10 probably looking in the wrong flash location or something Jun 30 16:44:58 I tried to dump manually just to check the offsets, the only offset I get junk is what I think is the right one Jun 30 16:49:56 patch -p0 < http://nbd.name/rt5350.patch? Jun 30 16:50:11 -p1 Jun 30 16:51:19 okie Jun 30 16:55:29 build #262 of sibyte is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/262 Jun 30 16:56:02 rebuilding.. Jun 30 16:56:28 thanks once again Jun 30 16:57:17 I finally have something to play with openwrt Jun 30 17:10:58 florian r37107 trunk/include/kernel-defaults.mk * buildroot: filter out dtbs KERNELNAME target (#13785) Jun 30 17:16:23 florian r37108 trunk/include/prereq-build.mk * prereq-build: check for "bc" (#13767) Jun 30 17:33:37 Devastator: so does it work? Jun 30 17:34:08 nbd still building, pretty old hardware here.. Jun 30 17:35:20 nbd do you know a way to read the dump file soc_wmac.eeprom? some hex reader? Jun 30 17:38:03 i'd look at it with hexdump and check the source code to figure out the format Jun 30 17:42:17 doesn't make any possible sense.. Jun 30 17:42:33 but I'm not sure if my flash layout is correct.. Jun 30 17:46:35 nbd can you take a look of what I've set and what is on stock firmware? mine: http://codepad.org/4q3HxIsJ and stock: http://codepad.org/pDQu530Z Jun 30 17:46:52 ok, build finished, I'm gonna test, brb Jun 30 17:53:34 Can someone help me with an issue with probing a 2 CFI NOR flashes Jun 30 17:54:19 I don't know if I need to specify both in the dts file, and if so, how to do it. Jun 30 17:54:27 nbd now it says eeprom file size is invalid, it wants 512, I just saw the patch from Gabor, can you include to your patch or should I hack just to test? Jun 30 17:55:07 i'll commit my fix Jun 30 17:55:56 nbd r37109 trunk/package/kernel/mac80211/patches/616-rt2x00-support-rt5350.patch * rt2x00: fix rf id override for RT5350 Jun 30 18:01:05 thanks! buildroot updated Jun 30 18:01:55 now I wonder why it asked for a 512 byte eeprom file if Gabor patch didn't went upstream yet.. Jun 30 18:08:31 why do you think it didn't go upstream? It was submitted not long ago, and was accepted three days ago Jun 30 18:08:33 build #236 of iop32x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/236 Jun 30 18:09:16 Devastator: https://git.kernel.org/cgit/linux/kernel/git/linville/wireless-next.git/commit/?id=51f877ab1ae13680dcb13de7d9b8f7dccb109e44 ;) Jun 30 18:09:42 KanjiMonster sorry, I meant for openwrt Jun 30 18:10:51 like.. how can my image asks for a 512 byte if every other router using the same chipset works with 272 byte file no problem? Jun 30 18:11:08 probably came with nbd's latest mac80211 update Jun 30 18:11:49 a-ha! 37105 Jun 30 18:12:51 let's see if I learned how to make kernel patches.. Jun 30 18:22:29 can I submit? Jun 30 18:26:57 jesus, I'm so dumb.. it's not the kernel I have to patch, it's 10-rt2x00-eeprom :| Jun 30 18:55:13 blogic: i sent a new patch to the ml to add fs_check functionality to block, it also removes a newline from a printf i missed on my last patch Jun 30 18:55:25 blogic: http://paste.debian.net/13436/ Jun 30 19:38:53 Hi all, I have an openwrt image running on a new board, It runs fine until the failsafe prompt... Jun 30 19:39:56 after that I see 3 log lines for ip tables, NET: registered protocol family 24 and a nf_conntrack version 0.5.0 just before my device reboots... Jun 30 19:40:16 (I do see a partial logline with only a timestamp) Jun 30 19:40:30 What can I do to find out what causes the crash? Jun 30 19:51:23 The_Lizard: go to failsafe, the manually insmod modules until you hit the one triggering the reset Jun 30 20:04:02 tripolar: please remind me tomorrow, I'm on a flaky gprs connection right now Jun 30 20:04:34 tripolar: a /msg will be fine in 10-12 hours Jun 30 20:07:39 nbd just for you to know, it works Jun 30 20:08:25 but 10-rt2x00-eeprom needs to be patched, change offset 272 to 512 and done hehe Jun 30 20:09:07 Kaloz: okay Jun 30 20:29:15 nbd r37110 trunk/package/ (27 files in 2 dirs) * hostapd: update to latest git version Jun 30 20:37:25 KanjiMonster: How do I know which modules have to be loaded? Jun 30 20:38:57 The_Lizard: /etc/moduled-boot.d and /etc/modules.d/ - these are text files with the module names in it, they are evaluated in alphabetical order Jun 30 20:48:58 I'm close to a successful port, just want to thank you all for time and patience, I've learned a lot during this process Jun 30 20:54:26 KanjiMonster: I don't have a moduled-boot.d, and i don't seem to be able to see the contents of /etc/modules.d (tried less /etc/modules.d Jun 30 20:54:54 modules-boot.d Jun 30 20:55:17 isn't there (I already assumed it was a typo) Jun 30 20:55:50 which target is this? Jun 30 20:56:04 VGV7519, a mips Jun 30 20:56:26 hum, I don't know, sorry Jun 30 20:56:31 http://wiki.openwrt.org/toh/arcadyan/vgv7519 Jun 30 20:59:34 it's lantiq, never played with one of those.. Jun 30 21:00:38 apparently... the modules.d is a directory... ;) Jun 30 21:01:50 yes, and modules-boot.d too Jun 30 21:02:37 There really is no modules-boot.d Jun 30 21:02:49 nbd r37111 trunk/package/ (7 files) * hostapd: fix multi-ssid and AP+STA, clean up code Jun 30 21:03:20 I have called insmod on all the files in modules.d, but none gives any output (or crashes my target) Jun 30 21:05:02 ah, I see that I have to remove the numbered prefix... Jun 30 21:05:24 nbd r37112 trunk/target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom * ramips: update wlan firmware hotplug script for new eeprom size Jun 30 21:05:37 yay! thanks! Jun 30 21:07:46 nbd before 37110 20 Mbit/s download, with 37110 12 Mbit/s, will try 37111 in a sec Jun 30 21:08:26 download over what? Jun 30 21:08:49 tp-link wr740n v4.26, wireless ht20, 2 meters Jun 30 21:09:23 is it possible to insmod all the entries from a /modules.d/ file at once? Jun 30 21:09:51 regular ap mode? Jun 30 21:10:06 The_Lizard there must be something in /etc/init.d to do that Jun 30 21:10:13 yep Jun 30 21:10:29 psk2, 1 client with iwl3945 Jun 30 21:11:58 hm, i don't see any throughput difference between pre-37110 and post-37110 Jun 30 21:12:02 on my tl-mr3020 Jun 30 21:12:17 compiling 37112 now Jun 30 21:13:07 I can't keep up with the speed of the changes, 10 changesets in... 2 hours? hehe Jun 30 21:13:18 Loaded all modules, but device didn't crash up on me, what is the next phase in booting? Jun 30 21:13:25 dape: if that still shows low throughput, then please double check the old version Jun 30 21:13:35 i don't see how the hostapd change could affect throughput in this way Jun 30 21:30:40 16 Mbit/s now Jun 30 21:31:31 14-16 but it's no biggie anyway, could be this laptop old intel wireless chip Jun 30 21:31:58 probably a measurement error Jun 30 21:32:26 unless you can consistently reproduce the throughput difference Jun 30 21:33:17 i'm gonna try tomorrow on a wndr3800 and a wdr3600 Jun 30 21:40:20 KanjiMonster: It isn't any of the kernel modules, it crashes after that... Jun 30 21:44:27 nbd seems okay now, 18-20 Mbit/s on this wr740n, i just lifted the router from the floor on a chair :P Jun 30 23:58:45 build #279 of ar7 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/279 Jul 01 00:11:00 I just have a few things to finish up: wireless mac address (does it get from eeprom file?), ethernet port leds are always lit, but blinks correctly, wps button led, reset button Jul 01 00:11:29 I don't know if openwrt has some gpio tool to do tests Jul 01 00:35:57 build #237 of mcs814x is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/237 Jul 01 00:38:16 build #241 of adm5120 is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/241 Jul 01 00:40:48 build #324 of brcm63xx is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/324 Jul 01 00:43:24 build #319 of at91 is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/319 Jul 01 00:46:03 build #313 of brcm47xx is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/313 Jul 01 00:48:29 build #307 of atheros is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/307 Jul 01 00:50:47 build #297 of cobalt is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/297 Jul 01 00:53:23 build #309 of orion is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/309 Jul 01 00:55:41 build #298 of lantiq is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/298 Jul 01 00:57:53 build #298 of ramips is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/298 Jul 01 01:04:20 build #277 of rb532 is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/277 Jul 01 01:10:41 build #277 of ppc44x is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/277 Jul 01 01:17:38 build #291 of uml is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/291 Jul 01 01:17:47 build #296 of ppc40x is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/296 Jul 01 01:20:00 build #280 of ar7 is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/280 Jul 01 01:22:54 build #263 of sibyte is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/263 Jul 01 01:25:45 build #273 of avr32 is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/273 Jul 01 01:28:24 build #265 of xburst is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/265 Jul 01 01:29:14 build #281 of x86 is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/281 Jul 01 01:31:19 build #264 of ixp4xx is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/264 Jul 01 01:32:08 build #263 of kirkwood is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/263 Jul 01 01:33:49 build #257 of ar71xx is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/257 Jul 01 01:34:50 build #258 of au1000 is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/258 Jul 01 01:36:20 build #224 of mpc52xx is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/224 Jul 01 01:37:18 build #210 of octeon is complete: Failure [failed shell_10 compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/210 **** ENDING LOGGING AT Mon Jul 01 02:59:58 2013