**** BEGIN LOGGING AT Wed Sep 21 02:59:57 2011 Sep 21 07:53:29 * DocScrutinizer WB everybody Sep 21 15:09:50 hello folks Sep 21 15:10:11 when using WPA, I cannot get the FR to reconnect reliably Sep 21 15:10:31 network works good the first time it's set up, but not successive times Sep 21 15:13:40 michelem: hey Sep 21 15:14:10 michelem: i am using NWA, it's reliable Sep 21 15:14:13 michelem: http://openmoko-public-mailinglists.1958.n2.nabble.com/ar6000-FR-s-wifi-bugs-workarounds-and-CLI-usage-tips-read-this-for-stable-wifi-td4607082.html Sep 21 15:16:03 h4v: I need to use the backend, no GUI Sep 21 15:18:41 michelem: well, my "tips" is probably the most detailed guide out there, nobody's "researched" any farther. Sep 21 15:30:45 PaulFertser: how do you "power-cycling ar6000" ? ifconfig down and up ? Sep 21 15:31:44 also, I don't get the SSID problem. Is it about some specific strings, or you just have to change the SSID periodically? Sep 21 15:51:21 michelem: no Sep 21 15:51:32 michelem: power-cycling is best done by unloading/unbinding the module. Sep 21 15:51:59 michelem: s3cmci, that is the driver for the integrated SD controller of the SoC. Sep 21 15:52:33 michelem: i could never associate with my AP with the said SSID, after i changed it, i could always associate. After i changed it back, i couldn't associate again. Sep 21 15:53:16 I don't have s3cmci, only s3c2410_udc (used by g_ether whose removal makes me lose usb0 too) Sep 21 15:53:27 michelem: no, that's not the one. Sep 21 15:53:57 michelem: probably you have that module built-in, so you have to unbind it rather than unload. Sep 21 15:54:25 here-s my happenings: wpa_supplicant works 1st time. Then, it associates successfully, but when I run udhcpc it goes "Authentication with c0:c1:c0:c3:3f:bc timed out", and enters an association/failed-auth loop Sep 21 15:54:49 ok, let me read up about unbind Sep 21 15:55:53 michelem: also, the range of the module is worse than that of common laptop's. So if your laptop works somewhere (e.g. behind 2 concrete walls) it doesn't mean FR can. Sep 21 15:56:28 michelem: so, my best advice is to stay reasonably close to the AP (at least for testing), and following what i wrote back then about power cycling the module and using the maxperf trick. Sep 21 15:56:51 I have good hopes in the power cycling Sep 21 15:56:59 trying now, will let you know Sep 21 16:02:20 PaulFertser: please help me with the path for unbind. find /sys/ -name 's3cmci*' returns nothing Sep 21 16:03:09 michelem: ls /sys/modules Sep 21 16:06:10 still can't figure how to unbind it. Is this sequence by lindi correct? http://docs.openmoko.org/trac/ticket/2277#comment:8 Sep 21 16:06:33 he unbinds s3c2440-sdi entirely Sep 21 16:07:27 michelem: yes, that should be correct, probably in your kernel version you should slightly amend the path Sep 21 16:07:53 michelem: sorry about sdi/mci confusion Sep 21 16:10:35 (yay, the mentioned ticket is what i actively participated in, providing a nice patch :) ) Sep 21 16:25:53 no doubt you're cool :) Sep 21 16:25:59 so the unbind/rebind trick works Sep 21 16:26:10 question is just how to integrate it into ifup/ifdown now Sep 21 16:28:47 this rocks Sep 21 16:28:50 thanks Paul Sep 21 16:28:58 michelem: on Debian you can add hooks to /etc/network/interfaces, should work Sep 21 16:29:01 michelem: :) Sep 21 16:29:13 I will use an "iface manual" and commands in there Sep 21 16:35:46 ok, workday is over Sep 21 16:35:50 see you next days folks Sep 21 16:35:56 See you, good luck! Sep 21 17:41:04 heyo Sep 21 22:04:18 has anyone found a good podcast solution for qtmoko? **** ENDING LOGGING AT Thu Sep 22 02:59:56 2011