| 00:02.58 | *** join/#maemo dhbiker (~dhbiker@193.2.218.150) |
| 00:08.50 | *** join/#maemo dhbiker (~dhbiker@193.2.218.150) |
| 00:28.14 | *** join/#maemo sleepee (~sleepee@adsl-64-237-146-146.prtc.net) |
| 01:08.45 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 01:08.54 | *** join/#maemo sleepee (~sleepee@adsl-64-237-146-146.prtc.net) |
| 01:24.20 | *** join/#maemo teotwaki (~crashandd@2a01:e35:8a44:eb00:213:2ff:fe39:c4d4) |
| 01:24.21 | *** join/#maemo teotwaki (~crashandd@Maemo/community/contributor/crashanddie) |
| 01:27.22 | *** join/#maemo Sc0rpius (~naikel@190.79.197.57) |
| 01:28.59 | *** join/#maemo RST38h (marat@wsip-184-180-40-182.ri.ri.cox.net) |
| 01:49.59 | *** join/#maemo sleepee (~sleepee@adsl-64-237-146-146.prtc.net) |
| 01:50.47 | *** join/#maemo sLumPia (~sLumPia@182.8.153.110) |
| 01:56.49 | sLumPia | Why is the dsp profile have POWERSAVE_BIAS=0 ? |
| 01:57.19 | sLumPia | Isn't it better to have POWERSAVE_BIAS=1 ? |
| 02:05.23 | *** join/#maemo uen| (~uen@p5DCB1C71.dip.t-dialin.net) |
| 02:20.51 | *** join/#maemo sleepee (~sleepee@adsl-64-237-146-146.prtc.net) |
| 02:23.56 | *** join/#maemo radic_ (~radic@dslb-178-002-210-110.pools.arcor-ip.net) |
| 02:47.53 | *** join/#maemo sleepee (~sleepee@adsl-64-237-146-146.prtc.net) |
| 02:55.35 | *** join/#maemo pcfe` (~pcfe@brln-4dbc180f.pool.mediaWays.net) |
| 02:55.36 | *** join/#maemo pcfe` (~pcfe@redhat/pcfe) |
| 02:59.44 | DocScrutinizer05 | please explain what's POWERSAVE_BIAS |
| 03:03.45 | *** join/#maemo DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 03:08.58 | sLumPia | wiki.maemo.org/How_To_Make_Your_Battery_Last_Longer#Powersave_bias |
| 03:20.21 | *** join/#maemo Gh0sty (~ghosty@213.211.140.78) |
| 03:28.12 | *** join/#maemo beford (~fernando@unaffiliated/beford) |
| 03:36.56 | *** join/#maemo MetalGearSolid (~MetalGear@sta-102-96.tm.net.my) |
| 03:46.01 | *** join/#maemo sleepee (~sleepee@adsl-64-237-146-146.prtc.net) |
| 03:57.52 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 04:10.05 | *** join/#maemo robbiethe1st (~robbiethe@71-221-196-99.spkn.qwest.net) |
| 04:50.20 | *** join/#maemo sleepee (~sleepee@adsl-64-237-146-146.prtc.net) |
| 04:50.27 | *** join/#maemo pcfe (~pcfe@brln-4d0ce52e.pool.mediaWays.net) |
| 04:50.28 | *** join/#maemo pcfe (~pcfe@redhat/pcfe) |
| 04:59.12 | *** join/#maemo ludens (~user@gateway/tor-sasl/ludens) |
| 05:01.25 | *** join/#maemo joga (FHYPgN6f@rikki.fi) |
| 05:03.44 | *** join/#maemo marainein (~net@2001:388:608c:6cb5:15fe:24ed:d73c:42af) |
| 05:03.53 | *** join/#maemo cyborg-one (~cyborg-on@212-178-0-78.broadband.tenet.odessa.ua) |
| 05:04.20 | *** join/#maemo stardiviner (~stardivin@218.74.187.203) |
| 05:28.04 | *** join/#maemo sLumPia (~sLumPia@114.123.189.4) |
| 05:50.31 | *** join/#maemo marainein (~net@2001:388:608c:6cb5:15fe:24ed:d73c:42af) |
| 06:20.14 | *** join/#maemo noodles900 (~jpinx@host86-131-169-102.range86-131.btcentralplus.com) |
| 06:20.14 | *** join/#maemo noodles900 (~jpinx@unaffiliated/jpinx) |
| 06:21.41 | *** join/#maemo ZogG (~zoggrules@funtoo/user/ZogG) |
| 06:22.17 | *** join/#maemo FlameReaper (~assassin@175.138.119.191) |
| 06:25.44 | *** join/#maemo stardiviner (~stardivin@122.236.251.248) |
| 06:32.37 | *** join/#maemo jpinx (~jpinx@host86-131-169-102.range86-131.btcentralplus.com) |
| 06:33.12 | *** join/#maemo Zahra (~Zahra@unaffiliated/belendax) |
| 06:35.03 | *** join/#maemo jpinx (~jpinx@unaffiliated/jpinx) |
| 07:01.19 | *** join/#maemo piggz (~piggz@host-92-18-183-47.as13285.net) |
| 07:09.52 | *** join/#maemo joga (YTLrjIne@rikki.fi) |
| 07:22.28 | *** join/#maemo e-yes (~e-yes@77.51.17.83) |
| 07:27.19 | Ikarus | anyone know if there is a telepathy backend for whatsapp ? |
| 07:28.35 | *** join/#maemo croppa (~stuart@CPE-120-146-137-99.static.nsw.bigpond.net.au) |
| 07:29.40 | *** join/#maemo sasquatch (~username@p579581BF.dip.t-dialin.net) |
| 07:31.40 | *** join/#maemo joga (WQenlnqo@rikki.fi) |
| 07:38.14 | *** join/#maemo piggz (~piggz@host-92-18-183-47.as13285.net) |
| 07:39.53 | *** join/#maemo zsolt (~zsolt@catv-89-132-223-220.catv.broadband.hu) |
| 07:40.32 | zsolt | hello!my n900 doesn't charge with my universal usb charger,need some advice,thank you |
| 07:41.14 | zsolt | the charger's max current is 1000mA |
| 07:43.26 | jacekowski | it's probably iphone charger |
| 07:43.30 | jacekowski | or n900 is overloading it |
| 07:43.47 | jacekowski | does it say charging on nothing happens when you plug it in? |
| 07:43.52 | zsolt | i bought as universal usb charger |
| 07:44.27 | jacekowski | does it say charging on nothing happens when you plug it in? |
| 07:44.47 | zsolt | mass storage mode or pc suite mode options pop up |
| 07:45.14 | jacekowski | sounds like some weird charger |
| 07:45.24 | zsolt | then i click outside this window it says charging only,but nothing happens |
| 07:45.51 | zsolt | yellow led is not blinking |
| 07:47.08 | zsolt | it charges my girlfriend's mp4 and other usb devices,but not my n900 |
| 07:47.50 | jacekowski | it sounds like iphone charger |
| 07:49.48 | zsolt | it is a switching mode adaptor |
| 07:50.00 | zsolt | read the manual |
| 07:50.40 | joga | I built a small solar panel charger once and to charge the n900 one pin (I forget which, D-something?) had to be soldered to ground. still for some reason it wouldn't charge my n900 but did charge my gf's n900 and other phones :) |
| 07:51.53 | zsolt | heard somewhere that need to be short something,but forgotten what to do |
| 07:51.57 | joga | not sure if it was about software, I'm running the power kernel etc |
| 07:52.05 | zsolt | mee too |
| 07:52.11 | zsolt | kp51r1 |
| 07:52.29 | zsolt | it charges from original wall charger |
| 07:53.48 | zsolt | so do you think is it a software issue? |
| 07:54.45 | *** join/#maemo marainein (~net@2001:388:608c:6cb5:15fe:24ed:d73c:42af) |
| 07:56.35 | *** join/#maemo jhb (~joerg@p579F6CAF.dip.t-dialin.net) |
| 07:56.41 | *** join/#maemo OkropNick (kuba@host-n2-72-190.telpol.net.pl) |
| 07:59.51 | zsolt | what happens if I short D+/D-? |
| 08:00.21 | *** join/#maemo geaaru (~geaaru@host249-56-dynamic.252-95-r.retail.telecomitalia.it) |
| 08:08.10 | *** join/#maemo M4rtinK (~M4rtinK@ip-85-160-40-235.eurotel.cz) |
| 08:09.55 | joga | zsolt actually that was probably it...shorting the D-pins |
| 08:12.06 | joga | zsolt http://talk.maemo.org/showthread.php?t=38230 |
| 08:12.13 | zsolt | thank you |
| 08:12.44 | *** join/#maemo TNZ (~quassel@2a01:e35:2e0e:3290:21ed:ffcb:d5ec:4cc8) |
| 08:14.04 | *** join/#maemo jhb1 (~joerg@p579F6CAF.dip.t-dialin.net) |
| 08:14.57 | *** join/#maemo brzys (~brzys@86-63-126-137.sta.asta-net.com.pl) |
| 08:19.13 | *** join/#maemo MacDrunk (~marper@201.165.163.183) |
| 08:19.43 | *** part/#maemo MacDrunk (~marper@201.165.163.183) |
| 08:24.49 | zsolt | willing to use it on usb host mode with peripherals by usb Y cable,isn't harmful for my devices to short d+ d-? |
| 08:28.08 | joga | I think if your devices are anything else than chargers or stuff that draws power from the port, you will be unhappy without the D-pins |
| 08:28.40 | *** join/#maemo jpinx (~jpinx@host86-131-169-102.range86-131.btcentralplus.com) |
| 08:28.47 | zsolt | my set is like this |
| 08:29.56 | zsolt | one usb came from a usb hub with devices attached and another with power only.it goes then to my phone |
| 08:30.03 | zsolt | it is an y cable |
| 08:30.09 | *** join/#maemo jpinx (~jpinx@unaffiliated/jpinx) |
| 08:32.19 | *** join/#maemo eMHa (~mh@HSI-KBW-37-49-79-172.hsi14.kabel-badenwuerttemberg.de) |
| 08:35.14 | *** join/#maemo shanttu (~shanttu@88.193.85.11) |
| 08:37.13 | kerio | zsolt: to be fair you can probably force dedicated mode with bq24150x_charger |
| 08:42.20 | *** join/#maemo _rd (~rd@p57B49A93.dip0.t-ipconnect.de) |
| 08:43.49 | *** join/#maemo mvp_ (~mvp@port463.ds1-abc.adsl.cybercity.dk) |
| 08:52.22 | *** join/#maemo jhb (~joerg@p579F6CAF.dip.t-dialin.net) |
| 08:56.52 | zsolt | yess!i did it,thank you |
| 09:13.16 | *** join/#maemo Pali (~pali@unaffiliated/pali) |
| 09:17.50 | Pali | ping freemangordon |
| 09:17.58 | freemangordon | Pali: pong |
| 09:18.13 | Pali | freemangordon, I sent uboot patches to uboot ML |
| 09:18.21 | freemangordon | good :) |
| 09:18.31 | Pali | I CCed you |
| 09:18.32 | freemangordon | I am REing cal ;) |
| 09:18.45 | freemangordon | thanks |
| 09:19.01 | Pali | can you write answer about thumb errata questions? |
| 09:19.15 | freemangordon | lemme see |
| 09:19.35 | Pali | there are some and that code is yours |
| 09:19.43 | freemangordon | ok |
| 09:21.48 | freemangordon | "default: missing." hehe :P |
| 09:21.53 | freemangordon | toldya |
| 09:28.54 | *** join/#maemo NIN101 (~NIN@p5DD281B2.dip0.t-ipconnect.de) |
| 09:29.58 | freemangordon | Pali: I am not sure I undrestand the questions. what am I supposed to answer to "_WHAT_ ?!" |
| 09:30.15 | freemangordon | and "Actually -- why |
| 09:30.16 | freemangordon | do you even do call into ROM ? |
| 09:30.22 | freemangordon | " |
| 09:30.59 | Pali | write it |
| 09:31.06 | freemangordon | not that I don;t know what code is supposed to do, but questioning style is not clear to me |
| 09:35.34 | *** join/#maemo iDont (~iDont@j138215.upc-j.chello.nl) |
| 09:40.42 | kerio | Pali: i want to try uboot, just 'cause |
| 09:40.52 | kerio | Pali: how do i merge kp52 with uboot? |
| 09:41.12 | Pali | kerio, install kernel-power-bootimg package |
| 09:41.14 | kerio | does uboot-mkimage work? |
| 09:41.28 | Pali | and then u-boot-utils |
| 09:41.34 | Pali | and then flash u-boot |
| 09:41.43 | Pali | and you get kp in bootmenu |
| 09:41.58 | kerio | Pali: so i'm supposed to ignore the uboot-* packages in extras-devel? |
| 09:42.14 | Pali | kerio, yes ignore all uboot packages in extras |
| 09:42.19 | kerio | got it |
| 09:42.31 | Pali | and first remove them |
| 09:42.38 | kerio | i don't have any installed :) |
| 09:42.45 | Pali | ok :-) |
| 09:42.58 | kerio | how do i flash uboot? can i do that from the device? |
| 09:43.24 | Pali | are you going to use that new build? |
| 09:43.31 | kerio | i suppose so |
| 09:43.39 | Pali | you can flash fiasco image on device by fiasco-image-update |
| 09:43.42 | kerio | this is a 2104 |
| 09:54.47 | kerio | Pali: hmm, why is the -bootimg installed in /boot? |
| 09:54.57 | kerio | i thought there was no way to access the onenand from uboot |
| 09:55.01 | Pali | yes |
| 09:55.21 | Pali | u-boot-update-bootmenu generate uImage from zImage and store it onto MyDocs |
| 09:55.49 | kerio | i see |
| 09:57.21 | *** join/#maemo joga (YN9AreC3@rikki.fi) |
| 10:03.24 | *** join/#maemo zsolt (~zsolt@catv-89-132-223-220.catv.broadband.hu) |
| 10:03.46 | *** join/#maemo _rd (~rd@p57B49A93.dip0.t-ipconnect.de) |
| 10:03.55 | kerio | Pali: it appears to have booted |
| 10:03.56 | kerio | neat |
| 10:04.01 | zsolt | hello again.my problem is that need to charge my phone during usb host mode |
| 10:04.28 | kerio | zsolt: you've got a crappy charger, there's probably a software way around it but meh |
| 10:04.51 | zsolt | no,i just shortened the d+ an d- |
| 10:04.52 | kerio | Pali: it werkd |
| 10:04.58 | kerio | *shorted |
| 10:05.03 | kerio | then it should wor |
| 10:05.04 | kerio | k |
| 10:05.04 | zsolt | it works now |
| 10:05.52 | zsolt | but if I set to usb host mode with charging it refuses,"error,charger detected |
| 10:06.22 | zsolt | using kp51r1 |
| 10:07.36 | kerio | Pali: uboot working on 2104 |
| 10:08.43 | kerio | Pali: predictably, the attached kernel doesn't work |
| 10:11.07 | kerio | Pali: hmm, selecting kp52 and then quickly closing the keyboard slider (to not get bootmenu afterwards) made it not work |
| 10:11.33 | Pali | kerio, then you have problem with maemo rootfs /dev |
| 10:11.56 | Pali | In bootmenu.sh I added some mknod which create needed devices in /dev |
| 10:12.06 | Pali | like /dev/null /dev/zero ... |
| 10:12.16 | kerio | \_o_/ |
| 10:13.40 | kerio | Pali: how do i make a combined uboot image from kp52? |
| 10:13.48 | kerio | do you have an uboot.bin? |
| 10:14.04 | Pali | unpack fiasco image and you got uboot.bin |
| 10:14.21 | Pali | flasher[-3.5] -F <image.fiasco> -u |
| 10:14.41 | Pali | flasher is on n900, flasher-3.5 is on computer |
| 10:15.10 | kerio | and then uboot-gen-combined with the zimage in /boot and that uboot.bin |
| 10:15.14 | kerio | and then fiasco-update-image |
| 10:15.14 | kerio | got it |
| 10:15.16 | kerio | ty :) |
| 10:18.25 | Pali | kerio, do you have fiasco-update-image-ask deb package installed? |
| 10:21.57 | zsolt | need advice please!now figured out how to attach usb Y cable set,to enpower peripherals and charge my phone at the same time,but usb host mode with charging refuses to operate,"error,charger detected"using kernel power 51r1 |
| 10:24.39 | Pali | you need to disconnect charger before initializing host mdoe |
| 10:24.54 | Pali | first establish usb host mode and then attach charger |
| 10:25.27 | Pali | zsolt ^^^ |
| 10:25.47 | zsolt | thank you! |
| 10:26.41 | jon_y | Pali: can uboot be made to turn on the backlight explicitly if keyboard is out? |
| 10:27.20 | jon_y | it turns on sometimes, but only from cold start |
| 10:27.33 | Pali | jon_y, somebody must write code for backlight first |
| 10:27.57 | jon_y | ok, I see that its not in yet |
| 10:28.13 | Pali | now I added only code for turning led off |
| 10:28.19 | jon_y | i2c pins to get it to turn on? |
| 10:28.26 | Pali | but backlight is not simple and I do not have time for it |
| 10:28.32 | jon_y | ok |
| 10:28.37 | Pali | for backlight is used SPI |
| 10:28.43 | Pali | not i2c |
| 10:29.15 | jon_y | special super secret proprietary spi command? |
| 10:30.03 | jon_y | is the byte sequence already known? |
| 10:31.34 | kerio | Pali: i do |
| 10:32.02 | Pali | jon_y, there is open source kernel driver |
| 10:32.16 | Pali | so need to port kernel drive to uboot |
| 10:32.27 | Pali | kernel driver is ack<something> |
| 10:32.44 | kerio | Pali: unpacking the fiasco only gave me a zImage |
| 10:33.00 | Pali | kerio, and what is problem? |
| 10:33.07 | kerio | the zImage is for uboot+omap |
| 11:52.14 | *** join/#maemo infobot (~infobot@rikers.org) |
| 11:52.14 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ -- COUNCIL ELECTIONS nomination period extended til 10-28! Dare to stand! -- N9/harmattan related questions please in #harmattan ! | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 11:56.10 | jaska | foobot |
| 12:03.18 | DocScrutinizer05 | zsolt: D+- short missing |
| 12:04.50 | kerio | zsolt: i expect kernel-power to already support everything |
| 12:12.54 | *** join/#maemo jpinx (~jpinx@host86-131-169-102.range86-131.btcentralplus.com) |
| 12:13.05 | *** join/#maemo jpinx (~jpinx@unaffiliated/jpinx) |
| 12:17.27 | kerio | Pali: srsly though, help me :c |
| 12:17.32 | kerio | i can't reboot my n900 while unattended now |
| 12:18.32 | jpinx | needs a chaperone ? ;) |
| 12:23.27 | kerio | jpinx: well, yes |
| 12:23.37 | kerio | somebody to open the kbd slider and choose a couple of menu entries |
| 12:25.59 | kerio | i wonder if uboot would even fit, with kernel-power |
| 12:29.17 | *** join/#maemo valdyn (~valdyn@valdyn.org) |
| 12:35.40 | *** join/#maemo heya (~theo.pamo@114.79.13.81) |
| 12:36.11 | heya | hai |
| 12:36.19 | kerio | heya! |
| 12:36.27 | kerio | (i'm so funny) |
| 12:36.40 | heya | why ? |
| 12:36.51 | kerio | because it's your nickname but also kind of a greeting |
| 12:37.16 | heya | yeah, i'm like |
| 12:39.32 | heya | i must go |
| 12:39.35 | *** part/#maemo heya (~theo.pamo@114.79.13.81) |
| 12:47.43 | kerio | ...that was weird |
| 12:50.54 | Skry | :D |
| 12:53.28 | kerio | ah fuck, i screwed up something D: |
| 12:53.46 | kerio | goddammit |
| 12:53.57 | kerio | ~flashing |
| 12:53.58 | infobot | i heard maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware |
| 12:54.29 | kerio | ~pali |
| 12:54.30 | infobot | i guess pali is http://atrey.karlin.mff.cuni.cz/~pali/ |
| 12:59.25 | *** join/#maemo brzys (~brzys@86-63-126-137.sta.asta-net.com.pl) |
| 13:04.09 | *** join/#maemo Neutron18 (~neutron@80.202.97.159) |
| 13:07.49 | *** join/#maemo avk_nebo (~avk_nebo@89.169.249.109) |
| 13:07.49 | *** join/#maemo Zahra (~Zahra@unaffiliated/belendax) |
| 13:08.32 | *** join/#maemo messerting (~messertin@cm-84.211.113.209.getinternet.no) |
| 13:09.57 | *** join/#maemo ced117 (~ced117@AStrasbourg-552-1-87-208.w92-141.abo.wanadoo.fr) |
| 13:09.57 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 13:18.49 | kerio | oh dear, i appear to have fucked something up |
| 13:19.02 | kerio | where's the data in osso-product-info stored? |
| 13:21.35 | merlin1991 | phew no idea, but ie the mp-fremnalte-*-pr changes the data in postinst |
| 13:21.42 | merlin1991 | which dataset is broken? |
| 13:23.04 | *** join/#maemo _rd (~rd@p57B49A93.dip0.t-ipconnect.de) |
| 13:23.21 | merlin1991 | just noticed hat on all 3 devices stock, cssu-stable and cssu-testing osso-product-info has 4 "unknown" entries |
| 13:24.14 | kerio | merlin1991: release name, full name, version, ossoversion |
| 13:24.17 | kerio | those are unknown |
| 13:25.01 | merlin1991 | yep, I've got the same, even on a completely clean maemo install |
| 13:25.49 | kerio | what the hell |
| 13:26.11 | kerio | that's not normal, is it |
| 13:26.25 | kerio | i thought there was something wrong with my CAL, and so i tried to nandwrite my backup |
| 13:26.28 | kerio | but apparently it doesn't fit |
| 13:26.36 | kerio | and writing with oob causes a segfault |
| 13:27.12 | kerio | it appears to be booting, at least |
| 13:27.24 | kerio | shakes his fist at Pali |
| 13:27.32 | *** join/#maemo Smily (Smily@BSN-142-124-174.dial-up.dsl.siol.net) |
| 13:27.44 | merlin1991 | err how is that possibly palis fault? :D |
| 13:27.57 | kerio | i toyed around with uboot today |
| 13:28.08 | kerio | so it must be his fault! |
| 13:28.29 | kerio | DocScrutinizer05: do you mind pastebinning the output of osso-product-info on t900? |
| 13:29.03 | DocScrutinizer05 | hmm? |
| 13:29.34 | kerio | i appear to not have that information anymore |
| 13:30.27 | DocScrutinizer05 | sigh, friggin pastebin sites changing their API all the time, so my scripts for direct pastebin from cmdline always break |
| 13:30.31 | Pali | kerio, if you flash some kernel without version, softupd will remove osso-product-info from CAL |
| 13:30.43 | kerio | Pali: i see |
| 13:30.50 | kerio | but i just flashed kp52 |
| 13:30.54 | kerio | with kernel-power-flasher |
| 13:30.54 | Pali | kerio, here is fix: https://gitorious.org/community-ssu/mp-fremantle-community-pr/blobs/master/debian/postinst |
| 13:31.27 | Pali | and then reboot phone |
| 13:31.43 | DocScrutinizer05 | here you are: http://pastebin.com/asLTHZwT |
| 13:32.10 | kerio | Pali, DocScrutinizer05: ty |
| 13:32.19 | kerio | Pali: btw, i removed uboot |
| 13:32.24 | kerio | mostly because i don't need it |
| 13:32.37 | Pali | kerio, you need only OSSO_VERSION |
| 13:32.48 | kerio | but it did work fine, as long as i didn't touch the stuff in MyDocs/bootmenu.img.d >:) |
| 13:32.54 | DocScrutinizer05 | OSSO_PRODUCT_WLAN_CHANNEL='fcc/us' pissing me |
| 13:33.23 | kerio | DocScrutinizer05: btw, nandwrite on CAL didn't work at all |
| 13:33.26 | Pali | kerio, u-boot-update-bootmenu will regenerate MyDocs/bootmenu.img.d |
| 13:33.50 | kerio | Pali: anyway, why MyDocs and not /home/boot* ? |
| 13:34.03 | Pali | because first fat32 partition |
| 13:34.17 | kerio | there's no ext support in uboot? :( |
| 13:34.17 | Pali | and it is mounted by maem to MyDocs |
| 13:34.25 | Pali | yes, there is ext2 |
| 13:34.32 | Pali | and now finaly there is also ext4 |
| 13:34.53 | Pali | but back in april there was no ext4 |
| 13:35.02 | DocScrutinizer05 | kerio: gathered as much, when I tried to create an image with nanddump that's identical to either dd or cat or mtd_debug |
| 13:36.13 | kerio | DocScrutinizer05: nanddump -o -b could work, i think |
| 13:36.17 | DocScrutinizer05 | kerio: anyway nota bene you probably need to erase NAND prior to flashing new content |
| 13:36.25 | kerio | DocScrutinizer05: nah, nandwrite does that |
| 13:37.56 | DocScrutinizer05 | kerio: (-o -b) exactly my thoughts, and you say it failed for you? |
| 13:38.07 | kerio | DocScrutinizer05: with -o -b it worked fine |
| 13:38.24 | DocScrutinizer05 | [2012-10-14 15:33:23] <kerio> DocScrutinizer05: btw, nandwrite on CAL didn't work at all |
| 13:38.34 | kerio | with my old dump |
| 13:38.40 | kerio | which is apparently useless |
| 13:39.02 | kerio | because i can't write it, not even with the option to account for the oob data |
| 13:39.07 | DocScrutinizer05 | you'd like me to provide a -o-b image of my CAL? |
| 13:39.14 | kerio | nah, i have one |
| 13:39.28 | kerio | and besides, your n900 is german :s |
| 13:39.35 | DocScrutinizer05 | ;-P |
| 13:40.00 | DocScrutinizer05 | I got others as well |
| 13:40.15 | kerio | do you have a british 2104 n900? |
| 13:40.27 | DocScrutinizer05 | OSSO_PRODUCT_REGION='Britain' |
| 13:40.34 | DocScrutinizer05 | IroN900 |
| 13:40.38 | DocScrutinizer05 | my daily phone |
| 13:40.41 | kerio | o/ |
| 13:40.42 | kerio | hw rev? |
| 13:41.10 | DocScrutinizer05 | Revision : 2101 |
| 13:41.14 | kerio | aww :( |
| 13:41.57 | DocScrutinizer05 | I'd bet you could try to hexedit the hwrev string in raw nand inage |
| 13:42.08 | kerio | that's not the point! they're different hw revs! |
| 13:42.23 | DocScrutinizer05 | how's that mattering for CAL? |
| 13:42.48 | DocScrutinizer05 | CAL *defines* the hwrev |
| 13:43.03 | kerio | you know what else defines the hwrev? the hw's rev |
| 13:43.13 | DocScrutinizer05 | so WHAT? |
| 13:43.18 | kerio | perhaps some critical calibration parameters differ from rev to rev |
| 13:43.54 | kerio | i'd really like to know *what* is stored in CAL |
| 13:43.58 | DocScrutinizer05 | either you got a phy hw of 2101 then my CAL is OK, or you got hwrev XYZA then you edit CAL image to meet that fact |
| 13:44.09 | DocScrutinizer05 | no calib will differ |
| 13:44.31 | DocScrutinizer05 | at least not to my knowledge |
| 13:45.08 | DocScrutinizer05 | IF it doesn't work, you're free to flash back to what's in your CAL *now* ;-P |
| 13:45.33 | kerio | but what if your CAL fucks up my n900 D: |
| 13:45.45 | kerio | might be slightly trolling at this point |
| 13:45.59 | DocScrutinizer05 | one thing's for sure: with wrong hwrev standard flashing will cease to work, since hwrev mainly seems to specify NAND bank geometry |
| 13:46.22 | kerio | yeah but that's the reason flasher-3.5 has a way to specify the hw rev, isn't it |
| 13:46.42 | DocScrutinizer05 | you might overcome that problem by explicitly overriding CAL hwrev via flasher-35 parameter |
| 13:46.51 | DocScrutinizer05 | yes :-) |
| 13:46.55 | kerio | did sambo7 ever report back after flashing your cal? |
| 13:47.14 | DocScrutinizer05 | the nandtester? never heard of him again |
| 13:47.19 | kerio | also, stuff like the IMEI isn't stored there, right? |
| 13:47.27 | kerio | it's stored in rapuyama's internal CAL |
| 13:48.26 | DocScrutinizer05 | IMEI isn't in CAL afaict |
| 13:48.47 | DocScrutinizer05 | yep |
| 13:49.19 | DocScrutinizer05 | IroN900:~# strings /dev/mtd1|grep -i IMEI ->null |
| 13:50.25 | *** join/#maemo Hoolxi (~Openfree@120.204.163.7) |
| 13:55.31 | DocScrutinizer05 | kerio: so how about clearly satting what you did to reflash CAL, and what's been your results |
| 13:55.37 | DocScrutinizer05 | stating* |
| 13:58.03 | DocScrutinizer05 | I'd like to verify the procedure, and then start a project to host CAL images for those who nandtested |
| 14:05.21 | kerio | DocScrutinizer05: nanddump -o -f calbackup /dev/mtd1ro |
| 14:05.29 | kerio | to write, nandwrite /dev/mtd1ro calbackup |
| 14:05.42 | *** join/#maemo kov_ (~kov@187.114.32.180) |
| 14:05.56 | kerio | to check, idk, maybe just nanddump without "-o" before and after |
| 14:06.00 | kerio | but i don't think they're required to be equal |
| 14:06.22 | kerio | the result of nanddump -o, nandwrite, nanddump -o is the same for both nanddumps |
| 14:06.47 | *** join/#maemo VDVsx (~VDVsx@a88-112-254-211.elisa-laajakaista.fi) |
| 14:06.50 | kerio | or, at least, they generate a md5 hash collision >:D |
| 14:11.12 | *** join/#maemo FlameReaper (~FR@203.82.92.17) |
| 14:13.30 | *** join/#maemo messerting (~messertin@cm-84.211.113.209.getinternet.no) |
| 14:19.01 | *** join/#maemo Free-MG (~test@p4FFE79A4.dip.t-dialin.net) |
| 14:22.23 | kerio | DocScrutinizer05: "-b" in nanddump skips bad blocks, but i don't know if it's a good or a bad thing |
| 14:25.21 | kerio | DocScrutinizer05: to be fair we'd need something specialized for CAL, that stores the data in a more generic format |
| 14:25.43 | kerio | flash memory sucks |
| 14:27.12 | Pali | kerio, storing to FS (maybe ubifs on nand?) |
| 14:28.23 | kerio | Pali: no, i mean, something to store the data in cal and to recreate it |
| 14:28.33 | kerio | i assume libcal has a way to deal with bad blocks |
| 14:29.25 | Pali | CAL is linked list |
| 14:29.42 | Pali | freemangordon, now working on RE libcal |
| 14:30.09 | kerio | linked lists also suck :c |
| 14:30.15 | kerio | does it do garbage collection? |
| 14:34.45 | *** join/#maemo FlameReaper (~assassin@175.138.127.209) |
| 14:35.48 | Pali | kerio, I thini it doing some wear leveling |
| 14:40.49 | *** join/#maemo krau|away (~krau@bombadil.infradead.org) |
| 14:41.42 | DocScrutinizer05 | I think it just uses up all available space, then may or may not compress stuff to recycle obsolete aka delet-marked entries |
| 14:42.38 | DocScrutinizer05 | I'm not even convinced it's a linke dlist, it *might* be a simple array with later entries overriding earlier ones |
| 14:43.50 | DocScrutinizer05 | given the usage pattern and purpose, it might never fill up during lifetime of a N900 |
| 14:46.49 | *** join/#maemo sleepee (~sleepee@64.237.146.146) |
| 14:46.56 | DocScrutinizer05 | kerio: anyway why do you think a nanddump image isn't appropriate for CAL? |
| 14:47.06 | kerio | DocScrutinizer05: because of bad blocks |
| 14:47.35 | DocScrutinizer05 | nanddump won't store any bad blocks to a -b file |
| 14:47.49 | DocScrutinizer05 | aiui |
| 14:47.57 | kerio | yeah but you're assuming you don't get any *new* bad blocks between the dump and the write |
| 14:48.10 | DocScrutinizer05 | eh? |
| 14:48.43 | DocScrutinizer05 | nanddump -b skips bad blocks in output data, nandwrite handles bad blocks on write |
| 14:50.17 | DocScrutinizer05 | if your NAND you try to write to has more bad blocks than the one you pulled your image from, the image won't fit completely into the 'new' NAND. I'd assume nandwrite noticing that at end of write and throws a warning |
| 14:53.37 | DocScrutinizer05 | I actually fail to see the usecase for a nanddump without -b, since you can't write back such an image to any NAND if it actually contains bad blocks |
| 14:53.37 | kerio | DocScrutinizer05: yeah but does the read happen in the same way? |
| 14:55.05 | DocScrutinizer05 | sure, nanddump -o -b should create an image with any bad blocks skipped/omitted |
| 14:58.16 | DocScrutinizer05 | my guess would be: nanddump -o -b /dev/mtd1 | nandwrite -m |
| 15:00.00 | DocScrutinizer05 | <kerio> to write, nandwrite /dev/mtd1ro calbackup |
| 15:00.13 | DocScrutinizer05 | seriously? /dev/mtd1ro ?? |
| 15:00.36 | DocScrutinizer05 | always thought ro means ReadOnly |
| 15:02.34 | Skry | it does |
| 15:03.14 | DocScrutinizer05 | kerio: to verify, you should do a mtd_debug erase <device> <offset> <len> between nanddump and nandwrite, to rule out your images don't differ just because your write failed completely |
| 15:04.06 | *** join/#maemo krayon (~fallen@pdpc/supporter/28for7/krayon) |
| 15:04.11 | DocScrutinizer05 | ((<kerio> the result of nanddump -o, nandwrite, nanddump -o is the same for both nanddumps)) no surprise when writing to mtd1ro |
| 15:06.50 | DocScrutinizer05 | what concerns me most is the difference between `cat mtd1ro` and `nanddump -b mtd1ro` |
| 15:07.19 | DocScrutinizer05 | or even `nanddump mtd1ro` |
| 15:08.17 | DocScrutinizer05 | (I got no bad blocks, according to nanddump, so -b shouldn't make any difference for me, but I tested both variants and neither is what I get from cat, or dd) |
| 15:10.20 | kerio | DocScrutinizer05: er, wtf, i meant /dev/mtd1 |
| 15:10.23 | DocScrutinizer05 | I'm reluctant to try nandwrite (on CAL) unless I figured what's the deal with this difference. I might test on mtd4 though |
| 15:11.00 | kerio | writing to mtd1ro causes errors :) |
| 15:11.09 | DocScrutinizer05 | thought as much |
| 15:12.41 | kerio | DocScrutinizer05: nanddump /dev/mtd1ro and nanddump -b /dev/mtd1ro have the same output for me |
| 15:13.15 | DocScrutinizer05 | then I get it your nandump also says "0 bad blocks" |
| 15:13.21 | kerio | yep |
| 15:13.43 | kerio | ECC failed/corrected, bad blocks, bbt blocks all 0 |
| 15:14.17 | DocScrutinizer05 | so, when kicking out OOB and badblocks from nanddump image, WTF it differs from a dd image of same mtd? |
| 15:14.41 | kerio | you mean when adding OOB and badblocks |
| 15:14.53 | kerio | well, idk |
| 15:15.14 | DocScrutinizer05 | err yep |
| 15:15.20 | kerio | but i think that the contents of /dev/mtd1 aren't supposed to be meaningful to a straight read |
| 15:15.32 | DocScrutinizer05 | who cares |
| 15:15.43 | DocScrutinizer05 | dd won't care if the content is meaningful |
| 15:16.09 | DocScrutinizer05 | cat as well isn't supposed to change data |
| 15:16.48 | kerio | so evidently nanddump is changing the data |
| 15:16.58 | DocScrutinizer05 | :nod: |
| 15:17.16 | DocScrutinizer05 | and I wanna know how and why |
| 15:17.22 | kerio | i don't know enough about mtd to know that :( |
| 15:17.27 | DocScrutinizer05 | before I dare to mess with my CAL content |
| 15:17.49 | *** join/#maemo gena2x (~gena2x@bsdmn.com) |
| 15:18.12 | DocScrutinizer05 | luckily we got a partiton reserved for R&D ;-) |
| 15:20.04 | DocScrutinizer05 | IroN900:~# cat /dev/mtd4|od |
| 15:20.05 | DocScrutinizer05 | 0000000 177777 177777 177777 177777 177777 177777 177777 177777 |
| 15:20.07 | DocScrutinizer05 | * |
| 15:20.08 | DocScrutinizer05 | 10000000 |
| 15:20.14 | DocScrutinizer05 | ;-D |
| 15:20.46 | *** join/#maemo SmilyOrg (Smily@BSN-61-61-6.dial-up.dsl.siol.net) |
| 15:21.06 | kerio | DocScrutinizer05: >:C |
| 15:21.09 | kerio | od /dev/mtd4 |
| 15:21.14 | kerio | stop abusing cats! |
| 15:21.39 | DocScrutinizer05 | nanddump /dev/mtd4|od 2>/dev/null WTF? |
| 15:22.17 | DocScrutinizer05 | 0000000 177777 177777 177777 177777 177777 177777 177777 177777 |
| 15:22.18 | DocScrutinizer05 | * |
| 15:22.20 | DocScrutinizer05 | 10200000 |
| 15:22.23 | kerio | it's got a bit more, yes |
| 15:22.31 | kerio | remove the oob, and you have mtd4 |
| 15:22.49 | DocScrutinizer05 | :nod: |
| 15:23.10 | DocScrutinizer05 | toldya, OOB is probably not read via cat mtd* |
| 15:23.39 | DocScrutinizer05 | like inodes aren't read for cat sdXN |
| 15:24.14 | DocScrutinizer05 | afaik it's OutOfBand info, which got that name for a reason |
| 15:24.41 | kerio | 1755dcebeeb04e075cbd6c6690ed490a - |
| 15:24.42 | kerio | 1755dcebeeb04e075cbd6c6690ed490a /dev/mtd1ro |
| 15:24.56 | kerio | the first is the output of nanddump -o /dev/mtd1ro |
| 15:25.28 | kerio | so there's that |
| 15:25.50 | DocScrutinizer05 | \o/ |
| 15:26.03 | kerio | why doesn't that happen on your n900(s)? |
| 15:26.22 | DocScrutinizer05 | dunno, might be a tribute to late night work |
| 15:26.34 | DocScrutinizer05 | (did those tests yesterday) |
| 15:26.51 | kerio | sudo nanddump -o /dev/mtd1ro | sudo md5sum - /dev/mtd1ro |
| 15:27.08 | kerio | let's just hope libcal doesn't use OOB data :> |
| 15:27.37 | DocScrutinizer05 | kerio: you nifty animal, what a nice cmdline ;-) |
| 15:28.27 | DocScrutinizer05 | OOB data is used by mtd driver |
| 15:28.43 | DocScrutinizer05 | it's kinda like NANDs FAT |
| 15:29.05 | DocScrutinizer05 | or free blocks table |
| 15:29.10 | DocScrutinizer05 | whatever |
| 15:29.30 | DocScrutinizer05 | libcal for sure won't mess with it, for all I know |
| 15:30.05 | DocScrutinizer05 | kerio: now only make sure you never forget to add -b to nanddump, even while for now it seems to make no difference for you |
| 15:30.12 | kerio | k |
| 15:30.44 | *** join/#maemo gena2x (~gena2x@bsdmn.com) |
| 15:31.24 | DocScrutinizer05 | kerio: now you could write your freshly created nanddump image to mtd4, then compare mtd1 and mtd4 ;-) |
| 15:31.35 | kerio | does it fit? |
| 15:31.47 | DocScrutinizer05 | better make a image of mtd4 before |
| 15:31.56 | kerio | mtd4 is empty |
| 15:32.05 | DocScrutinizer05 | I think there's plenty of room on mtd4 for CAL |
| 15:32.18 | DocScrutinizer05 | (empty) I know |
| 15:32.45 | DocScrutinizer05 | so worst case you could flash my empty-mtd4 image to yours if you don't find a better way to erase it |
| 15:33.00 | kerio | DocScrutinizer05: hmm, it's obviously different |
| 15:33.51 | kerio | ok, nanddump -l 393216 -ob /dev/mtd4ro gives me the same thing |
| 15:33.57 | DocScrutinizer05 | kerio: you did md5sum over full devices? |
| 15:34.12 | DocScrutinizer05 | they for sure differ, since iirc mtd4 is way larger |
| 15:34.22 | kerio | DocScrutinizer05: yeah, limiting the length makes it the same |
| 15:34.23 | DocScrutinizer05 | yeah :-D |
| 15:34.36 | DocScrutinizer05 | \o/ |
| 15:35.01 | kerio | and now mtd4 is all weird :( |
| 15:35.08 | DocScrutinizer05 | LOL |
| 15:35.20 | kerio | ok, flash_eraseall did the job |
| 15:35.27 | DocScrutinizer05 | :-D |
| 15:35.34 | kerio | apparently flash_erase requires start and end |
| 15:36.21 | DocScrutinizer05 | yeah |
| 15:36.31 | DocScrutinizer05 | according to their --help |
| 15:38.12 | DocScrutinizer05 | we should push robbiethe1st to finally add kernel and CAL backup and restore to BM ;-) |
| 15:38.56 | DocScrutinizer05 | since I don't feel too comfortable with formating CAL under the arse of libcal |
| 15:39.00 | kerio | DocScrutinizer05: am i a bad enough dude to erase cal and flash it again? |
| 15:39.04 | kerio | oh right |
| 15:39.16 | kerio | ok, something different then |
| 15:39.30 | kerio | am i a bad enough dude to dump the kernel partition, erase it, and write it again from the dumped data? |
| 15:40.21 | DocScrutinizer05 | kerio: I'd say you're as BAD as it gets. Michael Jackson was a sissi compared to you. So go ahead, nuke CAL and reflash it |
| 15:40.32 | kerio | DocScrutinizer05: btw, where's x-loader stored? |
| 15:40.39 | DocScrutinizer05 | or rather, first try with kernel ;-) |
| 15:40.48 | DocScrutinizer05 | in kernel partition |
| 15:40.54 | DocScrutinizer05 | errr NOLO |
| 15:41.04 | kerio | oh, "bootloader" contains both? |
| 15:41.07 | DocScrutinizer05 | yep |
| 15:41.18 | kerio | by the way, /dev/mtd2 is empty too |
| 15:41.27 | DocScrutinizer05 | basdically NOLO is appended to xloader like kernel is to uBoot |
| 15:41.41 | DocScrutinizer05 | not here ;-D |
| 15:42.06 | DocScrutinizer05 | if yours is empty, then you're a lucky man |
| 15:42.27 | kerio | i think i never had a proper kernel panic |
| 15:42.34 | DocScrutinizer05 | or you found another miracle of flasher-3.5 |
| 15:42.57 | DocScrutinizer05 | cat /dev/kmem |
| 15:43.04 | kerio | DocScrutinizer05: fu |
| 15:43.05 | DocScrutinizer05 | the check again |
| 15:43.25 | DocScrutinizer05 | ;-P |
| 15:43.50 | kerio | ok, kernel dumped, erased, written |
| 15:44.12 | DocScrutinizer05 | checked success of erasure? |
| 15:44.19 | kerio | yep |
| 15:44.23 | DocScrutinizer05 | cool man |
| 15:44.50 | DocScrutinizer05 | btw, how's about council, dear Mr. kerio? |
| 15:45.16 | DocScrutinizer05 | ;-) |
| 15:45.20 | kerio | i'm a busy man |
| 15:45.26 | DocScrutinizer05 | hehehe |
| 15:45.42 | DocScrutinizer05 | yeah, same here |
| 15:46.02 | kerio | hm, i wonder if that's the reason we're both always here |
| 15:46.19 | DocScrutinizer05 | no, reason and cause switched ;-) |
| 15:46.51 | kerio | ok, i'll rephrase |
| 15:46.54 | DocScrutinizer05 | we're always here, that's why we're so busy |
| 15:46.57 | kerio | technically i should be a busy man |
| 15:47.23 | DocScrutinizer05 | boot? |
| 15:47.31 | kerio | booted just fine |
| 15:47.36 | DocScrutinizer05 | :-D |
| 15:47.39 | DocScrutinizer05 | \o/ |
| 15:48.08 | DocScrutinizer05 | first instance of kernel flashed without any proprietary Nokia crap tools |
| 15:48.22 | DocScrutinizer05 | TAAADAAAAA dshhhh |
| 15:49.04 | kerio | now, i wonder *what* i flashed |
| 15:49.14 | DocScrutinizer05 | even a heart surgery on the living body |
| 15:49.54 | DocScrutinizer05 | why, is your N900 10 times as fast now? ;-P |
| 15:50.20 | kerio | no, i mean |
| 15:50.27 | kerio | i wonder if it bears any resemblance to the bzImage |
| 15:50.39 | DocScrutinizer05 | err, good question |
| 15:50.51 | DocScrutinizer05 | prolly not to bzImage |
| 15:51.09 | DocScrutinizer05 | but you better ask that to Pali |
| 15:51.23 | DocScrutinizer05 | he seems to know that bz shit |
| 15:51.29 | kerio | Pali: wtf did i flash |
| 15:51.32 | DocScrutinizer05 | headers and all |
| 15:51.37 | Pali | what? |
| 15:52.02 | kerio | Pali: what should the output of "nanddump -ob /dev/mtd3" be? |
| 15:52.12 | kerio | a bzimage with some trailing crap? |
| 15:52.14 | DocScrutinizer05 | Pali: a `cat dev/mtd3 >xxx` |
| 15:52.29 | Pali | special nolo header + zImage |
| 15:52.45 | DocScrutinizer05 | would that result in xxx having any similarity to a bzImage or any other kernel representation? |
| 15:52.45 | kerio | aww :( |
| 15:53.11 | Pali | DocScrutinizer05, some header (2kb maybe) and after that is zImage |
| 15:53.18 | DocScrutinizer05 | yeah |
| 15:53.23 | DocScrutinizer05 | thought as much |
| 15:53.23 | Pali | or other image (u-boot, ...) |
| 15:53.45 | Pali | DocScrutinizer05, old 0xFFFF has support for reverse flash = backup |
| 15:53.57 | DocScrutinizer05 | you (as uBoot maintainer) even should know the length of that header |
| 15:53.59 | Pali | when I have time, I will add it back to new 0xFFFF |
| 15:54.44 | DocScrutinizer05 | Pali: we were after a more generic aproach, fit for arbitrary mtd partitions |
| 15:54.48 | kerio | Pali: why do we need a specialized flasher again? |
| 15:54.56 | kerio | why can't we just prepare the image and then nandwrite? |
| 15:55.04 | DocScrutinizer05 | kerio: because of friggin NOLO |
| 15:55.04 | *** join/#maemo Snafu777 (~Snafu@unaffiliated/snafu777) |
| 15:55.12 | kerio | *prepare the image* |
| 15:55.43 | DocScrutinizer05 | how would you tell NOLO to nandwrite? |
| 15:55.52 | Pali | kerio, problem is that for unknown reason size of header in qemu n900 is not same as size of header on real n900... |
| 15:56.26 | kerio | DocScrutinizer05: i meant the on-device flashing |
| 15:56.35 | kerio | with the silly softupd+flasher |
| 15:56.39 | Pali | kerio, you can start patching 0xFFFF for nandump/nandflash support |
| 15:56.53 | DocScrutinizer05 | well, I for one am happy with a proper CAL and kernel backup on device in vicinity |
| 15:56.56 | Pali | we need to RE that dtupid header |
| 15:57.00 | Pali | *stupid |
| 15:57.09 | kerio | Pali: 0xFFFF basically boils down to preparing a certain image and then writing it to the NAND, doesn't it |
| 15:57.31 | DocScrutinizer05 | no, NOLO writes |
| 15:57.36 | kerio | :o |
| 15:57.44 | Pali | NOLO or softupd write to nand |
| 15:57.57 | Pali | NOLO using NOLO protocol and softupd using MkII protocol |
| 15:57.58 | DocScrutinizer05 | flasher-35 talks to NOLO with some weird (zmodem?) protocol |
| 15:57.58 | kerio | oh, 0xFFFF is on a computer's side |
| 15:58.00 | kerio | i see |
| 15:58.07 | Pali | kerio, also on device side |
| 15:58.11 | Pali | for backup |
| 15:58.18 | kerio | Pali: what does it do on the device side? |
| 15:58.27 | Pali | now nothing |
| 15:58.33 | Pali | but old version had support for backup |
| 15:58.33 | kerio | hm |
| 15:58.43 | Pali | and call to nandflash |
| 15:58.59 | kerio | oh well, i managed to successfully dump, erase and write the kernel partition |
| 15:59.03 | Pali | maybe there was partial RE of that header for 770/N8x0 devices |
| 15:59.05 | kerio | with only mtdtools |
| 15:59.31 | DocScrutinizer05 | not only kernel, even CAL! :-) |
| 15:59.32 | Pali | problem was that 0xFFFF had old source code of mtd tools included |
| 15:59.40 | Pali | so I removed old code |
| 16:00.02 | Pali | and new implementation should use direcl nanddump/nandsomething external applications... |
| 16:00.11 | DocScrutinizer05 | cool |
| 16:00.15 | DocScrutinizer05 | the unix way |
| 16:00.23 | DocScrutinizer05 | kudos, Pali |
| 16:00.31 | kerio | i still don't know if nanddump should skip bad blocks or not |
| 16:00.44 | DocScrutinizer05 | it should |
| 16:00.48 | kerio | are they skipped when reading? |
| 16:00.56 | Pali | somebody who want to implement it? |
| 16:01.02 | Pali | into 0xFFFF? |
| 16:01.03 | DocScrutinizer05 | since nandwrite can't write bad blocks, neither skip them in input |
| 16:01.10 | Pali | I really do not have time for 0xFFFF now.... |
| 16:01.23 | Pali | now loading & booting kernel image working |
| 16:01.31 | Pali | flashing was implemented but not tested |
| 16:01.41 | Pali | and there is missing support for MkII protocol |
| 16:01.48 | Pali | used for eMMC flashing |
| 16:01.53 | Pali | and flashing N950 |
| 16:02.53 | Pali | DocScrutinizer05, are you going to implement kernel & CAL backup to 0xFFFF? |
| 16:02.53 | kerio | DocScrutinizer05: sheevaplug > n900 |
| 16:03.03 | kerio | you can just nandwrite to the kernel mtd partition there |
| 16:03.08 | DocScrutinizer05 | Pali: hardly, though it might be fun |
| 16:03.18 | DocScrutinizer05 | probably not enough time |
| 16:04.34 | DocScrutinizer05 | I *might* pimp BM though |
| 16:05.02 | DocScrutinizer05 | o/ |
| 16:05.21 | *** join/#maemo sq-one (~sq-one@p549AB447.dip.t-dialin.net) |
| 16:05.21 | DocScrutinizer05 | gotta get to see some few hours of RL on this weekend |
| 16:08.26 | kerio | Pali: does your uboot also read some configuration file on the uSD? |
| 16:08.51 | Pali | kerio, no |
| 16:09.11 | Pali | but there is SD support |
| 16:09.26 | kerio | so you can configure uboot from the terminal... |
| 16:09.26 | Pali | so you can load & run script/kernel from SD card |
| 16:09.29 | kerio | i see |
| 16:09.59 | kerio | i suppose i *should* keep uboot installed, just so i can recover in an emergency |
| 16:10.17 | DocScrutinizer05 | cool, somebody edited Community_SSU wiki page, with an actually useful small addition |
| 16:10.18 | Pali | kerio, you can boot resuceos from uboot |
| 16:10.21 | kerio | an emergency that makes me lose the uUSB port |
| 16:11.54 | DocScrutinizer05 | you should edit uBoot-script on eMMC/MyDocs to offer the menu entry for jumping to uSD and boot the kernel and rootfs from there |
| 16:12.16 | kerio | DocScrutinizer05: you can configure uboot from the device |
| 16:12.25 | kerio | it's got a console |
| 16:12.29 | gena2x | seem my n900 reboots in loop. can anyone help? What i tried: boot Mer from sd (fails to boot kernel), reflash (fails to flash, only boots my pali bootloader)... |
| 16:12.36 | DocScrutinizer05 | you however shoud try to do that without messing with files in /etc/bootmenu.d/ |
| 16:13.05 | kerio | gena2x: "reflash" what? |
| 16:13.14 | DocScrutinizer05 | kerio: I know genuine uBoot, I know it has a console. I also recall it sucks donkeyballs |
| 16:13.23 | gena2x | kerio, emmc and combined image |
| 16:13.30 | kerio | no you didn't |
| 16:13.38 | kerio | otherwise you would've also flashed the kernel |
| 16:14.15 | gena2x | maemo kernel seem boot, but then device restarts |
| 16:14.17 | DocScrutinizer05 | gena2x: FLASHING IS THE PATH. iF IT FAILS, YOU DIDN'T READ THE ~FLASHING INSTRUCTIONS CAREFULLY |
| 16:14.26 | DocScrutinizer05 | OOPS capslock |
| 16:14.42 | gena2x | DocScrutinizer05, hi my evil doc, i followed all instructions of course |
| 16:14.56 | DocScrutinizer05 | did you do the test for empty battery? |
| 16:15.16 | gena2x | i bought new one... |
| 16:15.24 | DocScrutinizer05 | but did you do the test? |
| 16:15.32 | gena2x | for new battery??? |
| 16:15.36 | kerio | gena2x: if you're still getting uboot, then you botched the flash |
| 16:15.45 | DocScrutinizer05 | yep |
| 16:16.04 | DocScrutinizer05 | so, pretty please: 1. do battery test |
| 16:16.07 | gena2x | kerio, what i have is a: pali u-boot (work), it can boot kernel (reboots) |
| 16:16.13 | DocScrutinizer05 | hold 'u', plug in wallcharger |
| 16:16.51 | gena2x | kerio, pali boot also 'try' to boot mer (which worked a week ago!), it loads the kernel, but kernel can't start |
| 16:17.11 | DocScrutinizer05 | hmm, how could we help? |
| 16:17.47 | gena2x | DocScrutinizer05, sorry, i think battery test can't help in this situation... |
| 16:17.58 | Pali | full reflash |
| 16:18.06 | DocScrutinizer05 | you got exactly two options: set no_wd-timer flag, or reflash straight away |
| 16:18.07 | kerio | gena2x: correctly flashing VANILLA and COMBINED will give you a n900 at near-factory-conditions |
| 16:18.26 | Pali | combined, emmc, combined |
| 16:18.30 | DocScrutinizer05 | gena2x: ok, if you're already knowing ehat can help, why do you ask here? |
| 16:18.44 | Snafu777 | anyone get reaver working on the n900? |
| 16:18.48 | Snafu777 | without uninstalling kismet |
| 16:18.48 | kerio | right, combined, vanilla, combined |
| 16:18.51 | gena2x | DocScrutinizer05, welcome back to my ignore list |
| 16:18.59 | DocScrutinizer05 | :shrug: |
| 16:19.15 | kerio | Snafu777: why would kismet cause problems to reaver? |
| 16:19.25 | Snafu777 | dunno |
| 16:19.28 | Snafu777 | want to see the output? |
| 16:19.31 | kerio | (make sure you have the injection drivers with monitor mode enabled) |
| 16:19.33 | DocScrutinizer05 | welcome back to BOFH chan moderating. I won't tolerate asking questions and ignoring perfectly fine answers |
| 16:19.42 | gena2x | you btw is the only person in my ignore list for all time i am using irc |
| 16:19.50 | kerio | LART! LART! LART! LART! |
| 16:19.54 | gena2x | and forums and internet |
| 16:19.57 | Snafu777 | The following packages have unmet dependencies: |
| 16:19.57 | Snafu777 | <PROTECTED> |
| 16:19.57 | Snafu777 | E: Broken packages |
| 16:20.11 | Snafu777 | Nokia-N900:~# apt-get install libpcap1 |
| 16:20.13 | gena2x | sorry people, just some old stuff |
| 16:20.19 | Snafu777 | The following packages will be REMOVED: |
| 16:20.19 | Snafu777 | <PROTECTED> |
| 16:20.19 | Snafu777 | The following NEW packages will be installed: |
| 16:20.19 | Snafu777 | <PROTECTED> |
| 16:20.20 | Pali | why you have -dev package installed? |
| 16:20.21 | Snafu777 | =( |
| 16:20.25 | Snafu777 | cuz u need it |
| 16:20.29 | *** join/#maemo Dynamit (~Mohamed@84-55-71-22.customers.ownit.se) |
| 16:20.33 | kerio | no you don't |
| 16:20.34 | DocScrutinizer05 | Snafu777: stop that shit! |
| 16:20.42 | Snafu777 | eh Doc? |
| 16:20.43 | Pali | do you compiling something on n900? |
| 16:20.50 | Snafu777 | trying to run configure for reaver |
| 16:21.06 | Snafu777 | and from what i understand i need libpcap to configure it |
| 16:21.08 | kerio | Snafu777: do you even have a compiler on your n900? |
| 16:21.11 | gena2x | Pali: i can't flash anything |
| 16:21.17 | Snafu777 | bangs his head... |
| 16:21.17 | kerio | Snafu777: just grab the prebuilt reaver package |
| 16:21.25 | Snafu777 | is it in the repos? |
| 16:21.26 | Pali | Snafu777, compile it in scratchbox |
| 16:21.29 | kerio | Snafu777: also, don't paste more than a couple lines, use a pastebin |
| 16:21.29 | Pali | not on n900 |
| 16:21.39 | Snafu777 | hah |
| 16:21.40 | Snafu777 | okay |
| 16:21.42 | Snafu777 | im an idiot |
| 16:21.45 | Snafu777 | apt-get install reaver |
| 16:21.48 | Snafu777 | bangs his head hard |
| 16:21.49 | kerio | Snafu777: it's in extras-devel |
| 16:21.55 | Snafu777 | yep |
| 16:21.57 | Snafu777 | it sure is |
| 16:22.17 | Snafu777 | i just always try source first => |
| 16:22.20 | gena2x | Pali, oh, i got it, combined-emmc-combined |
| 16:22.39 | gena2x | Pali, i followed instructions on nokia site told me to flash emmc first... |
| 16:22.56 | DocScrutinizer05 | Pali: could you tell gena2x this is written on ~flashing in all verbosity that makes you wheep |
| 16:22.58 | gena2x | Pali, combined first really work, thanks |
| 16:24.19 | kerio | gena2x: it's explained multiple times in ~flashing, btw |
| 16:24.28 | Pali | ~flashing |
| 16:24.28 | infobot | hmm... maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware |
| 16:24.33 | *** join/#maemo RP_ (~richard@93-97-173-237.zone5.bethere.co.uk) |
| 16:25.52 | gena2x | really sorry guys, just that man once told me that i stole his code... after 2 hour of talk it turned out that 'i am other person', and etc, etc, for some reason he just hates me, i don't know why, this is not my general attitude to people, but i just can't stand him anymore. |
| 16:25.58 | DocScrutinizer05 | sure, he followed every single detail on that page, and when I give reasonable advice he tells me he knows better what can help and what won't, and I make it on his ignore that way |
| 16:26.40 | DocScrutinizer05 | gena2x: nobody is interested in your lame personal problems |
| 16:27.23 | DocScrutinizer05 | at least not here in this chan |
| 16:27.32 | DocScrutinizer05 | take it to the chan where it happened |
| 16:28.18 | DocScrutinizer05 | you came here for help, you rejected perfectly sane help |
| 16:28.35 | DocScrutinizer05 | don't try to find lame excuses for that nasty behaviour |
| 16:29.21 | Lava_Croft | yeah, thats only allowed for people who have gained enough social standing |
| 16:30.22 | DocScrutinizer05 | rejecting help on a "I know nuttin that's why I came here, but I know THIS won't help" basis. No sir, nobody is allowed such attitude |
| 16:31.23 | Lava_Croft | i guess you just disqualified yourself by disallowing someone to have a certain attitude |
| 16:31.26 | Lava_Croft | Good night! |
| 16:31.57 | *** join/#maemo guampa (~guampa@unaffiliated/guampa) |
| 16:32.36 | DocScrutinizer05 | I guess you were a tad picky on my words. everybody can have attitude whatever he wants, attitudes are like assholes, everybody has one. But *exposing* such attitude in this chan isn't tolerated |
| 16:33.38 | Snafu777 | Wow |
| 16:33.40 | Snafu777 | You guys are angry |
| 16:33.48 | DocScrutinizer05 | since it is leaching time of otherwise way more productive people, to explain solutions to the guy who loves to plain reject them, based on arrogance |
| 16:33.48 | Lava_Croft | No |
| 16:33.50 | Snafu777 | You all need to chill |
| 16:33.56 | kerio | grabs some popcorn |
| 16:33.59 | Lava_Croft | I just dont understand why apologies are so hard to accept :) |
| 16:33.59 | Snafu777 | Just find something and exploit it |
| 16:34.03 | Snafu777 | Write some code |
| 16:34.07 | Snafu777 | and force a change for good |
| 16:34.18 | kerio | *munch munch* |
| 16:34.27 | Lava_Croft | And why it's almost exclusively the same person over and over who is the source of a certain kind of vitriol |
| 16:34.38 | Lava_Croft | But I guess I'm not the first wondering, nor the last |
| 16:35.06 | Lava_Croft | But, I am stretching my luck here, good night! :) (no hard feelings whatsoever!) |
| 16:35.23 | Snafu777 | U know what is fun? |
| 16:35.33 | Snafu777 | Sitting in the subway drive through |
| 16:35.39 | Snafu777 | Running aircrack with my n900 |
| 16:35.43 | Snafu777 | breaking the wep |
| 16:35.51 | Snafu777 | and syn flooding the router, causing the credit card machine not to work |
| 16:35.56 | NIN101 | that's lame. |
| 16:35.58 | Snafu777 | proving that the owner is in violation of pcidss rules |
| 16:36.00 | kerio | you know what else is fun? |
| 16:36.09 | kerio | admitting to felonies on the internet |
| 16:36.11 | DocScrutinizer05 | Snafu777: lol |
| 16:36.13 | Snafu777 | Yeah? |
| 16:36.15 | Snafu777 | Its a blast |
| 16:36.21 | Snafu777 | Considering its my words |
| 16:36.23 | Snafu777 | with no proof -=) |
| 16:36.28 | Snafu777 | But is it a crime? |
| 16:36.30 | Snafu777 | Really |
| 16:36.37 | Snafu777 | Or is it a forray into ethics |
| 16:36.43 | Snafu777 | Good discussion |
| 16:36.45 | Snafu777 | if u ask me |
| 16:37.28 | DocScrutinizer05 | Snafu777: if your lines would consist of more than avrg 2.3 words, it was way easier to read what you say |
| 16:37.30 | *** join/#maemo e-yes (~e-yes@77.51.17.83) |
| 16:38.18 | Snafu777 | Man, yer an angry dude Doc |
| 16:38.34 | DocScrutinizer05 | i'm not angry - I give advice with a smile |
| 16:38.48 | Snafu777 | I type how i think man, sry if that bothers ya |
| 16:39.06 | DocScrutinizer05 | it bothers all those with small screen |
| 16:39.29 | Snafu777 | get a bigger screen or use bigger font......? =-) |
| 16:39.41 | DocScrutinizer05 | since your text scrolls off on top before anybody made to read all those jumping lines |
| 16:39.59 | Snafu777 | I call it Physical Training for the Eyes |
| 16:40.08 | DocScrutinizer05 | not everybody has a IRC reader wirh softscroll |
| 16:40.23 | DocScrutinizer05 | we're not in here for physical eye training |
| 16:40.25 | Snafu777 | Im helping you to become stronger |
| 16:40.39 | Lava_Croft | ok, not entirely good night yet! |
| 16:40.49 | NIN101 | trolls here, trolls there. |
| 16:40.51 | Snafu777 | Anyone want a copy of HydraFy or Ferret for the N900? |
| 16:42.05 | Lava_Croft | Instead of discuss important matters, we can all just watch someone jump from the edge of space |
| 16:42.15 | Lava_Croft | if gootube doesnt break down |
| 16:42.21 | Snafu777 | whens he jumping? |
| 16:42.37 | Lava_Croft | very soon |
| 16:42.45 | Lava_Croft | http://www.redbullstratos.com/live/ |
| 16:42.50 | Snafu777 | nice |
| 16:42.51 | Snafu777 | watchin |
| 16:43.03 | Lava_Croft | The stream is rather flaky |
| 16:43.03 | DocScrutinizer05 | is it a plane? is it a meteor? NOOOO it's Superma.... err what's the name of this guy? |
| 16:43.12 | Lava_Croft | Felix Baumgartner i think |
| 16:43.16 | DocScrutinizer05 | yep |
| 16:43.25 | DocScrutinizer05 | mach 1.5 or sth |
| 16:43.30 | Lava_Croft | i just wanna see him go through the sound barrier |
| 16:43.39 | gena2x | anyway, thanks much to all combined-emmc-combined way seems helped. It booted! |
| 16:43.41 | Lava_Croft | if i can see that on live video today, ill be just fine |
| 16:43.47 | Lava_Croft | gena2x: \o/ |
| 16:44.18 | Snafu777 | wow |
| 16:44.21 | Snafu777 | thanks for the reminder |
| 16:44.24 | Snafu777 | History here... |
| 16:44.48 | Lava_Croft | I'm watching this for the same reason I watch other ridiculous 'sports' |
| 16:44.50 | gena2x | and i've found nothing like that on wiki, wiki only tell that you need to flash emmc then combined |
| 16:44.51 | Lava_Croft | like Formula1 |
| 16:45.00 | Lava_Croft | i just hope something goes horribly wrong |
| 16:45.25 | Lava_Croft | gena2x: yes, the solution to problems caused by wrong flashing order are hard to find |
| 16:45.26 | kerio | hahaha |
| 16:45.30 | DocScrutinizer05 | http://wiki.maemo.org/Updating_the_tablet_firmware#Flashing_the_eMMC_in_the_N900 >> Note however that eMMC flashing will fail when your rootfs is completely messed up, the recommended flash sequence then is rootfs, eMMC, rootfs *again*.<< (Author: guess-who) |
| 16:45.48 | Lava_Croft | that didnt work for me iirc |
| 16:45.52 | Lava_Croft | i had to first flash older PR |
| 16:45.57 | Lava_Croft | and then newer PR, before it booted |
| 16:46.03 | DocScrutinizer05 | o.O |
| 16:46.04 | kerio | gena2x: "Note however that eMMC flashing will fail when your rootfs is completely messed up, the recommended flash sequence then is rootfs, eMMC, rootfs *again*. " |
| 16:46.07 | Lava_Croft | or just kernel from older PR, i dont recall correctly |
| 16:46.11 | Lava_Croft | its been a while |
| 16:47.50 | gena2x | kerio, whoops, than my bad, i skipped 'rationale'... |
| 16:48.26 | gena2x | Full citation: "Rationale: on accidental booting in between the 2 flash processes, the sequence formerly suggested (rootfs first) will result in a broken system. The sequence "eMMC first, then rootfs" is checked back with Nokia affiliates and is proven to work as long as your rootfs still is somewhat functional. Note however that eMMC flashing will fail when your rootfs is completely messed up, the recommended flash sequence then is rootfs, eMMC, rootfs *again*. |
| 16:48.26 | gena2x | <PROTECTED> |
| 16:48.40 | gena2x | didn't expect instructions in rationale... |
| 16:48.41 | Lava_Croft | DocScrutinizer05: iirc, doing the rootsfs -> emmc --> rootfs again thing just kept hanging at a certain percentage while flashing |
| 16:48.47 | DocScrutinizer05 | Lava_Croft: rootfs flashing is used as synonum for "flash COMBINED FIASCO image with rootfs, kernel, all that sh*t" in all that page. I don't think I ever heard it will fail unless you flash a former version first |
| 16:48.48 | Lava_Croft | (in my case) |
| 16:49.14 | Lava_Croft | yes, thats what i mean with rootfs too |
| 16:49.27 | Lava_Croft | i use it to name the .bin that not the emmc .bin :P |
| 16:49.43 | DocScrutinizer05 | then your experience is really a special case |
| 16:50.20 | Lava_Croft | the thing is, im almost 100% certain it was the same problem for which i sent another n900 back to nokia care |
| 16:50.30 | Lava_Croft | but meh, i will never know |
| 16:50.36 | kerio | DocScrutinizer05: heh, i just realized that if my microsd breaks i'm hosed |
| 16:50.40 | DocScrutinizer05 | well, those hangs on halfway are a rather ininvestigated mystery with flashing |
| 16:50.57 | kerio | well, i'd have to reflash |
| 16:51.08 | Lava_Croft | DocScrutinizer05: i had to flash an old PR, or part of it, for the newer PR to get flashed properly |
| 16:51.18 | Lava_Croft | that i know for certain, i really should have remembered the details |
| 16:51.33 | Lava_Croft | now i feel sad about not knowing it exactly anymore |
| 16:51.43 | *** join/#maemo SpeedEvil_ (~quassel@mauve.plus.com) |
| 16:51.45 | Lava_Croft | Baumgartner better fail hard, so i can cheer up |
| 16:51.46 | DocScrutinizer05 | realy strange, there's hardly any good explanation why this happens |
| 16:52.04 | Lava_Croft | im not an engineer, screw explanations:) |
| 16:52.23 | DocScrutinizer05 | Lava_Croft: don't worry, we'll find out about that bugger too, eventually |
| 16:53.50 | DocScrutinizer05 | once we got a proper full-featured replacement for friggin flasher-3.5, and maybe even some insight into NOLO, we might actually succeed in debugging such cases |
| 16:55.06 | DocScrutinizer05 | until then, we're happy you recovered on the second time it hit you, and we hope the experience will add to our toolbox |
| 16:55.32 | DocScrutinizer05 | it's a really rare case anyway |
| 16:55.36 | Lava_Croft | who hit the PR button? |
| 16:55.45 | Lava_Croft | Im fairly sure i didnt touch anything |
| 16:56.14 | Lava_Croft | Unless you are Nokia, there's not reason to use such language |
| 16:56.18 | Lava_Croft | no* |
| 16:56.26 | DocScrutinizer05 | well, sorry then |
| 16:56.35 | DocScrutinizer05 | cya |
| 16:56.51 | Lava_Croft | This feels like the Twilight Zone right now |
| 16:56.56 | DocScrutinizer05 | I'm really not in the mood to argue for argument's sake |
| 16:56.58 | Lava_Croft | I'll head out! |
| 16:57.00 | *** join/#maemo madalu (~user@unaffiliated/madalu) |
| 16:57.05 | Lava_Croft | o/ |
| 16:57.18 | kerio | trolls trolling trolls |
| 16:59.20 | DocScrutinizer05 | kerio: yeah, and *me* is the angry man then, esp when I feel like it's maybe time to hit the eject button |
| 17:00.06 | kerio | don't be upset |
| 17:00.09 | kerio | have a puppy: http://i.imgur.com/YqlLn.jpg |
| 17:00.13 | DocScrutinizer05 | nah, just bored |
| 17:00.16 | Lava_Croft | Maybe I need to add some "this is not intended very seriously" sign or something |
| 17:00.30 | gena2x | ahh, have to reinstall everything. |
| 17:00.34 | Lava_Croft | I was merely amazed at how you suddenly started to talk like the guy who provided me with/produced my n900 |
| 17:00.46 | Lava_Croft | I was not trying to sound angry :< |
| 17:01.08 | kerio | Lava_Croft: well, #maemo *is* the current n900 helpdesk, pretty much |
| 17:01.15 | kerio | this reminds me |
| 17:01.26 | kerio | deepy: did you fix the kbd slider? |
| 17:04.02 | *** join/#maemo rzr (~rzr@82.236.136.171) |
| 17:04.43 | DocScrutinizer05 | lost his magnet? |
| 17:05.05 | kerio | something like that, yes |
| 17:05.12 | DocScrutinizer05 | :nod: |
| 17:05.21 | kerio | it's easily fixable, right? |
| 17:05.26 | DocScrutinizer05 | sure |
| 17:05.39 | DocScrutinizer05 | get a tiny magnet, and some good glue |
| 17:07.35 | DocScrutinizer05 | though, when device thinks slide is _open_ all the time, odds are original magnet sticks to hall-switch and you only need some glue to fix it in postion where it belongs |
| 17:07.40 | gena2x | starts doing backups... |
| 17:25.07 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 17:25.35 | *** join/#maemo zsolt (~zsolt@catv-89-132-223-220.catv.broadband.hu) |
| 17:26.51 | zsolt | what can I do?to charge need to short data+ and data - on usb cable,but if I do this can't use any peripheral |
| 17:30.27 | kerio | zsolt: you need to short D+/D- on the charger's side |
| 17:30.30 | kerio | but that's it |
| 17:30.38 | kerio | aren't you using one of those Y cables? |
| 17:30.45 | zsolt | yes I do |
| 17:30.49 | kerio | the "power" side doesn't even have D+/D- i think |
| 17:32.17 | zsolt | figured out,that if short d+ and d- on the power side n900 wont recognize it |
| 17:32.43 | zsolt | so i have to short it on the cable that goes to phone directly |
| 17:33.41 | zsolt | http://talk.maemo.org/showthread.php?t=85658&page=7 built my own set by this article's shematic |
| 17:36.05 | *** join/#maemo SpeedEvil_ (~quassel@mauve.plus.com) |
| 17:36.15 | kerio | DocScrutinizer05: by the way, when toying with uboot today, i eventually had to flash a real kernel from my computer |
| 17:36.23 | kerio | and when i booted it, i got the datepicker screen |
| 17:37.12 | kerio | why? |
| 17:37.17 | kerio | i never removed the battery |
| 17:37.35 | kerio | and besides, my bupbat still holds, i think |
| 17:40.10 | DocScrutinizer05 | zsolt: that Y-cable is for powering N900 during hostmode. It's definitely _not_ the right solution for general charging purposes, using bme (nevermind if you dunno what's bme) and fastcharger/carcharger |
| 17:40.39 | DocScrutinizer05 | kerio: NOLO might reset the RTC chip |
| 17:40.46 | DocScrutinizer05 | on flashing kernel |
| 17:40.49 | DocScrutinizer05 | who knows |
| 17:41.04 | *** join/#maemo RP_ (~richard@93-97-173-237.zone5.bethere.co.uk) |
| 17:42.01 | zsolt | what i try to do is charging my phone at the sime time as use peripherals |
| 17:42.36 | DocScrutinizer05 | kerio: look, RTC just has a flag register telling system whether it's all ok, or flawed by bupbat/power_dropout, or other general borkage |
| 17:43.00 | DocScrutinizer05 | zsolt: so h-e-n with charging |
| 17:44.54 | DocScrutinizer05 | for h-e-n USB-hostmode with charging you need to use our charger script (sth like e.g. ShadowJK's charge21.sh) and that script shouldn't care about D+/- short, it even mustn't try to detect D+/- short since that breaks real USB data connection |
| 17:45.44 | ShadowJK | it does try do that |
| 17:45.57 | ShadowJK | but it's a cat you could comment out |
| 17:46.29 | GGon | goddamn raspberry pi |
| 17:46.57 | DocScrutinizer05 | or rather, check if musb-hdrc is in hostmode, then skip the D+- check |
| 17:47.22 | DocScrutinizer05 | smells charge22.sh |
| 17:48.51 | ShadowJK | The reason it does it is that when connected to real wallcharger it reduces power consumption by 80mA :-) |
| 17:49.28 | DocScrutinizer05 | I might feel like patching that scriptie into charge30.sh, taking cmdline parameters like cur-max, no-softstart, no-dlineshort-check |
| 17:50.13 | DocScrutinizer05 | yeah, the 80mA eaten by musb-hdrc not suspended |
| 17:50.22 | DocScrutinizer05 | and ULPI likewise |
| 17:50.29 | ShadowJK | charge3* is my secret experimental branch :) |
| 17:50.54 | DocScrutinizer05 | mhm, so I should name it charge42 then ;-D |
| 17:51.34 | ShadowJK | lol |
| 17:54.03 | *** join/#maemo MacDrunk (~marper@201.165.163.183) |
| 17:55.35 | *** part/#maemo MacDrunk (~marper@201.165.163.183) |
| 17:56.41 | kerio | 42 is clearly better than any other number |
| 17:57.58 | *** join/#maemo _rd (~rd@p57B48B75.dip0.t-ipconnect.de) |
| 17:58.29 | *** join/#maemo ZogG_laptop (~ZogG_lapt@109.64.221.173) |
| 17:58.29 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 18:00.01 | zsolt | thank you |
| 18:00.28 | DocScrutinizer05 | yw |
| 18:01.12 | kerio | zsolt: if you like hot new things, install kp52 and use bq2415x_charger |
| 18:01.28 | DocScrutinizer05 | :-D |
| 18:02.33 | kerio | instead of running scripts, you just "echo auto > /sys/class/something/mode" |
| 18:02.35 | DocScrutinizer05 | zsolt: if you like it convenient you might want to wait a bit longer before you dive into that adventure |
| 18:03.24 | DocScrutinizer05 | kerio: just that "not running scripts" for now also means "no proper feedback about what's going on" |
| 18:04.26 | DocScrutinizer05 | and the USB speed autodetect is far from being reliable yet |
| 18:04.30 | kerio | btw, what's the procedure to connect something that won't work at all with only 200mA? |
| 18:04.44 | *** join/#maemo retro|cz (~retro@106.142.broadband6.iol.cz) |
| 18:06.01 | DocScrutinizer05 | start h-e-n, start boostmode, plug powersupply to Y-cable and 1 second later plug Y-cable to N900 |
| 18:06.14 | DocScrutinizer05 | enumerate |
| 18:06.30 | DocScrutinizer05 | stop boostmode and start charge21.sh |
| 18:06.47 | kerio | oh, so boostmode still has to be on when enumerating |
| 18:06.50 | DocScrutinizer05 | s/mode/on/ |
| 18:07.20 | DocScrutinizer05 | kerio: doesn't really matter |
| 18:07.38 | DocScrutinizer05 | kerio: what matters though is not delaying enum too much |
| 18:07.48 | kerio | why's that? |
| 18:07.54 | DocScrutinizer05 | while stopping booston can be done any time |
| 18:08.47 | DocScrutinizer05 | that's because of some peripherals will "time out" on USB crank-up when ENUM is delayed too long after VBUS got applied |
| 18:09.06 | kerio | bleh |
| 18:09.08 | kerio | :s |
| 18:09.15 | DocScrutinizer05 | while other peripherals need like 30s before they even are ready to start enum |
| 18:09.40 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 18:11.56 | DocScrutinizer05 | so the sequence is: select speed, apply VBUS, [label:A] wait 3s, try ENUM, IF (ENUM_failed):A, wait 5s, mount. |
| 18:13.27 | kerio | meh |
| 18:13.28 | DocScrutinizer05 | only then "waste time" on dealing with charging |
| 18:13.32 | kerio | i need a tiny usb HUB |
| 18:13.34 | kerio | *hub |
| 18:13.50 | DocScrutinizer05 | pretty good idea |
| 18:14.56 | kerio | a cheap one that can be powered externally |
| 18:14.59 | DocScrutinizer05 | get a battery pack with not only a (one) USB-F outlet, but actually that outlet being upstream port with power of an embedded hub |
| 18:16.27 | DocScrutinizer05 | get a 3-pos switch on that package: off | fastcharger | hub |
| 18:16.55 | kerio | but... i don't want a battery pack :( |
| 18:17.06 | DocScrutinizer05 | with fastcharger pos obviously not powering hub electronics but only "upstream" port, and also shorting D+- |
| 18:19.50 | *** join/#maemo rcg (~rc@e183145024.adsl.alicedsl.de) |
| 18:24.06 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 18:26.14 | *** join/#maemo NIN101 (~NIN@p5DD281B2.dip0.t-ipconnect.de) |
| 18:29.08 | zsolt | thank you |
| 18:38.21 | Pali | kerio, 47 is better random number :D |
| 18:38.38 | kerio | Pali: 42 is everything but random |
| 18:38.56 | DocScrutinizer05 | ~42 |
| 18:38.56 | infobot | hmm... 42 is the answer to life the universe and everything, see also http://en.wikipedia.org/wiki/the_answer_to_life,_the_universe,_and_everything |
| 18:38.58 | kerio | Pali: anyway, make uboot+kp52 plskthx |
| 18:39.29 | Pali | kerio, I do not have time... |
| 18:39.36 | kerio | :c |
| 18:39.42 | kerio | it'll take like 20 seconds! |
| 18:40.01 | kerio | unless your upload speed is *really* bad |
| 18:40.16 | kerio | i don't have the latest uboot without an attached kernel |
| 18:41.41 | Pali | kerio, I need to look at & test patches from dfries http://gitorious.org/~dfries/community-ssu/dfriess-kernel-cssu |
| 18:41.53 | Pali | and also fiasco-image-update-ask must work |
| 18:42.08 | kerio | fiasco-image-update-ask worksforme |
| 18:42.23 | kerio | i tried kp52->kp52 (didn't ask), kp52->uboot (asked), uboot->kp52 (asked) |
| 18:42.45 | Pali | ok, thanks for testing! |
| 18:43.07 | Pali | kerio, and I have some problems here: https://www.spoj.pl/CHU12_Z1/problems/easy/ |
| 18:43.31 | freemangordon | Pali: almost ready with cal, any idea how to test it? |
| 18:43.32 | Pali | also some homeworks to school and ... |
| 18:43.49 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 18:44.05 | Pali | freemangordon, for testing cal is good qemu |
| 18:44.13 | Pali | n900 image in qemu |
| 18:44.18 | freemangordon | hmm |
| 18:44.27 | freemangordon | no such animal here |
| 18:44.30 | Pali | part of madde |
| 18:44.32 | kerio | Pali: hmm, SUMFOUR is weird |
| 18:45.03 | kerio | Pali: 10 seconds is... not a lot |
| 18:45.08 | Pali | SUMFOUR is solved :-) |
| 18:45.38 | Pali | also BOTTOM and SUMITR |
| 18:45.41 | kerio | Pali: is it doable in the naïve way? |
| 18:45.56 | Pali | kerio, no :-) |
| 18:46.46 | freemangordon | recursion? |
| 18:46.52 | Pali | but O(N^2*log(N)) is ok |
| 18:47.14 | kerio | Pali: hmm, sort the lists and do stuff with that, or something |
| 18:48.04 | freemangordon | Pali: could you help me with testing? |
| 18:48.26 | kerio | freemangordon: you can test it on the device, CAL is restorable! :D |
| 18:48.31 | Pali | freemangordon, first you dump CAL to pc and test in under nandsim |
| 18:48.46 | freemangordon | so far I should have cal_read_block ready |
| 18:48.46 | kerio | remember to dump it with nanddump -ob |
| 18:49.05 | Pali | $ sudo modprobe nandsim first_id_byte=0x20 second_id_byte=0xaa third_id_byte=0x00 fourth_id_byte=0x15 parts=1,3,2,16,16,2010 |
| 18:49.09 | Pali | on pc ^^^ |
| 18:49.19 | freemangordon | Pali: onlu /dev/mtd1? |
| 18:49.28 | freemangordon | *only |
| 18:49.39 | Pali | this will create nand device (with same n900 partitions) in RAM |
| 18:49.49 | freemangordon | the problem is I don't know what to try to read :D |
| 18:50.02 | freemangordon | 256MB? |
| 18:50.12 | Pali | yes |
| 18:50.18 | Pali | cat /dev/mtd1 > dump |
| 18:50.18 | freemangordon | comeon, my virtual machine has only 512 :D:D:D |
| 18:50.34 | freemangordon | hmm, ok |
| 18:50.36 | Pali | ok, look at modinfo nandsim |
| 18:50.44 | Pali | there should be param for smaller nand |
| 18:51.13 | freemangordon | Pali: that part is easy, more problematic is what am I supposed to read |
| 18:51.34 | Pali | sudo cat /dev/mtd1 > dump |
| 18:51.38 | freemangordon | ok |
| 18:51.40 | Pali | copy dump to pc |
| 18:51.44 | freemangordon | but what to read from CAL? |
| 18:52.06 | freemangordon | cal_read_block needs some parameters, you know :P |
| 18:52.06 | Pali | look at program calvaria |
| 18:52.14 | Pali | it can parse CAL data |
| 18:52.22 | Pali | so you will see what you can read |
| 18:52.33 | Pali | it can show all sections in CAL |
| 18:53.14 | freemangordon | are you sure it supports everything in CAL? as comparing opencal with my source, there is lots of stuff not supportd |
| 18:53.23 | freemangordon | Pali: there are 4 sections :D |
| 18:53.41 | freemangordon | section1/2, usersection and write-protect section |
| 18:54.00 | freemangordon | at least that is what I understood from the code |
| 18:54.11 | freemangordon | so I don;t need calravia to do that |
| 18:54.28 | Pali | calvaria only parse data, it show everything |
| 18:54.35 | Pali | write protect has other flag |
| 18:54.51 | freemangordon | do you have binary? |
| 18:54.51 | Pali | it also show old data |
| 18:55.28 | Pali | only source code: svn://svn.openwrt.org/openwrt/packages/utils/calvaria/files/src |
| 18:55.40 | freemangordon | this is not binary :D:D:D |
| 18:55.42 | freemangordon | but ok |
| 18:58.12 | kerio | why does openwrt care about CAL? |
| 18:58.19 | kerio | i thought it was a nokia-specific thing |
| 18:58.28 | DocScrutinizer05 | obviously not |
| 18:58.48 | DocScrutinizer05 | or wrt invented it for their N900 port |
| 18:59.52 | *** join/#maemo pcfe (~pcfe@brln-4d0ce52e.pool.mediaWays.net) |
| 18:59.52 | *** join/#maemo pcfe (~pcfe@redhat/pcfe) |
| 18:59.59 | kerio | freemangordon: 256mb is perfect, you have 256mb of nand and 256mb of usable ram :D |
| 19:01.45 | freemangordon | WTF? cal.h:4:26: error: mtd/mtd-user.h: No such file or directory |
| 19:05.27 | *** join/#maemo SpeedEvil_ (~quassel@mauve.plus.com) |
| 19:05.31 | *** join/#maemo avtobiff (~avtobiff@c-5a3e70d5.018-61-73746f28.cust.bredbandsbolaget.se) |
| 19:08.49 | avtobiff | hi! i am trying to figure out how to add a button to the Conversations HildonAppMenu. I have read UI docs and tutorials but still can't figure it out. I am using Pythno |
| 19:08.52 | avtobiff | Python |
| 19:14.53 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 19:15.46 | DocScrutinizer05 | afaik conversations is using browserd to show some local "html-page" as UI |
| 19:16.06 | avtobiff | do you by any chance now where i can find docs about this? |
| 19:16.14 | DocScrutinizer05 | hardly |
| 19:16.19 | avtobiff | :) |
| 19:16.30 | DocScrutinizer05 | search tmo for any tweaks to conversation |
| 19:17.04 | *** join/#maemo M4rtinK (~M4rtinK@mail.melf.eu) |
| 19:17.11 | DocScrutinizer05 | I seem to recall somebody changed some aspects of the GUI, like left vs right side to show icons, or sth like that |
| 19:18.01 | DocScrutinizer05 | google site:talk.maemo.org conversation |
| 19:18.51 | DocScrutinizer05 | maybe try to add some meaningful search keys like "CSS" or dunno what |
| 19:18.58 | DocScrutinizer05 | "html" |
| 19:19.03 | DocScrutinizer05 | "browserd" |
| 19:27.14 | beford | ping ZogG |
| 19:28.50 | freemangordon | Pali: calvaria does nothing :( |
| 19:28.55 | freemangordon | on /dev/mtd1 |
| 19:29.03 | Pali | yes, it mapping file |
| 19:29.10 | freemangordon | what? |
| 19:29.15 | Pali | and you cannot map mtd device |
| 19:29.23 | freemangordon | nice |
| 19:29.24 | Pali | you need to dump mtd to file |
| 19:29.35 | Pali | and then run calvaria on it |
| 19:29.45 | Pali | calvaria is only cal parser |
| 19:29.47 | freemangordon | well, and error message would be helpful , who wrote that? |
| 19:29.55 | Pali | I do not know |
| 19:29.55 | freemangordon | s/and/an/ |
| 19:29.59 | freemangordon | ok |
| 19:30.13 | Pali | but mapping mtd device is possible in upstream kernel |
| 19:30.15 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 19:30.21 | Pali | but not on 2.6.28 |
| 19:30.25 | DocScrutinizer05 | avtobiff: http://talk.maemo.org/showthread.php?t=70623 |
| 19:30.32 | freemangordon | Pali: ok |
| 19:36.03 | freemangordon | Pali: Unsupported ioctl: cmd=0x80204d01 |
| 19:36.03 | freemangordon | CAL ERROR: MEMGETINFO: Function not implemented |
| 19:36.13 | freemangordon | :( |
| 19:38.02 | Pali | freemangordon, I'm doing some modular arithmetic - cannot think about something else now... |
| 19:38.13 | freemangordon | hehe, ok |
| 19:38.14 | Pali | my head is going to explode... |
| 19:41.19 | avtobiff | DocScrutinizer05, found that also but the application menu does not seem to be in those html/css/js files |
| 19:45.04 | DocScrutinizer05 | ooh, the menu :-S you're quite probably outa luck with that |
| 19:45.22 | avtobiff | :( |
| 19:46.10 | DocScrutinizer05 | at least I don't know (means I have no idea, yay or nay) if conversations app allows to add menu items |
| 19:46.33 | DocScrutinizer05 | I'm rather sure convo app is closed source though |
| 19:46.55 | DocScrutinizer05 | mediaplayer for instance actually allows adding menu items |
| 19:47.07 | DocScrutinizer05 | contacts as well iirc |
| 19:48.38 | DocScrutinizer05 | barisione did something for contact-specific ringtones and I think he added a menu item to contacts app for that. For mediaplayer there's this plugin that allows browsing of fs-tree for playback of real files. Sorry I never can recall the name |
| 19:49.44 | gena2x | do anyone tried modrana? i do not understand how to setup gps there. |
| 19:49.53 | DocScrutinizer05 | hth to find your way where to search |
| 19:50.11 | *** join/#maemo alehorst (~alehorst@177.96.10.254) |
| 19:54.01 | DocScrutinizer05 | Pali: take care! :-) |
| 19:54.55 | DocScrutinizer05 | Pali: I don't even dare to wonder what modular arithmetics might be at all |
| 19:57.07 | *** join/#maemo ALoGeNo (~alogeno@243.Red-217-125-20.staticIP.rima-tde.net) |
| 19:57.08 | *** join/#maemo ALoGeNo (~alogeno@unaffiliated/alogeno) |
| 19:57.25 | *** join/#maemo joga (e5tExnp5@rikki.fi) |
| 19:58.32 | DocScrutinizer05 | ooh modulo |
| 19:58.52 | DocScrutinizer05 | circular closed value space |
| 19:59.11 | Pali | DocScrutinizer05, see: https://en.wikipedia.org/wiki/Modular_arithmetic |
| 19:59.27 | DocScrutinizer05 | exactly what I just did :-) |
| 20:01.02 | *** join/#maemo messerting (~messertin@cm-84.211.113.209.getinternet.no) |
| 20:01.09 | kerio | number theory is fun! |
| 20:01.28 | SpeedEvil | only in so many ways. |
| 20:01.40 | Pali | gena2x, maybe ask M4rtinK |
| 20:03.45 | gena2x | Pali, thanks |
| 20:07.20 | *** join/#maemo Ian-- (Ian--@46.11.30.95) |
| 20:15.09 | *** join/#maemo Vanadis (~Vanadis@84-73-15-21.dclient.hispeed.ch) |
| 20:16.45 | M4rtinK | gena2x: hi :) |
| 20:17.08 | M4rtinK | gena2x: what can I help you with ? |
| 20:19.46 | gena2x | M4rtinK, hi |
| 20:20.15 | gena2x | M4rtinK, i am trying to install modrana |
| 20:20.34 | gena2x | M4rtinK, and it seems can't turn on my gps |
| 20:21.01 | gena2x | M4rtinK, actually i am already figured out that it's python package installation problem |
| 20:21.47 | gena2x | python2.5-dbus seem can't be installed, but somehow installation of modrana went fine |
| 20:22.12 | M4rtinK | are you installing the package from Extras-devel ? |
| 20:22.18 | gena2x | yes |
| 20:22.30 | M4rtinK | well, that should just work :) |
| 20:22.40 | gena2x | i see in log: |
| 20:22.49 | gena2x | modRana: module: device_n900/device failed to load |
| 20:22.59 | gena2x | ImportError: No module named dbus.glib |
| 20:23.24 | gena2x | apt-get install python2.5-dbus |
| 20:23.34 | gena2x | The following packages have unmet dependencies: |
| 20:23.35 | gena2x | <PROTECTED> |
| 20:23.55 | M4rtinK | hmm |
| 20:23.58 | gena2x | apt-get install python2.5-xml |
| 20:24.05 | gena2x | Package python2.5-xml is a virtual package provided by: |
| 20:24.05 | gena2x | <PROTECTED> |
| 20:24.25 | gena2x | apt-get install python-xml |
| 20:24.33 | gena2x | python-xml is already the newest version |
| 20:24.38 | gena2x | %) |
| 20:24.55 | M4rtinK | try to install just python-dbus |
| 20:25.05 | M4rtinK | as it seems to be a different package |
| 20:26.27 | M4rtinK | hmm, looks like there is no dependency on python-dbus or python2.5-dbus listed for the modRana package at all :D |
| 20:26.27 | gena2x | shame on me! |
| 20:26.32 | M4rtinK | ? |
| 20:26.43 | gena2x | with python-dbus now it's fine =) |
| 20:26.44 | M4rtinK | well, shame on me if I forgot to add it :) |
| 20:27.03 | gena2x | are you one of authors of modrana? |
| 20:27.08 | M4rtinK | ok, I'll update the package dependencies :) |
| 20:27.14 | M4rtinK | yeah |
| 20:27.24 | gena2x | cool. nice app. going to try it. |
| 20:27.26 | M4rtinK | the sole active one :) |
| 20:27.32 | gena2x | oh |
| 20:27.37 | M4rtinK | thanks ! :) |
| 20:28.00 | M4rtinK | not that there are any non-active authors |
| 20:28.16 | M4rtinK | just that people send some patches or help with testing |
| 20:28.25 | gena2x | now it works |
| 20:28.33 | M4rtinK | but usually not participate on development regularly :) |
| 20:28.39 | M4rtinK | good to hear that :) |
| 20:29.18 | gena2x | thank you. going to try tomorrow in the car =) |
| 20:31.17 | M4rtinK | will you have connectivity for the whole trip ? |
| 20:31.35 | gena2x | yes |
| 20:31.58 | gena2x | wonder do you have any plans to collect traffic information? |
| 20:31.58 | M4rtinK | ok, so then everything should just work |
| 20:32.15 | M4rtinK | from users ? |
| 20:32.42 | M4rtinK | rather the other way around - use some API to display it in modRana |
| 20:32.58 | gena2x | doesn't matter from there. i am interested to see such information =) |
| 20:33.23 | M4rtinK | hh |
| 20:33.43 | M4rtinK | yes, it could be quite useful |
| 20:33.56 | DocScrutinizer51 | connecting to RDS woul.d be cool |
| 20:34.36 | DocScrutinizer51 | TMS actually |
| 20:34.41 | M4rtinK | IIRC how RDS works this might be actually doable |
| 20:35.12 | M4rtinK | but is the RDS/TMS code <-> location database available somewhere ? |
| 20:35.35 | DocScrutinizer51 | dunno |
| 20:35.43 | M4rtinK | as i think it just sends some codes for the event & area |
| 20:35.49 | DocScrutinizer51 | should be somehow defined somewhere |
| 20:36.43 | M4rtinK | well, I'm quite overloaded already :) but won't mind to merge it in if somebody does it :) |
| 20:37.08 | M4rtinK | modRana internals consultation included :) |
| 20:40.14 | *** join/#maemo teotwaki (~crashandd@2a01:e35:8a44:eb00:213:2ff:fe39:c4d4) |
| 20:40.14 | *** join/#maemo teotwaki (~crashandd@Maemo/community/contributor/crashanddie) |
| 20:42.27 | M4rtinK | BTW, there are more interesting data sources that could be added: POI extracts, weather radar data, weather prediction, restaurant/hotel review search, Wikimapia, Nominatim, etc. :) |
| 20:45.03 | gena2x | M4rtinK, hm, going to add |
| 20:45.24 | *** join/#maemo Snafu777 (~Snafu@unaffiliated/snafu777) |
| 20:46.27 | gena2x | M4rtinK, where can i found more information on this? |
| 20:46.31 | gena2x | *find |
| 20:48.22 | M4rtinK | gena2x: do you mean modRana or the different data sources ? |
| 20:49.24 | gena2x | M4rtinK, sorry, misunderstood, you've said 'could' =) |
| 21:00.26 | gena2x | M4rtinK, how to remove POI from map? |
| 21:01.03 | gena2x | M4rtinK, i am pressing 'clear visible' but it says 'nothing to clear' |
| 21:03.59 | M4rtinK | gena2x: there are two types of markers - those shown for POI and those for search results |
| 21:05.17 | *** join/#maemo rcg (~rcg@e183145024.adsl.alicedsl.de) |
| 21:05.53 | M4rtinK | gena2x: to clear the search result, click on one of them, select "tools" and then "clear results" |
| 21:07.38 | M4rtinK | gena2x: I should probably also add a "clear all visible" button to the main search menu |
| 21:07.39 | gena2x | M4rtinK, yeah |
| 21:07.57 | gena2x | M4rtinK, i mean this works |
| 21:33.11 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 21:44.54 | *** join/#maemo StyXman (~mdione@247.30.102.84.rev.sfr.net) |
| 21:44.54 | *** join/#maemo StyXman (~mdione@grulic/root/StyXman) |
| 22:21.18 | *** join/#maemo lxp (~lxp@212-183-122-50.adsl.highway.telekom.at) |
| 22:32.35 | *** join/#maemo joga (nLBZHOVL@rikki.fi) |
| 22:33.44 | *** join/#maemo sirdancealot7 (~sirdancea@98.82.broadband5.iol.cz) |
| 22:52.05 | *** join/#maemo Gizmokid2005 (~Gizmokid2@dedi.gizmokid2005.com) |
| 23:11.30 | *** join/#maemo pcfe` (~pcfe@brln-4dba88f7.pool.mediaWays.net) |
| 23:11.31 | *** join/#maemo pcfe` (~pcfe@redhat/pcfe) |
| 23:13.13 | *** join/#maemo ZogG_laptop (~ZogG_lapt@bzq-79-176-226-49.red.bezeqint.net) |
| 23:13.13 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 23:15.58 | Snafu777 | w00t, ngrep ported to the n900 |
| 23:16.00 | Snafu777 | !! |
| 23:16.50 | *** join/#maemo ZogG (~zoggrules@funtoo/user/ZogG) |
| 23:29.23 | *** join/#maemo krayonWork (~krayon@pdpc/supporter/28for7/krayon) |
