**** BEGIN LOGGING AT Sat Jan 25 02:59:59 2014
Jan 25 08:53:04 <SAiF> overheating like sh*t...
Jan 25 08:53:19 <SAiF> 49C
Jan 25 09:06:29 <SAiF> just because I keep instant messeger on
Jan 25 09:06:34 <SAiF> via wifi..
Jan 25 09:09:31 <ShadowJK> something's not right
Jan 25 09:11:11 <SAiF> fsck.vfat -a /dev/mmcblk1 bogging cpu.
Jan 25 09:11:46 <SAiF> which one is mmcblk1?
Jan 25 09:12:13 <ShadowJK> MyDocs
Jan 25 09:12:23 <SAiF> oops..
Jan 25 09:12:30 <ShadowJK> uh
Jan 25 09:12:35 <ShadowJK> or uSD
Jan 25 09:12:49 <SAiF> no.. I just removed usd
Jan 25 09:16:02 <SAiF> well killed it. :)
Jan 25 09:18:42 * kwtm agrees
Jan 25 09:19:02 * kwtm isn't sure what he just agreed to.
Jan 25 09:19:09 <kwtm> infobot: seen kwtm
Jan 25 09:19:11 <infobot> kwtm is currently on #maemo (40s). Has said a total of 1 messages. Is idling for 2s, last said: 'infobot: seen kwtm'.
Jan 25 09:19:24 <kwtm> Oh, good, I've not been muted.
Jan 25 09:21:27 <SAiF> load average fell from 2.30 to just  0.6 
Jan 25 09:22:00 <SAiF> and temp droping 43c ..
Jan 25 09:22:07 <SAiF> hmm... 
Jan 25 09:26:14 <sixwheeledbeast> fsck.vfat? mmcblk1 could be MyDocs or uSD unless you have KP
Jan 25 10:14:43 <hxka> mmcblk1 is uSD by default
Jan 25 10:15:19 <hxka> If he removed it while fsch was running, he have successfully shoot himself in the foot
Jan 25 10:19:55 <Ashley`> infobot, seen Ashley` 
Jan 25 10:19:56 <infobot> ashley` is currently on #maemo (1d 17h 23m 19s) #maemo-ssu (1d 17h 23m 19s). Has said a total of 159 messages. Is idling for 0s, last said: 'infobot, seen Ashley` '.
Jan 25 10:20:05 <Ashley`> yay
Jan 25 10:26:16 <sixwheeledbeast> hxka: mmcblk1 is only guaranteed to be uSD in KP due to a patch.
Jan 25 10:26:45 <hxka> what
Jan 25 10:28:11 <sixwheeledbeast> the stock kernel will give mmcblk0 to whatever device asks first.
Jan 25 10:28:46 <hxka> I really doubt that
Jan 25 10:28:58 <sixwheeledbeast> its not fixed that mmcblk0 = xyz
Jan 25 10:29:30 <sixwheeledbeast> have a look at upstart sources then
Jan 25 10:30:14 <sixwheeledbeast> or ask Pali
Jan 25 10:31:33 <hxka> upstart sources or upstart scripts?
Jan 25 10:33:31 <sixwheeledbeast> well actually system-services package
Jan 25 10:36:52 <sixwheeledbeast> rcS-late >>  # Find internal eMMC device, fallback to mmcblk0 \ for emmc in mmcblk1 mmcblk0; do
Jan 25 10:41:16 <hxka> That seems to be legacy from before it was implemented in udev rules
Jan 25 10:43:27 <hxka> See /etc/udev/rules.d/92-n770.rules and /lib/udev/mmc_id
Jan 25 10:50:56 <sixwheeledbeast> yes, they don't have fixed values either
Jan 25 10:54:01 <hxka> "what"
Jan 25 10:56:18 <sixwheeledbeast> hxka: http://mg.pov.lt/maemo-ssu-irclog/%23maemo-ssu.2013-09-14.log.html#t2013-09-14T14:11:02
Jan 25 11:01:38 <hxka> > real name is later configured by udev
Jan 25 11:01:54 <hxka> That's exactly what I'm talking about
Jan 25 11:02:14 <sixwheeledbeast> eh.
Jan 25 11:07:51 <sixwheeledbeast> "mmcblk1 is uSD by default" which as I said it isn't guaranteed on stock kernel
Jan 25 11:08:30 <hxka> it IS guaranteed
Jan 25 11:08:40 <hxka> See udev rules
Jan 25 11:09:13 <hxka> It will only assign mmcblk1 to external SD card
Jan 25 11:09:33 <hxka> And it will only assign mmcblk0 to internal eMMC card
Jan 25 11:10:08 <sixwheeledbeast> this is not what I have been told.
Jan 25 11:10:50 <hxka> You're confusing internal kernel numbers with devices udev creates in /dev/
Jan 25 11:11:40 <sixwheeledbeast> mmm
Jan 25 11:20:34 <SAiF> well read the logs.. :)
Jan 25 14:31:05 <freemangordon> does anyone have maemo Qt SDK offline installer?
Jan 25 18:12:28 <anYc> ~reflash
Jan 25 18:12:29 <infobot> i heard reflash is zImage and/or initrd.bin on CF and press C+D+Reset (collie) OR updater.sh, zimage.bin and/or initrd.bin on CF/SD and press OK while rebooting, then option 4, then CD or SF, then HAI (yes), then wait and cross fingers (all other models)
Jan 25 18:13:09 <anYc> o.O
Jan 25 18:16:40 <freemangordon> ~flashing
Jan 25 18:16:41 <infobot> rumour has it, maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware
Jan 25 18:27:33 <anYc> thx
Jan 25 18:30:08 <hxka> What devices ~reflash is about, though?
Jan 25 20:11:47 <DocScrutinizer05> well, pali is incorrect. mmc order isn't random. It's clearly defined that kernel first checks uSD interface which happens to be SoC's mmc-if1 and then checks mmc-if2 which is connected to eMMC in N900. the first MMC found is called mmc0, if a second is found it gets named mmc1. Later on initscripts and/or udev renames mmc1 and mmc0 in case a uSD is inserted
Jan 25 20:14:57 <DocScrutinizer05> some places never get renamed, see /proc/partitions
Jan 25 20:15:05 <DocScrutinizer05> http://privatepaste.com/8f11215a7c
Jan 25 20:15:44 <DocScrutinizer05> 15663104 mmcblk0;  31264768 mmcblk1
Jan 25 20:16:05 <DocScrutinizer05> obviously mmcblk0 size doesn't mazch size of eMMC
Jan 25 20:16:16 <DocScrutinizer05> mmcblk1 does, though
Jan 25 20:17:26 <DocScrutinizer05> we even once managed to swap complete eMMC to uSD since the user's eMMC been broken. We simply spotted and disabled the renaming
Jan 25 20:18:06 <DocScrutinizer05> iirc the comple patch been a one-char-edit - my favorite type of hack
Jan 25 20:18:10 <DocScrutinizer05> ;-)
Jan 25 20:22:33 <DocScrutinizer05> now if you wonder why - there's actually a rationale behind that: it allows to boot from uSD (in principle)
Jan 25 20:39:01 <DocScrutinizer05> btw same applies to your desktop PC, no matter if you use linux or windoze as your OS
Jan 25 20:39:36 <DocScrutinizer05> that's why recently device-references by label became popular
Jan 25 20:40:46 <DocScrutinizer05> dev/hda always been the master device on first ATA bus, iirc
Jan 25 20:41:02 <DocScrutinizer05> same for sata
Jan 25 20:42:22 <DocScrutinizer05> err, of course only when there been a master device on first ATA bus, otherwise next device found becomes HDA - right?
Jan 25 20:43:37 <DocScrutinizer05> soundcards are numberd by random (actually by timing during probing)
Jan 25 20:44:02 <DocScrutinizer05> that's why you can assign a soundcard number to a certain type of card, in ALSA
Jan 25 20:47:54 <nostros> hi!
Jan 25 20:48:58 <nostros> is this channel designed for glorification and worship of the all-mght nokia N900?
Jan 25 21:14:34 <DocScrutinizer05> hmm, he expected more entertainment it seems
Jan 25 21:37:33 <Sicelo> glorification and worship of the all-mght nokia N900? lol
Jan 25 21:37:36 <Sicelo> sounds like pron
Jan 25 23:04:33 <Ashley`> guys who wrote ytalk are awesome
Jan 25 23:04:47 <Ashley`> i'm talking using it for an hour now xD
Jan 26 00:20:46 <lexik_> Hi, is there someone with nmap-6.25 ('root bug' fixed) .deb for n900? meegoforum.pl where it was stored is now redirected to openos.pl, and direcotry structure seem broken, so.. if not, i will be forced to compile it myself :P
Jan 26 01:13:00 <kwtm1> Hi. How can I get a script executed when I receive a SMS?
Jan 26 01:13:29 <kwtm1> I've been looking at dbus-scripts and its GUI, but the GUI doesn't seem to have "when you receive a SMS" (somehow the "Connection" button doesn't work)
Jan 26 01:14:02 <kwtm1> and just looking at the the available DBus signals at http://wiki.maemo.org/N900_dbus doesn't tell me how to use it.
Jan 26 02:52:09 <Maxdamantus> so .. RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin is basically just a 250 MiB empty FAT32 filesystem?
Jan 26 02:52:23 <Maxdamantus> that's useful.
Jan 26 02:53:28 <Maxdamantus> oh wait, there are meant to be multiple partitions. 
Jan 26 02:55:21 <Maxdamantus> maybe the 0xFFFF tool didn't dump the whole thing.
**** ENDING LOGGING AT Sun Jan 26 02:59:59 2014