**** BEGIN LOGGING AT Fri Sep 20 03:00:00 2013
Sep 20 03:56:16 <Devastator> blogic ping
Sep 20 08:12:39 <blogic> Devastator: hi
Sep 20 08:43:30 <builder_> build #386 of orion is complete: Failure [failed compile_8]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/386
Sep 20 09:52:33 <merbanan> I'm getting a hanged udhcpc process that wont renew the ip address, it is just getting stuck in a syslog call
Sep 20 09:52:45 <merbanan> and it gets unstuck by restarting netifd
Sep 20 09:52:57 <merbanan> does that ring a bell to anyone ?
Sep 20 10:28:02 <builder_> build #355 of rb532 is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/355
Sep 20 10:30:35 <builder_> build #355 of ppc44x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/355
Sep 20 10:53:14 <builder_> build #377 of lantiq is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/377
Sep 20 11:24:00 <Devastator> blogic this is what my dmesg output shows: http://codepad.org/Bsr3TFXK
Sep 20 11:24:27 <builder_> build #368 of uml is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/368
Sep 20 11:24:33 <Devastator> blogic line 165
Sep 20 11:25:07 <Devastator> the call trace is not related, by the way, I've fixed
Sep 20 11:58:18 <builder_> build #335 of sibyte is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/335
Sep 20 12:34:35 <blogic> Devastator: ok, i will check in a sec
Sep 20 12:35:52 <Devastator> great, I also tried to discover from which function this debug message was coming, but couldn't find it
Sep 20 13:04:25 <blogic> Devastator: this is dir 615 h1 ?
Sep 20 13:05:00 <Devastator> blogic dir 610 a1
Sep 20 13:05:09 <Devastator> RT5350..
Sep 20 13:06:29 <blogic> Devastator: http://pastebin.com/yeb8ENh9
Sep 20 13:06:33 <blogic> try that patch please
Sep 20 13:06:42 <blogic> the phy leds and jtag pins are dual function
Sep 20 13:06:52 <blogic> so you cannot grab them for gpio function
Sep 20 13:07:09 <blogic> i am pretty sure that that patch will fix it
Sep 20 13:07:57 <Devastator> blogic thanks! I will test this later today
Sep 20 13:08:26 <blogic> ok
Sep 20 13:08:27 <Devastator> blogic does this mean jtag cannot be used?
Sep 20 13:08:30 <blogic> tell me if it worked
Sep 20 13:08:35 <blogic> yep
Sep 20 13:08:43 <blogic> jtag and gphy share the same ping
Sep 20 13:08:45 <blogic> jtag and gphy share the same pins
Sep 20 13:08:51 <Devastator> oh boy..
Sep 20 13:08:56 <blogic> ;)
Sep 20 13:09:07 <Devastator> won't be smart to brick this unit then..
Sep 20 13:09:20 <blogic> hehe
Sep 20 13:09:24 <zinx> blogic: dunno if wlan will ever work on this router (BR-6475nD, RT3883 based w/ PCIe dev id 3091 + 'RF3053')
Sep 20 13:09:34 <zinx> blogic: want patches anyway? :/
Sep 20 13:09:40 <blogic> zinx: sure
Sep 20 13:09:48 <blogic> zinx: there are rt3883 wiif patches floating around
Sep 20 13:09:52 <zinx> kk, i'll get 'em ready in the next few days
Sep 20 13:09:59 <blogic> i believe rt2x00 will see rt3883 support very soon
Sep 20 13:10:04 <blogic> zinx: please do
Sep 20 13:10:05 <zinx> blogic: i've tried various ones, they don't seem to function with mine
Sep 20 13:10:19 <blogic> zinx: gabor made a new series that i have seen working already
Sep 20 13:10:22 <zinx> blogic: the ones posted to the rt2x00 ml
Sep 20 13:10:30 <blogic> zinx: by gabor ?
Sep 20 13:10:33 <zinx> blogic: yeah
Sep 20 13:10:38 <blogic> ok
Sep 20 13:10:44 <blogic> well i am sure he will reowrk them
Sep 20 13:10:56 <blogic> zinx: never give up hope :)
Sep 20 13:10:57 <Devastator> blogic also, do you know how to get magic numbers for platform/upgrade.sh?
Sep 20 13:11:09 <zinx> blogic: latest i applied is "rt2x00: rt2800lib: fix band selection and LNA PE control for RT3593 PCIe cards"
Sep 20 13:11:11 <blogic> Devastator: most likely the first 32  bit of the uimage
Sep 20 13:11:27 <zinx> blogic: was hoping it would do the trick, but still no beacons/scanning
Sep 20 13:11:39 <Devastator> blogic so I just have to check that in original firmware?!
Sep 20 13:11:44 <blogic> Devastator: the sema thing
Sep 20 13:11:49 <zinx> blogic: i have to add support for the PCI id and various chip id stuff too :X
Sep 20 13:11:52 <blogic> Devastator: let me have a look
Sep 20 13:11:57 <Devastator> ok
Sep 20 13:12:36 <zinx> and i'll admit it's entirely probable i did it wrong last time
Sep 20 13:12:37 <blogic> today i want to play with the audio stuff for ralink
Sep 20 13:12:49 * blogic has a asus rp n53
Sep 20 13:12:58 <blogic> the audio drivers are already partially working
Sep 20 13:13:02 <zinx> heh
Sep 20 13:13:18 <zinx> can't help w/ that one, my device has no audio headers :)
Sep 20 13:14:03 <blogic> hehe
Sep 20 13:14:13 <zinx> i'm tempted to plug some USB ports in, but i dunno if it needs extra resistors/decoupling caps/whatever
Sep 20 13:14:30 <zinx> it has some pads for some smd resistors/caps next to the USB headers
Sep 20 13:14:58 <Devastator> I want to do that as well..
Sep 20 13:18:09 <zinx> the board also claims to support triple-stacked USB connectors, but if you look at the pads, two sets are connected on top w/ PCB trace :/
Sep 20 13:21:29 <Devastator> even with this jtag problem I think worth to port this router, I'm just worried now hehe
Sep 20 13:26:10 <Devastator> time to prepare a wiki entry with a big warning!
Sep 20 13:31:30 <Devastator> blogic I've discovered a few weeks ago I've put the router in the wrong place in rt2x00-eeprom, so I was getting wrong mac address for wireless, you don't mind if I send a patch fixing it and a few things on the dts file, do you?
Sep 20 13:35:52 <blogic> Devastator: ok
Sep 20 13:36:35 <Devastator> thanks, I thought you would get mad or something :)
Sep 20 14:01:30 <merbanan> nbd: I get a stale write call in the busybox dhcp client, when I kill netifd the stall is released
Sep 20 14:02:31 <merbanan> so somehow netifd wont complete the write
Sep 20 14:03:15 <merbanan> do you have any idea where to start looking to figure out this bug ?
Sep 20 14:25:26 <OpenWrt-Commits> luka r38083 trunk/target/linux/lantiq/dts/GIGASX76X.dts * lantiq: fix usb on sx76x
Sep 20 15:22:04 <Devastator> blogic ping
Sep 20 15:24:41 <Devastator> blogic this is what I have, port #1 led works as expected as always did, ports #2, #3 and #4 have inversed led polarity http://codepad.org/2LbUtSZ8
Sep 20 15:25:38 <blogic> Devastator: so more leds work now than before ?
Sep 20 15:26:05 <Devastator> blogic it's the same basically
Sep 20 15:26:32 <Devastator> how can one port have a polarity and the others inversed?
Sep 20 15:26:47 <blogic> hmmmm
Sep 20 15:27:44 <Devastator> I don't think ralink,portmap setting matters, right?
Sep 20 15:27:59 <blogic> nope
Sep 20 15:28:31 <Devastator> anyway, if you have an idea I'm here to test
Sep 20 15:40:24 <blogic> very strange
Sep 20 15:57:15 <Devastator> blogic I've commented out ralink,led-polarity, gpio-leds and gpio-keys-polled, but I think it is not related, right?
Sep 20 15:57:53 <blogic> ralink,led-polarity is related
Sep 20 16:42:24 <OpenWrt-Commits> juhosg r38084 trunk/target/linux/ar71xx/image/Makefile * ar71xx: fix Cameo934x initramfs image generation
Sep 20 16:42:25 <OpenWrt-Commits> juhosg r38085 trunk/target/linux/ar71xx/files/arch/mips/ath79/ dev-eth.c dev-eth.h * ar71xx: rename ath79_parse_mac_addr to ath79_parse_ascii_mac
Sep 20 16:42:26 <OpenWrt-Commits> juhosg r38086 trunk/target/linux/ar71xx/files/arch/mips/ath79/mach-dir-505-a1.c * ar71xx: dir-505-a1: use ath79_parse_ascii_mac helper
Sep 20 16:42:28 <OpenWrt-Commits> juhosg r38087 trunk/target/linux/ar71xx/files/arch/mips/ath79/mach-dir-825-b1.c * ar71xx: dir-825-b1: use ath79_parse_ascii_mac helper
Sep 20 16:42:29 <OpenWrt-Commits> juhosg r38088 trunk/target/linux/ar71xx/files/arch/mips/ath79/mach-dir-825-c1.c * ar71xx: dir-825-c1: use ath79_parse_ascii_mac helper
Sep 20 16:42:31 <OpenWrt-Commits> juhosg r38089 trunk/target/linux/ar71xx/files/arch/mips/ath79/mach-tew-673gru.c * ar71xx: tew-673gru: use ath79_parse_ascii_mac helper
Sep 20 16:42:35 <OpenWrt-Commits> juhosg r38090 trunk/target/linux/ar71xx/files/arch/mips/ath79/mach-tew-712br.c * ar71xx: tew-712br: use ath79_parse_ascii_mac helper
Sep 20 17:00:40 <OpenWrt-Commits> juhosg r38091 trunk/target/linux/ar71xx/base-files/etc/uci-defaults/02_network * ar71xx: set proper wan mac during initial configuration on dir-825-c1
Sep 20 17:03:17 <Devastator> blogic ok, but it can be only 0 or 1, correct?
Sep 20 17:05:36 <blogic> try 0 and 0xff
Sep 20 17:05:42 <blogic> well no
Sep 20 17:05:45 <blogic> 0x1ff
Sep 20 17:05:48 <blogic> no
Sep 20 17:05:50 <blogic> 0x1f :-D
Sep 20 17:05:56 <blogic> 0x1f it is
Sep 20 17:11:00 <Devastator> ralink,led-polarity <0x1f>?
Sep 20 17:13:19 <blogic> try it
Sep 20 17:13:31 <Devastator> danke sir :)
Sep 20 17:14:21 <blogic> does it work ?
Sep 20 17:15:54 <Devastator> blogic compiling..
Sep 20 17:16:07 <Devastator> or is there a way to change it with a tool?
Sep 20 17:16:46 <Devastator> like, inside the router..
Sep 20 17:21:53 <Devastator> blogic it doesn't work..
Sep 20 17:22:22 <Devastator> blogic if there was something I could do to debug or a gpio tool to test them..
Sep 20 17:22:33 <blogic> nope
Sep 20 17:22:39 <blogic> i will think a bout it a bi tmre
Sep 20 17:22:43 <blogic> i will think a bout it a bit more
Sep 20 17:23:03 <Devastator> alright
Sep 20 17:23:53 <Devastator> blogic offtopic: do you like soccer? like, do you have a favourite team? :P
Sep 20 17:25:26 <blogic> no
Sep 20 17:25:39 <blogic> football does not exist in me perceived reality
Sep 20 17:26:08 <Devastator> heheh
Sep 20 17:26:28 <Devastator> now ontopic: wireless led is also inversed, meh :|
Sep 20 17:29:53 <Devastator> ok, wan, wireless, ports #2, #3 and #4 have inversed led behavior, port #1 is correct
Sep 20 17:33:07 <Devastator> aha! I think I understand what's happening
Sep 20 17:36:11 <DonkeyHotei> heh, perceived realities are fun
Sep 20 17:36:15 <Devastator> maybe port #1 is "wan" and wan is port #1, that's because wan, ports #2, #3 and #4 are lit and port #1 is off
Sep 20 17:37:31 <Devastator> now.. should I touch 02_network or ralink,portmap to test my findings?
Sep 20 18:12:07 <Devastator> switch seems to be properly configured, I can get a ping reply from all lan ports, just the leds that are confusing..
Sep 20 18:15:16 <Devastator> maybe portmap? but I don't know available values for it..
Sep 20 18:18:20 <Devastator> blogic what's the worse that can happen with a wrong ralink,portmap value?
Sep 20 18:19:46 <Devastator> tried 1f and 2f, 1f makes the leds even worse (power led blinks together with port #2), 2f is current state..
Sep 20 18:44:12 <builder_> build #345 of avr32 is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/345
Sep 20 18:47:47 <builder_> build #292 of iop32x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/292
Sep 20 19:02:48 <Devastator> ok, I think I understand how ralink,portmap works now
Sep 20 21:43:35 <builder_> build #293 of ep93xx is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/293
Sep 20 23:27:46 <froek> i just bricked my wrt610n, is there a way to unbrick?
Sep 20 23:27:54 <froek> (checked site, no clear way)
Sep 20 23:33:29 <RooTer> tftp flashing isnt working?
Sep 20 23:40:26 <groz> got a serial console on it ?
Sep 20 23:40:33 <groz> is boot loader still intact ?
Sep 20 23:42:18 <froek> no tftp
Sep 20 23:42:25 <froek> no serial consol.. boot loader not sure
Sep 20 23:42:37 <froek> dhcp doesn't give an address (168.x.x.x)
Sep 20 23:42:56 <froek> (169.x.x.x) sorry
Sep 20 23:43:09 <froek> i've tried doing reset on boot, nothing...
Sep 20 23:43:17 <froek> power light is constantly flashing
Sep 20 23:44:25 <froek> i changed a hotplug script to mount things, but maybe that really messed up the boot :/
Sep 20 23:44:41 <froek> i compiled from trunk as well (never had a problem before)
Sep 20 23:47:02 <KanjiMonster> froek: try configuring your pc with a static ip in 192.168.1.0/24 (except 192.168.1.1) and start pinging 192.168.1.1 - if you turn on the device, you should receive a few (~3) replies with a TTL of 100; these are from the bootloader
Sep 20 23:47:18 <froek> KanjiMonster: i'll try that, standby
Sep 20 23:47:49 <froek> i get 1 ping
Sep 20 23:48:25 <KanjiMonster> okay, that means the bootloader is still intact; iirc you need push it with tftp it exactly in that moment you receive a reply
Sep 20 23:49:03 <froek> alright, i'll try
Sep 20 23:49:10 <groz> push in a good working image
Sep 20 23:49:15 <groz> no point sending same broken one
Sep 20 23:50:07 <froek> yeah, i'll push a trunk snapshot i know works
Sep 20 23:53:17 <froek> hmm i'm concerned i'm not getting pings anymore
Sep 20 23:53:22 <froek> i haven't tried flashing yet.
Sep 20 23:55:38 <froek> wow timing is so sensitive.. putting.. we'll see if it succeeds..
Sep 20 23:55:59 <froek> it said transfer timed out
Sep 21 00:01:23 <froek> i'm pretty sure i'm hitting it right on the point where it pings.. but it always timed out the transfer, ideas?
Sep 21 00:08:19 <groz> yah
Sep 21 00:08:27 <groz> hit it just before it pings
Sep 21 00:08:35 <groz> something I've done, and it's worked for me
Sep 21 00:08:42 <groz> start the tftp, then plug in the unit
Sep 21 00:08:51 <groz> after first ping which gets arp in place
Sep 21 00:08:54 <groz> repower the unit
Sep 21 00:09:11 <groz> when it pings on the second round, the tftp that's trying, will catch it
Sep 21 00:09:43 <groz> gotta run for a bit
Sep 21 00:09:58 <froek> k i'll try.. thx for help
Sep 21 01:12:00 <Devastator> if I edit something in target/linux/ramips/base-files/etc/... do I need to do anything before make to update the files?
**** ENDING LOGGING AT Sat Sep 21 03:00:00 2013