IRC log of #maemo for Sunday, 2012-08-26

*** hazchemix has quit IRC00:00
*** Kild has joined #maemo00:03
*** Kild has quit IRC00:06
Lava_Croft but i guess Kild left00:09
*** valeriusN has left #maemo00:10
*** valeriusN has joined #maemo00:11
*** mase76 has quit IRC00:19
*** mase76 has joined #maemo00:20
*** shanttu has quit IRC00:27
*** MrPingu has quit IRC00:30
*** zsolt_hun has quit IRC00:39
*** ferdna has quit IRC00:40
*** ferdna has joined #maemo00:41
*** MrPingu has joined #maemo00:44
DocScrutinizer05Lava_Croft: is there a proper instruction how to run something "as administrator" under windows? (sorry, windows noob here)00:46
*** philipl has quit IRC00:47
DocScrutinizer05I thought I once heard sth about holding shift while clicking on some menu entry, or whatever00:47
DocScrutinizer05or maybe even better: is there something similar to "su -" for windows cmd shell?00:48
*** dhbiker has quit IRC00:49
DocScrutinizer05bedmhm, thanks00:49
befordright click, run as administrator00:49
DocScrutinizer05beford: ^^^00:49
DocScrutinizer05hmm, so you could do that on cmd itself?00:49
befordyea, type cmd on the search box, when cmd appears on the menu right click it00:50
DocScrutinizer05(I.E. right click on "open dosbox" or whatever it's called)00:50
*** MrPingu has quit IRC00:51
DocScrutinizer05incredible if there's no way to change user on commandline in windows00:51
befordthere used to be runas.exe00:51
DocScrutinizer05well, must relate to window and shell being just one process on that "OS"00:51
DocScrutinizer05aaaah, runas.exe :-)00:52
befordyea but since windows vista it's not only running as a different user, even if your user has administrator privileges, when you start a shell or app by default it doesn't have those privileges so there is this new "run as administrator" menu entry00:53
DocScrutinizer05sigh, yeah, they got those per-invocation requesters as a 'fix' for everybody and his dog usually running under admin rights anyway00:54
DocScrutinizer05right, I forgot00:54
befordyea, UAC and people just disable it so heh00:55
beford>> It aims to improve the security of Microsoft Windows by limiting application software to standard user privileges until an administrator authorizes an increase or elevation. <<00:55
DocScrutinizer05right, UAC been the "name"00:55
DocScrutinizer05sounds a bit like aegis ;-P00:55
DocScrutinizer05only that with aegis, only Nokia can authorize elevate00:56
befordand itsnotabigtruck :P00:57
*** Ian-- has quit IRC01:04
*** Ian-- has joined #maemo01:07
*** mase_76 has joined #maemo01:07
*** mase76 has quit IRC01:11
DocScrutinizer05indeed ;-)01:12
*** livelace has quit IRC01:12
*** e-yes has quit IRC01:13
*** OkropNick has quit IRC01:16
*** valeriusN has left #maemo01:23
DocScrutinizer05btw ((<Estel_> and year ago it had more competent community than 2 years ago...  <Estel_> javispedro, well, from someone inside Maemo Community, thats the feeling)) actually I pretty much believe that's correct. Quite some part of "community" indeed came late and now thinks they are the smartest bunch ever, and all they have for those on whose shoulders they're standing is despise01:23
*** valeriusN has joined #maemo01:23
DocScrutinizer05doesn't mean this is justified by anything though01:28
DocScrutinizer05s/that's correct/the second quote is correct/01:29
*** Neutron8 has quit IRC01:29
*** Neutron8 has joined #maemo01:30
*** ced117 has quit IRC01:30
*** |thunder has quit IRC01:38
*** sambo7 has joined #maemo01:43
*** |thunder has joined #maemo01:45
*** guampa has joined #maemo01:57
*** guampa is now known as Guest2312001:57
*** markinfo has quit IRC01:57
*** Guest23120 has quit IRC01:58
*** markinfo has joined #maemo01:58
*** guampa_ has joined #maemo01:58
*** guampa_ is now known as guampa02:00
*** retro|cz has quit IRC02:03
*** brzys has joined #maemo02:05
*** mase_76 has quit IRC02:10
*** mase76 has joined #maemo02:11
*** markinfo has quit IRC02:32
*** sambo7 has quit IRC02:33
*** jhb1 has joined #maemo02:46
*** jhb has quit IRC02:49
*** mase76 has quit IRC02:51
*** otep has joined #maemo02:53
*** jonwil has joined #maemo02:53
*** jhb1 has quit IRC02:57
*** r00t|n900 has joined #maemo02:57
*** florian has quit IRC03:13
*** whsailing has joined #maemo03:15
*** brzys has quit IRC03:15
*** whsailing has left #maemo03:28
*** krayon has quit IRC03:30
*** Vibe has quit IRC03:30
*** Vibe has joined #maemo03:31
*** pauly has joined #maemo03:38
*** pauly is now known as Guest5267703:38
*** Guest52677 is now known as pauly1203:39
*** Rantwolf has quit IRC03:39
*** MacDrunk has joined #maemo03:41
*** retro|cz has joined #maemo03:42
*** githogori has quit IRC03:42
*** MacDrunk has left #maemo03:42
*** Gizmokid2005 has quit IRC03:44
*** ArGGu^^ has quit IRC03:44
*** Gizmokid2005 has joined #maemo03:48
pauly12i miss the n90003:48
pauly12no other phone takes raw pics03:49
*** ArGGu^^ has joined #maemo03:56
*** pauly12 has quit IRC03:57
*** ferdna has quit IRC04:02
*** uen| has joined #maemo04:05
jacekowskiraw pics from shit senor are still shit04:07
jonwilI have yet to see a cellphone camera sensor that is as good as even my fairly-entry-level Canon point & shoot04:08
jacekowskiraw is barely useful on DSLRs or other high end camera04:08
*** uen has quit IRC04:09
*** uen| is now known as uen04:09
*** Neutron8 has quit IRC04:09
jacekowskiunfortunately, if your picture is overexposed/underexposed/broken in any other way - raw won't help you04:09
*** r00t|n900 has quit IRC04:12
*** Neutron8 has joined #maemo04:12
jacekowskiwell, if picture i taken in good light you will have hard time telling difference between n900 and your camera if it's on standard 9x13 print04:13
*** TrD has quit IRC04:13
jacekowskiif you have enough light there is a lot you can do even with bad sensor04:14
jonwilMy Canon is much better at taking far away shots with its 10x optical zoom04:14
jonwiland much better at taking close up shots with its really good macro mode04:15
jacekowskimacro mode just enables close focusing04:16
jonwilyes but not all cameras are good at it04:17
jonwilLike the Sony I owned once (piece of junk that was)04:17
jacekowskisony now makes good EVIL cameras04:17
jacekowskiand well, their DSLRs are not bad either04:18
jonwilI would never buy another Sony product, not after some of the Sony crap I have bought over the years04:18
jacekowskiwell, i've bough samsung point and shoot04:18
jacekowskias a gift for someone04:19
jacekowskiand well, for the money, pictures are great04:19
jonwilI would only ever buy Canon cameras, I have used several and they are good04:19
jacekowskithough my dslr that costs 10x as much takes better pictures04:19
jacekowskibut i'm well surprised how samsung got into doign everything electronic04:20
jacekowskiand they are good at it04:20
jonwilI have a family member who swears by the Canon DSLRs (and is always putting new ones on his wishlist :)04:20
jacekowskinikon is much better04:20
jacekowskiand backwards compatible with lenses from first nikon dslrs04:20
jonwilI have both a Samsung LCD monitor and a Samsung LCD TV and they are really good04:20
jacekowskithough it's silly how much you have to pay for some of the features04:21
jacekowskiwifi - extra £15004:21
Luke-Jrmeh, a camera's a camera.04:21
jacekowskiwhile samsung camera has it all and costs £130 in total04:21
jacekowskiLuke-Jr: it's not as simple as that04:21
jonwilWhat I dont get is why cellphone companies seem to be rushing to put higher resolution sensors in their phones... When you increase the resolution like that but dont increase the physical size, less light hits each individual sensor and therefore the images aren't as good (especially in anything other than perfect light)04:24
jacekowskipeople don't know that04:25
jacekowskiall they compare is megapixels04:25
*** LaoLang_cool has joined #maemo04:31
SpeedEvilIt's not that simple.04:34
SpeedEvilIf you have a 5mm sensor, and then put double the number of photosensitive devices on it, the signal out does not change, unless the 'fill factor' changes.04:34
SpeedEvilSurely - the individual noise per device changes - but once you 'bin' them into a resulting image, it does not change.04:35
SpeedEvilExceeding the lens resolution can have other plusses - it reduces the colour artifacts due to the bayer matrix.04:35
SpeedEvilAlso - go and look at the 'dpreview' review of the nokia 808 pureview04:36
*** Neutron8 has quit IRC04:37
SpeedEvilIt's actually not terrible, even uncropped.04:38
*** Neutron8 has joined #maemo04:39
*** Neutron9 has joined #maemo04:44
*** Neutron8 has quit IRC04:44
*** atlas has joined #maemo04:45
*** nox- has quit IRC04:46
*** lxp has joined #maemo04:49
*** lxp1 has quit IRC04:51
*** valeriusN has left #maemo04:53
*** valeriusN has joined #maemo04:53
*** mlwane has joined #maemo04:58
*** ezisto has joined #maemo04:59
*** ezisto has quit IRC04:59
*** Neutron9 has quit IRC05:09
*** Neutron9 has joined #maemo05:11
*** iluminator105 has joined #maemo05:28
iluminator105this smartreflex is that built into kernel after 50 or you have to install it separately05:29
*** valeriusN has left #maemo05:29
*** valeriusN has joined #maemo05:30
DocScrutinizer05smartreflex is some hw block in CPU, that automatically adjusts the PSU chip Vcore voltage according to clock speed the CPU runs at05:34
DocScrutinizer05you can enable/disable/configure that hw block05:34
DocScrutinizer05but on N900 "official" statement (for all I know) from Nokia is, smartreflex hardware is buggy and mustn't get used unless you accept instabilities or even worse effects on hw05:35
iluminator105how do you enable hw block05:35
DocScrutinizer05via a command to kernel, that sets some special control registers05:36
DocScrutinizer05iirc they are called auxiliary control registers05:36
DocScrutinizer05or did you mean how users can do that?05:37
iluminator105hmm... i meant how users can do that yea05:37
DocScrutinizer05for user there's some /sysfs/*/*/* node that you can write true/flase to05:37
DocScrutinizer05or 1/005:38
DocScrutinizer05there are other related sysfs nodes to configure the SR hw block05:38
DocScrutinizer05buzzword *volting05:38
DocScrutinizer05and efuse IIRC05:38
iluminator105also how can install cssu kernel to n900 as a new install wipe the old installation05:39
DocScrutinizer05basically there has to be a means to tell the SR hw block which voltage to program to the voltage regulators for the several possible OPP (Operation Points, aka clock speeds)05:39
*** nix900 has joined #maemo05:40
DocScrutinizer05sorry, there's no official such thing like a cssu-kernel yet05:40
iluminator105so i would have to reset to factory setting then upgrade05:41
*** radic has quit IRC05:41
*** radic_ has joined #maemo05:41
*** radic_ is now known as radic05:41
DocScrutinizer05there's powerkernel51 which works with CSSU as well as pk50 does, and there's freemangordon's thumb-enabled kernel which should basically be identical with PPK5105:42
DocScrutinizer05iluminator105: I dunno what you plan to do, but I don't see any situation where you'd actually need to "reset to factory setting then upgrade"05:42
iluminator105i just have this ppp0 devel_adoc on internet connection that i just want to get rid of, they are on my internet connections at all times05:44
*** SmilyOrg has joined #maemo05:44
DocScrutinizer05for cssu-thumb you'd need pk51/thumb-kernel05:44
DocScrutinizer05sorry, you lost me. No clue what's "ppp0 devel-adhoc" and how it might be related to cssu or update05:45
*** valeriusN has left #maemo05:47
DocScrutinizer05maybe you managed to enable wifi injection drivers?05:47
*** valeriusN has joined #maemo05:47
*** Guest70736 has quit IRC05:48
DocScrutinizer05if that's the case, then a) you are already on bleeding-edge and nothing to update to, and b) you still had to enable those drivers manually afaik, and you could just revert what you did to do that05:48
iluminator105DocScrutinizer05, i dont how to get rid expect to reinstall to factory settings05:49
DocScrutinizer05reinstall factory settings means reflash rootfs+kernel, IOW go for flashing COMBINED in05:50
infobotwell, maemo-flashing is
iluminator105you lost me on cssu-thumb 2 byte code i get it but....i though if you install powerkernel thumb is installed as part of it05:50
DocScrutinizer05and - sorry no offense - it seems you should stay away from too much bleeding-edge stuff like that "cssu-kernel", injection drivers, etc. They are not meant for end users that run into problems with disabling resp handling them05:51
DocScrutinizer05most recent powerkernel comes with a patch for thumb executables05:52
DocScrutinizer05user can enable and disable that patch05:52
DocScrutinizer05that doesn't mean you may disable patch to revert to previous state05:53
DocScrutinizer05since then all your thumb binaries in userland that you installed will start segfaulting like mad05:53
iluminator105well thing is i made some changes to n900 i dont know what changes i made, i want to revert factory state then keep a journal of changes i made as i go05:54
DocScrutinizer05then flashing is the only way for you to recover to known state05:54
infobotwell, maemo-flashing is
iluminator105i am already in cssu kernel i wanna just overclock 800mzh nothing too crazy i dont wanna do thumb or anything 800mzh with smart reflex thats all05:55
DocScrutinizer05reflash to plain vanilla maemo5 PR1.305:56
DocScrutinizer05then from that factory default go on and do your changes as you like05:56
*** Jucato has quit IRC05:57
*** kimitake_idle has quit IRC05:57
DocScrutinizer05for what you just stated you want to do, you'll probably want to install powerkernel50 or 5105:57
*** jonwil has quit IRC05:58
DocScrutinizer05which is a precondition to do overclocking05:58
DocScrutinizer05(though honestly I personally would prefer thumb over OC every day)05:59
DocScrutinizer05but thumb is still quite experimental06:00
DocScrutinizer05anyway, first step: flashing COMBINED fiasco image. good luck06:01
iluminator105thumb seems complicated more chances of an error06:01
DocScrutinizer05rather first first step: do a proper full backup, preferrably by backupmenu06:02
DocScrutinizer05(thumb) yes, it's still experimental and thus not exactly a streamlined user experience06:02
DocScrutinizer05for installation06:02
DocScrutinizer05regarding backup, you probably don't even want to restore too much of your current system state. So maybe get the backup just for best practice and in case you mess something up or need to recover some data after flashing. Other than that purpose, your approach to redo all changes manually and write a proper log about what you did is better idea than restoring too much of what you wanted to get rid of06:06
*** Gh0sty has quit IRC06:19
*** Gh0sty has joined #maemo06:20
*** Vanadis__ has joined #maemo06:41
*** Vanadis has quit IRC06:44
Maceri want my blu ecigs :-/06:50
Maceri can see it now. a total act of desperation forcing me to use usb host mode on my n900 just to charge the ecig pack06:50
*** iluminator105 has quit IRC06:53
*** npm_ has quit IRC06:59
*** npm_ has joined #maemo07:00
befordi've not had a crash using thumb07:00
*** GNUton-BNC has quit IRC07:07
*** GNUton-BNC has joined #maemo07:08
*** kimitake has joined #maemo07:13
*** ferdna has joined #maemo07:32
*** kov_ has joined #maemo07:33
*** hardaker has quit IRC07:34
*** kov_ has quit IRC07:35
*** guampa has quit IRC08:05
*** ferdna has quit IRC08:25
*** auenfx4 has quit IRC08:38
*** auenf has joined #maemo08:39
*** kimitake is now known as kimitake_idle08:41
*** nix900 has quit IRC09:13
*** hazchemix has joined #maemo09:24
*** githogori has joined #maemo09:33
*** e-yes has joined #maemo09:40
*** LaoLang_cool has quit IRC09:41
*** dhbiker has joined #maemo09:41
*** LaoLang_cool has joined #maemo09:41
*** livelace has joined #maemo10:10
*** RP_ has quit IRC10:10
*** RP_ has joined #maemo10:11
*** RP_ has quit IRC10:16
*** ChikuLinu__ has joined #maemo10:16
*** TrD has joined #maemo10:16
*** Chiku|dc has quit IRC10:20
*** Pali has joined #maemo10:23
*** zsolt_hun has joined #maemo10:24
zsolt_hunhi there.try to boot nitrdroid with uboot,but it cant recognize vmlinuz,bad format10:25
zsolt_huni'm stuck with bootloaders and now don't have an idea which one is better10:26
*** florian has joined #maemo10:28
*** utanapischti has quit IRC10:29
*** Rantwolf has joined #maemo10:29
*** utanapischti has joined #maemo10:29
*** OkropNick has joined #maemo10:31
*** zsolt_hun has quit IRC10:32
*** zsolt_hun has joined #maemo10:36
*** RP_ has joined #maemo10:37
*** RP_ has quit IRC10:46
*** RP_ has joined #maemo10:46
*** onekenthomas has quit IRC10:53
*** onekenthomas has joined #maemo10:57
*** valeriusN has left #maemo11:09
*** valeriusN has joined #maemo11:09
*** RST38h has joined #maemo11:27
*** NIN101 has joined #maemo11:36
*** sirdancealot7 has joined #maemo11:40
*** onekenthomas has quit IRC11:45
*** netkat has joined #maemo11:52
*** Pali has quit IRC12:02
*** alehorst has quit IRC12:04
*** alehorst has joined #maemo12:06
*** Pali has joined #maemo12:07
*** Pali has quit IRC12:15
*** Pali has joined #maemo12:18
*** jhb has joined #maemo12:19
*** e-yes has quit IRC12:23
*** freemangordon has quit IRC12:30
*** ced117 has joined #maemo12:30
*** ced117 has quit IRC12:30
*** ced117 has joined #maemo12:30
*** TrD has quit IRC12:34
*** TrD has joined #maemo12:34
*** Zuccace has joined #maemo12:37
*** Elleo has quit IRC12:37
*** Elleo has joined #maemo12:38
*** Elleo has joined #maemo12:38
*** florian has quit IRC12:38
*** jhb1 has joined #maemo12:40
*** Zucca has quit IRC12:41
*** beford has quit IRC12:42
*** jhb has quit IRC12:44
*** brzys has joined #maemo12:44
*** TrD` has joined #maemo12:45
*** freemangordon has joined #maemo12:45
*** sq-one has joined #maemo12:47
*** jhb1 has quit IRC12:49
*** TrD has quit IRC12:49
*** florian has joined #maemo12:52
*** florian has joined #maemo12:52
*** hazchemix has quit IRC13:01
*** brzys has quit IRC13:01
*** jhb has joined #maemo13:02
*** iDont has joined #maemo13:02
*** valeriusN has left #maemo13:03
*** brzys has joined #maemo13:03
*** valeriusN has joined #maemo13:06
*** TrD` has quit IRC13:07
*** sq-one has quit IRC13:09
*** GNUton-BNC has quit IRC13:10
*** GNUton-BNC has joined #maemo13:10
*** thomasjfox has joined #maemo13:15
*** mlwane has quit IRC13:21
*** mlwane has joined #maemo13:26
*** jhb has quit IRC13:41
*** e-yes has joined #maemo14:00
*** brzys has quit IRC14:05
*** maybeArgh has joined #maemo14:05
*** maybeWTF has quit IRC14:08
*** florian has quit IRC14:19
*** croppa has quit IRC14:37
*** HtheB has joined #maemo14:40
*** Jucato has joined #maemo14:49
*** HtheB has quit IRC14:54
*** FIQ has quit IRC15:01
*** FIQ has joined #maemo15:01
*** cyborg-one has quit IRC15:03
*** alehorst has quit IRC15:05
*** alehorst has joined #maemo15:07
*** Zuccace has quit IRC15:10
*** Zucca has joined #maemo15:10
*** jean_brat has joined #maemo15:14
*** LaoLang_cool has quit IRC15:15
*** brzys has joined #maemo15:27
*** retro|cz has quit IRC15:31
*** retro|cz has joined #maemo15:42
*** cyborg-one has joined #maemo15:49
*** FIQ has quit IRC15:49
*** FIQ has joined #maemo15:50
*** Darkchaos has joined #maemo15:53
*** sq-one has joined #maemo15:55
*** GNUton-BNC has quit IRC16:04
*** GNUton-BNC has joined #maemo16:04
*** atlas has quit IRC16:16
*** hardaker has joined #maemo16:19
keriohm, what's the best way to make a simple debian chroot jail?16:21
kerioi don't want the whole of easy debian16:21
DocScrutinizer05depends on what you need16:22
DocScrutinizer05man chroot16:23
*** thomasjfox has quit IRC16:23
DocScrutinizer05or rather info chroot16:25
*** Jade is now known as Jade`16:26
*** Jade` is now known as Jade16:26
NIN101I would say using debootstrap16:27
kerioNIN101: does it work if the host is not debian but only debian-ish?16:29
DocScrutinizer05kerio: see info chroot16:30
DocScrutinizer05it depends on what you want to run in your "jail"16:30
*** ThreeM has quit IRC16:30
DocScrutinizer05chroot is a pretty simple and easy to grok concept16:31
NIN101iirc I deboostraped debian sid from maemo16:31
*** ThreeM has joined #maemo16:35
DocScrutinizer05kerio: otoh if you bindmount /* to /mychroot/*, you get a "jail" that's basically capable of doing everything and not restricted in any regard, so basically useless. The question is what you want to protect by your jail/chroot16:38
keriowell, i want to protect the maemoness of my system16:38
DocScrutinizer05and which components/devices of "server" system your binary running in chroot "client" needs access to16:39
keriodebianness :)16:39
*** ThreeM has quit IRC16:41
*** sq-one has quit IRC16:41
DocScrutinizer05on N900 one of the major usecases for a chroot is to move rootfs / to eMMC where you got no problems with lack of free storage space16:42
keriowell no, you would just move the rootfs there :)16:42
DocScrutinizer05well, sorry. I can't help you there16:42
DocScrutinizer05too few input to start thinking about your problem16:42
kerioi *am* aware of how chroot jails work, i just wanted to know if there was a preferred way of doing it16:43
keriohmm, there *is* such a thing as "easychroot"16:45
kerio(the thing easydebian uses)16:45
*** ThreeM has joined #maemo16:45
NIN101I would just go with debootstrap, it's one command and you get a minimal debian...16:46
kerioNIN101: easychroot is just a bunch of scripts to use chroot jails apparently16:47
DocScrutinizer05what else?16:54
*** ThreeM has quit IRC16:54
DocScrutinizer05there's simply not more to chroot than that16:54
kerioDocScrutinizer05: oh god lol16:55
keriouser ALL = NOPASSWD: ALL16:55
DocScrutinizer05I know ;-P16:55
keriothat's in "/etc/sudoers.d/chroot.sudoers" in the easy-chroot package16:55
infobotjrtools is, like,
keriono, no16:55
keriowhat the fuck16:55
DocScrutinizer05well, seems chroot.sudores took a bad example16:56
NIN101windows xp.16:56
kerioi mean, this is in extras16:56
DocScrutinizer05I thought rootsh looks pretty similar16:56
keriobut at least that gives out a warning16:56
kerioi wouldn't've known about this crap16:57
DocScrutinizer05fools with no idea about sudo and security16:57
kerioalso haha, easy-chroot installs its own /sbin/chroot16:57
kerioas /sbin/qchroot16:57
kerioprobably because of messybox16:57
keriooh no, nvm16:57
kerioit's just a shell script that chroots with bells and whistles and insecurity16:58
*** Pali has quit IRC16:58
keriomount -o bind /dev "$CHROOT/dev"16:58
keriooh HELL NAW16:58
DocScrutinizer05well, that's where chroot details start16:58
kerioyeah but you don't... do that16:58
DocScrutinizer05do you want to grant your jailed binary access to real devices or not16:59
keriomaybe not *all* of them16:59
kerioi mean, i suppose it's actually fine16:59
kerioonce you have root you can mknod anyway16:59
freemangordonguys, a stupid question, when typing with virtual keyboard and word prediction turned on, how to use what is predicted?17:01
DocScrutinizer05((<kerio> maybe not *all* of them)) that's why I asked what you want to do in your chroot17:08
kerioDocScrutinizer05: i don't actually know, i feel content with fremantle as it is17:08
DocScrutinizer05well, I think you know pretty good how to set up a chroot for your needs17:08
keriowell, i actually kinda do17:09
*** ludens has quit IRC17:09
DocScrutinizer05the only problem is you should get to know your needs then17:09
kerioi suppose so17:10
MohammadAGfreemangordon, tap as if moving cursor17:10
Sicelokewl. /me never knew either17:11
MohammadAGfreemangordon, testing <--tap here17:11
*** mase76 has joined #maemo17:15
freemangordonMohammadAG: thanks17:19
*** ThreeM has joined #maemo17:23
DocScrutinizer05a common step for mankind, but a giant leap for you, man! (in memoriam Niel Armstrong)17:24
*** ludens has joined #maemo17:24
*** ludens has quit IRC17:30
*** ludens has joined #maemo17:35
*** ThreeM has quit IRC17:39
*** ludens has quit IRC17:42
*** DocScrutinizer05 has quit IRC17:42
*** DocScrutinizer05 has joined #maemo17:42
*** sLumPia has joined #maemo17:56
*** ludens has joined #maemo17:56
*** alehorst has quit IRC18:06
*** alehorst has joined #maemo18:08
*** DHR has joined #maemo18:16
*** MrPingu has joined #maemo18:17
*** valeriusM has quit IRC18:21
MrPinguAnyone experienced constant  shutdowns  after 10 mins of uptime or less on N900?18:36
*** nix900 has joined #maemo18:37
MrPinguSuddenly, really suddenly... when I am in maemo or bootmenu it just shutdowns the whole time... Luckily backupmenu works on mass storage...18:38
kerioMrPingu: overclocked?18:39
keriofull reflash and try again18:39
kerioif it still does that, then it's borked18:39
MrPingubut I have 36000 wakeups :D18:39
jogain powertop?18:39
keriootherwise, you messed up something that the watchdog expects18:39
MrPinguWell, let's tell the story from the start18:40
MrPinguYesterday night went to bed, woke up this morning -> Everything fine18:40
*** atlas has joined #maemo18:41
MrPingufrom 8 am to 12 it worked nicely18:41
MrPinguthen I wanted to check time around 14:0018:41
*** valeriusM has joined #maemo18:41
MrPinguphone not responding, battery dead18:41
MrPinguSwapped battery with full one, 10 mins later phone off again18:42
MrPinguchecked battery in other phone was full for about 70%18:42
MrPinguGuess I need a reflash but it's just odd18:43
MrPingurestoring backup from backupmenu (1week old)didn't help either18:43
*** sambo7 has joined #maemo18:45
MrPinguWhat can go wrong so suddenly? I mean I didn't even touch my phone...18:45
MrPinguSicelo: Any fix or do I need to reflash?18:47
*** NIN101 has quit IRC18:48
Siceloi don't know. i was just mentioning that modem can sometimes be a culprit here. i wouldn't immediately suggest a reflash. see if you can't get people like DocScrutinizer05, freemangordon, etc18:49
*** NIN101 has joined #maemo18:49
*** valeriusM has quit IRC18:50
DocScrutinizer05MrPingu: you got KP51?18:51
MrPingu= KP51 from what I heard18:51
*** Ionakka has joined #maemo18:51
kerioMrPingu: do you have something in dmesg?18:52
DocScrutinizer05well, I totally lost track of this cssu-kernel stuff, actually there's no official cssu-kernel for plain CSSU-T/S18:52
MrPinguI am on thumb ;)18:52
MrPinguAnyway from what FMG told, cssu3 = KP5118:52
DocScrutinizer05I guess your problems are with KP, bme, bq24150.ko and related stuff18:52
DocScrutinizer05we've seen several such reports lately18:53
keriothat's FUD-ish18:53
DocScrutinizer05kerio: that's summary of events / reports of last few weeks18:53
MrPinguDocScrutinizer05, I didn't play with bme bq245150.ko. Can it go insane without interaction?18:54
DocScrutinizer05that's the huge mystery18:54
kerioin theory, no18:54
MrPingudamnit, now this brick doesn't even turn on18:54
keriothe module is blacklisted18:54
MrPinguoh nvm, act-dead state -.-18:55
kerioyep, definetely bq24k.ko problem18:55
DocScrutinizer05MrPingu: yeah, exactly in line with what we heard from other similar reports. Remove battery, reinsert after >60s, should reboot then18:55
kerioDocScrutinizer05: after 60s? what's that time?18:56
keriobupbat fail?18:56
DocScrutinizer05probably discharge time for Vbat buffer capacitors18:56
keriocapacitors losing power?18:56
kerioi see18:56
Siceloah, same issue as Estel had18:56
DocScrutinizer05I strongly suggest to roll back to KP5018:57
MrPinguStill 14000 wakeups, not a sane value18:58
DocScrutinizer05causede by whom?18:58
MrPinguHow to see that?19:00
*** mase_76 has joined #maemo19:00
DocScrutinizer05I'd bet it's I2C, bme, and/or kernel bq2415019:00
DocScrutinizer05MrPingu: powertop19:00
DocScrutinizer05MrPingu: how do you see the 14k wakeups?19:00
MrPinguI understand but how to see from what they come?19:01
DocScrutinizer05once there's IRQs listed with count, and then there's list of processes with count19:01
MrPinguDMA  - 712619:01
MrPinguI2c_omap  - 333919:02
MrPingugp - 238619:02
keriowhat's gp?19:02
MrPinguyou tell me :P19:02
DocScrutinizer05graphics processor? not sure19:02
DocScrutinizer05or general purpose19:03
*** NIN101 has quit IRC19:03
DocScrutinizer05I2C is kinda high19:03
MrPinguAnyway you are right i2c_omap is gone ape19:04
DocScrutinizer05dma for sure too19:04
MrPinguIt's even listed twice in IRQ table ;p19:04
DocScrutinizer05is that 56 or 5719:04
DocScrutinizer05there are two I2C busses19:04
*** NIN101 has joined #maemo19:04
MrPinguThe highest is 5619:04
MrPinguthe one lower in the table is 5719:05
DocScrutinizer05     56 |       2650 |           INTC | i2c_omap19:05
DocScrutinizer05     12 |        601 |           INTC | DMA19:05
DocScrutinizer05     37 |        493 |           INTC | gp19:05
DocScrutinizer05     57 |        328 |           INTC | i2c_omap19:05
DocScrutinizer05PID#    | Activity   | Name           | Function Entry (Expire)19:06
DocScrutinizer05      0 |        270 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)19:06
DocScrutinizer05     37 |         68D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)19:07
DocScrutinizer05      0 |         65 |  <kernel core> | hrtimer_start (tick_sched_timer)19:07
DocScrutinizer05    548 |         36 |         wl12xx | schedule_timeout (process_timeout)19:07
DocScrutinizer05this is with device idle, on fastcharger19:07
MrPinguMine is on pc, on idle too19:08
DocScrutinizer05so what are your top 3 PIDæactivity|name?19:08
MrPinguC#      | Ratio  | Avg/dura | Frequency | Ratio19:09
MrPingu     C0 |   2.4% |          |  1150 MHz |   nan% |19:09
MrPingu     C1 |  97.5% |   14.2ms |19:09
MrPinguThat's just not normal :O19:09
DocScrutinizer05nah, not that19:09
MrPingu 2276 root      20   0  2296 1140  896 R  2.0  0.5   0:00.49 top19:10
MrPingu   10 root      20   0     0    0    0 S  0.7  0.0   0:03.52 omap2_mcspi19:10
MrPingu 1707 user      20   0 56196  10m 6728 S  0.3  4.5   0:07.02 hildon-home19:10
DocScrutinizer05but yes, it's normal19:10
MrPinguI know19:10
MrPinguC1 normal?19:10
*** hazchemix has joined #maemo19:10
DocScrutinizer05if on charger19:10
MrPinguoh duh, it's on charger...19:10
MrPinguforget a little detail xD19:11
DocScrutinizer05MrPingu: please deliver top 3 from powertop, not frpm ps19:11
MrPinguPID#    | Activity   | Name           | Function Entry (Expire)19:11
*** valeriusM has joined #maemo19:11
MrPingu     38 |         36D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)19:11
MrPingu   1272 |         27 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)19:11
MrPingu      0 |         23 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)19:11
DocScrutinizer05duh, pretty little activity there19:12
DocScrutinizer05I'm missing 0 |        270 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)19:12
DocScrutinizer05somebody thought it was a good idea to mess with nohz in PK51?19:13
DocScrutinizer05err nevermind, it's third in your list19:14
*** brzys has quit IRC19:14
MrPinguSeems device cooled down a bit...19:15
DocScrutinizer05anyway for reboots, you should check dsme protocol19:15
MrPingudsme wdd: Error reading R&D mode flags, WD kicking enabled19:15
MrPingudsme wdd: Error opening WD /dev/twl4030_wdt: Device or resource busy19:16
MrPingudsme wdd: Error opening WD /dev/watchdog: Device or resource busy19:16
MrPingudsme wdd: no WD's opened; WD kicking disabled19:16
MrPingudsme wdd: Entering main loop, with 12 s interval19:16
MrPinguis that normal?19:16
Sicelohow did you get that?19:16
DocScrutinizer05not really I think19:16
MrPingurunning dsme19:16
DocScrutinizer05err, *running* dsme?19:16
DocScrutinizer05please check /var/lib/dsme/stats/lifeguard_restarts19:17
*** hardaker has quit IRC19:17
MrPinguNokia-N900:/var/lib/dsme/stats# cat lifeguard_restarts19:18
MrPingu/usr/bin/ohm-session-agent: 119:18
MrPingu/usr/sbin/alarmd.wrapper : 119:18
MrPingu/sbin/mce --force-syslog: 119:18
MrPingu/usr/bin/camera-ui: 219:18
MrPingu/usr/bin/mafw-dbus-wrapper mafw-gst-renderer: 119:18
MrPingu/usr/bin/hildon-home: 1219:18
MrPingu/usr/bin/hildon-desktop: 319:18
MrPingu/usr/bin/osso-abook-home-applet: 1319:18
MrPingu/usr/bin/hildon-status-menu: 1819:18
MrPingu/usr/bin/systemui: 1919:18
MrPingu/usr/sbin/browserd -d: 1819:18
MrPingu/usr/bin/hildon-input-method: 119:18
DocScrutinizer05not really relevant, just check what counted up after next faulty reboot19:18
Sicelorunniing dsme should give you those errors on an OK device. the watchdog is indeed busy (with first dsme instance)19:19
DocScrutinizer05dsme isn't meant to get started twice19:19
DocScrutinizer05anyway I don't see any bme related reboots in your lifeguard_restarts19:20
MrPinguNow, if i remove the charger would it shutdown itself again?19:20
DocScrutinizer05if it's on and active, it mustn't shut down on removing charger19:20
MrPinguWell it happend me thrice today, put phone away -> then come back phone off19:21
MrPinguThat's how I ended up with this chat :P19:21
Siceloif it's kernel, mos likely you should have a log in mtd2 iirc19:22
DocScrutinizer05MrPingu: please check syslog19:22
DocScrutinizer05and mtd2 as Sicelo suggests19:22
MrPinguLooked in mtd2 but didn't see anything special, at first glance19:24
DocScrutinizer05MrPingu: search in syslog for last "syslogd 1.5.0#5maemo7+0m5: restart."19:24
MrPingusyslog, sorry where could I find that?19:25
DocScrutinizer05see what's the last few lines *before* that19:25
DocScrutinizer05if you have ksyslogd installed19:25
DocScrutinizer05too bad19:25
DocScrutinizer05go install it19:25
MrPinguon my way sir19:25
*** atlas has quit IRC19:25
MrPingutools or sdk repo?19:25
DocScrutinizer05err, always tools if in question19:26
MrPinguAh, une moment19:26
DocScrutinizer05sysklogd - System Logging Daemon19:26
DocScrutinizer05500 ./ Packages19:27
DocScrutinizer05  Installed: 1.5-5maemo7+0m519:27
DocScrutinizer05apt-get install sysklogd19:28
DocScrutinizer05probably even in extras-devel19:28
DocScrutinizer05or extras19:29
MrPinguI don't think so19:29
MrPingucouldn't find it :P19:29
DocScrutinizer05or nokia core repo19:29
DocScrutinizer05Fremantle nokia-applications explicit armel19:31
MrPinguNever heard of that repo19:31
DocScrutinizer05Fremantle SDK free armel19:31
MrPinguYeah, saw it19:31
MrPingunot in tools but sdk19:31
DocScrutinizer05Fremantle SDK tools free armel19:31
DocScrutinizer05Maemo 5 device SSU repository (>= PR1.2)19:32
keriohm, i don't have nokia-applications19:32
*** valeriusN has quit IRC19:32
MrPinguMe neither...19:32
MrPinguBTW, I see some kernel-panics in mtd219:32
DocScrutinizer05just quoting
DocScrutinizer05do they have timestamps?19:33
DocScrutinizer05so you could actually tell when they happened19:33
MrPinguNo timestamps I believe19:34
MrPingubut they do have some numbers in front...19:34
DocScrutinizer05yeah, alas there's no decent tool to read out mtdoops19:34
DocScrutinizer05at least I'm not aware of any19:35
DocScrutinizer05ability to read is a clear advantage ;-P19:36
MrPinguShould I install that aswel?19:36
DocScrutinizer05nfc, just this minute discovered it19:37
MrPinguInstalling syslogd now19:37
DocScrutinizer05;-DIroN900:~# sp-oops-extract /dev/mtd219:38
DocScrutinizer05looks somewhat decent19:38
MrPinguseems device is gone sane again19:39
MrPinguI mean, more than 10 min uptime now without charger :)19:39
DocScrutinizer05*might* be trackerd hogging IO and thus causing system critical process to freeze which in turn triggers DSME lifeguard WD19:41
*** netkat has quit IRC19:41
MrPingumight be, but I have lowmemorymode thicked + throttle to 1019:41
DocScrutinizer05but no idea how that naive explanation might fit into act_dead problem19:41
MrPinguWakeups are still somewhat high19:42
DocScrutinizer05yeah, kinda high19:43
DocScrutinizer05where from do you read those?19:43
MrPinguif you are speaking of the devil...19:44
MrPinguscreen went black19:44
MrPingudevice off...19:44
DocScrutinizer05now is the time of syslog19:44
MrPinguInstalled at the right moment19:45
DocScrutinizer05and comparing mtd2 to what it been before19:45
MrPinguit skips the dots...19:45
DocScrutinizer05and checking dsme lifeguard reset stats19:45
MrPingubut asked for pin19:45
MrPinguhildon-home coming up :)19:46
MrPinguCan't get to app launcher :o19:46
DocScrutinizer05sorry, afk19:48
Estel_MrPingu, whats the problem?19:48
Estel_I saw in backscroll, that it's something related to what I had?19:48
Estel_merlin1991, ping19:49
MrPinguJust acting weird regarding battery, odd shutdowns19:49
Estel_any problems in turning it on again?19:49
Estel_(other than empty battery, if it's the case)19:49
Estel_symptoms? how it acts, when You can't turn it on?19:49
MrPinguact-dead mode19:49
Estel_as for kp51, I don't have any problems with battery life, it was just about turning on in act_dead instead of noprmal, which may be some mystery about my device hardware-wise, after all19:50
MrPinguor just reboots after the dots19:50
DocScrutinizer05MrPingu: please don't mess with flasher options to "fix" it19:50
MrPinguand random shutdowns while in maemo19:50
Estel_MrPingu, flasher options that DocScrutinizer05 have in mind are --set-rd-flag force-power-key - it make device to boot up as bootreason pwr_key always, so no act-dead19:51
MrPinguDocScrutinizer05: Yes, sir!19:51
Estel_in my case, it works well, but of cours,e doesn't help finding cause of problem19:51
Estel_thats probably, why DocScrutinizer05 ask You for not doing it19:51
MrPinguI had an extremely high number of wakeups19:51
Estel_but, You can always reset rd flags to normal, so if You need Your device reliable, you may turn this flag on, then, to help find problems, turn it off again19:52
Estel_yea, saw it19:52
Estel_well, in my case, no additional wakeups19:52
Estel_it's jsut that it booted in act_dead mode, and it was worse over time, i.e. harder and harder to turn it normal way19:52
MrPinguDocScrutinizer05: Need to see my syslog?19:52
Estel_although, multimeter doesn't show anything special on usb lines19:52
Estel_and no other oddities during runtime. i've also, recently, did some crazy repair of Ir diode19:53
Estel_that lead to short between battery + and ground, fixed later19:53
MrPinguAug 26 18:53:03 Nokia-N900 kernel: [  431.601623] HWRecoveryResetSGX: SGX Hardware Recovery triggere19:53
MrPingusyslog is full of that19:53
Estel_shouldn't matter, but You can't filter out that something is still wrong19:53
Estel_MrPingu, forward it to Pali, for sure19:53
Estel_nothing like that in my syslog, at least for sure not spamming it19:53
Estel_also, never heard about it from any kp51 user19:53
Estel_DocScrutinizer05, BTw, if You are here, please, read my signature carefully, if you're reffering to it ;)19:54
DocScrutinizer05[2012-08-26 18:24:42] <DocScrutinizer05> MrPingu: search in syslog for last "syslogd 1.5.0#5maemo7+0m5: restart."  [2012-08-26 18:25:02] <DocScrutinizer05> see what's the last few lines *before* that19:54
Estel_at least be able to distinguish between "I am" and "I was", as it's present in my signature for more than a month (since I have stepped down from Council)19:54
Estel_thanks in advance ;)19:54
*** beford has joined #maemo19:55
Estel_merlin1991, ping ping ping19:56
Estel_freemangordon, ping19:56
*** Pali has joined #maemo19:57
Estel_hey, Pali, MrPingu seems to have strange problems, that may be related to kp5119:57
Estel_might be*19:57
Palidescribe it19:57
Estel_<MrPingu> Aug 26 18:53:03 Nokia-N900 kernel: [  431.601623] HWRecoveryResetSGX: SGX Hardware Recovery triggere19:57
Estel_syslog full of that19:57
Estel_battery dying very fast19:57
Estel_many wakeups19:58
Estel_+, just like with me, his device sometimes boot only in act_dead, despite being turned out by power button19:58
MrPinguNow several graphic parts fail too19:58
Estel_but it's only one situation, where our symptoms are similalr - I don't have any problems *except* for act_dead19:58
Estel_started with kp5119:58
MrPinguI mean statusmenu can't be loaded except for some distorted colors19:58
Estel_I "fixed" it, temporary, by enabling rd flag force-power-button, so act_dead gtfo, but it's not "real" fix of course19:59
Paliflash 2.6.28 omap1 and see if it happends too19:59
*** livelace has quit IRC19:59
Paliif not then it is not kernel related19:59
MrPinguCan't, I am on thumb19:59
Estel_Pali, is there any change in kernel, that allows bq2415 to work properly?19:59
Estel_and is in effect even, if bq2415 isn't loaded?19:59
*** sambo7 has quit IRC19:59
PaliI did not look at bq2415x after v51 was released19:59
Palino time now...20:00
Estel_I know, i've reported tons of bugs against it in kp51 thread20:00
Estel_but I'm only asking if during coding kp51, have You added something20:00
Estel_in kernel20:00
Estel_for bq2415, to allow it work properly, that is in effect even without this module loaded?20:00
Estel_I'm trying to check if my act_dead problems are in any way indeed related to kp5120:01
Paliuse my RE getbootstate20:01
Paliand see if my getbootstate tell act_dead too20:02
Paliand if yes, look at code why20:02
Estel_where to expect logged output?20:02
Palisorry, now going offline, bye20:02
Estel_see ya20:02
*** mase_76 has quit IRC20:03
DocScrutinizer05errr, using getbootstate during act_dead to see if it shows act_dead? ;-)20:03
Estel_probably, he want me to check if his getboostate gets affected too20:03
DocScrutinizer05well, that's just a tad tricky to accomplish20:03
MrPingusylog shows two restarts20:03
Estel_and if yes, it gives more debug info (I hope)20:03
MrPinguone failed20:04
DocScrutinizer05[2012-08-26 18:24:42] <DocScrutinizer05> MrPingu: search in syslog for last "syslogd 1.5.0#5maemo7+0m5: restart."  [2012-08-26 18:25:02] <DocScrutinizer05> see what's the last few lines *before* that20:04
MrPinguand one normal with those fsckd graphics20:04
MrPinguAug 26 18:44:17 Nokia-N900 ke_recv[1939]: prop_modified:1928: udi /org/freedesktop/Hal/devices/platform_slide modified button.state.value20:04
MrPinguAug 26 18:44:27 Nokia-N900 cellular: csd[1334]: ISI_SMS .966735> ind_reg_status(): Net registration (ind) status:1 rc:020:04
MrPinguAug 26 18:44:27 Nokia-N900 cellular: csd[1334]: ISI_SMS .970031> set_timeout(): Timeout 2253 s event type:-120:04
*** sambo7 has joined #maemo20:05
DocScrutinizer05then it has to be a kerrnel panic/oops20:05
Estel_but why? never heard about someone else affected in such way20:05
MrPinguAug 26 19:00:55 Nokia-N900 kernel: [  903.265808] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:05
MrPinguAug 26 19:00:55 Nokia-N900 kernel: [  903.890838] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:05
MrPinguAug 26 19:01:01 Nokia-N900 kernel: [  909.453277] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:05
Estel_maybe sent it to Pali via PM on TMO?20:05
Estel_IRC is too loosy for such things, he won't read it, probably, if left here20:06
MrPinguAug 26 18:59:47 Nokia-N900 kernel: [  835.968933] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:06
MrPinguAug 26 19:00:01 Nokia-N900 kernel: [  849.937652] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:06
MrPinguAug 26 19:00:12 Nokia-N900 kernel: [  860.328216] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:06
MrPinguAug 26 19:00:12 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 0->1, is_layout_active:0, ChangeSusp:TRUE20:06
MrPinguAug 26 19:00:12 Nokia-N900 kernel: [  861.195434] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:06
MrPinguAug 26 19:00:13 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 1->0, is_layout_active:1, ChangeSusp:TRUE20:06
DocScrutinizer05maybe this doesn't increase the amount of info it contains20:06
MrPinguAug 26 19:00:14 Nokia-N900 kernel: [  862.460937] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:06
MrPinguAug 26 19:00:15 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 0->1, is_layout_active:0, ChangeSusp:TRUE20:06
MrPinguAug 26 19:00:15 Nokia-N900 kernel: [  864.132873] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:06
MrPinguAug 26 19:00:16 Nokia-N900 kernel: [  864.757965] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:06
MrPinguAug 26 19:00:18 Nokia-N900 kernel: [  866.406433] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:06
MrPinguAug 26 19:00:18 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 1->0, is_layout_active:1, ChangeSusp:TRUE20:06
MrPinguAug 26 19:00:18 Nokia-N900 kernel: [  866.804809] slide (GPIO 71) is now open20:06
MrPinguAug 26 19:00:18 Nokia-N900 ke_recv[1754]: prop_modified:1928: udi /org/freedesktop/Hal/devices/platform_slide modified button.state.value20:06
DocScrutinizer05MrPingu: please stop it!20:06
MrPinguAug 26 19:00:19 Nokia-N900 kernel: [  867.289276] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:06
MrPinguAug 26 19:00:19 Nokia-N900 kernel: [  867.914093] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:06
MrPinguAug 26 19:00:19 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 0->1, is_layout_active:0, ChangeSusp:TRUE20:06
MrPinguAug 26 19:00:20 Nokia-N900 kernel: [  868.539215] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:06
Estel_he can'ty it gor triggerred20:06
MrPinguAug 26 19:00:20 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 1->0, is_layout_active:1, ChangeSusp:TRUE20:06
MrPinguAug 26 19:00:21 Nokia-N900 kernel: [  869.296936] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:06
MrPinguAug 26 19:00:22 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 0->1, is_layout_active:0, ChangeSusp:TRUE20:06
MrPinguAug 26 19:00:22 Nokia-N900 kernel: [  870.961090] HWRecoveryResetSGX: SGX Hardware Recovery triggered20:06
Estel_he pasted huge output20:06
*** ChanServ sets mode: +o DocScrutinizer0520:06
MrPingumy whole log is spammed20:06
Estel_it got pasted line by line by his irc client20:06
MrPingugot 2 eat20:06
Estel_MrPingu, ever heard about zerobin?:P20:07
*** ChanServ sets mode: -o DocScrutinizer0520:07
Estel_or pastebin?:P20:07
DocScrutinizer05MrPingu: you should make sure you got no undervolting, overclocking, and no smartreflex activated20:07
*** Pali has quit IRC20:07
DocScrutinizer05if those HWRecoveryResetSGX aren't triggered by any of those, odds are your device silicon is EOL20:08
DocScrutinizer05(aka OC burnout, which of course can happen even without you ever doing OC, just way later)20:08
DocScrutinizer05but hey, maybe it's thumb related20:09
DocScrutinizer05also possible20:09
* DocScrutinizer05 away for dinner too20:10
Estel_:P hey, maybe it's related to anything :P Well, in last attempt, you might also want to backup everything, and do reflash, just to see if it's happen on stock too20:12
Estel_but don't worry, i'20:12
Estel_I'm quite confident, that you/we will find cause of it. Of course, "silicon EOL" is always possible - thus, always used as possible cause, when no one have freakin idea what is going on ;) But I have never seen situation, wshen it turned out to be the case for N900, so don't be much worried about that20:13
Estel_i.e. chances for such irreversible damage are loooow20:13
Estel_I'm out for some sunday afternun fun, feel free to ping me, will answer later20:14
Estel_BTw, merlin1991, my pings are still valid ;)20:14
*** sLumPia has quit IRC20:15
DocScrutinizer05btw merlin clearly stated he's not available until 1.9.20:18
* DocScrutinizer05 wonders why estel *always* has to argue like a turdhead, ignoring first 2 thirds of statement "if those HWRecoveryResetSGX aren't triggered by any of those, odds are your device silicon is EOL" as well as line before20:21
keriofor what it's worth, sometimes i get a silly graphical corruption, if i start doing things too quickly when the n900 is just booting20:21
kerioand that also prevents me from accessing the application launcher20:21
keriorebooting fixes it20:21
DocScrutinizer05and just going offensive with ""silicon EOL" is always possible - thus, always used as possible cause, when no one have freakin idea what is going on "20:21
kerioit happened on two N900s20:21
*** fuz_ has quit IRC20:23
DocScrutinizer05pisses me off when I tell 4 clearly defined and well pondered possible causes for gfx resets, and this dude first states "yeah, or *anything* else", just to continue "obviously you got no clue what's going on, but *ME* can assure all of you that it's not Si-EOL"20:24
DocScrutinizer05kerio: yep, gfx resets are not all that uncommon, but they shouldn't happen too frequently20:25
kerioDocScrutinizer05: what causes them?20:26
*** pigeon_ has quit IRC20:26
DocScrutinizer05nobody knows, or otherwise we already would've fixed them20:26
keriojust powervr silliness?20:26
DocScrutinizer05probably some Si-Erratum20:26
DocScrutinizer05some weird race condition occasionally hitting, on a hw level20:27
DocScrutinizer05alas TI is far from disclosing all of those Si-Err, esp when there's no proper workaround/fix20:27
*** pigeon has joined #maemo20:28
keriofukken TI20:28
DocScrutinizer05kerio: however there's already some botch "fix" in form of the automatic reset of gfx core via kernel "watchdog" aiui. Too bad when that doesn't suffice to revert to normal operation20:30
kerio"sure, the engine sometimes locks up, but there's a fix, you just start it again"20:30
DocScrutinizer05as long as that happens reliably and transparently in background, it's almost bearable20:31
*** sambo7 has quit IRC20:32
DocScrutinizer05I however don't see how gfx reboots could tear down or panic the whole linux core20:32
keriofukken kernel-power? :P20:33
DocScrutinizer05nah, KP isn't that bad20:33
DocScrutinizer05just a lot of the patches included never have seen proper review and thorough tests20:33
*** fuz_ has joined #maemo20:35
*** valeriusM has quit IRC20:35
DocScrutinizer05still I can't come up with a story how gfx reboots would cause inadverted kernel panic. But hey, that's the nature of bugs: you didn't think of this possible side effect until it bites your ass (otherwise you wouldn't have introduced the bug, no? ;-P)20:35
*** hurbu has joined #maemo20:35
DocScrutinizer05maybe the kernel watchdog process for gfx isn't reentrant, so kernel OOPS when gfx 'segfaults' during wtachdog resetting it?20:36
DocScrutinizer05MrPingu: [2012-08-26 19:07:36] <DocScrutinizer05> MrPingu: you should make sure you got no undervolting, overclocking, and no smartreflex activated [2012-08-26 19:08:26] <DocScrutinizer05> if those HWRecoveryResetSGX aren't triggered by any of those, odds are your device silicon is EOL [2012-08-26 19:08:55] <DocScrutinizer05> (aka OC burnout, which of course can happen even without you ever doing OC, just way later) [2012-08-26 19:09:24]20:38
DocScrutinizer05 <DocScrutinizer05> but hey, maybe it's thumb related20:38
kerioDocScrutinizer05: ooh, could be smartreflex20:38
kerioiirc it's enabled by default since kernel-power... 50? 51?20:38
freemangordonDocScrutinizer05:  HWRecoveryResetSGX was there since the begining of 20120:38
DocScrutinizer05sure thing. Nokia always told us SR is instable20:38
keriowell, by default-ish20:39
freemangordonkerio: bullshit, SR is not enabled by default20:39
kerioit's in the "default" profile20:39
DocScrutinizer05freemangordon: yep, I know, and already mentioned that20:39
kerioyou have to set it to be the default20:39
freemangordonkerio: SR has nothing to do woth SGX, it is on completely different power bus20:39
DocScrutinizer05freemangordon: [2012-08-26 19:25:38] <DocScrutinizer05> kerio: yep, gfx resets are not all that uncommon, but they shouldn't happen too frequently20:39
freemangordonkerio: in short, stop spreading FUD20:40
freemangordonDocScrutinizer05: yep20:40
MrPinguReboot fixes those SGX errors20:40
Lava_Crofti see a question mark on kerio's line20:40
Lava_Croftand an iirc20:40
DocScrutinizer05freemangordon: you're sure about that powerbus thing? *really* sure?20:40
Lava_Croftmaking it more of question than a statement20:40
Lava_Croftrelax man20:40
* kerio spreads more fud over a piece of bread and then eats it20:40
freemangordonand the only way to get rid of them is power off/on, a simple reboot won't help20:40
freemangordonDocScrutinizer05: not 100%, but near that value :)20:41
MrPinguI actually meant powercycle20:41
DocScrutinizer05freemangordon: depending on hw circuitry incl PCB layout around twl4030 power regulator circuitry this assumption might be incorrect for N90020:42
freemangordonDocScrutinizer05: BTW I think it is an issue in the driver , not silicon errata20:42
DocScrutinizer05and maybe that's exactly why Nokia said SR is flawed by hw20:42
freemangordonDocScrutinizer05: well, I don;t think there is a way SGX and core to operate on one and the same voltage20:42
MrPinguWakeups however are still insane high20:43
freemangordonas SGX frequency is constant ;)20:43
MrPingu9463 - DMA20:43
DocScrutinizer05no, but for example it's pretty easy to figure regulators for both are fed by same power rail so interference is quite possible20:43
*** florian has joined #maemo20:43
*** florian has joined #maemo20:43
freemangordoncould be, but SR does not change that20:44
MrPingu2600 - mmc120:44
DocScrutinizer05sure it does, it changes settings for one regulator and thus might cause interference to the other20:44
freemangordonDocScrutinizer05: the same does OPP control even without SR20:45
DocScrutinizer05maybe SR does more 'agressive' changes to regulator settings than non-SR OPP settings do20:45
freemangordonwell, this is too "maybe" so my bets are on a simple bug in the driver :)20:46
DocScrutinizer05quite tricky to rule out anything along that line20:46
DocScrutinizer05possible, even probable20:46
freemangordonhaving in mind we have the same behaviour it stock kernel too20:46
MrPinguWhat is exactly DMA and why is it taking so much wakeups?20:46
freemangordondirect memory access20:46
DocScrutinizer05good question, since mine isn't that spammy20:47
DocScrutinizer05might be your PC to USB20:47
DocScrutinizer05IOW usb data transfer20:47
MrPinguI am not attached to pc20:47
DocScrutinizer05ooh, nfc then20:47
DocScrutinizer05trackerd accessing eMMC? no idea20:48
MrPingume neither, im not as guru as you guys are :P20:48
*** valeriusM has joined #maemo20:48
DocScrutinizer05basically DMA isn't an autonomous process, it needs some (linux) process to control it20:49
DocScrutinizer05this linux process should show up un ps and/or (power)top20:49
DocScrutinizer05freemangordon: (same behaviour) not a few dozen or even hundereds of gfx resets during >10 min20:50
DocScrutinizer05at least I've never seen that20:50
MrPinguDo the gurus need some data from my device or else I am going to reflash20:51
MrPinguI need to have my device in a working state before tomorrow :P20:51
DocScrutinizer05umm, wait another 5 min please. Even _my_ brain needs time to complete evaluations ;-)20:51
MrPinguSure, you got 2 hours ;)20:52
MrPinguflashing doesn't take that long...20:52
DocScrutinizer05at least save syslog and sp-oops-extract20:52
DocScrutinizer05and a complete output of powertop20:53
freemangordonMrPingu: one question, how did this start?20:53
freemangordonout of the blue?20:53
MrPinguyes out of the blue20:53
freemangordondid you try to remove the battery?20:53
MrPinguI even swapped batteries20:53
DocScrutinizer05[2012-08-26 17:40:20] <MrPingu> Well, let's tell the story from the start20:54
DocScrutinizer05[2012-08-26 17:40:40] <MrPingu> Yesterday night went to bed, woke up this morning -> Everything fine20:54
DocScrutinizer05[2012-08-26 17:41:04] <MrPingu> from 8 am to 12 it worked nicely20:54
DocScrutinizer05[2012-08-26 17:41:18] <MrPingu> then I wanted to check time around 14:0020:54
DocScrutinizer05[2012-08-26 17:41:32] <MrPingu> phone not responding, battery dead20:54
keriooh god paste20:54
MrPinguYeah suddenly it had an flat battery20:54
MrPinguswapped it for a full one20:54
MrPingubut then I kept shutdowns within 10 mins20:55
DocScrutinizer05sorry guys, I really need to care about my dinner now20:55
freemangordonhmm, so you don't have any idea if rootfs is nog corrupted20:55
DocScrutinizer05df -h20:55
*** DHR has quit IRC20:55
freemangordonleading to some broken graphics file which h-d or h-h tries to load in SGX20:56
freemangordonMrPingu: did you try to change the theme?20:56
DocScrutinizer05quite a good story indeed20:56
MrPinguNot yet20:56
zeq1hey freemangordon :)20:56
*** mase76 has quit IRC20:56
DocScrutinizer05hey zeq120:56
freemangordonyou can also try to delete application snapshots20:56
zeq1Hi DocScrutinizer0520:56
freemangordonhi zeq120:56
DocScrutinizer05quite a good story indeedmrplease do a proper BM backup20:57
DocScrutinizer05errrrr :-(20:57
freemangordonMrPingu: /home/user/.cache/launch20:57
DocScrutinizer05MrPingu: please do a proper BM backup20:57
DocScrutinizer05and safe it off the phone20:58
MrPinguI have a properbackup of 17 aug and one of 25 aug on my pc20:58
freemangordongoing afk for a while20:58
MrPinguso yesterday20:58
DocScrutinizer05do one of the current state, with backupmenu20:58
MrPinguYes, will say when it's done ;)20:59
MrPinguIf some other steps are needed20:59
DocScrutinizer05add syslog and sp-oops-extract and powertop20:59
*** sambo7 has joined #maemo21:00
DocScrutinizer05this should allow forensic analysis later21:00
DocScrutinizer05then I suggest you reflash and test with standard config21:01
MrPinguNow I start wondering if my backup of yesterday might be affected21:01
*** jean_brat has quit IRC21:01
*** aloril has quit IRC21:01
MrPinguI remember my phone was extremely hot while backup'ing21:02
DocScrutinizer05probably unrelated21:04
MrPinguDocScrutinizer05: Standard config, you mean omap kernel, and no CSSU?21:04
DocScrutinizer05yep, please21:04
freemangordonwell, most probably some resource file (icon, .pvr, pcx, ) got corrupted21:05
DocScrutinizer05then reinstall step by step, and see if you can spot what causes the effect21:05
freemangordonDocScrutinizer05: let him try to clean .pvr cache and change the theme, it is a matter of seconds to be done21:05
DocScrutinizer05freemangordon: might we detect that somehow?21:05
DocScrutinizer05e.g by comparing *.pvr of old and fresh install21:06
MrPinguRight now backup'ing so can't do anything else...21:06
freemangordonDocScrutinizer05: .pvr is done on-the-fly by h-d21:06
DocScrutinizer05freemangordon: up to you :-)21:06
*** alehorst has quit IRC21:06
freemangordonthis is a part of smoke-and-mirror :)21:07
freemangordonand actually is a maemo specific hack in clutter21:07
freemangordonplus some SGX extension in GLES221:08
*** alehorst has joined #maemo21:08
freemangordonhacky all the way, so that could be a reason21:08
MrPinguWant me to do an eMMC flash too?21:08
DocScrutinizer05anyway, IF problems persist even after flashing, you might want to clean your battery contacts and get a new battery. Such symptoms *might* be caused by worn out LiIon cell or BSI borked - at least some of them, like sudden reboots and act_dead21:08
DocScrutinizer05MrPingu: eMMC most likely unrelated, so no21:09
freemangordonwell, .pvr cache is on eMMC21:09
DocScrutinizer05hmm, deleting it should suffice21:09
freemangordoniirc that is the only place21:10
DocScrutinizer05rm /home/user/.cache/launch/*21:10
MrPinguGet it21:10
DocScrutinizer05no need to flash whole eMMC first instance21:10
MrPinguOne advantage, now I can use your apt-get wrapper from the start :P21:10
MrPinguAre you going? Bye!21:11
*** aloril has joined #maemo21:15
MrPinguYes, something is wrong for sure21:15
MrPingumaybe fscked rootfs21:15
freemangordonmost probably :(21:16
MrPingulet me take a pic21:16
*** valeriusM has quit IRC21:17
MrPinguon boot it shows missing images and such21:17
MrPingusame problem I got with a fake digitizer/frontcover21:18
freemangordonMrPingu: well, well, defffinitely your fottfs is corrupted :(21:23
freemangordonrootfs that is21:23
MrPinguNote: this image problem is the first time I got this21:23
MrPinguI mean I have booted more than once today and I needed to load this screen because battery swap21:24
freemangordonanything suspicious in dmesg log?21:24
freemangordonrelated to NAND21:24
MrPinguHow to read whole dmesg log?21:24
freemangordonzeq1: any progress with ipclite?21:24
freemangordonMrPingu: dmesg21:25
MrPinguI mean i can't go further up on busybox21:25
freemangordondmesg > you_name_it.log21:25
DocScrutinizer05freemangordon: he got syslog meanwhile21:26
DocScrutinizer05syslog >=dmsg21:26
freemangordonyes, too noisy :)21:27
MrPinguI see mtdoops isn dmesg21:27
freemangordoncare to pastebin?21:27
DocScrutinizer05MrPingu: just unrelated "pro-tip": dmesg|less21:31
MrPinguDocScrutinizer05: Thanks21:32
freemangordonhmm, no SGX restarts now your images are missing :P21:33
MrPinguSGX issue was fixed after powercycle21:33
DocScrutinizer05please pastebin sp-oops-decode /dev/mtd221:34
DocScrutinizer05errr sp-oops-extract21:35
freemangordonDocScrutinizer05: makes no sense, his rootfs is FUBAR21:36
DocScrutinizer05probably you're right21:37
freemangordon21:20 <MrPingu>
freemangordonDocScrutinizer05: ^^^21:37
MrPinguYes, it is :(21:37
MrPinguRootfs, I have always treated you very nice. How dare you do this to me? :'(21:38
*** valeriusM has joined #maemo21:38
freemangordonMrPingu: you can check if your battery is loose, that caused me (and other people) lots of problems21:38
freemangordonrestarts/power-offs out of the blue21:38
DocScrutinizer05[2012-08-26 20:08:54] <DocScrutinizer05> anyway, IF problems persist even after flashing, you might want to clean your battery contacts and get a new battery. Such symptoms *might* be caused by worn out LiIon cell or BSI borked - at least some of them, like sudden reboots and act_dead21:38
freemangordoncleaning won't help, he has to extend the springs21:39
MrPingubattery isn't loose21:39
DocScrutinizer05check your battery's contacts. You see bumps like half spheres. Do they touch each other?21:40
DocScrutinizer05well, sorry I'm afk again21:40
freemangordonMrPingu: which kernel do you use?21:41
freemangordonwell, the last kernel opps is from KP47 :D21:41
MrPinguYes I see these bumps, they don't touch21:41
MrPinguAre u sure?21:41
freemangordonaccording to the log21:42
freemangordonlemme check once again21:42
MrPingulogs are saved through reflahs?21:42
MrPingudon't believe that ;p21:42
MrPingulast reflash was in may, KP49 atleast I think21:43
MrPinguGot sane wakeups too now21:43
freemangordon"/dev/mtd2" is not flashed21:43
MrPinguDoesn't it get emptied?21:44
freemangordonMrPingu: yes, the last kernel oops is from KP4721:44
*** Ionakka has quit IRC21:44
freemangordonit is a circular buffer21:44
freemangordonsome kind of :)21:44
teotwaki__pretty insane:
MrPinguit's not a kernel bug then ;)21:46
*** sambo7 has quit IRC21:47
MrPinguIt sucks I need a reflash though21:47
freemangordonMrPingu: well, it is21:48
MrPinguit is?21:48
freemangordonjust doesn't result in oops21:48
povbot_Bug 9150: Device doesn't respond via UI. syslog reports HWRecoveryResetSGX: SGX Hardware Recovery triggered, sgx_misr eating all CPU21:48
freemangordona pretty old one :)21:48
freemangordonit took Nokia 2 years or so to mark it WONTFIX ;)21:49
MrPinguand now I am hit by it -.-21:50
freemangordonyou are hit by a corrupted fs triggering the bug :P21:50
MrPinguidc, it comes both down to an reflash ;p21:51
MrPinguDo you think it's safe to restore yesterday's BM backup or is it possible that contains the corruption?21:52
freemangordonyes "(21:52
freemangordonwell, it worths nothing to try it21:52
freemangordonafaik, as I never used BM21:52
MrPinguMe neither, actually21:52
freemangordonbetter ask doc ;)21:53
freemangordonhe is BM fan and can help you21:53
MrPinguHe said it was safe ;)21:53
freemangordonwell, go on then :)21:53
DocScrutinizer05BM doesn't mkfs21:53
DocScrutinizer05so all you do is replace files via 'cp'21:54
DocScrutinizer05if actually fs is corrupted, a BM restore without prior flashj won't help21:54
zeq1freemangordon: I had a little trouble getting fennec to build from romaxa's  patchset.  For some reason his patches didn't match the base rev. identified in the repo.21:55
DocScrutinizer05a restore after flash can't cause additional damage though, beyond wasted time to do all flashing again21:55
freemangordonzeq1: did you ask romaxa?21:55
MrPinguYou say *additional* :P21:56
*** niwakame|away has quit IRC21:56
DocScrutinizer05well, you might restore files that got messed up/corrupted21:56
kerioBM should really mkfs21:56
kerioi mean, the ubifs21:56
DocScrutinizer05indeed it should have an option for that21:56
DocScrutinizer05at least BM can run fsck21:57
DocScrutinizer05but I guess that's useless on ubifs21:57
kerioattach the ubi volume, mkfs.ubifs21:57
*** |thunder has quit IRC21:57
DocScrutinizer05I still fail to grok why system reboots after 10 minutes21:58
MrPingu(or less)21:59
* DocScrutinizer05 suspects fs corruption not being the root cause of the problem, but maybe rather a consequence21:59
freemangordonDocScrutinizer05: hmm, maybe I am wrong
povbot_Bug 7017: SGX memory reset seems failed during reboot21:59
freemangordonthough besides the statement, there is no real info22:00
freemangordonDocScrutinizer51: some WD is kicking, dsme most probably22:01
*** jhb has joined #maemo22:01
*** hardaker has joined #maemo22:02
freemangordonafaik after n tries in x seconds, if a process still fails to start, dsme reboots the device22:02
freemangordonfails to start as crashes :D22:02
zeq1freemangordon: I need to check to see if romaxa has updated the repo since.  If not I'll contact him.  I did try to fix up the patches but there were still tricky build failures.22:02
MrPinguNote: I got no reboots22:03
MrPinguit's just the device wasn't "on" anymore22:03
MrPingusometimes it booted to act-dead22:03
MrPingusometimes it booted normal22:03
freemangordonzeq1: ok. sorry I can't help, but I just finished VKB REing and want to play with the kernel a little bit. Your libc patches are welcome :P22:03
MrPingubut when it booted normal it insane number of wakeups22:04
freemangordonMrPingu: you have loose battery22:04
freemangordonI can bet on that22:04
zeq1Ah yes, did I not make them available?22:04
zeq1I've still not had any problems fwiw22:05
freemangordonthe only way n900 to power-off out of the blue is through bad battery connection22:05
freemangordonzeq1: don't remember, it was 2-3 weeks ago :D22:05
freemangordonzeq1: anyway, I will pester you starting from tomorrow :P22:06
zeq1ok :)22:06
freemangordonmerlin1991 needs a proper .deb for toolchain ;)22:06
freemangordon4.7.2 I mean22:06
zeq1I'd better get back to my gf, been busy decorating all day, lazy evening...22:07
freemangordonyeah, not a bad idea22:07
keriofreemangordon: or by battery brownout22:07
zeq1freemangordon: native toolchian deb or host (cross) toolchain deb22:07
kerio(if you screw with bme)22:07
freemangordonzeq1: cross22:07
freemangordonthe one installable in OS, not in SB22:08
zeq1I need to build the new one anyway22:08
freemangordonor even better something similar to original SB installer (python one)22:08
*** Darkchaos has quit IRC22:08
freemangordonzeq1: why?22:08
zeq1why use the latest Linaro?22:09
zeq1bug fixes :)22:09
freemangordonhmm, I missed "the latest Linaro" part :P22:09
freemangordonzeq1: but better keep 4.7.222:10
MrPingufreemangordon: IDK, battery doesn't seem to be loose22:10
freemangordonMrPingu: well, NFC then22:10
zeq1yes, that's the Linaro "stable" version (anyway afk for a while)22:10
*** jhb has quit IRC22:10
MrPinguReflashing now, and moving on...22:11
*** wicket64 has joined #maemo22:13
DocScrutinizer05MrPingu: you say the spheres of battery springs don't touch. They should though (at least almost)22:19
*** niwakame|away has joined #maemo22:19
DocScrutinizer05well, not actually touch, but a tiny bit too large a gap between them will cause poor contact to the blades of N90022:21
DocScrutinizer05It's a known problem that springs get out of shape when you insert anything too large into the battery contacts, or even just with time they get too weak22:22
DocScrutinizer05anyway, bending them 'inwards' with a needle or pinpointed knife so much that the spheres touch should cure any such problems (be careful not to cause shortcircuits when doing so!)22:24
teotwaki__bloody hell, I hate it when my credit card bounces22:29
teotwaki__I'm stuck without food tonight, because for some unknown reason, the bank decided to refuse any transaction.22:30
kerio>tracked money22:31
*** qwazix has joined #maemo22:32
*** qwazix has quit IRC22:33
*** sambo7 has joined #maemo22:37
*** dhbiker has quit IRC22:37
*** krayon has joined #maemo22:40
MrPinguDocScrutinizer, well that's just the case. Was about to write I can't see if they touch. Almost none space between them ;)22:47
MrPinguSending cmt-mcusw image (5826 kB)...22:48
MrPingu100% (5826 of 5826 kB, avg. 7970 kB/s)22:48
MrPinguSending request 0x14 failed: Invalid or incomplete multibyte or wide character22:48
MrPinguFlashing cmt-mcusw... Sending request 0x50 failed: Protocol error22:48
MrPinguWTF for problem do we have now? :(22:48
teotwaki__kerio: tell me about it22:48
keriolrn2cash and bitcoins22:49
keriowhich are about the same thing22:49
kerioactually, bitcoins are even *less* traceable22:49
*** iDont has quit IRC22:49
*** |thunder has joined #maemo22:50
*** bsdmaniak has joined #maemo22:53
*** dhbiker has joined #maemo22:53
MrPingumd5sums match22:54
teotwaki__kerio: lol, I'll be damned if I get conned in one of does stupid pyramid schemes22:57
kerioteotwaki__: like the US dollar?22:57
teotwaki__kerio: and sorry, but the whole "traceable" thing, I LOL when I see the first "bitcoin credit card" on /..22:57
MrPingunvm, other USB connection saved it22:57
*** perlite has quit IRC23:22
*** perlite has joined #maemo23:24
*** atlas has joined #maemo23:29
DocScrutinizer05I thought bitcoin is zombibied meanwhile23:31
DocScrutinizer05or gone down like Reichmarks23:32
infobotsomebody said jrtools was
*** MrPingu has quit IRC23:36
*** nox- has joined #maemo23:40
*** Venusaur has quit IRC23:44
*** Venusaur has joined #maemo23:47
*** kodomo_ has joined #maemo23:49
sambo7hi nandtester here23:49
keriohi sambo723:50
sambo7FINALLY I was able to revive my device:-)23:50
sambo7flasher-3.5 -h RX-51:2101 -F RX-51_2009SE_20.2010.36-2.203.1_PR_COMBINED_203_ARM.bin -c -S usb -f23:50
sambo7cold flashing didn't work for me23:51
sambo7at least what is described in the tutorial23:51
Sicelolooks like cold-flashing to me23:52
sambo7and flasher-3.5 -h RX-51:2101 -F <fiasco_image> -c -S usb23:52
*** kodomo has quit IRC23:52
Sicelowhat was the problem btw?23:52
sambo7didn't work either23:52
sambo7I nandtested mtd0-mtd523:53
sambo7I also was trying to use Nokia phoenix...cold flashing was ok,but warm flashing failed23:53
sambo7in the beginning I was always using the global image23:54
sambo7but a few days ago I remembered that I have a device from Englang and I started to use the English image23:55
sambo7don't know if this made a difference23:55
Sicelonice. i think someone else had tol use a 'localized' image a while back23:56
Sicelophoenix didn't need some special cable?23:56
DocScrutinizer05if coldflash restores CAL, then for sure localization matters23:56
DocScrutinizer05btw >>flasher-3.5 -h RX-51:2101 -F RX-51_2009SE_20.2010.36-2.203.1_PR_COMBINED_203_ARM.bin -c -S usb -f<< and >>flasher-3.5 -h RX-51:2101 -F <fiasco_image> -c -S usb<< seem to differ only in additional -f23:57
DocScrutinizer05err, mompls23:57
*** hurbu has quit IRC23:58
DocScrutinizer05and actually if coldflashing fails, the hw build revision might matter23:59
DocScrutinizer05iirc you only took a shot into the blue with 210123:59
sambo7I have a lot of errors when I run dmesg23:59
*** MrPingu has joined #maemo23:59

Generated by 2.15.1 by Marius Gedminas - find it at!