**** BEGIN LOGGING AT Sat Aug 03 03:00:00 2013
Aug 03 05:34:47 <builder> build #329 of lantiq is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/329
Aug 03 07:08:36 <russell--> anybody here from paris?
Aug 03 07:11:51 <MartijnVdS> russell--: Amsterdam close enough?
Aug 03 07:14:02 * russell-- wants a couple dozen of these: http://www.eden-market.fr/1220-1587-thickbox/soya-cake-banh-tan-tan-80g.jpg
Aug 03 07:14:24 <russell--> they won't ship to the US (they have a fairly brief shelf life)
Aug 03 07:14:55 * russell-- will probably have to go collect them in person ;-)
Aug 03 08:03:53 <builder> build #301 of avr32 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/301
Aug 03 08:07:56 <MartijnVdS> russell--: do you know who I have to talk to about my patch (http://patchwork.openwrt.org/patch/3892/)?
Aug 03 08:29:09 <builder> build #292 of xburst is complete: Failure [failed compile_9]  Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/292
Aug 03 08:31:59 <builder> build #289 of kirkwood is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/289
Aug 03 08:34:01 <builder> build #259 of iop32x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/259
Aug 03 08:39:52 <builder> build #326 of ppc40x is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/326
Aug 03 08:53:19 <russell--> MartijnVdS: i don't know, sorry.  also, should those *_das_* variables by dae instead?
Aug 03 08:53:40 <russell--> e.g. "radius_das_client" and "radius_das_port"
Aug 03 08:54:08 <russell--> maybe note
Aug 03 08:54:10 <russell--> not*
Aug 03 09:01:45 <KanjiMonster> russell--: there isn't, phy_driver_register is called on module insert, and the module is only successfully inserted if it returns no error; _unregister is only called if the module was successfully inserted and is now getting removed, so at that place all three have to have been successfully registered
Aug 03 09:03:57 <russell7> KanjiMonster: okay
Aug 03 09:04:03 <The_Lizard> Hi all, i'm messing around with a brn image, but the bootloader doesn't want to load it
Aug 03 09:04:43 <The_Lizard> I see some differences in what I get as output, and the original image I ripped off the device
Aug 03 09:18:35 <russell--> ah, right, ret isn't an object, it's non-zero on error
Aug 03 09:18:44 <russell--> nm
Aug 03 09:26:33 <MartijnVdS> russell--: no, hostapd wants "das" in there, not "dae", but nothing else uses that (while "dae" is used in other projects, notably strongswan and "radiator"; it's also the title of the RFC)
Aug 03 09:37:18 <builder> build #262 of ep93xx is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/262
Aug 03 09:47:05 <trine> trunk is broken at the moment
Aug 03 09:47:23 <trine> something is wrong with networking
Aug 03 09:48:02 <trine> after a flashing the new trunk my nanostation was reset to defaults
Aug 03 09:48:24 <trine> i have a serial line attached to it and can access it over that
Aug 03 09:48:46 <trine> I can telnet to the nano and set a passwd
Aug 03 09:48:58 <trine> but ssh does not then start up
Aug 03 09:50:11 <trine> and if i /etc/init.d/network restart all that does is to reset the nano to defaults again and where I can then telnet to it once more
Aug 03 09:52:17 <trine> its just as though its doing an erase of rootfs
Aug 03 10:08:38 <The_Lizard> Cool, my brn-boot image is working ;)
Aug 03 10:08:45 <The_Lizard> now I have to fix it's storage
Aug 03 10:10:26 <OpenWrt-Commits> hauke r37661 trunk/package/kernel/linux/modules/video.mk * kernel: only add v4l2-compat-ioctl32 when CONFIG_COMPAT is set
Aug 03 10:11:03 <blogic> The_Lizard: nice
Aug 03 10:11:30 <blogic> what wifi deos the unit have that you have got there ?
Aug 03 10:11:51 <The_Lizard> I have no idea yet, as it is unther the metal plate
Aug 03 10:12:14 <The_Lizard> Is it possible to remove it without damaging? so I can place it back later on?
Aug 03 10:13:55 <The_Lizard> anything else, when powering the device, with the reset button pressed, it is initializing the network...
Aug 03 10:14:17 <The_Lizard> I have read something about some firmware flashing page should be at 192.168.1.1, but I haven't managed to find anything yet...
Aug 03 10:16:14 <The_Lizard> I was thinking that could lead to an non-jtag installation method ;)
Aug 03 10:16:47 <The_Lizard> http://wiki.openwrt.org/doc/techref/bootloader/brnboot
Aug 03 10:18:03 <The_Lizard> my signature seems to be 5D000080
Aug 03 10:18:48 <KanjiMonster> The_Lizard: if you still have the original bootlog there should be a hint in it
Aug 03 10:19:18 <The_Lizard> it is on the wiki, but it is pretty silent... http://wiki.openwrt.org/toh/arcadyan/vgv7519
Aug 03 10:19:59 <The_Lizard> it only outputs some header, magic values, c_entry and install exceptions
Aug 03 10:21:29 <KanjiMonster> oh, okay
Aug 03 10:21:48 <KanjiMonster> well, on vr9 the highest chance is actually lantiq wifi
Aug 03 10:22:22 <KanjiMonster> especially if it is from arcadyan
Aug 03 10:23:45 <The_Lizard> I will give it a try soldering it off..
Aug 03 10:24:20 <The_Lizard> blogic: any news on obtaining a device?
Aug 03 10:27:18 <KanjiMonster> The_Lizard: you shouldn't need to; as soon as you get pci(e) to work you should see it
Aug 03 10:27:53 <The_Lizard> does the easy80920 board have wifi?
Aug 03 10:28:35 <KanjiMonster> The_Lizard: yes and no; it has one mini pci and two mini pcie slots; and comes with two cards (one mini pci and one mini pcie; both lantiq wave300)
Aug 03 10:28:44 <KanjiMonster> so it's replaceable
Aug 03 10:29:00 <KanjiMonster> (it's an eval/dev board after all)
Aug 03 10:29:45 <KanjiMonster> iirc the current dts(i) files don't register the pci(e) yet
Aug 03 10:30:55 <russell--> KanjiMonster: /me is here in case you have anything to try on the b53 driver problem, but it's getting late here, off to bed soon unless there is something cooking to try
Aug 03 10:31:17 <KanjiMonster> russell--: just go to bed, unlikely I will have anything soon
Aug 03 10:31:25 <russell--> okay, thanks
Aug 03 10:32:23 <The_Lizard> pci is in the dtsi file, it is exactly as it is in the easy80920.dtsi file
Aug 03 10:32:30 <The_Lizard> pci@E105400
Aug 03 10:33:11 <The_Lizard> is it possible I have to use another gpios-reset?
Aug 03 10:35:26 <OpenWrt-Commits> wigyori r37662 trunk/target/linux/ imx23/modules.mk imx23/patches/105-imx23-dcp.patch imx23/patches/106-add-dcp-dts.patch * imx23: add hw crypto (dcp) support
Aug 03 10:37:34 <OpenWrt-Commits> wigyori r37663 trunk/target/linux/imx23/patches/110-lradc-dts.patch * imx23: add missing DTS config for lradc
Aug 03 10:40:01 <builder> build #259 of mcs814x is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/259
Aug 03 11:00:01 <The_Lizard> I hate XModem already... takes 15 minutes to test 1 build...
Aug 03 11:09:25 <_rmk_> you need faster serial
Aug 03 11:49:59 <OpenWrt-Commits> nbd r37664 trunk/package/kernel/gpio-button-hotplug/src/gpio-button-hotplug.c * gpio-button-hotplug: fix active_low handling, possibly broken in r37643
Aug 03 11:56:36 <OpenWrt-Commits> nbd r37665 trunk/package/kernel/gpio-button-hotplug/src/gpio-button-hotplug.c * gpio-button-hotplug: cleanup, fix compiler warning
Aug 03 12:09:34 <builder> build #245 of mpc52xx is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/245
Aug 03 12:11:46 <builder> build #230 of octeon is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/230
Aug 03 13:40:15 <builder> build #293 of xburst is complete: Failure [failed compile_9]  Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/293
Aug 03 17:09:48 <OpenWrt-Commits> hauke r37666 trunk/package/kernel/broadcom-diag/src/diag.c * broadcom-diag: add gpio config for Linksys E4200v1
Aug 03 17:10:46 <OpenWrt-Commits> hauke r37667 trunk/package/kernel/broadcom-diag/src/diag.c * broadcom-diag: add gpio config for Asus RT-N66U
Aug 03 17:12:16 <OpenWrt-Commits> hauke r37668 trunk/package/kernel/broadcom-diag/src/diag.c * broadcom-diag: show error message in case something goes wrong with gpio irq
Aug 03 17:47:25 <middey> I flashed my easybox 904 Lte (vrx288 ar9 lantiq processor) with the generic ar9 image from attitude_adjustment and now it is on a boot loop  where should i send the bootlog too ?
Aug 03 17:49:54 <middey> or can i help in any way to support the device ?
Aug 03 17:54:10 <luka> middey: where did you get that device?
Aug 03 17:54:45 <middey> luka on ebay  why do you ask that ?
Aug 03 17:54:50 <luka> and vrx288 is not ar9 chip it's vr9
Aug 03 17:54:54 <luka> i want to get one too
Aug 03 17:55:27 <luka> middey: on ebay.com there are no hits for "easybox 904"
Aug 03 17:55:32 <middey> hm ok then i must look again no wonder that it not worked
Aug 03 17:55:56 <middey> luka i think this device is only produced for Vodafone Germany
Aug 03 17:58:14 <blogic> middey: you can help by doanting a unit ;)
Aug 03 17:59:35 <middey> blogic: Yes but i have not so much money as student that i can buy another one
Aug 03 18:00:26 <blogic> ;)
Aug 03 18:03:05 <blogic> middey: is there 2 versions of the 904 btw ?
Aug 03 18:03:29 <middey> blogic: in december my old LTE tarif end. Then i (my parents) would make a new and then i should get a easybox 904 then i can donate this old device. But i don't know if this is usefull because the sim card slot is bricked
Aug 03 18:03:42 <middey> blogic:  yes one for dsl and one for LTE/4g
Aug 03 18:05:14 <middey> blogic: are vr9 chipsets supported yet in openwrt ?
Aug 03 18:05:34 <blogic> yes
Aug 03 18:06:38 <middey> can i download a generic image and test it on that device ? (Are they precompiled or must i download the buildroot)
Aug 03 18:08:03 <blogic> that wont work
Aug 03 18:21:21 <middey> why do you think that that won't work blogic ?
Aug 03 18:22:04 <blogic> for a start you need to load the right phy firmware
Aug 03 18:22:09 <blogic> and there are 4 versions of it
Aug 03 18:23:30 <middey> ah ok and what's the difference between the version or the  better question is what way can i find out what of the four version can be match ?
Aug 03 18:24:01 <blogic> well there are gbit and fe firmwares
Aug 03 18:24:12 <blogic> and then it depends on the chip revision you have
Aug 03 18:24:28 <blogic> in general there is no "quick way" to test it
Aug 03 18:24:38 <blogic> you will need to properly port owrt to the unit to mak it work
Aug 03 18:24:50 <middey> and my chip is covered by something black :(
Aug 03 18:25:02 <MartijnVdS> Technical term is "goop"
Aug 03 18:25:57 <blogic> MartijnVdS: ;)
Aug 03 18:26:51 <middey> but i have the gpl sourcecode of it and the device runs already openwrt but when i flash the gpl image the ethernet and the wifi interface don't get initialiezed does that mean that it doesn't iclude the phy firmware ?
Aug 03 18:27:36 <blogic> no idea what that means
Aug 03 18:27:38 <blogic> sorry
Aug 03 18:28:13 <MartijnVdS> it could mean the GPL sources don't include drivers or firmware for the PHYs, or that they're incompetent and the GPL source isn't complete/correct.
Aug 03 18:29:28 <blogic> MartijnVdS: if i had to guess i would put my money on incompetence
Aug 03 18:30:37 <middey> blogic if you want you can look on their sourcecode that they send to nils (from gpl-violations)
Aug 03 18:31:49 <blogic> middey: it needs 1:08 more to download ;)
Aug 03 18:33:35 <middey> ok thank you for investing your time
Aug 03 18:42:09 <The_Lizard> blogic: is it OK to call out VICTORY?
Aug 03 18:42:33 <The_Lizard> I have a running openwrt, on my device, with working network (using the brn image)
Aug 03 18:45:22 <middey> blogic: i now have telnet access on the device. If you need any information from the device that i can access through telnet just ask for it
Aug 03 18:48:36 <The_Lizard> internal phy's not working yet though
Aug 03 19:19:11 <middey> blogic is the "phy" integrated in the SoC or is it a extra chip ?
Aug 03 19:19:25 <blogic> yes and yes
Aug 03 19:19:40 <blogic> there are internal and external ones
Aug 03 19:22:34 <middey> ok i found a maybe two external they labeled as  Latinq PEF7071 is that the phy name that you must know to identify the driver ?
Aug 03 19:35:46 <middey> blogic are this the chips you are looking for ?
Aug 03 21:06:37 <written_direcon> jow_laptop, ping
Aug 03 22:14:58 <builder> build #329 of cobalt is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/329
Aug 03 22:25:45 <tripolar> hi
Aug 03 22:26:09 <tripolar> Kaloz: hi, could you also give me write access to rtorrent? i'd also like to maintain it
Aug 03 22:27:21 <builder> build #345 of brcm47xx is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/345
Aug 03 22:36:30 <KanjiMonster> tripolar: ping
Aug 03 22:40:00 <tripolar> KanjiMonster: hi
Aug 03 22:40:06 <KanjiMonster> hi
Aug 03 22:40:36 <tripolar> KanjiMonster: can you give me write access to rtorrent?
Aug 03 22:41:27 <KanjiMonster> regarding r37614 ("[packages] cmus: make OSS configurable") - a) don't hide unrelated changes/fixes in the commit; either mention them in the commit log or make them a separate commit. b) "$(if $(CONFIG_CMUS_WITH_PULSE),+pulseaudio-daemon,)" - this does not work at all for menuconfig
Aug 03 22:44:30 <tripolar> KanjiMonster here it works when i enable it i get
Aug 03 22:44:39 <tripolar> opkg depends cmus|grep pulse pulseaudio-daemon
Aug 03 22:44:46 <tripolar> opkg depends cmus|grep pulse
Aug 03 22:44:50 <tripolar>         pulseaudio-daemon
Aug 03 22:45:43 <KanjiMonster> tripolar: enabling CMUS_WITH_PULSE does not enable pulseaudio-daemon in menuconfig; you have to enable it manually, and menuconfig allows you to set cmus to =y even when pulseaudio-daemon is =m
Aug 03 22:47:34 <tripolar> KanjiMonster is there a way to add a dynamic dep without defining a new package?
Aug 03 22:48:00 <tripolar> that works in menuconfig
Aug 03 22:50:12 <KanjiMonster> tripolar: the way this was before 37606 should work
Aug 03 22:50:49 <tripolar> KanjiMonster: the problem is this creates a circular dependency
Aug 03 22:51:37 <tripolar> CMUS_WITH_PULSE depends on cmus and cmus dependency depends on CMUS_WITH_PULSE
Aug 03 22:54:00 <KanjiMonster> I don't quite follow
Aug 03 22:55:08 <KanjiMonster> this works for other packages, so I don't see why it shouldn't work for cmus
Aug 03 22:55:40 <tripolar> maybe i did something wrong i will retry it again
Aug 03 22:56:47 <tripolar> KanjiMonster: as i sayed
Aug 03 22:56:48 <tripolar> tmp/.config-package.in:37737:error: recursive dependency detected!
Aug 03 22:56:48 <tripolar> tmp/.config-package.in:37737:   symbol PACKAGE_cmus depends on CMUS_WITH_PULSE
Aug 03 22:56:51 <tripolar> feeds/packages/sound/cmus/Config.in:4:  symbol CMUS_WITH_PULSE depends on PACKAGE_cmus
Aug 03 22:57:05 <tripolar> no other package is doing this
Aug 03 22:59:27 <tripolar> KanjiMonster: thats the diff
Aug 03 22:59:28 <tripolar> http://paste.debian.net/22533/
Aug 03 23:04:07 <tripolar> KanjiMonster any idea?
Aug 03 23:04:30 <KanjiMonster> tripolar: the problem are the !avr32 and audio_support dependencies of pulseaudio
Aug 03 23:17:18 <builder> build #10 of imx23 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/imx23/builds/10
Aug 03 23:18:08 <tripolar> KanjiMonster: but pulseaudio doesnt dirctly depend on AUDIO_SUPPORT, only cmus has
Aug 03 23:18:11 <tripolar> +AUDIO_SUPPORT:alsa-lib
Aug 03 23:18:25 <tripolar> i dont get where the avr stuff is coming from
Aug 03 23:20:06 <tripolar> KanjiMonster: i found the fix
Aug 03 23:26:57 <tripolar> KanjiMonster when i remove the depends on line in Config.in it works but then the Configuration menu is below cmus and not "inside" cmus
Aug 03 23:27:48 <tripolar> KanjiMonster is this okay?
Aug 03 23:28:01 <KanjiMonster> that's no the proper fix
Aug 03 23:28:04 <KanjiMonster> *not
Aug 03 23:29:03 <KanjiMonster> the proper fix is actually ... complicated
Aug 03 23:29:30 <tripolar> what would be the proper fix?
Aug 03 23:30:40 <KanjiMonster> tripolar: make pulseaudio-daemon's !avr32/AUDIO_SUPPORT dependencies not go to cmus, but to the config option enabling pulseaudio support
Aug 03 23:32:13 <KanjiMonster> (the proper fix is likely using a real package dependency management system and not forcing menuconfig into one ;)
Aug 03 23:32:28 <tripolar> KanjiMonster: but pulseaudios Makefile has no AUDIO_SUPPORT or !avr32 line
Aug 03 23:34:05 <tripolar> KanjiMonster: am i wrong?
Aug 03 23:35:44 <KanjiMonster> I guess one of pulseaudio's dependencies has it
Aug 03 23:36:53 <KanjiMonster> pulseaudio -> alsa-lib -> kmod-sound-core -> AUDIO_SUPPORT
Aug 03 23:37:45 <tripolar> so what would you propose as a fix
Aug 03 23:37:49 <OpenWrt-Commits> luka r37669 packages/net/nmap/Makefile * [packages] nmap: upgrade to 6.40
Aug 03 23:38:19 <KanjiMonster> pulseaudio -> libsndfile -> !avr32
Aug 03 23:38:22 <KanjiMonster> not sure
Aug 03 23:38:46 <tripolar> i mean removing the cmus dep for the options would at least work
Aug 03 23:38:59 <KanjiMonster> that just hides the problem
Aug 03 23:39:48 <tripolar> i would say the best solution overall would be a global pulseaudio flag that enables pulseaudio support in packages that support it like AUDIO_SUPPORT - PULSEAUDIO_SUPPORT
Aug 04 00:08:37 <OpenWrt-Commits> luka r37670 packages/net/ tinyproxy/Makefile tinyproxy/patches/040-fix_url_filter_in_transparent_mode.patch tinyproxy/patches/010-no-docs-and-tests.patch tinyproxy/patches/030-allow_bind_in_transparent_mode.patch * [packages] tinyproxy: update to 1.8.3
Aug 04 00:41:52 <zinx> blogic: should i clean up my BR-6475ND patch?  still doesn't support wireless, though it will be a little easier to implement now.   it uses a pci "RT3071" (as reported by the hardware, dunno about accuracy), id 1814:3091 w/ a RF3853 that uses the new EEPROM layout.  there's no eeprom on the device - it has to be loaded from a file - so supporting specification of it in the dts will need to be added too
Aug 04 00:42:34 <zinx> blogic: dunno when i'll get around to trying my hand at the wireless changes, and it's somewhat useless as a wireless router without that ;)
Aug 04 01:01:12 <builder> build #355 of at91 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/355
Aug 04 02:03:07 <builder> build #308 of rb532 is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/308
Aug 04 02:06:00 <builder> build #308 of ppc44x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/308
Aug 04 02:42:04 <builder> build #360 of brcm63xx is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/360
Aug 04 02:55:14 <builder> build #322 of uml is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/322
**** ENDING LOGGING AT Sun Aug 04 02:59:58 2013