**** BEGIN LOGGING AT Wed Jul 24 02:59:59 2013
**** BEGIN LOGGING AT Wed Jul 24 05:27:42 2013
Jul 24 05:57:04 <builder> build #297 of rb532 is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/297
Jul 24 05:59:54 <builder> build #297 of ppc44x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/297
Jul 24 06:03:23 <builder> build #318 of cobalt is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/318
Jul 24 06:53:41 <builder> build #311 of uml is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/311
Jul 24 08:56:42 <OpenWrt-Commits> blogic r37521 trunk/target/linux/ramips/ (12 files in 8 dirs)
Jul 24 08:56:42 <OpenWrt-Commits> ramips: Basic support for the AsiaRF RT5350 based AWM002 module and evaluation board.
Jul 24 08:58:11 <tripolar> hi
Jul 24 08:58:15 <tripolar> when i'd like to debug a prog with gdb - i folloed this guid
Jul 24 08:58:25 <tripolar> http://wiki.openwrt.org/doc/devel/gdb
Jul 24 08:58:50 <tripolar> but it seems compiling just the program with make package/busybox/{clean,compile} V=99 CONFIG_DEBUG=y doesnt work as a lot of symbols are missing
Jul 24 08:59:24 <tripolar> can i compile a complete image and flash it directly to get all symbols resolved?
Jul 24 08:59:36 <jow_laptop> I suggest to use gdbserver
Jul 24 08:59:45 <jow_laptop> this way you do not need any unstripped binaries on the target
Jul 24 08:59:50 <tripolar> jow_laptop: i am but symbols are missing from uclibc
Jul 24 08:59:55 <tripolar> all of them
Jul 24 09:00:03 <jow_laptop> they you did it wrong
Jul 24 09:00:19 <tripolar> because i didnt compile the how image with " Compile packages with debugging info"
Jul 24 09:00:20 <jow_laptop> use scripts/remote-gdb, this will setup the sysroot accordingly so that gdb can resolve librariy symbols
Jul 24 09:00:33 <jow_laptop> you don't need a complete image with debug info to resolve symbols in libc
Jul 24 09:01:09 <tripolar> jow_laptop: so i jsut have to compile the program id like to debug with debug symbols?
Jul 24 09:01:16 <jow_laptop> right
Jul 24 09:01:25 <jow_laptop> also make sure that the image you run is identical to you buildroot env
Jul 24 09:01:40 <jow_laptop> otherwise library memory locations will not match and gdb cannot resolve symbols
Jul 24 09:02:02 <jow_laptop> so in doubt reflash to a just produced image before you start debugging
Jul 24 09:02:40 <jow_laptop> if it does not work from the get-go its likely a library version / abi mismatch and you do not need to try anything further
Jul 24 09:03:32 <tripolar> jow_laptop but can i flash a image that is compiled with " Compile packages with debugging info"
Jul 24 09:03:55 <tripolar> or should i compile it normally and afterwards recompile the prog i want to debug?
Jul 24 09:04:35 <jow_laptop> normally
Jul 24 09:04:43 <jow_laptop> in my experience debug images do not even boot
Jul 24 09:05:17 <tripolar> okay to know because im working remote :)
Jul 24 09:05:23 <tripolar> okay good to know because im working remote :)
Jul 24 09:05:40 <tripolar> thanks for your help
Jul 24 09:06:55 <Pteridium> blogic, KanjiMonster: was my fault. i had compiled the toolchain with "Compile in support for the new Graphite framework in GCC 4.4+". Without this option there are no problems.
Jul 24 09:06:59 <tripolar> jow_laptop: and can i login with my dev.openwrt.org user into the wiki to change text?
Jul 24 09:07:09 <Pteridium> Didn't realized, sorry...
Jul 24 09:07:55 <blogic> Pteridium: fiddleing with the gcc settings is not a good idea ;)
Jul 24 09:08:11 <blogic> Pteridium: nonetheless we will see about fixing the deadcode thing on 63xx
Jul 24 09:08:18 <blogic> so at least we foun that bug
Jul 24 09:09:07 <tripolar> jow_laptop is the gdb client on the host compiled by default?
Jul 24 09:10:10 <Pteridium> no, wasn't deadc0de problem.
Jul 24 09:11:24 <Pteridium> only a toolchain option that sometimes can give problems
Jul 24 09:12:32 <Pteridium> to summarize: to test and port a new board mark the default and safe options
Jul 24 09:14:46 <blogic> yes
Jul 24 09:14:53 <blogic> but the deacode stuff should still be fixed
Jul 24 09:15:58 <KanjiMonster> blogic: I'm still not convinced this issue isn't caused by a gcc miscompilation
Jul 24 09:18:35 <Pteridium> KanjiMonster: made the compilation with SMP; with a bcm6328 and the Graphite option marked all works fine
Jul 24 09:19:48 <KanjiMonster> Pteridium: maybe it's a SMP problem? have you tried what happends if you limit the number of cpus to 1?
Jul 24 09:20:07 <Pteridium> still not
Jul 24 09:20:27 <Pteridium> i'll made this tep later
Jul 24 09:20:31 <Pteridium> step*
Jul 24 09:21:25 <KanjiMonster> (adding maxcpus=1 to the command line should do the trick)
Jul 24 09:23:34 <Pteridium> ok. Give me a moment to send to seguridadwireless forum a working image
Jul 24 09:23:53 <Pteridium> i'll keep you informed
Jul 24 09:27:24 <builder> build #281 of sibyte is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/281
Jul 24 09:45:31 <dape> guys i need some advices please, i got the ZTE h218n ( http://wwwen.zte.com.cn/en/products/access/cpe/201111/t20111110_352102.html ) and i have telnet access on it, i even managed to compile some packages from openwrt 8.09 and move on its flash and run them with LD_LIBRARY_PATH
Jul 24 09:46:19 <dape> but it seems i cannot get more than 30 Mbit/s via wget -O /dev/null on it, the routing through it seems fine, i get 90 Mbit
Jul 24 09:46:41 <dape> its chinese firmware runs a 2.6.21.5 kernel, could this be the problem?
Jul 24 09:47:29 <dape> i'm interested in finding a method to bandwidth test on the box with its current firmware and whatever i can extract from openwrt 8.09 and run on it
Jul 24 09:48:37 <dape> from /proc/cpuinfo i see system type 947xxGR and cpu model MIPS 74k v4.9, it has 64 mb ram and i suspect 20 mb flash
Jul 24 10:10:56 <OpenWrt-Commits> jow r37522 trunk/package/system/ubox/Makefile * ubox: update to git head
Jul 24 10:17:00 <builder> build #283 of xburst is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/283
Jul 24 10:30:16 <champtar> Someone for authsae patches :
Jul 24 10:30:16 <champtar> http://patchwork.openwrt.org/patch/3711/
Jul 24 10:30:16 <champtar> http://patchwork.openwrt.org/patch/3845/
Jul 24 10:30:16 <champtar> http://patchwork.openwrt.org/patch/3847/
Jul 24 10:30:16 <champtar> It's fully fonctional with AR9220 (need nohwcrypt=1 for AR9100, i've sended a mail to linux-wireless for this bug)
Jul 24 10:57:27 <blogic> champtar: hmmm
Jul 24 10:57:37 <blogic> we are currently not adding any new packages to the packages/ feed
Jul 24 10:58:31 <champtar> blogic: why? and it's the core (trunk/package/...)
Jul 24 10:58:32 <blogic> so you need to find someone that will merge it to trunk
Jul 24 10:58:59 <blogic> champtar: adding it to trunk means a openwrt core dev needs to claim maintainership for the package
Jul 24 10:59:23 <blogic> and as for the packages feed ... there are 1000+ packages in their rotting away that are not maintained
Jul 24 10:59:32 <blogic> so we are not adding any new ones at the moment
Jul 24 10:59:39 <blogic> we are working on a new policy how to handle this
Jul 24 11:00:01 <blogic> but for now you will need to find a core developer to claim mainatinership or it wont get merged
Jul 24 11:00:15 <blogic> this was also all explained in the AA announce email
Jul 24 11:03:15 <champtar> ok, but for the authsae case, openwrt is about wireless, and authsae is for secured mesh, so it's really a feature that openwrt must have
Jul 24 11:04:20 <blogic> :58 < blogic> champtar: adding it to trunk means a openwrt core dev needs to claim maintainership for the package
Jul 24 11:04:47 <blogic> this is for 11s ?
Jul 24 11:04:51 <champtar> yes
Jul 24 11:04:55 <blogic> who uses 11s ?
Jul 24 11:05:03 <blogic> just curious
Jul 24 11:05:20 <blogic> i was under the impression, that olpc showed that 11s is disfunctional with more than say 5 nodes
Jul 24 11:06:29 <champtar> i don't know who use 11s but many won't use it because it's not encryted
Jul 24 11:07:34 <blogic> so for those reasons i dont see it as being a "must have" for owrt
Jul 24 11:08:02 <blogic> and because of this it cannot be classified in importance similar to hostapd for example
Jul 24 11:08:16 <blogic> and hence you need to find a dev that will sponsor it and claim maintainership
Jul 24 11:08:28 <blogic> and i think it will be hard to find that person right now
Jul 24 11:08:45 <blogic> we will soon have a new policy for none core developers being maintainers in feeds
Jul 24 11:08:59 <blogic> once that policy is in place we can add your package to that feed i guess
Jul 24 11:11:14 <champtar> blogic: you don't need to say 3 time that i need a core developper, i've understand it the first time :)
Jul 24 11:11:16 <champtar> I don't think this can be in feeds because it must be integrated with mac80211.sh
Jul 24 11:11:55 <blogic> in that case oyu need to convine felix
Jul 24 11:12:06 <blogic> *convince
Jul 24 11:12:19 <nbd> i'll take a look
Jul 24 11:12:28 <champtar> cool
Jul 24 11:13:49 <nbd> can you change it to use libnl-tiny instead of libnl?
Jul 24 11:14:04 <nbd> since libnl-tiny is already used by the base system and is much smaller
Jul 24 11:14:50 <champtar> i've read somewhere that it work, i'll give a try
Jul 24 11:15:10 <nbd> you need to adjust the cflags accordingly
Jul 24 11:16:58 <champtar> ok, any other problems (mac80211.sh patch?)
Jul 24 11:17:49 <nbd> i'll review that stuff in a few minutes
Jul 24 11:17:55 <blogic> nbd: thx
Jul 24 11:17:56 <nbd> i think i'll start by pulling in the elliptic curve crypto patch
Jul 24 11:18:08 <nbd> but i'll change the default to enabled, because there were people requesting EC support also for things like strongswan
Jul 24 11:18:44 <jow_laptop> how much size does it add?
Jul 24 11:19:24 <nbd> ~35k ipk size increase
Jul 24 11:19:25 <jow_laptop> luckily we have cyassl alternatives for various crypto using services already so openssl size changes are not as severe as in the past
Jul 24 11:19:32 <jow_laptop> hm, that is significant
Jul 24 11:19:42 <nbd> it's not that much relative to openssl total size
Jul 24 11:19:45 <jow_laptop> true
Jul 24 11:19:47 <blogic> 5-7k after lzma
Jul 24 11:19:54 <nbd> blogic: more
Jul 24 11:19:57 <blogic> sure ?
Jul 24 11:19:58 <nbd> it's 35k after gzip
Jul 24 11:20:01 <blogic> ahhhh
Jul 24 11:20:13 <blogic> ipk increase .... sorry misread
Jul 24 11:20:18 <blogic> then its a lot
Jul 24 11:20:35 <nbd> openssl is already 627k gzipped
Jul 24 11:20:47 <nbd> so ~5% increase is not that much
Jul 24 11:24:49 <nbd> champtar: the mac80211.sh changes look ok
Jul 24 11:47:00 <builder> build #330 of orion is complete: Failure [failed compile_8]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/330
Jul 24 11:52:22 <tripolar> jow_laptop: i compiled a new image flashed it and i still get
Jul 24 11:52:25 <tripolar> Reading symbols from /mnt/data/Develop/Openwrt/trunk_git/staging_dir/target-mips_r2_uClibc-0.9.33.2/root-ar71xx/usr/bin/rtorrent...done.
Jul 24 11:52:28 <tripolar> 0x77fe0f60 in ?? () from /mnt/data/Develop/Openwrt/trunk_git/scripts/../staging_dir/target-mips_r2_uClibc-0.9.33.2/root-ar71xx/lib/ld-uClibc.so.0
Jul 24 11:54:56 <jow_laptop> tripolar: did you use remote-gdb ?
Jul 24 11:57:42 <tripolar> i used gdbserver on the device
Jul 24 11:58:03 <jow_laptop> and remote-gdb in your tree?
Jul 24 11:58:04 <tripolar> as it doesnt allow rewote connecitons as it seems i used ssh to forward the port
Jul 24 11:58:14 <tripolar> and ./scripts/remote-gdb on the host
Jul 24 11:58:25 <jow_laptop> then put the complete output into pastebin
Jul 24 11:59:38 <tripolar> jow_laptop: i compiled a new image i will flash it and post the output afterwards
Jul 24 11:59:44 <tripolar> be back in few minutes
Jul 24 12:10:41 <tripolar> jow_laptop: http://paste.debian.net/18231/
Jul 24 12:11:04 <jow_laptop> tripolar: build_dir
Jul 24 12:11:12 <jow_laptop> all binaries in staging_dir are stripped
Jul 24 12:11:32 <jow_laptop> ./scripts/remote-gdb 127.0.0.1:9000 ./build_dir/target-mips_r2_uClibc-0.9.33.2/rtorrent-*/rtorrent
Jul 24 12:13:40 <tripolar> jow_laptop: still http://paste.debian.net/18232/
Jul 24 12:14:47 <tripolar> src/rtorrent seems to be unstipped
Jul 24 12:14:51 <tripolar> unstripped
Jul 24 12:14:52 <tripolar> -rwxr-xr-x 1 tux users 834K 24. Jul 13:47 ./build_dir/target-mips_r2_uClibc-0.9.33.2/rtorrent-0.9.2/ipkg-ar71xx/rtorrent/usr/bin/rtorrent
Jul 24 12:14:55 <tripolar> -rwxr-xr-x 1 tux users  27M 24. Jul 13:47 ./build_dir/target-mips_r2_uClibc-0.9.33.2/rtorrent-0.9.2/src/rtorrent
Jul 24 12:16:23 <tripolar> jow_laptop: any idea why it doesnt work?
Jul 24 12:16:30 <jow_laptop> no, it works ootb for me
Jul 24 12:16:45 <tripolar> should i copy over the unstripped rtorrent to the device?
Jul 24 12:16:46 <jow_laptop> did you consider a missing dynamic library?
Jul 24 12:16:57 <tripolar> could be libtorrent
Jul 24 12:17:07 <jow_laptop> because even without debug ld-uClibc.so.0 I see symbols
Jul 24 12:17:36 <jow_laptop> http://paste.debian.net/18234/
Jul 24 12:19:14 <jow_laptop> and no, there is no need to copy over the debug binary
Jul 24 12:20:35 <jow_laptop> but you don't use mklibs or something?
Jul 24 12:21:33 <tripolar> mklibs?
Jul 24 12:21:39 <tripolar>    from /mnt/data/Develop/Openwrt/trunk_git/scripts/../staging_dir/target-mips_r2_uClibc-0.9.33.2/root-ar71xx/lib/ld-uClibc.so.0
Jul 24 12:22:00 <tripolar> for ping i get
Jul 24 12:22:01 <tripolar> 0x77fe0f60 in ?? () from /mnt/data/Develop/Openwrt/trunk_git/scripts/../staging_dir/target-mips_r2_uClibc-0.9.33.2/root-ar71xx/lib/ld-uClibc.so.0
Jul 24 12:22:13 <tripolar> what could be the problem?
Jul 24 12:22:26 <tripolar> i create a complete new image
Jul 24 12:22:56 <tripolar> even cleaned staging_dir and build_dir
Jul 24 12:22:56 <jow_laptop> run "info sharedlibrary" in the gdb console
Jul 24 12:23:03 <jow_laptop> for me it reads:
Jul 24 12:23:18 <jow_laptop> (gdb) info sharedlibrary
Jul 24 12:23:18 <jow_laptop> From        To          Syms Read   Shared Object Library
Jul 24 12:23:18 <jow_laptop> 0x77fe0e90  0x77fe6880  Yes (*)     /home/jow/devel/openwrt.git/scripts/../staging_dir/target-mips_r2_uClibc-0.9.33.2/root-ar71xx/lib/ld-uClibc.so.0
Jul 24 12:23:31 <tripolar> info sharedlibrary
Jul 24 12:23:31 <tripolar> From        To          Syms Read   Shared Object Library
Jul 24 12:23:31 <tripolar> 0x77fe0e90  0x77fe6880  No          /mnt/data/Develop/Openwrt/trunk_git/scripts/../staging_dir/target-mips_r2_uClibc-0.9.33.2/root-ar71xx/lib/ld-uClibc.so.0
Jul 24 12:23:45 <jow_laptop> put ./scripts/diffconfig.sh into pastebin
Jul 24 12:25:12 <jow_laptop> maybe its a C++ specific problem, idk
Jul 24 12:25:20 <tripolar> http://paste.debian.net/18236/
Jul 24 12:26:09 <tripolar> jow_laptop but busybox looks the same as rtorrent
Jul 24 12:26:09 <tripolar> i mean the output
Jul 24 12:26:09 <tripolar> should i recompile uclibc with debug symbols?
Jul 24 12:30:55 <tripolar> jow_laptop: did you see the link?
Jul 24 12:33:42 <tripolar> nbd: hi, do you know what i could do when i get  0x77fe0f60 in ?? () from /mnt/data/Develop/Openwrt/trunk_git/scripts/../staging_dir/target-mips_r2_uClibc-0.9.33.2/root-ar71xx/lib/ld-uClibc.so.0
Jul 24 12:33:48 <tripolar> in remote-gdb
Jul 24 12:34:02 <nbd> as you said, compile uclibc with debug symbols
Jul 24 12:34:07 <nbd> we should probably enable that by default
Jul 24 12:34:45 <nbd> at least the part that affects the cflags
Jul 24 12:34:49 <nbd> not the general debugging stuff
Jul 24 12:36:31 <nbd> i'll look into that
Jul 24 12:38:14 <tripolar> nbd: when i recompiled uclibc do i have to reflash the router? or can i just reinstall it?
Jul 24 12:38:23 <tripolar> i'm on sd-ext
Jul 24 12:38:28 <tripolar> -sd
Jul 24 12:39:08 <tripolar> nbd: when i recompiled uclibc do i have to reflash the router? or can i restart the gdb and use the newly compiled lib
Jul 24 12:39:23 <nbd> if you enabled it via the existing Kconfig option, you need to reinstall it
Jul 24 12:39:28 <nbd> becaues that one affects more than just the compile flags
Jul 24 12:39:54 <OpenWrt-Commits> nbd r37523 trunk/package/ libs/openssl/Config.in libs/openssl/Makefile * openssl: add elliptic curve crypto compilation options to openssl
Jul 24 12:39:58 <OpenWrt-Commits> nbd r37524 trunk/package/libs/openssl/Config.in
Jul 24 12:39:58 <OpenWrt-Commits> openssl: enable elliptic curve crypto by default (so that it can be used by things like ipsec as well)
Jul 24 12:40:01 <OpenWrt-Commits> nbd r37525 trunk/toolchain/uClibc/common.mk
Jul 24 12:40:02 <OpenWrt-Commits> uClibc: build with debug symbols by default (without changing other compile related flags)
Jul 24 12:40:35 <tripolar> nbd: quick fix thanks
Jul 24 12:41:33 <tripolar> nbd: how do i just recompule uclibc? make toolchain/uClibc/{clean,compile} ?
Jul 24 12:46:01 <tripolar> jow_laptop: do you how to clean just uclibc
Jul 24 12:48:09 <jow_laptop> you need to rebuidl the toolchain
Jul 24 12:51:13 <tripolar> okay thanks
Jul 24 12:53:26 <tripolar> jow_laptop, nbd thanks for your help
Jul 24 13:04:13 <OpenWrt-Commits> nbd r37526 trunk/package/libs/libubox/Makefile * libubox: update to latest version, includes a small uloop fix
Jul 24 14:27:05 <Pteridium> blogic, KanjiMonster: the rootfs_data issue is not related with SMP. With a basic image (Luci and something more) seems to work fine. Maybe is caused by a package?
Jul 24 14:29:16 <Pteridium> http://pastebin.com/jWj77GrH
Jul 24 16:28:24 <The_Lizard> blogic: ping
Jul 24 16:28:52 <The_Lizard> I've updated the bootlog...
Jul 24 16:29:44 <blogic> ok
Jul 24 16:29:56 <blogic> i just tested on a easy80902 and ti works
Jul 24 16:30:17 <The_Lizard> ok, but apparently it uses another firmware right?
Jul 24 16:30:19 <blogic> show me your dts file please
Jul 24 16:30:29 <blogic> i tested on a v1.2 and v1.1
Jul 24 16:30:36 <blogic> and i testedt FE and GE firmwaes
Jul 24 16:30:41 <blogic> i tested all 4 and all 4 work
Jul 24 16:31:07 <The_Lizard> where do FE and GE stand for?
Jul 24 16:31:39 <blogic> Fast Ethernet (100mbit)
Jul 24 16:31:47 <blogic> Gbit Ethernet (1000mbit)
Jul 24 16:31:55 <blogic> you have 2 internal phys
Jul 24 16:31:58 <blogic> each loads a firmware
Jul 24 16:32:10 <blogic> either a single port gbit or a dual port 100mbit
Jul 24 16:32:34 <blogic> so you can have 2 * gbit or 4 * 100mbit ports
Jul 24 16:32:52 <The_Lizard> ok, thanks
Jul 24 16:33:06 <The_Lizard> I assume I have the gigabit images?
Jul 24 16:33:24 <blogic> yes
Jul 24 16:33:30 <blogic> show me your full dts file please
Jul 24 16:34:30 <blogic> i ported 2 new baord with vr9 today and it works
Jul 24 16:34:35 <blogic> do all ports fail or just some
Jul 24 16:35:11 <blogic> and when oyu plug a cable do you see "[    4.728000] eth0: port 4 got link
Jul 24 16:36:02 <The_Lizard> http://pastebin.com/wjJA98uc
Jul 24 16:36:52 <The_Lizard> In the bootlog, it is at 4.272000
Jul 24 16:37:51 <The_Lizard> I guess all ports fail... but haven't tested that lately
Jul 24 16:38:01 <The_Lizard> could it be due to firewall settings?
Jul 24 16:38:05 <blogic> no
Jul 24 16:38:15 <The_Lizard> should DHCP work?
Jul 24 16:38:55 <The_Lizard> The weird thing is that the tftp stuff works in my u-boot
Jul 24 16:39:00 <The_Lizard> * afk for dinner *
Jul 24 16:55:01 <The_Lizard> * back &
Jul 24 16:59:31 <The_Lizard> none of the ports work (tried ping from and to host computer
Jul 24 16:59:48 <OpenWrt-Commits> nbd r37527 trunk/ package/libs/polarssl/Makefile package/libs/polarssl/patches/310-fix_blowfish_key_len.patch package/libs/polarssl/patches/300-openssl_cipher_name_compat.patch package/libs/polarssl/patches/200-reduce_config.patch * polarssl: update to version 1.2.8
Jul 24 16:59:51 <OpenWrt-Commits> nbd r37528 trunk/package/libs/ustream-ssl/Makefile
Jul 24 16:59:52 <OpenWrt-Commits> ustream-ssl: update to latest version, add a package for the polarssl build variant
Jul 24 17:00:10 <The_Lizard> after plugging in the cable, it reports br-lan port x (eth0) entered forwarding state 3 times... ain't that weird?
Jul 24 17:01:09 <Pteridium> this report, afaik, is normal in XWAY target
Jul 24 17:01:19 <The_Lizard> ok
Jul 24 17:01:42 <The_Lizard> how do I configure the correct mac addresses?
Jul 24 17:02:43 <Pteridium> should be in the flash, no?
Jul 24 17:02:54 <The_Lizard> I have overwritten 'everything'
Jul 24 17:03:09 <The_Lizard> so should I configure it in u-boot, and passing it as arguments?
Jul 24 17:03:57 <Pteridium> could be an option...
Jul 24 17:04:27 <The_Lizard> I have seen something about UCI? is it possible through that method?
Jul 24 17:04:54 <Pteridium> no idea, sorry :(
Jul 24 17:09:43 <Pteridium> have you added your board in (owrt_dir)/target/lantiq/base files/uci-defaults/02_network? By default the ethernet ports are configured in eth0, but your router could has them in eth1
Jul 24 17:10:45 <The_Lizard> didn't change anything there...
Jul 24 17:10:52 <The_Lizard> didn't know anything existed over there
Jul 24 17:12:53 <The_Lizard> lets try something...
Jul 24 17:12:54 <Pteridium> another option could be edit /etc/config/network and add eth1
Jul 24 17:13:07 <The_Lizard> eth1 should be my wan config...
Jul 24 17:13:49 <The_Lizard> should I re-flash my device after changing the uci file?
Jul 24 17:14:45 <DonkeyHotei> Devastator: do you get 11n speeds on the rt5350?
Jul 24 17:15:23 <Pteridium> The_Lizard: no
Jul 24 17:15:36 <Devastator> my device is not officially supported, so I couldn't test wireless n yet
Jul 24 17:16:06 <DonkeyHotei> if you can boot a build, you can test it
Jul 24 17:16:17 <Pteridium> once edited /etc/config/wireless run /etc/init.d/network restart
Jul 24 17:17:54 <Pteridium> or reboot the router
Jul 24 17:25:12 <The_Lizard> any idea what I should place into the network configuration?
Jul 24 17:25:16 <The_Lizard> or some docs?
Jul 24 17:27:29 <Pteridium> no idea in this moment, sorry :(
Jul 24 17:37:58 <The_Lizard> Pteridium: any idea what the 't' does in the switch_vlan line?
Jul 24 17:38:44 <blogic> its the trunk port
Jul 24 17:38:51 <The_Lizard> trunk?
Jul 24 17:39:08 <blogic> google ? :)
Jul 24 17:39:34 <Pteridium> the port attached to the SoC?
Jul 24 17:39:39 <KanjiMonster> t = preserve tag
Jul 24 17:39:54 <KanjiMonster> (802.1q VLAN tag)
Jul 24 17:39:56 <Pteridium> ok, tagged
Jul 24 17:40:51 <The_Lizard> KanjiMonster: do you have any idea what I should be making of the uci-defaults? (network configuration)
Jul 24 17:41:13 <The_Lizard> I have no idea what the numbers stand for..
Jul 24 17:41:34 <KanjiMonster> which numbers?
Jul 24 17:41:50 <The_Lizard> the things after ucidef_add_switch and *_add_switch_vlan
Jul 24 17:42:05 <The_Lizard> I have 2 'interfaces' in my dts files, lan and wan
Jul 24 17:42:12 <blogic> The_Lizard: ?
Jul 24 17:42:24 <The_Lizard> yes?
Jul 24 17:42:27 <blogic> what do you need vlans for ?
Jul 24 17:42:42 <blogic> you have 2 interfaces
Jul 24 17:42:51 <blogic> they are there so you dont need vlans
Jul 24 17:42:54 <The_Lizard> I have no idea, but Pteridium pointed me towards the uci-defaults
Jul 24 17:43:01 <blogic> Pteridium: buh
Jul 24 17:43:03 <The_Lizard> ok, so I don't need to adjust this file?
Jul 24 17:43:08 <blogic> The_Lizard: ignore him ;)
Jul 24 17:43:09 <blogic> no
Jul 24 17:43:24 <blogic> that file is not the reason for your problem
Jul 24 17:43:28 <blogic> did you try all ports ?
Jul 24 17:43:30 <The_Lizard> cool, I was already wondering why the easy80920 boards weren't there
Jul 24 17:43:35 <The_Lizard> yes, but none worked
Jul 24 17:44:04 <The_Lizard> tried to ping from and to host computer
Jul 24 17:44:12 <The_Lizard> should DHCP work already?
Jul 24 17:45:33 <The_Lizard> Is there anything I can try now?
Jul 24 17:46:06 <Pteridium> blogic: could be the lan interface in eth1?
Jul 24 17:49:44 <The_Lizard> blogic: is there anything I can do?
Jul 24 18:12:08 <Devastator> DonkeyHotei I'm currently porting the device, so I'm running initramfs builds, still have to figure out ethernet switch led polarity and wireless mac address
Jul 24 18:12:51 <DonkeyHotei> Devastator: did you read what i wrote about the device i tried? https://lists.openwrt.org/pipermail/openwrt-devel/2013-July/020765.html
Jul 24 18:13:13 <Devastator> not really, reading now
Jul 24 18:14:01 <DonkeyHotei> i built initramfs only too
Jul 24 18:15:01 <DonkeyHotei> i may deploy the device with stock fw for now
Jul 24 18:15:32 <DonkeyHotei> i will know more within the hour about whether i will need to do that
Jul 24 18:15:50 <Devastator> I didn't have time to write to the list, I want to ask those questions there and with luck, port this device fully
Jul 24 18:16:46 <DonkeyHotei> if all 3 devices are having the eth led issue, it's likely a chip support thing
Jul 24 18:17:10 <DonkeyHotei> mac address is correct in my test
Jul 24 18:17:32 <Devastator> I don't know for sure, but you are probably right
Jul 24 18:17:55 <Devastator> the port cable is plugged when image boots remains off, the others lit
Jul 24 18:18:40 <Devastator> it's likely inverse polarity, but I don't know how to test after it boots
Jul 24 18:25:00 <OpenWrt-Commits> jow r37529 trunk/package/system/ubox/Makefile * ubox: update to git head
Jul 24 18:26:39 <The_Lizard> blogic: ?
Jul 24 18:27:37 <The_Lizard> would it help if you had console access to my device?
Jul 24 18:27:51 <The_Lizard> i could let you access my computer...
Jul 24 18:59:18 <champtar1> nbd: authsae compiling/linking with libnl-tiny http://patchwork.openwrt.org/patch/3851/
Jul 24 19:01:22 <builder> build #253 of iop32x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/253
Jul 24 19:14:05 <builder> build #224 of octeon is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/224
Jul 24 19:41:04 <champtar1> nbd: wait a bit, my patch got merged in authsae git, i'will send a new patch
Jul 24 20:05:26 <builder> build #256 of ep93xx is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/256
Jul 24 20:08:57 <written_direcon> anyone can help me to configure routing guest-wlan traffic over a openvpn tunnel?
Jul 24 20:26:58 <The_Lizard> * back *
Jul 24 20:32:16 <KanjiMonster> written_direcon: wrong channel
Jul 24 20:54:01 <written_direcon> haha, KanjiMonster :-(
Jul 24 20:54:20 <blogic> written_direcon: he did not make a joke
Jul 24 21:21:01 <The_Lizard> blogic: do you have other ideas about what might be wrong?
Jul 24 21:21:20 <blogic> The_Lizard: how often do you plan o ask that question and/or email me it ?
Jul 24 21:21:23 <blogic> ;)
Jul 24 21:21:43 <The_Lizard> I haven't got an answer, not even an I don't know...
Jul 24 21:22:22 <blogic> i dont know
Jul 24 21:22:52 <The_Lizard> ok, thanks for the help...
Jul 24 21:57:59 <KanjiMonster> The_Lizard: mailing questions to developers privately is usually considered bad etiquette
Jul 24 22:00:40 <The_Lizard> I'm sorry, blogic told me he would test a kernel on a EASY80920 board, I had asked here a few times, but never got a response, so mailed him if he had time to test it out...
Jul 24 22:01:50 <The_Lizard> I don't want to be a pain in the ass, I tought he could help me further, but instead of just telling me, he didn't respond to questions...
Jul 24 22:04:52 <The_Lizard> Any idea what I should do to get my board running? otherwise I will just flash the original firmware back and quit the experiment...
**** ENDING LOGGING AT Thu Jul 25 02:59:58 2013