| 00:15.16 | *** join/#maemo whsailing (~whsailing@112.97.192.27) |
| 00:28.58 | *** part/#maemo whsailing (~whsailing@112.97.192.27) |
| 00:31.25 | *** join/#maemo Vibe (~Vibe@gateway/tor-sasl/vib3) |
| 00:38.34 | *** join/#maemo pauly (62da843f@gateway/web/freenode/ip.98.218.132.63) |
| 00:40.49 | pauly12 | hello |
| 00:41.19 | *** join/#maemo MacDrunk (~marper@201.164.158.209) |
| 00:42.00 | *** join/#maemo retro|cz (~retro@106.142.broadband6.iol.cz) |
| 00:42.30 | *** part/#maemo MacDrunk (~marper@201.164.158.209) |
| 00:48.01 | *** join/#maemo Gizmokid2005 (~Gizmokid2@dedi.gizmokid2005.com) |
| 00:48.36 | pauly12 | i miss the n900 |
| 00:49.18 | pauly12 | no other phone takes raw pics |
| 00:56.37 | *** join/#maemo ArGGu^^ (~ArGGu^^@91-157-136-189.elisa-laajakaista.fi) |
| 01:05.03 | *** join/#maemo uen| (~uen@p5DCB13D2.dip.t-dialin.net) |
| 01:07.40 | jacekowski | so |
| 01:07.49 | jacekowski | raw pics from shit senor are still shit |
| 01:07.52 | jacekowski | sensor* |
| 01:08.30 | jonwil | I have yet to see a cellphone camera sensor that is as good as even my fairly-entry-level Canon point & shoot |
| 01:08.34 | jacekowski | raw is barely useful on DSLRs or other high end camera |
| 01:09.06 | jacekowski | unfortunately, if your picture is overexposed/underexposed/broken in any other way - raw won't help you |
| 01:12.46 | *** join/#maemo Neutron8 (~neutron@159.80-202-97.nextgentel.com) |
| 01:13.20 | jacekowski | well, 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 print |
| 01:13.25 | jacekowski | is* |
| 01:14.14 | jacekowski | if you have enough light there is a lot you can do even with bad sensor |
| 01:14.59 | jonwil | My Canon is much better at taking far away shots with its 10x optical zoom |
| 01:15.09 | jonwil | and much better at taking close up shots with its really good macro mode |
| 01:16.48 | jacekowski | macro mode just enables close focusing |
| 01:17.30 | jonwil | yes but not all cameras are good at it |
| 01:17.42 | jonwil | Like the Sony I owned once (piece of junk that was) |
| 01:17.56 | jacekowski | sony now makes good EVIL cameras |
| 01:18.06 | jacekowski | and well, their DSLRs are not bad either |
| 01:18.25 | jonwil | I would never buy another Sony product, not after some of the Sony crap I have bought over the years |
| 01:18.48 | jacekowski | well, i've bough samsung point and shoot |
| 01:19.03 | jacekowski | as a gift for someone |
| 01:19.12 | jacekowski | and well, for the money, pictures are great |
| 01:19.17 | jonwil | I would only ever buy Canon cameras, I have used several and they are good |
| 01:19.28 | jacekowski | though my dslr that costs 10x as much takes better pictures |
| 01:20.13 | jacekowski | but i'm well surprised how samsung got into doign everything electronic |
| 01:20.16 | jacekowski | and they are good at it |
| 01:20.17 | jonwil | I have a family member who swears by the Canon DSLRs (and is always putting new ones on his wishlist :) |
| 01:20.29 | jacekowski | nikon is much better |
| 01:20.47 | jacekowski | and backwards compatible with lenses from first nikon dslrs |
| 01:20.48 | jonwil | I have both a Samsung LCD monitor and a Samsung LCD TV and they are really good |
| 01:21.25 | jacekowski | though it's silly how much you have to pay for some of the features |
| 01:21.31 | jacekowski | wifi - extra £150 |
| 01:21.46 | Luke-Jr | meh, a camera's a camera. |
| 01:21.46 | jacekowski | while samsung camera has it all and costs £130 in total |
| 01:21.58 | jacekowski | Luke-Jr: it's not as simple as that |
| 01:24.48 | jonwil | What 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) |
| 01:25.18 | jacekowski | people don't know that |
| 01:25.24 | jacekowski | all they compare is megapixels |
| 01:31.36 | *** join/#maemo LaoLang_cool (~LaoLang_c@221.226.175.141) |
| 01:34.27 | SpeedEvil | It's not that simple. |
| 01:34.58 | SpeedEvil | If 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. |
| 01:35.28 | SpeedEvil | Surely - the individual noise per device changes - but once you 'bin' them into a resulting image, it does not change. |
| 01:35.57 | SpeedEvil | Exceeding the lens resolution can have other plusses - it reduces the colour artifacts due to the bayer matrix. |
| 01:36.29 | SpeedEvil | Also - go and look at the 'dpreview' review of the nokia 808 pureview |
| 01:38.34 | SpeedEvil | It's actually not terrible, even uncropped. |
| 01:39.46 | *** join/#maemo Neutron8 (~neutron@80.202.97.161) |
| 01:44.04 | *** join/#maemo Neutron9 (~neutron@80.202.97.159) |
| 01:45.40 | *** join/#maemo atlas (~atlas@kurios.r4780y.com) |
| 01:49.17 | *** join/#maemo lxp (~lxp@212-183-126-89.adsl.highway.telekom.at) |
| 01:53.18 | *** part/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 01:53.29 | *** join/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 01:58.50 | *** join/#maemo mlwane (~mlwane@94.97.5.33) |
| 01:59.40 | *** join/#maemo ezisto (~mlwane@94.97.5.33) |
| 02:11.03 | *** join/#maemo Neutron9 (~neutron@80.202.97.159) |
| 02:28.50 | *** join/#maemo iluminator105 (~iluminato@unaffiliated/iluminator105) |
| 02:29.11 | iluminator105 | this smartreflex is that built into kernel after 50 or you have to install it separately |
| 02:29.54 | *** part/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 02:30.05 | *** join/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 02:34.18 | DocScrutinizer05 | smartreflex is some hw block in CPU, that automatically adjusts the PSU chip Vcore voltage according to clock speed the CPU runs at |
| 02:34.44 | DocScrutinizer05 | you can enable/disable/configure that hw block |
| 02:35.47 | DocScrutinizer05 | but 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 hw |
| 02:35.59 | iluminator105 | how do you enable hw block |
| 02:36.25 | DocScrutinizer05 | via a command to kernel, that sets some special control registers |
| 02:36.54 | DocScrutinizer05 | iirc they are called auxiliary control registers |
| 02:37.19 | DocScrutinizer05 | or did you mean how users can do that? |
| 02:37.34 | iluminator105 | hmm... i meant how users can do that yea |
| 02:37.54 | DocScrutinizer05 | for user there's some /sysfs/*/*/* node that you can write true/flase to |
| 02:38.01 | DocScrutinizer05 | or 1/0 |
| 02:38.34 | DocScrutinizer05 | there are other related sysfs nodes to configure the SR hw block |
| 02:38.48 | DocScrutinizer05 | buzzword *volting |
| 02:38.59 | DocScrutinizer05 | and efuse IIRC |
| 02:39.22 | iluminator105 | also how can install cssu kernel to n900 as a new install wipe the old installation |
| 02:39.57 | DocScrutinizer05 | basically 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) |
| 02:40.03 | *** join/#maemo nix900 (~bugzy@99-191-138-94.lightspeed.irvnca.sbcglobal.net) |
| 02:40.38 | DocScrutinizer05 | sorry, there's no official such thing like a cssu-kernel yet |
| 02:41.28 | iluminator105 | so i would have to reset to factory setting then upgrade |
| 02:41.41 | *** join/#maemo radic_ (~radic@dslb-178-010-026-182.pools.arcor-ip.net) |
| 02:42.12 | DocScrutinizer05 | there'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 PPK51 |
| 02:42.57 | DocScrutinizer05 | iluminator105: 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" |
| 02:44.01 | iluminator105 | i 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 times |
| 02:44.29 | *** join/#maemo SmilyOrg (Smily@BSN-176-219-252.dial-up.dsl.siol.net) |
| 02:44.33 | DocScrutinizer05 | for cssu-thumb you'd need pk51/thumb-kernel |
| 02:45.04 | DocScrutinizer05 | o.O |
| 02:45.41 | DocScrutinizer05 | sorry, you lost me. No clue what's "ppp0 devel-adhoc" and how it might be related to cssu or update |
| 02:47.35 | *** part/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 02:47.40 | DocScrutinizer05 | maybe you managed to enable wifi injection drivers? |
| 02:47.45 | *** join/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 02:48.58 | DocScrutinizer05 | if 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 that |
| 02:49.02 | iluminator105 | DocScrutinizer05, i dont how to get rid expect to reinstall to factory settings |
| 02:50.04 | DocScrutinizer05 | reinstall factory settings means reflash rootfs+kernel, IOW go for flashing COMBINED in |
| 02:50.09 | DocScrutinizer05 | ~flashing |
| 02:50.09 | infobot | well, maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware |
| 02:50.38 | iluminator105 | you lost me on cssu-thumb 2 byte code i get it but....i though if you install powerkernel thumb is installed as part of it |
| 02:51.38 | DocScrutinizer05 | and - 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 them |
| 02:52.39 | DocScrutinizer05 | most recent powerkernel comes with a patch for thumb executables |
| 02:52.51 | iluminator105 | agreed |
| 02:52.55 | DocScrutinizer05 | user can enable and disable that patch |
| 02:53.25 | DocScrutinizer05 | that doesn't mean you may disable patch to revert to previous state |
| 02:53.55 | DocScrutinizer05 | since then all your thumb binaries in userland that you installed will start segfaulting like mad |
| 02:54.16 | iluminator105 | well 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 go |
| 02:54.41 | DocScrutinizer05 | then flashing is the only way for you to recover to known state |
| 02:55.12 | DocScrutinizer05 | ~flashing |
| 02:55.12 | infobot | well, maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware |
| 02:55.34 | iluminator105 | i 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 all |
| 02:56.31 | DocScrutinizer05 | reflash to plain vanilla maemo5 PR1.3 |
| 02:56.51 | DocScrutinizer05 | then from that factory default go on and do your changes as you like |
| 02:57.57 | DocScrutinizer05 | for what you just stated you want to do, you'll probably want to install powerkernel50 or 51 |
| 02:58.33 | DocScrutinizer05 | which is a precondition to do overclocking |
| 02:59.48 | DocScrutinizer05 | (though honestly I personally would prefer thumb over OC every day) |
| 03:00.30 | DocScrutinizer05 | but thumb is still quite experimental |
| 03:01.20 | DocScrutinizer05 | anyway, first step: flashing COMBINED fiasco image. good luck |
| 03:01.38 | iluminator105 | thumb seems complicated more chances of an error |
| 03:02.02 | DocScrutinizer05 | rather first first step: do a proper full backup, preferrably by backupmenu |
| 03:02.38 | DocScrutinizer05 | (thumb) yes, it's still experimental and thus not exactly a streamlined user experience |
| 03:02.48 | DocScrutinizer05 | for installation |
| 03:06.07 | DocScrutinizer05 | regarding 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 of |
| 03:20.51 | *** join/#maemo Gh0sty (~ghosty@79.132.235.166) |
| 03:41.47 | *** join/#maemo Vanadis__ (~Vanadis@46-126-8-235.dynamic.hispeed.ch) |
| 03:50.07 | Macer | i want my blu ecigs :-/ |
| 03:50.36 | Macer | i can see it now. a total act of desperation forcing me to use usb host mode on my n900 just to charge the ecig pack |
| 04:00.10 | *** join/#maemo npm_ (~npm@cpe-198-72-183-90.socal.res.rr.com) |
| 04:00.58 | beford | i've not had a crash using thumb |
| 04:08.04 | *** join/#maemo GNUton-BNC (~gnuton@85-156-118-65.elisa-mobile.fi) |
| 04:13.41 | *** join/#maemo kimitake (~kimitake@75.0.178.95) |
| 04:32.38 | *** join/#maemo ferdna (~ferdna@cpe-67-10-220-35.elp.res.rr.com) |
| 04:33.24 | *** join/#maemo kov_ (~kov@201-58-117-145.user.veloxzone.com.br) |
| 05:39.53 | *** join/#maemo auenf (David@171.72.233.220.static.exetel.com.au) |
| 06:24.39 | *** join/#maemo hazchemix (~user@ip51ccb388.speed.planet.nl) |
| 06:33.04 | *** join/#maemo githogori (~githogori@c-50-131-15-16.hsd1.ca.comcast.net) |
| 06:40.59 | *** join/#maemo e-yes (~e-yes@94.45.170.98) |
| 06:41.30 | *** join/#maemo dhbiker (~dhbiker@46.123.29.0) |
| 06:41.40 | *** join/#maemo LaoLang_cool (~LaoLang_c@221.226.175.141) |
| 07:10.07 | *** join/#maemo livelace (~livelace@62.192.242.235) |
| 07:11.18 | *** join/#maemo RP_ (~richard@93-97-173-237.zone5.bethere.co.uk) |
| 07:16.36 | *** join/#maemo ChikuLinu__ (~Chiku01@vau06-5-88-183-56-98.fbx.proxad.net) |
| 07:16.51 | *** join/#maemo TrD (~nnscript@dsl-pribrasgw1-ff15c300-52.dhcp.inet.fi) |
| 07:23.30 | *** join/#maemo Pali (~pali@unaffiliated/pali) |
| 07:24.47 | *** join/#maemo zsolt_hun (~zsolt@catv-89-133-7-183.catv.broadband.hu) |
| 07:25.36 | zsolt_hun | hi there.try to boot nitrdroid with uboot,but it cant recognize vmlinuz,bad format |
| 07:26.34 | zsolt_hun | i'm stuck with bootloaders and now don't have an idea which one is better |
| 07:28.52 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 07:29.24 | *** join/#maemo Rantwolf (~rantwolf@static-217-17-207-54.net.encoline.de) |
| 07:29.41 | *** join/#maemo utanapischti (~username@p579585D7.dip.t-dialin.net) |
| 07:31.47 | *** join/#maemo OkropNick (~OkropNick@host-n2-72-190.telpol.net.pl) |
| 07:36.37 | *** join/#maemo zsolt_hun (~zsolt@catv-89-133-7-183.catv.broadband.hu) |
| 07:37.04 | *** join/#maemo RP_ (~richard@93-97-173-237.zone5.bethere.co.uk) |
| 07:46.50 | *** join/#maemo RP_ (~richard@93-97-173-237.zone5.bethere.co.uk) |
| 07:57.04 | *** join/#maemo onekenthomas (~kthomas@c-107-3-244-159.hsd1.tn.comcast.net) |
| 08:09.49 | *** part/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 08:09.59 | *** join/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 08:27.42 | *** join/#maemo RST38h (marat@wsip-184-180-40-182.ri.ri.cox.net) |
| 08:36.46 | *** join/#maemo NIN101 (~NIN@p5DD29778.dip0.t-ipconnect.de) |
| 08:40.48 | *** join/#maemo sirdancealot7 (~sirdancea@98.82.broadband5.iol.cz) |
| 08:52.09 | *** join/#maemo netkat (~tty1@tm.82.192.36.45.dc.telemach.net) |
| 09:06.47 | *** join/#maemo alehorst (~alehorst@177.16.36.166) |
| 09:07.35 | *** join/#maemo Pali (~pali@unaffiliated/pali) |
| 09:18.56 | *** join/#maemo Pali (~pali@unaffiliated/pali) |
| 09:19.38 | *** join/#maemo jhb (~joerg@tmo-107-17.customers.d1-online.com) |
| 09:30.26 | *** join/#maemo ced117 (~ced117@AStrasbourg-552-1-104-99.w92-148.abo.wanadoo.fr) |
| 09:30.26 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 09:34.56 | *** join/#maemo TrD (~nnscript@dsl-pribrasgw1-ff15c300-52.dhcp.inet.fi) |
| 09:37.12 | *** join/#maemo Zuccace (zucca@dsl-hkibrasgw4-fe54df00-80.dhcp.inet.fi) |
| 09:38.10 | *** join/#maemo Elleo (~Elleo@mikeasoft.com) |
| 09:38.10 | *** join/#maemo Elleo (~Elleo@libre.fm/hacker/elleo) |
| 09:40.51 | *** join/#maemo jhb1 (~joerg@tmo-096-157.customers.d1-online.com) |
| 09:44.45 | *** join/#maemo brzys (~brzys@213.189.44.27) |
| 09:45.35 | *** join/#maemo TrD` (~nnscript@dsl-pribrasgw1-ff15c300-52.dhcp.inet.fi) |
| 09:45.42 | *** join/#maemo freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net) |
| 09:47.50 | *** join/#maemo sq-one (~sq-one@p57977D9D.dip.t-dialin.net) |
| 09:52.06 | *** join/#maemo florian (~fuchs@p5B23EF34.dip.t-dialin.net) |
| 09:52.07 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 10:02.47 | *** join/#maemo jhb (~joerg@82.113.121.102) |
| 10:02.57 | *** join/#maemo iDont (~dennis@j138215.upc-j.chello.nl) |
| 10:03.14 | *** part/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 10:03.45 | *** join/#maemo brzys (~brzys@86-63-126-137.sta.asta-net.com.pl) |
| 10:06.05 | *** join/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 10:10.53 | *** join/#maemo GNUton-BNC (~gnuton@85-156-118-65.elisa-mobile.fi) |
| 10:15.35 | *** join/#maemo thomasjfox (~thomasjfo@rockbox/developer/thomasjfox) |
| 10:26.13 | *** join/#maemo mlwane (~mlwane@94.97.5.33) |
| 11:00.06 | *** join/#maemo e-yes (~e-yes@94.45.170.98) |
| 11:05.42 | *** join/#maemo maybeArgh (~cl@p5B16624F.dip.t-dialin.net) |
| 11:40.53 | *** join/#maemo HtheB (~HtheB@82-169-197-27.ip.telfort.nl) |
| 11:49.40 | *** join/#maemo Jucato (~Jucato@kde/developer/jucato) |
| 12:01.13 | *** join/#maemo FIQ (~FIQ@unaffiliated/fiq) |
| 12:07.14 | *** join/#maemo alehorst (~alehorst@177.16.36.166) |
| 12:10.50 | *** join/#maemo Zucca (zucca@dsl-hkibrasgw4-fe54df00-80.dhcp.inet.fi) |
| 12:14.28 | *** join/#maemo jean_brat (~shreevath@122.167.229.76) |
| 12:27.10 | *** join/#maemo brzys (~brzys@86-63-126-137.sta.asta-net.com.pl) |
| 12:42.57 | *** join/#maemo retro|cz (~retro@106.142.broadband6.iol.cz) |
| 12:49.32 | *** join/#maemo cyborg-one (~cyborg-on@79-140-1-86.broadband.tenet.odessa.ua) |
| 12:50.33 | *** join/#maemo FIQ (~FIQ@unaffiliated/fiq) |
| 12:53.29 | *** join/#maemo Darkchaos (~darkchaos@88.130.211.232) |
| 12:55.40 | *** join/#maemo sq-one (~sq-one@p57977D9D.dip.t-dialin.net) |
| 13:04.24 | *** join/#maemo GNUton-BNC (~gnuton@85-156-118-65.elisa-mobile.fi) |
| 13:19.36 | *** join/#maemo hardaker (~hardaker@mail.hardakers.net) |
| 13:21.03 | kerio | hm, what's the best way to make a simple debian chroot jail? |
| 13:21.08 | kerio | i don't want the whole of easy debian |
| 13:22.37 | DocScrutinizer05 | depends on what you need |
| 13:23.10 | DocScrutinizer05 | man chroot |
| 13:25.43 | DocScrutinizer05 | or rather info chroot |
| 13:27.07 | NIN101 | I would say using debootstrap |
| 13:29.47 | kerio | NIN101: does it work if the host is not debian but only debian-ish? |
| 13:30.05 | DocScrutinizer05 | kerio: see info chroot |
| 13:30.17 | DocScrutinizer05 | it depends on what you want to run in your "jail" |
| 13:31.05 | DocScrutinizer05 | chroot is a pretty simple and easy to grok concept |
| 13:31.22 | NIN101 | iirc I deboostraped debian sid from maemo |
| 13:35.19 | *** join/#maemo ThreeM (~DonJohnso@cassiopeia.uberspace.de) |
| 13:38.13 | DocScrutinizer05 | kerio: 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/chroot |
| 13:38.44 | kerio | well, i want to protect the maemoness of my system |
| 13:39.29 | DocScrutinizer05 | and which components/devices of "server" system your binary running in chroot "client" needs access to |
| 13:39.51 | kerio | debianness :) |
| 13:42.09 | DocScrutinizer05 | on 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 space |
| 13:42.27 | kerio | well no, you would just move the rootfs there :) |
| 13:42.43 | DocScrutinizer05 | well, sorry. I can't help you there |
| 13:42.59 | DocScrutinizer05 | too few input to start thinking about your problem |
| 13:43.12 | kerio | i *am* aware of how chroot jails work, i just wanted to know if there was a preferred way of doing it |
| 13:45.02 | kerio | hmm, there *is* such a thing as "easychroot" |
| 13:45.08 | kerio | (the thing easydebian uses) |
| 13:45.29 | *** join/#maemo ThreeM (~DonJohnso@cassiopeia.uberspace.de) |
| 13:46.44 | NIN101 | I would just go with debootstrap, it's one command and you get a minimal debian... |
| 13:47.48 | kerio | NIN101: easychroot is just a bunch of scripts to use chroot jails apparently |
| 13:54.15 | DocScrutinizer05 | what else? |
| 13:54.40 | DocScrutinizer05 | there's simply not more to chroot than that |
| 13:55.03 | kerio | DocScrutinizer05: oh god lol |
| 13:55.08 | kerio | user ALL = NOPASSWD: ALL |
| 13:55.20 | DocScrutinizer05 | I know ;-P |
| 13:55.22 | kerio | that's in "/etc/sudoers.d/chroot.sudoers" in the easy-chroot package |
| 13:55.24 | DocScrutinizer05 | ~jrtools |
| 13:55.25 | infobot | jrtools is, like, http://wiki.maemo.org/User:Joerg_rw/tools |
| 13:55.27 | kerio | no, no |
| 13:55.43 | kerio | THIS SHIT ENABLES PASSWORDLESS SUDO WITHOUT WARNING |
| 13:55.48 | kerio | what the fuck |
| 13:56.01 | DocScrutinizer05 | well, seems chroot.sudores took a bad example |
| 13:56.02 | NIN101 | windows xp. |
| 13:56.16 | kerio | i mean, this is in extras |
| 13:56.41 | DocScrutinizer05 | I thought rootsh looks pretty similar |
| 13:56.49 | kerio | yeah |
| 13:56.55 | kerio | but at least that gives out a warning |
| 13:57.02 | kerio | i wouldn't've known about this crap |
| 13:57.11 | DocScrutinizer05 | fools with no idea about sudo and security |
| 13:57.28 | kerio | also haha, easy-chroot installs its own /sbin/chroot |
| 13:57.33 | kerio | as /sbin/qchroot |
| 13:57.37 | kerio | probably because of messybox |
| 13:57.45 | DocScrutinizer05 | :-o |
| 13:57.50 | kerio | oh no, nvm |
| 13:58.10 | kerio | it's just a shell script that chroots with bells and whistles and insecurity |
| 13:58.22 | kerio | mount -o bind /dev "$CHROOT/dev" |
| 13:58.25 | kerio | oh HELL NAW |
| 13:58.45 | DocScrutinizer05 | well, that's where chroot details start |
| 13:58.58 | kerio | yeah but you don't... do that |
| 13:59.15 | DocScrutinizer05 | do you want to grant your jailed binary access to real devices or not |
| 13:59.26 | kerio | maybe not *all* of them |
| 13:59.39 | kerio | i mean, i suppose it's actually fine |
| 13:59.53 | kerio | once you have root you can mknod anyway |
| 14:01.34 | freemangordon | guys, a stupid question, when typing with virtual keyboard and word prediction turned on, how to use what is predicted? |
| 14:08.02 | DocScrutinizer05 | ((<kerio> maybe not *all* of them)) that's why I asked what you want to do in your chroot |
| 14:08.19 | kerio | DocScrutinizer05: i don't actually know, i feel content with fremantle as it is |
| 14:08.21 | kerio | \_o_/ |
| 14:08.33 | DocScrutinizer05 | well, I think you know pretty good how to set up a chroot for your needs |
| 14:08.51 | DocScrutinizer05 | :-) |
| 14:08.54 | kerio | =D |
| 14:09.01 | kerio | well, i actually kinda do |
| 14:09.19 | DocScrutinizer05 | the only problem is you should get to know your needs then |
| 14:10.02 | kerio | i suppose so |
| 14:10.12 | MohammadAG | freemangordon, tap as if moving cursor |
| 14:11.23 | Sicelo | kewl. /me never knew either |
| 14:11.50 | MohammadAG | freemangordon, test0,2ing <--tap here |
| 14:15.25 | *** join/#maemo mase76 (~mase76@p5DD3A155.dip.t-dialin.net) |
| 14:19.19 | freemangordon | MohammadAG: thanks |
| 14:23.56 | *** join/#maemo ThreeM (~DonJohnso@cassiopeia.uberspace.de) |
| 14:24.03 | DocScrutinizer05 | a common step for mankind, but a giant leap for you, man! (in memoriam Niel Armstrong) |
| 14:24.05 | *** join/#maemo ludens (~user@93.158.64.201) |
| 14:35.38 | *** join/#maemo ludens (~user@93.158.64.201) |
| 14:42.46 | *** join/#maemo DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 14:56.13 | *** join/#maemo sLumPia (~sLumPia@182.11.148.58) |
| 14:56.53 | *** join/#maemo ludens (~user@93.158.64.201) |
| 15:08.49 | *** join/#maemo alehorst (~alehorst@177.16.36.166) |
| 15:16.18 | *** join/#maemo DHR (~hugh@CPE00606767ed59-CM000f9fa81660.cpe.net.cable.rogers.com) |
| 15:17.38 | *** join/#maemo MrPingu (~chatzilla@86.92.226.97) |
| 15:36.50 | MrPingu | Anyone experienced constant shutdowns after 10 mins of uptime or less on N900? |
| 15:37.44 | *** join/#maemo nix900 (~bugzy@99-191-138-94.lightspeed.irvnca.sbcglobal.net) |
| 15:38.35 | MrPingu | Suddenly, really suddenly... when I am in maemo or bootmenu it just shutdowns the whole time... Luckily backupmenu works on mass storage... |
| 15:39.16 | joga | hmh...nope |
| 15:39.28 | kerio | MrPingu: overclocked? |
| 15:39.31 | MrPingu | Nope |
| 15:39.39 | kerio | full reflash and try again |
| 15:39.43 | kerio | if it still does that, then it's borked |
| 15:39.46 | MrPingu | but I have 36000 wakeups :D |
| 15:39.57 | joga | in powertop? |
| 15:39.59 | kerio | otherwise, you messed up something that the watchdog expects |
| 15:40.01 | MrPingu | yeah |
| 15:40.20 | MrPingu | Well, let's tell the story from the start |
| 15:40.40 | MrPingu | Yesterday night went to bed, woke up this morning -> Everything fine |
| 15:41.01 | *** join/#maemo atlas (~atlas@ppp-69-214-12-43.dsl.klmzmi.ameritech.net) |
| 15:41.04 | MrPingu | from 8 am to 12 it worked nicely |
| 15:41.18 | MrPingu | then I wanted to check time around 14:00 |
| 15:41.26 | *** join/#maemo valeriusM (~user@95.153.180.13) |
| 15:41.32 | MrPingu | phone not responding, battery dead |
| 15:42.21 | MrPingu | Swapped battery with full one, 10 mins later phone off again |
| 15:42.34 | MrPingu | checked battery in other phone was full for about 70% |
| 15:43.27 | MrPingu | Guess I need a reflash but it's just odd |
| 15:43.52 | MrPingu | restoring backup from backupmenu (1week old)didn't help either |
| 15:45.23 | *** join/#maemo sambo7 (b219f8ff@gateway/web/freenode/ip.178.25.248.255) |
| 15:45.43 | MrPingu | What can go wrong so suddenly? I mean I didn't even touch my phone... |
| 15:46.38 | Sicelo | modem |
| 15:47.32 | MrPingu | Sicelo: Any fix or do I need to reflash? |
| 15:49.01 | Sicelo | i 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, etc |
| 15:49.33 | *** join/#maemo NIN101 (~NIN@p5DD29778.dip0.t-ipconnect.de) |
| 15:51.17 | DocScrutinizer05 | MrPingu: you got KP51? |
| 15:51.23 | MrPingu | cssu3 |
| 15:51.31 | DocScrutinizer05 | ? |
| 15:51.35 | MrPingu | = KP51 from what I heard |
| 15:51.50 | *** join/#maemo Ionakka (~lechuck@a91-153-151-125.elisa-laajakaista.fi) |
| 15:52.00 | kerio | MrPingu: do you have something in dmesg? |
| 15:52.20 | DocScrutinizer05 | well, I totally lost track of this cssu-kernel stuff, actually there's no official cssu-kernel for plain CSSU-T/S |
| 15:52.37 | MrPingu | I am on thumb ;) |
| 15:52.51 | MrPingu | Anyway from what FMG told, cssu3 = KP51 |
| 15:52.54 | DocScrutinizer05 | I guess your problems are with KP, bme, bq24150.ko and related stuff |
| 15:53.19 | DocScrutinizer05 | we've seen several such reports lately |
| 15:53.20 | kerio | maaaaaaaaan |
| 15:53.30 | kerio | that's FUD-ish |
| 15:53.52 | DocScrutinizer05 | kerio: that's summary of events / reports of last few weeks |
| 15:54.21 | MrPingu | DocScrutinizer05, I didn't play with bme bq245150.ko. Can it go insane without interaction? |
| 15:54.34 | DocScrutinizer05 | that's the huge mystery |
| 15:54.34 | kerio | in theory, no |
| 15:54.35 | MrPingu | damnit, now this brick doesn't even turn on |
| 15:54.38 | kerio | the module is blacklisted |
| 15:55.20 | MrPingu | oh nvm, act-dead state -.- |
| 15:55.27 | kerio | haha |
| 15:55.43 | kerio | yep, definetely bq24k.ko problem |
| 15:55.55 | DocScrutinizer05 | MrPingu: yeah, exactly in line with what we heard from other similar reports. Remove battery, reinsert after >60s, should reboot then |
| 15:56.05 | kerio | DocScrutinizer05: after 60s? what's that time? |
| 15:56.08 | kerio | bupbat fail? |
| 15:56.30 | DocScrutinizer05 | probably discharge time for Vbat buffer capacitors |
| 15:56.30 | kerio | capacitors losing power? |
| 15:56.35 | kerio | i see |
| 15:56.57 | Sicelo | ah, same issue as Estel had |
| 15:57.02 | DocScrutinizer05 | I strongly suggest to roll back to KP50 |
| 15:57.28 | kerio | :c |
| 15:58.12 | MrPingu | Still 14000 wakeups, not a sane value |
| 15:58.24 | DocScrutinizer05 | causede by whom? |
| 15:58.32 | DocScrutinizer05 | -e |
| 16:00.12 | MrPingu | How to see that? |
| 16:00.21 | *** join/#maemo mase_76 (~mase76@p5DD3A155.dip.t-dialin.net) |
| 16:00.28 | DocScrutinizer05 | I'd bet it's I2C, bme, and/or kernel bq24150 |
| 16:00.33 | DocScrutinizer05 | MrPingu: powertop |
| 16:00.47 | DocScrutinizer05 | MrPingu: how do you see the 14k wakeups? |
| 16:01.01 | MrPingu | I understand but how to see from what they come? |
| 16:01.40 | DocScrutinizer05 | once there's IRQs listed with count, and then there's list of processes with count |
| 16:01.57 | MrPingu | DMA - 7126 |
| 16:02.10 | MrPingu | I2c_omap - 3339 |
| 16:02.25 | MrPingu | gp - 2386 |
| 16:02.42 | kerio | what's gp? |
| 16:02.51 | MrPingu | you tell me :P |
| 16:02.53 | DocScrutinizer05 | graphics processor? not sure |
| 16:03.21 | DocScrutinizer05 | or general purpose |
| 16:03.59 | DocScrutinizer05 | I2C is kinda high |
| 16:04.07 | MrPingu | Anyway you are right i2c_omap is gone ape |
| 16:04.20 | DocScrutinizer05 | dma for sure too |
| 16:04.33 | MrPingu | It's even listed twice in IRQ table ;p |
| 16:04.34 | DocScrutinizer05 | is that 56 or 57 |
| 16:04.36 | DocScrutinizer05 | ? |
| 16:04.51 | DocScrutinizer05 | there are two I2C busses |
| 16:04.53 | *** join/#maemo NIN101 (~NIN@p5DD29778.dip0.t-ipconnect.de) |
| 16:04.56 | MrPingu | The highest is 56 |
| 16:05.05 | MrPingu | the one lower in the table is 57 |
| 16:05.47 | DocScrutinizer05 | <PROTECTED> |
| 16:05.48 | DocScrutinizer05 | <PROTECTED> |
| 16:05.50 | DocScrutinizer05 | <PROTECTED> |
| 16:05.51 | DocScrutinizer05 | <PROTECTED> |
| 16:06.38 | DocScrutinizer05 | PID# | Activity | Name | Function Entry (Expire) |
| 16:06.40 | DocScrutinizer05 | --------+------------+----------------+--------------------------- |
| 16:06.41 | DocScrutinizer05 | <PROTECTED> |
| 16:07.29 | DocScrutinizer05 | <PROTECTED> |
| 16:07.31 | DocScrutinizer05 | <PROTECTED> |
| 16:07.32 | DocScrutinizer05 | <PROTECTED> |
| 16:07.55 | DocScrutinizer05 | this is with device idle, on fastcharger |
| 16:08.19 | MrPingu | Mine is on pc, on idle too |
| 16:08.53 | DocScrutinizer05 | so what are your top 3 PIDæactivity|name? |
| 16:09.13 | MrPingu | C# | Ratio | Avg/dura | Frequency | Ratio |
| 16:09.14 | MrPingu | --------+--------+----------+-----------+--------+ |
| 16:09.16 | MrPingu | <PROTECTED> |
| 16:09.17 | MrPingu | <PROTECTED> |
| 16:09.22 | MrPingu | That's just not normal :O |
| 16:09.24 | DocScrutinizer05 | nah, not that |
| 16:10.09 | MrPingu | <PROTECTED> |
| 16:10.10 | MrPingu | <PROTECTED> |
| 16:10.12 | MrPingu | <PROTECTED> |
| 16:10.13 | MrPingu | <PROTECTED> |
| 16:10.13 | DocScrutinizer05 | but yes, it's normal |
| 16:10.15 | MrPingu | I know |
| 16:10.24 | MrPingu | C1 normal? |
| 16:10.28 | DocScrutinizer05 | yep |
| 16:10.30 | *** join/#maemo hazchemix (~user@ip51ccb388.speed.planet.nl) |
| 16:10.34 | DocScrutinizer05 | if on charger |
| 16:10.58 | MrPingu | oh duh, it's on charger... |
| 16:11.10 | MrPingu | forget a little detail xD |
| 16:11.26 | DocScrutinizer05 | MrPingu: please deliver top 3 from powertop, not frpm ps |
| 16:11.48 | MrPingu | PID# | Activity | Name | Function Entry (Expire) |
| 16:11.50 | MrPingu | --------+------------+----------------+--------------------------- |
| 16:11.51 | *** join/#maemo valeriusM (~user@46.61.94.40) |
| 16:11.51 | MrPingu | <PROTECTED> |
| 16:11.53 | MrPingu | <PROTECTED> |
| 16:11.54 | MrPingu | <PROTECTED> |
| 16:12.20 | DocScrutinizer05 | duh, pretty little activity there |
| 16:12.57 | DocScrutinizer05 | I'm missing 0 | 270 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer) |
| 16:13.33 | DocScrutinizer05 | somebody thought it was a good idea to mess with nohz in PK51? |
| 16:14.34 | DocScrutinizer05 | err nevermind, it's third in your list |
| 16:15.10 | MrPingu | Seems device cooled down a bit... |
| 16:15.14 | DocScrutinizer05 | anyway for reboots, you should check dsme protocol |
| 16:15.59 | MrPingu | dsme wdd: Error reading R&D mode flags, WD kicking enabled |
| 16:16.00 | MrPingu | dsme wdd: Error opening WD /dev/twl4030_wdt: Device or resource busy |
| 16:16.02 | MrPingu | dsme wdd: Error opening WD /dev/watchdog: Device or resource busy |
| 16:16.04 | MrPingu | dsme wdd: no WD's opened; WD kicking disabled |
| 16:16.05 | MrPingu | dsme wdd: Entering main loop, with 12 s interval |
| 16:16.07 | MrPingu | is that normal? |
| 16:16.21 | Sicelo | how did you get that? |
| 16:16.35 | DocScrutinizer05 | not really I think |
| 16:16.35 | MrPingu | running dsme |
| 16:16.49 | DocScrutinizer05 | err, *running* dsme? |
| 16:17.10 | DocScrutinizer05 | please check /var/lib/dsme/stats/lifeguard_restarts |
| 16:18.07 | MrPingu | Nokia-N900:/var/lib/dsme/stats# cat lifeguard_restarts |
| 16:18.09 | MrPingu | /usr/bin/ohm-session-agent: 1 |
| 16:18.11 | MrPingu | /usr/sbin/alarmd.wrapper : 1 |
| 16:18.12 | MrPingu | /sbin/mce --force-syslog: 1 |
| 16:18.14 | MrPingu | /usr/bin/camera-ui: 2 |
| 16:18.16 | MrPingu | /usr/bin/mafw-dbus-wrapper mafw-gst-renderer: 1 |
| 16:18.18 | MrPingu | /usr/bin/hildon-home: 12 |
| 16:18.20 | MrPingu | /usr/bin/hildon-desktop: 3 |
| 16:18.21 | MrPingu | /usr/bin/osso-abook-home-applet: 13 |
| 16:18.23 | MrPingu | /usr/bin/hildon-status-menu: 18 |
| 16:18.25 | MrPingu | /usr/bin/systemui: 19 |
| 16:18.27 | MrPingu | /usr/sbin/browserd -d: 18 |
| 16:18.29 | MrPingu | /usr/bin/hildon-input-method: 1 |
| 16:18.53 | DocScrutinizer05 | not really relevant, just check what counted up after next faulty reboot |
| 16:19.04 | Sicelo | runniing dsme should give you those errors on an OK device. the watchdog is indeed busy (with first dsme instance) |
| 16:19.12 | DocScrutinizer05 | yep |
| 16:19.27 | DocScrutinizer05 | dsme isn't meant to get started twice |
| 16:19.41 | MrPingu | :) |
| 16:20.12 | DocScrutinizer05 | anyway I don't see any bme related reboots in your lifeguard_restarts |
| 16:20.14 | MrPingu | Now, if i remove the charger would it shutdown itself again? |
| 16:20.41 | DocScrutinizer05 | if it's on and active, it mustn't shut down on removing charger |
| 16:21.19 | MrPingu | Well it happend me thrice today, put phone away -> then come back phone off |
| 16:21.44 | MrPingu | That's how I ended up with this chat :P |
| 16:22.21 | Sicelo | if it's kernel, mos likely you should have a log in mtd2 iirc |
| 16:22.37 | DocScrutinizer05 | MrPingu: please check syslog |
| 16:22.52 | DocScrutinizer05 | and mtd2 as Sicelo suggests |
| 16:24.31 | MrPingu | Looked in mtd2 but didn't see anything special, at first glance |
| 16:24.42 | DocScrutinizer05 | MrPingu: search in syslog for last "syslogd 1.5.0#5maemo7+0m5: restart." |
| 16:25.01 | MrPingu | syslog, sorry where could I find that? |
| 16:25.02 | DocScrutinizer05 | see what's the last few lines *before* that |
| 16:25.12 | DocScrutinizer05 | /var/log/syslog |
| 16:25.24 | DocScrutinizer05 | if you have ksyslogd installed |
| 16:25.32 | MrPingu | nope |
| 16:25.38 | DocScrutinizer05 | too bad |
| 16:25.42 | DocScrutinizer05 | go install it |
| 16:25.49 | MrPingu | on my way sir |
| 16:25.55 | DocScrutinizer05 | :-) |
| 16:25.56 | MrPingu | tools or sdk repo? |
| 16:26.10 | DocScrutinizer05 | err, always tools if in question |
| 16:26.27 | MrPingu | Ah, une moment |
| 16:26.44 | DocScrutinizer05 | sysklogd - System Logging Daemon |
| 16:27.14 | DocScrutinizer05 | 500 https://downloads.maemo.nokia.com ./ Packages |
| 16:27.26 | DocScrutinizer05 | sysklogd: |
| 16:27.28 | DocScrutinizer05 | <PROTECTED> |
| 16:28.25 | DocScrutinizer05 | apt-get install sysklogd |
| 16:28.57 | DocScrutinizer05 | probably even in extras-devel |
| 16:29.05 | DocScrutinizer05 | or extras |
| 16:29.18 | MrPingu | I don't think so |
| 16:29.23 | MrPingu | couldn't find it :P |
| 16:29.24 | DocScrutinizer05 | or nokia core repo |
| 16:30.30 | DocScrutinizer05 | http://maemo.org/packages/view/sysklogd/ |
| 16:31.03 | DocScrutinizer05 | Fremantle nokia-applications explicit armel |
| 16:31.17 | MrPingu | Never heard of that repo |
| 16:31.20 | DocScrutinizer05 | Fremantle SDK free armel |
| 16:31.27 | MrPingu | Yeah, saw it |
| 16:31.33 | MrPingu | not in tools but sdk |
| 16:31.36 | DocScrutinizer05 | Fremantle SDK tools free armel |
| 16:32.06 | DocScrutinizer05 | Maemo 5 device SSU repository (>= PR1.2) |
| 16:32.07 | kerio | hm, i don't have nokia-applications |
| 16:32.33 | MrPingu | Me neither... |
| 16:32.55 | MrPingu | BTW, I see some kernel-panics in mtd2 |
| 16:33.01 | DocScrutinizer05 | just quoting http://maemo.org/packages/view/sysklogd/ |
| 16:33.09 | DocScrutinizer05 | :nod: |
| 16:33.28 | DocScrutinizer05 | do they have timestamps? |
| 16:33.42 | DocScrutinizer05 | so you could actually tell when they happened |
| 16:34.15 | MrPingu | No timestamps I believe |
| 16:34.24 | MrPingu | but they do have some numbers in front... |
| 16:34.46 | DocScrutinizer05 | yeah, alas there's no decent tool to read out mtdoops |
| 16:35.16 | DocScrutinizer05 | at least I'm not aware of any |
| 16:36.16 | DocScrutinizer05 | ability to read is a clear advantage ;-P |
| 16:36.19 | DocScrutinizer05 | http://maemo.org/packages/view/sp-oops-extract/ |
| 16:36.48 | MrPingu | Should I install that aswel? |
| 16:37.01 | DocScrutinizer05 | nfc, just this minute discovered it |
| 16:37.03 | DocScrutinizer05 | ;-D |
| 16:37.51 | MrPingu | Installing syslogd now |
| 16:38.24 | DocScrutinizer05 | ;-DIroN900:~# sp-oops-extract /dev/mtd2 |
| 16:38.35 | DocScrutinizer05 | looks somewhat decent |
| 16:39.20 | MrPingu | seems device is gone sane again |
| 16:39.33 | MrPingu | I mean, more than 10 min uptime now without charger :) |
| 16:41.10 | DocScrutinizer05 | *might* be trackerd hogging IO and thus causing system critical process to freeze which in turn triggers DSME lifeguard WD |
| 16:41.49 | MrPingu | might be, but I have lowmemorymode thicked + throttle to 10 |
| 16:41.54 | DocScrutinizer05 | but no idea how that naive explanation might fit into act_dead problem |
| 16:42.37 | MrPingu | Wakeups are still somewhat high |
| 16:42.40 | MrPingu | 7700 |
| 16:43.07 | DocScrutinizer05 | yeah, kinda high |
| 16:43.23 | DocScrutinizer05 | where from do you read those? |
| 16:43.58 | MrPingu | damn |
| 16:44.06 | MrPingu | if you are speaking of the devil... |
| 16:44.19 | MrPingu | screen went black |
| 16:44.27 | MrPingu | device off... |
| 16:44.45 | DocScrutinizer05 | now is the time of syslog |
| 16:45.02 | MrPingu | Installed at the right moment |
| 16:45.06 | DocScrutinizer05 | and comparing mtd2 to what it been before |
| 16:45.39 | MrPingu | it skips the dots... |
| 16:45.44 | DocScrutinizer05 | and checking dsme lifeguard reset stats |
| 16:45.47 | MrPingu | but asked for pin |
| 16:46.05 | MrPingu | hildon-home coming up :) |
| 16:46.09 | MrPingu | ls |
| 16:46.18 | MrPingu | whoops |
| 16:46.54 | MrPingu | Can't get to app launcher :o |
| 16:48.19 | DocScrutinizer05 | sorry, afk |
| 16:48.22 | DocScrutinizer05 | bbl |
| 16:48.47 | Estel_ | MrPingu, whats the problem? |
| 16:48.57 | Estel_ | I saw in backscroll, that it's something related to what I had? |
| 16:49.09 | Estel_ | merlin1991, ping |
| 16:49.21 | MrPingu | Just acting weird regarding battery, odd shutdowns |
| 16:49.30 | Estel_ | any problems in turning it on again? |
| 16:49.35 | MrPingu | sometimes |
| 16:49.37 | Estel_ | (other than empty battery, if it's the case) |
| 16:49.47 | Estel_ | symptoms? how it acts, when You can't turn it on? |
| 16:49.58 | MrPingu | act-dead mode |
| 16:50.11 | 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 all |
| 16:50.14 | MrPingu | or just reboots after the dots |
| 16:50.14 | Estel_ | hm |
| 16:50.25 | DocScrutinizer05 | MrPingu: please don't mess with flasher options to "fix" it |
| 16:50.38 | MrPingu | and random shutdowns while in maemo |
| 16:51.11 | 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-dead |
| 16:51.12 | MrPingu | DocScrutinizer05: Yes, sir! |
| 16:51.26 | Estel_ | in my case, it works well, but of cours,e doesn't help finding cause of problem |
| 16:51.40 | Estel_ | thats probably, why DocScrutinizer05 ask You for not doing it |
| 16:51.46 | MrPingu | I had an extremely high number of wakeups |
| 16:51.58 | MrPingu | ls |
| 16:52.08 | 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 again |
| 16:52.11 | Estel_ | yea, saw it |
| 16:52.16 | Estel_ | well, in my case, no additional wakeups |
| 16:52.39 | 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 way |
| 16:52.46 | MrPingu | DocScrutinizer05: Need to see my syslog? |
| 16:52.50 | Estel_ | although, multimeter doesn't show anything special on usb lines |
| 16:53.05 | Estel_ | and no other oddities during runtime. i've also, recently, did some crazy repair of Ir diode |
| 16:53.19 | Estel_ | that lead to short between battery + and ground, fixed later |
| 16:53.23 | MrPingu | Aug 26 18:53:03 Nokia-N900 kernel: [ 431.601623] HWRecoveryResetSGX: SGX Hardware Recovery triggere |
| 16:53.27 | MrPingu | syslog is full of that |
| 16:53.29 | Estel_ | shouldn't matter, but You can't filter out that something is still wrong |
| 16:53.39 | Estel_ | MrPingu, forward it to Pali, for sure |
| 16:53.47 | Estel_ | nothing like that in my syslog, at least for sure not spamming it |
| 16:53.57 | Estel_ | also, never heard about it from any kp51 user |
| 16:54.09 | Estel_ | DocScrutinizer05, BTw, if You are here, please, read my signature carefully, if you're reffering to it ;) |
| 16:54.26 | 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* that |
| 16:54.39 | 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) |
| 16:54.55 | Estel_ | thanks in advance ;) |
| 16:55.59 | *** join/#maemo beford (~beford@unaffiliated/beford) |
| 16:56.02 | Estel_ | merlin1991, ping ping ping |
| 16:56.44 | Estel_ | freemangordon, ping |
| 16:57.04 | *** join/#maemo Pali (~pali@unaffiliated/pali) |
| 16:57.24 | Estel_ | hey, Pali, MrPingu seems to have strange problems, that may be related to kp51 |
| 16:57.34 | Estel_ | might be* |
| 16:57.44 | Pali | describe it |
| 16:57.52 | Estel_ | <MrPingu> Aug 26 18:53:03 Nokia-N900 kernel: [ 431.601623] HWRecoveryResetSGX: SGX Hardware Recovery triggere |
| 16:57.56 | Estel_ | syslog full of that |
| 16:57.59 | Estel_ | battery dying very fast |
| 16:58.02 | Estel_ | many wakeups |
| 16:58.16 | Estel_ | +, just like with me, his device sometimes boot only in act_dead, despite being turned out by power button |
| 16:58.19 | MrPingu | Now several graphic parts fail too |
| 16:58.34 | Estel_ | but it's only one situation, where our symptoms are similalr - I don't have any problems *except* for act_dead |
| 16:58.38 | Estel_ | started with kp51 |
| 16:58.40 | Estel_ | probably |
| 16:58.53 | MrPingu | I mean statusmenu can't be loaded except for some distorted colors |
| 16:59.00 | Estel_ | I "fixed" it, temporary, by enabling rd flag force-power-button, so act_dead gtfo, but it's not "real" fix of course |
| 16:59.02 | Pali | flash 2.6.28 omap1 and see if it happends too |
| 16:59.17 | Pali | if not then it is not kernel related |
| 16:59.20 | MrPingu | Can't, I am on thumb |
| 16:59.23 | Estel_ | Pali, is there any change in kernel, that allows bq2415 to work properly? |
| 16:59.30 | Estel_ | and is in effect even, if bq2415 isn't loaded? |
| 16:59.56 | Pali | I did not look at bq2415x after v51 was released |
| 17:00.02 | Pali | no time now... |
| 17:00.11 | Estel_ | I know, i've reported tons of bugs against it in kp51 thread |
| 17:00.13 | Estel_ | understandable |
| 17:00.25 | Estel_ | but I'm only asking if during coding kp51, have You added something |
| 17:00.26 | Estel_ | in kernel |
| 17:00.43 | Estel_ | for bq2415, to allow it work properly, that is in effect even without this module loaded? |
| 17:01.08 | Estel_ | I'm trying to check if my act_dead problems are in any way indeed related to kp51 |
| 17:01.46 | Pali | use my RE getbootstate |
| 17:02.00 | Pali | and see if my getbootstate tell act_dead too |
| 17:02.06 | Estel_ | OK |
| 17:02.06 | Pali | and if yes, look at code why |
| 17:02.18 | Estel_ | where to expect logged output? |
| 17:02.19 | Pali | sorry, now going offline, bye |
| 17:02.22 | Estel_ | ok |
| 17:02.23 | Estel_ | see ya |
| 17:03.24 | DocScrutinizer05 | errr, using getbootstate during act_dead to see if it shows act_dead? ;-) |
| 17:03.51 | Estel_ | probably, he want me to check if his getboostate gets affected too |
| 17:03.52 | DocScrutinizer05 | well, that's just a tad tricky to accomplish |
| 17:03.55 | MrPingu | sylog shows two restarts |
| 17:03.58 | Estel_ | and if yes, it gives more debug info (I hope) |
| 17:04.11 | MrPingu | one failed |
| 17:04.20 | 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* that |
| 17:04.29 | MrPingu | and one normal with those fsckd graphics |
| 17:04.54 | MrPingu | Aug 26 18:44:17 Nokia-N900 ke_recv[1939]: prop_modified:1928: udi /org/freedesktop/Hal/devices/platform_slide modified button.state.value |
| 17:04.55 | MrPingu | Aug 26 18:44:27 Nokia-N900 cellular: csd[1334]: ISI_SMS .966735> ind_reg_status(): Net registration (ind) status:1 rc:0 |
| 17:04.57 | MrPingu | Aug 26 18:44:27 Nokia-N900 cellular: csd[1334]: ISI_SMS .970031> set_timeout(): Timeout 2253 s event type:-1 |
| 17:05.08 | *** join/#maemo sambo7 (b219f8ff@gateway/web/freenode/ip.178.25.248.255) |
| 17:05.21 | DocScrutinizer05 | then it has to be a kerrnel panic/oops |
| 17:05.42 | Estel_ | but why? never heard about someone else affected in such way |
| 17:05.46 | MrPingu | Aug 26 19:00:55 Nokia-N900 kernel: [ 903.265808] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:05.47 | MrPingu | Aug 26 19:00:55 Nokia-N900 kernel: [ 903.890838] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:05.49 | MrPingu | Aug 26 19:01:01 Nokia-N900 kernel: [ 909.453277] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:05.50 | Estel_ | maybe sent it to Pali via PM on TMO? |
| 17:06.07 | Estel_ | IRC is too loosy for such things, he won't read it, probably, if left here |
| 17:06.10 | MrPingu | Aug 26 18:59:47 Nokia-N900 kernel: [ 835.968933] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:06.12 | MrPingu | Aug 26 19:00:01 Nokia-N900 kernel: [ 849.937652] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:06.13 | MrPingu | Aug 26 19:00:12 Nokia-N900 kernel: [ 860.328216] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:06.15 | MrPingu | Aug 26 19:00:12 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 0->1, is_layout_active:0, ChangeSusp:TRUE |
| 17:06.17 | MrPingu | Aug 26 19:00:12 Nokia-N900 kernel: [ 861.195434] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:06.18 | MrPingu | Aug 26 19:00:13 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 1->0, is_layout_active:1, ChangeSusp:TRUE |
| 17:06.19 | DocScrutinizer05 | maybe this doesn't increase the amount of info it contains |
| 17:06.20 | MrPingu | Aug 26 19:00:14 Nokia-N900 kernel: [ 862.460937] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:06.21 | MrPingu | Aug 26 19:00:15 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 0->1, is_layout_active:0, ChangeSusp:TRUE |
| 17:06.22 | MrPingu | Aug 26 19:00:15 Nokia-N900 kernel: [ 864.132873] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:06.24 | MrPingu | Aug 26 19:00:16 Nokia-N900 kernel: [ 864.757965] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:06.24 | Estel_ | +q |
| 17:06.26 | MrPingu | Aug 26 19:00:18 Nokia-N900 kernel: [ 866.406433] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:06.27 | MrPingu | Aug 26 19:00:18 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 1->0, is_layout_active:1, ChangeSusp:TRUE |
| 17:06.29 | MrPingu | Aug 26 19:00:18 Nokia-N900 kernel: [ 866.804809] slide (GPIO 71) is now open |
| 17:06.30 | MrPingu | Aug 26 19:00:18 Nokia-N900 ke_recv[1754]: prop_modified:1928: udi /org/freedesktop/Hal/devices/platform_slide modified button.state.value |
| 17:06.31 | DocScrutinizer05 | MrPingu: please stop it! |
| 17:06.32 | MrPingu | Aug 26 19:00:19 Nokia-N900 kernel: [ 867.289276] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:06.33 | MrPingu | Aug 26 19:00:19 Nokia-N900 kernel: [ 867.914093] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:06.35 | MrPingu | Aug 26 19:00:19 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 0->1, is_layout_active:0, ChangeSusp:TRUE |
| 17:06.36 | MrPingu | Aug 26 19:00:20 Nokia-N900 kernel: [ 868.539215] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:06.37 | Estel_ | he can'ty it gor triggerred |
| 17:06.38 | MrPingu | Aug 26 19:00:20 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 1->0, is_layout_active:1, ChangeSusp:TRUE |
| 17:06.39 | MrPingu | Aug 26 19:00:21 Nokia-N900 kernel: [ 869.296936] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:06.41 | MrPingu | Aug 26 19:00:22 Nokia-N900 browserd[2095]: SET_ACTIVE:0x3f8060, 0->1, is_layout_active:0, ChangeSusp:TRUE |
| 17:06.42 | MrPingu | Aug 26 19:00:22 Nokia-N900 kernel: [ 870.961090] HWRecoveryResetSGX: SGX Hardware Recovery triggered |
| 17:06.44 | Estel_ | he pasted huge output |
| 17:06.44 | *** mode/#maemo [+o DocScrutinizer05] by ChanServ |
| 17:06.45 | MrPingu | my whole log is spammed |
| 17:06.47 | MrPingu | sorry |
| 17:06.48 | MrPingu | BRB |
| 17:06.49 | Estel_ | it got pasted line by line by his irc client |
| 17:06.50 | MrPingu | got 2 eat |
| 17:07.01 | Estel_ | MrPingu, ever heard about zerobin?:P |
| 17:07.04 | *** mode/#maemo [-o DocScrutinizer05] by ChanServ |
| 17:07.06 | Estel_ | or pastebin?:P |
| 17:07.36 | DocScrutinizer05 | MrPingu: you should make sure you got no undervolting, overclocking, and no smartreflex activated |
| 17:08.27 | DocScrutinizer05 | if those HWRecoveryResetSGX aren't triggered by any of those, odds are your device silicon is EOL |
| 17:08.55 | DocScrutinizer05 | (aka OC burnout, which of course can happen even without you ever doing OC, just way later) |
| 17:09.24 | DocScrutinizer05 | but hey, maybe it's thumb related |
| 17:09.34 | DocScrutinizer05 | also possible |
| 17:10.56 | DocScrutinizer05 | away for dinner too |
| 17:12.56 | 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 too |
| 17:13.00 | Estel_ | but don't worry, i' |
| 17:13.46 | 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 that |
| 17:13.56 | Estel_ | i.e. chances for such irreversible damage are loooow |
| 17:14.27 | Estel_ | I'm out for some sunday afternun fun, feel free to ping me, will answer later |
| 17:14.36 | Estel_ | BTw, merlin1991, my pings are still valid ;) |
| 17:18.58 | DocScrutinizer05 | btw merlin clearly stated he's not available until 1.9. |
| 17:21.03 | 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 before |
| 17:21.23 | kerio | for what it's worth, sometimes i get a silly graphical corruption, if i start doing things too quickly when the n900 is just booting |
| 17:21.33 | kerio | and that also prevents me from accessing the application launcher |
| 17:21.38 | kerio | rebooting fixes it |
| 17:21.39 | DocScrutinizer05 | and 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 " |
| 17:21.45 | kerio | it happened on two N900s |
| 17:24.26 | DocScrutinizer05 | pisses 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" |
| 17:25.38 | DocScrutinizer05 | kerio: yep, gfx resets are not all that uncommon, but they shouldn't happen too frequently |
| 17:26.02 | kerio | DocScrutinizer05: what causes them? |
| 17:26.23 | DocScrutinizer05 | nobody knows, or otherwise we already would've fixed them |
| 17:26.23 | kerio | just powervr silliness? |
| 17:26.39 | DocScrutinizer05 | probably some Si-Erratum |
| 17:27.02 | DocScrutinizer05 | some weird race condition occasionally hitting, on a hw level |
| 17:27.57 | DocScrutinizer05 | alas TI is far from disclosing all of those Si-Err, esp when there's no proper workaround/fix |
| 17:28.18 | *** join/#maemo pigeon (~pigeon@eth5284.nsw.adsl.internode.on.net) |
| 17:28.41 | kerio | fukken TI |
| 17:28.46 | DocScrutinizer05 | yep |
| 17:30.36 | DocScrutinizer05 | kerio: 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 operation |
| 17:30.41 | kerio | hehe |
| 17:30.59 | kerio | "sure, the engine sometimes locks up, but there's a fix, you just start it again" |
| 17:31.41 | DocScrutinizer05 | as long as that happens reliably and transparently in background, it's almost bearable |
| 17:32.36 | DocScrutinizer05 | I however don't see how gfx reboots could tear down or panic the whole linux core |
| 17:33.03 | kerio | fukken kernel-power? :P |
| 17:33.27 | DocScrutinizer05 | nah, KP isn't that bad |
| 17:33.50 | DocScrutinizer05 | just a lot of the patches included never have seen proper review and thorough tests |
| 17:35.12 | *** join/#maemo fuz_ (nobody@vau75-10-88-164-23-88.fbx.proxad.net) |
| 17:35.21 | DocScrutinizer05 | still 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) |
| 17:35.21 | *** join/#maemo hurbu (~hurbanza@78.134.59.78) |
| 17:36.29 | MrPingu | Back! |
| 17:36.49 | DocScrutinizer05 | maybe the kernel watchdog process for gfx isn't reentrant, so kernel OOPS when gfx 'segfaults' during wtachdog resetting it? |
| 17:38.01 | DocScrutinizer05 | MrPingu: [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] |
| 17:38.02 | DocScrutinizer05 | <PROTECTED> |
| 17:38.26 | kerio | DocScrutinizer05: ooh, could be smartreflex |
| 17:38.39 | kerio | iirc it's enabled by default since kernel-power... 50? 51? |
| 17:38.47 | freemangordon | DocScrutinizer05: HWRecoveryResetSGX was there since the begining of 201 |
| 17:38.48 | DocScrutinizer05 | sure thing. Nokia always told us SR is instable |
| 17:38.50 | freemangordon | 2010* |
| 17:39.01 | kerio | well, by default-ish |
| 17:39.03 | freemangordon | kerio: bullshit, SR is not enabled by default |
| 17:39.05 | kerio | it's in the "default" profile |
| 17:39.09 | DocScrutinizer05 | freemangordon: yep, I know, and already mentioned that |
| 17:39.17 | kerio | you have to set it to be the default |
| 17:39.37 | freemangordon | kerio: SR has nothing to do woth SGX, it is on completely different power bus |
| 17:39.41 | DocScrutinizer05 | freemangordon: [2012-08-26 19:25:38] <DocScrutinizer05> kerio: yep, gfx resets are not all that uncommon, but they shouldn't happen too frequently |
| 17:40.00 | freemangordon | kerio: in short, stop spreading FUD |
| 17:40.03 | kerio | k |
| 17:40.04 | freemangordon | DocScrutinizer05: yep |
| 17:40.23 | MrPingu | Reboot fixes those SGX errors |
| 17:40.23 | Lava_Croft | i see a question mark on kerio's line |
| 17:40.25 | Lava_Croft | and an iirc |
| 17:40.25 | DocScrutinizer05 | freemangordon: you're sure about that powerbus thing? *really* sure? |
| 17:40.30 | Lava_Croft | making it more of question than a statement |
| 17:40.32 | Lava_Croft | relax man |
| 17:40.38 | kerio | spreads more fud over a piece of bread and then eats it |
| 17:40.55 | freemangordon | and the only way to get rid of them is power off/on, a simple reboot won't help |
| 17:41.16 | freemangordon | DocScrutinizer05: not 100%, but near that value :) |
| 17:41.18 | MrPingu | I actually meant powercycle |
| 17:42.27 | DocScrutinizer05 | freemangordon: depending on hw circuitry incl PCB layout around twl4030 power regulator circuitry this assumption might be incorrect for N900 |
| 17:42.33 | freemangordon | DocScrutinizer05: BTW I think it is an issue in the driver , not silicon errata |
| 17:42.46 | DocScrutinizer05 | and maybe that's exactly why Nokia said SR is flawed by hw |
| 17:42.58 | freemangordon | DocScrutinizer05: well, I don;t think there is a way SGX and core to operate on one and the same voltage |
| 17:43.24 | MrPingu | Wakeups however are still insane high |
| 17:43.33 | freemangordon | as SGX frequency is constant ;) |
| 17:43.48 | MrPingu | 9463 - DMA |
| 17:43.48 | DocScrutinizer05 | no, but for example it's pretty easy to figure regulators for both are fed by same power rail so interference is quite possible |
| 17:43.55 | *** join/#maemo florian (~fuchs@sign-4db6bdd5.pool.mediaWays.net) |
| 17:43.55 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 17:44.12 | freemangordon | could be, but SR does not change that |
| 17:44.15 | MrPingu | 2600 - mmc1 |
| 17:44.43 | DocScrutinizer05 | sure it does, it changes settings for one regulator and thus might cause interference to the other |
| 17:45.10 | freemangordon | DocScrutinizer05: the same does OPP control even without SR |
| 17:45.35 | DocScrutinizer05 | maybe SR does more 'agressive' changes to regulator settings than non-SR OPP settings do |
| 17:46.15 | freemangordon | well, this is too "maybe" so my bets are on a simple bug in the driver :) |
| 17:46.24 | DocScrutinizer05 | quite tricky to rule out anything along that line |
| 17:46.42 | DocScrutinizer05 | possible, even probable |
| 17:46.43 | freemangordon | having in mind we have the same behaviour it stock kernel too |
| 17:46.46 | MrPingu | What is exactly DMA and why is it taking so much wakeups? |
| 17:46.59 | freemangordon | direct memory access |
| 17:47.10 | DocScrutinizer05 | good question, since mine isn't that spammy |
| 17:47.26 | DocScrutinizer05 | might be your PC to USB |
| 17:47.36 | DocScrutinizer05 | IOW usb data transfer |
| 17:47.37 | MrPingu | uhm |
| 17:47.44 | MrPingu | I am not attached to pc |
| 17:47.51 | DocScrutinizer05 | ooh, nfc then |
| 17:48.13 | DocScrutinizer05 | trackerd accessing eMMC? no idea |
| 17:48.15 | MrPingu | me neither, im not as guru as you guys are :P |
| 17:48.28 | *** join/#maemo valeriusM (~user@95.153.189.21) |
| 17:49.02 | DocScrutinizer05 | basically DMA isn't an autonomous process, it needs some (linux) process to control it |
| 17:49.25 | DocScrutinizer05 | this linux process should show up un ps and/or (power)top |
| 17:50.23 | DocScrutinizer05 | freemangordon: (same behaviour) not a few dozen or even hundereds of gfx resets during >10 min |
| 17:50.34 | DocScrutinizer05 | at least I've never seen that |
| 17:51.11 | DocScrutinizer05 | <10min* |
| 17:51.18 | MrPingu | Do the gurus need some data from my device or else I am going to reflash |
| 17:51.46 | MrPingu | I need to have my device in a working state before tomorrow :P |
| 17:51.50 | DocScrutinizer05 | umm, wait another 5 min please. Even _my_ brain needs time to complete evaluations ;-) |
| 17:52.36 | MrPingu | Sure, you got 2 hours ;) |
| 17:52.51 | MrPingu | flashing doesn't take that long... |
| 17:52.55 | DocScrutinizer05 | at least save syslog and sp-oops-extract |
| 17:53.16 | DocScrutinizer05 | and a complete output of powertop |
| 17:53.24 | freemangordon | MrPingu: one question, how did this start? |
| 17:53.29 | freemangordon | out of the blue? |
| 17:53.31 | MrPingu | NFC |
| 17:53.35 | MrPingu | yes out of the blue |
| 17:53.50 | freemangordon | did you try to remove the battery? |
| 17:53.59 | MrPingu | I even swapped batteries |
| 17:54.03 | DocScrutinizer05 | [2012-08-26 17:40:20] <MrPingu> Well, let's tell the story from the start |
| 17:54.04 | DocScrutinizer05 | [2012-08-26 17:40:40] <MrPingu> Yesterday night went to bed, woke up this morning -> Everything fine |
| 17:54.05 | DocScrutinizer05 | [2012-08-26 17:41:04] <MrPingu> from 8 am to 12 it worked nicely |
| 17:54.07 | DocScrutinizer05 | [2012-08-26 17:41:18] <MrPingu> then I wanted to check time around 14:00 |
| 17:54.08 | DocScrutinizer05 | [2012-08-26 17:41:32] <MrPingu> phone not responding, battery dead |
| 17:54.10 | DocScrutinizer05 | [ |
| 17:54.13 | kerio | oh god paste |
| 17:54.15 | freemangordon | thanks |
| 17:54.40 | MrPingu | Yeah suddenly it had an flat battery |
| 17:54.46 | MrPingu | swapped it for a full one |
| 17:55.06 | MrPingu | but then I kept shutdowns within 10 mins |
| 17:55.21 | DocScrutinizer05 | sorry guys, I really need to care about my dinner now |
| 17:55.25 | freemangordon | hmm, so you don't have any idea if rootfs is nog corrupted |
| 17:55.36 | MrPingu | nope |
| 17:55.43 | DocScrutinizer05 | df -h |
| 17:56.02 | freemangordon | leading to some broken graphics file which h-d or h-h tries to load in SGX |
| 17:56.13 | freemangordon | MrPingu: did you try to change the theme? |
| 17:56.18 | DocScrutinizer05 | quite a good story indeed |
| 17:56.21 | MrPingu | Not yet |
| 17:56.39 | zeq1 | hey freemangordon :) |
| 17:56.47 | DocScrutinizer05 | hey zeq1 |
| 17:56.50 | freemangordon | you can also try to delete application snapshots |
| 17:56.55 | zeq1 | Hi DocScrutinizer05 |
| 17:56.58 | freemangordon | hi zeq1 |
| 17:57.21 | MrPingu | where? |
| 17:57.26 | DocScrutinizer05 | quite a good story indeedmrplease do a proper BM backup |
| 17:57.35 | freemangordon | MrPingu: /home/user/.cache/launch |
| 17:57.36 | DocScrutinizer05 | errrrr :-( |
| 17:57.48 | DocScrutinizer05 | MrPingu: please do a proper BM backup |
| 17:58.03 | DocScrutinizer05 | and safe it off the phone |
| 17:58.11 | DocScrutinizer05 | save* |
| 17:58.17 | MrPingu | I have a properbackup of 17 aug and one of 25 aug on my pc |
| 17:58.19 | freemangordon | going afk for a while |
| 17:58.26 | MrPingu | so yesterday |
| 17:58.36 | DocScrutinizer05 | do one of the current state, with backupmenu |
| 17:59.14 | MrPingu | Yes, will say when it's done ;) |
| 17:59.23 | MrPingu | If some other steps are needed |
| 17:59.41 | DocScrutinizer05 | add syslog and sp-oops-extract and powertop |
| 18:00.06 | *** join/#maemo sambo7 (b219f8ff@gateway/web/freenode/ip.178.25.248.255) |
| 18:00.24 | DocScrutinizer05 | this should allow forensic analysis later |
| 18:01.19 | DocScrutinizer05 | then I suggest you reflash and test with standard config |
| 18:01.23 | MrPingu | Now I start wondering if my backup of yesterday might be affected |
| 18:01.51 | DocScrutinizer05 | o/ |
| 18:02.52 | MrPingu | I remember my phone was extremely hot while backup'ing |
| 18:04.21 | DocScrutinizer05 | nah |
| 18:04.37 | DocScrutinizer05 | probably unrelated |
| 18:04.47 | MrPingu | DocScrutinizer05: Standard config, you mean omap kernel, and no CSSU? |
| 18:04.56 | DocScrutinizer05 | yep, please |
| 18:05.07 | freemangordon | well, most probably some resource file (icon, .pvr, pcx, ) got corrupted |
| 18:05.22 | DocScrutinizer05 | then reinstall step by step, and see if you can spot what causes the effect |
| 18:05.48 | freemangordon | DocScrutinizer05: let him try to clean .pvr cache and change the theme, it is a matter of seconds to be done |
| 18:05.53 | DocScrutinizer05 | freemangordon: might we detect that somehow? |
| 18:06.08 | freemangordon | ^^^ |
| 18:06.24 | DocScrutinizer05 | e.g by comparing *.pvr of old and fresh install |
| 18:06.26 | MrPingu | Right now backup'ing so can't do anything else... |
| 18:06.45 | freemangordon | DocScrutinizer05: .pvr is done on-the-fly by h-d |
| 18:06.47 | DocScrutinizer05 | freemangordon: up to you :-) |
| 18:07.02 | freemangordon | this is a part of smoke-and-mirror :) |
| 18:07.02 | DocScrutinizer05 | :nod: |
| 18:07.39 | freemangordon | and actually is a maemo specific hack in clutter |
| 18:08.11 | freemangordon | plus some SGX extension in GLES2 |
| 18:08.18 | *** join/#maemo alehorst (~alehorst@177.16.36.166) |
| 18:08.30 | freemangordon | hacky all the way, so that could be a reason |
| 18:08.50 | MrPingu | Want me to do an eMMC flash too? |
| 18:08.55 | 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_dead |
| 18:09.32 | DocScrutinizer05 | MrPingu: eMMC most likely unrelated, so no |
| 18:09.43 | freemangordon | well, .pvr cache is on eMMC |
| 18:09.55 | DocScrutinizer05 | hmm, deleting it should suffice |
| 18:09.58 | freemangordon | "/home/user/.cache/launch" |
| 18:10.09 | freemangordon | iirc that is the only place |
| 18:10.12 | DocScrutinizer05 | rm /home/user/.cache/launch/* |
| 18:10.24 | MrPingu | Get it |
| 18:10.47 | DocScrutinizer05 | no need to flash whole eMMC first instance |
| 18:10.48 | MrPingu | One advantage, now I can use your apt-get wrapper from the start :P |
| 18:10.58 | DocScrutinizer05 | cya |
| 18:11.00 | DocScrutinizer05 | :-D |
| 18:11.28 | MrPingu | Are you going? Bye! |
| 18:15.38 | *** join/#maemo aloril (~aloril@84.249.126.153) |
| 18:15.47 | MrPingu | Yes, something is wrong for sure |
| 18:15.55 | MrPingu | maybe fscked rootfs |
| 18:16.07 | freemangordon | most probably :( |
| 18:16.24 | MrPingu | let me take a pic |
| 18:17.57 | MrPingu | on boot it shows missing images and such |
| 18:18.10 | freemangordon | hehe |
| 18:18.38 | MrPingu | same problem I got with a fake digitizer/frontcover |
| 18:22.26 | MrPingu | http://imgur.com/GXp6N |
| 18:23.03 | freemangordon | MrPingu: well, well, defffinitely your fottfs is corrupted :( |
| 18:23.10 | freemangordon | damn |
| 18:23.17 | freemangordon | rootfs that is |
| 18:23.41 | MrPingu | Note: this image problem is the first time I got this |
| 18:24.03 | MrPingu | I mean I have booted more than once today and I needed to load this screen because battery swap |
| 18:24.07 | freemangordon | anything suspicious in dmesg log? |
| 18:24.17 | freemangordon | related to NAND |
| 18:24.48 | MrPingu | How to read whole dmesg log? |
| 18:24.56 | freemangordon | zeq1: any progress with ipclite? |
| 18:25.06 | freemangordon | MrPingu: dmesg |
| 18:25.10 | MrPingu | I mean i can't go further up on busybox |
| 18:25.29 | freemangordon | dmesg > you_name_it.log |
| 18:26.23 | DocScrutinizer05 | freemangordon: he got syslog meanwhile |
| 18:26.44 | DocScrutinizer05 | syslog >=dmsg |
| 18:27.06 | freemangordon | yes, too noisy :) |
| 18:27.07 | MrPingu | I see mtdoops isn dmesg |
| 18:27.28 | freemangordon | care to pastebin? |
| 18:31.28 | DocScrutinizer05 | MrPingu: just unrelated "pro-tip": dmesg|less |
| 18:31.56 | MrPingu | pastebin.com/nWjH4dq3 |
| 18:32.51 | MrPingu | DocScrutinizer05: Thanks |
| 18:33.29 | freemangordon | hmm, no SGX restarts now your images are missing :P |
| 18:33.52 | MrPingu | SGX issue was fixed after powercycle |
| 18:34.55 | DocScrutinizer05 | please pastebin sp-oops-decode /dev/mtd2 |
| 18:35.51 | DocScrutinizer05 | errr sp-oops-extract |
| 18:36.43 | freemangordon | DocScrutinizer05: makes no sense, his rootfs is FUBAR |
| 18:37.02 | DocScrutinizer05 | probably you're right |
| 18:37.05 | freemangordon | 21:20 <MrPingu> http://imgur.com/GXp6N |
| 18:37.09 | freemangordon | DocScrutinizer05: ^^^ |
| 18:37.32 | MrPingu | Yes, it is :( |
| 18:37.33 | DocScrutinizer05 | :nod: |
| 18:38.07 | MrPingu | Rootfs, I have always treated you very nice. How dare you do this to me? :'( |
| 18:38.10 | *** join/#maemo valeriusM (~user@85.26.180.158) |
| 18:38.24 | freemangordon | MrPingu: you can check if your battery is loose, that caused me (and other people) lots of problems |
| 18:38.41 | MrPingu | http://pastebin.com/nPUHRDk1 |
| 18:38.47 | freemangordon | restarts/power-offs out of the blue |
| 18:38.48 | 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_dead |
| 18:39.04 | freemangordon | cleaning won't help, he has to extend the springs |
| 18:39.13 | DocScrutinizer05 | :nod: |
| 18:39.45 | MrPingu | battery isn't loose |
| 18:40.23 | DocScrutinizer05 | check your battery's contacts. You see bumps like half spheres. Do they touch each other? |
| 18:40.52 | DocScrutinizer05 | well, sorry I'm afk again |
| 18:41.03 | freemangordon | MrPingu: which kernel do you use? |
| 18:41.10 | MrPingu | cssu3 |
| 18:41.45 | freemangordon | well, the last kernel opps is from KP47 :D |
| 18:41.47 | MrPingu | Yes I see these bumps, they don't touch |
| 18:41.59 | MrPingu | Are u sure? |
| 18:42.08 | freemangordon | according to the log |
| 18:42.13 | freemangordon | lemme check once again |
| 18:42.31 | MrPingu | logs are saved through reflahs? |
| 18:42.45 | MrPingu | don't believe that ;p |
| 18:43.12 | MrPingu | last reflash was in may, KP49 atleast I think |
| 18:43.33 | MrPingu | Got sane wakeups too now |
| 18:43.38 | MrPingu | 3000 |
| 18:43.51 | freemangordon | "/dev/mtd2" is not flashed |
| 18:44.12 | MrPingu | Doesn't it get emptied? |
| 18:44.12 | freemangordon | MrPingu: yes, the last kernel oops is from KP47 |
| 18:44.16 | freemangordon | no |
| 18:44.35 | freemangordon | it is a circular buffer |
| 18:44.46 | freemangordon | some kind of :) |
| 18:44.52 | teotwaki__ | pretty insane: http://www.youtube.com/watch?v=1zXwOoeGzys |
| 18:46.17 | MrPingu | it's not a kernel bug then ;) |
| 18:47.50 | MrPingu | It sucks I need a reflash though |
| 18:48.10 | freemangordon | MrPingu: well, it is |
| 18:48.18 | MrPingu | it is? |
| 18:48.28 | freemangordon | just doesn't result in oops |
| 18:48.34 | freemangordon | https://bugs.maemo.org/show_bug.cgi?id=9150 |
| 18:48.35 | povbot_ | 04Bug 9150: Device doesn't respond via UI. syslog reports HWRecoveryResetSGX: SGX Hardware Recovery triggered, sgx_misr eating all CPU |
| 18:48.47 | freemangordon | a pretty old one :) |
| 18:48.52 | MrPingu | :( |
| 18:49.33 | freemangordon | it took Nokia 2 years or so to mark it WONTFIX ;) |
| 18:50.13 | MrPingu | and now I am hit by it -.- |
| 18:50.46 | freemangordon | you are hit by a corrupted fs triggering the bug :P |
| 18:51.28 | MrPingu | idc, it comes both down to an reflash ;p |
| 18:52.08 | MrPingu | Do you think it's safe to restore yesterday's BM backup or is it possible that contains the corruption? |
| 18:52.09 | freemangordon | yes "( |
| 18:52.24 | freemangordon | well, it worths nothing to try it |
| 18:52.35 | freemangordon | afaik, as I never used BM |
| 18:52.53 | MrPingu | Me neither, actually |
| 18:53.06 | freemangordon | better ask doc ;) |
| 18:53.26 | freemangordon | he is BM fan and can help you |
| 18:53.32 | MrPingu | He said it was safe ;) |
| 18:53.42 | freemangordon | well, go on then :) |
| 18:53.58 | DocScrutinizer05 | BM doesn't mkfs |
| 18:54.13 | DocScrutinizer05 | so all you do is replace files via 'cp' |
| 18:54.40 | DocScrutinizer05 | if actually fs is corrupted, a BM restore without prior flashj won't help |
| 18:55.10 | zeq1 | freemangordon: 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. |
| 18:55.16 | DocScrutinizer05 | a restore after flash can't cause additional damage though, beyond wasted time to do all flashing again |
| 18:55.32 | freemangordon | zeq1: did you ask romaxa? |
| 18:56.02 | MrPingu | You say *additional* :P |
| 18:56.23 | zeq1 | brb |
| 18:56.34 | DocScrutinizer05 | well, you might restore files that got messed up/corrupted |
| 18:56.41 | kerio | BM should really mkfs |
| 18:56.54 | kerio | i mean, the ubifs |
| 18:56.55 | DocScrutinizer05 | indeed it should have an option for that |
| 18:57.09 | DocScrutinizer05 | at least BM can run fsck |
| 18:57.22 | DocScrutinizer05 | but I guess that's useless on ubifs |
| 18:57.26 | kerio | attach the ubi volume, mkfs.ubifs |
| 18:58.50 | DocScrutinizer05 | I still fail to grok why system reboots after 10 minutes |
| 18:59.04 | MrPingu | (or less) |
| 18:59.30 | DocScrutinizer05 | suspects fs corruption not being the root cause of the problem, but maybe rather a consequence |
| 18:59.48 | freemangordon | DocScrutinizer05: hmm, maybe I am wrong https://bugs.maemo.org/show_bug.cgi?id=7017#c17 |
| 18:59.50 | povbot_ | 04Bug 7017: SGX memory reset seems failed during reboot |
| 19:00.11 | freemangordon | though besides the statement, there is no real info |
| 19:01.30 | freemangordon | DocScrutinizer51: some WD is kicking, dsme most probably |
| 19:01.47 | *** join/#maemo jhb (~joerg@tmo-097-26.customers.d1-online.com) |
| 19:02.06 | *** join/#maemo hardaker (~hardaker@mail.hardakers.net) |
| 19:02.28 | freemangordon | afaik after n tries in x seconds, if a process still fails to start, dsme reboots the device |
| 19:02.48 | freemangordon | fails to start as crashes :D |
| 19:02.53 | zeq1 | freemangordon: 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. |
| 19:03.26 | MrPingu | Note: I got no reboots |
| 19:03.37 | MrPingu | it's just the device wasn't "on" anymore |
| 19:03.46 | MrPingu | sometimes it booted to act-dead |
| 19:03.51 | MrPingu | sometimes it booted normal |
| 19:03.59 | freemangordon | zeq1: 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 :P |
| 19:04.07 | MrPingu | but when it booted normal it insane number of wakeups |
| 19:04.21 | freemangordon | MrPingu: you have loose battery |
| 19:04.27 | freemangordon | I can bet on that |
| 19:04.55 | zeq1 | Ah yes, did I not make them available? |
| 19:05.13 | zeq1 | I've still not had any problems fwiw |
| 19:05.16 | freemangordon | the only way n900 to power-off out of the blue is through bad battery connection |
| 19:05.36 | freemangordon | zeq1: don't remember, it was 2-3 weeks ago :D |
| 19:06.11 | freemangordon | zeq1: anyway, I will pester you starting from tomorrow :P |
| 19:06.36 | zeq1 | ok :) |
| 19:06.42 | freemangordon | merlin1991 needs a proper .deb for toolchain ;) |
| 19:06.52 | freemangordon | 4.7.2 I mean |
| 19:07.05 | zeq1 | I'd better get back to my gf, been busy decorating all day, lazy evening... |
| 19:07.21 | freemangordon | yeah, not a bad idea |
| 19:07.27 | kerio | freemangordon: or by battery brownout |
| 19:07.35 | zeq1 | freemangordon: native toolchian deb or host (cross) toolchain deb |
| 19:07.42 | kerio | (if you screw with bme) |
| 19:07.42 | freemangordon | zeq1: cross |
| 19:07.55 | zeq1 | ok |
| 19:08.01 | freemangordon | the one installable in OS, not in SB |
| 19:08.24 | zeq1 | I need to build the new one anyway |
| 19:08.44 | freemangordon | or even better something similar to original SB installer (python one) |
| 19:08.48 | freemangordon | zeq1: why? |
| 19:09.08 | zeq1 | why use the latest Linaro? |
| 19:09.14 | zeq1 | bug fixes :) |
| 19:09.35 | freemangordon | hmm, I missed "the latest Linaro" part :P |
| 19:10.03 | freemangordon | zeq1: but better keep 4.7.2 |
| 19:10.12 | MrPingu | freemangordon: IDK, battery doesn't seem to be loose |
| 19:10.26 | freemangordon | MrPingu: well, NFC then |
| 19:10.32 | zeq1 | yes, that's the Linaro "stable" version (anyway afk for a while) |
| 19:11.01 | MrPingu | Reflashing now, and moving on... |
| 19:13.42 | *** join/#maemo wicket64 (~wicket@81-86-240-143.dsl.pipex.com) |
| 19:19.21 | DocScrutinizer05 | MrPingu: you say the spheres of battery springs don't touch. They should though (at least almost) |
| 19:19.48 | *** join/#maemo niwakame|away (hashtag@ircbouncer.eu) |
| 19:21.27 | DocScrutinizer05 | well, not actually touch, but a tiny bit too large a gap between them will cause poor contact to the blades of N900 |
| 19:22.36 | DocScrutinizer05 | It'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 weak |
| 19:24.50 | DocScrutinizer05 | anyway, 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!) |
| 19:25.19 | DocScrutinizer05 | o/ |
| 19:29.36 | teotwaki__ | bloody hell, I hate it when my credit card bounces |
| 19:30.10 | teotwaki__ | I'm stuck without food tonight, because for some unknown reason, the bank decided to refuse any transaction. |
| 19:31.57 | kerio | >tracked money |
| 19:32.00 | kerio | mfw |
| 19:32.46 | *** join/#maemo qwazix (~qwazix@athedsl-351601.home.otenet.gr) |
| 19:37.23 | *** join/#maemo sambo7 (b219f8ff@gateway/web/freenode/ip.178.25.248.255) |
| 19:40.47 | *** join/#maemo krayon (~fallen@pdpc/supporter/28for7/krayon) |
| 19:47.24 | MrPingu | DocScrutinizer, well that's just the case. Was about to write I can't see if they touch. Almost none space between them ;) |
| 19:48.02 | MrPingu | Sending cmt-mcusw image (5826 kB)... |
| 19:48.03 | MrPingu | 100% (5826 of 5826 kB, avg. 7970 kB/s) |
| 19:48.05 | MrPingu | Sending request 0x14 failed: Invalid or incomplete multibyte or wide character |
| 19:48.06 | MrPingu | Flashing cmt-mcusw... Sending request 0x50 failed: Protocol error |
| 19:48.15 | MrPingu | WTF for problem do we have now? :( |
| 19:48.27 | teotwaki__ | kerio: tell me about it |
| 19:49.15 | kerio | lrn2cash and bitcoins |
| 19:49.19 | kerio | which are about the same thing |
| 19:49.29 | kerio | actually, bitcoins are even *less* traceable |
| 19:50.02 | *** join/#maemo |thunder (~e@c-68-42-120-238.hsd1.mi.comcast.net) |
| 19:53.57 | *** join/#maemo bsdmaniak (~bsdmaniak@std93-20-88-120-139-80.fbx.proxad.net) |
| 19:53.58 | *** join/#maemo dhbiker (~dhbiker@APN-122-175-252-gprs.simobil.net) |
| 19:54.15 | MrPingu | md5sums match |
| 19:57.05 | teotwaki__ | kerio: lol, I'll be damned if I get conned in one of does stupid pyramid schemes |
| 19:57.22 | kerio | teotwaki__: like the US dollar? |
| 19:57.41 | teotwaki__ | kerio: and sorry, but the whole "traceable" thing, I LOL when I see the first "bitcoin credit card" on /.. |
| 19:57.49 | MrPingu | nvm, other USB connection saved it |
| 20:24.36 | *** join/#maemo perlite (~perlite@114-25-195-123.dynamic.hinet.net) |
| 20:29.38 | *** join/#maemo atlas (~atlas@kurios.r4780y.com) |
| 20:31.33 | DocScrutinizer05 | I thought bitcoin is zombibied meanwhile |
| 20:32.02 | DocScrutinizer05 | or gone down like Reichmarks |
| 20:32.31 | MrPingu | ~jrtools |
| 20:32.31 | infobot | somebody said jrtools was http://wiki.maemo.org/User:Joerg_rw/tools |
| 20:36.38 | MrPingu | BRB |
| 20:40.56 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 20:47.23 | *** join/#maemo Venusaur (~desu@wikipedia/Antonio-Lopez) |
| 20:49.11 | *** join/#maemo kodomo_ (~gregor@f052068064.adsl.alicedsl.de) |
| 20:49.55 | sambo7 | hi nandtester here |
| 20:50.02 | kerio | hi sambo7 |
| 20:50.18 | sambo7 | FINALLY I was able to revive my device:-) |
| 20:50.21 | kerio | neat |
| 20:50.22 | kerio | how? |
| 20:50.58 | sambo7 | 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 |
| 20:51.30 | sambo7 | cold flashing didn't work for me |
| 20:51.47 | sambo7 | at least what is described in the tutorial |
| 20:52.37 | Sicelo | looks like cold-flashing to me |
| 20:52.40 | sambo7 | and flasher-3.5 -h RX-51:2101 -F <fiasco_image> -c -S usb |
| 20:52.45 | Sicelo | what was the problem btw? |
| 20:52.47 | sambo7 | didn't work either |
| 20:53.11 | sambo7 | I nandtested mtd0-mtd5 |
| 20:53.53 | sambo7 | I also was trying to use Nokia phoenix...cold flashing was ok,but warm flashing failed |
| 20:54.17 | sambo7 | in the beginning I was always using the global image |
| 20:55.16 | sambo7 | but a few days ago I remembered that I have a device from Englang and I started to use the English image |
| 20:55.29 | sambo7 | don't know if this made a difference |
| 20:56.01 | Sicelo | nice. i think someone else had tol use a 'localized' image a while back |
| 20:56.21 | Sicelo | phoenix didn't need some special cable? |
| 20:56.39 | DocScrutinizer05 | if coldflash restores CAL, then for sure localization matters |
| 20:57.46 | DocScrutinizer05 | btw >>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 -f |
| 20:57.58 | DocScrutinizer05 | err, mompls |
| 20:58.07 | DocScrutinizer05 | yeah |
| 20:59.08 | DocScrutinizer05 | and actually if coldflashing fails, the hw build revision might matter |
| 20:59.31 | DocScrutinizer05 | iirc you only took a shot into the blue with 2101 |
| 20:59.33 | sambo7 | I have a lot of errors when I run dmesg |
| 20:59.56 | *** join/#maemo MrPingu (~MrPingu@86.92.226.97) |
| 21:00.01 | sambo7 | hw-revision could not be read |
| 21:00.29 | DocScrutinizer05 | sure, since it's in CAL |
| 21:00.29 | sambo7 | Found device RX-51, hardware revision 0000 |
| 21:01.02 | sambo7 | I got the error messages when flashing |
| 21:01.04 | sambo7 | Bootloader error log follows: ERROR: invalid header magic at addr 0x00000000: c0911a26 ERROR: invalid header magic at addr 0x00000000: ce9fb9e6 ERROR: Error processing request, stalling ERROR: EP0 STALL sent Error getting version of 'sw-release' Overriding revision information given by board. |
| 21:01.15 | Sicelo | phoenix didn't need some special cable? |
| 21:01.48 | DocScrutinizer05 | phoenix can do what flasher does |
| 21:01.51 | DocScrutinizer05 | via USB |
| 21:01.54 | DocScrutinizer05 | not more |
| 21:02.17 | DocScrutinizer05 | for anything beyond, you need special 'cable' |
| 21:02.33 | Sicelo | ah. |
| 21:02.55 | Sicelo | still wishes to revive his WSOD-stricken N-Gage |
| 21:03.01 | sambo7 | I found some tutorial in youtube & tried it...but I guess that like in flasher only the first part of the cold flashing was successful |
| 21:03.04 | kerio | :c |
| 21:03.23 | kerio | sambo7: your n900 will probably malfunction, though |
| 21:03.49 | kerio | a bunch of informations were lost |
| 21:04.00 | kerio | even if you bring it back to life |
| 21:04.09 | sambo7 | I guess,it will... |
| 21:04.46 | sambo7 | I already got some CAL errors messages in terminal... |
| 21:05.53 | sambo7 | and when I go on product info I get Nokia N900 <unknown> & Version:<unknown> |
| 21:06.54 | kerio | well, at least it fails gracefully |
| 21:06.56 | kerio | does the phone work? |
| 21:07.27 | sambo7 | haven't treid it yet... |
| 21:07.46 | Sicelo | sambo7: i also have version unknown for product info |
| 21:07.49 | Sicelo | :( |
| 21:08.13 | kerio | Sicelo: on your n-gage? |
| 21:09.12 | Sicelo | N900 |
| 21:09.23 | *** join/#maemo alehorst (~alehorst@177.16.36.166) |
| 21:10.09 | DocScrutinizer05 | sambo7: so probably time to try restoring CAL from an image, with nandwrite |
| 21:10.48 | sambo7 | is nandwrite part of the mtd-tools? |
| 21:10.50 | kerio | the phone should really not work |
| 21:10.51 | Sicelo | kerio: i have an N-Gage that no shop here can flash. i have N900 too, and another working N-Gage :P |
| 21:10.53 | DocScrutinizer05 | yep |
| 21:10.54 | sambo7 | pre-installed? |
| 21:11.34 | DocScrutinizer05 | there's nandread/write and there's mtd_debug |
| 21:11.50 | DocScrutinizer05 | for sure not preinstalled though |
| 21:12.34 | sambo7 | will test if phone works first |
| 21:12.36 | *** join/#maemo livelace (~livelace@62.192.242.235) |
| 21:12.41 | sambo7 | wifi is working |
| 21:15.24 | DocScrutinizer05 | well, sure you may test if phone works, but in the end you want to try and restore CAL somehow, since it can't get worse than it's now |
| 21:16.20 | *** join/#maemo Darkchaos (~darkchaos@i59F7A8F8.versanet.de) |
| 21:16.27 | DocScrutinizer05 | and at very least hw-version should get set to some sane value - otherwise you might expect problems on every simple reflash |
| 21:17.43 | DocScrutinizer05 | maybe you could find out about your hw revision via the device's serial number |
| 21:18.41 | DocScrutinizer05 | or with even more luck, hw rev is stored to modem filesystem as well |
| 21:19.01 | DocScrutinizer05 | and you *might* find out about it via pnatd |
| 21:19.36 | DocScrutinizer05 | (just handwaving, I never checked what you could find out from modem regarding hw rev) |
| 21:22.18 | sambo7 | @Doc ... maybe you can give me some support on which commands to use in the terminal to advance... |
| 21:26.03 | *** join/#maemo MrPingu (~MrPingu@86.92.226.97) |
| 21:27.07 | *** join/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 21:28.54 | *** join/#maemo cyborg-o1e (~cyborg-on@79-140-0-93.broadband.tenet.odessa.ua) |
| 21:30.13 | sambo7 | sorry,have to quit for now...maybe I'll be back later or tomorrow |
| 21:30.14 | sambo7 | bye |
| 21:32.54 | *** join/#maemo bullx (~ircchatte@117.136.5.150) |
| 21:33.22 | bullx | hello everybody |
| 21:33.57 | bullx | I am a N9 user |
| 21:34.24 | *** join/#maemo zeq1 (~s_j_newbu@cpc19-rdng21-2-0-cust106.15-3.cable.virginmedia.com) |
| 21:34.28 | bullx | resently i try to write some script |
| 21:35.04 | bullx | i want it auto run after system startup |
| 21:35.44 | bullx | but i can't find the rc.local file |
| 21:36.21 | Sicelo | #harmattan |
| 21:36.33 | bullx | is N9 has some after file for configure autorun? |
| 21:36.47 | Sicelo | see /topic |
| 21:37.32 | bullx | thx for respond~ |
| 21:39.15 | teotwaki__ | I still can't believe Armstrong is dead. |
| 21:39.19 | Sicelo | maybe DocScrutinizer05, MohammadAG and others know .. but i'm sure they are in #harmattan as well |
| 21:40.03 | DocScrutinizer05 | teotwaki__: actually I already tried (in vain) to give a farewell bonmot |
| 21:40.38 | teotwaki__ | there's a space missing :P |
| 21:40.40 | teotwaki__ | it's "bon mot" |
| 21:40.56 | teotwaki__ | but in this case, "mot juste" would be more appropriate |
| 21:41.18 | DocScrutinizer05 | for what I came up with, neither is appropriate |
| 21:41.44 | DocScrutinizer05 | "ouch!" probably is most appropriate ;-D |
| 21:42.46 | teotwaki__ | Well, I'd simply say that the man who accomplished mankind's greatest leap just embarked on man's greatest journey. |
| 21:44.01 | teotwaki__ | anyway, gotta go feed a colleague's cat. 'later |
| 21:44.19 | DocScrutinizer05 | o/ |
| 22:03.58 | *** join/#maemo Ian--- (~ian@78.133.59.35) |
| 22:42.31 | *** part/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 22:42.43 | *** join/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 22:59.12 | *** join/#maemo |thunder (~e@c-68-42-120-238.hsd1.mi.comcast.net) |
| 23:05.11 | *** join/#maemo Ian-- (~ian@46.11.107.237) |
| 23:08.45 | *** join/#maemo hardaker (~hardaker@mail.hardakers.net) |
| 23:25.30 | *** join/#maemo HtheB (~HtheB@188.91.8.140) |
| 23:52.02 | *** join/#maemo HtheB (~HtheB@82-169-197-27.ip.telfort.nl) |
| 23:58.17 | *** join/#maemo ColdFyre (~lenny@c-98-248-56-123.hsd1.ca.comcast.net) |