**** BEGIN LOGGING AT Wed Nov 07 03:00:02 2012
Nov 07 05:44:14 <gogasan> hi! question: how can i access to value of brightness in nokia N900/maemo5?
Nov 07 05:44:37 <gogasan> such as 'cat /blah/blah/blah'
Nov 07 05:55:46 <gogasan> no ideas?.. ?(
Nov 07 07:03:51 <Sicelo> congrats to our new Council
Nov 07 07:03:56 <Sicelo> \./
Nov 07 07:04:45 <Sicelo> topic needs adjusting
Nov 07 10:17:07 <MrPingu> meh, xbindkeys not so batteryfriendly :(
Nov 07 10:23:12 <vi_> MrPingu: ...
Nov 07 10:23:16 <vi_> MrPingu: yes it is.
Nov 07 10:23:48 <vi_> MrPingu: what is the problem
Nov 07 10:24:14 <vi_> ?
Nov 07 10:24:47 <MrPingu> It's the 1st application listed in my powertop :(
Nov 07 10:27:25 <MrPingu> and it's not getting in C4 state 
Nov 07 10:29:55 <MrPingu> vi_: where did you get xbindkeys from? The package in the repos is empty
Nov 07 10:32:09 <MrPingu> Maybe my binary is faulty?
Nov 07 10:32:44 <MrPingu> Hard to believe but something has to cause my xbindkeys go crazy
Nov 07 10:33:50 <vi_> MrPingu: I got xbindkeys from an external source.
Nov 07 10:34:03 <vi_> I cannot remember where.
Nov 07 10:34:35 <vi_> ALthough if you just wget the debian wheezy armel package and use the binary from that I imagine it would work.
Nov 07 10:35:12 <vi_> Or I could send you the binary?
Nov 07 10:35:43 <MrPingu> I got it somewhere from TMO, but can't remember either
Nov 07 10:35:57 <vi_> If it is going nuts, that could imply you have configured it incorrectly.
Nov 07 10:36:14 <vi_> Also, is it a persistant problem or has it just happened this once?
Nov 07 10:36:24 <vi_> Is there an xbindkeys in the repo?
Nov 07 10:36:45 <MrPingu> extras-devel, but it's a 0byte package :P
Nov 07 10:37:27 <MrPingu> I believe it happened since I put a script to event.d for booting up xbindkeys automatically
Nov 07 10:37:45 <vi_> MrPingu: Then that might be your problem.
Nov 07 10:38:04 <vi_> I have xbindkeys running ALL the time with no issues.
Nov 07 10:38:17 <vi_> I will wager that we have the same binary (found on tmo).
Nov 07 10:38:40 <MrPingu> exec run-standalone.sh su user -c /opt/xbindkeys/xbindkeys
Nov 07 10:38:55 <MrPingu> That's my script, anything wron with that line, then?
Nov 07 10:39:18 <MrPingu> Started and stopped on hildon-desktop
Nov 07 10:40:05 <vi_> I do not know, I start it from /etc/X11/Xsession.post/80fullscreen
Nov 07 10:40:11 <vi_> #!/bin/sh
Nov 07 10:40:11 <vi_> xbindkeys -f /home/user/.xbindkeysrc
Nov 07 10:40:19 <vi_> ^which contains that
Nov 07 10:42:07 <Sicelo> also check the logs for this channel. i seem to remember someone once had this very issue here before
Nov 07 10:43:13 <MrPingu> vi_: what are these numbers in that folder for?
Nov 07 10:43:20 <MrPingu> some kind of order?
Nov 07 10:50:15 <MrPingu> Sicelo: thanks, found it
Nov 07 10:50:30 <vi_> MrPingu: the numbers define the order that the scripts are excuted in.
Nov 07 10:51:04 <MrPingu> From what I read there, event.d fsck something up
Nov 07 10:51:10 <MrPingu> http://mg.pov.lt/maemo-irclog/%23maemo.2012-05-26.log.html
Nov 07 10:51:11 <vi_> I have used 80 as this makes it one of the last things to be executed.
Nov 07 10:51:31 <vi_> I believe xbindkeys SHOULD be launched from xsession anyway.
Nov 07 10:51:43 <vi_> ideologicaly anyway.
Nov 07 10:53:20 <MrPingu> I just noticed, why are some files there not marked executable?
Nov 07 10:53:47 <vi_> on xsesson.post?
Nov 07 10:53:50 <vi_> NFC.
Nov 07 10:54:10 <MrPingu> Yeah
Nov 07 10:54:52 <MrPingu> Thanks, vi_
Nov 07 10:55:09 <MrPingu> I got to go now, driving lesson
Nov 07 10:55:37 <vi_> GL!
Nov 07 11:24:01 * vi_ fires up the coffee machine
Nov 07 11:43:26 <vi_> apt-get remove osso-systemui-tklock
Nov 07 11:43:36 <vi_> reboot
Nov 07 11:43:38 <vi_> ...
Nov 07 11:43:58 <vi_> c'mon baby, dont you quit on me now!
Nov 07 11:46:13 <chem|st> DocScrutinizer51: grats...
Nov 07 11:47:12 <vi_> chem|st: yo
Nov 07 11:47:59 <chem|st> vi_: yo'bro
Nov 07 11:48:21 <chem|st> DocScrutinizer51: and as a present you get a 1 month bann of estel!
Nov 07 11:48:37 <vi_> chem|st: wait, what?
Nov 07 11:48:37 * chem|st did not ban him btw
Nov 07 11:48:42 <vi_> what has happened??
Nov 07 11:49:12 <chem|st> started a second account and posted with it
Nov 07 11:49:31 <vi_> chem|st: Holy shit, that is proper crazy behaviour.
Nov 07 11:49:36 <chem|st> infraction points added up to ban period of 1 month
Nov 07 11:49:54 <vi_> was his first account banned at the time?
Nov 07 11:50:10 <chem|st> he blames me as if I have personal interests in getting rid of him
Nov 07 11:50:21 <chem|st> vi_: sure
Nov 07 11:50:53 <vi_> how did you identify his second account?  Identical IPs?
Nov 07 11:51:18 <chem|st> to make clear I did just want to have him cool down a bit I added only 2 infractions to ban him for 3 days only, with a warning that it could be worse
Nov 07 11:51:41 <vi_> chem|st: I have complete fait and respect for your actions as a TMO mod.
Nov 07 11:51:48 <chem|st> Letsee backwards eesteL, + identical IPs
Nov 07 11:52:15 <vi_> are any of his posts still up?
Nov 07 11:52:47 <chem|st> most of the time I look the other way when people start a flamewar... but having several people report him for the same post becomes a need to act
Nov 07 11:52:54 <chem|st> vi_: no posts deleted
Nov 07 11:54:05 <vi_> did you mean:
Nov 07 11:54:11 <vi_> no, posts deleted
Nov 07 11:54:14 <vi_> or
Nov 07 11:54:20 <vi_> No! Posts deleted.
Nov 07 11:54:33 <vi_> no posts deleted.
Nov 07 12:00:51 <vi_> apt-get remove osso-systemui-tklock <--utter fail
Nov 07 12:01:05 <chem|st> vi_: as I wrote it... to elaborate "no post got deleted"
Nov 07 12:01:11 <vi_> lockscreen no longer works.
Nov 07 12:08:13 <vi_> and softpoweroff does not ignore touchscreen inputs.
Nov 07 12:32:37 <MrPingu> vi_ are you dissecting your maemosoftware?
Nov 07 12:36:02 <vi_> no.
Nov 07 12:36:22 <vi_> I *just* want a way to lock/unlock the n900 with just the powerbutton.
Nov 07 12:36:37 <vi_> No swipe the screen to unlock horse shit.
Nov 07 12:36:45 <vi_> jonwil: I SUMMON THEE.
Nov 07 12:37:41 <vi_> It would seem lockscreen is osso-systemui-tklock.
Nov 07 12:37:49 <vi_> Except it is closed source.
Nov 07 12:38:17 <vi_> If there was just some way to hack it so it would *just* be a screen lock.
Nov 07 12:38:23 <vi_> with no lockscreen.
Nov 07 12:38:40 <vi_> Honestly, the lockscreen is a huge waste of time and space.
Nov 07 12:38:48 <vi_> DOuble press power to lock.
Nov 07 12:38:55 <vi_> double press power to unlock.
Nov 07 12:38:59 <vi_> Is that so hard?
Nov 07 12:41:25 <jonwil> I never did figure out exactly how it works :(
Nov 07 12:42:39 <vi_> Wow, it worked!
Nov 07 12:42:53 <vi_> That is a shame jonwil, at least you tried.
Nov 07 12:42:57 <vi_> Thank you.
Nov 07 12:44:01 <jonwil> I figured out enough that someone who knows more about maemo progamming could probably write something new
Nov 07 12:44:05 <jonwil> but thats about it
Nov 07 12:46:06 <SpeedEvil> vi_: I just never lock it, but use the lock switch on the side to unlock
Nov 07 12:46:36 <vi_> SpeedEvil: You newver lock it?
Nov 07 12:46:46 <SpeedEvil> no
Nov 07 12:46:49 <vi_> How do you stop the contents of your pocket messing your desktop up?
Nov 07 12:46:54 <SpeedEvil> I never see the lock screen
Nov 07 12:47:01 <vi_> aaah yes.
Nov 07 12:47:06 <SpeedEvil> I always lock it with the awitx on the side
Nov 07 12:47:13 <SpeedEvil> switch
Nov 07 12:47:19 <vi_> But I want to be able to unlock it by the power button.
Nov 07 12:47:31 <SpeedEvil> fair enough
Nov 07 12:47:58 <vi_> One handed operation you know.
Nov 07 12:48:09 <vi_> for when I am jerkin it and need to make a call.
Nov 07 12:58:01 <chem|st> woohoo http://media.steampowered.com/client/installer/steam.deb
Nov 07 13:05:12 <chem|st> lardman: you had an ARGZ error while compiling libchamplain... how did you get rid of it
Nov 07 13:07:10 <merlin1991> hm they made REALLY sure that this deb only runs on ubuntu
Nov 07 13:07:14 <merlin1991> the depdns are evil
Nov 07 13:07:24 <chem|st> lardman: I try to compile modest for cssu stable... I did compile it successfully then I installed some python stuff then I reset the git folder and now I am stuck with aclocal: macro `gl_FUNC_ARGZ' required but not defined
Nov 07 13:07:41 <chem|st> merlin1991: does it?
Nov 07 13:07:51 <chem|st> did not trys to install yet
Nov 07 13:08:08 <merlin1991> multiarch-support (>= 2.15-0ubuntu10.2) and generally tons of >= depends
Nov 07 13:08:47 <chem|st> wtf is multiarch-support ?
Nov 07 13:10:05 <SpeedEvil> vi_: I find lock switch easier than power button
Nov 07 13:10:17 <chem|st> ah I get it
Nov 07 13:10:59 <jonwil> I suspect they are specifically targeting Ubuntu for now so their tech support is minimized
Nov 07 13:11:05 <vi_> SpeedEvil: with one hand?
Nov 07 13:11:41 <chem|st> jonwil: means I need to get some ubuntu on a USB3 stick and get it booting on my usb3 hub
Nov 07 13:12:09 <vi_> merlin1991: I got excited till I saw the 'ubuntu only' thing.
Nov 07 13:12:12 <chem|st> I'll try ramdisk instead
Nov 07 13:12:18 <vi_> Why not just make it for debian?
Nov 07 13:12:19 <jonwil> I do wonder how they have done the DRM on the Linux version
Nov 07 13:12:55 <jonwil> and how they prevent someone with e.g. a nice copy of GDB stripping the protection
Nov 07 13:13:52 <vi_> jonwil: I don't know, but you are probably the man to 'fix' it.
Nov 07 13:14:22 <jonwil> I dont care about Steam or Steam games though
Nov 07 13:14:30 <jonwil> Never had any interest in playing any of the Valve games
Nov 07 13:14:47 <vi_> ...
Nov 07 13:14:53 <vi_> not even half life 2?
Nov 07 13:14:57 <jonwil> nope
Nov 07 13:14:57 <Pali> you can check in your process if you are being debugged
Nov 07 13:15:10 <vi_> but
Nov 07 13:15:13 <vi_> but
Nov 07 13:15:15 <vi_> HL2
Nov 07 13:15:22 <jonwil> There are solutions to that, especially if you can make whatever kernel and libc changes you like
Nov 07 13:15:35 <Pali> yes, of cource
Nov 07 13:16:03 <Pali> but this know only few people
Nov 07 13:21:10 <jonwil> Linux guys are smarter than most
Nov 07 13:31:50 <deepy\SIGSEGV> That statement in itself is based on false assumptions
Nov 07 13:50:50 <lardman> chem|st: pong
Nov 07 13:52:26 <lardman> chem|st: re champlain was a long time ago, can you give me some more background on your error and I can see if I've still got the build directory scudding around somewhere
Nov 07 14:58:15 <dfaure> what's the name of the executable for the image viewer on the N9 ?
Nov 07 14:58:53 <dfaure> ah, mediaviewer works
Nov 07 15:10:04 <chem|st> lardman: I run in to a missing ARGZ.m4 as libtools is outdated
Nov 07 15:10:09 <chem|st> I have no clue
Nov 07 15:10:58 <chem|st> it is mystic behaviour of build env to build something just fine and the next second you have an error
Nov 07 15:12:05 <chem|st> Running aclocal-1.8...
Nov 07 15:12:05 <chem|st> aclocal: macro `gl_FUNC_ARGZ' required but not defined
Nov 07 15:12:05 <chem|st> make: *** [configure-stamp] Error 1
Nov 07 15:12:25 <chem|st> last 3 automake lines
Nov 07 15:12:34 <lardman> hmm, and you say I had this problem?
Nov 07 15:13:11 <lardman> http://mg.pov.lt/maemo-irclog/%23maemo.2009-11-04.log.html ah, so I did
Nov 07 15:13:12 <chem|st> http://mg.pov.lt/maemo-irclog/%23maemo.2009-11-04.log.html
Nov 07 15:13:17 <lardman> :)
Nov 07 15:13:18 <chem|st> :)
Nov 07 15:14:46 <lardman> is my package still in the repo?
Nov 07 15:14:54 <lardman> or is this where you're grabbing it from?
Nov 07 15:14:57 <chem|st> the thing is I did not recognize anything wierd from dependencies which got pulled in with python-dev so I proceeded, now I do not know what was pulled in anymore and have no idea how to find out to uninstall or reinstall something/anything etc... lost
Nov 07 15:15:26 <chem|st> lardman: I'm not trying to compile yours... I try to compile modest
Nov 07 15:15:33 <lardman> oh I see
Nov 07 15:15:43 <chem|st> it is a libtool or automake issue afaik
Nov 07 15:15:56 <lardman> yeah and apparently something that doens't happen with a clean build
Nov 07 15:16:03 <chem|st> we ran into intltool issues earlier
Nov 07 15:16:46 <chem|st> there was a pointer for a directory wrong as versions of automake got mixed
Nov 07 15:17:05 <chem|st> installing them in the right order did fix that
Nov 07 15:17:33 <chem|st> took me quiet a while to find that out 
Nov 07 15:18:05 <lardman> I'm afraid I have no idea, it was a long time ago, best bet is probably to see whether I did any trickery in the debian/rules that was uploaded with the package in order to make it build
Nov 07 15:18:06 <chem|st> not the missing dir link but the right procedure of installing automake versions
Nov 07 15:19:13 <chem|st> ehrm it is still in configuration steps
Nov 07 15:19:44 <lardman> that's handled by debian/rules too
Nov 07 15:19:59 <lardman> unless the package I uploaded could really only be built once
Nov 07 16:47:33 <DocScrutinizer05> (([2012-11-07 12:46:13] <chem|st> DocScrutinizer51: grats...)) thanks
Nov 07 16:48:03 <DocScrutinizer05> on what particularly though?
Nov 07 16:48:51 <freemangordon> http://talk.maemo.org/showpost.php?p=1291506&postcount=252
Nov 07 16:48:53 <freemangordon> LOL
Nov 07 16:49:05 <DocScrutinizer05> ((<chem|st> DocScrutinizer51: and as a present you get a 1 month bann of estel!)) sounds fine to me, but I'm not sure I can accept that present. Maybe better donate it to community
Nov 07 16:50:18 <vi_> freemangordon: cherry?
Nov 07 16:50:29 <freemangordon> I was wondering how Pali earned the money for all n900s he has, now it is clear :D:D:D
Nov 07 16:50:36 <freemangordon> vi_: maybe
Nov 07 16:52:27 <DocScrutinizer05> actually, do we have not-my-nokia cherry killer 'bugfix' in CSSU? Shouldn't we?
Nov 07 16:52:51 <vi_> DocScrutinizer05: It is too late by then.
Nov 07 16:53:05 <DocScrutinizer05> not really
Nov 07 16:53:10 <vi_> By the time a user has gotten to cssu they *probably* have already used gsm.
Nov 07 16:53:10 <freemangordon> well, I haven't heard af any recent harm done by cherry. Neither we have a bug report for that
Nov 07 16:53:45 <DocScrutinizer05> sure too late for past SMS, but not too late to nuke the shite off the system, so it doesn't get activated again by accident
Nov 07 16:53:58 <vi_> DocScrutinizer05: very good point.
Nov 07 16:54:14 <vi_> WTF were they thinking?
Nov 07 16:54:23 <freemangordon> I wonder, why not everybody got those problems. I swear I was asked to enable it and I dissmised the dialog by tapping outside it
Nov 07 16:54:41 <vi_> freemangordon: orly?
Nov 07 16:54:42 <freemangordon> end AFAIK no messages sent here
Nov 07 16:54:45 <freemangordon> yep
Nov 07 16:55:31 <vi_> AFAIU it fired up automatically the first time you connected to a gsm network and the 'firstboot' flag was set.
Nov 07 16:55:49 <DocScrutinizer05> plus we *could* add a recommendation to remove SIM before flashing any new clean system, and only inserting it again after updating to CSSU
Nov 07 16:55:49 <freemangordon> well, not exactly "enable", but you know that big dialog with EULA or whatever
Nov 07 16:56:28 <freemangordon> But deffinitely, I was asked. Don;t ask me for the details, it was 2 years ago :D
Nov 07 16:57:22 <DocScrutinizer05> the nasty detail: this kicks in again whenever you delete the cherry flag file
Nov 07 16:57:26 <vi_> DocScrutinizer05: Ideally, a cssu ready pre-rolled firmware with all the shit taken out.
Nov 07 16:58:31 <freemangordon> DocScrutinizer05: does that happen on "factory reset"?
Nov 07 16:59:29 <DocScrutinizer05> nfc
Nov 07 16:59:41 <vi_> A really freaky thing I have never gotten to the bottom of is /usr/share/sounds
Nov 07 16:59:42 <DocScrutinizer05> never used or looked into 'factory reset'
Nov 07 16:59:53 <vi_> it is ~9mb on rootfs.
Nov 07 16:59:58 <DocScrutinizer05> for sure it kicks in on flashing eMMC
Nov 07 17:00:04 <DocScrutinizer05> err, wait
Nov 07 17:00:21 <vi_> even if you move it to /opt and symlink it back.
Nov 07 17:00:27 <vi_> It comes back after boot.
Nov 07 17:00:34 <DocScrutinizer05> is that cherry thing on /home or somewhere in /etc?
Nov 07 17:00:43 <freemangordon> vi_: whaat?
Nov 07 17:00:53 <vi_> DocScrutinizer05: home I believe.
Nov 07 17:00:58 <vi_> freemangordon: fo reals.
Nov 07 17:01:34 <DocScrutinizer05> vi_: check auto-optify config, might get de-optified
Nov 07 17:01:41 <freemangordon> DocScrutinizer05: disagree, I flashed eMMC a couple of months ago. AFAIk there were no SMSes
Nov 07 17:01:57 <vi_> freemangordon: Do you still have cherry installed?
Nov 07 17:02:15 <freemangordon> don;t see a reason I don;t have it
Nov 07 17:02:19 <freemangordon> *why
Nov 07 17:02:26 <freemangordon> lemmme check
Nov 07 17:02:52 <vi_> freemangordon: because it is a massive pile of shit seems like a good reason not to have it.
Nov 07 17:03:05 <DocScrutinizer05> hehe
Nov 07 17:03:14 <DocScrutinizer05> ~jrtools
Nov 07 17:03:14 <infobot> it has been said that jrtools is http://wiki.maemo.org/User:Joerg_rw/tools
Nov 07 17:03:17 <DocScrutinizer05> sorry
Nov 07 17:03:34 <freemangordon> ii  cherry                                              0.25-1+0m5                                 Cherry for MyNokia
Nov 07 17:03:40 <DocScrutinizer05> # kill that cherry PITA, before it sends SMS  --  STILL ACTUAL!
Nov 07 17:03:42 <DocScrutinizer05> # see http://wiki.maemo.org/PR1.2_compulsory_My_Nokia_subscription
Nov 07 17:03:43 <DocScrutinizer05> touch /home/user/.cherry_state
Nov 07 17:04:05 <vi_> apt-get purge cherry
Nov 07 17:04:13 <DocScrutinizer05> :nod:
Nov 07 17:04:20 <vi_> it uninstalls cleanly.
Nov 07 17:04:30 <vi_> They got that bit right
Nov 07 17:04:31 <DocScrutinizer05> really? not in MP?
Nov 07 17:04:39 <DocScrutinizer05> duh!
Nov 07 17:04:44 <vi_> as far as I recall
Nov 07 17:05:01 <freemangordon> hmm, no /home/user/.cherry_state here
Nov 07 17:05:52 <kerio> DocScrutinizer05: http://maemo.org/packages/package_instance/view/fremantle_ssu_pr1-2_armel/mp-fremantle-generic-pr/10.2010.19-1/ has no cherry anywhere
Nov 07 17:06:01 <vi_> gtg
Nov 07 17:06:03 <vi_> :q
Nov 07 17:06:07 <DocScrutinizer05> apt-cache show mp-fremantle-community-pr|grep cherry  ->NULL; indeed it's no dependency
Nov 07 17:08:03 <DocScrutinizer05> IroN900:~# apt-cache policy  cherry
Nov 07 17:08:05 <DocScrutinizer05> cherry:
Nov 07 17:08:06 <DocScrutinizer05>   Installed: (none)
Nov 07 17:08:08 <DocScrutinizer05>   Candidate: 0.25-1+0m5
Nov 07 17:08:24 <freemangordon> that is really weird
Nov 07 17:08:42 <freemangordon> though iirc chery_state is in /etc
Nov 07 17:08:47 <DocScrutinizer05> I once had not-my-nokia installed
Nov 07 17:09:10 <DocScrutinizer05> [2012-11-07 18:03:40] <DocScrutinizer05> touch /home/user/.cherry_state
Nov 07 17:10:01 <DocScrutinizer05> IroN900:~# apt-cache policy notmynokia
Nov 07 17:10:03 <DocScrutinizer05> notmynokia:
Nov 07 17:10:04 <DocScrutinizer05>   Installed: 1.0+maemo-1
Nov 07 17:14:42 <kerio> DocScrutinizer05: meh, removing cherry is cleaner
Nov 07 17:15:09 <freemangordon> I don't have .cherry_state
Nov 07 17:15:15 <freemangordon> this is really werid
Nov 07 17:16:54 <freemangordon> hmm, maybe it also checks for first boot
Nov 07 17:19:45 <DocScrutinizer05> kerio: I guess removing cherry is all that's done by notmynokia
Nov 07 17:19:54 <kerio> iirc no
Nov 07 17:19:57 <DocScrutinizer05> (plus the settings plugin of course)
Nov 07 17:20:10 <kerio> it just touches .cherry_state every boot
Nov 07 17:20:21 <DocScrutinizer05> fsckng insane
Nov 07 17:20:46 <DocScrutinizer05> well, sorry for that. Not insane, just a poor approach
Nov 07 17:20:55 <kerio> maybe some earlier -pr had cherry as a dependency
Nov 07 17:20:57 <DocScrutinizer05> not radical enough for such a huge POS
Nov 07 17:21:03 <kerio> so you couldn't remove it without botching OS updates from HAM
Nov 07 17:21:16 <DocScrutinizer05> quite possible
Nov 07 17:21:32 <kerio> the -generic-pr doesn't, btw
Nov 07 17:21:38 <DocScrutinizer05> you could however mess up stuff via postinstall scripts ;-)
Nov 07 17:23:33 <DocScrutinizer05> apt-cache show mp-fremantle-generic-pr|grep cherry  -> screensfull of crap
Nov 07 17:25:12 <kerio> DocScrutinizer05: btw, is bme sigstoppable without too many issues?
Nov 07 17:25:20 <DocScrutinizer05> nope
Nov 07 17:25:27 <kerio> hm
Nov 07 17:25:30 <DocScrutinizer05> will cause reboot
Nov 07 17:25:39 <kerio> why?
Nov 07 17:25:40 <DocScrutinizer05> in 60'ish seconds
Nov 07 17:25:50 <kerio> how does dsme check if bme is supposed to be running or not?
Nov 07 17:25:54 <DocScrutinizer05> timeout of some keep-alive stuff
Nov 07 17:26:04 <DocScrutinizer05> iirc
Nov 07 17:27:26 <DocScrutinizer05> I guess the bme devels took special care to ensure bme is up and running, since we see what might happen if it ever fails, on N8x0/diablo
Nov 07 17:27:28 <kerio> apparently /tmp/bme.was.stopped or something
Nov 07 17:27:46 <kerio> oh no, nvm
Nov 07 17:27:53 <kerio> it's a thing in post-stop from upstart maybe
Nov 07 17:28:36 <DocScrutinizer05> kerio: why are HD apps sometimes closing after 120s? It's some keep-alive stuff
Nov 07 17:28:52 <DocScrutinizer05> bme probably talking to dsme via IPC
Nov 07 17:29:07 <kerio> meh
Nov 07 17:29:09 <kerio> wtf is dsme anyway?
Nov 07 17:29:25 <DocScrutinizer05> device status management entity or sth
Nov 07 17:29:58 <DocScrutinizer05> basically it first and foremost does start and survey/monitor processes
Nov 07 17:30:21 <kerio> hm, what does bme_RX-51 -b do?
Nov 07 17:30:39 <DocScrutinizer05> kerio: dsmetool --help
Nov 07 17:31:03 <DocScrutinizer05>   -b, --boottest  Test battery and pre-charge
Nov 07 17:31:08 <kerio> i see
Nov 07 17:31:29 <DocScrutinizer05> some nonsense cruft, for bq24150
Nov 07 17:31:36 <kerio> is it needed?
Nov 07 17:31:52 <DocScrutinizer05> not for battery or bq24150, yes for scripts
Nov 07 17:32:32 <DocScrutinizer05> if it fails, I guess you get that "red indicator failure" issue, which means your battery is totally broken
Nov 07 17:32:42 <DocScrutinizer05> I guess ^^^
Nov 07 17:33:21 <DocScrutinizer05> bq24150 doeswn't need any such stuff, nor does the battery in general
Nov 07 17:33:50 <DocScrutinizer05> or rather: bq24150 does that opaque and invisible, automatically
Nov 07 17:34:29 <DocScrutinizer05> so probably it's another heritage cruft from former OS versions
Nov 07 17:34:56 <DocScrutinizer05> diablo and before, when bme was the only entity to ensure your battery wouldn't explode
Nov 07 17:35:45 <DocScrutinizer05> (N810 charging being completely software controlled, down to pulse width genereation of charger switch transistor, so to say)
Nov 07 17:36:54 <kerio> hahaha what
Nov 07 17:36:59 <kerio> awesome
Nov 07 17:42:01 <DocScrutinizer05> not you see why Nokia been so extremely reluctant and over-anxious regarding anything bme realted. Their sw department simply missed the news that N900 charging got fundamentally sanitized and bme basically no longer needed
Nov 07 17:42:10 <DocScrutinizer05> s/not/now/
Nov 07 17:42:10 <infobot> DocScrutinizer05 meant: now you see why Nokia been so extremely reluctant and over-anxious regarding anything bme realted. Their sw department simply missed the news that N900 charging got fundamentally sanitized and bme basically no longer needed
Nov 07 17:43:03 <DocScrutinizer05> even stskeeps took >one yera to accept that info for true
Nov 07 17:43:18 <DocScrutinizer05> my typing sucks extraordinarily today
Nov 07 17:45:49 <kerio> DocScrutinizer05: what's the worse you can do from the software side?
Nov 07 17:46:02 <kerio> thrash the battery a bit too much?
Nov 07 17:46:17 <DocScrutinizer05> (([2012-11-07 17:54:23] <freemangordon> I wonder, why not everybody got those problems.)) I guess most users not even noticed. Mind you, the SMS got hidden from rt-eventlog db, so never shows up in "sent messages"
Nov 07 17:48:14 <kerio> Pali: without "bme 1.0" your notifier can't figure out the battery is done charging
Nov 07 17:48:50 <kerio> and then i guess that it got confused and i had to reboot to make the applet work properly
Nov 07 17:49:09 <Pali> kerio, what?
Nov 07 17:49:20 <Pali> please write what did you do
Nov 07 17:49:28 <Pali> and where is problem
Nov 07 19:39:40 <vi__> MrPingu: have you used scratchbox?
Nov 07 19:39:46 <vi__> freemangordon: ping
Nov 07 19:39:49 <MrPingu> Yes, I have
Nov 07 19:40:12 <vi__> so I am currently set to x86 target
Nov 07 19:42:06 <vi__> how do I download source code from the debian repos for example?
Nov 07 19:42:26 <vi__> for a simple example, lets consider gnu fortune.
Nov 07 19:42:39 <vi__> A very simple terminal program.
Nov 07 19:42:43 <MrPingu> I use webinterface of debian
Nov 07 19:42:57 <vi__> Do I just wget the source package?
Nov 07 19:43:02 <MrPingu> Yeah
Nov 07 19:43:34 <MrPingu> for ngrep and tcpdump I made, I just downloaded tarball from original site
Nov 07 19:43:51 <Pali> vi__: packages.debian.org
Nov 07 19:44:02 <MrPingu> what pali says
Nov 07 19:44:14 <Pali> find package, click on source and download what you want :-)
Nov 07 19:45:05 <vi__> ok, that is the 'official' best way to do it?
Nov 07 19:45:24 <MrPingu> To change target go into sb-menu
Nov 07 19:45:30 <MrPingu> select target ;)
Nov 07 19:45:36 <vi__> sb-menu?
Nov 07 19:45:57 <vi__> oh wow!
Nov 07 19:46:00 <vi__> sb-menu!
Nov 07 19:46:55 <MrPingu> just issue sb-menu inside scratchbox
Nov 07 19:47:28 <MrPingu> Someone interested in testing hamster and ferret? (sidejacking tools)
Nov 07 19:47:35 <vi__>     You are trying to set yourself up as a middleman to skim some euros off the top?[...]
Nov 07 19:47:38 <vi__> that's the way you would do it i know, i know...
Nov 07 19:47:42 <vi__> what a total fuck
Nov 07 19:52:03 <vi__> Pali: I cannot seem to find source packages on that address pali
Nov 07 19:52:52 <vi__> .dsc is a debian source package?
Nov 07 19:52:57 <MrPingu> Yep
Nov 07 19:53:06 <vi__> what do I do with it?
Nov 07 19:53:19 <MrPingu> Look into it ;)
Nov 07 19:53:22 <vi__> do I simply untar and make?
Nov 07 19:53:25 <MrPingu> It's just a tar
Nov 07 19:53:42 <vi__> or is there a debian specific way of dealing with it?
Nov 07 19:54:38 <MrPingu> Yes, there is and I still need to look into that
Nov 07 19:55:06 <MrPingu> because I just compiled from source and made a deb with dpkg-deb -b
Nov 07 19:55:43 <MrPingu> that isn't the right way :P
Nov 07 19:56:02 <MrPingu> It works good, though
Nov 07 19:56:07 <Pali> you need to download .dsc and .tar file (+diff if available)
Nov 07 19:56:19 <Pali> then do: dpkg-source -x file.dsc
Nov 07 19:56:24 <Pali> go to unpacked directory
Nov 07 19:56:33 <Pali> and call: dpkg-buildpackage -b -rfakeroot
Nov 07 19:57:11 <vi__> AFAIK I am supposed to used apt-get source <package-name>
Nov 07 19:57:21 <vi__> however that returns nothing I want.
Nov 07 19:57:40 <vi__> I asssume this is because I need to add debian source repos to ap sources.list
Nov 07 19:57:49 <vi__> is this correct?
Nov 07 19:58:26 <MrPingu> I just download them manually but that could do the job too, I guess?
Nov 07 19:58:35 <Pali> do not add any other repositories to sources.lists
Nov 07 19:58:58 <Pali> download files from packages.debian.org and do above commands ^^^
Nov 07 19:59:16 <Pali> dpkg-source -x file.dsc will unpack dsc+tar+diff file
Nov 07 19:59:19 <vi__> so I have to manually get the package and ALL the dependencies?
Nov 07 19:59:28 <Pali> yes
Nov 07 19:59:36 <vi__> lame
Nov 07 19:59:43 <Pali> there is no other way
Nov 07 19:59:44 <MrPingu> Pali: Thanks, I will try to get ngrep + updated libpcap + updated tcpdump in repos asap
Nov 07 20:00:31 <vi__> MrPingu: nice one.
Nov 07 20:00:41 <vi__> Shoot for the moon, do nmap as well!
Nov 07 20:00:59 <vi__> Pali: where does optification come in?
Nov 07 20:01:04 <Pali> btw, there is http://maemo.org/packages/view/libpcap-dev/
Nov 07 20:01:19 <Pali> vi__, create file debian/optify and write here auto
Nov 07 20:01:27 <Pali> echo auto > debian/optify
Nov 07 20:01:39 <Pali> garage autobuilder then optify package
Nov 07 20:01:54 <MrPingu> really, I just symlinked everyfile in postinstall manually ;o
Nov 07 20:02:02 <Pali> do not need this
Nov 07 20:02:16 <Pali> and this is bad
Nov 07 20:02:22 <Pali> to do it in postinst
Nov 07 20:02:35 <Pali> because you do not have to have space for unpack to rootfs!!
Nov 07 20:02:47 <Pali> better do: echo auto > debian/optify
Nov 07 20:03:07 <MrPingu> Pali, I did place the binary in opt
Nov 07 20:03:16 <Pali> ok
Nov 07 20:03:40 <MrPingu> but symlink is created in postinst
Nov 07 20:03:46 <Pali> why??
Nov 07 20:03:52 <Pali> just add symlink to deb package
Nov 07 20:04:02 <MrPingu> because, it's my first package ever
Nov 07 20:04:48 <MrPingu> I will try to get the "proper" version in the repos 
Nov 07 20:05:00 <MrPingu> with proper I mean, your way of packaging :)
Nov 07 20:05:09 <Pali> edit debian/links
Nov 07 20:05:13 <Pali> and add here:
Nov 07 20:05:45 <Pali> opt/real_binary usr/bin/symlinked_binary
Nov 07 20:05:51 <Pali> MrPingu ^^^
Nov 07 20:06:35 <MrPingu> :D
Nov 07 20:07:10 <Pali> and uncommnet dh_link in debian/rules (if is commented)
Nov 07 20:07:41 <vi__> Pali: this is some good tips pali! thank you.
Nov 07 20:07:55 <vi__> I am going to compile program 'pi'
Nov 07 20:08:02 <vi__> it calculates pi.
Nov 07 20:08:16 <hatseflats> hey everyone
Nov 07 20:08:19 <MrPingu> Start simple :)
Nov 07 20:08:27 <MrPingu> Hi hatseflats
Nov 07 20:08:30 <vi__> I will try to do it with both thumb2 and armel.
Nov 07 20:08:35 <vi__> yo dawg.
Nov 07 20:08:51 <vi__> and compare the performance of both.
Nov 07 20:09:02 <hatseflats> I've got a longtime issue with my n810, I blamed the battery, but now I think it might be the device itself
Nov 07 20:09:14 <kerio> vi__: printf("π\n");
Nov 07 20:09:16 <kerio> DONE
Nov 07 20:09:25 <vi__> if there is no performance difference (due to lack of neon optimisation) I will use some elf thingy to see that it works.
Nov 07 20:09:38 <MrPingu> vi__: I will come back in an hour, I see 3 new apps in the repos, deal?
Nov 07 20:09:50 <vi__> kerio: you are pr0 l33t pr0gram3r.
Nov 07 20:09:56 <hatseflats> basically, I can't turn it 'on' without the powercord in, and when it is, it goes into a continuous reset cycle, the nokia logo will show up, stick around for a second or two, it'll shut off, and start all over again
Nov 07 20:10:18 <kerio> hatseflats: reflash it
Nov 07 20:10:22 <vi__> hatseflats: I have never had an n8x0.
Nov 07 20:10:30 <vi__> However I would be inclined to reflash!
Nov 07 20:10:38 <hatseflats> kerio: that's nice, but you can't reflash if it doesn't even allow you to get into debug mode
Nov 07 20:10:57 <kerio> dafuq
Nov 07 20:11:00 <kerio> you can brick a n8x0?
Nov 07 20:11:04 <hatseflats> I guess I can
Nov 07 20:11:16 <hatseflats> but I'm not sure I bricked it, or just blew 4 batteries
Nov 07 20:11:23 <MrPingu> vi__: you need to manually pass thumb2 to compiler 
Nov 07 20:12:00 <MrPingu> Don't ask me how, as I didn't do it myself yet :P
Nov 07 20:12:36 <kerio> -mthumb -mtune=cortex-a8
Nov 07 20:12:42 <kerio> or something
Nov 07 20:12:46 <kerio> freemangordon: do you also use -mtune?
Nov 07 20:13:07 <freemangordon> no, i usually use -mcpu
Nov 07 20:13:39 <kerio> oh, mcpu is stricter
Nov 07 20:13:51 <freemangordon> when I use anything at all
Nov 07 20:13:53 <freemangordon> :)
Nov 07 20:14:06 <kerio> we need moar performance! :(
Nov 07 20:14:14 <freemangordon> I don;t think -mcpu makes any difference on n900
Nov 07 20:14:21 <kerio> why not? it's a cortex a8
Nov 07 20:14:27 <kerio> it's written on the underside of the monitor!
Nov 07 20:14:39 <freemangordon> monitor?
Nov 07 20:14:44 <freemangordon> what device do you have?
Nov 07 20:14:47 <kerio> screen, or whatever
Nov 07 20:14:50 <freemangordon> :P
Nov 07 20:14:59 <MrPingu> Haha
Nov 07 20:15:07 <kerio> http://en.wikipedia.org/wiki/Computer_monitor
Nov 07 20:15:32 <hatseflats> hmm, seems like it's a known failure, bootlooping
Nov 07 20:15:44 <hatseflats> caused by reflashing on low battery...
Nov 07 20:15:59 <freemangordon> kerio: my point is that it makes no difference if you compile with or without -mcpu=cortex-a8 
Nov 07 20:16:22 <kerio> really? :o
Nov 07 20:16:28 <freemangordon> at least for arm/thumb2 only code
Nov 07 20:16:52 <freemangordon> at least that is what i have seen
Nov 07 20:16:56 <kerio> freemangordon: btw, are you sure you're enabling both neon and vfpv3?
Nov 07 20:17:11 <freemangordon> neon implies vfp afaik
Nov 07 20:18:03 <freemangordon> and armv7-a implies vfpv3 if only -mfpu=vfp is passed
Nov 07 20:18:14 <freemangordon> might be wrong as well
Nov 07 20:18:30 <freemangordon> but there are not so much programs using FP
Nov 07 20:18:40 * freemangordon is afk
Nov 07 20:19:49 <kerio> ohai iDont 
Nov 07 20:19:53 <kerio> sup
Nov 07 20:20:04 <iDont> hi kerio
Nov 07 20:20:31 <iDont> good, received two patches to introduce Diablo support in busybox-power :)
Nov 07 20:20:39 <iDont> and how are you?
Nov 07 20:20:44 <hatseflats> stupid nokia -_- why design a device that simply can't charge without an bootable OS
Nov 07 20:20:44 <kerio> all good
Nov 07 20:20:56 <iDont> great :)
Nov 07 20:21:06 <kerio> hatseflats: dude, the n8x0 can be flashed and/or boot without a battery anyway
Nov 07 20:21:23 <kerio> and (i discovered this just today) charging is quite the big deal on the n8x0
Nov 07 20:21:38 <hatseflats> the resources on the web say otherwise, how does that work?
Nov 07 20:21:58 <kerio> iDont: i've seen the latest bb-p for fremantle - i have to say, i don't really like the divert to rootfs
Nov 07 20:22:16 <kerio> iDont: can't you just divert and rename to /opt/busybox-power?
Nov 07 20:22:19 <hatseflats> I *can* get my hands on a standalone charger for these batteries for about 20 bucks, that's really my last resort
Nov 07 20:22:43 <kerio> hatseflats: i don't have a n8x0, so i can't really help you - i'm only repeating what i heard
Nov 07 20:22:52 <timmy> im going to flash my n900 but im facing this message: USB device found found at bus 001, device address 012.
Nov 07 20:22:52 <timmy> Error claiming USB interface: Device or resource busy
Nov 07 20:22:52 <inz> Damn, ownCloud on N810 is quite slow.
Nov 07 20:23:05 <kerio> but there's a magic ritual that can be used to summon an ancient demon that can help you
Nov 07 20:23:12 <kerio> -ahem-
Nov 07 20:23:15 <kerio> DocScrutinizer05: *poke*
Nov 07 20:23:18 <hatseflats> inz: pretty much anything is slow on the n810
Nov 07 20:23:40 <iDont> kerio, rationale is that /opt is on a different partition, which *might* not be available at some point (although that's pretty unlikely in Maemo, since you won't be able to boot then)
Nov 07 20:24:17 <kerio> iDont: apt is running, that means that the system is kinda booted
Nov 07 20:24:41 <kerio> at least, it means that opt is mounted
Nov 07 20:24:54 <iDont> you've got a point there
Nov 07 20:25:00 <inz> hatseflats, yeah, I just thought it would make a decent home web server, but seems I was wrong
Nov 07 20:25:10 <inz> hatseflats, or then I'll need something not written in PHP =)
Nov 07 20:25:13 <kerio> iDont: also, there's a way to specify a diversion for everyone except a specific package
Nov 07 20:25:15 <hatseflats> that too :p
Nov 07 20:25:30 <hatseflats> I mean, bare bones the hardware is pretty beefy for a mobile device of it's time
Nov 07 20:25:49 <hatseflats> but hildon is like pushing a car up a hill
Nov 07 20:25:50 <kerio> inz: rpi or dreamplug
Nov 07 20:26:12 <iDont> kerio, what's wrong with the current diversion setup (except for the diversion location)?
Nov 07 20:26:13 <kerio> iDont: which would be neat :)
Nov 07 20:26:26 <iDont> I'm open to suggestions ;)
Nov 07 20:27:16 <kerio> it's a local diversion, those are usually done by the local admin
Nov 07 20:27:42 <inz> kerio, sure, but don't have 'em lying around idle.
Nov 07 20:27:51 <hatseflats> inz: I do :p
Nov 07 20:28:03 <kerio> inz: the sheevaplug is really neat
Nov 07 20:28:09 <hatseflats> but somehow I want this n810 to work more than my rpi
Nov 07 20:29:54 <iDont> kerio, I'll look into it. Will I be able to let bb-power install /bin/busybox directly with a proper diversion? (disclaimer: I'm not too familiar with dpkg-divert, yet)
Nov 07 20:30:03 <kerio> iDont: "dpkg-divert --rename --package busybox-power /bin/busybox" in preinst and then ship /bin/busybox
Nov 07 20:30:05 <kerio> yep
Nov 07 20:30:15 <kerio> at least, that's what i've gathered
Nov 07 20:30:23 <kerio> gregoa: confirm?
Nov 07 20:31:03 <kerio> iDont: actually, "dpkg-divert --rename --package busybox-power --divert /opt/busybox-power/busybox /bin/busybox"
Nov 07 20:31:15 <gregoa> kerio: "grep dpkg-divert /var/lib/dpkg/info/*" on any debian (or ubuntu etc.) system :)
Nov 07 20:31:22 <kerio> and then "dpkg-divert --rename --remove /bin/busybox"
Nov 07 20:31:37 <gregoa> kerio: I also need to look up the syntax, and never remember the difference between local and package diversions
Nov 07 20:31:39 <iDont> kerio, sounds great :). I'll test it out and commit the change if it works as expected
Nov 07 20:31:49 <kerio> gregoa: oh, there's a way to specify diversions in the package itself?
Nov 07 20:32:33 <iDont> heh, sounds like I'll have to read up some more on dpkg-divert
Nov 07 20:32:42 <kerio> oh no, it's just preinst/postinst as i said
Nov 07 20:32:51 <kerio> er, postrm
Nov 07 20:33:10 <iDont> ok
Nov 07 20:33:22 <kerio> iDont: adobe-flashplayer-10-1 does it just like that
Nov 07 20:33:48 <iDont> kerio, thanks, I'll use that package as a reference
Nov 07 20:35:00 <gregoa> kerio: random example from my machine: https://paste.debian.net/207299/
Nov 07 20:35:56 <kerio> gregoa: yeah, that's about what i was saying :)
Nov 07 20:37:31 <gregoa> kerio: perfect :)
Nov 07 20:45:55 <kerio> DocScrutinizer05: is the n8x0 reflashable without a charged battery?
Nov 07 20:48:46 <DocScrutinizer05> no
Nov 07 20:49:16 <DocScrutinizer05> afaik it has pretty much same restrictions as N900
Nov 07 20:49:34 <DocScrutinizer05> see
Nov 07 20:49:36 <DocScrutinizer05> ~flash
Nov 07 20:49:37 <infobot> methinks maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware
Nov 07 20:49:53 <kerio> hatseflats: :(
Nov 07 20:50:21 <DocScrutinizer05> ^^^ precedes N900
Nov 07 20:51:32 <vi__> just brute force the battery with some 4v.
Nov 07 20:52:04 <kerio> hell no
Nov 07 20:52:15 <kerio> don't fuck with batteries
Nov 07 20:52:22 <vi__> kerio: y?
Nov 07 20:52:26 <vi__> r u a chikin?
Nov 07 20:52:36 <kerio> bcuz EXPLOOOOOOSIONS
Nov 07 20:52:38 <vi__> buk buk bukark.
Nov 07 20:53:13 <vi__> kerio: It is a li-ion battery, not a nitro glycerin bomb.
Nov 07 20:58:21 <vi__> so I just typed dpkg-source -x ./cln_1.3.1-2.dsc
Nov 07 20:58:26 <vi__> dpkg-source -x ./cln_1.3.1-2.dsc
Nov 07 20:58:35 <vi__> dpkg-source -x ./cln_1.3.1-2.dsc
Nov 07 20:58:39 <vi__> dpkg-source -x ./cln_1.3.1-2.dsc
Nov 07 20:58:51 <vi__> So I just tyoed: dpkg-source -x ./cln_1.3.1-2.dsc
Nov 07 20:58:55 <vi__> and got:
Nov 07 20:59:14 <vi__> gpgv: keyblock resource `/home/paul/.gnupg/trustedkeys.gpg': general error
Nov 07 20:59:14 <vi__> gpgv: Signature made Sun Dec 20 21:17:02 2009 GMT using DSA key ID F0199162
Nov 07 20:59:14 <vi__> gpgv: Can't check signature: public key not found
Nov 07 20:59:14 <vi__> dpkg-source: warning: failed to verify signature on ./cln_1.3.1-2.dsc
Nov 07 20:59:14 <vi__> dpkg-source: warning: Unknown checksum algorithm `sha256', ignoring
Nov 07 20:59:16 <vi__> dpkg-source: error: cannot fstat file ./cln_1.3.1.orig.tar.gz: No such file or directory
Nov 07 21:00:05 <vi__> excuse me while I derp.
Nov 07 21:00:13 <kerio> vi__: the fuck dude
Nov 07 21:01:15 <vi__> excuse me.  I have very little clue the fuck I am doing.
Nov 07 21:06:13 <vi__> holy shit
Nov 07 21:06:31 <vi__> for a program that calculates pi, there is an imperial fuckton of code.
Nov 07 21:06:54 <vi__> all they need is pi=(22/7);print $pi
Nov 07 21:07:40 <kerio> vi__: no u >:C
Nov 07 21:08:06 <ShadowJK> the compiler can optimize that to putc('3');
Nov 07 21:08:48 <vi__> what -o level should I use as standard?
Nov 07 21:09:15 <ShadowJK> gentoo ricers always roll -O6
Nov 07 21:09:47 <vi__> ~gentoosmite ShadowJK 
Nov 07 21:09:48 * infobot spends 5 days recompiling ShadowJK, and when it's all done, ShadowJK runs no faster than previously
Nov 07 21:10:16 <vi__> ~gentoosmite ShadowJK 
Nov 07 21:10:17 * infobot spends 5 days recompiling ShadowJK, and when it's all done, ShadowJK runs no faster than previously
Nov 07 21:10:17 <kerio> vi__: -O3 -funroll-loops -ftree-vectorize -mfpu=neon -mcpu=cortex-a8
Nov 07 21:10:23 <kerio> for BLAZING SPEEEEEEDS
Nov 07 21:10:27 <kerio> or maybe not
Nov 07 21:10:35 <kerio> because the neon vectorizer in gcc *sucks balls*
Nov 07 21:10:40 <vi__> ho maek it thumb pploz?
Nov 07 21:10:48 <ShadowJK> Every vectorizer does
Nov 07 21:10:56 <DocScrutinizer05> vi__: stop scattering please!
Nov 07 21:11:06 <vi__> ~scattering
Nov 07 21:11:28 <vi__> This is a term I am not familiar with.
Nov 07 21:11:52 <kerio> vi__: start scatting instead
Nov 07 21:12:04 <kerio> ski bi di bi di do bap do
Nov 07 21:12:06 <ShadowJK> Except the one in intel's compiler, it managed a 5% boost to an algorithm trivially sped up by 800% in 5 minutes by a asm coder
Nov 07 21:12:07 <DocScrutinizer05> I don't think you need to repeat each and every of you posts 2, 3, or even 4 times
Nov 07 21:12:22 <kerio> ShadowJK: ohoho
Nov 07 21:13:29 * ShadowJK goes sleep
Nov 07 21:13:44 <DocScrutinizer05> ShadowJK:  n8, pal
Nov 07 21:14:10 <DocScrutinizer05> kerio: he's da scatmaaaan!
Nov 07 21:14:57 <vi__> http://www.youtube.com/watch?v=FpFL3Twojj0
Nov 07 21:16:49 <DocScrutinizer05> http://www.youtube.com/watch?v=Y2mRA03dWUI
Nov 07 21:18:12 <DocScrutinizer05> http://www.youtube.com/watch?v=azomdixxX3c
Nov 07 21:18:57 <iDont> Did the files section at garage.maemo.org recently break? I can't seem to download any package from it (from any garage page)
Nov 07 21:20:07 <vi__> wtf am i watching
Nov 07 21:20:48 <vi__> http://www.youtube.com/watch?v=2Ui_MVLPRS4&feature=related
Nov 07 21:20:49 <DocScrutinizer05> Ski-Ba-Bop-Ba-Dop-Bop
Nov 07 21:21:04 <iDont> hmm, the file release system does appear to have some issues atm: http://talk.maemo.org/showthread.php?p=1291583
Nov 07 21:21:46 <kerio> vi__: you're watching "rednex - cotton eye joe"
Nov 07 21:22:29 <DocScrutinizer05> I guess rotting creeping in meanwhile, otherwise how would they manage to get the whole infra down to its knees til end of December?
Nov 07 21:22:31 <vi__> now I am watching 'ketchup song'
Nov 07 21:22:36 <kerio> haha
Nov 07 21:22:50 <kerio> vi__: http://www.albinoblacksheep.com/flash/llama
Nov 07 21:22:55 <kerio> much better
Nov 07 21:23:02 <vi__> so much shit music from 20 years ago.
Nov 07 21:24:16 <DocScrutinizer05> actually 20 years ago there already was 99.x% of shit music - hard to find the 0.y% that was bearable by then
Nov 07 21:24:33 <DocScrutinizer05> to find good music you need to go back maybe 30 years
Nov 07 21:24:46 <maybeArgh> i blame eurodance
Nov 07 21:26:12 <DocScrutinizer05> trivia about the scatman: he actually had a problem that he cured by singing
Nov 07 21:26:50 <DocScrutinizer05> at least that's been his legend
Nov 07 21:28:10 <vi__> yeah, and now he is dead.
Nov 07 21:28:21 <vi__> Obvious symptom of singing.
Nov 07 21:29:56 <vi__> what version of libc6 is in maemo5?
Nov 07 21:30:05 <vi__> how would I check that in scratchbox?
Nov 07 21:36:38 <jacekowski> i've just found out that Fluke 289 runs linux
Nov 07 21:36:58 <jacekowski> and it's just a meter
Nov 07 21:37:38 <SpeedEvil> GPL violating?
Nov 07 21:37:56 <jacekowski> yeah, looks like it
Nov 07 21:38:04 <jacekowski> i can't find anything on fluke website
Nov 07 21:38:21 <SpeedEvil> at least there is a likely hood of fixing
Nov 07 21:38:23 <jacekowski> unless they are using vanila kernel which in which case they are probably ok to do it
Nov 07 21:38:29 <SpeedEvil> err, no
Nov 07 21:38:38 <SpeedEvil> you have to provide source
Nov 07 21:38:44 <SpeedEvil> even if it's stock
Nov 07 21:39:05 <SpeedEvil> are you aware of the GPL violations list?
Nov 07 21:39:08 <jacekowski> but that would explain why that meter takes like 10s to start
Nov 07 21:39:31 <SpeedEvil> why do you think it does?
Nov 07 21:40:05 <jacekowski> well some long time ago i've installed updating software for that meter
Nov 07 21:40:19 <jacekowski> updated the meter and done nothing later
Nov 07 21:40:20 <SpeedEvil> ah, k
Nov 07 21:40:32 <jacekowski> now i've found where did it install all the files
Nov 07 21:40:44 <jacekowski> and i've found .hex so i've disassembled it just out of curiosity
Nov 07 21:40:54 <jacekowski> but then there was couple other files
Nov 07 21:41:28 <jacekowski> one of those was ELF file
Nov 07 21:41:37 <SpeedEvil> GPL violations list is a good point to get advice
Nov 07 21:41:55 <SpeedEvil> or yo can talk to fluke direct, of course
Nov 07 21:42:21 <SpeedEvil> you should at least read the GPL, and understand their obligations first though
Nov 07 21:42:44 <jacekowski> i want to double check that it is linux for sure
Nov 07 21:42:54 <jacekowski> not something linux like
Nov 07 21:43:16 <SpeedEvil> yeah
Nov 07 21:43:22 <jacekowski> vxworks uses ELFs as well
Nov 07 21:43:32 <SpeedEvil> grep for strings, look for ttys on boot
Nov 07 21:43:32 <jacekowski> and in terms of API it's very similiar
Nov 07 21:43:58 <jacekowski> i don't have kernel itself
Nov 07 21:44:04 <jacekowski> i just have one excecutable
Nov 07 21:44:11 <jacekowski> it looks like update process is not updating kernel
Nov 07 21:44:48 <jacekowski> just two files, one that runs on secondary MSP processor that seems to do all the measuring and main ARM doing all display, graphing, logging
Nov 07 21:45:00 <SpeedEvil> ah
Nov 07 21:46:27 <jacekowski> hmmm
Nov 07 21:51:02 <jacekowski> after looking more into it, it looks more like eCOS
Nov 07 21:51:05 <jacekowski> which is GPL as well
Nov 07 21:53:48 <vi__> how do I set the code to compile as -mfpu=neon?
Nov 07 21:53:59 <vi__> is it passed as a parameter to configure or make?
Nov 07 21:54:09 <kerio> it's a cflag
Nov 07 21:54:24 <vi__> ls
Nov 07 21:54:38 <vi__> ...
Nov 07 21:54:40 <vi__> so
Nov 07 21:55:43 <vi__> But I do not directly invoke gcc.
Nov 07 21:56:24 <SpeedEvil> flags in make file
Nov 07 21:57:29 <vi__> so do I need to edit Makefile to set thos flags or can I pass them directly to make?
Nov 07 21:57:54 <jon_y> depends on the makefile
Nov 07 21:58:15 <jacekowski> SpeedEvil: that gpl violations list
Nov 07 21:58:18 <vi__> in the makefile there is a line CFLAGS = -g -O2
Nov 07 21:58:32 <jon_y> yes, add it there
Nov 07 21:58:39 <jacekowski> SpeedEvil: what's the deal with it exactly
Nov 07 21:58:48 <vi__> is the 'correct' way to do it by editing this file or by passing these parameters to something?
Nov 07 21:59:18 <jon_y> is it autotools?
Nov 07 21:59:27 <vi__> I have NFC.
Nov 07 21:59:45 <vi__> I wget the source from debian source repo.
Nov 07 21:59:50 <jon_y> did you run configure?
Nov 07 21:59:54 <vi__> type ./configure
Nov 07 22:00:05 <jon_y> that would likely be autotools
Nov 07 22:00:22 <jon_y> ./configure CFLAGS="-g -O2 -mfpu=neon"
Nov 07 22:00:37 <vi__> so should I pass the the cflags to configure when it generates the makefile?
Nov 07 22:00:53 <vi__> jon_y: Thank you. I owe you 1 donut.
Nov 07 22:01:24 <jon_y> not needed after that
Nov 07 22:01:48 <vi__> what are these:
Nov 07 22:01:52 <vi__> -mfpu=neon -ftree-vectorize -fgraphite -lto 
Nov 07 22:01:58 <jon_y> if the configure has been written sanely, you can just do CFLAGS=-mfpu=neon
Nov 07 22:02:08 <jon_y> those are link time optimizations
Nov 07 22:02:10 <vi__> are these all cflags?
Nov 07 22:02:16 <jon_y> yes
Nov 07 22:02:27 <jon_y> CFLAGS are used by C compile and link time
Nov 07 22:02:36 <jon_y> CXXFLAGS for C++ equivalent
Nov 07 22:02:53 <jon_y> CPPFLAGS are compile time flags used by both C and C++
Nov 07 22:02:56 <vi__> configure: error: C compiler cannot create executables
Nov 07 22:02:59 <vi__> ^error
Nov 07 22:03:11 <jon_y> look into configure.log
Nov 07 22:03:17 <jon_y> or post it on pastebin
Nov 07 22:03:19 <vi__> cat ./configure.log
Nov 07 22:03:32 <DocScrutinizer05> W*T*F?? http://www.youtube.com/watch?feature=fvwp&NR=1&v=_oUp_JjPJok  10 hours?
Nov 07 22:03:47 <DocScrutinizer05> endless loop
Nov 07 22:03:54 <jon_y> 10 hours of silence? :)
Nov 07 22:04:22 <jon_y> vi__: likely it should be -flto
Nov 07 22:04:25 <jon_y> not -lto
Nov 07 22:05:01 <vi__> jon_y: I was just in the process of eliminating the possibilities
Nov 07 22:05:12 <vi__> what is the -lto mean?
Nov 07 22:05:14 <jon_y> autotools is awesome, best buildsystem, even when MSVC and windows is involved :)
Nov 07 22:05:23 <jon_y> -lto means link to libto
Nov 07 22:05:41 <jon_y> -flto oth means use link time optimization
Nov 07 22:05:44 <vi__> It does seem to be making the devilishly complicated  process of compilation a piece of cake.
Nov 07 22:06:08 <jon_y> but it works very well, unlike cmake
Nov 07 22:06:15 <jon_y> especially when cross compiling
Nov 07 22:08:32 <vi__> failed.
Nov 07 22:08:35 <vi__> error 1.
Nov 07 22:08:40 <vi__> incomprehensible.
Nov 07 22:08:49 <vi__> ./base/hash/cl_hash2.h:121:9: note: use 'this->_garcol_fun' instead
Nov 07 22:08:49 <vi__> make[1]: *** [cl_rcpointer2_hashweak_rcpointer.lo] Error 1
Nov 07 22:08:49 <vi__> make[1]: Leaving directory `/home/paul/pi/cln-1.3.1/src'
Nov 07 22:08:49 <vi__> make: *** [all-recursive] Error 1
Nov 07 22:09:23 <jon_y> looks like an error from the compiler
Nov 07 22:09:40 <jon_y> maybe some c++ template exploded?
Nov 07 22:09:52 <jon_y> you may want to set CXXFLAGS too
Nov 07 22:10:05 <vi__> ...
Nov 07 22:10:08 <vi__> set it to what?
Nov 07 22:10:53 <jon_y> CXXFLAGS to the same thing as CFLAGS
Nov 07 22:11:02 <vi__> jon_y: oh, ok.
Nov 07 22:11:07 <jon_y> eg the neon thing
Nov 07 22:11:28 <jon_y> otherwise, the C++ code may not be using neon at all
Nov 07 22:12:45 <vi__> derp
Nov 07 22:13:08 <vi__> you cannot shoehorn neon into non neon specific code?
Nov 07 22:14:17 <jon_y> maybe, but without it, your C++ is compiled without -mfpu=neon
Nov 07 22:14:39 <jon_y> CFLAGS only affects C compile, CXXFLAGS for C++
Nov 07 22:14:58 <jon_y> I assume it's C++ anyway from the "this" pointer
Nov 07 22:15:31 <jon_y> it is still possible somebody called the pointer "this" in C
Nov 07 22:17:56 <DocScrutinizer05> jon_y: not silence - actually I think it's been a while since I've last seen something insane as http://www.youtube.com/playlist?list=PL2D5ACE7F76092751
Nov 07 22:19:42 <jon_y> DocScrutinizer05: youtube poop everywhere!
Nov 07 22:20:18 <DocScrutinizer05> what's this 10 hours crap about anyway? some new form of dadaism in video arts?
Nov 07 22:20:47 <jon_y> it's just youtub poop
Nov 07 22:20:59 <jon_y> file it as the same category as nyan cat
Nov 07 22:21:18 <DocScrutinizer05> in fact nyan cat is in that list
Nov 07 22:21:34 <jon_y> heh, I see it
Nov 07 22:21:56 <DocScrutinizer05> 480 hours of torture
Nov 07 22:22:12 <DocScrutinizer05> handed to evil 3letter agencies free of charge
Nov 07 22:22:49 <jon_y> DocScrutinizer05: use with sensory deprivation? :)
Nov 07 22:22:58 <DocScrutinizer05> oops 490:00:01
Nov 07 22:23:34 <vi__> http://www.youtube.com/watch?v=dP3H4iwhnZk
Nov 07 22:24:27 <jon_y> what is that?
Nov 07 22:24:40 <SpeedEvil> jacekowski: discussions of, and advice on what tomdonwhen you find a GPL violator
Nov 07 22:24:52 <vi__> a man in a horses head mask and a mankini cooking fly agaric mushrooms.
Nov 07 22:26:25 <SpeedEvil> jacekowski: do you have any code in the kernel?
Nov 07 22:26:38 <SpeedEvil> oh, you said ecos nvm
Nov 07 22:26:39 <vi__> jon_y: can anything be compiled as a static binary?
Nov 07 22:27:15 <jon_y> it really depends
Nov 07 22:27:23 <jon_y> you can try adding -static
Nov 07 22:27:54 <vi__> I guess it would need all the code for the depends.
Nov 07 22:29:49 <vi__> needs sigc++
Nov 07 22:29:52 <jon_y> for static libraries, things get a bit complicated
Nov 07 22:30:01 <vi__> I donut even know what that is.
Nov 07 22:30:27 <jon_y> static libraries must be specified with all the dependencies explicitly when used at link time
Nov 07 22:30:46 <vi__> I assumed as much.
Nov 07 22:30:52 <jon_y> vi__: I just watched your video, I have to say:
Nov 07 22:31:00 <jon_y> WTF Japan?
Nov 07 22:31:16 <vi__> that is why 'wgetting' the source from debian website seems so 'wrong'
Nov 07 22:31:19 <jon_y> not that it's a bad thing, song was catchy :)
Nov 07 22:31:43 <jon_y> actually, it has nothing to do with debian
Nov 07 22:31:47 <vi__> you should hear the musin in the original.
Nov 07 22:31:56 <vi__> ^music
Nov 07 22:32:18 <jon_y> yeah, I should look for it
Nov 07 22:32:46 <jon_y> static libs are just unlinked libs, you need to fulfill the link time requirements
Nov 07 22:33:15 <jon_y> I know ELF allows undefined symbols, but your executable may complain about the symbols and exit at runtime
Nov 07 22:33:35 <jon_y> so best to deal with it before shipping your programs
Nov 07 22:34:46 <jacekowski> SpeedEvil: eCos is GPL so it's still a violation
Nov 07 22:34:55 <jacekowski> unless there is some commercial version of it
Nov 07 22:35:41 <jon_y> vi__: for libc version, you can try running /lib/libc.so from the shell
Nov 07 22:35:52 <jon_y> it may work or not
Nov 07 22:36:05 * DocScrutinizer05 likes to teach infobot some new ~lart procedure, along the lines of "infobot ties $deliquent to a chair and plays a 10h Nyan cat to $deliquent"
Nov 07 22:37:17 <DocScrutinizer05> might consider it for a hold-the-line music on next PBX I need to configure
Nov 07 22:38:59 <jon_y> vi__: was that youtube link a youtube sync mix?
Nov 07 22:39:04 <jacekowski> DocScrutinizer05: i've got a pbx to configure
Nov 07 22:39:33 <vi__> jon_y: I dont know what a sync mix is.
Nov 07 22:39:44 <DocScrutinizer05> vi__: >>Unfortunately, this UMG-music-content is not available in Germany because GEMA has not granted the respective music publishing rights.<<
Nov 07 22:40:04 <vi__> jacekowski: use the portal radio music.
Nov 07 22:40:05 <jon_y> vi__: video synched with a random piece of music
Nov 07 22:40:18 <jon_y> some of them match very very well
Nov 07 22:40:25 <vi__> jon_y: I do not know.
Nov 07 22:40:36 <DocScrutinizer05> jacekowski: need a link to Nyan Cat?
Nov 07 22:40:54 <jon_y> I saw a call of duty blackops trailer sync once
Nov 07 22:41:15 <jacekowski> DocScrutinizer05: have you got version that it's voip codec friendly?
Nov 07 22:41:23 <jacekowski> that is*
Nov 07 22:41:24 <DocScrutinizer05> or rather, the question is: are you THAT misanthropic?
Nov 07 22:42:04 <DocScrutinizer05> dunno, depends on your codec I guess
Nov 07 22:42:18 <DocScrutinizer05> 711a or what's the name should work ;-D
Nov 07 22:42:18 <jacekowski> i'll have to try it then
Nov 07 22:42:28 <jacekowski> well, what if someone calls from gsm
Nov 07 22:42:31 <jacekowski> hmm
Nov 07 22:42:57 <DocScrutinizer05> http://www.youtube.com/watch?v=jI-kpVh6e1U&list=SP2D5ACE7F76092751&index=26&feature=plpp_video
Nov 07 22:43:00 <DocScrutinizer05> here you are
Nov 07 22:43:21 <DocScrutinizer05> in HD!!!!!!!!
Nov 07 22:43:27 <DocScrutinizer05> XP
Nov 07 22:44:04 <DocScrutinizer05> r33b.net
Nov 07 22:44:38 <jon_y> can't find the blackops trailer mixed with 80s music anymore
Nov 07 22:44:47 <jon_y> somehow it was perfect
Nov 07 22:45:22 <DocScrutinizer05> no hypnotoad and nyan cat fight in my brain, what a terrible mess
Nov 07 22:45:37 <Skry> my favorite chars
Nov 07 22:45:57 <Skry> I find nyan cat very calming
Nov 07 22:46:42 <DocScrutinizer05> I think it is like a mixture of meth and sulfuric acid to the brain
Nov 07 22:47:37 <DocScrutinizer05> well, if you got ADHS actually nyan cat might calm you down
Nov 07 22:47:45 <DocScrutinizer05> ;-)
Nov 07 22:48:44 <DocScrutinizer05> my feeling about that, no offense intended
Nov 07 22:50:02 <jon_y> try LSD dream simulator :)
Nov 07 22:50:46 <Skry> None taken, sometimes when your brain is on "overdrive" too long and you've had way too much caffeine (or meth) and shit starts breaking around you, 10 minutes of nyan cat quite efficiently stops all brain functions.
Nov 07 22:51:43 <vi__> I think I may have thumb compiled bzip2
Nov 07 22:51:55 <vi__> and libbz2.so
Nov 07 22:52:44 <vi__> So this proves it works, how does one upload it to autobuilder?
Nov 07 22:54:51 <MrPingu> vi_: congratz
Nov 07 22:57:03 <vi__> I guess the wise thing to do is to upload it to a test device and confirm that neon vectorisation has improved the performance.
Nov 07 23:17:55 <vi__> how do you do a 'full reset' on the bq27x00 chip?
Nov 07 23:34:45 <vi__> :q
Nov 07 23:35:07 <RiD> poor boy
Nov 07 23:35:10 <RiD> no one told him how
Nov 07 23:36:26 <DocScrutinizer05> he'll find out sooner or later
Nov 07 23:36:46 <RiD> I bet the later, because he's going to sleep
Nov 07 23:36:47 <DocScrutinizer05> after a day with battery removed he will magically find the answer
Nov 07 23:36:58 <RiD> lol
Nov 07 23:37:04 <RiD> how about over a month without it :(
Nov 07 23:38:41 <DocScrutinizer05> actually there _is_ a way to do a programmed reset
Nov 07 23:38:58 <DocScrutinizer05> but I CBA to look it up in datasheet
Nov 07 23:39:23 <DocScrutinizer05> since nobody ever fellt the need for doing that - it resets on a few minutes without battery
Nov 07 23:39:28 <RiD> better just do it the simple way
Nov 07 23:39:42 <RiD> that's like buying a fridge to heat chicken
Nov 07 23:40:11 <RiD> Ok, that was not a good comparison
Nov 07 23:41:32 <DocScrutinizer05> the bq27200 is meant to get mounted permanently to a LiIon cell. The way Nokia used it is kinda abuse of the chip. For permanent mount on top of battery cell you may need reset via register access, not so for N900 where it resets as soon as battery removed and a few uF of capacitor discharged
Nov 08 00:48:40 <louisdk> hi :)
Nov 08 00:55:12 <louisdk> is everybody sleeping? :)
Nov 08 00:55:24 <Skry> nope
Nov 08 00:56:23 <louisdk> skry: do you use an n900 as your primary phone?
Nov 08 00:58:58 <Skry> louisdk: yes
Nov 08 01:00:15 <louisdk> skry: cool. do you have cssu installed on it?
Nov 08 01:00:59 <Skry> sure, and thumb
Nov 08 01:01:37 <louisdk> skry: does thumb make a big performance boost?
Nov 08 01:03:10 <Skry> you'll notice the difference
Nov 08 01:04:48 <louisdk> skry: okay. i have an n950. nice phone but miss the hildon desktop.
Nov 08 01:05:16 <Skry> yeah, h-d is nice
Nov 08 01:06:17 <louisdk> skry: what about the battery life on your n900?
Nov 08 01:08:51 <Skry> well, I have the original battery from '09 and I guess it's sufficient, I dont do calls that much. It runs several days idle.
Nov 08 01:09:30 <Skry> I think I usually charge it every other day
Nov 08 01:10:36 <louisdk> skry: when i used an n900 i had to charge i everyday cause i always had my IM accounts enabled. 
Nov 08 01:13:37 <Skry> sounds normal. imo battery is fine if it lasts through the day, you can charge it while you sleep.
Nov 08 01:16:14 <louisdk> skry: well i don't have fuctional n900 anymore. mic and usb broken.
Nov 08 01:18:50 <Skry> fix it
Nov 08 01:22:03 <louisdk> i can't really find a way to fix the mic without getting a new phone. it's a motherboard issue
Nov 08 01:23:46 <Skry> ahh, ok then. you could fix the usb though and start doing something with it
Nov 08 01:23:57 <Skry> or you can sell it to me dirt cheap :)
Nov 08 01:27:02 <SpeedEvil> mic is 'easy' to fix
Nov 08 01:27:15 <SpeedEvil> it's a relatively large part IIRC
Nov 08 01:27:25 <SpeedEvil> but it is a nontrivial repair
Nov 08 01:28:24 <jonwil> damn, I wish it wasn't so hard to use openssl to do AES encryption :(
**** ENDING LOGGING AT Thu Nov 08 03:00:01 2012