**** BEGIN LOGGING AT Tue Nov 23 02:59:57 2010 Nov 23 05:44:22 ~moo Nov 23 05:44:22 * apt mooooooooo! I am cow, hear me moo, I weigh twice as much as you. I am cow, eating grass, methane gas comes out my ass Nov 23 06:16:28 DocScrutinizer-8: hey :) what do you think about comparision between n810 and n900 keyboards? And what about the form-factor, would you rather prefer a device as big as n810 or n900? Nov 23 06:16:55 clearly N810 Nov 23 06:17:56 DocScrutinizer: wiki up, thanks! Nov 23 06:17:56 though I'm really used to N900 now. The first ~6 months were a PITA with the N900 kbd, and a feeling like trousers 3 sizes too small with screen Nov 23 06:18:05 * gena2x just checked Nov 23 06:20:10 the N900 has a bit nicer dome switches than N810 (pressure, feedback) but that's realy not related to formfactor. I.E I guess I could swap the N810 domes with N900 spare parts Nov 23 06:35:16 DocScrutinizer: many people say that n810 is too damn big to be used as a phone... Nov 23 06:35:33 I don't care Nov 23 06:36:28 what's the problem? too long distance to microphone when holding the (nonexistent) earpiece to your ear? :-D Nov 23 06:37:45 I'd understand somebody claiming it's too big to *carry* it, but then what's the use of such device when you can't carry it anyway Nov 23 06:37:55 DocScrutinizer: i guess not, as my friend uses n810 as a voip handset just fine. Nov 23 06:38:06 me too Nov 23 06:38:25 and the missing earpiece is a real annoyance Nov 23 06:38:31 DocScrutinizer: my sister says that even n900 is too big and not really useful as she carries a netbook almost all the time with her anyway. Nov 23 06:38:48 weird Nov 23 06:39:36 DocScrutinizer: well, she's got internet access at home, at work, PC's are everywhere around, and on the underground ride it makes sense to take a break and listen to some music or read some book. Nov 23 06:39:39 she should rethink - then she must come to the conclusion it's actually too small to fully replace her netbook Nov 23 06:40:20 DocScrutinizer: yes, exactly. Too small to replace the netbook, too unnecessarily big for a cellphone. Also not comfortable to use with one hand. Nov 23 06:40:37 yes Nov 23 06:40:56 still way more comfortable to use with one hand than FR Nov 23 06:42:27 Hehe, i've recently fall down on people while trying to type "pkill -f -9 fsogsmd; pkill -f -9 fsousaged" while being on a train :) Nov 23 07:04:54 PaulFertser: look at the right hand lower mount hole!! http://www.engadget.com/photos/nokias-qwerty-slidin-n9-shows-up-in-the-wilds-of-china/#3277333 Nov 23 07:11:22 DocScrutinizer: sorry, where exactly? Nov 23 07:12:14 lower right screw hole, you see a helix :-D Nov 23 07:12:48 upper hole has same, though hard to spot Nov 23 07:13:19 now that's smart Nov 23 08:40:26 JaMa: another problem with the latest n900 image... looks like it does not have all the needed modules included Nov 23 08:40:36 there are only very few and touchscreen does not work Nov 23 08:40:46 after installing kernel-modules all is fine Nov 23 08:45:26 mrmoku: http://git.shr-project.org/git/?p=n900-oe.git;a=commit;h=f4f38098f7110f8a81353912c005705adbf9a5e3 this one wasn't merged to OE Nov 23 08:45:55 mrmoku: if those required modules have same name in .28 and .35 then it would be good to add them to machine.conf Nov 23 08:47:29 JaMa: ok Nov 23 08:47:46 have to go to school now... see if my son is behaving nicely ;) Nov 23 08:47:47 bbl Nov 23 08:49:51 heyho Nov 23 08:50:06 hi Nov 23 08:50:47 morphis: can you bump msmcomm SRCREV in oe to something compatible with current fsogsmd rev? Nov 23 08:51:10 I can Nov 23 08:51:23 it does not compile? Nov 23 08:51:49 http://git.shr-project.org/git/?p=n900-oe.git;a=commit;h=f4f38098f7110f8a81353912c005705adbf9a5e3 Nov 23 08:51:54 ups sorry Nov 23 08:51:57 http://tinderbox.openembedded.org/public/logs/task/10791283.txt Nov 23 08:53:26 do you compiling for palmpre machine? Nov 23 08:53:29 and latest msmcommd failed to build too http://tinderbox.openembedded.org/public/logs/task/10800150.txt Nov 23 08:53:41 morphis: on shr buildhost yes Nov 23 08:53:44 jepp I know Nov 23 08:53:52 ok Nov 23 08:54:19 morphis: cornucopia SRCREV was bumped without build test for pre.. and since then pre images were failing Nov 23 08:54:39 freesmartphone.org: 03morphis 07msmcomm * rb72ae4ed3d71 10/libmsmcomm/src/ (Makefile.am frame.c msmcomm.h): libmsmcomm: remove public lowlevel frame handling functionality Nov 23 08:54:43 msmcommd build should be fixed with my next commit on the msmcomm repository Nov 23 08:54:49 great ... Nov 23 08:54:58 * JaMa is curious if someone is actually using "official" pre images from shr buildhost, or if it's wasting cpu cycles there Nov 23 08:55:09 that should at least fix msmcommd build Nov 23 08:55:31 JaMa: no, as I know currently nobody is using the "official" shr images for the palm pre Nov 23 08:55:51 so we can stop building them until it gets back in a reasonable state Nov 23 08:56:38 ok trying to build latest rev and then I'll bump it and stop building those :) Nov 23 08:57:21 but latest rev should not be compatible with latest from fsogsmd Nov 23 08:57:29 so fsogsmd stills fails Nov 23 08:57:35 s/stills/still/ Nov 23 08:57:35 morphis meant: so fsogsmd still fails Nov 23 08:57:41 I will fix this today Nov 23 08:57:50 but first I have to do some other things Nov 23 08:57:52 ah :/ Nov 23 08:57:59 ok, thanks anyway Nov 23 08:58:22 no problem Nov 23 08:58:33 will ping you when fsogsmd is usable again Nov 23 08:58:36 (for the palm pre) Nov 23 08:59:27 ok Nov 23 09:04:12 <[Rui]> JaMa: with yesterday's Linux, yeah, WS still there Nov 23 09:04:39 <[Rui]> moin Nov 23 09:06:42 today I've checked diff -rq of sources before and after switch to one-patch (before adding gta01 support) and no patch is missing now Nov 23 09:07:01 [Rui]: can you confirm that you haven't got WSOD with previous 2.6.34 kernel? Nov 23 09:07:27 <[Rui]> JaMa: I hadn't updated for about two weeks, and was running 2.6.34.7 without WS Nov 23 09:07:40 <[Rui]> then a couple of days ago I updated, and now I get WS Nov 23 09:07:40 [Rui]: or even test it with some older 2.6.34.7 from http://build.shr-project.org/shr-unstable/images/om-gta02/old/ Nov 23 09:07:52 <[Rui]> yesterday, there was a Linux update, still WS Nov 23 09:09:03 <[Rui]> JaMa: I can try with an older 2.6.34.7 sure, you suspect WS may be caused by sth else? Nov 23 09:09:12 yes that update was adding missing wsod fix which never was in shr 2.6.34 Nov 23 09:09:28 only in 2.6.32 Nov 23 09:09:48 <[Rui]> ok Nov 23 09:09:50 well I've updated xf86-video-glamo with Xorg crash fix few days ago Nov 23 09:10:04 <[Rui]> hms... Nov 23 09:10:06 so it could be related but still strange Nov 23 09:10:15 <[Rui]> that would be a likely suspect as well Nov 23 09:10:50 <[Rui]> which one would you suggest, modules-2.6.34.7-oe9+gitr9+e4182f3551f1b8e8f8bd07a2d68e49a0ec4cd04a-r0-om-gta02.tgz ? (plus kernel) Nov 23 09:10:53 [Rui]: but that fix just dispatches cmd queue properly.. shouldn't cause wsod at all Nov 23 09:11:29 [Rui]: yes please test this one Nov 23 09:11:58 also there was small rather formal defconfig update http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=c3119c5f43a91c265a51db469c446c89d5d3cc54 Nov 23 09:13:47 [Rui]: if it works then uImage-2.6.34-r4-oe10-om-gta02.bin and oe12 Nov 23 09:14:03 <[Rui]> rebooting Nov 23 09:17:31 <[Rui]> blanked... so let's give it a few more minutes Nov 23 09:19:55 morphis: msmcomm* built fine with that rev and also fsogsmd compiled fine with it, should I push it to OE (to have something which builds) or should I wait for your ping? Nov 23 09:20:22 hm Nov 23 09:20:25 push it Nov 23 09:20:35 I will bump it later anyway Nov 23 09:20:37 fsogsmd-1_0.5.0+gitr852+8fa36faa70f85c168124dfd020d87796cd155a53 it's not latest Nov 23 09:20:57 but thats the current version in OE? Nov 23 09:21:01 yes Nov 23 09:27:33 <[Rui]> JaMa: got a whitescreen with that Linux Nov 23 09:28:03 <[Rui]> so let's try oe10 and oe12 Nov 23 09:37:08 <[Rui]> I either didn't wait long enough, or have no WS with oe10 Nov 23 09:38:12 [Rui]: if you got it with this then it will be in oe10 and 12 too (they are newer) Nov 23 09:38:43 s/this/2.6.34.7-oe9+gitr9/ Nov 23 09:38:43 JaMa meant: [Rui]: if you got it with 2.6.34.7-oe9+gitr9 then it will be in oe10 and 12 too (they are newer) Nov 23 09:42:33 <[Rui]> JaMa: yeah, and it checks Nov 23 09:43:48 <[Rui]> gotta go to work. bye Nov 23 09:43:48 hey, I'm using newupgrades from yesterday and I'm not having wsod here Nov 23 09:44:05 <[Rui]> pespin: it's not "of death" :) just WS Nov 23 09:44:18 <[Rui]> pespin: maybe you need to let it go blank for a longer time Nov 23 09:44:36 [Rui], been using it since yesterday without any white screen Nov 23 09:45:03 tried waiting for abou 10 min without problems Nov 23 09:58:36 pespin: that sort of WS showing after some time is something only some devices suffer from... since ever Nov 23 09:58:51 * mrmoku happens to have one of those devices where it happens reliably after 2mins :/ Nov 23 10:26:05 hi guys Nov 23 10:26:26 i got some time to try to fight new WS Nov 23 10:27:19 JaMa: so, have you find patch responsible for ws? Nov 23 10:28:19 gena2x: the one you pointed was missing in all SHR built 2.6.34 Nov 23 10:28:33 yeah, i can recall it Nov 23 10:28:38 gena2x: but [Rui] and mrmoku have wsod even with it Nov 23 10:28:48 so nothing changed? Nov 23 10:29:11 probably not (I don't have wsod with and without) so don't know Nov 23 10:29:35 as far as i know this kind of ws is 'blank then wait 3 minutes'? Nov 23 10:29:45 yes Nov 23 10:29:50 is it recoverable? Nov 23 10:29:52 i bet yes Nov 23 10:29:54 yes Nov 23 10:30:12 and btw that patch from qtmoko doesn't apply cleanly on top of kms patches.. Nov 23 10:30:26 so I've used the version I had in shr 2.6.32 Nov 23 10:30:40 hopefully I've rebased it right back then Nov 23 10:31:01 at least it worked before with 2.6.32 Nov 23 10:31:04 ok, first of all i'll try shr kernel and try to reproduce wsod here Nov 23 10:33:30 i think one of patches fixed exactly this kind of wsod - recoverable and unblank, just can't recall which one. Nov 23 10:33:42 need to check old logs... Nov 23 10:36:06 gena2x: http://gitorious.org/~jama/htc-msm-2-6-32/openmoko-kernel/commit/6167442376dc8e0c6580dc60d752802afa8e1e7b ie this one? Nov 23 10:37:27 nono, i mean one of my two patches, let me dive into it... Nov 23 10:53:08 gena2x: note, that this WS does not happen equally on all devices... just some devices suffer Nov 23 10:53:29 my theory is that all suffer if you wait long enough :P Nov 23 10:57:53 last time i got my WSOD then switched to new compiler version Nov 23 10:57:59 s/last/one/ Nov 23 10:58:52 some optimisation/reordering and bah Nov 23 11:04:08 ~apt Nov 23 11:04:12 ~moo Nov 23 11:04:27 apt :( Nov 23 11:04:41 i am missing you... Nov 23 11:05:16 growl, timing-related WSoDs :( Nov 23 11:05:34 not really new. Nov 23 11:05:47 i bet this like 'temperature' related Nov 23 11:30:29 daaaaaamn, depmon in nand... Nov 23 11:30:39 s/depmon/depmod/ Nov 23 11:30:39 gena2x meant: daaaaaamn, depmod in nand... Nov 23 12:10:14 ok, i can't reproduce it here Nov 23 12:10:25 downloaded shr kernel Nov 23 12:10:33 and modules (oe13) Nov 23 12:11:12 but that's only with kms, does it work correctly with your rootfs? Nov 23 12:11:14 boot, (framebuffer-only), om screen power 0 for a while , resumed fine Nov 23 12:11:35 s/resumed/unblanked/ Nov 23 12:11:35 gena2x meant: boot, (framebuffer-only), om screen power 0 for a while , unblanked fine Nov 23 12:11:39 here is same kernel with normal FB http://build.shr-project.org/tests/jama/kernel-nodrm/ Nov 23 12:11:56 hey, kms version seem working Nov 23 12:12:59 i got here http://build.shr-project.org/shr-unstable/images/om-gta02/ Nov 23 12:13:14 so... Nov 23 12:13:27 one more test with refrigerator Nov 23 12:13:32 ok, just surprised, because someone reported it didn't work with qtmoko rootfs IIRC Nov 23 12:14:52 it does not really work (qtmoko is not loading for some reason), but ssh and general framebuffer works Nov 23 12:15:11 i mean qtopia is not loading Nov 23 12:15:18 (qtmoko v28 btw) Nov 23 12:15:51 anyway - no surprise it is working, as it only need framebuffer Nov 23 12:17:36 after refrigerator it still working Nov 23 12:17:41 so... bad news Nov 23 12:18:50 mrmoku: is it easy to reproduce WS? Nov 23 12:19:41 but i can't believe so many people have it and i can't reproduce Nov 23 12:22:01 may be this somehow related to userspace? Nov 23 12:24:48 ok, i'll try to chroot to shrs rootfs and run X server Nov 23 12:29:31 SHR: 03mail 07libphone-ui-shr * r3f1f05e5057e 10/src/view/message-new-view.c: message-new-view: fixed the new-line management in content, avoiding extra space usage Nov 23 12:34:25 heh, starting Xserver in this way (chroot to shr) lead to nice example of total WSOD Nov 23 13:00:06 SHR: 03mail 07libphone-ui-shr * rec494b5adbcc 10/src/view/message-new-view.c: message-new-view: improve the previous commit Nov 23 13:06:11 gena2x: for me... very easy... very reliably Nov 23 13:06:45 gena2x: and I'm convinced that it _depend's on the device_ too Nov 23 13:06:50 not just a software thing Nov 23 13:07:24 can you try to disable X server, reboot and reproduce on base system? Nov 23 13:08:11 gena2x: not right now... got to take care of my little son Nov 23 13:08:22 will do as soon as possible Nov 23 13:08:30 ok Nov 23 13:36:11 gena2x: ps ax: http://shr.pastebin.com/VEn00tpJ Nov 23 13:36:16 gena2x: and I have a white screen Nov 23 13:36:59 have you really reboot, may be better poweroff/poweron and disabled X on boot? Nov 23 13:37:30 I set 3 as default level in inittab Nov 23 13:37:53 no fso/phonefsod/phoneuid whatsoever is started Nov 23 13:37:53 so x driver should not be related... Nov 23 13:38:03 did just reboot though Nov 23 13:38:05 no poweroff Nov 23 13:38:22 * mrmoku retries with pulling the battery before boot Nov 23 13:42:01 seem no ws? :) Nov 23 13:44:10 gena2x: screen all white no ws? Nov 23 13:44:39 just it took longer for testing... Nov 23 13:44:56 so, same after full power off? Nov 23 13:45:13 still waiting... as without phonefsod there is no dimming Nov 23 13:46:05 hmm... in my test before it was suspended... and after resume there was the white screen... Nov 23 13:46:21 maybe I should test with just no x and fso running? Nov 23 13:47:22 yes, actually only x talk to glamo Nov 23 13:47:47 i think you can blank via ssh Nov 23 13:47:55 i am using omhacks tool Nov 23 13:48:15 * mrmoku installs omhacks Nov 23 13:48:43 om screen power 0 & om screen power 1 Nov 23 13:49:01 ok, screen is off now Nov 23 13:49:06 * mrmoku waits two minutes Nov 23 13:50:40 DAAAAAMN! Nov 23 13:51:16 i forgot damn bug with sd card and kms kernels... grrrr... it killed my fs Nov 23 13:51:50 again Nov 23 13:52:20 gena2x: turned screen back on.... and.... is WHITE :) Nov 23 13:52:48 mrmoku: can you try with nondrm kernel? Nov 23 13:52:52 om screen power 0 and om screen power 1 brings it back online? Nov 23 13:53:20 gena2x: yeah, did that Nov 23 13:53:24 ahh Nov 23 13:53:26 moment Nov 23 13:53:31 dmesg here btw. http://shr.pastebin.com/i0ubRGCe Nov 23 13:53:33 ? Nov 23 13:53:45 gena2x: yup, brings it back online Nov 23 13:54:05 can you try mine kernel? Nov 23 13:54:16 sure Nov 23 13:54:20 where ? Nov 23 13:54:29 http://www.bsdmn.com/openmoko/gpsfix/ Nov 23 13:54:34 for example this one Nov 23 13:54:42 uImage-b6.bin Nov 23 13:54:50 modules-b6.tar.gz Nov 23 13:55:19 boot just to command line of course Nov 23 13:56:37 i thought it were ThibG patch which fixed exactly WS like you have Nov 23 13:56:55 it did back then (at least I thought too) Nov 23 13:58:11 * mrmoku rebooting Nov 23 13:58:18 (with power off in between :P) Nov 23 13:58:30 <[Rui]> Heinervdm: hi, yeah that screenshot looks weird, where do you have th ecode? Nov 23 13:58:40 <[Rui]> any news about the WS? Nov 23 13:59:26 we speaking about it Nov 23 13:59:43 [Rui]: so, you installed other kernel version, and no more WS? Nov 23 14:00:12 <[Rui]> gena2x: no, even with a kernel from the end of October (like I had before the upgrade) I get the WS Nov 23 14:00:18 <[Rui]> it's being caused by something else. Nov 23 14:00:34 <[Rui]> gena2x: this morning I tried older kernels with JaMa Nov 23 14:00:49 heh Nov 23 14:01:02 Qi disliked your kernel and booted the other partition instead :P Nov 23 14:01:34 ohh Nov 23 14:01:41 -rw-r--r-- 1 root root 1405 Nov 23 14:48 uImage-b6.bin Nov 23 14:01:46 kernel that small would be nice ;) Nov 23 14:01:58 clever Qi :) Nov 23 14:02:18 * mrmoku refetches Nov 23 14:02:21 JaMa: yup, indeed :P Nov 23 14:02:28 mrmoku: just remane it Nov 23 14:02:28 more clever then me :(/ Nov 23 14:02:33 *rename Nov 23 14:02:42 ah, Nov 23 14:02:45 size. Nov 23 14:02:47 ok :) Nov 23 14:02:53 -rw-r--r-- 1 root root 2437692 Nov 23 14:55 uImage-b6.bin Nov 23 14:02:54 better Nov 23 14:03:10 name is ok Nov 23 14:03:15 will it find it? Nov 23 14:03:19 yeah, I did the link Nov 23 14:03:26 do not forget depmod Nov 23 14:03:39 I did Nov 23 14:04:15 [Rui]: the code is at home, can 't show you now :( Nov 23 14:04:50 <[Rui]> Heinervdm: ok, yesterday you /quit'ted just a bit too soon :) Nov 23 14:05:11 ok, screen off... waiting 2min Nov 23 14:05:21 [Rui]: :) will show you this evening Nov 23 14:05:39 <[Rui]> Heinervdm: bad Heinervdm, should use a repo always ;) Nov 23 14:06:12 [Rui]: hmmm.. thanks. Nov 23 14:07:38 something else and not X Nov 23 14:08:44 and also in debian Nov 23 14:09:00 with kernel from Mirv... hm. Nov 23 14:09:18 gena2x: yup, white screen too Nov 23 14:09:26 root@om-gta02 ~ # cat /proc/version Nov 23 14:09:26 Linux version 2.6.34b6-v28 (gena@work) (gcc version 4.4.5 20100824 (prerelease) (Debian 4.4.4-11) ) #17 Thu Nov 4 23:08:37 MSK 2010 Nov 23 14:10:07 and power 0 & 1 recovers Nov 23 14:10:24 * gena2x going to install shr Nov 23 14:11:01 gena2x: want me to try your rootfs too? Nov 23 14:11:31 you may try qtmoko v28 Nov 23 14:11:47 if your NAND is free for example Nov 23 14:11:51 it has v34 kernel Nov 23 14:11:57 ok Nov 23 14:12:25 http://sourceforge.net/projects/qtmoko/files/ Nov 23 14:12:34 get uImage-v28.2.bin kernel Nov 23 14:13:57 JaMa: anyone is going to squash bloody sd card corruption on umount kms bug? Nov 23 14:14:49 JaMa: consider question as addition to the kms-fb talk :) or nobody else has it? Nov 23 14:15:50 * gena2x really recalled what were problem with kms Nov 23 14:22:51 * JaMa didn't have fs corruption for long (with .34) but I got one lately.. maybe probability of broken fs after reboot is corresponds with drm cmdq flushing frequency Nov 23 14:23:09 s/ is// Nov 23 14:24:31 may be really my current problems with fs is not related with that bug. but it definetly were reason. Nov 23 14:24:40 s/is/are/ Nov 23 14:24:40 gena2x meant: may be really my current problems with fs are not related with that bug. but it definetly were reason. Nov 23 14:26:09 if broken fs is really only with kms enabled then I would probably drop kms support from official shr kernels (as nobody seems using it anyways..) Nov 23 14:26:26 gena2x: ok, qtmoko booted... what now? Nov 23 14:26:36 apt-get install omhacks Nov 23 14:26:58 and om screen power like before Nov 23 14:27:20 what ip does qtmoko have? Nov 23 14:27:42 192.168.0.220 i think, but never used it Nov 23 14:27:50 may be 202 Nov 23 14:27:55 yeah, 202 Nov 23 14:28:12 hmm... does not let me in Nov 23 14:28:22 my usual quest is qterminal and change it to 1.5 Nov 23 14:28:27 root? Nov 23 14:28:36 yup Nov 23 14:28:37 empty password? Nov 23 14:28:39 yup Nov 23 14:28:47 hmmm Nov 23 14:28:48 I think so at least I did not give one Nov 23 14:29:01 go terminal Nov 23 14:29:06 and do passwd... Nov 23 14:29:12 or Nov 23 14:29:24 hm, i can't recall if qtmoko has password Nov 23 14:29:44 ahh... found the terminal :P Nov 23 14:30:42 if ssh responds, only password or login name can be wrong Nov 23 14:31:27 or you connecting not to qtmoko Nov 23 14:31:36 may be 202 is localhost Nov 23 14:32:13 i dunno, i have 192.168.0 as main network, so i have to reconfigure always to 192.168.1. Nov 23 14:33:03 heh Nov 23 14:33:08 disconnect :( Nov 23 14:33:34 check ip with ifconfig in qtmoko terminal Nov 23 14:33:43 no, it was known-hosts on my laptop Nov 23 14:33:45 :P Nov 23 14:33:58 running apt-get install omhacks Nov 23 14:34:00 ah, rm line from ~/.ssh Nov 23 14:34:06 yeah, yeah Nov 23 14:34:58 ok, screen is off now... will go downstairs eat a piece of cake and admire the white when I come back :P Nov 23 14:37:22 JaMaOff: i can say, that i never saw any sd corruption with non-kms version Nov 23 14:39:00 JaMaOff: and contrary, now i boot kms kernel and bah. apt-cache segfaulted. Nov 23 14:39:41 (after reboot with fb kernel) Nov 23 14:39:55 it's totally possible kms is not related in this case Nov 23 14:40:03 gena2x: yup, screen is white Nov 23 14:40:29 mrmoku`: so, thanks for testing. Nov 23 14:40:42 and power 0 & 1 recovers as expected Nov 23 14:40:48 gena2x: well... yw :) Nov 23 14:41:08 it's totally clean that it is not related to shr userspace Nov 23 14:41:51 and that it will be insane to debug for me :( Nov 23 14:42:07 without a device that behaves like that... difficult Nov 23 14:42:36 i have one slight idea you can test Nov 23 14:42:44 no, impossible Nov 23 14:43:05 so, this means that just qtmoko has too few users Nov 23 14:43:35 no Nov 23 14:53:16 SHR: 03mail 07libphone-ui-shr * rb38ede1896db 10/src/view/message-new-view.c: message-new-view: correctly show the msg count when reached the char limit Nov 23 15:00:52 gena2x: either that or only lucky users which have a 'good' device Nov 23 15:01:51 it is very possible that it is just software bug Nov 23 15:02:21 for example some component is used in way out of specifications Nov 23 15:02:52 and on some devices such usage is working on other doesn't Nov 23 15:03:28 and as we really have no glamo and lcd specifications, it's not easy to check this Nov 23 15:04:19 yeah, what I meant is that it shows on some hardware but not all Nov 23 15:04:24 sure it might be a software bug Nov 23 15:04:41 a kernel bug probably Nov 23 15:09:16 mrmoku: btw, did you power-off before booting qtmoko? Nov 23 15:11:24 yup Nov 23 15:11:31 including a pull of the bat Nov 23 15:11:46 you have qi btw?.. Nov 23 15:11:51 yup Nov 23 15:12:24 hm. this is different part in our bootchain :) Nov 23 15:12:34 but it should work Nov 23 15:13:13 hmm... I could install u-boot to see if it makes a difference... later though Nov 23 15:13:18 nono Nov 23 15:43:57 freesmartphone.org: 03morphis 07msmcomm * re8728dbef575 10/libmsmcomm/src/message_types.c: libmsmcomm: enable get_sms_center_number message Nov 23 15:44:04 freesmartphone.org: 03morphis 07msmcomm * rc2219b010ded 10/libmsmcomm/src/event_misc.c: libmsmcomm: remove link established event as it is not used anywhere Nov 23 16:09:12 hi all together! Nov 23 16:09:18 can someone help me with this: http://tinderbox.openembedded.net/public/logs/task/10953634.txt Nov 23 16:09:35 i'm trying to build for palmpre but it fails at do_rootfs everytime Nov 23 16:13:32 Slyon: do you have any special packages added to image or is it as is from OE master? Nov 23 16:13:58 its OE master Nov 23 16:14:09 Slyon: I would start with lvm2 rebuild and whatever recipe provides device-mapper Nov 23 16:14:25 JaMaOff: okay will try Nov 23 16:14:54 SHR: 03mail 07libphone-ui-shr * rc1775ff65914 10/src/view/ (contact-list-common.c message-new-view.c): contact-list-common: show the contact user image only if the file exists Nov 23 16:21:56 JaMaOff, another thing: vala-terminal doesn't start on my neo. It returns this error: Nov 23 16:22:09 vala-terminal: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory Nov 23 16:22:22 is this a known issue? Nov 23 16:24:09 JaMaOff, any my shr-lite-image do_rootfs fails again. i rebuilded (-c clean and -c build) lvm2 and device-mapper. but it gives the same error Nov 23 19:02:09 [Rui]: here is the code: http://heinervdm.dyndns.info/shr-git/libphone-ui-shr/src/phoneui-calendar.c and here the .edc: http://heinervdm.dyndns.info/shr-git/libphone-ui-shr/data/calendar.edc i hope you can help me :) Nov 23 19:57:52 <[Rui]> Heinervdm hi Nov 23 19:58:03 [Rui]: hi Nov 23 19:58:59 <[Rui]> Heinervdm: it's view/calender-month-view.c right? Nov 23 19:59:25 [Rui]: oh yes, i linked the wrong file Nov 23 20:01:05 <[Rui]> Heinervdm: urk, can't help you... I tried to do a similar thing and got to that same horrible result Nov 23 20:01:18 <[Rui]> Heinervdm: it has to do with sizing of the thing you'r swallowing Nov 23 20:01:43 <[Rui]> did you try to swallow a box with the month view inside it, instead? Nov 23 20:02:08 [Rui]: no, i haven't tried anything else Nov 23 20:02:50 <[Rui]> Heinervdm: but I eventually gave up on that... because of that all that's edje-ified in elmdentica is the main genlist view Nov 23 20:03:29 <[Rui]> have to go home, hopefully will be able to check from here. Nov 23 20:03:31 <[Rui]> there Nov 23 20:09:51 Hey! Check this out, a real-life dead-lock: http://i.imgur.com/l8UoK.jpg Nov 23 20:24:46 PaulFertser: hehe, fun :P Nov 23 20:24:54 (to watch from the window ;) Nov 23 20:25:28 mrmoku: if the drivers actually were sane and obeying the rules, they wouldn't get into such a state. Nov 23 20:25:46 yeah, sure Nov 23 20:31:34 Slyon|away: than check in what's pulling those to image and if they are also pulled in http://build.shr-project.org/shr-unstable/images/om-gta02/shr-lite-eglibc-ipk--20101122-om-gta02-testlab/depends-nokernel-nolibc-noupdate-nomodules.dot Nov 23 20:32:13 PaulFertser: lol :) Nov 23 20:37:04 Slyon|away: morphis fixed that in OE master :) Nov 23 20:38:25 JaMaOff, jepp, i know. i talked to him in #openmoko-de Nov 23 20:38:31 JaMaOff, thanks anyways Nov 23 20:49:34 JaMaOff: is it correct that there are 3 libnss_...so.3 files not in eglibc-dev package? Nov 23 21:11:28 now it's too big... http://scap.linuxtogo.org/files/fd99e8740fe6aac008b0e204184eb40e.png Nov 23 21:11:43 and the buttons are still missing Nov 23 23:00:31 <[Rui]> ah, btw... I found a small problem with SHR and E17 Nov 23 23:00:46 <[Rui]> where are the icon theme settings? :) Nov 23 23:00:57 <[Rui]> missing, I tells ya Nov 23 23:20:24 hi, it seem that my bluetooth keyboard is finally working on the n900 with some scripts and config modifications Nov 23 23:20:42 hi mrmoku Nov 24 02:24:43 SHR: 03mail 07libphone-ui-shr * rda69fb548580 10/src/view/ (message-show-view.c message-show-view.h): message-show-view: code cleanup Nov 24 02:24:47 SHR: 03mail 07libphone-ui-shr * r9bc8f5331ee7 10/src/view/message-list-view.c: message-list-view: added "call" button in hoversel Nov 24 02:24:51 SHR: 03mail 07libphone-ui-shr * r782d810cb25b 10/src/view/ (message-show-view.c message-show-view.h): message-show-view: added forward support in hoversel Nov 24 02:25:03 SHR: 03mail 07libphone-ui-shr * r30f884cf5641 10/src/view/ (message-show-view.c message-show-view.h): message-show-view: don't show the "Call", "Add contact" buttons if not needed Nov 24 02:26:27 SHR: 03mail 07libphone-ui-shr * r908a2aefd077 10/src/view/message-list-view.c: message-list-view: show the "Answer" and "Call" buttons only on inbound messages **** ENDING LOGGING AT Wed Nov 24 02:59:58 2010