**** BEGIN LOGGING AT Thu Jan 09 02:59:58 2014 Jan 09 03:35:40 DocScrutinizer05, I just found your yesterday nights reply. thanks Jan 09 06:03:23 hello people - i have asked this already but this time with more clarity... Is it possible to make my n900 as a access/swipe card to open doors ? Jan 09 06:03:41 i would like to replace my access card to office with n900 Jan 09 06:19:46 usually.. no. making another device as an access device is the equivalent of duplicating a key, and that's exactly what they don't want people doing... that being said if you understand the access system enough, anything's possible... Jan 09 07:55:59 btw, lats time I've attempted Thumb version of CSSU, it borked Fcam drivers. Is it fixed now? Jan 09 07:56:33 no, and I guess it is a WONTFIX Jan 09 07:56:50 hmm? why? Jan 09 07:57:06 this warrants I would stay miles away from that thumb stuff then :\ Jan 09 07:57:08 because the problem is woth fcam kernel module Jan 09 07:57:14 *with Jan 09 07:57:44 what's wrong with this module? oO Jan 09 07:57:49 t3st3r: in extras-devel there is such module which is compatible with both KP and cssu-thumb Jan 09 07:58:18 what is KP? Power Kernel? Jan 09 07:58:20 t3st3r: it refuses to load (or similar) on not-omap1 kernel Jan 09 07:58:22 yes Jan 09 07:58:38 [11:58:27] t3st3r: it refuses to load (or similar) on not-omap1 kernel <- so it does some checks? Jan 09 07:58:49 NFC what it does Jan 09 07:58:54 but I doubt Jan 09 07:59:02 it checks for the kernel version Jan 09 07:59:46 t3st3r: wht you can try - install KP52, install fcam drivers from extras-devel Jan 09 07:59:56 at that point your camera should be fine Jan 09 08:00:11 if it is fine, install cssu-thumb Jan 09 08:07:14 What - NFC? Jan 09 08:07:42 [11:59:53] t3st3r: wht you can try - install KP52, install fcam drivers from extras-devel <- hmm, is it compatible with thumb? Jan 09 08:10:38 nfc=no * clue Jan 09 08:11:17 solofight: not easily and not natively either, but it is possible to make an object (N900) into a access card. Jan 09 08:22:18 sixwheeledbeast: make n900 into a access card ? thats exactly what i want to do Jan 09 08:22:24 sixwheeledbeast: ideas please Jan 09 08:28:36 ecc3g: http://computer.howstuffworks.com/question662.htm correct place ? Jan 09 08:28:42 to understand it better ? Jan 09 12:43:39 DocScrutinizer: infobot joined! Jan 09 12:55:26 Hello everyone, would anyone mind helping me out? I just received my (secondhand) N900 in the mail. The battery seems fully empty, and when I supply power (over wall plug) it first charges autonomously for a minute or two (non-flashing orange LED), then boots up (bright Nokia screen, flashing orange LED), stays on the Nokia screen for a few seconds (about 10; screen darkens afterwards), and after about half a minute crashes (no LED at all) - only to Jan 09 12:55:26 reboot shortly after (bright Nokia screen again, LED flashes again), it stays in this state for 10 seconds or so, then turns off (no LED again), stays off for ~20 seconds, then starts in autonomous mode again (non-blinking LED). This pretty much repeats forever (or well, I've seen it happen ~5 times now). Jan 09 12:55:31 I assume this is the dreaded bootloop? Jan 09 12:55:50 I found this: http://web.fournier.nl/2012/07/nokia-n900-charging-depleted-battery.html -- is it worth trying? Jan 09 12:56:47 Or is there a way I can just prevent the device from leaving autonomous-mode charging? I wanted to reflash it anyways, but it needs a charged battery for me to do so. Jan 09 13:01:34 i don't know of a way to prvent it from leaving autonomous Jan 09 13:07:49 I probably need an external charger or another phone then. Jan 09 13:08:05 It's tempting to try the trick I linked to, but I don't want to risk bricking my 'new' phone. Jan 09 13:08:29 If it's boot looping it's already what people call "bricked" Jan 09 13:09:09 You can still reflash a bootlooping device, right? Jan 09 13:10:35 Can I charge the device while in 'reflashing mode' (having pressed U and all that)? Jan 09 13:10:40 no Jan 09 13:10:56 or, "probably not" Jan 09 13:12:18 I'm not even 100% sure it's actually "bootlooping", some users on the Maemo-forums suggest it's an issue with power drain spiking on boot and the phone switching back to autonomous mode. Jan 09 13:14:52 I guess I'll try the rescue image in this case, will report back. Jan 09 13:15:41 I get a new battery every year or so, they wear out kinda fast Jan 09 13:18:34 Guess it might be a worn-out battery that's to blame. Jan 09 13:24:13 Back in a bit, rebooting my PC to allow loading unsigned drivers. Jan 09 13:35:32 ~flatbatrecover Jan 09 13:35:32 Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber going off - in this case start over again with ~flatbatrecover. CAVEAT! Only works when ~rootfs is OK (no ~bootloop)!. Jan 09 13:35:49 Satorin, ^^ I guess Jan 09 13:51:54 Thank you SAiF! I'll try that first. Jan 09 13:54:16 ~bootloop Jan 09 13:54:17 bootloop is, like, when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing. E.g. using ~rescueOS. Or external charger or BL-5J compatible other device. Jan 09 13:54:52 Okay, will first wait 30 minutes to try flatbatrecover, if that fails I'll go the rescueos route! Jan 09 13:56:48 Satorin: the "trick" is pretty sane, it's a proven rescueOS based battery charging it seems, after cursory look. No way you could do additional damage by that Jan 09 13:57:03 flatbatrecover won't help Jan 09 13:57:54 watching the device bootlooping for 30 min doesn't help either Jan 09 14:13:42 Seems you're right, trying rescueos flash now. Jan 09 14:18:51 the thing Satorin describes also happened for me under any kind of KP Jan 09 14:18:55 just saying Jan 09 14:18:55 Okay, I connected to the PC as per instructions, but it's not flashing (reports as "(Storage mode)", and yes, I am keeping 'u' pressed on connect). Strange thing is: The orange LED /does/ flash now, indicating a charging state. Jan 09 14:19:14 I only got it in the mail today, no clue what's on it Jan 09 14:19:29 i.e. if charging when device was off, it would proceed to boot, show nokia logo, minor delay, then crash and reboot, ad infinitum Jan 09 14:19:37 allthough you should probably reflash regardless Jan 09 14:19:43 so that it's clean Jan 09 14:20:14 not saying the device is running KP Jan 09 14:20:32 but rebootloop during charging doesn't necessarily mean dead device is what I'm saying Jan 09 14:21:15 when amber led flashing: KEEP it! Jan 09 14:21:19 let it charge Jan 09 14:21:52 don't change anything! Jan 09 14:22:01 I will! Jan 09 14:22:07 until battery full, and then an hour on top Jan 09 14:22:15 It charges from USB now, or so it seems... Wall-plug gave issues. Jan 09 14:22:22 only then go do a full reflash Jan 09 14:22:45 is that the original nokia wallcharger plug? Jan 09 14:23:21 (not that I haven't seen issues with Nokia charger too) Jan 09 14:23:41 but a 3rd party wallcharger may be incompatible by design Jan 09 14:23:45 No, it has equal power specs though. Jan 09 14:23:54 Well, I'm happy with the blinking LED now. ^^' Jan 09 14:23:57 that doesn't say much Jan 09 14:24:19 3rd party chargers often miss the mandatory D+/- line short Jan 09 14:24:30 resulting in charging failing Jan 09 14:25:08 That sounds like it might be the issue... Jan 09 14:25:12 yep Jan 09 14:25:19 problem solved Jan 09 14:25:22 :-) Jan 09 14:25:55 It boots over usb, too. Jan 09 14:28:26 yes, blinking amber basically means it *has* booted Jan 09 14:29:29 I'm actually in the OS now! Time to let it charge before doing a reflash. Thanks! Jan 09 14:29:35 there's a mode called "ACT_DEAD" that pretends the device is off and only charging, but in fact the linux is fully booted up and just on a different ->runlevel Jan 09 14:30:10 Ah! I see how that works now... Jan 09 14:30:38 :-) Jan 09 14:31:11 oh, and welcome to the club! :-) Jan 09 14:31:17 Oh wow, the seller sure didn't reflash it... I'm getting emails. Jan 09 14:31:25 Thanks a lot! Jan 09 14:31:25 LOL!!!! Jan 09 14:32:49 you should "switch off" again, I.E. enter act_dead, it is charging waay faster since no WLAN, display and other stuff eats power the battery needs for charging Jan 09 14:33:23 I will, thanks for the suggestion. ^^ Jan 09 14:33:24 worst case the system can eat more power than the USB can provide, effectively DIScharging the battery Jan 09 14:34:13 sometimes the system tells you about that problem with a yellow notifier saying "insufficient power" OWTTE Jan 09 14:34:23 sometimes not Jan 09 14:35:30 Mhm, well, I've turned it off now. Jan 09 14:35:52 14 unread mails, the old owner seems to be a sysadmin. Darn, it really deserves a reflash. Jan 09 14:35:59 I'll wait 'till the LED turns green. Jan 09 14:38:03 you're aware of Jan 09 14:38:06 +flashing Jan 09 14:38:13 ~flashing Jan 09 14:38:13 extra, extra, read all about it, maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware Jan 09 14:38:16 ? Jan 09 14:38:26 I read through it! Jan 09 14:38:28 Seems doable. Jan 09 14:38:38 I'm looking to install CSSU-Testing (Thumb). Jan 09 14:39:12 the most concise and precise description is at the end, under "troubleshooting". However please read the *complete* page first Jan 09 14:39:59 and please first make friend with the default/standard system, not going to install lots of stuff, especially not CSSU and/or stuff from extras-devel repos Jan 09 14:40:31 then after a week or so come back here asking for the leet stuff ;-) Jan 09 14:40:49 there are a few pitfalls, stuff you should steer clear from Jan 09 14:41:14 That sounds like some solid advice. Jan 09 14:41:23 The wiki is awesome! Jan 09 14:41:36 and a few annoying little bumps in the road that are easily avoided or handled with a word of help from an experienced user Jan 09 14:43:11 and probably the very first thing you should install is Jan 09 14:43:13 +bm Jan 09 14:43:18 dang!! Jan 09 14:43:20 ~bm Jan 09 14:43:21 from memory, backupmenu is http://talk.maemo.org/showthread.php?t=63975 Jan 09 14:43:53 then cpu load applet and simple brightness applet Jan 09 14:44:04 Backupmenu seems like a must-have indeed. :P Jan 09 14:44:50 what's your level of expertise re general linux? Jan 09 14:44:56 shell? Jan 09 14:46:55 when you're a shell tinkerer, then this might be a nice starting point, after a few days of learning to know stock maemo: Jan 09 14:46:58 ~jrtools Jan 09 14:47:00 it has been said that jrtools is http://wiki.maemo.org/User:Joerg_rw/tools Jan 09 14:47:26 I'd say very familiar. Jan 09 14:47:32 * Satorin takes a look. Jan 09 14:47:43 when you are not familiar and friend with shell, then don't even bother reading that Jan 09 14:48:59 oh, and: maemo is NOT debian, particularly when it comes to apt and dpkg and package management at alrge Jan 09 14:49:02 large* Jan 09 14:49:58 do *not* use apt/dpkg until you understand the differences between maemo and a "normal" debian system Jan 09 14:50:44 inside hint: the dependencies in maemo repositories are mostly fubar Jan 09 14:50:58 I'll have to look into the differences concerning apt-get indeed, as I'm very used to the Debian way. Jan 09 14:51:10 whole maemo fremantle is basically one large metapackage Jan 09 14:51:16 Some neat info on the jrtools wiki page! Jan 09 14:51:23 thanks Jan 09 14:52:33 ~mp Jan 09 14:52:34 somebody said mp was Northern Mariana Islands Jan 09 14:52:39 meh Jan 09 14:53:38 ~listkeys #maemo mp Jan 09 14:53:39 Factoid search of '#maemo mp' by key returned no results. Jan 09 14:53:44 ~listkeys #maemo Jan 09 14:53:46 Factoid search of '#maemo' by key (16 of 72): #maemo awesome-keymap ;; #maemo bootloop ;; #maemo cal ;; #maemo cmtfix ;; #maemo db ;; #maemo debhelper7 ;; #maemo expired-key ;; #maemo flopswap ;; #maemo getversion ;; #maemo hamvsfam ;; #maemo mirrors ;; #maemo must ;; #maemo mustn't ;; #maemo oh ;; #maemo omp ;; #maemo pkgs. Jan 09 14:53:52 Looking forward to tinker with all that stuff. Jan 09 14:53:57 * Satorin stares at the blinking LED. Jan 09 14:54:02 :-D Jan 09 14:55:29 *maybe* you want to install BM and do a backup of the current system, just in case. Before you're going to flash the device Jan 09 16:22:55 Hello, what is the "open source bme replacement" I'm hearing about? Jan 09 16:23:10 hxka: hmm? Jan 09 16:23:10 Is it the bq27x00_battery module? Jan 09 16:23:13 no Jan 09 16:24:07 it is battery module+charger module+rx51_battery module+isp1704 module+hal addon+libbmeipc+the applet :) Jan 09 16:25:07 hxka: https://gitorious.org/rx51-bme-replacement Jan 09 16:27:41 Oh, thanks Jan 09 16:30:06 What do I need to do to use it besides "stop bme; modprobe bq27x00_battery bq2415x_charger rx51_battery"? Jan 09 16:30:39 hxka: this is *replacement* ;) Jan 09 16:31:18 Um Jan 09 16:31:24 anyone managed to set up a NFSv4 mount with rpcbind and idmapd ? rpcbind does not seem to be packaged yet, but there may be a good reason for that. Anyone with more information about it ? Jan 09 16:31:59 hxka: pull the source code from gitorious, dpkg-buildpackage it and install it Jan 09 16:32:17 hxka: kerneel modules are provided by KP52 Jan 09 16:32:22 kernel even Jan 09 16:32:58 Oh, so it's not already packaged Jan 09 16:33:24 hxka: it could be, but it is Pali that maintains that Jan 09 16:33:51 and he is MIA for some time (his laptop is broken and waits for repairs) Jan 09 16:34:06 ~pali Jan 09 16:34:07 rumour has it, pali is http://atrey.karlin.mff.cuni.cz/~pali/ Jan 09 16:34:40 hxka: but seems he is a good boy http://atrey.karlin.mff.cuni.cz/~pali/projects/maemo/bme-replacement.html Jan 09 16:34:43 :) Jan 09 16:35:11 ~bme-replacement Jan 09 16:35:11 hmm... bme-replacement is http://atrey.karlin.mff.cuni.cz/~pali/rx51-bme-replacement http://atrey.karlin.mff.cuni.cz/~pali/projects/maemo/bme-replacement.html See also: http://wiki.maemo.org/Bme_replacement . Please, use wiki page to report bugs/problems and/or solutions to them! Jan 09 16:35:33 hxka: I think you have everything now :) Jan 09 16:35:59 oh, that is debian repo actually Jan 09 16:36:52 freemangordon: Great, thanks :) Jan 09 16:37:47 peetah: I don't know of any "good reason" Jan 09 16:38:30 peetah: IOW I guess it's simply not build yet Jan 09 16:38:49 nobody took care to do Jan 09 16:39:26 but maybe I just don't know of that good reason despite such reason may exist Jan 09 16:39:51 freemangordon: ^^^ any info? Jan 09 16:40:12 DocScrutinizer05: ok I'll try make my own then, and if I succeed that will give me a good reason to practice maemo packaging Jan 09 16:40:25 :-) Jan 09 16:40:25 DocScrutinizer05: no Jan 09 16:40:30 that's the spirit Jan 09 16:40:42 DocScrutinizer05: don;t forget I am not linux admin :) Jan 09 16:41:05 peetah: will be cool to upload it to repos if you manage to make it run Jan 09 16:41:10 yeah i know Jan 09 16:41:24 freemangordon: sure, that was my pont Jan 09 16:41:30 s/pont/point Jan 09 16:42:10 Finally charged and backupped! It's flashing time~ Jan 09 16:42:49 on a sidenote: some nice read about maemo community spirit (and Neo900), among other more general considerations: http://culturedigitally.org/2014/01/spam-and-the-challenge-of-chasing-shadows/ Jan 09 16:43:43 Satorin: Also note to restore a backup with backupmenu you have to be on the same kernel as the backup image. Jan 09 16:44:53 Good to know. I'm on the latest stock kernel, though CSSU-Thumb will replace that. Jan 09 16:48:11 sixwheeledbeast: Not quite. You can restore a backup with any working kernel. To be able to boot after that, yes, you need to have same kernel flashed :P Jan 09 16:48:29 correct :) Jan 09 16:49:22 well, that's what I mean. Why would you want a non bootable device? Jan 09 16:49:45 I learned that the hard way and had to flash the kernel with flasher Jan 09 16:50:49 sixwheeledbeast: You wouldn't, I'm just nitpicking Jan 09 16:51:06 :P Jan 09 16:54:29 It would be nice to have some warning I agree. Jan 09 16:55:31 Yes. CSSU-Thumb will need a kernel with errata workaround. Jan 09 17:23:18 http://pix.apic.name/Kleinerdrei.jpg Jan 09 18:20:02 can anyone lend a hand with bash / sed? Jan 09 18:29:48 MohammadAG, hi, Jan 09 18:30:25 hi Jan 09 18:45:26 MohammadAG: What do you mean? Jan 09 18:45:54 I need to remove all spaces before special characters Jan 09 18:46:02 for example, ! ? , etc Jan 09 18:46:21 I can match this with \s[\.!?;] Jan 09 18:46:46 sed 's/ \([!?,]\)/\1/g' Jan 09 18:46:47 basically, I want sed 's/\s[\.!?;]/[\.!?;]/g' Jan 09 18:47:30 sed 's/ \([\.!?;]\)/\1/g' then Jan 09 18:47:31 oh hey, that worked Jan 09 18:47:45 I don't understand how though :p Jan 09 18:48:31 \1 gets replaced with first matched group, thai is everything between \( and \) Jan 09 18:49:15 (in that case) Jan 09 18:49:37 wow MohammadAG! long time no see! :-) Jan 09 18:53:01 thanks hxka :D Jan 09 18:53:14 yay Jan 09 18:53:20 DocScrutinizer05, hi! Jan 09 18:53:25 I've been busy with life Jan 09 18:53:35 (and *lowers head* android) Jan 09 18:54:01 hxka, I'm actually helping someone out with his assignment Jan 09 18:56:08 hxka, this is the crap I came up with http://pastebin.com/FF23s5xJ Jan 09 18:56:30 I'd rate it 1 in a scale of 1-10 crappiness Jan 09 18:57:17 ISP problems, can't reach pastebin.com :( Jan 09 18:59:52 Reflashed succesfully, now installing CSSU! ^_^ Jan 09 19:01:50 hxka, http://mohammadag.xceleo.org/blablabla.sh Jan 09 19:05:25 MohammadAG: You probably don't want to uppercase chars after `;'. Jan 09 19:08:40 Wait, that was in the assignment. Nevermind. Strange though. Jan 09 19:09:15 hxka, indeed Jan 09 19:09:21 grammatically it looks; Weird Jan 09 19:09:39 plus it doesn't make sense to have else after it Jan 09 19:10:23 MohammadAG: hi! where you'veen hiding, man? Jan 09 19:10:33 *been Jan 09 19:11:00 between some Jelly Beans :p Jan 09 19:11:06 and life Jan 09 19:11:37 oh dear. how's on the dark side of the force? Jan 09 19:12:09 It's actually not bad Jan 09 19:12:16 once you get past the lack of some tools Jan 09 19:12:17 I miss nano Jan 09 19:12:41 only nano? Jan 09 19:12:45 what about mc? Jan 09 19:13:29 Nope Jan 09 19:13:31 I never use that Jan 09 19:13:41 in fact, I've never useD that Jan 09 19:13:47 Mhm, strange, I opted to install CSSU Thumb, but under 'Product info' it states "21.2011.38-1Tmaemo9.1, flavor: Testing." Jan 09 19:13:50 I used ls + cp + mv on maemo Jan 09 19:13:54 I can live with them on Android Jan 09 19:14:06 Satorin: that's normal Jan 09 19:14:06 till my shell loses tab completion Jan 09 19:14:12 Oh, phew. Jan 09 19:14:16 Was afraid I messed something up. Jan 09 19:14:21 Satorin: oh, wait Jan 09 19:14:33 hahahaha Jan 09 19:14:33 you nedd to apt-get/apt-get upgrade Jan 09 19:14:40 need* Jan 09 19:14:55 upgrade from the xterminal or from HAM? Jan 09 19:15:11 right now -testing has higher version than -thumb (will fix that as soon as I have some spare time) Jan 09 19:15:24 Satorin: from xterminal Jan 09 19:15:39 Okay, will do! Jan 09 19:15:44 Satorin: or simply do: Jan 09 19:16:15 apt-get install mp-fremantle-community-pr=T-maemo9-thumb0 Jan 09 19:16:47 Satorin: wait Jan 09 19:16:51 apt-get install mp-fremantle-community-pr=21.2011.38-1Tmaemo9+thumb1 Jan 09 19:16:56 this is the correct version Jan 09 19:17:14 I see... will apt-get update/upgrade do the same, or should I set it manually with the above command? Jan 09 19:17:31 Satorin: both will do the same, but latter is safer Jan 09 19:18:02 I don;t know what repos you have enabled, so apt-get upgrade could do stuff it should not Jan 09 19:18:05 so: Jan 09 19:18:10 apt-get install mp-fremantle-community-pr=21.2011.38-1Tmaemo9+thumb1 Jan 09 19:18:17 I suppose I need root? Jan 09 19:18:22 :nod: Jan 09 19:18:25 I will run that. Thanks! Jan 09 19:18:40 Satorin: install rootsh if not already did so Jan 09 19:19:10 I didn't, but I'll do it now. It's a clean installation right now. Jan 09 19:19:15 Satorin: mark how much "space will be freed" :) Jan 09 19:19:25 freemangordon: to upgrade to the latest version of mp-fremantle-community-pr you can just run apt-get install mp-fremantle-community-pr Jan 09 19:19:40 And apt-get won't do anything unintended Jan 09 19:19:40 hxka: the latest is -testing Jan 09 19:19:56 and it won;t pull the correct packages Jan 09 19:20:01 then upgrade wouldn't fix that Jan 09 19:20:04 no Jan 09 19:20:11 it will Jan 09 19:20:25 hxka: just trust me on that one, ok? :) Jan 09 19:20:33 I gtg, night Jan 09 19:20:41 Thanks for your help, goodnight freemangordon :) Jan 09 19:21:22 anyone knows how to use openssl? Jan 09 19:32:57 freemangordon: Okay, I've just installed 21.2011.38-1Tmaemo9.1 version, and what do you think, apt-get upgrade doesn't want to revert it back to 21.2011.38-1Tmaemo9+thumb1, just as I said. Jan 09 19:40:35 Is there a neater fix for the expired keys than setting the time back? Jan 09 19:46:21 I'm running an apt-get upgrade, lets see. Jan 09 19:48:43 Done. No super-interesting packaged got pulled in at all. Jan 09 19:48:45 Still on testing. Jan 09 19:51:15 Satorin: you can still do apt-get install mp-fremantle-community-pr=21.2011.38-1Tmaemo9+thumb1 Jan 09 19:51:54 But this won't do anything significant besides changing the displayed version Jan 09 19:52:16 So technically I'm already using the thumb binaries? Jan 09 19:52:35 You were using them all along Jan 09 19:52:57 oh, great! Jan 09 19:53:03 Well, so far so good in that case. Jan 09 19:59:36 Satorin: mark how much "space will be freed" :) Jan 09 19:59:47 If only! It adds ~2000kb Jan 09 19:59:53 But that's because it's pulling in other packages. Jan 09 20:00:02 you should trust freemangordon, he's maintainer of cssu-thumb Jan 09 20:00:12 I do trust him, of course. :P Jan 09 20:00:58 and the warning to never do apt-get upgrade still applies Jan 09 20:01:23 more often than not it will NOT do what you expect it to do Jan 09 20:02:22 we already seen core libs getting replaced by fubar versions some funny guy uploaded to extras-devel or sth like that Jan 09 20:02:52 Oh, I see how that works now. Jan 09 20:02:58 Luckily everything seems to work fine for me, up to now. Jan 09 20:03:03 frequently users update their apps to latest but broken version from extras-devel or even cssu-devel Jan 09 20:03:53 and steer clear of fapman, it does even worse things, like apt-get autoremove Jan 09 20:04:09 The horror! Jan 09 20:04:26 I do get a notification of an updated metapackage now, but that's because I reverted to the thumb version... Jan 09 20:04:38 How do I make sure my binaries are actually the thumb ones now? Jan 09 20:05:05 yes, the cssu-testing metapackae is newer than the cssu-thumb metapackage, I guess Jan 09 20:05:30 by installing the cssu-thumb metapackage you pull in all the thumb stuff Jan 09 20:05:50 It didn't seem to pull in a lot. Jan 09 20:05:53 But that might be me. Jan 09 20:06:27 cssu-thumb is not exactly easy for users to handle Jan 09 20:07:25 Wait, so the metapackage is supposed to downgrade everything from the 'newer' testing-metapackage? Jan 09 20:07:28 I somehow doubt that happened. Jan 09 20:07:54 cssu-testing installs the cssu repo with a higher trustlevel than the core nokia repos, aiui. Thus it's warranted that HAM will update correctly and not roll back patches shipped by CSSU when a Nokia update ships Jan 09 20:08:26 for CSSU-thumb the situation is more complex since both cssu-T/S and cssu-thumb live in same repo Jan 09 20:09:15 just look into the MP what it pulls in, and how Jan 09 20:09:30 toldya dependencies in maemo are a horror show Jan 09 20:09:39 Hehe, I figured. Jan 09 20:09:49 It seems the metapackage doesn't pull in any other thumb-packages. Jan 09 20:10:00 Hell, I doubt I'm even on the thumb-kernel. Jan 09 20:10:11 uname -a Jan 09 20:10:53 Linux Nokia-N900 2.6.28.10-cssu3 #1 PREEMPT Sat Jul 28 18:05:05 EDT 2012 armv71 unknown Jan 09 20:10:55 that's a no. Jan 09 20:11:11 when you're not on thumbified kernel, the system would already explode into your face Jan 09 20:11:26 actually you're not Jan 09 20:11:29 It seems to hold up so far. :P Jan 09 20:11:37 It's just there are no thumb packages at all. Jan 09 20:11:40 Except for the metapackage itself. Jan 09 20:11:44 wait wut? Jan 09 20:11:56 It's what I think, but I'm the noob here... Jan 09 20:12:00 2.6.28.10-cssu3 wtf is that? Jan 09 20:12:32 get powerkernel! Jan 09 20:12:36 ~kp Jan 09 20:12:36 extra, extra, read all about it, kp is http://talk.maemo.org/showthread.php?t=89823 Jan 09 20:13:07 Yeah, I was planning on doing that since I want to overclock a tiny bit. Jan 09 20:13:09 might be the cssu thumb kernel, that's deprecated Jan 09 20:14:14 Installing the power kernel now. Jan 09 20:14:21 Though I doubt it does anything for the thumb packages. Jan 09 20:16:52 Well, now it says 2.6.28.10-power52 :P Jan 09 20:20:07 looks better though porbbaly almost same kernel Jan 09 20:20:14 probably Jan 09 20:21:25 there's a sysnode or proc or dev or whatever somewhere, where you could disable the thumb patch in kernel. If you're curious ;-P Jan 09 20:26:12 Well, yeah. Jan 09 20:26:24 Is there any way I can revert all applicable packages 'back' to the -thumb version? Jan 09 20:26:31 They're on -testing now, I'm pretty sure. Jan 09 20:37:11 do what freemangordon told ya Jan 09 20:39:36 I did everything I was instructed to already. Jan 09 20:39:45 It only downgrades the metapackage but doesn't pull in thumb binaries. Jan 09 20:39:51 The binaries on my system are the testing ones. Jan 09 20:39:53 :( Jan 09 20:44:04 "-cssu3" that's the kernel pulled in if you don't have KP Jan 09 20:44:09 for thumb Jan 09 20:45:27 it's practically KP Jan 09 20:45:54 I'm sure my system supports the thumb binaries now, but it doesn't run any of them because all the testing ones have a higher version. Jan 09 20:46:00 Satorin: short answer: noooooooooooo Jan 09 20:46:09 downgrading is Bad with a capital Bad Jan 09 20:46:26 long answer: pin the community-thumb repo at a priority higher than 1000 Jan 09 20:46:28 and upgrade Jan 09 20:46:34 That'd work? Jan 09 20:46:37 I'll try it right now. Jan 09 20:46:37 eyup Jan 09 20:46:55 apt won't consider downgrading unless the repo the packages are coming from has a priority higher than 1000 Jan 09 20:52:40 I tried, but the behavior of apt-get upgrade doesn't seem to change. Jan 09 20:52:48 I would have thought all thumb ones would be there. "dpkg-query -W osso-pdf-viewer" Jan 09 20:52:56 Oh wait. Jan 09 20:53:00 Let me check... Jan 09 20:55:05 or even "dpkg-query -W | grep +thumb" for a full list Jan 09 20:55:27 but osso-pdf-view was updated recently IIRC Jan 09 20:55:39 ~cssu-thumb Jan 09 20:55:40 well, cssu-thumb is [thumb2 microb] indeed seems to render like mad, subjectively, or http://talk.maemo.org/showpost.php?p=1220597, or http://wiki.maemo.org/Community_SSU/Thumb Jan 09 20:56:20 Tmaemo8.3+thumb2 it seems Jan 09 20:56:46 freemangordon can you update the changelog on wmo please :) Jan 09 21:00:45 ~312/5 Jan 09 21:00:45 62.4 Jan 09 21:01:00 ~62*3 Jan 09 21:01:00 186 Jan 09 21:10:57 I seem to have it working now. I pinned the repo and upgraded again. Jan 09 21:11:11 Packages are their thumb versions now. Jan 09 21:15:40 OMG what Jan 09 21:16:02 9.1 only brings fmtx-middleware and two qt libs Jan 09 21:16:18 They never had any thumb-compiled version Jan 09 21:16:54 There is no point in pinning the thumb repo, there is nowhere to downgrade there Jan 09 21:17:42 Except the mp, of course Jan 09 21:19:28 Satorin: for the general usage, only pin it to something like 600 Jan 09 21:21:35 Nope, I lied. Those tho libs do have a thumb version, and you probably have it already. Jan 09 21:22:42 * Satorin notes. Jan 09 21:22:45 It added ~2000kb because they're new, not an upgrade Jan 09 21:22:57 Enabling Smartreflex should be safe, right? Jan 09 21:23:05 Sorry for all the noob questions by the way. Jan 09 21:23:07 Yeah Jan 09 21:28:14 Smartreflex is stable on stock frequencies yes Jan 09 21:29:10 unclear Jan 09 21:30:03 according to Nokia it's not stable Jan 09 21:30:28 ~sr Jan 09 21:30:29 [SmartReflex] >>Again, TI and we [Nokia] couldn't fix SmartReflex - we say memory corruption in front of our own eyes with that enabled, so we had to ship that disabled.<< Jan 09 21:32:58 of course you're free to outsmart TI and Nokia engineers, or simply say they lie at you Jan 09 21:33:33 or gamble and hope you have a "good" device Jan 09 21:34:08 or just don't care and go for SR no matter what, just for the leetness Jan 09 21:35:03 you as well can wear a tinfoil hat and claim nobody but you knows about the benefits it brings Jan 09 21:36:06 Wow, that was really unhelpful Jan 09 21:36:18 http://wiki.maemo.org/Smartreflex#Kernel_Power Jan 09 21:38:27 It is even enabled by default in kernel-power Jan 09 21:41:29 (maybe that's not true, but it definitely enabled in k-p-s default profile) Jan 09 21:42:41 well, that's thanks to those who prever gambling and leetness over stability and secure data Jan 09 21:42:52 prefer even Jan 09 21:46:25 I can think of at least 5 causes why SR fails and about same number of reasons why it may not fail on your particular device Jan 09 21:47:51 and of course almost all of those reasons are not static and stable - means when it doesn't fail today, that#s not any warranty that it doesn't fail tomorrow maybe Jan 09 21:48:49 while the true measured power savings form SR are rather marginal Jan 09 21:50:07 actually playing mp3 is probably the only usecase where SR would have any *noticeable* effect - as in "maybe 10% longer" or somesuch Jan 09 21:51:14 and please don't answer now with general undervolting since that's not what SR is all about Jan 09 21:51:58 SR is strictly about automatic core voltage regulation according to operating parameters of the core Jan 09 21:52:53 means on 500MHz and 600MHz SR has probably no effect per definitionem Jan 09 21:54:05 >I can think of at least 5 causes why SR fails and about same number of reasons why it may not fail on your particular device Jan 09 21:54:16 Can you elaborate? Jan 09 21:56:55 as elaborated above SR regulates core voltage. This is done in twl4030 PSM chip. just one possible cause of SR falure might be a propagation delay on Vcore trace from twl4030 to omap3430, caused by either a capacitor with specs out of range, or a layout oopsie, or a silicon error in either of both chips. Except the layout error all those culprits are depending on e.g. ambient temperature and whatnot else Jan 09 21:58:39 the trace may even be prone to ringing Jan 09 21:58:54 a particularly lovely effect EE have to cope with Jan 09 22:00:05 anyway there's no way whatsoever you could make sure or even just find out about SR status on your device Jan 09 22:01:00 hello everybody :) Jan 09 22:01:02 unless you have a lab equpped with instruments that cost in the 6 digit rnage Jan 09 22:01:21 I have a nokia n900 , with a very stupid problem with its camera Jan 09 22:01:54 when it is dark , the flash works but right before the lens takes the picture Jan 09 22:02:03 so the picture is always dark Jan 09 22:02:03 oooh Jan 09 22:02:15 that's indeed stupid Jan 09 22:02:28 hahaha lol :D Jan 09 22:02:36 are you sure you haven't disabled flashlight? Jan 09 22:02:39 DocScrutinizer05: I must admit I'm not competent enough to tell if that makes sense. Jan 09 22:02:48 do you think that is software related!? Jan 09 22:03:03 no it is Automatic in camera settings Jan 09 22:03:19 I have the package flashlight installed Jan 09 22:03:26 when flash disabled, I think it still uses flashlight for autofocus Jan 09 22:04:17 Mike11: honestly? reflash the device, then test without any of your usual apps installed (yet) Jan 09 22:04:42 no better idea on my side Jan 09 22:05:34 yes thanks man :D Jan 09 22:05:53 flashlight allows me to use the mobile as a torch Jan 09 22:06:08 make a BM backup and a standard osso backup Jan 09 22:06:10 I don't think it is the one causing problems though Jan 09 22:06:19 then flash the rootfs Jan 09 22:06:24 then test Jan 09 22:06:46 then use the osso backup to restoe one app after the other, and test in between Jan 09 22:06:53 that will take too long :( but looks like it is the only way :( Jan 09 22:07:11 when you think you found the culprit, restore from BM backup and uninstall the culprit Jan 09 22:07:12 can it be the super user kernel!!?? Jan 09 22:07:30 thanks for your time man :) Jan 09 22:07:40 I doubt it's kernel related Jan 09 22:08:34 probably a smart bisect startegy with installing apps can considerably reduce the time to spot the culprit Jan 09 22:08:34 also I was trying to install gcc compiler on n900 , but I have a problem with header files :( Jan 09 22:09:08 a program with no includes that does nothing compiles Jan 09 22:09:10 reflash (takes 90s), install first 50% of apps (takes maybe 15 min automatic installation) Jan 09 22:09:35 but when I include iostream , it says that file not found!!? Jan 09 22:09:36 when the error doesn't sho up, install 50% of the remaining 50% Jan 09 22:09:58 if error occured after 50% already: reflash and install only 25% Jan 09 22:10:12 yes I will google those kinds of backups (BM and osso) , I've never done them before Jan 09 22:10:23 do they backup intalled applications? Jan 09 22:10:42 you're not supposed to install gcc and friends on rootfs Jan 09 22:10:51 won't fit Jan 09 22:11:08 ~bm Jan 09 22:11:09 extra, extra, read all about it, backupmenu is http://talk.maemo.org/showthread.php?t=63975 Jan 09 22:11:23 how else can I intall gcc? Jan 09 22:11:24 and osso backup is the defualt backup you find in appstarter Jan 09 22:11:35 hmm good :) Jan 09 22:11:36 install gcc in easydeb chroot Jan 09 22:12:07 why is it that bad to install gcc on rootfs?? Jan 09 22:12:12 when you actually *need* compiler on your N900 Jan 09 22:12:24 because rootfs is +small* Jan 09 22:12:52 Dateisystem Size Used Avail Use% EingehÃĪngt auf Jan 09 22:12:53 rootfs 228M 169M 56M 76% / Jan 09 22:13:11 seems like I need a lot of more reading about the device :) Jan 09 22:13:29 ~optification Jan 09 22:13:30 optification is a inventive duct tape workaround to reclaim space in fs root, done due to the fact the systeminit *and* partitioning is FUBAR, http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing/Installing_under_opt_and_MyDocs, or ""OMG - I wish they looked into FHS and moved /usr to eMMC"", http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE2 bullet1,2 and fhs-2.3.html#PURPOSE16 dot3" Jan 09 22:13:43 I will read about this stuff (rootfs limitations, BM , chroot easydeb, .. ) Jan 09 22:13:49 you don#t wnat to do this for gcc. So -> easydebian chroot Jan 09 22:13:58 thanks again man :) Jan 09 22:14:02 yw Jan 09 22:14:23 out of curiosity how do you have this experience ??! Jan 09 22:14:25 :) Jan 09 22:14:44 lingering on here for 5 years Jan 09 22:14:46 ;-) Jan 09 22:15:01 cool buddy I want to be like you :p Jan 09 22:15:11 no, you don't ;-D Jan 09 22:15:57 why?! everybody wants to ask you :p Jan 09 22:16:21 you are like google now :) Jan 09 22:18:25 a) don't think it feels good to be google Jan 09 22:18:36 b) that's my least worry Jan 09 22:19:03 those 5 years basically ruined my life Jan 09 22:19:08 ;-) Jan 09 22:20:01 to be like me means you'll turn into a grumpy old sick zombie Jan 09 22:21:20 why do you think of yourself like that??! how old are you man ? Jan 09 22:21:48 older than I'd prefer to be Jan 09 22:22:37 maybe but you can still do what you want , no matter what age you are :) Jan 09 22:23:13 well, right now I actually do what is a lot of fun for me, yeah Jan 09 22:23:26 i'm just wondering if nobody else has issues with the media player and mafw-gst-renderer... http://talk.maemo.org/showthread.php?t=72156&page=157 Jan 09 22:23:35 wish you the best buddy :D Jan 09 22:23:46 hi xes! Jan 09 22:23:49 issues? Jan 09 22:23:51 hi Doc! Jan 09 22:24:10 mafw-gst-renderer is.... sub-par Jan 09 22:24:36 http://talk.maemo.org/showthread.php?t=72156&page=157 tl;dr Jan 09 22:25:39 issues...for a long time... Now it seems that something is more clear Jan 09 22:27:15 what issues? Jan 09 22:27:43 video not starting ...random Jan 09 22:27:54 ooh Jan 09 22:27:57 (nothing is really random) Jan 09 22:28:07 proly related to DSP Jan 09 22:29:12 yep i was thinking the same. But now i have changed opinion Jan 09 22:29:36 every now and then H.264(?) decoder in DSP locks up, and sometimes not even a software reset (done autonatically) will resurrect it. Then you actually need to power down resp reboot Jan 09 22:29:47 killing mafw-gst-renderer solves completely Jan 09 22:29:54 ooooh! Jan 09 22:30:03 nice find! Jan 09 22:31:34 my stupid OMP script gives ~99% working videos and more ram (see last post) Jan 09 22:31:48 but, for sure is not a proper solution Jan 09 22:31:56 miniminimini-app: queenbeecon-button: label="recover video", exec="killall mafw-gst-renderer" ? Jan 09 22:32:31 kill gst-renderer before and after omp... ;) Jan 09 22:32:50 oh, OMP Jan 09 22:33:36 btw with stock media player it happens the same Jan 09 22:33:38 that might in fact explain it Jan 09 22:33:46 hmm, not Jan 09 22:33:53 yep Jan 09 22:34:11 rarely ever (if at all) happened to me Jan 09 22:35:24 rarely != never and when that process is freezed it remains in that state until reboot Jan 09 22:39:23 and do you know why it freezes? Jan 09 22:40:17 I mean, when it happens so frequently to you, maybe a strace atached per default would shed some light on it? Jan 09 22:41:24 or maybe gstreamer resp mafw even has some --debug already built in and it's just disabled or piped to /dev/null ? Jan 09 22:41:29 ..not a clear idea so far Jan 09 23:11:12 hello Jan 10 02:35:18 happy new year! :) Jan 10 02:36:36 happy new year, Jan 10 02:36:44 isnt it a little late.. Jan 10 02:57:21 never too late Jan 10 02:57:21 :D **** ENDING LOGGING AT Fri Jan 10 02:59:59 2014