| 00:03.11 | DocScrutinizer05 | honestly ponders to integrate a malware filter to CSSU. First candidates to nuke form device and HAM list of available apps: batterypatch and speedpatch |
| 00:03.20 | DocScrutinizer05 | and fapman |
| 00:03.23 | DocScrutinizer05 | ;-P |
| 00:03.53 | *** join/#maemo louisdk (~louis@31.25.18.35) |
| 00:04.34 | DocScrutinizer05 | meh, waaay simpler: get dummy void packages of same name into CSSU MP |
| 00:04.36 | *** join/#maemo cyborg-o1e (~cyborg-on@212-178-5-119.broadband.tenet.odessa.ua) |
| 00:04.39 | DocScrutinizer05 | done, next! |
| 00:05.14 | DocScrutinizer05 | merlin1991: ^^^ |
| 00:05.18 | DocScrutinizer05 | ;-P |
| 00:07.13 | DocScrutinizer05 | merlin1991: no kidding, we should ponder that |
| 00:08.34 | *** join/#maemo DrGrov (~C.J@unaffiliated/drgrov) |
| 00:08.51 | *** part/#maemo DrGrov (~C.J@unaffiliated/drgrov) |
| 00:09.08 | DocScrutinizer05 | of course we should triple-check if we want to restrict user's feeedom of choice in that way. But for *some* particular rogue pkgs I think we might at least discuss the pros and cons |
| 00:09.53 | louisdk | First boot after updating my N950 to PR1.3 by leaked "ROM". Seems like everything is right :) |
| 00:10.18 | DocScrutinizer05 | fine :-) just a tad ECHAN |
| 00:12.59 | DocScrutinizer05 | chem|st: is it really tolerable that *patch malware (or basketware) still has "adverts" on tmo? |
| 00:13.29 | DocScrutinizer05 | I'm afraid it's even in extras repo |
| 00:51.20 | *** join/#maemo Dibblah (~Dibblah@host86-168-39-42.range86-168.btcentralplus.com) |
| 01:00.26 | *** join/#maemo beford (~beford@unaffiliated/beford) |
| 01:01.16 | *** join/#maemo DrGrov (~C.J@unaffiliated/drgrov) |
| 01:01.33 | *** part/#maemo DrGrov (~C.J@unaffiliated/drgrov) |
| 01:08.37 | ShadowJK | lol |
| 01:26.57 | *** join/#maemo Hoolxi (~Openfree@120.204.177.81) |
| 01:30.51 | *** join/#maemo wmarone (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net) |
| 01:32.58 | *** part/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 01:33.08 | *** join/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 01:35.49 | *** join/#maemo rick8024 (~try@xdsl-89-0-162-86.netcologne.de) |
| 01:36.24 | *** join/#maemo bef0rd (~fernando@unaffiliated/beford) |
| 01:58.01 | kerio | jacekowski: i need some hex editing on image-viewer |
| 01:58.18 | kerio | jacekowski: i need the free ram check to be cracked |
| 01:58.37 | kerio | because it doesn't work properly with >4GB of free ram+swap |
| 02:00.51 | *** join/#maemo jluisn (~quassel@177.135.63.41) |
| 02:00.56 | *** join/#maemo uen| (~uen@p5DCB36A8.dip.t-dialin.net) |
| 02:14.03 | DocScrutinizer51 | iirc jacekowski lacks a working n900, so if we want him do such things we should ponder what to do about that |
| 02:21.29 | kerio | :( |
| 02:21.30 | kerio | hmm |
| 02:21.38 | kerio | send him the binary? |
| 02:22.10 | kerio | maybe the whole package, to be installed in scratchbox |
| 02:22.23 | kerio | \_o_/ |
| 02:22.33 | kerio | i asked him because he did fmtx too |
| 02:22.43 | kerio | and that was harder to do than this |
| 02:30.13 | DocScrutinizer05 | send him a N900 ;-) |
| 02:40.34 | *** part/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 02:40.46 | *** join/#maemo valeriusN (~valeriusN@xmpp.jrudevels.org) |
| 02:46.13 | *** join/#maemo SmilyOrg (Smily@89.142.213.68) |
| 03:03.23 | *** join/#maemo Jucato (~jucato@kde/developer/jucato) |
| 03:21.02 | *** join/#maemo Gh0sty (~ghosty@213.219.149.112.adsl.dyn.edpnet.net) |
| 03:40.04 | *** join/#maemo Shapeshifter (~Shapeshif@saskatoon.icu.uzh.ch) |
| 03:42.04 | *** join/#maemo Timmy (~quassel@37.254.25.130) |
| 03:42.04 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 03:46.59 | *** join/#maemo atlas (~atlas@kurios.r4780y.com) |
| 03:53.17 | *** join/#maemo atlas (~atlas@kurios.r4780y.com) |
| 03:53.37 | *** join/#maemo fredrinLap (~fn@cm-84.208.108.15.getinternet.no) |
| 04:08.14 | Timmy | freemangordon: hey |
| 04:22.58 | *** join/#maemo hardaker (~hardaker@75-101-67-197.dsl.dynamic.omsoft.com) |
| 05:05.34 | *** join/#maemo mhlavink (quassel@nat/redhat/x-rztaadifnobwlnxh) |
| 05:07.19 | *** join/#maemo kerio (kerio@unaffiliated/kerio) |
| 05:21.37 | *** join/#maemo args[0] (~args0]@199.188.72.28) |
| 05:34.34 | *** join/#maemo Hurrian (~yuki@121.54.2.104) |
| 06:16.14 | *** join/#maemo johnsu01 (user@gateway/shell/gnu/x-jixbngzltkpibavr) |
| 06:19.23 | *** join/#maemo johnsu01 (user@fsf/staff/johnsu01) |
| 06:38.21 | *** join/#maemo wmarone_ (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net) |
| 06:43.42 | *** join/#maemo johnsu01` (user@gateway/shell/gnu/x-lmurefnacwjffumu) |
| 06:46.01 | *** join/#maemo johnsu01` (user@fsf/staff/johnsu01) |
| 06:53.53 | *** join/#maemo antero (~antero@cs181045014.pp.htv.fi) |
| 07:10.31 | *** join/#maemo entitled (e@lodju.net) |
| 07:14.56 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 07:16.25 | *** join/#maemo ChikuLinu__ (Chiku01@2a01:e35:8b73:8620:a93c:876:e525:9f26) |
| 07:29.41 | *** join/#maemo utanapischti (~username@p4FF2C930.dip.t-dialin.net) |
| 07:30.15 | *** join/#maemo jrocha (~JRocha@183.2.165.83.dynamic.mundo-r.com) |
| 07:35.05 | RzR | has any of you a diablo scrachbox toolchain handy ? |
| 07:40.55 | *** join/#maemo e-yes (~e-yes@95.73.166.224) |
| 07:52.55 | *** join/#maemo GNUton-BNC (~gnuton@81-197-75-61.elisa-mobile.fi) |
| 07:57.22 | *** join/#maemo heroux (~heroux@5070823C.static.ziggozakelijk.nl) |
| 08:04.15 | *** join/#maemo Hoolxi (~Openfree@183.195.228.6) |
| 08:17.55 | *** join/#maemo piggz__ (~piggz@host-92-18-202-200.as13285.net) |
| 08:26.31 | *** join/#maemo NIN101 (~NIN@p5DD280B2.dip0.t-ipconnect.de) |
| 08:29.39 | *** join/#maemo OkropNick (kuba@host-n2-72-190.telpol.net.pl) |
| 08:30.27 | *** join/#maemo livelace (~livelace@62.192.242.235) |
| 08:42.08 | *** join/#maemo ced117 (~ced117@AStrasbourg-552-1-82-228.w92-141.abo.wanadoo.fr) |
| 08:42.08 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 08:46.16 | *** join/#maemo geaaru (~geaaru@host135-169-dynamic.41-79-r.retail.telecomitalia.it) |
| 08:54.37 | *** join/#maemo GNUton-BNC (~gnuton@81-197-75-61.elisa-mobile.fi) |
| 08:58.34 | *** part/#maemo MacDrunk (~marper@201.164.180.247) |
| 09:01.00 | *** join/#maemo sirdancealot (~sirdancea@98.82.broadband5.iol.cz) |
| 09:04.18 | *** join/#maemo args[0] (~args0]@199.188.72.28) |
| 09:10.38 | *** join/#maemo args[0] (~args0]@199.188.72.28) |
| 09:12.55 | *** join/#maemo GNUton-BNC (~gnuton@81-197-75-61.elisa-mobile.fi) |
| 09:16.58 | *** join/#maemo args[0] (~args0]@199.188.72.28) |
| 09:22.15 | *** join/#maemo radic (~radic@dslb-094-216-236-040.pools.arcor-ip.net) |
| 09:26.55 | *** join/#maemo toxaris (~toxaris@90-230-114-186-no34.tbcn.telia.com) |
| 09:29.54 | *** join/#maemo piggz__ (~piggz@host-92-18-202-200.as13285.net) |
| 09:50.45 | *** join/#maemo GNUton-BNC (~gnuton@81-197-75-61.elisa-mobile.fi) |
| 10:24.46 | *** join/#maemo luca__ (~luca@i5E8796EC.versanet.de) |
| 10:29.28 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 10:33.40 | *** join/#maemo stardiviner (~stardivin@218.74.187.181) |
| 10:37.04 | *** join/#maemo GNUton-BNC (~gnuton@81-197-75-61.elisa-mobile.fi) |
| 10:42.33 | *** join/#maemo lxp (~lxp@62-47-165-253.adsl.highway.telekom.at) |
| 11:05.39 | *** join/#maemo maybeHere (~cl@p5B16775F.dip.t-dialin.net) |
| 11:09.32 | *** join/#maemo Darkchaos (~darkchaos@i59F7AC18.versanet.de) |
| 11:13.14 | *** join/#maemo Sazpaimon__ (~wat@pool-68-238-249-133.phlapa.fios.verizon.net) |
| 11:13.32 | *** join/#maemo Sazpaimon__ (wat@pool-68-238-249-133.phlapa.fios.verizon.net) |
| 11:17.28 | *** join/#maemo Darkchaos (~darkchaos@i59F7AC18.versanet.de) |
| 11:19.41 | *** join/#maemo murrayc (~murrayc@ppp-188-174-61-99.dynamic.mnet-online.de) |
| 11:34.13 | *** join/#maemo bsdmaniak (~bsdmaniak@std93-20-88-120-139-80.fbx.proxad.net) |
| 11:34.26 | kerio | DocScrutinizer05: you there? |
| 11:37.39 | *** join/#maemo valeriusL (~valerius@85.26.180.158) |
| 11:42.11 | *** join/#maemo lbt_ (~david@78.32.229.233) |
| 11:42.12 | *** join/#maemo lbt_ (~david@Maemo/community/contributor/lbt) |
| 11:47.42 | kerio | DocScrutinizer05: why does your calibration script start, stop and restart bme? |
| 11:47.53 | kerio | can't you just start it once, when it's done? |
| 11:49.36 | DocScrutinizer05 | kerio: yep, I'm always here |
| 11:49.42 | *** join/#maemo ale152 (~quassel@host158-22-dynamic.7-87-r.retail.telecomitalia.it) |
| 11:50.01 | kerio | DocScrutinizer05: i know, i'm always here too but sometimes i'm asleep or away from anything ircful |
| 11:50.15 | DocScrutinizer05 | well, maybe cargo cult coding. It seemed to have healthy effects whenever I messed around with bme |
| 11:50.52 | kerio | haha |
| 11:51.05 | DocScrutinizer05 | often bme recovers from totally insane battery capacity guestimate after second restart |
| 11:51.14 | kerio | anyway, i'm going to rewrite your calibration script to not use bq27200.sh |
| 11:51.17 | kerio | because there's no reason to |
| 11:51.30 | DocScrutinizer05 | sure |
| 11:51.32 | kerio | it spams the i2c bus for no reason, considering that you only need vdq and edv1 |
| 11:51.53 | DocScrutinizer05 | not that this would matter at all in this context |
| 11:52.20 | DocScrutinizer05 | but sure, go ahead, it's sane and feasible |
| 11:52.59 | DocScrutinizer05 | I've just been lazy when writing this lil fanzy especially for your convenience, in 10 minutes |
| 11:53.25 | kerio | oh, btw |
| 11:53.32 | kerio | busybox does have a way to do bitwise AND |
| 11:53.57 | DocScrutinizer05 | you're sure that's not busybox-power? |
| 11:54.37 | kerio | yep |
| 11:54.47 | kerio | $(( (0x04 & 0x04) / 4 )) |
| 11:54.55 | DocScrutinizer05 | (NB bq27200.sh is ShadowJK's work, based on a bashscript called bq27k-detail I wrote) |
| 11:54.57 | kerio | versus $(( (0x04 & 0x03) / 4 )) |
| 11:55.28 | DocScrutinizer05 | hm? |
| 11:55.37 | kerio | one is 1, the other is 0 |
| 11:55.45 | DocScrutinizer05 | sure |
| 11:55.58 | kerio | in BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso31+0cssu0) |
| 11:56.31 | DocScrutinizer05 | well, bq27k-details is using arrays, and those are missing in messybox |
| 11:57.45 | DocScrutinizer05 | I admit I might have copied the bit-dissecting code from shadowjk though |
| 11:58.42 | DocScrutinizer05 | so even while I'm aware of bit-ops in bash, the code to dissect flags might still be plain interger arithmetic |
| 11:59.01 | ShadowJK | assumed sh didn't habe binary arithmetic and used integer arithmetic |
| 12:00.00 | kerio | also, why do you all people use $( ) instead of ` `? |
| 12:00.18 | DocScrutinizer05 | simple answer? because you can nest it |
| 12:00.23 | kerio | oic |
| 12:00.27 | ShadowJK | i find it clearer, and also $() is easier to type |
| 12:01.10 | ShadowJK | It's probably not ', and ` and ยด are behind sym keyboard on n900 |
| 12:01.10 | DocScrutinizer05 | ambiguous lexems always are prone to fail miserably |
| 12:01.20 | ShadowJK | and I'm not sure which one it is :) |
| 12:01.36 | DocScrutinizer05 | that too |
| 12:02.09 | DocScrutinizer05 | see PITA with "ticks" |
| 12:02.32 | DocScrutinizer05 | and "embeddend'ticks'" |
| 12:03.26 | DocScrutinizer05 | luckily in shellscript you can toggle between ' and " usually, so it's parseable |
| 12:04.19 | DocScrutinizer05 | how much more convenient is a clear distinction between opening and closing lexem |
| 12:05.06 | DocScrutinizer05 | if I wasn't that lazy, I'd even use ${envvar} all the time |
| 12:08.00 | DocScrutinizer05 | kerio: bq27k-detail2: >> $(( (0x${dmp[0x0A]} & 2#10000000)?1:0 )) CHGS Charge State flag. A 1 in the CHGS indicates a charge current (VSRP > VSRN). Charging." << |
| 12:15.14 | kerio | DocScrutinizer05: am i a bad person if i make it #!/bin/bash just because i feel safer? |
| 12:15.31 | DocScrutinizer05 | no, not at all |
| 12:15.42 | DocScrutinizer05 | better than other way around |
| 12:16.18 | DocScrutinizer05 | never use #!/bin/sh when you're actually not sure you might have used bashisms |
| 12:17.39 | DocScrutinizer05 | actually verifying scripts for basic shell compatibility (no *isms) is a pretty tedious task |
| 12:17.55 | DocScrutinizer05 | at least I haven't found any proper tool to do it yet |
| 12:24.20 | kerio | hm, how do i call functions in shell scripts? |
| 12:24.44 | kerio | oh, like binaries |
| 12:24.44 | kerio | k |
| 12:26.40 | kerio | ah goddammit, the semantics of conditions in shell scripting are fucking stupid |
| 12:29.21 | *** join/#maemo radic (~radic@dslb-094-216-236-040.pools.arcor-ip.net) |
| 12:30.33 | DocScrutinizer05 | hmm? |
| 12:31.43 | DocScrutinizer05 | (like binaries) actually more like shellscripts (which in turn don't differ much from binaries for the way to invoke them) |
| 12:33.14 | DocScrutinizer05 | actually I just started wondering if local env predefines work for function calls intrascript as well (env1=a env2=b myfunction) |
| 12:33.46 | DocScrutinizer05 | to be precise I wonder if those envs will get dropped when function returns |
| 12:34.09 | kerio | hm, how does ! work in the context of an if? |
| 12:34.17 | kerio | i mean, what's the distributivity with &&? |
| 12:34.29 | *** join/#maemo jhb (~joerg@tmo-102-181.customers.d1-online.com) |
| 12:34.30 | DocScrutinizer05 | ! >> && |
| 12:35.15 | kerio | meh, i'll do it inside test |
| 12:35.32 | kerio | how do i output to stderr? |
| 12:35.32 | DocScrutinizer05 | if [ !a && !b] <=> if [ ! (a || b) ] |
| 12:35.38 | kerio | yeah, yeah, i figured :) |
| 12:35.53 | DocScrutinizer05 | exec >2 |
| 12:35.56 | DocScrutinizer05 | ;-P |
| 12:35.56 | kerio | wait, i can do || inside test, too? |
| 12:35.59 | kerio | neat |
| 12:36.11 | kerio | DocScrutinizer05: i actually meant for just a message |
| 12:36.20 | kerio | also it should be >%2, right? |
| 12:36.24 | DocScrutinizer05 | aah, then as usual |
| 12:36.29 | kerio | or something |
| 12:36.36 | kerio | i can never remember the syntax for file descriptors :s |
| 12:36.45 | DocScrutinizer05 | yeah |
| 12:36.53 | kerio | nope, &2 |
| 12:37.25 | DocScrutinizer05 | simple - just remember & means "addr of" |
| 12:37.32 | kerio | ... |
| 12:37.42 | kerio | what you did there, i see it |
| 12:40.22 | *** join/#maemo louisdk (~louisdk@31.25.18.35) |
| 12:40.22 | DocScrutinizer05 | I think busybox also doesn't know base2 consts |
| 12:40.32 | DocScrutinizer05 | like 2#10000000 |
| 12:41.01 | DocScrutinizer05 | not sure about that either |
| 12:43.13 | DocScrutinizer05 | kerio: thanks for making me aware of >> |
| 12:43.14 | DocScrutinizer05 | if [ x$BASH_VERSION = x ]; then |
| 12:43.16 | DocScrutinizer05 | <PROTECTED> |
| 12:43.21 | DocScrutinizer05 | << missing a redirect to stderr |
| 12:43.53 | kerio | DocScrutinizer05: what's /usr/sbin/i2cset -y -m 0x80 2 0x6b 0x00 0x80; # timer reset ? |
| 12:44.06 | DocScrutinizer05 | err, just that |
| 12:44.27 | DocScrutinizer05 | it resets watchdog timer in bq24150 |
| 12:44.47 | kerio | but... you just reset it |
| 12:44.52 | kerio | with /usr/sbin/i2cset -y 2 0x6b 0x01 0xcc |
| 12:45.03 | kerio | or is that just "stop charge"? |
| 12:45.08 | DocScrutinizer05 | yep |
| 12:45.45 | DocScrutinizer05 | you can't stop watchdog in bq24150. It will engage first time you send *any* I2C command |
| 12:45.50 | kerio | k |
| 12:45.57 | kerio | yeah but you keep resetting it |
| 12:46.07 | kerio | no, wait |
| 12:46.07 | DocScrutinizer05 | and on expiry will reset bq24150 to defaults which are "enable emergency charging" |
| 12:46.55 | DocScrutinizer05 | that's why I first stop charging, then keep watchdog happy so it stays in off-mode |
| 12:47.30 | DocScrutinizer05 | otherwise it would resume emergency charging after watchdog expiry (32s) |
| 12:47.34 | kerio | i see |
| 12:47.59 | kerio | and then when you stop it it immediately restarts because the watchdog has expired? |
| 12:48.22 | DocScrutinizer05 | during max 32s, yes |
| 12:49.06 | DocScrutinizer05 | might be as little as 15s, due to chip's timebase is rather ??? |
| 12:49.24 | ShadowJK | If software doesn't check in every 32s, every setting made and every command sent is lost and chip resets to defaults: charge @ 100mA to a low level |
| 12:49.38 | DocScrutinizer05 | exactly |
| 12:49.47 | DocScrutinizer05 | only 32s is upper limit |
| 12:50.01 | DocScrutinizer05 | to stay on safe side, we need something like 10s period |
| 12:50.15 | kerio | hm, does sh have a do/while? |
| 12:50.20 | DocScrutinizer05 | yep |
| 12:50.29 | kerio | nope |
| 12:50.36 | kerio | it only has a while |
| 12:50.37 | ShadowJK | I lowered the period until resets stopped happening, and ended up with 15s |
| 12:50.39 | DocScrutinizer05 | while true; do echo fool:; done |
| 12:50.48 | kerio | that's a while, not a do...while |
| 12:50.55 | DocScrutinizer05 | meh |
| 12:51.43 | DocScrutinizer05 | it has while and until |
| 12:51.56 | DocScrutinizer05 | I hate until |
| 12:52.37 | kerio | dbus-send is standard fremantle, right? |
| 12:52.39 | DocScrutinizer05 | since it's a maximum confusing while !cond |
| 12:52.47 | DocScrutinizer05 | yep |
| 12:52.55 | kerio | and so are start and stop |
| 12:53.05 | DocScrutinizer05 | though any path in any script isn't |
| 12:53.19 | DocScrutinizer05 | $PATH that is |
| 12:53.44 | DocScrutinizer05 | nope, basically start and stop are convenience stuff for initctl start and initctl stop |
| 12:54.05 | kerio | but they're binary files! |
| 12:54.27 | kerio | ooh, links to initctl |
| 12:54.36 | DocScrutinizer05 | so while you may get away with start bme, you actually *ought* use /sbin/initctl start bme |
| 12:54.48 | kerio | can i at least avoid paths for sleep and echo? |
| 12:54.51 | kerio | and test |
| 12:55.09 | DocScrutinizer05 | that's a pretty good question |
| 12:55.13 | DocScrutinizer05 | :-D |
| 12:55.36 | DocScrutinizer05 | probably it's safe to assume "standard" PATH being set |
| 12:55.48 | DocScrutinizer05 | which is sth like /bin /sbin |
| 12:55.56 | kerio | meh, i'll choose to assume that root has initctl and dbus-send in the path, and echo and sleep are something |
| 12:56.06 | DocScrutinizer05 | yep |
| 12:56.12 | *** join/#maemo jhb (~joerg@tmo-102-158.customers.d1-online.com) |
| 12:56.13 | DocScrutinizer05 | basically everybody does |
| 12:56.17 | kerio | or should i assume that they're in the place they ought to be, aka /sbin/initctl and /usr/bin/dbus-send ? |
| 12:56.38 | DocScrutinizer05 | for those yes you should assume and call them like that |
| 12:56.49 | DocScrutinizer05 | (I didn't) |
| 12:56.59 | DocScrutinizer05 | shame on me |
| 12:57.57 | DocScrutinizer05 | well according to above rationale you may assume initctl is in /sbin and thus "known", while dbus-send obviously isn't |
| 12:59.39 | DocScrutinizer05 | most sane way to handle that is to define envs for the "unknown2 stuff, like >> dbus="/usr/bin/dbus-send" |
| 12:59.51 | DocScrutinizer05 | then even test for exectuable property |
| 12:59.54 | kerio | nah, /usr/bin/dbus-send is part of dbus |
| 12:59.59 | kerio | it's standard fremantle |
| 13:00.09 | kerio | i2cget/i2cset are in i2c-tools though, and i do test for those like that :) |
| 13:00.46 | kerio | DocScrutinizer05: work in progress: http://fpaste.org/xwxH/ |
| 13:01.41 | DocScrutinizer05 | sweet |
| 13:01.45 | DocScrutinizer05 | :-) |
| 13:02.48 | kerio | todo: more putting stuff in functions |
| 13:02.51 | kerio | so the logic is clearer |
| 13:03.53 | DocScrutinizer05 | # TODO: display TTF here |
| 13:04.01 | kerio | that, too ) |
| 13:04.02 | kerio | :) |
| 13:04.03 | DocScrutinizer05 | s/TTF/TTE/ |
| 13:04.07 | kerio | ok |
| 13:04.09 | kerio | :c |
| 13:04.24 | DocScrutinizer05 | it's DIScharging, so TimeToEmpty |
| 13:04.50 | kerio | i thought it was Time To Finish |
| 13:04.56 | kerio | but alright |
| 13:05.06 | DocScrutinizer05 | kerio: kudos, a delight to read such pretty code at a sunday afternoon |
| 13:05.11 | kerio | brb walking the dog |
| 13:05.37 | kerio | also ^__________^ |
| 13:07.28 | *** join/#maemo Timmy (~quassel@37.254.22.248) |
| 13:07.29 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 13:16.55 | DocScrutinizer05 | kerio: while true; do kick_bq24k; sleep 10; edv1 && break; done; |
| 13:19.19 | DocScrutinizer05 | maybe even |
| 13:19.40 | DocScrutinizer05 | while kick_bq24k && sleep 10; do edv1 && break; done; |
| 13:20.46 | DocScrutinizer05 | (sometimes simplifies ^C abort |
| 13:20.48 | DocScrutinizer05 | ) |
| 13:22.07 | kerio | oh right |
| 13:22.07 | kerio | :c |
| 13:22.11 | kerio | but that makes it uglier! |
| 13:22.17 | DocScrutinizer05 | hehe |
| 13:22.36 | DocScrutinizer05 | ugly and short, or whining about missing do until |
| 13:22.43 | DocScrutinizer05 | ;-) |
| 13:22.50 | DocScrutinizer05 | or bloated |
| 13:22.51 | kerio | besides, wouldn't ^C during the sleep exit the loop, causing the rest of the script to go on? |
| 13:23.04 | DocScrutinizer05 | depends on settings |
| 13:24.11 | DocScrutinizer05 | either a cmd returning with error that isn't cought will abort whole script (incl any while true loop), or it will simply be ignored and the loop happily continues forever |
| 13:24.53 | DocScrutinizer05 | iirc it's set +e / -e |
| 13:25.14 | DocScrutinizer05 | your scripts inherit that setting from invoking shell |
| 13:25.53 | DocScrutinizer05 | all disclaimer "I'm not really awake yet" |
| 13:28.17 | DocScrutinizer05 | set +e; while true; do sleep 1; done |
| 13:28.22 | DocScrutinizer05 | set -e; while true; do sleep 1; done |
| 13:33.13 | kerio | TTE is in minutes, right? |
| 13:34.43 | DocScrutinizer05 | right |
| 13:35.19 | kerio | ah crap |
| 13:35.25 | kerio | Time to empty: 0x01fc minutes |
| 13:35.54 | DocScrutinizer05 | >> -e Exit immediately if a pipeline (which may consist of a single simple command), a subshell command enclosed in parentheses, or one of the commands executed as part of a command list enclosed by braces (see SHELL GRAMMAR above) exits with a non-zero status. The shell does not exit if the command that fails is part of the command list immediately following a while or until[...] |
| 13:35.56 | DocScrutinizer05 | This option applies to the shell environment and each subshell environment separately (see COMMAND EXECUTION ENVIRONMENT above), and may cause subshells to exit before executing all the commands in the subshell. |
| 13:35.57 | DocScrutinizer05 | << |
| 13:37.39 | DocScrutinizer05 | whatever, I found sometimes >> while true; do ... sleep 1; done << loops are pretty hard to abort, while you abort them easily when testing for sleep command's return code |
| 13:38.06 | kerio | meh, ^C kills everything |
| 13:38.21 | kerio | maybe i should check for the exit value of sleep and restart bme before closing the script |
| 13:38.22 | kerio | but meh |
| 13:38.31 | DocScrutinizer05 | depends (remaining to define on what) |
| 13:38.53 | DocScrutinizer05 | maybe you should use a trap to restart bme |
| 13:39.12 | DocScrutinizer05 | trap start_bme exit |
| 13:39.40 | DocScrutinizer05 | see booston |
| 13:39.51 | kerio | or maybe the user should fuck off and let my script be |
| 13:40.22 | kerio | >:C |
| 13:40.30 | DocScrutinizer05 | having a exit trap to cleanup is a pretty nice idea, much underrated |
| 13:41.14 | DocScrutinizer05 | and it's so infinitely more convenient than to handle each abort path in a single else branch |
| 13:41.15 | kerio | i should probably display the current flow too |
| 13:42.09 | kerio | http://fpaste.org/b6Ay/ |
| 13:42.51 | DocScrutinizer05 | http://maemo.cloud-7.de/maemo5/usr/sbin/booston |
| 13:44.02 | kerio | by the way, what's the correct term? pet the watchdog? tickle the watchdog? kick the watchdog? |
| 13:44.34 | *** join/#maemo Ken-Young (~Ken@pool-68-160-39-2.bos.east.verizon.net) |
| 13:46.03 | ShadowJK | diablo called it kick |
| 13:47.08 | DocScrutinizer05 | I kick dogs, other like to tickle them |
| 13:47.37 | DocScrutinizer05 | probably depends on whether you like dogs or not |
| 13:47.59 | *** join/#maemo jluisn (~quassel@177.98.208.167) |
| 13:48.44 | DocScrutinizer05 | kerio: you'll need root to run that script, and in root you need run-standalone.sh for dbus-send |
| 13:49.00 | Ken-Young | I have recently had to re-install the Maemo 5 scratchbox SDK on a machine running Ubuntu. It installed smoothly, but when I run the x86 desktop withing xephyr, the Hildon widgets don't work properly. Specifically, the drop-down menus don't show any text the first time they are accessed (though they do show text during subsequent accesses) and changes made to the GUI widgets do not show up on the widgets, although the widget events a |
| 13:49.00 | Ken-Young | re seen by the application. Has anyone seen this problem and found a fix? |
| 13:52.18 | *** join/#maemo luf (~luf@ip-89-103-166-30.net.upcbroadband.cz) |
| 13:52.28 | *** join/#maemo diverse_izzue (~hunzikea@2606ds5-by.0.fullrate.dk) |
| 13:53.15 | DocScrutinizer05 | (kick vs tickle) actually both terms are missleading, since the dog is considered state:sleeping unless you forget to do whatever you name the action to keep it sleeping and it wakes up and barks |
| 13:53.36 | DocScrutinizer05 | I think neither kicking nor tickling will make a real dog continue sleeping |
| 13:54.47 | DocScrutinizer05 | probably the whole term / picture / analogy is a bit... odd |
| 13:55.39 | DocScrutinizer05 | since real watchdogs don't usually behave on a timeout policy of any kind |
| 14:01.43 | ShadowJK | sure they do, if you're gone from home too long they eat your shoes and couch |
| 14:02.07 | DocScrutinizer05 | hehehehehe |
| 14:05.31 | *** join/#maemo Gizmokid2005 (~Gizmokid2@dedi.gizmokid2005.com) |
| 14:14.52 | *** join/#maemo hardaker (~hardaker@75-101-67-197.dsl.dynamic.omsoft.com) |
| 14:35.53 | *** join/#maemo cyborg-one (~cyborg-on@31.31.97.126) |
| 14:39.16 | *** join/#maemo louisdk (~louisdk@31.25.18.35) |
| 14:48.17 | *** join/#maemo CodenameStrike-N (~Codenames@203.82.92.67) |
| 14:52.01 | *** join/#maemo louisdk (~louis@31.25.18.35) |
| 14:59.57 | *** join/#maemo cyborg-o1e (~cyborg-on@212-178-14-66.broadband.tenet.odessa.ua) |
| 15:01.39 | *** join/#maemo vi__ (~user@31.185.137.96) |
| 15:02.41 | *** join/#maemo HotJessicaBOOBS (~DESU@184.82.139.46) |
| 15:05.23 | *** join/#maemo disco_stu_droid (~wrt54gl@190.216.32.137) |
| 15:07.48 | *** join/#maemo args[0] (~args0]@199.188.72.28) |
| 15:08.03 | *** join/#maemo DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 15:09.46 | *** join/#maemo DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 15:13.58 | *** join/#maemo xmlich02_ (~imlich@ip-62-245-126-159.net.upcbroadband.cz) |
| 15:17.48 | *** join/#maemo MrPingu (~Thunderbi@86.92.226.97) |
| 15:21.01 | DocScrutinizer05 | WTF of the month: http://gitorious.org/community-ssu/ke-recv/blobs/master/src/events.c#line149 ff |
| 15:21.09 | *** join/#maemo M4rtinK (~M4rtinK@mail.melf.eu) |
| 15:21.38 | *** join/#maemo args[0] (~args0]@199.188.72.28) |
| 15:27.48 | ZogG_laptop | DocScrutinizer05: there is goto in C? |
| 15:27.55 | *** join/#maemo args[0] (~args0]@199.188.72.28) |
| 15:27.56 | ZogG_laptop | and it's usable? i mean people use it? |
| 15:28.05 | ZogG_laptop | args[0]: cool nick |
| 15:30.54 | Ikarus | ZogG_laptop: *shudder* |
| 15:31.36 | Ikarus | but that kind of error handeling code is the probably the only sane use for goto |
| 15:32.23 | *** join/#maemo Jucato (~jucato@kde/developer/jucato) |
| 15:32.58 | ZogG_laptop | Ikarus: i know C a little bit only, never met goto yet. |
| 15:33.03 | ZogG_laptop | C/C++ |
| 15:33.07 | ZogG_laptop | both |
| 15:33.43 | DocScrutinizer05 | Ikarus: backward goto usually is EVIL |
| 15:34.11 | DocScrutinizer05 | a chain of THREE backward goto is MASTER_OF_EVIL |
| 15:35.05 | *** join/#maemo Krayon (~fallen@pdpc/supporter/28for7/krayon) |
| 15:35.17 | DocScrutinizer05 | forward goto to exit, or jump to errorhandler at end of function - ok'ish |
| 15:35.57 | DocScrutinizer05 | but never ever do a backward goto, especially not into a structure element like if{} while{} anything like that |
| 15:36.55 | DocScrutinizer05 | hell that looks like COBOL disassembly |
| 15:36.56 | Ikarus | DocScrutinizer05: hehehe |
| 15:38.12 | *** join/#maemo louisdk (~louis@31.25.18.35) |
| 15:39.39 | *** join/#maemo akls (~alex@82.131.0.191.cable.starman.ee) |
| 15:43.44 | *** join/#maemo disco_stu_droid (~wrt54gl@190.216.32.137) |
| 15:44.36 | *** join/#maemo Timmy (~quassel@37.254.22.248) |
| 15:44.37 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 15:45.02 | *** join/#maemo e-yes (~e-yes@94.45.170.171) |
| 15:50.43 | *** join/#maemo dimw1t (~atlas@adsl-76-235-204-127.dsl.klmzmi.sbcglobal.net) |
| 15:58.54 | kerio | DocScrutinizer05: it's perfectly legal to jump inside a loop in C |
| 15:59.25 | DocScrutinizer05 | kerio: legal and any good practice are two differnet things |
| 16:00.26 | kerio | also see duff's device |
| 16:05.07 | *** join/#maemo sixwheeledbeast (~sixwheele@host-89-243-129-183.as13285.net) |
| 16:06.47 | *** join/#maemo bsdmaniak (~bsdmaniak@std93-20-88-120-139-80.fbx.proxad.net) |
| 16:08.48 | DocScrutinizer05 | http://pastebin.ca/2200289 |
| 16:09.44 | DocScrutinizer05 | ^^^ pretty low effort cleanup, could of course be done smarter and nicer |
| 16:10.25 | DocScrutinizer05 | no more backwards goto |
| 16:10.44 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 16:10.58 | DocScrutinizer05 | (yeah I know there's a bit missing around line190 then) |
| 16:13.41 | DocScrutinizer05 | actually 188,189 are obsolete then |
| 16:14.27 | DocScrutinizer05 | and [190] error3: volume_id_close (vid); needs some love |
| 16:15.38 | kerio | by the way, label: code; on the same line should be ground for execution |
| 16:15.45 | kerio | s/ground/grounds/ |
| 16:16.42 | DocScrutinizer05 | err, [192] error1: set_localised_label(mmc); needs ome love |
| 16:18.05 | *** join/#maemo messerting (~messertin@cm-84.211.113.209.getinternet.no) |
| 16:18.45 | DocScrutinizer05 | usually you have only one error: label, and do the >> if (fd < 0) << etc there |
| 16:19.37 | DocScrutinizer05 | doesn't matter you already did it before, on >> if (fd < 0) { goto error} |
| 16:19.56 | *** join/#maemo Timmy (~quassel@37.254.22.248) |
| 16:19.56 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 16:23.39 | DocScrutinizer05 | kerio: goto jumping into while or for loops usually yields pretty messy unexpected results (if the coder doing that really expected *anything*) |
| 16:24.30 | DocScrutinizer05 | jumping into if(){} branches may work |
| 16:24.52 | DocScrutinizer05 | but for sure should be avoide3d as much as possible |
| 16:27.05 | *** join/#maemo jhb1 (~joerg@89.204.138.55) |
| 16:33.22 | *** join/#maemo jhb (~joerg@tmo-106-254.customers.d1-online.com) |
| 16:37.04 | *** join/#maemo philipl (~mrkiasu@c-67-188-112-44.hsd1.ca.comcast.net) |
| 16:44.55 | *** join/#maemo illuminata (illuminata@ipv6.deformedfeatures.com) |
| 16:45.16 | DocScrutinizer05 | illuminata: please elaborate on details of your boot problem |
| 16:45.45 | illuminata | so. i'm hit by the reboot loop bug. and pretty hard apparently because flashing latest nokia firmware didn't fix it |
| 16:45.47 | DocScrutinizer05 | illuminata: you (ever) used recent powerkernel? |
| 16:45.59 | illuminata | and nope |
| 16:46.24 | DocScrutinizer05 | how exactly are the sequence of sympthoms of this reboot loop? |
| 16:46.59 | DocScrutinizer05 | does jumping-dots splashscreen show up? |
| 16:47.40 | illuminata | home icons either don't draw or disappear. carrier name cycles too. and if by jumping dots you mean the loading screen then yeah |
| 16:48.33 | illuminata | and it seems to actually be crashing faster now that i re-flashed |
| 16:48.56 | DocScrutinizer05 | probably you got some homescreen settings in your $home dir that cause hildon desktop to segfault. Eventually dsme will reboot device after too many restarts of HD |
| 16:49.22 | illuminata | similar was mentioned prior, but shouldn't a firmware flash take care of any of those settings, too? |
| 16:49.25 | DocScrutinizer05 | reflashing COMBINED doesn't clear/delete those files |
| 16:49.30 | illuminata | aaaaaaaaaah |
| 16:49.40 | *** join/#maemo luf (~luf@ip-89-103-166-30.net.upcbroadband.cz) |
| 16:49.51 | DocScrutinizer05 | since flashing COMBINED keeps all your "user data" intact |
| 16:50.16 | DocScrutinizer05 | you got backupmenu installed? |
| 16:50.36 | illuminata | don't think so, unless that's the same as the standard backup app |
| 16:50.41 | DocScrutinizer05 | nope |
| 16:50.44 | DocScrutinizer05 | ~bm |
| 16:50.44 | infobot | i heard backupmenu is http://talk.maemo.org/showthread.php?t=63975 |
| 16:51.12 | DocScrutinizer05 | it would allow you to gather access to a shell in early boot, before HD goes mad |
| 16:51.20 | illuminata | dunno if i can use it though considering the phone won't even stay on a minute now |
| 16:51.29 | DocScrutinizer05 | in this shell you could manually clean out some files in $HOME |
| 16:52.36 | illuminata | maybe i can install it if i work fast enough (but probably not) |
| 16:53.05 | illuminata | but assuming i don't care what's on the phone, is there any firmware packages that i can install that'd allow for a 100% clean install? |
| 16:53.21 | kerio | DocScrutinizer05: backupmenu requires a somewhat working system though |
| 16:53.32 | kerio | because it's intended to work when stuff is ok |
| 16:53.36 | DocScrutinizer05 | for now there's proabably three possible rescue pathes for you: disable watchdogs via flasher (should stopp reboots, so you *might* gain access to xterm via kbd shortcut). use ~rescue-system. reflash VANILLA (and lose all your user data) |
| 16:53.42 | kerio | ~rescue-system |
| 16:53.50 | kerio | oh infobot |
| 16:53.52 | kerio | ~rescueos |
| 16:54.01 | kerio | ~rescue |
| 16:54.06 | kerio | DocScrutinizer05: you suck |
| 16:54.20 | DocScrutinizer05 | ~listkeys rescue |
| 16:54.26 | kerio | oh, with a - |
| 16:54.28 | kerio | wtf |
| 16:54.30 | kerio | ~rescue-os |
| 16:54.30 | infobot | rumour has it, rescue-os is http://wiki.maemo.org/User:Nin101/N900_Rescue_OS, or http://nin101.uni.cx/N900/rescueOS/documentation.txt, or http://206.253.166.96/N900/rescueOS/ |
| 16:55.17 | illuminata | hmm |
| 16:55.18 | DocScrutinizer05 | illuminata: flashing VANILLA is the "easiest" and most reliable way, given you don't care about user data (or have proper backup) |
| 16:55.20 | kerio | infobot: no, rescue-os is http://wiki.maemo.org/User:Nin101/N900_Rescue_OS , or http://nin101.uni.cx/N900/rescueOS/documentation.txt , or http://206.253.166.96/N900/rescueOS/ |
| 16:55.20 | infobot | okay, kerio |
| 16:55.25 | kerio | (added spaces before commas) |
| 16:55.42 | kerio | (not sure if it's just my irc client being stupid, but clicking didn't work properly, it thought , was part of the url) |
| 16:55.48 | NIN101 | the wiki page is outdated, you might as well remove everything except the URL with the IP |
| 16:56.00 | DocScrutinizer05 | kerio: thanks |
| 16:56.18 | kerio | NIN101: huh... why? what's wrong with nin101.uni.cx? |
| 16:56.46 | illuminata | i'm getting a malware warning for uni.cx in chrome |
| 16:56.58 | kerio | infobot: no, rescue-os is http://206.253.166.96/N900/rescueOS/ |
| 16:56.58 | infobot | kerio: okay |
| 16:57.11 | kerio | DocScrutinizer05: how do i add redirects for factoids? |
| 16:57.18 | kerio | like, make rescueos an alias for rescue-os |
| 16:57.33 | DocScrutinizer05 | ~rescueos is <reply>see rescue-os |
| 16:57.34 | infobot | okay, DocScrutinizer05 |
| 16:57.43 | kerio | huh |
| 16:57.46 | kerio | ~rescueos |
| 16:57.46 | infobot | extra, extra, read all about it, rescue-os is http://206.253.166.96/N900/rescueOS/ |
| 16:57.49 | kerio | i see |
| 16:58.18 | kerio | hmm, something bad about thumb2 binaries |
| 16:58.18 | illuminata | is there any way i can mass storage mount the phone before it fully boots into maemo? |
| 16:58.31 | NIN101 | rescueos |
| 16:58.40 | kerio | you can't chroot on a thumby system if you don't have a thumb-aware kernel |
| 16:58.47 | kerio | illuminata: rescueos does that |
| 16:58.50 | DocScrutinizer05 | illuminata: probably not, when it bootloops like yours |
| 16:58.51 | kerio | also bootmenu |
| 16:58.53 | kerio | also backupmenu |
| 16:59.04 | illuminata | k |
| 16:59.11 | DocScrutinizer05 | yeah, except those, of course |
| 16:59.20 | illuminata | meh |
| 16:59.28 | kerio | notice that neither one of those will let you access the rootfs |
| 16:59.29 | illuminata | just wanted to pull some pics off, then i wouldn't mind flashing vanilla |
| 16:59.34 | kerio | because well, it's not a block device |
| 16:59.41 | kerio | an alternative is usb networking and then ssh |
| 16:59.52 | DocScrutinizer05 | illuminata: you *may* disable watchdogs, and then happily mount MSM |
| 17:00.06 | kerio | ~ass-rage |
| 17:00.09 | kerio | no |
| 17:00.12 | kerio | ~ass rage |
| 17:00.12 | infobot | somebody said ass rage was Mass STOrage |
| 17:00.24 | kerio | giggles |
| 17:01.59 | DocScrutinizer05 | illuminata: it's just HD respawning too fast, so dsme reboots device. with watchdogs disabled (lifeguard-wd iirc), it won't reboot and MSM should work |
| 17:02.28 | DocScrutinizer05 | with a bit of luck |
| 17:03.04 | NIN101 | afk |
| 17:03.14 | illuminata | cool. i did some steps on a forum while at work a couple days ago, ran cat on some of that lifeguard stuff, and it was saying similarly iirc |
| 17:06.16 | DocScrutinizer05 | illuminata: flasher-3.5 --help |
| 17:07.11 | illuminata | w0rd. found a string of flags online that should do the trick too. but so far it's stayed alive in mass storage mode without rebooting |
| 17:07.25 | illuminata | got images out of fcamera, trying to find where the standard camera images are hidden |
| 17:07.34 | illuminata | *standard camera app |
| 17:08.04 | *** join/#maemo Sazpaimon__ (~wat@91.240.65.38) |
| 17:08.46 | DocScrutinizer05 | flasher --set-rd-flags |
| 17:08.53 | illuminata | dcim, there we go |
| 17:09.09 | DocScrutinizer05 | cool |
| 17:09.23 | *** join/#maemo shanttu (~shanttu@dsl-hkibrasgw3-ff55c100-11.dhcp.inet.fi) |
| 17:10.03 | illuminata | alrighty, thanks for the help everybody. should just be a matter of a vanilla flash now |
| 17:10.16 | illuminata | then maybe i'll see about cssu |
| 17:10.21 | kerio | cssu is good! |
| 17:10.27 | DocScrutinizer05 | flasher --set-rd-flags=no-lifeguard-reset,no-ext-wd,no-omap-wd |
| 17:10.29 | illuminata | stable too? |
| 17:10.31 | DocScrutinizer05 | iirc |
| 17:10.36 | kerio | idk |
| 17:10.43 | kerio | i'm on cssu-devel+thumb now |
| 17:10.52 | kerio | but i'm crazy and i don't do anything important in my life anyway |
| 17:11.00 | illuminata | lol |
| 17:11.05 | kerio | starts crying |
| 17:11.15 | DocScrutinizer05 | illuminata: yes, CSSU-S is stable (and actually wouldn't have rebooted for you ;-D ) |
| 17:11.20 | kerio | cssu-s is old |
| 17:11.36 | *** join/#maemo jluisn (~quassel@177.98.208.167) |
| 17:11.53 | illuminata | lol, good to know. maybe i'll give it a shot |
| 17:12.03 | DocScrutinizer05 | you should |
| 17:12.12 | DocScrutinizer05 | it's recommended for everybody now |
| 17:12.16 | illuminata | but is it true that it's hard to roll back from? |
| 17:12.30 | DocScrutinizer05 | you don't want to roll back |
| 17:12.56 | DocScrutinizer05 | just like you don't want or can rollback from PR1.3 to PR1.2 |
| 17:14.41 | DocScrutinizer05 | just think of it like PR1.4 |
| 17:15.19 | illuminata | k |
| 17:15.26 | DocScrutinizer05 | it's not about new features primarily, it's mere support for all users |
| 17:16.06 | DocScrutinizer05 | fixing bugs that Nokia never will touch |
| 17:16.25 | sixwheeledbeast | kerio: yes CSSU stable is old but that's how they become stable. with testing testing and more testing. |
| 17:17.11 | DocScrutinizer05 | and next CSSU-S release is at horizon - RSN, only a matter of weeks now |
| 17:17.28 | sixwheeledbeast | that's nice to know |
| 17:17.51 | *** join/#maemo markinfo (~marek@dhcp11.dmg.tuwien.ac.at) |
| 17:19.03 | DocScrutinizer05 | illuminata: you most probably won't notice any difference after installing CSSU-S |
| 17:19.43 | DocScrutinizer05 | if you do, let us know. There shouldn't be any difference regarding user experience |
| 17:20.07 | DocScrutinizer05 | except some annoying bugs missing |
| 17:20.10 | DocScrutinizer05 | ;-) |
| 17:21.18 | DocScrutinizer05 | all new leete things are strictly optional |
| 17:21.29 | DocScrutinizer05 | opt-in |
| 17:21.56 | *** join/#maemo Sazpaimon__ (~wat@pool-68-238-249-133.phlapa.fios.verizon.net) |
| 17:22.55 | *** join/#maemo Sazpaimon__ (wat@91.240.65.38) |
| 17:22.55 | *** join/#maemo Sazpaimon__ (wat@unaffiliated/Sazpaimon) |
| 17:23.15 | *** join/#maemo Sazpaimon__ (wat@91.240.65.38) |
| 17:23.21 | DocScrutinizer05 | on CSSU-Stable that is, CSSU-Testing is a bit more bleeding edge, since we need the new features tested, so in T they are opt-out (or at least that's what we try to achieve, some are not optional [yet]) |
| 17:23.26 | *** join/#maemo Sazpaimon__ (wat@unaffiliated/Sazpaimon) |
| 17:24.35 | DocScrutinizer05 | anyway I couldn't think of any reason why you would wnat to roll back to plain PR1.3.1 from CSSU-S |
| 17:24.50 | kerio | DocScrutinizer05: it's easy to roll back to PR1.3, btw |
| 17:25.01 | DocScrutinizer05 | reflash, yes |
| 17:25.04 | kerio | :D |
| 17:27.46 | illuminata | lol, gotcha |
| 17:27.57 | *** join/#maemo hardaker (~hardaker@75-101-67-197.dsl.dynamic.omsoft.com) |
| 17:31.28 | *** join/#maemo toxaris (~toxaris@90-230-114-186-no34.tbcn.telia.com) |
| 17:34.06 | DocScrutinizer05 | illuminata: one tiny "fix" I'm actually proud of, is that CSSU in your case wouldn't reboot device on HD respawning too fast, but simply give up, leaving you with a device like you could also get with watchdogs disabled |
| 17:34.34 | illuminata | that'd be great should similar crop up again |
| 17:35.08 | DocScrutinizer05 | press shift-ctrl-x on kbd and you shouls still get a shell |
| 17:36.00 | illuminata | worked |
| 17:36.12 | illuminata | and for some reason the phone's stayed alive for a bit now |
| 17:36.28 | DocScrutinizer05 | I meant on a not-bootlooping fecked CSSU |
| 17:36.44 | illuminata | right. just saying i've been lucky thus far on this boot |
| 17:36.52 | illuminata | still gonna vanilla it i think though |
| 17:36.56 | illuminata | got what i wanted off the phone |
| 17:37.35 | DocScrutinizer05 | nice. Well some widget on desktop going apeshit will tear down whole HD process. Sometimes the widget recovers though, or simply waits a bit till it acts up again |
| 17:37.55 | DocScrutinizer05 | in your case I guess it's been OMweather or what's the name |
| 17:38.00 | illuminata | i tried removing widgets but they'd vanish before i could clear them off from a gui |
| 17:38.11 | illuminata | i uninstalled omweather completely, no dice |
| 17:39.04 | DocScrutinizer05 | I once had same bootloop problem when I dragged OMweather from one screen to next, while same time $something interrupted the process |
| 17:40.01 | DocScrutinizer05 | back in "good ole" Pr1.0 times |
| 17:40.45 | DocScrutinizer05 | I wasn't as luckky as you |
| 17:40.50 | DocScrutinizer05 | had to reflash |
| 17:41.02 | DocScrutinizer05 | vanilla |
| 17:41.27 | illuminata | well my luck is only that it hasn't rebooted yet but the icon cycling issues are still being annoying |
| 17:42.00 | DocScrutinizer05 | you actually should reflash vanilla too |
| 17:42.13 | DocScrutinizer05 | now that you secured all your data |
| 17:43.17 | DocScrutinizer05 | it's indeed been an unfortunate decision to run all widgets *inside* HD process |
| 17:43.42 | DocScrutinizer05 | when any of them segfaults, it's actually HD that goes down |
| 17:46.09 | illuminata | indeed |
| 17:47.26 | *** join/#maemo Zahra (~Zahra@unaffiliated/belendax) |
| 17:48.46 | *** join/#maemo qwazix_ (~qwazix@athedsl-351601.home.otenet.gr) |
| 17:53.10 | illuminata | great, not getting a success message when flashing emmc |
| 17:53.28 | illuminata | stops at 20% on the data transfer and sends be back to prompt |
| 17:54.24 | DocScrutinizer05 | hmm, might be cable |
| 17:54.49 | DocScrutinizer05 | or sometimes download file corruption of image file |
| 17:55.04 | DocScrutinizer05 | sometimes just wrong file |
| 17:55.08 | illuminata | http://talk.maemo.org/showthread.php?t=78088 combing through this thread |
| 17:55.24 | DocScrutinizer05 | recheck you're using the 'latest' vanilla image |
| 17:55.54 | illuminata | am indeed |
| 18:03.31 | *** join/#maemo murrayc (~murrayc@ppp-188-174-61-99.dynamic.mnet-online.de) |
| 18:05.07 | *** join/#maemo stardiviner (~stardivin@218.74.187.181) |
| 18:11.02 | illuminata | well, seems that just treating it as if the emmc flash worked did the trick |
| 18:11.42 | illuminata | so maybe it really did and just didn't report it as such |
| 18:13.34 | *** join/#maemo NIN102 (~NIN@p5DD2995A.dip0.t-ipconnect.de) |
| 18:19.43 | kerio | when calibrating bq27k, it's better to have a steady, low-ish drain instead of a jittery but stronger drain, right? |
| 18:21.48 | DocScrutinizer05 | yes |
| 18:22.39 | kerio | why does it make a difference, though |
| 18:22.40 | kerio | ? |
| 18:24.48 | *** join/#maemo MacDrunk (~marper@201.164.180.247) |
| 18:25.07 | *** part/#maemo MacDrunk (~marper@201.164.180.247) |
| 18:33.23 | DocScrutinizer05 | due to internal impedance, it will reach EDV1 sooner or later, depending on hifger or lower current |
| 18:33.31 | DocScrutinizer05 | higher* |
| 18:34.50 | kerio | should EDV1 be reached with the lowest possible current consumption, to calibrate the battery more accurately? |
| 18:35.13 | DocScrutinizer05 | also in cery bursty load you might encounter a situation where system shuts down due to minimum voltage for system tripped before EDV1 had time to "stabilize" (needs some 10s or so to get detected) |
| 18:35.39 | DocScrutinizer05 | kerio: the calibration will be 100% exact for the current it's done with |
| 18:36.18 | kerio | i see |
| 18:36.19 | DocScrutinizer05 | so if you want to calibrate your device for idle standby time, you should use a load similar to idle load |
| 18:37.06 | kerio | hm, is screen at max brightness similar to screen at low brightness + irc over 3g? |
| 18:37.23 | kerio | meh, i don't really care anyway |
| 18:37.29 | DocScrutinizer05 | if you are more interested in TTE at maximum load, use maximum load for calibration |
| 18:37.51 | DocScrutinizer05 | yes, kinda |
| 18:45.50 | *** join/#maemo freemangordon (~freemango@130.204.50.168) |
| 18:47.14 | *** join/#maemo hardaker (~hardaker@75-101-67-197.dsl.dynamic.omsoft.com) |
| 18:48.23 | kerio | DocScrutinizer05: hrmpf, calculating AI is actually pretty hard :s |
| 18:54.07 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 19:08.38 | *** join/#maemo thuttu77 (~thuttu77@cs181246145.pp.htv.fi) |
| 19:10.01 | *** join/#maemo flo_lap (~fuchs@sign-4d094984.pool.mediaWays.net) |
| 19:10.02 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 19:29.37 | *** join/#maemo gomiam (~magao@89.128.139.188) |
| 19:41.57 | *** join/#maemo Kilroo (~Kilroo@cpe-098-026-200-222.triad.res.rr.com) |
| 19:44.35 | *** join/#maemo Timmy (~quassel@37.254.22.248) |
| 19:44.35 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 19:49.09 | freemangordon | ~seen zeq |
| 19:49.12 | infobot | zeq <~s_j_newbu@2a01:348:1e3:1:e6ec:10ff:fe9a:d418> was last seen on IRC in channel #maemo, 11d 2h 27m 27s ago, saying: 'see you later DocScrutinizer05 '. |
| 19:55.41 | ZogG_laptop | ~seen Elop |
| 19:55.42 | infobot | elop <~outlawart@d24-150-93-26.home.cgocable.net> was last seen on IRC in channel #meego, 122d 16h 38m 19s ago, saying: 'I still keep in touch with engineers at Espoo'. |
| 19:57.03 | Sicelo | wut? :D |
| 20:23.13 | *** join/#maemo ferdna (~ferdna@cpe-67-10-220-35.elp.res.rr.com) |
| 20:27.34 | *** join/#maemo robbiethe1st (~robbiethe@70-57-165-156.spkn.qwest.net) |
| 20:29.44 | DocScrutinizer05 | ~seen stevenelop |
| 20:29.46 | infobot | DocScrutinizer05: i haven't seen 'stevenelop' |
| 20:29.55 | DocScrutinizer05 | ~seen stefenelop |
| 20:29.55 | infobot | i haven't seen 'stefenelop', DocScrutinizer05 |
| 20:30.26 | DocScrutinizer05 | ~seen stephenelop |
| 20:30.26 | infobot | DocScrutinizer05: i haven't seen 'stephenelop' |
| 20:30.36 | DocScrutinizer05 | incredible |
| 20:31.02 | stephenelop | see me now, stupid bot? |
| 20:34.38 | *** join/#maemo piggz__ (~piggz@host-92-18-202-200.as13285.net) |
| 20:39.49 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 20:51.52 | *** join/#maemo user__ (~user@31.185.137.96) |
| 20:53.01 | *** join/#maemo shamus (~shamus@ip-206-192-195-49.marylandheights.ip.cablemo.net) |
| 20:54.42 | user__ | what have I missed |
| 20:54.44 | user__ | ? |
| 20:58.08 | *** join/#maemo kodomo (~gregor@g225040046.adsl.alicedsl.de) |
| 21:02.17 | DocScrutinizer05 | to change your nick to something less lame? |
| 21:03.22 | vi___ | DocScrutinizer05: you are killing all fun |
| 21:04.28 | DocScrutinizer05 | killing fun is so much fun |
| 21:05.36 | *** join/#maemo brzys (~brzys@86-63-126-137.sta.asta-net.com.pl) |
| 21:06.53 | OxDEADBEEF | so nothing is new then? |
| 21:09.48 | OxDEADBEEF | dont go and see that new movie 'the raven' |
| 21:09.58 | OxDEADBEEF | it sucks so many asses. |
| 21:24.52 | *** join/#maemo GNUton-BNC (~gnuton@81-197-75-61.elisa-mobile.fi) |
| 21:27.32 | ZogG_laptop | DocScrutinizer05: u are not Elop's buddy, you can't call him by name? |
| 21:27.50 | ZogG_laptop | vi_: sold your n950? |
| 21:30.00 | ZogG_laptop | ~seen MohammadAG |
| 21:30.02 | infobot | mohammadag <~MohammadA@Maemo/community/contributor/MohammadAG> was last seen on IRC in channel #harmattan, 1d 6h 8m 23s ago, saying: 'if the screen is off the device is probably locked'. |
| 21:34.28 | *** join/#maemo calvaris (~calvaris@dslb-088-073-144-099.pools.arcor-ip.net) |
| 21:42.19 | *** join/#maemo philipl (~mrkiasu@c-67-188-112-44.hsd1.ca.comcast.net) |
| 21:43.25 | DocScrutinizer05 | robbiethe1st: |
| 21:43.28 | robbiethe1st | ? |
| 21:43.46 | DocScrutinizer05 | [2012-09-02 23:38:09] <DocScrutinizer05> DANG! there's a armel fiaco-gen pkg!!! |
| 21:43.53 | *** join/#maemo ponyofdeath (~vladi@cpe-75-80-169-76.san.res.rr.com) |
| 21:44.13 | robbiethe1st | Link? |
| 21:44.13 | DocScrutinizer05 | [2012-09-02 23:39:10] <DocScrutinizer05> so BM might *finally* learn to create proper self-containing fiasco images - incl kernel and all \o/ |
| 21:44.23 | DocScrutinizer05 | http://maemo.org/packages/view/sdk-fiasco-gen/ |
| 21:44.32 | kerio | robbiethe1st: do eeeeeeet |
| 21:45.07 | kerio | robbiethe1st: also, can you fix the thing where i can't access the shell inside BM because both root's and user's login shells are bash? |
| 21:45.20 | DocScrutinizer05 | [2012-09-02 23:40:07] <DocScrutinizer05> could even create a shellscript for x86 that even contains flasher-3.5 --- BM "create full fiasco". ass rage copy BMfiasco_2012-09-02.sh to PC. In case of desaster just run it in shell --- or store to uSD in N900. In case swap uSD to PC and run BMfiasco_2012-09-02.sh to restore |
| 21:45.52 | kerio | DocScrutinizer05: it's not that easy to make ubifs images |
| 21:46.13 | DocScrutinizer05 | ummm |
| 21:46.34 | kerio | ubi is /weird as fuck/ |
| 21:46.42 | robbiethe1st | Actually, good point there. I've done it a couple times; I forget what I had to do exactly, but it required a Linux PC as well... |
| 21:51.43 | DocScrutinizer05 | I'd guess finding out about how to create ubi image from a ubifs device like / should be possible |
| 21:52.18 | robbiethe1st | Check first page of my bm topic |
| 21:52.33 | DocScrutinizer05 | if we mamange to create rootfs image from fresh device that's identical to one image extracted from fiasco, we should be fine with modified rootfs as well |
| 21:52.45 | *** join/#maemo Kilroo (~Kilroo@cpe-098-026-200-222.triad.res.rr.com) |
| 21:53.25 | DocScrutinizer05 | robbiethe1st: check for what specifically? |
| 21:53.36 | robbiethe1st | I've already /made/ a flashable rootfs |
| 21:53.42 | DocScrutinizer05 | mhm |
| 21:53.59 | DocScrutinizer05 | not extracted from fiasco biut actually *made*? |
| 21:54.07 | robbiethe1st | It's just not quite as compressed(IIRC), and also reqired a Linux PC with a specific version of mtd-utils to do it |
| 21:54.08 | robbiethe1st | Yup |
| 21:54.15 | kerio | oh, from the files |
| 21:54.16 | kerio | neat |
| 21:54.28 | kerio | ...wait, mtd-utils? |
| 21:54.30 | kerio | no |
| 21:54.39 | kerio | you don't flash ubi volumes like that :S |
| 21:54.39 | DocScrutinizer05 | pah! we'll get that special version of mtd-tools to N900 |
| 21:55.08 | DocScrutinizer05 | actually you might |
| 21:55.35 | DocScrutinizer05 | mtd-read might be involved into the trick, but I fail to see how that's running on X86 then |
| 21:55.39 | kerio | no, you're supposed to ubimkvol and ubiupdatevol or something |
| 21:55.52 | robbiethe1st | see http://talk.maemo.org/showthread.php?t=63975&page=1 "Can I restore my BackupMenu images through the Nokia Flasher?" |
| 21:55.58 | DocScrutinizer05 | kerio: you're a real delight today |
| 21:56.03 | kerio | http://www.linux-mtd.infradead.org/faq/ubifs.html#L_mkfubifs |
| 21:56.09 | kerio | ty |
| 21:56.26 | robbiethe1st | Uses mkfs.ubifs / ubinize to make it |
| 21:57.10 | kerio | then it's cool :D |
| 21:57.23 | robbiethe1st | Which come from mtd-utils. |
| 21:57.35 | kerio | ...it's still in mtd-utils? :o |
| 21:57.50 | kerio | huh, it is |
| 21:57.55 | robbiethe1st | On Ubuntu(as of the time I wrote it)? Yes |
| 21:58.11 | kerio | yep, same on debian |
| 21:58.50 | robbiethe1st | Heck, want to do something? Make a nice little script that can turn a BM rootfs tarball into a flashable image on device. |
| 21:59.09 | DocScrutinizer05 | mkfs.ubifs -m 2048 -e 129024 -c 2047 -R 4MiB -r ./rootfs/ -v ./base.ubi.img |
| 21:59.22 | DocScrutinizer05 | should work on N900 in BM 'live' |
| 21:59.42 | DocScrutinizer05 | ubinize -o ./rootfs.img ubinize.cfg -m 2048 -p 128KiB -s 512 |
| 21:59.48 | DocScrutinizer05 | no need for PC |
| 22:00.00 | DocScrutinizer05 | just need "working" mtd-utils on N900 |
| 22:00.04 | robbiethe1st | ^^ |
| 22:00.20 | DocScrutinizer05 | actually working mkfs.ubifs and ubinize |
| 22:00.20 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 22:00.50 | kerio | well, the binaries are there |
| 22:01.04 | kerio | but they're not in the BM chroot jail - would they have to be in ram? |
| 22:01.06 | *** join/#maemo mva (mva@im.pirate-party.ru) |
| 22:01.20 | DocScrutinizer05 | probably |
| 22:02.43 | DocScrutinizer05 | yep, ubinize and mkfs.ubifs are available here as well |
| 22:03.28 | kerio | the thing is, it's better for the flash to do what BM has been doing |
| 22:03.42 | DocScrutinizer05 | hmm? |
| 22:03.52 | kerio | ubifs does wear levelling and keeps track of writes |
| 22:04.04 | DocScrutinizer05 | we're not writing to ubifs |
| 22:04.09 | DocScrutinizer05 | we're reading it |
| 22:04.15 | kerio | no, i mean |
| 22:04.21 | kerio | it's better to do rm -rf and then cp |
| 22:04.32 | kerio | i think |
| 22:04.36 | DocScrutinizer05 | heh? |
| 22:05.02 | DocScrutinizer05 | how's that fitting into flasher-3.5 -f -F myBMfiasco.bin ? |
| 22:05.07 | kerio | ubifs keeps track of writes/erases and does wear-levelling based on that |
| 22:05.27 | kerio | flashing erases that information |
| 22:06.29 | *** join/#maemo Cor-Ai_ (~cor-ai@c-5743e253.67-8-64736c10.cust.bredbandsbolaget.se) |
| 22:06.54 | *** join/#maemo johnsu01` (user@gateway/shell/gnu/x-tdzkbspyldybijig) |
| 22:06.59 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 22:07.04 | DocScrutinizer05 | well, that's what flashing does |
| 22:07.55 | kerio | yeah |
| 22:07.59 | kerio | but it's better *not* to do that :) |
| 22:08.15 | DocScrutinizer05 | given there's a working wear leveling, there can't be a wear debit on any page. So flashing will just happen to an equally worn out NAND |
| 22:08.22 | *** join/#maemo fasta_ (~xchat@xs8.xs4all.nl) |
| 22:09.06 | DocScrutinizer05 | it's not like ubi will accumulate wear on one sector, to switch to next sector once the first one reached a certain threshold |
| 22:09.20 | kerio | no, quite the opposite :) |
| 22:09.39 | DocScrutinizer05 | so where's the info that gets lost on flashing? |
| 22:10.18 | DocScrutinizer05 | sure, flashing *might* write 20% more pages than cp * |
| 22:10.40 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 22:10.45 | DocScrutinizer05 | but hey, that's why it's called flashing |
| 22:11.26 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 22:12.17 | DocScrutinizer05 | and _for_sure_ flashing myBMfiasco.bin will be less wear to NAND than flashing fiasco-combined-2010-36-2.bin with an *additional* restore cp * from BM |
| 22:12.29 | kerio | hm |
| 22:12.36 | kerio | meh, that's a good point |
| 22:12.40 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 22:12.58 | kerio | robbiethe1st: feature request: BM that can be loaded in ram from flasher |
| 22:13.17 | kerio | that would be *sweet* |
| 22:13.21 | DocScrutinizer05 | huh? |
| 22:13.55 | kerio | DocScrutinizer05: rescue-os but with backupmenu |
| 22:14.02 | DocScrutinizer05 | if your fs is corrupt, no BM untar will correct that |
| 22:14.26 | kerio | DocScrutinizer05: only the rootfs can be corrupt |
| 22:14.32 | kerio | i mean |
| 22:14.38 | kerio | DocScrutinizer05: only the rootfs can be corrupt and cause a problem |
| 22:14.49 | kerio | optfs is mkfsed |
| 22:14.55 | DocScrutinizer05 | sure |
| 22:15.36 | DocScrutinizer05 | so it's again flashing ubi that does a lot of magic (also flashing vfat btw, since that's a PITA to fsck) |
| 22:15.39 | kerio | and if i had a working shell in backupmenu, i could remake the rootfs ubifs |
| 22:17.49 | DocScrutinizer05 | I'd adore a DamnSmallLinux with a self-comprised BM flasher-3.5 and fiasco shell script, preferrably both as .iso to burn to mini-CD as well as in any other suitable form to make me happily restore on whatever PC I can get hold of |
| 22:18.21 | DocScrutinizer05 | e.g as bootable partition on uSD |
| 22:19.22 | kerio | DocScrutinizer05: and maybe find a way to use bootmenu's MSM to boot the pc from the n900 itself! |
| 22:19.23 | kerio | >:D |
| 22:19.30 | DocScrutinizer05 | probably restoring was even faster than doing backup then |
| 22:20.24 | DocScrutinizer05 | well, that's a bit of a vicious circle, since N900 considered flawed when we wnat to run this backup menu restorer |
| 22:21.13 | DocScrutinizer05 | keeping partition1 VFAT on uSD bootable though can't be much of a problem |
| 22:21.29 | DocScrutinizer05 | bootable under X86 |
| 22:21.47 | DocScrutinizer05 | and using a uSD cardreader keyring |
| 22:22.20 | DocScrutinizer05 | I'm carrying one on me since >4 years now iirc |
| 22:26.18 | *** join/#maemo Sazpaimon_ (~wat@pool-68-238-249-133.phlapa.fios.verizon.net) |
| 22:34.14 | DocScrutinizer05 | dafaq I'm not getting anymore what's going on with my PC network. br0 WTF?! |
| 22:35.58 | *** join/#maemo DrGrov (~C.J@unaffiliated/drgrov) |
| 22:36.13 | *** part/#maemo DrGrov (~C.J@unaffiliated/drgrov) |
| 22:37.01 | DocScrutinizer05 | googles ifconfig br0 |
| 22:38.04 | DocScrutinizer05 | ooooh xen FFS |
| 22:47.04 | jacekowski | that's bridge |
| 22:47.08 | jacekowski | not only xen thing |
| 22:51.23 | *** join/#maemo dev (~dev@itc-scholz.de) |
| 23:00.42 | *** join/#maemo dev (~dev@itc-scholz.de) |
| 23:00.55 | robbiethe1st | kerio, can you test something for me? |
| 23:01.32 | robbiethe1st | Go into /usr/share/backupmenu/extrafiles.tar.gz, edit filelist.txt and add the line: "ln -s /tmp/disk/bin/sh /tmp/disk/bin/bash" at the bottom. |
| 23:01.57 | robbiethe1st | save/retar, boot into backupmenu and see if you can now access the shell |
| 23:06.42 | stardiviner | I find the default root shell /bin/sh does not read $HOME/.bashrc config file, I want to add some path into $PATH, let root shell read them at startup time, what should I do ? change the SHELL of root into bash ? or something else ? |
| 23:15.33 | robbiethe1st | hm |
| 23:15.57 | robbiethe1st | DocScrutinizer05, this would be your area of experties, i think |
| 23:16.09 | *** join/#maemo johnsu01` (user@fsf/staff/johnsu01) |
| 23:21.16 | Skry | robbiethe1st: use .profile |
| 23:21.38 | robbiethe1st | not me, but... |
| 23:21.48 | Skry | oops :) |
| 23:22.06 | Skry | stardiviner: use .profile |
| 23:36.53 | stardiviner | Skry: thanks |
| 23:41.29 | Skry | np |