IRC log of #maemo-ssu for Tuesday, 2014-02-11

« Monday, 2014-02-10 Index Wednesday, 2014-02-12 »
*** g3kk3r has quit IRC00:05
*** hbib1 has quit IRC00:06
*** sixwheeledbeast has quit IRC00:16
*** sixwheeledbeast has joined #maemo-ssu00:18
*** g3kk3r has joined #maemo-ssu00:43
*** luf has quit IRC00:44
silviofboa - bad, i test my software (my second n900 is on the way) on vm with xephyr. and i wonder why i have only a hildon-dekstop 2.2.140 installed on x86-target. (on armel-target) it is 2.2.153 installed). Now I have found that we not providing a _i386-package of hildon newer than 2.2.140.00:57
silviofI think I will wait onto my second n900 ^^00:57
silviofor other - can i build a complete environment woth e.g. a "make world" or so?00:58
silviofs/woth/with/01:00
infobotsilviof meant: or other - can i build a complete environment with e.g. a "make world" or so?01:00
*** arcean has quit IRC01:09
*** arcean has joined #maemo-ssu01:10
*** sixwheeledbeast has quit IRC01:11
merlin1991silviof: we don't provide _i386 packages for the cssu stuff, if you want to run cssu in xephyr you have to build from source01:14
silviofmerlin1991: okay, thx - than i will wait on a developer n900 :-P01:34
silviofgood night - by the way01:35
*** sixwheeledbeast has joined #maemo-ssu01:41
*** M4rtinK has quit IRC01:53
*** okias has quit IRC02:36
*** arcean has quit IRC02:50
*** sixwheeledbeast has quit IRC03:21
*** dos1 has quit IRC03:31
*** sixwheeledbeast has joined #maemo-ssu03:34
*** Milhouse has quit IRC03:40
*** MohammadAG has quit IRC03:40
*** MohammadAG has joined #maemo-ssu03:47
*** Milhouse has joined #maemo-ssu03:53
*** amizraa has quit IRC04:12
MaxdamantusJust wondering .. what's the difference between zImage-2.6.28.10-cssu1 and zImage-2.6.28.10-cssu1.fiasco?04:28
MaxdamantusThere seems to be some metadata at the beginning of the .fiasco, but flasher doesn't unpack it with -u04:32
MaxdamantusOh, nvm .. was using the flasher wrong.04:33
Maxdamantusalso answers the question I asked in #maemo the other day of what "FIASCO" means .. I think the people there thought I was asking about etymology, but I just wanted to know that it referred to essentially an archive format (and not a software distribution or something).04:37
*** unclouded has quit IRC04:47
*** g3kk3r has quit IRC05:01
*** silviof has quit IRC05:01
*** g3kk3r has joined #maemo-ssu05:01
*** amizraa has joined #maemo-ssu05:04
*** silviof has joined #maemo-ssu05:08
*** sixwheeledbeast has quit IRC05:11
*** sixwheeledbeast has joined #maemo-ssu05:26
*** amiconn has quit IRC05:29
*** amiconn_ has joined #maemo-ssu05:29
*** amiconn_ is now known as amiconn05:29
*** kostola_ has quit IRC06:23
*** kostola has joined #maemo-ssu06:23
*** unclouded has joined #maemo-ssu06:43
*** thedead1440_ has quit IRC07:16
*** thedead1440 has quit IRC07:16
*** sunny_s has joined #maemo-ssu08:44
*** Maxdamantus has quit IRC08:46
*** Maxdamantus has joined #maemo-ssu08:50
*** thedead1440 has joined #maemo-ssu09:18
*** Maxdamantus has quit IRC09:24
*** Maxdamantus has joined #maemo-ssu09:26
*** sunny_s has quit IRC09:27
*** zz_ototo is now known as ototo09:35
DocScrutinizer05(i386 packages of cssu) would that change anything after all? I mean, does xephyr have orientation support? and how? would MHD shortcuts really work on xephyr? Anything else difference you could notice UX wise?09:49
DocScrutinizer05xephyr stuff is meant to test *apps* during development, no?09:51
DocScrutinizer05we got no CSSU-only apps (well, not really)09:51
DocScrutinizer05and that's fine the way it is, and expected to stay this way09:52
* DocScrutinizer05 finally tests rollback of wlancond, after err 2(?) years of IRC not reconnecting after connection roaming09:54
silviofDocScrutinizer05: Its a matter of test of software. I use my maemo-based mobile on daily basis. If I develop some components than I will test it. But without a second phone I have only the xephyr-way. But the xephyr way is only functional on X86.09:54
DocScrutinizer05so?09:55
silviofso!09:55
DocScrutinizer05how's that related to cssu?09:55
DocScrutinizer05you can't test cssu "components" on x8609:56
DocScrutinizer05generally09:56
DocScrutinizer05and any app isn't supposed to need cssu to run09:56
silviofno you cant, because if you change something in hildon-desktop you need to build a package and to install with dpkg. Thats is not able because some depencies are not provided for the x86.09:57
DocScrutinizer05so, depending on what "components" you want to develop, you're either fine with x86 emu as is, or can't use it at all09:57
DocScrutinizer05and not because there's no cssu x86 available, but because x86 isn't the right thing to use for some components to test09:59
DocScrutinizer05IroN900:~# ll /usr/sbin/wlancond*10:03
DocScrutinizer05-rwxr-xr-x 1 root root 59764 2012-08-22 19:53 /usr/sbin/wlancond10:03
DocScrutinizer05-rwxr-xr-x 1 root root 57692 2011-12-24 17:38 /usr/sbin/wlancond.bak10:03
DocScrutinizer05MHM!10:03
DocScrutinizer05IroN900:~# mv /usr/sbin/wlancond /usr/sbin/wlancond.new10:05
DocScrutinizer05IroN900:~# cp /usr/sbin/wlancond.bak /usr/sbin/wlancond10:05
DocScrutinizer05IroN900:~# uptime10:05
DocScrutinizer05 09:04    84 Tage 10:20 an,  0 Benutzer,  Durchschnittslast: 0,15, 0,07, 0,0210:05
DocScrutinizer05IroN900:~# dsmetool -b10:05
DocScrutinizer05let's see if that will fix this annoying obscure incapability of xchat to detect a change of own IP -> connection stall -> reconnect_to_server10:07
*** sixwheeledbeast has quit IRC10:09
*** MohammadAG has quit IRC10:18
*** MohammadAG_ has joined #maemo-ssu10:19
*** MohammadAG_ is now known as MohammadAG10:19
*** sixwheeledbeast has joined #maemo-ssu10:21
DocScrutinizer05merlin1991: http://mg.pov.lt/maemo-ssu-irclog/%23maemo-ssu.2011-12-26.log.html#t2011-12-26T22:46:0710:23
DocScrutinizer05merlin1991: what's been the purpose of patched wlancond? I can't find "wlancond" string in cssu-t changelog10:24
*** freemangordon_ has joined #maemo-ssu10:38
*** freemangordon_ has quit IRC10:44
*** ototo is now known as zz_ototo10:44
merlin1991the package name is osso-wlan, it contains 1 fix for the injeciton driver that has no side effects and a fix for eapd11:20
merlin1991commits: https://gitorious.org/community-ssu/osso-wlan/commit/d33e64330937dd1812bed257a4525513ebaf8fe1 and https://gitorious.org/community-ssu/osso-wlan/commit/22c5e804febd00195dc48dae652b120a3e28936911:21
*** jon_y has joined #maemo-ssu11:22
merlin1991DocScrutinizer05: ^^11:24
DocScrutinizer05thanks11:27
DocScrutinizer05what's eapd?11:28
merlin1991its part of the wpa auth stuff11:29
DocScrutinizer05aah11:29
DocScrutinizer05I'm finally fed up with xchat taking 60min to reconnect to ZNC when I leave WLAN range and roam to GPRS11:30
DocScrutinizer05checking all possible culprits now, but I can't find anything that makes sense11:30
merlin1991there's always the chance that xchat is the culprit ;)11:33
*** jon_y has quit IRC11:39
*** zz_ototo is now known as ototo11:44
DocScrutinizer05yeah, but I can't recall it changed since it worked, which it evidently did11:45
DocScrutinizer05only change I can think of: update to ZNC1.011:45
DocScrutinizer05might ZNC ping-keep-alive not be aware of IP changes?11:47
DocScrutinizer05which would mean it answers pings from arbitrary source IP11:48
DocScrutinizer05no matter if a client authenticated there or not11:48
DocScrutinizer05and even if that was the case, then where from are the 3600 seconds from IP change on N900 till xchat re-registering with ZNC11:50
DocScrutinizer05or maybe xchat doesn't accept "net_ping_timeout = 90" and defaults to 3600?11:51
*** freemangordon_ has joined #maemo-ssu11:52
DocScrutinizer05merlin1991: do you have the xchat code at hand? could you check if xchat rejects "net_ping_timeout = 90" and defaults to 3600?11:58
DocScrutinizer05it seems I might have changed the net_ping_timeout from 240 to 90 eventually11:59
*** arcean has joined #maemo-ssu12:10
DocScrutinizer51let's see what happens now when roaming to GPRS12:14
DocScrutinizer05ok12:15
* DocScrutinizer05 starts a timer in mind12:15
*** jon_y has joined #maemo-ssu12:17
*** sunny_s has joined #maemo-ssu12:17
DocScrutinizer05ok, the 301 seconds I've sent net_ping_timeout to have expired. No reconnect of xchat >:-(12:22
DocScrutinizer05changing wlancond didn't help12:23
DocScrutinizer05changing all suspicious settings in ZNC didn't help12:23
DocScrutinizer05hmm, relogin after 25 min12:44
*** luf has joined #maemo-ssu12:45
*** joshgillies has joined #maemo-ssu13:02
DocScrutinizer51hmmm13:10
DocScrutinizer51*something* changed13:10
DocScrutinizer51it now does relogin after 25min13:11
DocScrutinizer05with "net_ping_timeout = 301"13:11
DocScrutinizer05strace of xchat looks strange13:11
DocScrutinizer05anyway no packets sent between ZNC and xchat for the whole duration of disconnect   => xchat is buggy, or fremantle system is buggy13:12
*** sixwheeledbeast has quit IRC13:22
*** lizardo has joined #maemo-ssu13:28
*** NishanthMenon has joined #maemo-ssu13:38
*** sixwheeledbeast has joined #maemo-ssu13:54
*** javispedro has joined #maemo-ssu13:57
*** dhbiker has quit IRC14:11
*** dhbiker has joined #maemo-ssu14:15
*** hbib has joined #maemo-ssu14:53
*** javispedro has quit IRC15:02
*** hbib has quit IRC15:05
*** hbib has joined #maemo-ssu15:08
*** joshgillies has quit IRC15:13
*** hbib1 has joined #maemo-ssu15:19
*** hbib has quit IRC15:21
*** M4rtinK has joined #maemo-ssu15:22
FIQDocScrutinizer05: for me, xchat is usually having a hard time to figure out that it disconnected if that's what you're referring to16:16
FIQnot just on N900, but on desktop as well16:16
DocScrutinizer05well, th<t been different for me, a maybe 1 or 2 years ago. eventually it changed to xchat needing exactly 60min after IP change to reconnect16:17
DocScrutinizer05and now it seems my tweaks changed that 25min16:18
DocScrutinizer05the only things i changed on N900 were: "net_ping_timeout = 90" -> "net_ping_timeout = 301" (SIC!), and replacing CSSU wlancond by a two years old orginal version16:19
DocScrutinizer05I can't see any logic in either of both changing time to reconnect form 60 to 25min16:19
DocScrutinizer05I nevertheless wonder if maybe ZNC is somehow remote-controlling what xchat does, regarding timeouts and whatnot16:22
DocScrutinizer05if that wasn't 25 but 18min 8possible, since I only tested 2 times and not very precisely) then this would suggest timeout is  5400min / net_ping_timeout16:28
DocScrutinizer05s/timeout/time till reconnect/16:28
infobotDocScrutinizer05 meant: if that wasn't 25 but 18min 8possible, since I only tested 2 times and not very precisely) then this would suggest time till reconnect is  5400min / net_ping_timeout16:28
DocScrutinizer05I wonder if IRC protocol does something similar like SIP, for keepalive timeout negotiation. I.E. both the server (here ZNC) and the client (xchat) negotiate the timeout based on some prefrences set on either side. In the end this would mean xchat actually gets "remote controlled" by ZNC like I suspected above16:32
*** NIN101 has joined #maemo-ssu16:34
DocScrutinizer05particularly: when ZNC tells xchat "hey, I gonna send a keepalive ping to you every 60 min" then it's of course clear why xchat won't notice the IP change resp "disconnect" any sooner16:34
DocScrutinizer05maybe xchat asks for 90 seconds interval, and ZNC answers 60 but some bug multiplies that by 60 to convert from seconds to minutes (or simply places wrong unit in there)16:36
DocScrutinizer05anyway, you can easily adjust xchat net_ping_timeout:  /set net_ping_timeout <value in seconds>16:38
DocScrutinizer05just in case you want to experiment a bit with this16:39
*** M4rtinK has quit IRC16:39
DocScrutinizer05note that the new value doesn't get saved to .xchat2/xchat.conf until you gracefully exit xchat (or find the "save" menu entry)16:40
DocScrutinizer05now if only I'd find a more easy method than changing the IP of N900, to test this16:42
*** Vazay has joined #maemo-ssu17:05
*** FIQ has quit IRC17:05
*** FIQ has joined #maemo-ssu17:15
*** FIQ is now known as Guest5354617:15
*** Vazay has quit IRC17:28
*** arcean_ has joined #maemo-ssu17:35
*** radekp__ is now known as radekp17:35
*** anYc has quit IRC17:37
*** arcean has quit IRC17:38
*** freemangordon_ has quit IRC17:45
*** anYc has joined #maemo-ssu17:57
*** luf has quit IRC18:02
*** Guest53546 has quit IRC18:04
*** Guest53546 has joined #maemo-ssu18:04
*** Guest53546 is now known as FIQ18:04
FIQDocScrutinizer05: do you know how the irc protocol looks like?18:06
FIQthe only thing the server sends continuosly is a ping timeout check18:07
FIQthe server doesn't tell the client to do anything regarding connectivity (besides these pingpongs)18:08
FIQthe server *does* "remote control" irc clients, but only by issuing IRC commands to it, i.e. to set chanmodes/usermodes, join/part channels, change your nick and host, etc18:09
FIQand since there's a bajillion different irc servers and there's not really a strict standard, the client has to obey to be able to function properly everywhere18:09
*** joshgillies has joined #maemo-ssu18:09
DocScrutinizer05FIQ: does >>I wonder if IRC protocol does something similar like SIP<< sound like I know IRC protocol?18:10
FIQno it doesn't18:10
FIQthat's why I told a bit :D18:10
FIQi.e. the fact that the server doesn't tell the client anything regarding timeouts18:10
DocScrutinizer05aha18:11
*** joshgillies has quit IRC18:14
DocScrutinizer05tbh i'm not particularly interested in IRC protocol. What i'd like to know are details about how xchat handles net_ping_timeout18:16
DocScrutinizer05I'd even think that keep-alive-pings are only loosely related to IRC protocol, if at all18:17
keriothe IRC protocol doesn't deal with it i think18:18
kerioi mean, there's no specified timeout18:18
DocScrutinizer05at least xchat has it under net_*, not under irc_*18:18
*** hbib has joined #maemo-ssu18:24
*** hbib has quit IRC18:40
*** hbib has joined #maemo-ssu18:42
*** radekp has quit IRC18:46
*** dos1 has joined #maemo-ssu18:55
*** dos1 has joined #maemo-ssu18:55
ShadowJKThe irc server independently decides how often to send pings towards clien (if any)t, the client independently decides how often to send pings towards server, if any.18:59
*** FIQ has quit IRC19:00
ShadowJKxchat in maemo was patched to remove most timers, so all pinging is disabled by default.19:00
DocScrutinizer05DAMN! who decided THAT to be a good idea?19:01
ShadowJKBecause it ate humongous amounts of power before that change19:02
DocScrutinizer05I can't see any reasonable rationale behind that19:02
ShadowJKThere were about half a dozen 1s timers, iirc19:02
DocScrutinizer05it still spins in a poll() = timeout loop with ~2s loop time19:03
ShadowJKnet_ping_timeout is probably not even meant to send periodical pings19:03
DocScrutinizer05I don't care if it sends pings19:03
DocScrutinizer05it however shall notice missing inbound pings from server, or otherwise detect that server lost connection19:04
DocScrutinizer05this worked a year or max 2 years ago, nof it's fubar19:04
DocScrutinizer05now*19:04
DocScrutinizer05whoever decided to implement that patch err botch for sure didn't do a clever thing19:05
ShadowJKxchat doesn't know how often the server intends to send pings, or if it will send pings at all.19:05
ShadowJKThat it ever worked on your network was probably a coincidence or accident :P19:06
DocScrutinizer05well, that's why I thought it sends pings itself, and period should be the net_ping_timeout19:06
DocScrutinizer05no, definitely no coincidence19:06
DocScrutinizer05I carefully tuned it to work like it should19:07
ShadowJKAmusingly, googling turns up people on hexchat with same "issue"19:07
*** FredrIQ has joined #maemo-ssu19:07
*** okias has joined #maemo-ssu19:08
DocScrutinizer05and xchat never "ate battery like mad" om my device, see bq27200 logs on wiki power19:08
ShadowJKWe didn't have bq27200 access whenever xchat was ported19:09
DocScrutinizer05irrelevant19:09
DocScrutinizer05I had a working xchat and I metered it with bq27200.sh19:09
ShadowJKxchat hasn't been modified since 2009 or so anyways :P19:09
DocScrutinizer05then your whole story about removed timers is moot19:10
DocScrutinizer05since I told that my xchat worked a 2 years ago19:10
ShadowJKYeah that stuff was all done in Maemo4 and Maemo5 2009 until powertop showed saner number of wakeups19:11
ShadowJKI dont think xchat has been touched since19:11
*** FredrIQ has quit IRC19:13
*** FredrIQ has joined #maemo-ssu19:13
*** FredrIQ is now known as FIQ19:13
ShadowJKxchat on PC behaves the same, I just tried set net_ping_timeout to 10, and nothing is sent19:19
*** FIQ has quit IRC19:19
*** FIQ has joined #maemo-ssu19:19
*** BCMM has joined #maemo-ssu19:21
ShadowJKugh, actually, it causes reoccurring disconnects, since no ping is sent, no pings can be received,  it is now is on a 10s reconnect cycle19:22
ShadowJKlol19:22
*** LauRoman has joined #maemo-ssu19:23
DocScrutinizer05most weird stuff: the only things i changed on N900 were: "net_ping_timeout = 90" -> "net_ping_timeout = 301" (SIC!), and replacing CSSU wlancond by a two years old orginal version. which made xchat re-register after ~25min instead of 60min19:23
DocScrutinizer05I should try /set net_ping_timeout 600 and see if it reconnects after 5 minutes then19:25
ShadowJKTurning on gui_lagometer makes it send stuff every 10s or so on PC19:25
ShadowJKI use /timer -repeat 0 600 allserv ping19:25
ShadowJKon N900, to send a ping every 10 minutes19:25
DocScrutinizer05oooooh! lag-o-meter!!19:25
DocScrutinizer05I think I disabled that19:25
DocScrutinizer05DANG!19:26
DocScrutinizer05(/timer) niiiice!19:26
DocScrutinizer05but... does it notice when ping fails? and does it reconnect then?19:27
DocScrutinizer05lemme find where's that goddamn lagometer option19:28
ShadowJKIt would take 5 minutes for tcp to timeout, or if the other end is actually alive, it would probably send a RST and it'd fail immediately19:28
ShadowJK/set gui_lagometer19:28
DocScrutinizer05didn't use that, I'm sure19:29
DocScrutinizer05erheehee#@!!$%  line 54: gui_lagometer = 019:30
DocScrutinizer05but I guess I used settings19:30
*** okias has quit IRC19:33
DocScrutinizer51ok19:33
DocScrutinizer05so, I just 2roamed" wlan->gprs19:34
*** amizraa has quit IRC19:44
DocScrutinizer511836 recdonnected19:45
DocScrutinizer05so it took 3 minutes when lagometer = 119:46
DocScrutinizer05miracle solved19:46
DocScrutinizer05problem spotted - now how to eliminate it?19:47
DocScrutinizer05seems net_ping_timeout just sets a threshold for lagometer, eh?19:49
DocScrutinizer05no lagometer, no threshold, no timeout, no reconnect19:49
*** amizraa has joined #maemo-ssu19:51
DocScrutinizer05what we actually would want is a config parameter for ping interval of lagometer, while lagometer=1|0 SHALL only be a GUI thing19:51
DocScrutinizer05ShadowJK: thanks a megaton!19:51
*** sixwheeledbeast has quit IRC19:54
*** sixwheeledbeast has joined #maemo-ssu19:55
ShadowJKI wonder if net_ping_timeout also works on pings sent with /timer19:58
DocScrutinizer05that's what I asked19:59
DocScrutinizer05[2014-02-11 18:27:27] <DocScrutinizer05> but... does it notice when ping fails? and does it reconnect then?19:59
*** ototo is now known as zz_ototo20:02
*** zz_ototo is now known as ototo20:03
*** ototo is now known as zz_ototo20:06
*** zz_ototo is now known as ototo20:12
*** ototo is now known as zz_ototo20:13
*** zz_ototo is now known as ototo20:14
*** ototo is now known as zz_ototo20:20
*** zz_ototo is now known as ototo20:38
*** sunny_s has quit IRC21:07
*** NishanthMenon has quit IRC21:24
*** FIQ has quit IRC21:25
*** NishanthMenon has joined #maemo-ssu21:25
*** Guest21837 has joined #maemo-ssu21:30
*** Guest21837 has quit IRC21:40
*** FredrIQ has joined #maemo-ssu21:46
*** FredrIQ is now known as Guest4754921:46
*** Guest47549 has quit IRC21:48
*** FIQ- has joined #maemo-ssu21:50
*** BCMM has quit IRC22:53
*** honestly has joined #maemo-ssu23:12
*** okias has joined #maemo-ssu23:20
*** NIN101 has quit IRC23:24
*** lizardo has quit IRC23:29
« Monday, 2014-02-10 Index Wednesday, 2014-02-12 »

Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!