**** BEGIN LOGGING AT Tue Apr 02 02:59:58 2013
Apr 02 05:54:37 <eddyb> I've just woken up
Apr 02 05:54:59 <eddyb> and my N900 which was charging overnight is off
Apr 02 05:55:20 <eddyb> I have multiboot, power kernel doesn't work, default kinda does
Apr 02 05:55:40 <eddyb> but when I start it, the led goes white/yellow and then fades off
Apr 02 05:56:14 <eddyb> and if I leave the bootloader alone, it reboots or something, in a loop
Apr 02 05:57:25 <eddyb> the internet says batery too low
Apr 02 05:59:50 <Drathir> i vave solution to get back internet connection without restart the phone when write cant connect... only what need to do is 2 times ifconfig phonet0 down
Apr 02 06:00:32 <Drathir> and after gprs and network off 2 times ifconfig phonet0 up
Apr 02 06:01:24 <Drathir> eddyb: charger is broken i think...
Apr 02 06:01:38 <eddyb> Drathir: that's what I thought, too
Apr 02 06:02:43 <Drathir> eddyb: connect phone to pc and stay that few hours usb charging can be little slower...
Apr 02 06:03:18 <eddyb> it seems to work better from my laptop, but I think the usb cable is a bit borked :(
Apr 02 06:05:16 <Drathir> eddyb: ewentually put off battery for about minutes and try then put in back and poweron phone... but i have only one that situation that phone dont see charger and dont charging...
Apr 02 06:05:51 <eddyb> damn thing still restarts when connected to the laptop
Apr 02 06:06:02 <eddyb> so it's something in the phone that's broken :(
Apr 02 06:07:08 <Drathir> eddyb: you must stay phone off about 15-30 min depends of charging power to phone can boot up corectly...
Apr 02 06:11:58 <Drathir> if make loop when connected i think isnt bad phone  try to make something like in my words pre boot mode and have to little batery power to do that and do that in loop mode when battery go to enough power loop sould stop and phone will be charging orange blinking light...
Apr 02 06:14:43 <eddyb> it's charging
Apr 02 06:14:56 <eddyb> but every half a minute it reboots
Apr 02 06:15:20 <eddyb> and because nokia is stupid, it drains battery with that vibrator motor and the screen
Apr 02 06:23:42 <Drathir> low secure thing that maybe can broke your phone is put out the battery when phone is connected to charger and put in bac that can help stop loop mode but  i think could be very risky and dangerous...
Apr 02 06:24:30 <eddyb> XD
Apr 02 06:25:12 <eddyb> anyway, I'll leave it in there, hopefully it charges a bit while I'm gone
Apr 02 06:26:11 <Drathir> yes should charge in max 30 minutes to stop loop mode...
Apr 02 06:29:31 <Drathir> my 750mA make that in 10-15min when have drained battery... pc usb depends of pc could e 350-500mA max 900 if good remember...
Apr 02 06:31:40 <Drathir> i have too broken Nokia charger 1200mA she charging slower than phone discharging ^^
Apr 02 07:11:27 <Drathir> what is for buffer there ? http://monitor.maemo.org/ganglia/graph_all_periods.php?h=www&m=load_one&r=2hr&s=by%20name&hc=4&mc=2&st=1364822289&g=mem_report&z=large&c=maemo
Apr 02 09:41:42 <sixwheeledbeast> mmm, someone using one of my apps is having trouble but I can't see why.
Apr 02 09:42:33 <sixwheeledbeast> seems when pressing a checkbox while in terminal this appears http://pastebin.com/30tKRUw4
Apr 02 09:45:22 <SpeedEvil> that's not a local error
Apr 02 09:45:38 <SpeedEvil> oh, never mind
Apr 02 09:46:39 <SpeedEvil> sorry, forgotten what x errors I may have known.
Apr 02 09:49:20 <sixwheeledbeast> SpeedEvil: I am not sure at all, I guess a X Error is not local, a quick google of the error points to pixman
Apr 02 09:59:37 <SpeedEvil> I was suffering context failure, and thinking of android :'( 
Apr 02 09:59:43 <SpeedEvil> which has no x
Apr 02 10:01:43 <Apic> Damn. I did "passwd -l root", now "sudo gainroot" stopped working
Apr 02 10:01:49 <Apic> Hope deinstall/install Cycle will help
Apr 02 10:02:44 <Apic> Ah, »sudser« looks good
Apr 02 10:04:05 <sixwheeledbeast> ~sudser
Apr 02 10:05:41 <DocScrutinizer05> sudser is da shite
Apr 02 10:06:33 <DocScrutinizer05> re-install rootsh
Apr 02 10:07:09 <DocScrutinizer05> or use ssh root@localhost
Apr 02 10:07:39 <DocScrutinizer05> err, that won't work either with password locked
Apr 02 10:08:02 <DocScrutinizer05> restore etc/passwd in BM
Apr 02 10:08:31 <Apic> BM?
Apr 02 10:08:36 <DocScrutinizer05> ~bm
Apr 02 10:08:37 <infobot> backupmenu is probably http://talk.maemo.org/showthread.php?t=63975
Apr 02 10:08:42 <Apic> Ah, k
Apr 02 10:08:48 <Apic> tnx
Apr 02 10:08:54 <DocScrutinizer05> ssh might still work
Apr 02 10:09:39 <DocScrutinizer05> depending on what you did, do you have sshkeys installed
Apr 02 10:09:41 <DocScrutinizer05> ?
Apr 02 10:10:22 <DocScrutinizer05> uninstall and reinstall ssh might ask you for a password for root ;-)
Apr 02 10:10:36 <DocScrutinizer05> a *new* password
Apr 02 10:15:37 <DocScrutinizer05> eddyb: nope that's not nokia who's stupid. you probably ran into flatbat ddeadlock, your rootfs doesn't charge anymore, and thus you are locked in a bootloop that you only can escape with external charger and flashing
Apr 02 10:16:50 <DocScrutinizer05> and I *never* heard about taking out battery while charging stops bootloop
Apr 02 10:22:21 <kerio> yeah, that one's BS
Apr 02 10:22:31 <kerio> DocScrutinizer05: has anyone tested ramloading on low battery yet
Apr 02 10:22:32 <kerio> ?
Apr 02 10:22:58 <DocScrutinizer05> somebody for sure, just I don't know her/him
Apr 02 10:23:34 <DocScrutinizer05> but yeah, I planned to suggest rescueOS but forgot
Apr 02 10:23:40 <kerio> hrmpf
Apr 02 10:23:52 <kerio> DocScrutinizer05: do you know anyone who tested ramloading on low battery yet?
Apr 02 10:23:58 <kerio> is that better?
Apr 02 10:24:12 <DocScrutinizer05> no, I don't know anybody
Apr 02 10:28:29 <DocScrutinizer05> warfare for king, he obviously fixed the "matterhorn" issue in http://monitor.maemo.org/ganglia/graph_all_periods.php?h=www&m=load_one&r=2hr&s=by%20name&hc=4&mc=2&st=1364822289&g=mem_report&z=large&c=maemo
Apr 02 10:28:36 <DocScrutinizer05> FINALLY! :-))
Apr 02 10:29:56 <kerio> yay
Apr 02 10:40:55 <SpeedEvil> :-) 
Apr 02 10:41:31 <Apic> B-)
Apr 02 10:43:46 <jacekowski> are we sure that it's not because the cron job causing this is not running anymore?
Apr 02 10:49:24 <kerio> either way
Apr 02 11:03:01 <eddyb> DocScrutinizer05: thanks, and to be clear: my remark was that turning on the vibrator was a stupid idea from nokia
Apr 02 11:03:13 <eddyb> hey, you know what? it's green now
Apr 02 11:03:26 <DocScrutinizer05> turning on vibrator?
Apr 02 11:03:42 <eddyb> in that loop, every half a minute or so, it was vibrating
Apr 02 11:04:08 <DocScrutinizer05> sure, it's doing a short vibra kick during boot
Apr 02 11:04:15 <DocScrutinizer05> nothing wrong with that
Apr 02 11:04:46 <eddyb> it happened so often that it made me think it's wasting all that energy on the stupid motor
Apr 02 11:04:50 <eddyb> oh dammit
Apr 02 11:05:27 <DocScrutinizer05> the moment it does that the battery is supposed to have already enough charge form emergency charging to power the device for at least a few minutes, even with a short vibra kick
Apr 02 11:05:30 <eddyb> it's fully charged but I still get a yellow (the first time, now white) led fading then a restart
Apr 02 11:05:58 <eddyb> now it's white every time
Apr 02 11:06:24 <eddyb> I left it charging this morning (about 4-5 hours ago) and when I came back it had green on the led
Apr 02 11:06:36 <DocScrutinizer05> your rootfs is fsckdup, you need to fix bme to re-enable proper charging
Apr 02 11:06:47 <DocScrutinizer05> or your charger is broken
Apr 02 11:07:07 <DocScrutinizer05> I'd bet on bme
Apr 02 11:07:11 <DocScrutinizer05> and KP
Apr 02 11:07:33 <eddyb> yeah, the problem happened even with USB charging and now it kinda looks charged
Apr 02 11:07:42 <eddyb> but something in the kernel/system is bad
Apr 02 11:08:11 <eddyb> so I took the battery out, what now :/?
Apr 02 11:08:25 <DocScrutinizer05> something broke around bq27200_battery.ko, bq24150.ko, bme-replacement, and powerkernel
Apr 02 11:09:00 <eddyb> oh, I just watched a DEFCON presentation on hacking apple batteries, which use similar bq chips
Apr 02 11:09:13 <kerio> maybe he doesn't even have the bme replacement installed
Apr 02 11:09:20 <eddyb> are those ko objects in the fs or in an initrd?
Apr 02 11:09:28 <kerio> eddyb: just because they're called "bq", it doesn't mean they are similar
Apr 02 11:09:29 <DocScrutinizer05> 1st thing to check: remove battery, press and hold "U" key, insert battery, check if NOKIA screen with USB icon *stays*
Apr 02 11:09:48 <eddyb> kerio: but they're still TI battery chips
Apr 02 11:10:27 <kerio> yeah, but afaik they're complex enough to have an uploadable firmware
Apr 02 11:10:28 <eddyb> do I let go of U?
Apr 02 11:10:51 <DocScrutinizer05> only after device powered up
Apr 02 11:11:09 <eddyb> kerio: so do apple batteries, I guess you're referring to the fact that apple or nokia can write their own firmwares
Apr 02 11:11:25 <kerio> no, i mean apple batteries
Apr 02 11:11:30 <DocScrutinizer05> hold U, insert battery, push powerbutton or plug USB charger, check screen, release U
Apr 02 11:11:36 <kerio> the bq27200 on n900 doesn't have anything similar
Apr 02 11:12:00 <eddyb> oh I didn't power it
Apr 02 11:13:25 <DocScrutinizer05> if NOKIA&USB stays, you release U and power it down again (immediately to save battery). Then prepare ~flashing
Apr 02 11:13:48 <eddyb> yellow/orange led on
Apr 02 11:13:55 <eddyb> screen is stayin
Apr 02 11:14:03 <DocScrutinizer05> if NOKIA&USB doesn't stay, you're out of luck since your battery is too weak for flashing
Apr 02 11:14:29 <eddyb> what would change by flashing?
Apr 02 11:14:49 <DocScrutinizer05> it resets your system to stock config
Apr 02 11:15:13 <eddyb> I installed multiboot, nitdroid and powerkernel (the last one doesn't start at all in multiboot)
Apr 02 11:15:24 <kerio> oh god
Apr 02 11:15:44 <DocScrutinizer05> since it's pretty much the only thing you can do with a bootloop (except rescueOS and BM), it's probably the thing you wanna go for
Apr 02 11:16:08 <DocScrutinizer05> ~maemo-multiboot
Apr 02 11:16:09 <eddyb> and I have some stuff in MyDocs (which I hope I'll get to keep) but I'm not sure about contacts, browser history, etc
Apr 02 11:16:09 <infobot> well, maemo-multiboot is deprecated, and a horrible hack.  PROBLEMS WITH NITDROID/MULTIBOOT? reflash rootfs&kernel aka COMBINED
Apr 02 11:16:22 <eddyb> lol
Apr 02 11:16:25 <kerio> if you don't know how to get out of a bootloop, you shouldn't go anywhere near nitdroid
Apr 02 11:16:37 <eddyb> I haven't used it in months
Apr 02 11:16:38 <kerio> and, regardless of who you are, you shoudln't think about going anywhere near multiboot
Apr 02 11:17:08 <eddyb> mostly because it breaks powerkernel and I have to force-reinstall three things to have powerkernel working in multiboot after I use nitdroid
Apr 02 11:17:15 <DocScrutinizer05> eddyb: that's the "nice" feature of multiboot: it can nuke your whole system every single boot you do
Apr 02 11:17:32 <eddyb> DocScrutinizer05: that's why it says "can't find files to flash"?
Apr 02 11:17:40 <DocScrutinizer05> aborting the boot is sufficient to do that to your system
Apr 02 11:17:45 <eddyb> when powerkernel it's broken by nitdroid or now
Apr 02 11:17:55 <eddyb> DocScrutinizer05: oh shit I think that's what happened here
Apr 02 11:18:13 <eddyb> damn :(
Apr 02 11:18:17 <eddyb> ~flashing
Apr 02 11:18:18 <infobot> i heard maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware
Apr 02 11:18:46 <eddyb> I'm guessing this? http://wiki.maemo.org/Updating_the_tablet_firmware#Linux_PC
Apr 02 11:19:14 <DocScrutinizer05> all your settings and data and history and contacts live in your homedir on eMMC, they will survive a rootfs flashing
Apr 02 11:19:29 <eddyb> thanks, I feel better now
Apr 02 11:19:42 <eddyb> oh, fiasco. a friend of mine wrote 0xffff
Apr 02 11:20:47 * DocScrutinizer05 idly wonders if multiboot should get removed from extras(-testing)
Apr 02 11:20:55 <DocScrutinizer05> if it even is there
Apr 02 11:21:17 <eddyb> so I should never touch nitdroid again?
Apr 02 11:21:25 <eddyb> gingerbread isn't that good anyway :(
Apr 02 11:21:27 <DocScrutinizer05> for sure it's dangerous and harmful to device, and I think it's missing any proper warning about that fact
Apr 02 11:22:01 <eddyb> DocScrutinizer05: it would be nice if the whole NOLO thing was explained somewhere
Apr 02 11:22:45 <eddyb> all this embedded bootloader stuff is weird, especially when it's proprietary/custom
Apr 02 11:23:05 <DocScrutinizer05> eddyb: let me put it this way: even the nitdroid guys abandoned multiboot afaik. And in my book N900 is a maemo device, not a android device. There are better cheaper android devices, but there's no other maemo device at all
Apr 02 11:24:18 <eddyb> sadly, maemo isn't the peak of mobile linux, and I would've liked to use Chrome/Chromium on it :(
Apr 02 11:24:53 <eddyb> DocScrutinizer05: IIRC the installer uses multiboot. or it did a few months ago when I installed it
Apr 02 11:24:57 <DocScrutinizer05> I think there's a #nitdroid channel. It's dead I've been told
Apr 02 11:25:39 <DocScrutinizer05> eddyb: if you want android, sell your N900 on ebay and get two SGS2 for the money you earned from your N900
Apr 02 11:25:42 <eddyb> I think I've tried Mer or Nemo, but those used an external SD (which was a bit slow, and I have to make my own partitions to fit it)
Apr 02 11:25:50 <DocScrutinizer05> there are enough users who want *maemo*
Apr 02 11:26:13 <DocScrutinizer05> and there are enough cheap but better devices capable of running android
Apr 02 11:26:49 <eddyb> I probably want too much from a manufacturer... opensource hardware (or at least public specs) and opensource software
Apr 02 11:27:37 <eddyb> http://skeiron.org/tablets-dev/maemo-dev-env-downloads.php :(
Apr 02 11:27:48 <DocScrutinizer05> eh?
Apr 02 11:28:21 <DocScrutinizer05> what's wrong with skeiron?
Apr 02 11:28:42 <DocScrutinizer05> ~skeiron
Apr 02 11:28:43 <infobot> well, skeiron is the semi-official backup and emergency standin for all internet borne maemo resources: http://skeiron.org/tablets-dev/   http://talk.maemo.org/showthread.php?p=1315143#post1315143
Apr 02 11:28:43 <eddyb> oh, I had to remove .php: http://skeiron.org/tablets-dev/maemo-dev-env-downloads/
Apr 02 11:29:06 <eddyb> .deb :(
Apr 02 11:29:46 <eddyb> so I have to use a tar.gz and manually install a ton of 32bit deps
Apr 02 11:30:16 <DocScrutinizer05> so what? everybody who's interested in development for maemo has to go thru it
Apr 02 11:30:42 <eddyb> nvm, it seems to work out of the box
Apr 02 11:30:50 <ShadowJK> (or use the vm)
Apr 02 11:31:01 <eddyb> I'm not touching ubuntu
Apr 02 11:31:18 <DocScrutinizer05> for completely unclear reasons *nobody* so far provided a vmware image that's up to date and has full sb install
Apr 02 11:31:43 <DocScrutinizer05> or at least I haven't heard about it
Apr 02 11:31:59 <eddyb> USA/UK/Global... hmmm
Apr 02 11:32:14 <eddyb> IIRC this N900 was originally bought in Germany
Apr 02 11:32:19 <DocScrutinizer05> you're aware that SDK != flasher, are you?
Apr 02 11:32:32 <DocScrutinizer05> use global
Apr 02 11:32:58 <eddyb> I got it for free from my friend who replaced it with an iphone or something
Apr 02 11:33:25 <DocScrutinizer05> please carefully and *completely* read:
Apr 02 11:33:28 <DocScrutinizer05> ~flash
Apr 02 11:33:29 <infobot> i guess maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware
Apr 02 11:33:47 <DocScrutinizer05> when you're done, read it again!
Apr 02 11:33:47 <Apic> I want to make a Debian Chroot Image. Why does »dd if=/dev/zero of=deb.ext3 bs=1M count=1 seek=2001« make the System hang?
Apr 02 11:33:55 <Apic> Does it need to build intensive FAT blocklists?
Apr 02 11:34:39 <Apic> Or maybe I should use skip=?
Apr 02 11:35:47 <DocScrutinizer05> Apic: maybe because there's not enough room for a 2.001GB image? (though a sparse file which shouldn't eat much space). 
Apr 02 11:36:06 <Apic> I flashed new Vanilla, there's almost 32G free
Apr 02 11:36:18 <eddyb> DocScrutinizer05: I read it, but I'm curios about things like "what happens if USB suddenly disconnects? what's broken and what's still there? is it enough working stuff left for another retry?"
Apr 02 11:36:29 <eddyb> it would be easier if I could understand the architechture
Apr 02 11:36:41 <eddyb> and what you can break and what's safe
Apr 02 11:36:55 <eddyb> what's responsible for the NOKIA screen at boot
Apr 02 11:37:00 <DocScrutinizer05> eddyb: you can't brick N900 (basically, unless you're an expert or gifted fool)
Apr 02 11:37:18 <DocScrutinizer05> that's NOLO
Apr 02 11:37:21 <eddyb> ok, that's better. resident firmware?
Apr 02 11:37:29 <DocScrutinizer05> basically yes
Apr 02 11:37:40 <eddyb> that you can't touch without electrocuting the device or breaking a chip
Apr 02 11:37:47 <Apic> Doc: Never mind, now it finished
Apr 02 11:38:33 <DocScrutinizer05> well, the boot is ROMBL->(XLoader->)NOLO->(uboot->)Linuxkernel
Apr 02 11:38:46 <DocScrutinizer05> ROMBL is in CPU and can't get altered
Apr 02 11:38:59 <DocScrutinizer05> coldflash would be used to flash a new NOLO
Apr 02 11:39:15 <DocScrutinizer05> NOLO in turn does usual flashing of rootfs etc
Apr 02 11:39:50 <DocScrutinizer05> I actually hardly ever heard of anybody who nuked his NOLO so you don't need to worry aout coldflashing
Apr 02 11:40:08 <DocScrutinizer05> if your NOKIA screen shows up, your NOLO is fine
Apr 02 11:41:26 <DocScrutinizer05> Apic: I suspect dd reading 2GB of zeros from /dev/zero, just to dicard them
Apr 02 11:41:31 <eddyb> uboot is optional and has a minimal user interface
Apr 02 11:41:38 <eddyb> and XLoader?
Apr 02 11:41:58 <DocScrutinizer05> xloader is a stage in booting that's merged into NOLO basically
Apr 02 11:42:30 <Apic> DocScrutinizer05: Can you suggest a way that doesn't read? Add »skip=«?
Apr 02 11:42:49 <DocScrutinizer05> http://www.omappedia.org/wiki/Bootloader_Project
Apr 02 11:43:02 <DocScrutinizer05> Apic: sorry, no
Apr 02 11:43:12 <Apic> DocScrutinizer05: Tnx anyway B-)
Apr 02 11:43:22 <DocScrutinizer05> dunno off top of my head about skip
Apr 02 11:44:24 <DocScrutinizer05> eddyb: in above page, you s/uboot/NOLO/, for N900
Apr 02 11:45:55 <eddyb> thanks
Apr 02 11:46:02 <DocScrutinizer05> eddyb: N900 uBoot is not the uBoot mentioned on http://www.omappedia.org/wiki/Bootloader_Project
Apr 02 11:46:25 <eddyb> it's flashing fast
Apr 02 11:46:26 <DocScrutinizer05> N900 uBoot is packed together with linuxkernel into one "file"
Apr 02 11:46:38 <DocScrutinizer05> fast is <60s
Apr 02 11:46:44 <DocScrutinizer05> <2s is a fail
Apr 02 11:47:07 <eddyb> erasing CMT is slowest so far
Apr 02 11:47:17 <DocScrutinizer05> yeah, that's all fine
Apr 02 11:47:41 <eddyb> hmm, so, any clues what secondary and 2nd mean?
Apr 02 11:47:50 <eddyb> they're weird names :/
Apr 02 11:47:53 <Hurrian> secondary = nolo
Apr 02 11:47:55 <eddyb> oh
Apr 02 11:48:01 <DocScrutinizer05> you shouldn't boot up device with SIM, rather install notmynokia first, or you send that nasty SMS
Apr 02 11:48:10 <eddyb> what SMS?
Apr 02 11:48:19 <Hurrian> MyNokia
Apr 02 11:48:20 <DocScrutinizer05> SIM
Apr 02 11:48:33 <DocScrutinizer05> err premium SMS to Nokia
Apr 02 11:48:37 <eddyb> oh
Apr 02 11:49:03 <Hurrian> eddyb: tl;dr - after flashing, ensure SIM is not inserted, get root permissions and "apt-get remove cherry*"
Apr 02 11:49:04 <eddyb> I don't have the SIM in because I moved it to a 1000-ish phone until I fix the N900
Apr 02 11:49:19 <eddyb> CMT flashed successfully
Apr 02 11:49:22 <DocScrutinizer05> well, unless you flashed eMMC/VANILLA it shouldn't be a problem
Apr 02 11:49:48 <DocScrutinizer05> there's a tagfile that stops that rogue SMS thing
Apr 02 11:49:51 <DocScrutinizer05> ~jrtools
Apr 02 11:49:52 <infobot> [jrtools] http://wiki.maemo.org/User:Joerg_rw/tools
Apr 02 11:50:17 <DocScrutinizer05> that tagfile is in your homedir, and will survive flashing of rootfs
Apr 02 11:50:19 <eddyb> YES
Apr 02 11:50:21 <eddyb> no
Apr 02 11:50:32 <eddyb> YES
Apr 02 11:50:46 <eddyb> for some reason it stopped in the middle of booting
Apr 02 11:50:50 <eddyb> thanks guys :D
Apr 02 11:50:51 <DocScrutinizer05> no
Apr 02 11:50:55 <DocScrutinizer05> it didn't stop
Apr 02 11:51:10 <DocScrutinizer05> it just takes longer than usual on first boot
Apr 02 11:51:12 <DocScrutinizer05> read
Apr 02 11:51:14 <DocScrutinizer05> ~flash
Apr 02 11:51:16 <infobot> rumour has it, maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware
Apr 02 11:51:18 <DocScrutinizer05> read it again
Apr 02 11:51:31 <DocScrutinizer05> read it completely
Apr 02 11:51:38 <eddyb> boot animation started, screen went black, led went orange, then boot animation started again
Apr 02 11:51:50 <Hurrian> that's optification.
Apr 02 11:52:00 <DocScrutinizer05> will take minutes 
Apr 02 11:52:41 <eddyb> Welcome
Apr 02 11:52:46 <DocScrutinizer05> it's pretty lengthy elaborated in ~flash
Apr 02 11:53:10 <eddyb> haptic feedback is enabled by default, it's a bit cool
Apr 02 11:53:21 <DocScrutinizer05> read it again, read it *completely* from first to last line
Apr 02 11:57:30 <eddyb> well, my device is working again :P
Apr 02 13:18:28 <DocScrutinizer05> [general notice] repository is down, due to broken xen-vif 
Apr 02 13:42:12 <DocScrutinizer05> [general notice] we need to reboot blade-a
Apr 02 14:05:54 <eddyb> DocScrutinizer05: if anything, mcusw is a good RE toy to chew - I now have a visual analyzer for ARM binaries: green is code, red is strings: http://i.imgur.com/saVRsaM.jpg generated by http://jsfiddle.net/srJC4/9/
Apr 02 14:08:31 <DocScrutinizer05> [general notice] we shuld be (almost) back to normal on maemo.org
Apr 02 14:08:41 <DocScrutinizer05> sorry for the inconvenience
Apr 02 16:49:06 <RST38h> Moo, VDVsx
Apr 02 19:07:23 <sixwheeledbeast> You tell 'em DocScrutinizer05! Bloody *patches
Apr 02 19:07:42 <DocScrutinizer05> hehe
Apr 02 19:09:25 <DocScrutinizer05> "well, there's an issue, we should discuss it. So here we go .... <time passing by while discussion> OK, we heard all arguments and now we decide: its TAU." <one week later> "but hey, we should discuss that TAU thing!!"
Apr 02 19:10:00 <DocScrutinizer05> fools
Apr 02 19:12:22 <DocScrutinizer05> particularly some special e*_fools that start calling names and blame others as biased and unfair as soon as the decision made isn't the one they want to see 
Apr 02 19:13:36 <DocScrutinizer05> or even when it is, they still start bitching at those who made it - probably just because nobody asked e*_fools about their acknowledgment for said decision
Apr 02 19:14:39 <DocScrutinizer05> or just for fun, or to satisfy their perverted sense of humor and desire for arguing
Apr 02 19:14:43 <DocScrutinizer05> I dunno
Apr 02 19:15:32 <sixwheeledbeast> patchism?
Apr 02 19:41:58 <Ben`> WHOIS ManoftheSea
Apr 02 19:42:43 <Ben`> WHOIS <ManoftheSEA>
Apr 02 19:42:59 <Ben`> WHOIS <aidy>
Apr 02 19:43:41 <sixwheeledbeast> Ben`: slash first?
Apr 02 19:52:12 <DocScrutinizer51> /whois Ben` 
Apr 02 19:52:32 <DocScrutinizer51> ;-P
Apr 02 19:52:52 <DocScrutinizer51> ~botsnack
Apr 02 19:52:54 <infobot> DocScrutinizer51: aw, gee
Apr 02 19:53:22 <DocScrutinizer51> even better: /msg nickserv info Ben` 
Apr 02 19:57:44 <DocScrutinizer51> WTF is wrong with my xchat (timers)?? not only that it doesn't reregister anymore unless it misses keepalive pings for 200min, it alo doesn't allow me anymore to highlight lines in chatwin, rather context menu pops up no matter how far I 'drag'
Apr 02 19:58:53 * DocScrutinizer51 wonders if the latter might be related to a former messing around with gtk config values
Apr 02 20:03:02 <SpeedEvil> I vaguely recall there were power management hacks done to the timers
Apr 02 20:03:20 <DocScrutinizer51> OMFG
Apr 02 20:04:38 <DocScrutinizer51> who's to blame^W shoot?
Apr 02 20:05:04 <ShadowJK> Well it hasn't been changed in 3-4 years..
Apr 02 20:05:52 <DocScrutinizer51> it however changed for me during last 3..4 months
Apr 02 20:06:55 <DocScrutinizer51> I still wonder how ZNC1.0 update could be related
Apr 02 20:07:20 <DocScrutinizer51> since it clearly seems to be a N900 local issue
Apr 02 20:08:31 <kerio> works fine for me
Apr 02 20:08:36 <DocScrutinizer51> FFS
Apr 02 20:08:58 <DocScrutinizer51> what specifically?
Apr 02 20:09:16 <ShadowJK> The normal lag-timer side-effect keepalive was disabled in 2009 or so (along eith the entire UI for that, afaik)
Apr 02 20:09:37 <ShadowJK> when xchat power hogging was brought under control
Apr 02 20:09:51 <DocScrutinizer51> umm
Apr 02 20:10:51 <DocScrutinizer51> I had my special setup with keepalive = 90(s) or so, since times before I adopted ZNC
Apr 02 20:10:59 <ShadowJK> /timer timers still work, and I use that myself to ping my bouncer once every 10 minutes, to detect connection break
Apr 02 20:11:46 <DocScrutinizer51> well, I don't use Vtimer for that
Apr 02 20:12:04 <DocScrutinizer51> there's a config in xchat.cfg
Apr 02 20:12:25 <DocScrutinizer51> ping-timeout, or keepalive or sth
Apr 02 20:13:54 <ShadowJK> If that timer isn't working, then it's been disabled since 2009 for sure :P
Apr 02 20:13:59 <DocScrutinizer51> my problem however is: in 5min I'll leave this WLAN range and N900 will switch to GPRS and everything working just fine... except xchat which stays disconnected for at least 2h
Apr 02 20:14:09 <DocScrutinizer51> or until reconnect
Apr 02 20:14:39 <DocScrutinizer51> and that clearly changed THIS year
Apr 02 20:14:58 <DocScrutinizer51> worked like a charm last year's xmas
Apr 02 20:15:55 <DocScrutinizer51> I'll post a ping every 30s now...
Apr 02 20:15:59 <ShadowJK> It's always acted as "appears to be connected, but first attempt to type a chat line disconnects" for me
Apr 02 20:15:59 <DocScrutinizer51> ping
Apr 02 20:16:18 <DocScrutinizer51> while leaving AP range
Apr 02 20:16:35 <DocScrutinizer51> ping
Apr 02 20:17:04 <DocScrutinizer51> ~ping
Apr 02 20:17:04 <infobot> ~pong
Apr 02 20:17:28 <DocScrutinizer51> ~ping
Apr 02 20:17:29 <infobot> ~pong
Apr 02 20:18:40 <ShadowJK> /allserv ping
Apr 02 20:18:59 <ShadowJK> /timer -repeat 0 600 allserv ping
Apr 02 20:19:03 <ShadowJK> is what I use
Apr 02 20:19:43 <ShadowJK> Using openvpn between N900 and my server for seamless transition between wlans and 3g too
Apr 02 20:33:40 <DocScrutinizer51> had a friggin net_outoreconnect_on_fail = o in xchat.cfg, dunno if it's related and how it might have changed
Apr 02 20:33:49 <DocScrutinizer51> ~ping
Apr 02 20:33:50 <infobot> ~pong
Apr 02 20:34:15 <DocScrutinizer51> ping_timeout anyway been 240
Apr 02 20:35:03 <DocScrutinizer51> ok, roaming now from GPRS/2G to home AP
Apr 02 20:41:41 <sixwheeledbeast> it's like a table-tennis championship in here
Apr 02 20:48:01 <DocScrutinizer05> sixwheeledbeast: you got no idea about all the pings that were in the green
Apr 02 20:48:47 <DocScrutinizer05> I actually continued ~ping until [2013-04-02 22:33:40] <DocScrutinizer51> had a friggin ...
Apr 02 20:49:49 <DocScrutinizer05> now sitting at home, with a freshly started xchat with net_outoreconnect_on_fail = 1, and I roamed to my home AP. Result: dead
Apr 02 20:50:31 <sixwheeledbeast> [infobot] 15 love
Apr 02 20:50:37 <sixwheeledbeast> :P
Apr 02 20:50:42 <DocScrutinizer05> I'll give it another few minutes, but obviously it doesn't want to reconnect, as usual
Apr 02 20:52:09 <DocScrutinizer05> funny detail: I can log in via WLAN just fine
Apr 02 20:52:30 <DocScrutinizer05> so I'll use that to somehow get a tcpdump
Apr 02 20:52:41 <DocScrutinizer05> alas this tends to dump own activities
Apr 02 20:52:57 <DocScrutinizer05> like a nuclear chain reaction
Apr 02 20:53:23 <DocScrutinizer05> each byte transferred causes 10 bytes of log printout that also are transferred bytes
Apr 02 20:55:45 <ShadowJK> "tcpdump not port 22"
Apr 02 21:04:54 <kerio> DocScrutinizer05: unfiltered tcpdump over the network? that's neat
Apr 02 21:05:16 <DocScrutinizer05> ShadowJK: verbatim?
Apr 02 21:05:42 <DocScrutinizer05> kerio: which network?
Apr 02 21:06:00 <DocScrutinizer05> my local WPA2 WLAN? ***evil*** ;-P
Apr 02 21:06:32 <DocScrutinizer05> bash: tcpdump: command not found
Apr 02 21:06:36 * DocScrutinizer05 burps
Apr 02 21:07:27 <DocScrutinizer05> there's no tcpdump, but there's tshark ;-)
Apr 02 21:07:52 <kerio> does tshark have a way to ignore tshark data?
Apr 02 21:08:06 <DocScrutinizer05> for sure
Apr 02 21:08:22 <kerio> oh you could do a local dump, ofc
Apr 02 21:08:26 <DocScrutinizer05>   -f <capture filter>      packet filter in libpcap filter syntax
Apr 02 21:08:45 <DocScrutinizer05> alas I'm no libpcap filter syntax wizard
Apr 02 21:09:00 <DocScrutinizer05> xcat still zombie mode
Apr 02 21:09:07 <DocScrutinizer05> xchat even
Apr 02 21:16:25 <ShadowJK> DocScrutinizer05; yeah "not port 22" ignores ssh
Apr 02 21:16:38 <ShadowJK> "not port 22 and not port 53"
Apr 02 21:23:28 <kerio> what's 53?
Apr 02 21:23:54 <Apic> dns
Apr 02 21:27:52 <kerio> i see
Apr 02 21:27:56 <kerio> right
Apr 02 21:28:01 <kerio> why would you want to skip that?
Apr 02 21:29:11 <Apic> Because it's Background-Noise
Apr 02 21:40:26 <tx0h> hello
Apr 02 21:40:44 <Apic> Hi
Apr 02 21:41:28 <tx0h> when i run this calibrate-bg27k script, it tells me: please charge battery! Use fastcharger!
Apr 02 21:41:41 <tx0h> how can i use fastcharger and what is it?
Apr 02 21:42:44 <ShadowJK> not a computer
Apr 02 22:03:04 <kerio> the fastcharger is the charger you got with the n900
Apr 02 22:03:11 <kerio> the one that plugs into the wall
Apr 02 22:03:37 <tx0h> aha?!
Apr 02 22:03:56 <tx0h> ty
Apr 02 22:04:08 <tx0h> don
Apr 02 22:04:28 <tx0h> don't have it with me, just a usb cable :-(
Apr 02 22:07:20 <DocScrutinizer05> ShadowJK: will that meet " packet filter in libpcap filter syntax" specs of tshark?
Apr 02 22:09:23 <DocScrutinizer05> tx0h: using a USB cable and PC *might* work, but also might fail to restart charging after calibration finished. So you might find yourself with a depleted battery in your N900 the next morning, when you start that script when going to sleep
Apr 02 22:12:33 <DocScrutinizer05> *any* php cracks around? please see http://privatepaste.com/fb4e62912c and help your techstaff team to sanitize this nightmare
Apr 02 22:14:16 <kerio> lol php
Apr 02 22:14:56 <DocScrutinizer05> *sigh* yes
Apr 02 22:15:13 * DocScrutinizer05 starts to hate midgard
Apr 02 22:15:38 <DocScrutinizer05> you should see how it gets invoked!!
Apr 02 22:16:45 <DocScrutinizer05> a crontable entry invokes /usr/local/bin/garage_sync.sh
Apr 02 22:17:35 <DocScrutinizer05> and that shellscript does (among other stuff): lynx -dump -auth=admin:1Easdfghj http://local.maemo.org/midcom-exec-org.maemo.garagesync/import.php?confirm=1 | sed '/^$/d'
Apr 02 22:18:01 <kerio> did you seriously paste the password here
Apr 02 22:18:02 <DocScrutinizer05> now if that's not blowing your mind, I dunno what else might
Apr 02 22:18:28 <DocScrutinizer05> do I seriously look like a koala?
Apr 02 22:18:42 <DocScrutinizer05> ;-P
Apr 02 22:19:01 <kerio> wait, what's that sed invocation?
Apr 02 22:19:05 <kerio> don't print blank lines?
Apr 02 22:19:27 <DocScrutinizer05> you might notice the sequence "asdfghj" is a nice one for typing
Apr 02 22:19:40 <kerio> good for a password, so you don't forget it!
Apr 02 22:20:17 <DocScrutinizer05> honestly nobody remembers that password ;-P
Apr 02 22:27:13 <DocScrutinizer05> this crappy php script is the culprit for the insane "matterhorn" memusage sawtooth patterns that strike the 6GB RAM limit on WWW VM every now and then (while usually the job "only" neds 5GB to complete)
Apr 02 22:28:30 <DocScrutinizer05> we thought we fixed it by enabling the systemwide maxmem by commenting out #ini_set('memory_limit', -1);
Apr 02 22:29:24 <DocScrutinizer05> but that only results in [Tue Apr 02 21:12:34 2013] [error] [client 213.128.137.20] PHP Fatal error:  Allowed memory size of 367001600 bytes exhausted (tried to allocate 76 bytes) in /usr/share/php/midcom/lib/midcom/core/collector.php on line 336
Apr 02 22:30:02 <DocScrutinizer05> isn't it a shame?
Apr 02 22:30:38 <DocScrutinizer05> I'd have coded that shite on a ZX81 without ram extension, in basic
Apr 02 22:30:52 <DocScrutinizer05> and it wouldn't have any such issues
Apr 02 22:31:10 <DocScrutinizer05> and probably even was faster
Apr 02 22:32:00 <DocScrutinizer05> if it wasn't for those MIDGARD helper functions, for which there seems not any bindings to a proper language available
Apr 02 22:38:49 <DocScrutinizer05> ok, so much for the "daily WTF" and a tiny bit of horror. Your humble maemo admin manager feels like urgently needing a beer and a vodka
Apr 02 22:39:22 <DocScrutinizer05> if you have *any* suggestions how to sanitize the stuff sketched above, just holler please!
Apr 02 22:41:06 <DocScrutinizer05> we can't throw 16GB of ram at that stupid job, to cope with memleaks. And we eventually need it running again, to make the whole maemo.org work for devels
Apr 02 22:41:58 * DocScrutinizer05 waves and heads out, silently sobbing
Apr 02 22:44:58 <DocScrutinizer05> btw: xchat still zombified
Apr 02 22:45:04 <kerio> DocScrutinizer05: put the vodka *in* the beer!
Apr 02 22:45:15 <DocScrutinizer05> good plan ;-D
Apr 02 22:45:24 <kerio> actually, even better
Apr 02 22:45:30 <kerio> grab the beer glass
Apr 02 22:45:32 <kerio> fill it with vodka
Apr 02 22:45:37 <DocScrutinizer05> put some beer in the vodka?
Apr 02 22:45:45 <kerio> at that point, you might as well skip the beer
Apr 02 22:45:51 <DocScrutinizer05> hehe
Apr 02 22:46:02 <DocScrutinizer05> ~lart php
Apr 02 22:46:03 * infobot teaches php that M$ Access is a database. No, really, a database. A real live multi-user... well, ok, not multi-user, but a database. Yeah, that sounds right.
Apr 02 22:46:11 <kerio> NO INFOBOT
Apr 02 22:46:11 <DocScrutinizer05> ~kill midgard
Apr 02 22:46:12 * infobot shoots a excited anti-electron gun at midgard
Apr 02 22:46:16 <kerio> DON'T TEACH PHP ABOUT ACCESS
Apr 02 22:46:18 <kerio> STOP
Apr 02 22:46:31 <kerio> what have we done
Apr 02 22:47:35 <RST38h> KILL KILL DESTROY
Apr 02 22:47:38 <freemangordon> DocScrutinizer05: what, memleak in php?
Apr 02 22:47:56 <DocScrutinizer05> you forgot the plural-S
Apr 02 22:48:27 <DocScrutinizer05> freemangordon: yeah, incredible, isn't it?
Apr 02 22:48:58 <freemangordon> DocScrutinizer05: but, but... AFAIK php should not leak. I mean... couldn't we up/downgrade php module?
Apr 02 22:49:35 <DocScrutinizer05> WUT??? my xchat resurrected rom zombie state
Apr 02 22:50:19 <kerio> the messiah came back from the dead!
Apr 02 22:50:19 <freemangordon> DocScrutinizer05: honestly, I have always succeed to stay away from php, but my little knowledge on the matter tells me that a different version of php module should fix it
Apr 02 22:50:21 <DocScrutinizer05> so pretty exactly 2h again, until it notices a changed IP
Apr 02 22:50:26 <kerio> little late for easter, though
Apr 02 22:51:22 <DocScrutinizer05> freemangordon: now if you tell me *which* php module is the culprit, we actually might ponder that
Apr 02 22:51:39 <freemangordon> DocScrutinizer05: isn't that LAMP?
Apr 02 22:52:00 <DocScrutinizer05> LAMP with a ton of midgard on top
Apr 02 22:52:22 <kerio> DocScrutinizer05: http://phpmanualmasterpieces.tumblr.com/
Apr 02 22:52:38 <DocScrutinizer05> and *somebody* in the stack probably forgets to unset() a few vars for each call
Apr 02 22:53:04 <jacekowski> DocScrutinizer05: did you really just post main midgard password here?
Apr 02 22:53:12 <kerio> hahahaha
Apr 02 22:53:54 <jacekowski> ahm, no
Apr 02 22:53:58 <jacekowski> real pw is different
Apr 02 22:54:44 <freemangordon> DocScrutinizer05: do youknow which version midgard is?
Apr 02 22:55:55 <DocScrutinizer05> nfc
Apr 02 22:56:05 <jacekowski> i don't think it's php leaking as such, it's midgard plugin that's not allowing proper clean up
Apr 02 22:56:16 <DocScrutinizer05> :nod:
Apr 02 22:57:34 <DocScrutinizer05> I'd bet on it instantiating a new db view object each time you do any query
Apr 02 22:59:09 <DocScrutinizer05> and since php doesn't instantiate a new interpreter when calling out of own context, all those linger on forever
Apr 02 22:59:41 <freemangordon> DocScrutinizer05: anyone asked on #midgard?
Apr 02 22:59:59 <DocScrutinizer05> until apache is closing the original (and only) php interpreter instance when script quits
Apr 02 23:00:08 <jacekowski> Midgard version => 8.09.9.99
Apr 02 23:00:14 <DocScrutinizer05> well, I didn't
Apr 02 23:00:27 <freemangordon> jacekowski: thanks
Apr 02 23:00:47 <jacekowski> talking midgard
Apr 02 23:00:58 <jacekowski> i was trying to find some documentation for this piece of shit
Apr 02 23:01:03 <jacekowski> and it's like non existient
Apr 02 23:21:01 <freemangordon> jacekowski: looking at your memory report, it seems you're dumping  the memory usage before unset($person);
Apr 02 23:23:50 <DocScrutinizer51> RST38h: any idea what might take xchat 2h to sense a IP change (roaming) and reconnect to ZNC?
Apr 02 23:24:05 <DocScrutinizer51> ~ping
Apr 02 23:24:06 <infobot> ~pong
Apr 02 23:36:36 <freemangordon> DocScrutinizer05: what about splitting that php into 3?
Apr 02 23:37:31 <freemangordon> and invoking them in a row from a shell script (which gets invoked from cron)?
Apr 03 00:32:36 <DocScrutinizer05> freemangordon: already suggested, but I'm afraid that's still not sufficient to neuter that beast
Apr 03 00:34:00 <DocScrutinizer05> freemangordon: my idea is to only proces 100 lines of any of the 3 sections, then exit that script with an integer as return value, and invoke it again with that integer to skip the int:num-of-lines
Apr 03 00:35:29 <DocScrutinizer05> *maybe* even return name/id/whatever of last account processed, and then do a 'seek' or whatever it's named in SQL, for next higher reecord in primary key sequence
Apr 03 00:36:49 <DocScrutinizer05> nah, nevermind, the lines in that .csv are master, so all we need is a linenumber to resume processing, process another 100 lines, and exit with new current linenumber as return value
Apr 03 00:37:13 * DocScrutinizer05 doesn't believe saying such bullshit
Apr 03 00:37:59 <DocScrutinizer05> nuke all that crap, and code dat shite in a decent langiage, with direct SQL access
Apr 03 00:39:28 <DocScrutinizer05> /usr/share/php/midcom/lib/midcom/core/collector.php my ass
Apr 03 00:40:30 <DocScrutinizer05> there's a point where you just have to *drop* everything legacy cruft, and design sth from scratch
Apr 03 00:41:35 <DocScrutinizer05> all those $objects instantiated everywhere give me nausea
Apr 03 00:42:46 <DocScrutinizer05> $objects are for math profs and wimps, real men use FORTRAN or ASSEMBLER to code stuff
Apr 03 00:43:04 <DocScrutinizer05> ;-)
Apr 03 00:44:00 <DocScrutinizer05> at least in assembler there's no doubt at all about when garbage collector kicks in
Apr 03 00:44:15 <DocScrutinizer05> you simply re-use memory areas
**** ENDING LOGGING AT Wed Apr 03 02:59:57 2013