IRC log for #maemo-ssu on 20120902

01:30.51*** join/#maemo-ssu wmarone (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
02:50.07*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
05:07.18*** join/#maemo-ssu kerio (kerio@unaffiliated/kerio)
06:38.21*** join/#maemo-ssu wmarone_ (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
08:26.31*** join/#maemo-ssu NIN101 (~NIN@p5DD280B2.dip0.t-ipconnect.de)
09:21.09*** join/#maemo-ssu arcean (~arcean@aacs101.neoplus.adsl.tpnet.pl)
09:25.59*** join/#maemo-ssu arcean (~arcean@aacs101.neoplus.adsl.tpnet.pl)
09:26.55*** join/#maemo-ssu toxaris (~toxaris@90-230-114-186-no34.tbcn.telia.com)
10:45.08merlin1991luf ping
10:48.42merlin1991@asnyone how would I found out about my hdd drives from the commandline (manufacturer and similar info)
11:19.18merlin1991neither luf nor pali around
11:19.22merlin1991but i need them both
11:34.13*** join/#maemo-ssu bsdmaniak (~bsdmaniak@std93-20-88-120-139-80.fbx.proxad.net)
12:22.21DocScrutinizer05merlin1991: find out about hdd? try hdparm
12:24.06DocScrutinizer05merlin1991: also smart tools may help a lot
12:25.37DocScrutinizer05hdparm -I </phy/name>
12:27.22DocScrutinizer05smartctl --all /dev/sda
12:29.00DocScrutinizer05maybe smartctl -i /dev/sda
12:29.09DocScrutinizer05a tad more terse
13:27.30gregoamerlin1991: lshw is also nice for getting hardware info
13:47.27merlin1991gregoa: lshw is nice, I never knew it existed :D
13:47.59gregoa:)
13:52.18*** join/#maemo-ssu luf (~luf@ip-89-103-166-30.net.upcbroadband.cz)
13:52.59lufmerlin1991: pong
13:58.10*** join/#maemo-ssu arcean (~arcean@aaes189.neoplus.adsl.tpnet.pl)
14:01.38DocScrutinizer05luf: you got your account?
14:01.57lufDocScrutinizer05: yes. thanks.
14:03.27lufI didn't assign the task as I want to do once by once. Not all tasks at one time.
14:03.43DocScrutinizer05no lshw on my PC
14:03.59lufDocScrutinizer05: let's install it ;)
14:04.01DocScrutinizer05must be a buntkuh thing
14:04.11DocScrutinizer05;-P
14:05.28DocScrutinizer05merlin1991: you seen my semi-honest rant about "blacklisting" rogue pkgs?
14:05.33DocScrutinizer05over at #maemo
14:06.23DocScrutinizer05[2012-09-02 02:03:11] * DocScrutinizer05 honestly ponders to integrate a malware filter to CSSU. First candidates to nuke form device and HAM list of available apps: batterypatch and speedpatch [2012-09-02 02:03:19] <DocScrutinizer05> and fapman [2012-09-02 02:03:23] <DocScrutinizer05> ;-P [2012-09-02 02:04:33] <DocScrutinizer05> meh, waaay simpler: get dummy void packages of same name into CSSU MP
14:23.12kerioDocScrutinizer05: with a really high version, you mean?
14:23.21keriobtw, does uninstalling for those work?
14:24.36DocScrutinizer05kerio: yep
14:24.50DocScrutinizer05(for first Q)
14:25.42DocScrutinizer05kerio: NFC if you could properly uninstall this *patch abominations
14:25.49DocScrutinizer05I'd rather guess you can't
14:26.18DocScrutinizer05s/this/these/.
14:38.56keriogoddammit, where's pali
14:39.02kerioi want to know how ke-recv is supposed to work
14:42.17DocScrutinizer05hehe
14:42.28DocScrutinizer05you're not alone
14:43.06DocScrutinizer05maybe reading source could help? ;-)
14:43.33kerioi hoped for a bbscript
14:43.48DocScrutinizer05bitbake receipe?
14:43.56DocScrutinizer05eeew
14:44.04keriobusybox script
14:44.09DocScrutinizer05ouch
14:44.18kerio"shell" is too much for that crap
14:44.39DocScrutinizer05ak, I'm fine with that
14:44.43DocScrutinizer05ok*
14:45.00DocScrutinizer05;-)
14:45.02kerioalso, i hope pali made his changes configurable
14:45.11kerioi don't want to export my whole sd when i tap "mass storage mode"
14:45.22DocScrutinizer05I doubt there's much configurability in ke-recv
14:45.25kerio(also, how do i trigger the automounter manually?)
14:45.48DocScrutinizer05ke-recv-test ?
14:46.13keriohm, there's nothing *that* specific
14:46.32DocScrutinizer05m - enable USB mass storage
14:46.33keriohm, maybe e - check device <arg>
14:46.40DocScrutinizer05or that
14:47.03DocScrutinizer05cb - close battery cover signal
14:47.17DocScrutinizer05will obviously automount the uSD
14:47.38kerionope!
14:47.52keriodoesn't work
14:47.55DocScrutinizer05unless ke-recv-test is to fake signals *from* ke-recv *to* other subsystems
14:48.24keriofdisk /dev/mmcblk1 and then w works, though
14:48.35DocScrutinizer05which again is as obscure as ke-recv itself
14:48.39keriooh no, doesn't
14:48.43keriobecause i'm actually using the usd
14:48.44kerio:S
14:50.26DocScrutinizer05http://gitorious.org/community-ssu/ke-recv/trees/master
14:50.35DocScrutinizer05for your "convenience"
14:52.16kerioso far the only way i've found is to use fdisk or similar to trigger the automounter
14:52.23keriobut it only works if you're not using the uSD at all
14:55.22DocScrutinizer05haha for http://gitorious.org/community-ssu/ke-recv/blobs/master/src/ke-recv.schemas#line72
14:56.35DocScrutinizer05gitorious html formatter doesn't like the <cr> in there, I wonder if it's otherwise harmless
14:57.16DocScrutinizer05http://gitorious.org/community-ssu/ke-recv/blobs/master/src/ke-recv.schemas#line83 same
14:57.28DocScrutinizer05124 same
14:57.48DocScrutinizer05135,
14:59.43DocScrutinizer05kerio: http://gitorious.org/community-ssu/ke-recv/blobs/master/src/osso-mmc-mount.sh; http://gitorious.org/community-ssu/ke-recv/blobs/master/src/mmc-mount ??
15:01.13DocScrutinizer05kerio: finally you'll want to have a look to http://gitorious.org/community-ssu/ke-recv/blobs/master/src/events.c
15:01.49merlin1991encoding bs ftw
15:02.08merlin1991luf: I'll get back to you tomorrow? or are you around in about 4 hours today?
15:02.27merlin1991make that 4 to 6 :D
15:03.09lufmerlin1991: We'll see.
15:05.12lufFeel free to write what you want even when I'm not available.
15:05.35lufOr you can send me the mail :)
15:07.28merlin1991well my main question was about rtcom-logger-async, where does the code come from, does it affect other packages aswell, ...
15:07.56merlin1991since the obexd update would require it
15:08.03*** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg)
15:09.01merlin1991DocScrutinizer05: blacklist won't worge because said packages don't uninstall properly so we risk more removing them than keeping them
15:09.13merlin1991s/worge/work/
15:09.46*** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg)
15:09.54DocScrutinizer05(const char*)dgettext("hildon-fm", "sfil_li_memorycard_removable"), 100);  --- BLAERGH!
15:12.06DocScrutinizer05http://gitorious.org/community-ssu/ke-recv/blobs/master/src/events.c#line149  OOOUUUUUCH!
15:13.26DocScrutinizer05http://gitorious.org/community-ssu/ke-recv/blobs/master/src/events.c#line149  OOOUUUUUCH!http://gitorious.org/community-ssu/ke-recv/blobs/master/src/events.c#line168   http://gitorious.org/community-ssu/ke-recv/blobs/master/src/events.c#line176   HOLY SPAGHETTI MONSTER W*T*F?!
15:14.50DocScrutinizer05Author: Kimmo H�m�l�inen <kimmo.hamalainen@nokia.com>
15:15.09DocScrutinizer05I probably should memorize that one pretty well
15:15.20DocScrutinizer05just in case
15:16.46DocScrutinizer05can't stop puking
15:17.26DocScrutinizer05a chain of THREE backwards goto plus one forward goto to actual "end of mess"
15:17.47DocScrutinizer05I can't recall when I last seen such indigestible mess
15:17.48*** join/#maemo-ssu MrPingu (~Thunderbi@86.92.226.97)
15:18.16kerioDocScrutinizer05: oh lol
15:19.08DocScrutinizer05that's how you scare pupils in first class C course
15:19.23DocScrutinizer05or general programming class
15:20.01DocScrutinizer05I.E. it's worse than worst prototypical bad examples I've ever encountered
15:20.24kerioDocScrutinizer05: mmc-mount sounds... weird
15:20.33kerioi mean, there's a file in /etc/default/ that lists the options for vfat partitions
15:20.38keriobut that's not referred to anywhere :S
15:20.45kerioi think
15:20.48kerioor maybe it sets an env?
15:20.53keriomeh
15:21.09*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
15:21.17kerioi don't even
15:21.28keriowhy did nokia feel the need to reinvent an automounter?
15:21.33kerioand why didn't they implement it in a sensible way?
15:22.33DocScrutinizer05I only hope it's not been pali to introduce this goto-horrorshow in there
15:22.40keriocheck the blame
15:23.06kerioivaylo dimitrov
15:30.40DocScrutinizer05tell me how to do that? (check blame)
15:31.06DocScrutinizer05aah nm
15:31.09kerioup on that page, "Blame"
15:31.28kerioalternatively, git someweirdshitthatsoundsunrelated thatfile
15:33.04DocScrutinizer05ivaylo dimitrov sounds uncomfortably familiar :-/
15:35.05*** join/#maemo-ssu Krayon (~fallen@pdpc/supporter/28for7/krayon)
15:39.31*** join/#maemo-ssu arcean (~arcean@aaes189.neoplus.adsl.tpnet.pl)
15:45.51DocScrutinizer05honestly this needs cleanup!
15:48.17DocScrutinizer05if only it's pulling down lines 143,144,  154,155,  161,162  to bootom of function, in secuence error3:  error2: error1: and obviously deleting former 144 155 162
15:48.34DocScrutinizer05plus a few 3 more edits
15:48.49DocScrutinizer05NO BACKWARDS GOTO! NEVER!
15:49.47kerioprepares a commit to fix that, by using setjmp/longjmp
15:49.57keriou mad
15:50.03keriowhy u mad
15:54.40*** join/#maemo-ssu M13 (~M13@170.133-224-87.telenet.ru)
15:58.28*** join/#maemo-ssu illuminata (illuminata@ipv6.deformedfeatures.com)
15:59.54illuminataso i got that nasty auto-reboot bug. just cropped up a couple/few days ago
16:00.05illuminatagonna try to go ssu, hope it doesn't boot me out
16:00.47illuminataseems ok enough when i'm actively using an app. yet again i was just actively using the app manager and it rebooted so
16:02.43kerioauto-reboot bug? :o
16:03.38illuminatayeah. it sucks bad. icons/carrier name can't stay drawn on the home screen. they disappear. keeps cycling. after a few minutes the phone reboots
16:04.00keriowhat did you install, exactly?
16:04.19keriosounds like a dsme reboot
16:04.39illuminatanothing for months really
16:05.05keriowell something broke somewhere and dsme gets tired of respawning it so it reboots your phone
16:05.13illuminatai tried uninstalling omweather, didn't see if i could uninstall rss. those don't draw at all
16:05.25kerioso... hildon-home problem
16:05.26illuminatai figured it was something like that but wasn't sure on the specifics
16:05.32keriotry deleting the config files for that
16:05.41kerioand by deleting i mean moving somewhere else
16:05.48illuminatahmm, will try
16:06.47*** join/#maemo-ssu bsdmaniak (~bsdmaniak@std93-20-88-120-139-80.fbx.proxad.net)
16:06.58kerioilluminata: were you on some flavour of cssu?
16:07.02keriomaybe thumb?
16:07.08illuminatanope, just 1.3.1
16:07.09keriobut without the appropriate kernel
16:07.14keriohm
16:07.27keriodid you overclock?
16:07.42illuminatanah
16:07.50illuminatai mean i really don't do much with this phone short of calls and irc
16:08.22kerioanyway, you could enable rd mode
16:08.25kerioand disable the watchdog
16:08.30kerio(this can be done with flasher)
16:08.39kerio(well, it must be done with flasher, really)
16:09.18illuminatawill it work with any flavor of the flasher? because i might have to boot up my linux laptop as i'm in a 64 bit windows environment now
16:10.18kerio\_o_/
16:10.55illuminatathat's either a shrug or a muscle flex
16:11.26kerioyes
16:27.01*** join/#maemo-ssu fruct (~fruct@188.242.38.250)
16:28.21fructHello All. I'm start community-ssu-enabler, and my device is unusable now! Please help me!
16:28.38DocScrutinizer05first clean / rename your hildon-desktop related config files like suggested by kerio
16:28.53keriofruct: which one?
16:29.28DocScrutinizer05fruct: there's a pretty clear and non-interpretable instruction on how to enable CSSU, on
16:29.31DocScrutinizer05~cssu
16:29.31infobotrumour has it, cssu is http://wiki.maemo.org/Community_SSU
16:29.44fructkerio: the stable version
16:29.48DocScrutinizer05did you follow that?
16:30.27DocScrutinizer05actually http://wiki.maemo.org/Community_SSU#Installation
16:32.15DocScrutinizer05starts to think there's some weird package named cssu-enabler out there, free to install by user any arbitrary (fapman, apt) way he feels might fit
16:32.28keriohe said community-ssu-enabler
16:32.32fructI did do backup =(
16:32.33fructI'm before install power kernel and enchanced busybox
16:32.54keriofruct: what do you mean by "unusable"?
16:34.03DocScrutinizer05fruct: there's no support for any other way to install CSSU, other than the one described at http://wiki.maemo.org/Community_SSU#Installation
16:34.17DocScrutinizer05and actually no other way usually works
16:34.28fructthe icons and status bar moved to upper left corner and desktop not switch and dont enable edit mode
16:34.42DocScrutinizer05(unless your name is kerio and you love to mess with stuff)
16:34.46kerio=D
16:34.54kerioDocScrutinizer05: hey, i did follow the instruction for cssu-te
16:35.05kerioand then i realized that HAM is stupid
16:35.17DocScrutinizer05wasn't it you who refused to use HAM?
16:35.28kerioyeah but the first installation used community-ssu-enabler
16:35.46kerioi mean, followed the whole instructions
16:35.53DocScrutinizer05mhm
16:36.06DocScrutinizer05so maybe we'll eventually find out if fruct did as well?
16:36.12kerioby the way, does community-ssu-enabler mark the maemo5 packages for manual installation? because autoremove works fine
16:36.29kerioi mean, it doesn't autoremove stuff that it shouldn't, for me
16:36.39DocScrutinizer05then you're lucky
16:36.52DocScrutinizer05for me it did ever since PR1.0.1
16:37.04keriodid you upgrade from pr 1.0.1?
16:37.18DocScrutinizer05no, from PR1.0
16:37.24keriowow
16:37.30DocScrutinizer05tp PR1.0.1, to Pr1.1...
16:37.37kerionever reflashed? neat
16:37.45DocScrutinizer05never reflashed
16:37.51DocScrutinizer05iirc
16:38.16keriothere was a dude that installed dos 6 in a VM
16:38.18DocScrutinizer05and that's what makes the big difference for autoremove
16:38.24kerioand then started upgrading windows, from 1 to 7
16:38.38kerioDocScrutinizer05: you could just mark those package manual
16:38.41keriowith apt-mark
16:38.45kerio*packages
16:39.37DocScrutinizer05fruct: we (well I at least) still didn't get what exactly you did
16:40.41DocScrutinizer05unless your problem is with installation as described in http://wiki.maemo.org/Community_SSU#Installation, I'd suggest you reflash to clean PR1.3, then follow http://wiki.maemo.org/Community_SSU#Installation
16:42.33DocScrutinizer05*IF* your problem actually was during following instructions of http://wiki.maemo.org/Community_SSU#Installation, we'd like to hear details though, to fix any glitches in either cssu-enabler or instructions
16:43.00keriomaybe it was busybox-power! >:D
16:43.22DocScrutinizer05I tried hard to not comment on it ;-P
16:43.42illuminatawooooow. re-flashed to nokia firmware. still doing that stupid bug
16:43.53keriowell i actually had a tiny problem with the busybox-power upgrade
16:43.56kerioer
16:44.01DocScrutinizer05illuminata: please elaborate
16:44.02keriowell, the reinstall
16:44.11kerioilluminata: please elaborate, but in #maemo
16:44.17DocScrutinizer05indeed
16:44.20fructkerio: yes! I install busybox-power!
16:44.21keriobecause it's clearly not a CSSU problem anymore :)
16:44.29illuminatawill do. thought i was gonna make progress on that front
16:44.32keriofruct: i'm kinda joking, it should cause no problems
16:44.37illuminatawas gonna be like "aw yeah cssu time"
16:49.39*** join/#maemo-ssu luf (~luf@ip-89-103-166-30.net.upcbroadband.cz)
16:51.41fructstrange, on loading, first screen - normal and after, desktop becomes not normal
16:56.46lufmerlin1991: I created rtcom-eventlogger-async from scratch. It's dbus daemon for async calls from obexd for call history and also MAP in near future. It's something like evolution-data-server-factory. Nothing else than obexd depends on rtcom-eventlogger-async. I asked you for creating new git repo for it.
16:59.43merlin1991ah now I understand what it is :)
16:59.46merlin1991I'll do the repo
17:01.56merlin1991it's just, that I darkly remember a package called rtcom-eventlogger, but I don't even know what it does
17:02.27merlin1991luf: by MAP you mean what?
17:03.18lufMessage Access P(what is it for?) in obexd. To synchronize also SMS/... with HF.
17:03.38merlin1991ah okay, map maps to maps/gps/whatever in my head :D
17:03.55DocScrutinizer05Protocol
17:03.57lufrtcom-eventlogger is from nokia and it's for accessing the sms, call history etc.
17:05.56merlin1991is the dbus interface the -async demon exports something that is based on obexd stuff, or more generic?
17:08.44lufit has two parts. server side and client side (library). Server side is the process what listen on some dbus path and response queries.
17:10.06merlin1991is it reentrant?
17:10.19lufThe client part is for easy calling it:
17:10.21lufgint rtcomel_get_event_async(RTCOMELEventCallback cb, const guint id, const gchar *intcols, const gchar *strcols, gpointer closure)
17:10.21lufgint rtcomel_get_event_list_async(RTCOMELEventListCallback cb, const gchar *query, const gchar *intcols, const gchar *strcols, const guint offset, const gint limit, gpointer closure)
17:10.21lufgint rtcomel_get_event_list_count_async(RTCOMELEventListCountCallback cb, const gchar *query, const guint offset, const gint limit, gpointer closure)
17:10.43lufThis is exported from the client library.
17:13.30lufmerlin1991: the dbus ensure that only once request is answered at a time in server side.
17:14.25lufAnd I see nothing on client side what should be problematic in threads.
17:14.54lufI took an inspiration from eds and DBUS examples on maemo pages :)
17:17.46kerioby the way, why does cssu have "releases"?
17:21.05merlin1991so anybody could use the lib?
17:27.27DocScrutinizer05kerio: that's actually a good question. In fact I'm pushing towards rolling updates since long. We need to get rid of MP as much as possible for that
17:27.46DocScrutinizer05and sort the dependencies mess
17:27.48kerioDocScrutinizer05: there's a problem though
17:28.00kerioHAM can't upgrade non-user, non-metapackage packages
17:28.12DocScrutinizer05:nod:
17:28.30keriofuckin HAM
17:28.34DocScrutinizer05unless they are pulled in as dependency
17:29.07DocScrutinizer05or you put HAM into red-pill mode, aiui
17:29.47merlin1991DocScrutinizer05: which is removed from ham since pr1.2 (or 1.3)
17:29.53DocScrutinizer05ooh, are you 'old enough' to know red-pill?
17:30.01keriohuh, i am
17:30.05kerioand i had my first n900 in pr1.2
17:30.10kerio\_o_/
17:30.16kerioanyway, you also need to tell HAM to show all packages
17:30.21DocScrutinizer05merlin1991: I thought pali recently re-introdiuced it
17:30.36keriowhich is what brings the time apt-worker takes to do his things from 4 minutes to 15 minutes, for me
17:31.28*** join/#maemo-ssu toxaris (~toxaris@90-230-114-186-no34.tbcn.telia.com)
17:45.06DocScrutinizer05merlin1991: how it feels @home again?
17:45.21merlin1991not as hot :D
17:45.25merlin1991but my pc is broken :/
17:45.40DocScrutinizer05eeeew! :-/
17:46.36DocScrutinizer05merlin1991: we need to clean up the mess in ke-recv: http://pastebin.ca/2200289
17:47.18DocScrutinizer05[2012-09-02 17:13:25] <DocScrutinizer05> http://gitorious.org/community-ssu/ke-recv/blobs/master/src/events.c#line149  OOOUUUUUCH!http://gitorious.org/community-ssu/ke-recv/blobs/master/src/events.c#line168   http://gitorious.org/community-ssu/ke-recv/blobs/master/src/events.c#line176   HOLY SPAGHETTI MONSTER W*T*F?!
18:03.34kerioDocScrutinizer05: hmm, could a hexedited image-viewer be distributed by cssu?
18:03.50DocScrutinizer05why not?
18:04.35DocScrutinizer05afaik we already distribute a hexedited libsms.so
18:06.35kerioto do what? :o
18:06.41kerioalso, can't we do the same for fmtxd?
18:08.04lufmerlin1991: sure anybody could use it.
18:13.32*** join/#maemo-ssu NIN102 (~NIN@p5DD2995A.dip0.t-ipconnect.de)
18:14.11DocScrutinizer05kerio: your most hated CBSMS oppername applet
18:14.30DocScrutinizer05basing on patched libsms.so
18:14.33kerioD:
18:14.45kerioi see
18:14.57keriobtw, the current one in -devel hasn't shown the problem again
18:15.18DocScrutinizer05so you wanna say "WFM"?
18:15.30kerioi wanna say "i forgive you"
18:15.35DocScrutinizer05hehehe
18:15.37keriobut i'm still not sure the bug was fixed
18:15.56DocScrutinizer05I feel with and like you
18:28.10*** part/#maemo-ssu fruct (~fruct@188.242.38.250)
18:44.36illuminatacssu was a success. the afternoon dilemma is over it seems
18:45.16illuminatathanks for all the help
18:45.50*** join/#maemo-ssu freemangordon (~freemango@130.204.50.168)
18:49.48kerioilluminata: yay
18:52.21freemangordonDocScrutinizer05: I am not the original author of the spaghetti code ;)
18:52.45freemangordonthere was a patch on the bugtracker, I just applied it
18:53.05freemangordonbut actually code is not that bad, i LIKE goto
18:53.27DocScrutinizer05duuuude!
18:53.33DocScrutinizer05http://pastebin.ca/2200289
18:54.07*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
18:54.30freemangordonhehe
18:54.31DocScrutinizer05:-)
18:55.02freemangordonI am not saying it can't be done much better :p
18:55.48DocScrutinizer05I#m iindeed feeling great relief it's not your crime
18:56.41freemangordonwell, the cases I use backward goto are rare, for example if some counter needs to be reset or such
18:57.05DocScrutinizer05:nod:
18:57.15DocScrutinizer05a SHOULD NOT case
18:57.17DocScrutinizer05~2119
18:57.17infobotThe key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
18:57.28freemangordonbut usually it leads to much clear an simple code than ifs needed to achieve the same
18:58.41DocScrutinizer05sure, there's exactly one accepted usecase for goto:  goto error (forward)
18:59.35freemangordonwell, I disagree, as i indeed like it, there are cases when backward goto saves a lot of code. But agree it should be used with caution
19:00.00freemangordonand only once :D
19:00.29freemangordonnot 3 times in a row
19:01.21freemangordonhttps://bugs.maemo.org/8904
19:01.23povbotBug 8904: Memory card name changes to "mmc-undefined-name" after a couple of days
19:02.55freemangordonDocScrutinizer05: Andrew Zabolotny
19:03.05freemangordonwhoever is that guy
19:07.18freemangordonkerio: btw what is your question about ke-recv?
19:07.35keriofreemangordon: "how the hell does it work?"
19:07.45keriospecifically, how do i trigger the automounter?
19:07.54kerioke-recv-test e /dev/mmcblk1 didn't work
19:08.00freemangordonyou don;t need to trigger it manually
19:08.18freemangordonke-recv-test?
19:08.51freemangordonwhat FS is mmcblk1?
19:09.18freemangordonkerio: ^^^
19:09.27keriommcblk1p1 is vfat
19:09.37keriommcblk1p2 and mmcblk1p3 are linux swap, but they shouldn't be touched
19:09.48keriofreemangordon: another question: how do i choose what gets exported in ass rage mode?
19:10.02freemangordonwell, is it /dev/mmcblk1 or /dev/mmcblk1p1?
19:10.20keriobecause g_file_storage exports the whole of /dev/mmcblk1, which is kinda bad for me, because i *will* be using the swap in mmcblk1p2
19:10.25keriofreemangordon: neither worked
19:10.35kerio"ke-recv-test e" should be "check device"
19:10.44kerionot sure which kind of check
19:11.23freemangordonkerio: something is broken there, I use swap partition on SD card and have no problem with seeing vfat partition in PC
19:11.54keriofreemangordon: i see the vfat partition on pc
19:11.57keriobut i also see the other two
19:11.59keriowhich is... bad
19:12.37freemangordonwell, it is not ke-rcv to balme
19:12.42freemangordon*blame
19:13.45freemangordonI am not dure what will happen if g_file_storage gets /dev/mmcblk1p1 as backing stoeage
19:13.50freemangordon*storage
19:13.59freemangordonWTF is wring with me :(
19:14.34freemangordonseems there is no way to write without typos today, sorry :)
19:16.13freemangordonkerio: actually it is logical(and better) to see the whole SD card when connected to PC, not only the first VFAT partition
19:16.24keriohell naw
19:16.28freemangordonhell yes
19:16.37keriomuch like it's awful that the PC sees the whole emmc instead of just mydocs
19:17.06freemangordonno, it is different, SD card is removable storage
19:17.14keriowell, not on my system
19:17.14kerioso
19:17.17keriohow do i configure this?
19:17.40freemangordonimagine you want to dd an image to your SD card
19:17.48freemangordonconfigure what?
19:18.00kerioconfigure what gets exported in MSM
19:18.09DocScrutinizer05I friggin wonder how swap might be used when same time it's exported assrage
19:18.12keriofreemangordon: imagine what happens if something else writes to the swap partition
19:18.22kerioDocScrutinizer05: kernel magick
19:18.27DocScrutinizer05aiui ass rage umounts all
19:18.46freemangordonswap is not mounted aiui
19:18.59kerioswap does not count as mounted, it's just "in use" in some way by the kernel
19:19.46kerioDocScrutinizer05: notice that i don't know if the pc can actually write to it
19:20.01kerioi have good reasons not to try, obviously
19:22.15freemangordonwell, I wonder what will happen if only the partition (i.e. not MBR) gets exported
19:22.30freemangordonmost probably a mess
19:28.31keriofreemangordon: huh?
19:28.34keriowhy?
19:28.39kerioit's the same as MyDocs
19:29.02kerioit's not a fake MBR, it's just a single partition
19:29.09freemangordonyeah, might be I am wrong.
19:29.09kerioit's a bit weird, but not too much
19:30.32DocScrutinizer05I actually thought uSD would get exported exactly same way
19:30.45DocScrutinizer05only first partiton, if more than one exist
19:30.57kerioi thought so too
19:30.58DocScrutinizer05dunno why I thought that
19:31.33freemangordonme too, but it does not make sense, tell me how you are going to use dd, fdisk, etc if only firs VFAT partition is exported
19:31.50DocScrutinizer05maybe somebody should check on stock freemantle
19:32.06keriofreemangordon: by... removing the uSD and doing that on a card reader?
19:32.08freemangordonthe whole device gets exported
19:32.16freemangordonDocScrutinizer05: ^^^
19:32.29freemangordonno change here
19:32.31keriobesides, you need the appropriate ioctl() call to make the kernel reread the partition table
19:32.44kerioso you can't fdisk properly anyway
19:33.13DocScrutinizer05well, does a plain partiton export differ from a whole device export when the whole device is formatted superfloppy?
19:33.25freemangordonkerio: you can force partition table re-read by simply removing the backcover
19:33.33kerio...
19:33.41kerioSO GET THE CARD OUT AND USE A CARD READER
19:33.44kerioffs
19:34.10freemangordonkerio: well, I don't have card reader, but have 2 n900s :P
19:34.31freemangordonDocScrutinizer05: there is no change to the behaviour compared to stock
19:34.40DocScrutinizer05checked?
19:35.08freemangordonI am using swap on uSD for 2 years or so. Partitioned through PC
19:35.19DocScrutinizer05hmm, fair enough
19:35.55keriofreemangordon: and you open your backcover like that?
19:35.56kerio:s
19:36.37DocScrutinizer05kerio: "opening backover" might work via ke-recv-test
19:37.01freemangordonkerio: the use cases for exporting the whole device are much wider than exporting a single VFAT partition only. for example you may have one vfat visible in every OS, and one EXTx, visible in linux
19:37.19keriofreemangordon: that's why i asked for a way to configure it
19:37.24DocScrutinizer05damn, I looked into precisely all that some 6..12 months ago, can't recall a single detail
19:37.39freemangordonhow the hell you will copy data to that EXTx partition? through wireless?
19:37.49MrPinguRemoving backover is insta-reboot because swap got unmounted
19:37.58kerioMrPingu: not quite instant
19:37.59freemangordonMrPingu: only if active
19:38.13DocScrutinizer05hehe
19:38.34MrPinguWhile I don't have swap on eMMC enabled ;p
19:38.37keriofreemangordon: sshfs/nfs/whateverfs over usb networking, for instance
19:38.53freemangordonkerio: you are aware USB networking is 1.1?
19:38.54DocScrutinizer05wait, there been some syscall to make kernel re-read partition table?
19:39.04keriofreemangordon: usb networking is what?
19:39.06freemangordonsfdisk -R or something
19:39.12freemangordonkerio: USB 1.1
19:39.12kerioDocScrutinizer05: sure, the thing fdisk does when you write
19:39.15keriofreemangordon: o rly
19:39.22freemangordonafaik
19:39.42DocScrutinizer05wut?
19:39.46freemangordonit is not USB 2.0
19:39.50freemangordontry it
19:39.53DocScrutinizer05FFS
19:40.02kerioi distinctly remember getting a fuckload of MB/s
19:40.12keriobesides, g_ether is better anyway
19:40.13freemangordonssh?
19:40.22keriojust the connection
19:40.31keriowith nc
19:40.37keriosend zeros from one side, discard them on the other
19:40.51keriohrmpf, i can't retest now
19:40.57keriobecause otherwise i'd lose VDQ
19:41.05DocScrutinizer05well, I got some 12..14MB/s which is way beyond the max of 12Mb/s of usb1.1
19:41.09freemangordonwell, AFAIK g_ether is not USB 2.0
19:41.20keriothen maybe g_nokia is better
19:41.36DocScrutinizer05in ass rage mode
19:41.43freemangordong_noika is 2.0 AFAIK
19:41.44kerioi wonder if pali's patch to automatically enable usb networking in pc suite mode is already in -devel
19:41.48keriofreemangordon: then use g_nokia
19:41.51keriono biggie
19:41.59freemangordonkerio: under XP?
19:42.11keriono, we're trying to write to an ext3 partition
19:42.18kerioso linux :)
19:42.34freemangordonbut it is not exported anywa, so it does not matter
19:42.38freemangordon:P
19:42.52keriothere's nothing exported, we're trying to work around it
19:42.53freemangordonwhatever
19:43.28freemangordonthe way it is now, is compatible with all of the OSes around, in HS mode
19:43.34kerionope
19:43.47kerioi can't write to an ext3 partition from xp
19:43.56freemangordonare you sure?
19:44.28kerioif we allow using third-party software then there's no reason usb networking via g_nokia shouldn't be allowed too
19:45.13freemangordonkerio: I am missing your point, really. You want us to remove functionality because you have some special use case?
19:45.35kerioI WANT IT TO BE CONFIGURABLE SO I CAN CHANGE IT FROM THE DEFAULT WHICH IS HOW IT IS AND HOW IT'S ALWAYS BEEN TO BETTER FIT MY NEEDS
19:45.36freemangordonThe functionality tha exists in stock fremantle
19:45.44freemangordonthen file a bug dammit
19:46.02freemangordonand stop shouting, ok?
19:46.24kerioOK, FRIEND!
19:46.49freemangordonseems your capslock has stuck
19:46.57keriowas joking
19:47.19freemangordonwas not
19:47.25freemangordonreally, file a bug
19:47.46kerioi just filed a bug!
19:47.53kerioright here!
19:48.17freemangordonno, the place to file a bug is on the bugtracker ;)
19:52.55kerioi'll just wait for pali
19:52.58keriohe's much nicer to me :c
19:53.18keriooh pali, where art thou
19:53.49freemangordonhe has exams, so don't hold your breath :P
19:54.12keriopff, lack of commitment
19:54.17kerioi have two exams this month
19:54.22freemangordonyou'll have to deal with the evil freemangordon :D
19:54.22keriobut am i studying?
19:54.28keriono, i'm slacking off on irc
19:55.49DocScrutinizer05shut up, kids!
19:56.00DocScrutinizer05;-P
19:56.36keriobut we're bored!
19:56.40keriotell us a story, uncle scrutinizer!
19:57.49DocScrutinizer05Sep  2 21:56:26 halebop kernel: [2666849.686045] usb 2-2: new high speed USB device number 15 using ehci_hcd
19:57.50DocScrutinizer05Sep  2 21:56:26 halebop kernel: [2666849.803102] usb 2-2: New USB device found, idVendor=0421, idProduct=01c7
19:57.52DocScrutinizer05Sep  2 21:56:26 halebop kernel: [2666849.803105] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
19:57.53DocScrutinizer05Sep  2 21:56:26 halebop kernel: [2666849.803107] usb 2-2: Product: N900 (Storage Mode)
19:58.09DocScrutinizer05new **high** speed USB device
19:58.22DocScrutinizer05storage mode
20:01.14DocScrutinizer05halebop:/home/jr/Dokumente/downloads/hplip # lsusb -vd 0421:01c7
20:01.15DocScrutinizer05Bus 002 Device 015: ID 0421:01c7 Nokia Mobile Phones N900 (Storage Mode)
20:01.17DocScrutinizer05...
20:01.18DocScrutinizer05<PROTECTED>
20:01.52DocScrutinizer05so much for ass rage is usb1.1
20:02.49keriothis story was boring
20:02.58kerioand freemangordon said g_ether was usb1.1
20:03.15kerionot g_file_storage
20:06.18DocScrutinizer05now THIS story is boring
20:07.08DocScrutinizer05[2012-09-02 21:38:53] <freemangordon> kerio: you are aware USB networking is 1.1?
20:07.10DocScrutinizer05indeed
20:07.14DocScrutinizer05is boring
20:07.29keriobut is it? i don't think so
20:07.36keriog_nokia is faster than 1.1
20:07.53DocScrutinizer05I never ever used g_nokia or usb networking
20:08.01DocScrutinizer05waaay too boring ;-P
20:08.54keriousb networking is the shit
20:09.14keriolagfree, phat throughput
20:10.15DocScrutinizer05knetworkmanager sucks donleyballs though
20:11.10DocScrutinizer05so I would've no internet on laptop when connecting to N900 via USB networking. Unbearable
20:13.15keriowat
20:13.16keriowhy?
20:15.16DocScrutinizer05as soon as I activate PC suite mode, knetworkmanager grabs it and I can't manually config it any more
20:15.33DocScrutinizer05alas knetworkmanager handles it as NIC
20:15.55DocScrutinizer05or rather usb-modem
20:16.00keriohahahahahahah
20:16.07keriotry g_ether then
20:16.09DocScrutinizer05indeed
20:16.17keriobesides, the usb network card is a separate thing
20:17.03DocScrutinizer05maybe, but it already conflicts with normal network connectivity on KDE
20:17.54keriodamn, kde sucks
20:18.10DocScrutinizer05well, currently knetworkmanager thinks there's NO NIC at all, so maybe worth another try, since the NIC this text is traveling over should be invisible and thus unaffected
20:18.20keriooh lol
20:18.55DocScrutinizer05I probably been fed up and configured it as "on-boot" and "manual config"
20:19.45DocScrutinizer05oooh LOL, network manager not running, please start it
20:20.41DocScrutinizer05incredible shit
20:22.06DocScrutinizer05Sep  2 22:21:08 halebop dbus-daemon[996]: dbus[996]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
20:22.37DocScrutinizer05Sep  2 22:21:08 halebop dbus[996]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
20:22.40keriooh poetter
20:22.50DocScrutinizer05indeed
20:22.55DocScrutinizer05~poettering
20:22.55infobot'sth is poettering' means it acts invasive, possessive, destructive, and generally in an egocentric exacerbating negative way. ``this cancer is extremely poettering''
20:23.22keriowhy did we get the pulseaudio dude to redesign init?
20:24.05DocScrutinizer05~lart systemd
20:24.05infobotoverclocks systemd until systemd burns out
20:24.16DocScrutinizer05can't be any hard
20:24.39DocScrutinizer05probably already burned out since 3 days before initial release
20:27.46DocScrutinizer05reason: no such file or directory
20:28.06DocScrutinizer05POETTERING!!!!! WHICH FUCKING no such file???
20:35.20*** join/#maemo-ssu dimir (~dimir@dimir.eu)
20:35.29dimirEHLO!
20:35.57dimirRecently GSM module on my n900 stopped working.
20:36.34dimirIt throws the message "All telephony functions, including emergency calls, are disabled due to a communication error. To recover, you might have to reboot the device."
20:36.39dimirThe well-known error.
20:37.02keriowell, have you tried to reboot the device?
20:37.03dimirSo at first it was appearing once a day or something, reboot was fixing that.
20:37.05kerio:)
20:37.29dimirIt then started to happen more and more often until recently reboots stopped helping completely.
20:37.44keriodimir: btw, why is this related to CSSU?
20:37.53dimirI have followed the threads on maemo forum, like this one: http://talk.maemo.org/showthread.php?t=60881
20:37.53DocScrutinizer05hmm, yeah. fatal :.{
20:38.04freemangordonmaybe he has a solution and wants to share it
20:38.09dimirNop.e
20:38.12dimirdamn.
20:38.36kerio:c
20:38.37dimirThe thread suggests some reflashing otherwise it's h/w problem.
20:38.48dimirBut it seems there were lots of people having such problem.
20:38.55dimirThe thread is of year 2009 though.
20:38.56DocScrutinizer05most common fatal hw defect
20:39.22dimirI was wondering if you know of recent solutions, or things that might be causing this.
20:39.35dimirOr maybe this is known to be fixed in recent images.
20:39.41dimiroh man.
20:39.45dimirI so hope it's not h/w.
20:39.54dimirI'm already using CSSU btw.
20:39.59DocScrutinizer05seems there's been the typical bathtub curve for many early failures then after a few years of 'silence' slow increase of same problem again
20:40.39dimirAh man.
20:40.56dimirBut I just wanted to consult here before I go for a reflash.
20:41.19dimirI mean, it seems there are some reports that reflashing in this kind of state of the phone bricks it.
20:41.39dimirIt's functional properly, all except the GSM module.
20:41.48dimirI mean, wi-fi, etc. all works properly.
20:42.08DocScrutinizer05seems a chip or soldering problem with modem itself
20:42.45DocScrutinizer05some users even can make it come and go by pressing a particular key on hw kbd
20:42.48dimirSo, perhaps taking it to the service could be a good idea?
20:43.04dimirRight.
20:43.12DocScrutinizer05reflow soldering the modem chip *might* help
20:43.29dimirCould be a soldering problem, that'd explain why the problem was first occasional and then going more and more often.
20:43.44DocScrutinizer05yep, soldering or bonding
20:43.47dimirI just am too afraid to do that myself. :-D
20:44.04kerionokia don't care
20:44.07kerionokia don't give a fuck
20:44.12DocScrutinizer05better let it do somebody with proper hot air reflow workstation
20:44.12dimirsure.
20:44.27keriothey'll give you a lumia 900
20:44.34kerioi mean, the number is the same!
20:44.45kerioor maybe a n8
20:44.50keriowhich you can sell to buy another n900 on ebay
20:44.57dimirDocScrutinizer05: so you mean, find the scheme of the phone to locate the modem and take it to a friend that can solder and bond?
20:45.04dimirkerio: :-D
20:45.15DocScrutinizer05nobody can bond
20:45.21dimirkerio: yeah, already was checking some n900-s on eBay. :-)
20:45.27DocScrutinizer05bonding is inside chip
20:45.28dimiroh crap.
20:45.42DocScrutinizer05those hair thin gold wires
20:45.50dimiroooh.
20:46.20DocScrutinizer05but you can try reflow
20:46.26DocScrutinizer05aka 'soldering'
20:46.29keriowhat's reflow?
20:46.37DocScrutinizer05~wiki reflow
20:46.50kerioi see
20:47.20DocScrutinizer05hot air reflow in this case
20:47.44DocScrutinizer05needs quite some experience to do it right
20:47.51DocScrutinizer05and the proper tools
20:48.01dimirYou mean this can be done at home?
20:48.35DocScrutinizer05not really, unless you got a SMT rework station aka hot air / IR reflow soldering station
20:48.52DocScrutinizer05some freaks try it in oven
20:49.07DocScrutinizer05but it usually kills the whole device
20:49.16kerioit works with x360s!
20:49.43DocScrutinizer05you need proper temperature to +/-5°C
20:50.10dimiryeah.
20:50.20dimirThanks for the info!
20:50.22DocScrutinizer05and even then it's not really guaranteed a completely assembled PCB will survive reflow
20:50.32dimirI wonder though, if there is a scheme of the pcb available?
20:50.39DocScrutinizer05sure
20:50.43DocScrutinizer05:-)
20:50.53DocScrutinizer05check wiki
20:51.08DocScrutinizer05there are links to places for download
20:55.37dimirNokia_N900_RX-51_Service_Manual_L1L2_v1_0.pdf ?
20:57.45DocScrutinizer05also helps, yeah
20:58.06DocScrutinizer05usually to be found 2in same directory" as the schematics.pdf
20:58.16DocScrutinizer05s/2/"/
21:01.27DocScrutinizer05dimir: you also might find this helpful: http://maemo.cloud-7.de/Gallery-N900-exploded/
21:02.14dimirDocScrutinizer05: thanks!
21:03.33DocScrutinizer05dimir: pnatd in a terminal may tell if modem is showing *any* life: AT<enter> should answer OK
21:04.35kerioyeah, if the modem can't answer "AT" then it's as toast as it can get
21:05.56dimirDocScrutinizer05: should I run pnatd as root?
21:05.59DocScrutinizer05yes
21:06.32dimirNope, it's not even printing what I type
21:06.32DocScrutinizer05and don't bother to quit the command, you can't (except with "killall pnatd" from other shell)
21:06.47DocScrutinizer05not rpinting what you type is 'normal'
21:06.47dimiryeah, I figured that.
21:06.54dimirOK.
21:07.03dimirSo I type in AT<enter> but nothing happens.
21:07.07dimirI do that via ssh.
21:07.11dimirIf that's OK.
21:07.12DocScrutinizer05send it twice
21:07.14dimirOK.
21:07.25DocScrutinizer05at<enter>
21:07.35dimirAh, lower-case.
21:07.42DocScrutinizer05doesn't matter
21:08.00DocScrutinizer05just press enter key!
21:08.05DocScrutinizer05not type <enter>
21:08.09dimirtwice - does nothing too.
21:08.12kerioLOL
21:08.15dimirLUL
21:08.18DocScrutinizer05though actually even then it should answer error
21:08.27dimirIt just hangs there.
21:08.32dimirNo output.
21:08.36DocScrutinizer05RIP
21:08.46dimirNice.
21:09.18DocScrutinizer05try switching to airplane mode and back to normal
21:09.24DocScrutinizer05then repeat AT
21:09.26dimirJust a sec.
21:09.43dimirI would need to take my ass off the couch.
21:09.44dimir:-D
21:10.16DocScrutinizer05actually you *might* wnat to *remove* the SIM
21:10.23dimirIt's not there.
21:10.29DocScrutinizer05occasionally we seen modems crash on very corrupted SIM
21:10.32dimirI have it in a backup phone.
21:10.39DocScrutinizer05:nod:
21:11.21DocScrutinizer05place a ptch of carton or paper inside SIM holder, to make sure VDD isn't short to metal
21:11.24dimirdidn't help.
21:11.42dimirAh, alright.
21:11.51DocScrutinizer05check syslog/dmesg
21:12.03DocScrutinizer05grep for "cmt" (iirc)
21:14.17DocScrutinizer05dimir: in dialer type "*#06#"
21:14.40DocScrutinizer05should answer with notifier with your IMEI
21:14.54dimirnothing in dmesg and I don't have /var/log/syslog
21:15.22dimirIMEI: <empty>
21:15.36DocScrutinizer05your modem is dead. So sorry for you
21:15.40dimirOh man.
21:16.03dimirSo, you are sure reflashing won't help?
21:16.18DocScrutinizer05a reflash never can hurt, it *might* fix a cmt firmware that for whatever reasons got corrupted
21:16.21keriona`vi is winning ^_^
21:16.42keriodimir: didn't the people in the forums report bricking after reflash?
21:16.48DocScrutinizer05odds are 1000:1 against that
21:17.10dimirkerio: just a couple. :-)
21:17.24keriodo it
21:17.28dimirDocScrutinizer05: OK, do you mean full reflash?
21:17.32keriobackup the important data though
21:17.36dimiryeah.
21:17.38dimirSure.
21:17.39DocScrutinizer05nah, you can't brick a N900 by flashing
21:17.40keriodimir: in theory, the stuff on the emmc doesn't really matter
21:17.55dimirkerio: OK.
21:17.57DocScrutinizer05exactly
21:18.07keriobut meh, i always full reflash
21:18.07dimirSo, just a rootfs?
21:18.09keriojust 'cause
21:18.14dimirAh, right.
21:18.37dimirSo, any link to the latest CSSU image?
21:18.44keriothere isn't one :c
21:18.48DocScrutinizer05no such thing
21:18.52kerioyou need to install pr 1.3 and then upgrade to cssu
21:18.57DocScrutinizer05PR1.3 is latest
21:19.06dimirAh, OK.
21:19.12kerioDocScrutinizer05: why, though?
21:19.15DocScrutinizer05damn, kerio faster than me
21:19.16dimirI think I had it somewhere.
21:19.51DocScrutinizer05kerio: because nobody bothered to fiascogen a CSSU image?
21:20.08keriois it even possible? :o
21:20.16DocScrutinizer05I'd guess it is
21:20.27kerioi mean, nokia managed to do it
21:20.34kerioso it's definetely possible
21:20.34DocScrutinizer05though fiascogen is closed source... so :-S
21:20.38keriobut is it feasible to do?
21:21.02DocScrutinizer05yes, there are custom fisco images
21:21.07kerioneat
21:21.25DocScrutinizer05robbiethe1st did one with BM, NIN101 did a rescue image afaik
21:21.40kerionin101's is weirder, though
21:21.44keriobecause you're supposed to just load it
21:21.51DocScrutinizer05doesn't matter
21:21.56DocScrutinizer05still a fisco image
21:22.17DocScrutinizer05google for fiascogen
21:22.30kerioi don't want to open pandora's jar
21:24.06DocScrutinizer05http://talk.maemo.org/showthread.php?t=74121
21:24.35DocScrutinizer05I have used it successfully to make a flashable image for the NAND memory. By combining a rootfs image and a kernel image in one fiasco image with:
21:24.37DocScrutinizer05Code:
21:24.38DocScrutinizer05fiasco-gen -g -k kernelImage -r rootfsImage -o myOwnFiasco.bin
21:25.20DocScrutinizer05I can flash this image to the N900 with:
21:25.22DocScrutinizer05Code:
21:25.23DocScrutinizer05flasher-3.5 -F myOwnFiasco.bin -f -R
21:38.09DocScrutinizer05DANG! there's a armel fiaco-gen pkg!!!
21:39.11DocScrutinizer05so BM might *finally* learn to create proper self-containing fiasco images
21:39.32DocScrutinizer05incl kernel and all \o/
21:40.07DocScrutinizer05could even create a shellscript for x86 that even contains flasher-3.5
21:40.37dimirAnd you can finally say taa-taa to Nookia?
21:40.54dimirCompletely I mean. :-)
21:41.30DocScrutinizer05BM "create full fiasco".  ass rage copy BMfiasco_2012-09-02.sh to PC. In case of desaster just run it in shell
21:42.37DocScrutinizer05or store to uSD in N900. In case swap uSD to PC and run BMfiasco_2012-09-02.sh to restore
21:43.03DocScrutinizer05~seen robbiethe1st
21:43.06infobotrobbiethe1st is currently on #maemo (1h 15m 32s), last said: 'yeah'.
21:43.13DocScrutinizer05hey!!!
21:49.36DocScrutinizer05dimir:
21:49.41DocScrutinizer05~flashing
21:49.41infobotit has been said that maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware
21:50.03dimirDocScrutinizer05: cheers.
21:55.03*** join/#maemo-ssu taziff1 (~Taziff@cyr108.internetdsl.tpnet.pl)
22:48.12dimirFlashing didn't help.
22:48.37dimirAnd at the end of the flashing (as I saw others reported) there was a message: CMT flashing failed
22:48.52dimirLike:
22:48.53dimir[...]
22:48.55dimirFlashing kernel... done.
22:48.56dimirSending and flashing rootfs image (185728 kB)...
22:48.56dimir100% (185728 of 185728 kB, avg. 13632 kB/s)
22:48.58dimirFinishing flashing... done
22:49.00dimirCMT flashing failed
22:49.13dimirBut it boots and functions as previously.
22:52.08dimir~repository
22:57.30ShadowJKdoes dmesg have stuff about cmt rst rq
23:00.27SpacedOutluf: DocScrutinizer05 :The events.db trigger hack to populate the call durations only works for one call at a time.  I have a package minutemonitor that can handle multiple.  If the triggers get autoinstalled I don't want them.
23:40.00*** join/#maemo-ssu taziff1 (~Taziff@cyr108.internetdsl.tpnet.pl)
23:48.30merlin1991luf: http://gitorious.org/community-ssu/rtcom-eventlogger-async

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.