| 00:22.31 | *** join/#maemo ssvb (~ssvb@212.16.98.80) |
| 00:30.24 | *** join/#maemo cybertheque (~chatzilla@77.160.251.216.lan.static.cptelecom.net) |
| 01:03.23 | *** join/#maemo mschlens_ (~mschlens@p5DE7B9EF.dip0.t-ipconnect.de) |
| 01:18.34 | *** join/#maemo hardfalcon1 (~hardfalco@f048134042.adsl.alicedsl.de) |
| 01:24.20 | *** join/#maemo ecc3g (blc@r.jajcs.net) |
| 01:30.19 | *** join/#maemo Humpelstilzchen (erik@e177102151.adsl.alicedsl.de) |
| 01:44.36 | DocScrutinizer05 | hmmpf |
| 01:44.49 | DocScrutinizer05 | thedead1440: ^^ |
| 01:45.44 | DocScrutinizer05 | idly wonders wwhen ernest75 last time updated catalogs |
| 01:46.06 | *** join/#maemo triggerhappy (~quassel@112.209.53.176) |
| 01:46.11 | DocScrutinizer05 | must have been like a year ago |
| 01:46.48 | DocScrutinizer05 | thedead1440: some symlinks missing? |
| 02:20.09 | *** join/#maemo Ninja (~ninja@50.9.215.104) |
| 02:21.49 | *** join/#maemo robbiethe1st (~robbiethe@50-52-17-221.cral.id.frontiernet.net) |
| 02:43.32 | *** join/#maemo triggerhappy (~quassel@112.209.53.176) |
| 03:02.14 | *** join/#maemo lxp1 (~lxp@194-166-216-236.adsl.highway.telekom.at) |
| 03:34.06 | *** join/#maemo maybeArgh (~cl@p5B1647EE.dip0.t-ipconnect.de) |
| 03:53.41 | Macer | hm |
| 03:54.02 | Macer | dont know why but pan doesnt seem to agree with connecting to non-standard ports |
| 03:54.05 | Macer | wth |
| 03:54.13 | Macer | figured it was just straight masqing |
| 03:54.20 | Macer | masqerading |
| 03:54.33 | Macer | :-/ |
| 03:56.28 | Macer | lame stuff |
| 04:03.15 | *** join/#maemo Custodian (~Custodian@46.39.225.253) |
| 04:45.04 | *** join/#maemo triggerhappy (~quassel@112.209.53.176) |
| 04:56.55 | *** join/#maemo hahlo (hahlo@fedora/hahlo) |
| 04:57.57 | *** join/#maemo FReaper-PC (~honoo-pc@jlp-208-83.tm.net.my) |
| 04:59.28 | *** join/#maemo kraft (kraft@gateway/shell/blinkenshell.org/x-hmyltglmxfkxdxnz) |
| 05:09.57 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 05:16.16 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 05:17.26 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 05:28.54 | *** join/#maemo Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr) |
| 05:35.42 | *** join/#maemo LauRoman (~LauRoman@5-14-91-21.residential.rdsnet.ro) |
| 05:49.03 | *** join/#maemo FR-PC (~honoo-pc@jlp-208-83.tm.net.my) |
| 05:49.19 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 05:52.02 | *** join/#maemo pdanek (~amidofil@79.110.204.14) |
| 06:05.47 | *** join/#maemo githogori (~githogori@c-50-156-57-127.hsd1.ca.comcast.net) |
| 06:09.24 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 06:14.33 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 06:19.39 | *** join/#maemo ZogG_lap1op (~ZogG_lapt@212.199.182.172) |
| 06:23.05 | *** join/#maemo kolp (~quassel@103.Red-88-18-104.staticIP.rima-tde.net) |
| 06:30.01 | *** join/#maemo XATRIX (~xatrix@77.88.209.171) |
| 06:36.13 | *** join/#maemo odin_ (~Odin@2a01:348:261:32:211:11ff:fe6b:2483) |
| 06:50.32 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 06:51.27 | *** join/#maemo tanty (~agomez@cs78210056.pp.htv.fi) |
| 06:55.33 | *** join/#maemo HylianSavior (hylian@HYLIANDESKTOP.RES.CMU.EDU) |
| 07:01.20 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 07:07.15 | *** join/#maemo zammy (~sammy@ppp-179-43.98-62.inwind.it) |
| 07:11.22 | *** join/#maemo OkropNick (kuba@host-n2-75-80.telpol.net.pl) |
| 07:12.27 | *** join/#maemo ecc3g (blc@r.jajcs.net) |
| 07:13.52 | *** join/#maemo zammy (~sammy@ppp-179-43.98-62.inwind.it) |
| 07:16.21 | *** join/#maemo zammy (~sammy@ppp-179-43.98-62.inwind.it) |
| 07:17.22 | *** join/#maemo mhlavink (quassel@nat/redhat/x-ukbpkrtfaquoydvx) |
| 07:18.09 | *** join/#maemo zammy (~sammy@ppp-179-43.98-62.inwind.it) |
| 07:29.29 | *** join/#maemo DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 07:35.27 | *** join/#maemo DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 07:43.52 | *** join/#maemo otep_ (~quassel@AP-203.167.4.11.sysads.com) |
| 07:45.47 | *** part/#maemo pdanek (~amidofil@79.110.204.14) |
| 07:49.04 | *** join/#maemo NIN101 (~NIN@p5DD28963.dip0.t-ipconnect.de) |
| 07:51.51 | *** join/#maemo troulouliou_dev (~troulouli@unaffiliated/troulouliou-dev/x-4757952) |
| 07:52.05 | troulouliou_dev | hi is the dev mobo for neo900 the gta04 ? |
| 07:53.35 | psycho_oreos | I personally somewhat doubt it, it maybe based on it however. Why don't you ask these questions in the tmo thread? |
| 07:54.52 | troulouliou_dev | psycho_oreos, afraid to be involved :) |
| 07:55.21 | troulouliou_dev | i just wonder if they plan to provide some mobo then start porting |
| 07:55.23 | psycho_oreos | troulouliou_dev, afraid? o.O it's not like they will be dragging people into development. |
| 07:55.36 | troulouliou_dev | psycho_oreos, ill be myself :) |
| 07:56.27 | psycho_oreos | The hardware work is completely independent of software. If Neo900 is ready to be released/shipped and the fptf isn't ready still, the hardware will still get shipped nonetheless to their buyers. |
| 07:58.50 | psycho_oreos | *shrug*, there are plenty of "fans" but only very few of them actually put forth into being involved. I'm certain if one has queries, it's not like the team behind it will start forcing you to join them. |
| 08:01.06 | psycho_oreos | Anyway, it's up to you. If you were patient enough, you might even be able to get proper and direct responses rather than "maybe", "possible", "could be" from someone who is sort of spectating on the side. :) |
| 08:02.13 | troulouliou_dev | psycho_oreos, i was just asking cause the the GTA04 is expensive and it is required to wait for 200 orders for them to start shipping |
| 08:02.24 | troulouliou_dev | and if i m not wrong it happens only once :) |
| 08:03.13 | psycho_oreos | I can imagine it's only because of a niche market that it's targeting at. Though Neo900 maybe different imo as it is sort of an extension to N900 and is also living off N900's fame. |
| 08:04.39 | psycho_oreos | I also recall openpandora was quite similar too, pre-orders only until they pick up a certain amount before they start actual manufacture. |
| 08:09.17 | *** join/#maemo zeq (~s_j_newbu@2a01:348:1e3:8080:caf7:33ff:fe77:cf27) |
| 08:15.53 | *** join/#maemo hardfalcon (~hardfalco@f048134042.adsl.alicedsl.de) |
| 08:16.42 | *** join/#maemo shentey (~shentey@pD9EA69A7.dip0.t-ipconnect.de) |
| 08:18.17 | *** join/#maemo zammy (~sammy@ppp-179-43.98-62.inwind.it) |
| 08:20.41 | troulouliou_dev | will see i guess this project is for late 2014/2015 |
| 08:27.52 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 08:28.37 | *** join/#maemo _rd (~rd@p57B48261.dip0.t-ipconnect.de) |
| 08:28.54 | *** join/#maemo arcean (~arcean@aaeq113.neoplus.adsl.tpnet.pl) |
| 08:31.14 | *** join/#maemo tzafrir_laptop (~tzafrir@local.xorcom.com) |
| 08:32.56 | *** join/#maemo ZogG_laptop (~ZogG_lapt@212.199.182.172) |
| 08:32.56 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 08:39.15 | *** join/#maemo sq-one (~sq-one@p57977E79.dip0.t-ipconnect.de) |
| 08:44.03 | *** join/#maemo robotanarchy (~robotanar@g226211254.adsl.alicedsl.de) |
| 08:44.51 | *** join/#maemo triggerhappy (~quassel@112.209.53.176) |
| 08:53.07 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 08:54.20 | *** join/#maemo zammy (~sammy@ppp-179-43.98-62.inwind.it) |
| 09:02.48 | *** join/#maemo zammy (~sammy@ppp-179-43.98-62.inwind.it) |
| 09:04.48 | *** join/#maemo goldkatze (~nobody@unaffiliated/goldkatze) |
| 09:05.23 | *** join/#maemo zammy (~sammy@ppp-179-43.98-62.inwind.it) |
| 09:42.50 | *** join/#maemo jonwil (~jonwil@27-33-137-199.static.tpgi.com.au) |
| 09:43.21 | *** join/#maemo marainein (~net@2001:388:608c:6cb5:41a8:1e17:ebb4:3cb0) |
| 09:49.34 | *** join/#maemo pcfe (~pcfe@host86-181-5-17.range86-181.btcentralplus.com) |
| 10:09.01 | jonwil | is so bored :( |
| 10:11.16 | x29a | build a neo900 |
| 10:11.42 | jonwil | doesn't have the parts or tools to do that :P |
| 10:16.24 | troulouliou_dev | any tips where i can finda screen replaceent for my N900 ; mine is too scratched with some brightness issue in some area |
| 10:30.18 | x29a | troulouliou_dev: have you checked ebay? |
| 10:30.38 | *** join/#maemo ZogG_laptop (~ZogG_lapt@212.199.182.172) |
| 10:30.38 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 10:31.09 | troulouliou_dev | x29a, nothing |
| 10:31.17 | x29a | where are you located? |
| 10:31.22 | x29a | even amazon.com has them |
| 10:33.04 | *** join/#maemo maybeHere (~cl@p5B1647EE.dip0.t-ipconnect.de) |
| 10:34.13 | *** join/#maemo maybeWTF (~cl@p5B1647EE.dip0.t-ipconnect.de) |
| 10:34.14 | *** join/#maemo ebzzry_ (~ebzzry@112.203.179.38) |
| 10:35.42 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 10:48.35 | *** join/#maemo utanapischti (~username@p3EE3E17E.dip0.t-ipconnect.de) |
| 10:48.43 | *** join/#maemo RP_ (~richard@93-97-173-237.zone5.bethere.co.uk) |
| 10:53.48 | *** join/#maemo xray256 (~xray256@149.241.43.82) |
| 11:00.10 | *** join/#maemo florian (~fuchs@sign-4d091ec1.pool.mediaWays.net) |
| 11:00.10 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 11:04.10 | *** join/#maemo lizardo (lizardo@nat/indt/x-lksizyhhvocwypev) |
| 11:13.51 | *** join/#maemo maybeHere (~cl@p5B1647EE.dip0.t-ipconnect.de) |
| 11:14.33 | troulouliou_dev | x29a, africa |
| 11:19.55 | *** join/#maemo DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 11:33.31 | *** join/#maemo Hurrian (~Hurrian@unaffiliated/rikanee) |
| 11:42.01 | *** join/#maemo eMHa (~mh@HSI-KBW-217-008-061-244.hsi.kabelbw.de) |
| 11:45.08 | *** join/#maemo Pali (~Pali@Maemo/community/contributor/Pali) |
| 11:47.17 | *** join/#maemo triggerhappy (~quassel@112.209.53.176) |
| 11:50.30 | *** join/#maemo _nicolai_ (~nicolai@pop8-126.catv.wtnet.de) |
| 11:52.07 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 12:12.31 | *** join/#maemo uen (~uen@p5DCB3AAB.dip0.t-ipconnect.de) |
| 12:49.27 | *** join/#maemo trx (ns-team@212.200.198.102) |
| 12:49.27 | *** join/#maemo trx (ns-team@devbin/founder/trx) |
| 12:59.20 | *** join/#maemo SAiF (79f1b682@gateway/web/freenode/ip.121.241.182.130) |
| 12:59.35 | *** join/#maemo DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 13:12.53 | *** join/#maemo SmilybOrg (Smily@BSN-61-6-251.dial-up.dsl.siol.net) |
| 13:15.40 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 13:22.24 | Sc0rpius | autobuilder broken again :( |
| 13:27.54 | *** join/#maemo ebzzry__ (~ebzzry@112.203.179.38) |
| 13:32.46 | *** join/#maemo Hurrian (~Hurrian@unaffiliated/rikanee) |
| 13:51.53 | *** join/#maemo xray256 (~xray256@149.241.43.82) |
| 13:57.50 | *** join/#maemo andre__ (~andre__@wikimedia/aklapper) |
| 13:57.51 | *** join/#maemo cityLights (~nivw@bzq-218-29-26.cablep.bezeqint.net) |
| 14:17.02 | *** join/#maemo deepaero (~deepaero@212.188.183.73) |
| 14:18.53 | deepaero | hi all! wanted to ask if there are any ways to skip next track using volume rocker while screen is locked? |
| 14:23.56 | DocScrutinizer05 | I'm pretty sure there's an app for that |
| 14:26.49 | deepaero | is it? found only one for Meego ,N9 |
| 14:26.49 | psycho_oreos | shortcutd |
| 14:28.06 | deepaero | great stuff, will try this one |
| 14:28.39 | DocScrutinizer05 | it is, since ~4 years agp I suggested to augment it so that with short press you skip and long press still adjusts volume |
| 14:29.03 | DocScrutinizer05 | s/p/o/ |
| 14:32.00 | deepaero | sounds promising, my lumia 925 has so imperfect headphone socket, just sent that to service. If it's died within 2 months of usage and start missing signal - I'd pull out of shelf my good old n900 in order to have a painless listening experience |
| 14:33.19 | *** join/#maemo zammy (~sammy@ppp-179-43.98-62.inwind.it) |
| 14:33.27 | DocScrutinizer05 | I hope you stored it with battery removed |
| 14:33.59 | deepaero | nope 0_o |
| 14:34.09 | deepaero | any possible problems if not? |
| 14:34.11 | DocScrutinizer05 | fool |
| 14:34.37 | deepaero | I must admit it |
| 14:34.49 | DocScrutinizer05 | sure, battery dies, incinerates, and burns down your house |
| 14:35.21 | deepaero | just got property insurance, nice idea |
| 14:36.35 | DocScrutinizer05 | actually just yesterday in ZV they reported about pedelec batteries - after storing them away for 6 years - suddenly incinerated |
| 14:36.50 | DocScrutinizer05 | s/z/T/ |
| 14:36.56 | DocScrutinizer05 | s/Z/T/ |
| 14:38.40 | DocScrutinizer05 | in every battery warning paper it's written "do not discharge to <2.0V (value may vary slightly) or venting and fire may happen) |
| 14:38.47 | DocScrutinizer05 | " |
| 14:39.34 | DocScrutinizer05 | now batteries discharge by self-discharge, but for sure they discharge way faster when inserted to device |
| 14:40.39 | DocScrutinizer05 | and definitely cells die when deep-discharged, even when usually no fire or explosion |
| 14:41.24 | DocScrutinizer05 | thus, NEVER store away a device with battery inserted! |
| 14:41.25 | *** join/#maemo zammy (~sammy@ppp-179-43.98-62.inwind.it) |
| 14:41.28 | DocScrutinizer05 | ~batteryfaq |
| 14:41.28 | infobot | [batteryfaq] http://wiki.openmoko.org/wiki/Battery_Questions_and_Answers |
| 14:41.44 | deepaero | good to know. I'm using that time to time looking for the new WEP spots around if any - fortunately no drain yet |
| 14:42.24 | DocScrutinizer05 | N900 seems "safe" to store with battery inserted for 4 weeks |
| 14:42.49 | DocScrutinizer05 | but I wouldn't rely on it |
| 14:43.25 | deepaero | in regards to battery drain - had some Chinese phone watches and these were diying within 2 weekes without charging. |
| 14:43.35 | DocScrutinizer05 | several subsystems are not powered down hard when CPU goes to power-down state: LEDs, Modem, a few others |
| 14:44.56 | DocScrutinizer05 | so proper shutdown is mandatory, otherwise battery drain may be way higher than usual, while device _looks_ like off |
| 14:45.16 | deepaero | useful trick |
| 14:45.30 | DocScrutinizer05 | removing battery is the trick |
| 14:46.07 | deepaero | the battery denied to charging within device once. Just cutted old Nokia charger to and keeping right polar connected wires to battery contact plates. |
| 14:46.13 | deepaero | for 2 mins |
| 14:46.15 | DocScrutinizer05 | even removing for 30s and then inserting again should result in a known-good powerdown state |
| 14:46.52 | DocScrutinizer05 | deepaero: battery never refuses to charge in N900 |
| 14:47.08 | deepaero | it was about Chinese smart watches |
| 14:47.11 | DocScrutinizer05 | ~flatbatrecover |
| 14:47.11 | infobot | Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber going off - in this case start over again with ~flatbatrecover |
| 14:48.45 | DocScrutinizer05 | infobot: no, flatbatrecover is Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber going off - in this case start over again with ~flatbatrecover. CAVEAT! Only works when rootfs is OK (no bootloop)!. |
| 14:48.45 | infobot | DocScrutinizer05: okay |
| 14:48.50 | DocScrutinizer05 | ~flatbatrecover |
| 14:48.50 | infobot | rumour has it, flatbatrecover is Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber going off - in this case start over again with ~flatbatrecover. CAVEAT! Only works when rootfs is OK (no bootloop)!. |
| 14:49.31 | DocScrutinizer05 | ~listkeys bootloop |
| 14:52.17 | DocScrutinizer05 | ~#maemo bootloop is when your device has broken rootfilesystem, so during reboot it fails on some service startup and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing. |
| 14:52.17 | infobot | okay, DocScrutinizer05 |
| 14:52.50 | DocScrutinizer05 | infobot: no, flatbatrecover is Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber going off - in this case start over again with ~flatbatrecover. CAVEAT! Only works when rootfs is OK (no ~bootloop)!. |
| 14:52.50 | infobot | DocScrutinizer05: okay |
| 14:53.19 | DocScrutinizer05 | ~listkeys rootfs |
| 14:53.29 | DocScrutinizer05 | ~rootfs |
| 14:53.29 | infobot | [rootfs] mount ro, but all the nessary files that need to be writen to are created in a ramdisk that is rw |
| 14:53.45 | DocScrutinizer05 | ~forget rootfs |
| 14:53.46 | infobot | i forgot rootfs, DocScrutinizer05 |
| 14:54.18 | *** join/#maemo shentey (~shentey@pD9EA6B9F.dip0.t-ipconnect.de) |
| 14:54.50 | deepaero | <PROTECTED> |
| 14:55.22 | *** join/#maemo zammy (~sammy@ppp-179-43.98-62.inwind.it) |
| 14:55.22 | *** join/#maemo HylianSavior (~hylian@HYLIANDESKTOP.RES.CMU.EDU) |
| 14:57.20 | *** join/#maemo zammy (~sammy@ppp-179-43.98-62.inwind.it) |
| 14:58.24 | *** join/#maemo Vurp (~Jag@m90-129-81-202.cust.tele2.se) |
| 14:58.48 | DocScrutinizer05 | ~#maemo rootfs is <reply>rootfs: the content of the storage volume mounted under /, on NAND mtd5 partition. Also called "the system", since it's all the files forming the linux core system (except the kernel itself). Reflash rootfs from COMBINED (see ~flashing). Also see ~bootloop |
| 14:58.48 | infobot | DocScrutinizer05: okay |
| 15:02.19 | DocScrutinizer05 | infobot: no, flatbatrecover is Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber going off - in this case start over again with ~flatbatrecover. CAVEAT! Only works when ~rootfs is OK (no ~bootloop)!. |
| 15:02.19 | infobot | DocScrutinizer05: okay |
| 15:03.08 | DocScrutinizer05 | infobot: no, flatbatrecover is <reply>Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber going off - in this case start over again with ~flatbatrecover. CAVEAT! Only works when ~rootfs is OK (no ~bootloop)!. |
| 15:03.08 | infobot | DocScrutinizer05: okay |
| 15:03.12 | *** join/#maemo Pilke (~Pilke@87-95-11-24.bb.dnainternet.fi) |
| 15:03.20 | DocScrutinizer05 | ~flatbatrecover |
| 15:03.20 | infobot | Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber going off - in this case start over again with ~flatbatrecover. CAVEAT! Only works when ~rootfs is OK (no ~bootloop)!. |
| 15:03.26 | *** join/#maemo Zerf (~Deepaero@dab-hlw1-h-34-4.dab.02.net) |
| 15:03.30 | DocScrutinizer05 | ~rootfs |
| 15:03.30 | infobot | rootfs: the content of the storage volume mounted under /, on NAND mtd5 partition. Also called "the system", since it's all the files forming the linux core system (except the kernel itself). Reflash rootfs from COMBINED (see ~flashing). Also see ~bootloop |
| 15:03.59 | DocScrutinizer05 | ~bootloop |
| 15:03.59 | infobot | from memory, bootloop is when your device has broken rootfilesystem, so during reboot it fails on some service startup and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing. |
| 15:06.02 | DocScrutinizer05 | infobot: no, #maemo bootloop is when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing. |
| 15:06.02 | infobot | okay, DocScrutinizer05 |
| 15:11.05 | brolin_empey | DocScrutinizer05: Does either the GTA04 or the Neo900 have external RGB video output capable of driving an external display? I want my handheld/pocket computer to have VGA output capable of driving an external display. |
| 15:12.55 | DocScrutinizer05 | brolin_empey: sorry, no RGB signal available on OMAP3 standard design |
| 15:13.51 | brolin_empey | wants the ability to drive an external CRT display, not only a flat-panel/fixed-pixel display. |
| 15:13.56 | DocScrutinizer05 | the composite video signal is mixed internally in OMAP3 |
| 15:16.15 | DocScrutinizer05 | the other video signals are digital |
| 15:18.22 | kerio | is the only video output going to be composite? |
| 15:19.03 | DocScrutinizer05 | that's what I just said |
| 15:19.20 | kerio | you also said that the other video signals are digital |
| 15:19.24 | kerio | i like digital |
| 15:19.29 | kerio | numbers are cool |
| 15:19.32 | brolin_empey | Yes, I know I can drive both a CRT display and a flat-panel/fixed-pixel display with the external composite video output but I meant I want external analog RGB video output, such as VGA, so I can drive an external CRT display with an analog RGB video input, such as VGA. |
| 15:19.45 | kerio | can we get digital video somewhere other than the screen? |
| 15:20.55 | DocScrutinizer05 | brolin_empey: I just explained to you that such RGB signal is not available on OMAP standard design, and we won't add a RGB converter circuit and a VGA connector |
| 15:21.14 | kerio | haha, a full-size VGA connector would be hilarious though |
| 15:21.43 | kerio | bonus points if you also add sockets for the screws |
| 15:22.05 | DocScrutinizer05 | kerio: no, LCD is the only accessable digital video bus |
| 15:22.11 | kerio | shame |
| 15:22.27 | kerio | ...would there be some way to tap into that to output to, say, dvi? |
| 15:22.47 | kerio | theoretically, at least |
| 15:23.01 | kerio | or is it something specific to the type of screen used in the n900? |
| 15:23.06 | DocScrutinizer05 | see beagleboard HDMI discussion and beagleboard circuit diagram |
| 15:23.53 | DocScrutinizer05 | you need to route the signal to some converter and thus the LCD is black while you do |
| 15:24.05 | DocScrutinizer05 | you need a muxer chip to do that |
| 15:24.18 | DocScrutinizer05 | see |
| 15:24.20 | DocScrutinizer05 | http://talk.maemo.org/showthread.php?t=91142 |
| 15:24.33 | DocScrutinizer05 | search for muxer |
| 15:25.42 | DocScrutinizer05 | for your convenience: http://talk.maemo.org/showthread.php?p=1375110&highlight=muxer#post1375110 |
| 15:30.01 | DocScrutinizer05 | kerio: for sure you can disassemble the screen half, unplug the LCD and plug in a RGB or HDMI or whatever-yiu-like converter instead |
| 15:31.24 | *** join/#maemo freemangordon (~freemango@46.249.74.23) |
| 15:37.02 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 15:56.18 | *** join/#maemo amizraa (~amizraa@gateway/tor-sasl/amizraa) |
| 15:57.18 | freemangordon | Sc0rpius: ping |
| 15:58.36 | *** join/#maemo pdanek (~amidofil@79.110.204.14) |
| 16:02.27 | *** join/#maemo Ninja (~ninja@50.9.215.104) |
| 16:07.47 | Sc0rpius | freemangordon, pong |
| 16:08.41 | freemangordon | Sc0rpius: please reupload yaparri to autobuilder again, builder was down for the last ~24 hours |
| 16:08.49 | freemangordon | so your upload got lost |
| 16:11.00 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 16:11.22 | Sc0rpius | yeah I've heard it was in maintenance |
| 16:13.24 | DocScrutinizer05 | [general notice] autobuilder resumed. Please don't forget to always BUMP YOUR VERSION even when re-uploading a package that failed to build |
| 16:14.33 | Sc0rpius | done |
| 16:14.36 | Sc0rpius | let's see what happens. |
| 16:14.40 | freemangordon | thanks |
| 16:14.46 | DocScrutinizer05 | bumping version never hurts. Not doing so sometimes causes problems that block autobuilder or even worse trouble |
| 16:16.00 | freemangordon | [2013-10-03 16:15:02] Processing package yappari 1.1.41. Uploader: naikel, builder: builder1 |
| 16:16.00 | freemangordon | [2013-10-03 16:15:07] Building yappari 1.1.41 for target 'maemo-fremantle-armel-extras-devel' |
| 16:16.34 | *** join/#maemo Neutron115 (~neutron@80.202.98.36) |
| 16:17.33 | DocScrutinizer05 | http://wstaw.org/m/2013/10/03/plasma-desktopoc3743.png |
| 16:18.47 | DocScrutinizer05 | and with usual delay even ganglia show "green" on builder |
| 16:19.57 | freemangordon | yep, it seems to be just fine, it was a false alarm IMO |
| 16:20.07 | DocScrutinizer05 | :nod: |
| 16:20.22 | DocScrutinizer05 | caused by lack of proper diagnostic means |
| 16:20.24 | *** join/#maemo eMHa (~mh@HSI-KBW-37-209-40-177.hsi15.kabel-badenwuerttemberg.de) |
| 16:20.53 | freemangordon | DocScrutinizer05: caused by me refusing to touch builder yesterday :D |
| 16:21.06 | DocScrutinizer05 | isn't that the same |
| 16:21.17 | freemangordon | well... ok :) |
| 16:22.03 | DocScrutinizer05 | after all when there was a proper diagnostic website showing state of builder for every user, no flase alarm ever had come up |
| 16:22.44 | freemangordon | Sc0rpius: how big is yappari?!? it is still building on 4 cores!!! |
| 16:23.11 | DocScrutinizer05 | when I had such page (or other means to check what's going on with builder), I would have touched or not touched builder yesterday, instead of simply pausing it |
| 16:23.33 | Sc0rpius | well it doesn't take a lot of time to build, but it has a lot of dependencies, and that would make the builder take a while |
| 16:23.48 | freemangordon | DocScrutinizer05: you paused it because the maintainer told you to do so ;) |
| 16:24.09 | freemangordon | anyway, I'm out (semi) |
| 16:25.02 | DocScrutinizer05 | I paused it because luser been asking me to do so and I couldn't find my BOFH hat ;-P |
| 16:30.35 | Sc0rpius | yappari 1.1.41 OK |
| 16:30.56 | Sc0rpius | it "just" took 14 minutes :P |
| 16:31.05 | Sc0rpius | it builds in second in my desktop. |
| 16:31.08 | Sc0rpius | seconds |
| 16:33.49 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 16:34.38 | *** join/#maemo pdanek (~amidofil@79.110.204.14) |
| 16:37.34 | kerio | Sc0rpius: don't brag :v |
| 16:38.28 | FIQ | hi, just curious, but I was going to, partially as a test, partially because it feels more clean that way, quickly translate the orientation lock application in SSU. Given how it's just 3 strings, it seems fairly simple to do even though I haven't used .po(t) files before. Is the strings in that .po vs the template .pot supposed to be have a mismatch...? |
| 16:39.16 | FIQ | what I did was copying the .pot to sv_SE.po, but when comparing other .po files already, they seem to use a completely different set of strings |
| 16:43.28 | *** join/#maemo MohammadAG_ (~MohammadA@Maemo/community/contributor/MohammadAG) |
| 16:45.12 | FIQ | MohammadAG: yo, is .pot source strings supposed to be completely different from source strings in the resulting .po files in the orientation-lock cssu application? |
| 16:46.33 | *** join/#maemo konelix (~konelix@190.148.216.121) |
| 16:48.19 | *** join/#maemo M4rtinK (~M4rtinK@ip-89-177-124-88.net.upcbroadband.cz) |
| 16:50.31 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 16:54.10 | *** join/#maemo sixwheeledbeast (~paul@cl-1547.lon-02.gb.sixxs.net) |
| 16:54.17 | *** join/#maemo Sder (~Deepaero@dab-bhx1-h-8-7.dab.02.net) |
| 17:01.49 | *** join/#maemo OkropNick (kuba@host-n2-75-80.telpol.net.pl) |
| 17:03.11 | *** join/#maemo arcean (~arcean@aaeq113.neoplus.adsl.tpnet.pl) |
| 17:04.41 | thedead1440 | Hi DocScrutinizer05 |
| 17:04.49 | DocScrutinizer05 | hi |
| 17:04.59 | thedead1440 | re the Source symlink; I can't find any such thing... No idea if it existed pre-migration |
| 17:05.13 | *** join/#maemo Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr) |
| 17:06.00 | DocScrutinizer05 | that's the point. i guess our 2backup" lacked those symlinks |
| 17:06.22 | thedead1440 | unless the source is: http://www.scratchbox.org/download/files/sbox-releases/hathor/src/ |
| 17:06.38 | DocScrutinizer05 | thus only way we get to know about them missing is by users complaining |
| 17:06.39 | *** join/#maemo Aser (~Deepaero@dab-bas2-h-85-3.dab.02.net) |
| 17:06.41 | *** join/#maemo valerius (~user@85.26.180.142) |
| 17:07.22 | thedead1440 | true |
| 17:09.51 | thedead1440 | there is no ernest75 around so i can't ascertain with him if the above url is what he is looking for :( |
| 17:10.43 | DocScrutinizer05 | yeah, a pity |
| 17:11.27 | thedead1440 | apologies for the reduced online activity; i have a ton going on in RL hence can't find the time to be available as much |
| 17:12.18 | mashina | rm -rf /rl |
| 17:12.37 | thedead1440 | haha |
| 17:12.55 | DocScrutinizer05 | np |
| 17:13.49 | DocScrutinizer05 | error: /rl: not found |
| 17:14.12 | thedead1440 | haha doc you never had one in the first place so no use trying it out :D |
| 17:16.29 | DocScrutinizer05 | yeah, my problem rather are bad blocks on medium |
| 17:16.41 | thedead1440 | hehe |
| 17:18.13 | divVerent | speaking of bad blocks... |
| 17:18.31 | divVerent | is there a way to analyze the eMMC of the N900 without actually using up a write cycle or two like badblocks does? |
| 17:18.38 | divVerent | like, is there a tool to query e.g. number of remaining spare blocks |
| 17:19.13 | divVerent | because, I suspect bad blocks on mine... had on-boot fsck delete files multiple times, after clean shutdown |
| 17:19.25 | divVerent | and also it complained about differing FATs |
| 17:20.03 | NIN101 | isn't this info somewhere in proc or am I confused? |
| 17:20.35 | divVerent | that is what I want to know |
| 17:20.45 | divVerent | i.e. where such a proc/sysfs node might be |
| 17:21.03 | divVerent | I'd be surprised, so I didn't look there yet - as with hard drives you need smartctl too |
| 17:21.36 | NIN101 | I'm quite convinced I got this info for NAND once from proc, |
| 17:21.51 | NIN101 | maybe I find it again... |
| 17:23.01 | NIN101 | /sys/class/ubi/ubi0 |
| 17:23.23 | NIN101 | isn't emmc though |
| 17:24.28 | divVerent | ubi0? |
| 17:24.32 | divVerent | right, I was looking for mmc0 |
| 17:24.39 | divVerent | didn't see anything that hints to health status |
| 17:24.46 | divVerent | did find the cover switch info in mmc1 though :P |
| 17:25.45 | ShadowJK | In general there's no way to get such info from emmc |
| 17:25.49 | ShadowJK | (or sd) |
| 17:26.02 | divVerent | yes, I also know no such tool for USB SD card readers |
| 17:26.24 | divVerent | was just hoping there might be a N900 specific way |
| 17:26.37 | ShadowJK | And in my experience, a badblocks run doesn't necessarily catch bad blocks, as the bad block might sit in the spare/free pool for an unknown amount of cycles |
| 17:26.50 | divVerent | that too, but... |
| 17:27.02 | divVerent | one CAN hope that the wear levelling would know about the bad blocks and not use them again |
| 17:27.12 | divVerent | so you should only ever "repeatedly" hit bad blocks if all spare blocks are used up |
| 17:27.17 | divVerent | and then badblocks SHOULD be able to find them |
| 17:27.48 | divVerent | of course, badblocks' testing method for this is probably wrong |
| 17:28.00 | divVerent | to really find them, you probably need to fill ALL disk with a pattern, and then read it all and verify |
| 17:28.05 | divVerent | and not do it in small chunks like badblocks does |
| 17:28.12 | ShadowJK | I had a SD card once that was unaware of the bad blocks on it |
| 17:28.15 | divVerent | more like what memtest86 does :P |
| 17:28.17 | *** join/#maemo rcg (~rcg@2a02:908:e250:3801:76de:2bff:fe08:7809) |
| 17:28.38 | ShadowJK | they vanished, and then reappeared in a different place, during repeated badblocks -w runs |
| 17:28.51 | divVerent | yes, this is also why badblocks fails :P |
| 17:28.57 | divVerent | you can hit a single bad block many times |
| 17:28.59 | divVerent | or not at all |
| 17:29.04 | divVerent | due to wear levelling |
| 17:29.29 | divVerent | if badblocks wrote once then verified once, at least this would preclude hitting the same bad block many times |
| 17:29.53 | divVerent | haha, THIS is what dmcrypt is for ;) |
| 17:29.58 | divVerent | encrypt disk, fill with zeros, verify zeros |
| 17:30.27 | divVerent | a hardware bug is unlikely to hit AES "just right" |
| 17:30.52 | divVerent | but kidding, a simple per block CRC would do as well |
| 17:35.27 | *** part/#maemo pdanek (~amidofil@79.110.204.14) |
| 17:37.01 | ShadowJK | Modern good SD have portions of the flash running as SLC, and caches stuff there before flushing to main MLC or TLC storage area, so a simple write followed by read verify only checls if slc cache is working :P |
| 17:42.56 | jdoles | The Port field is grey/disabled in the set smtp port field. |
| 17:43.12 | jdoles | How can I set the outgoing smtp port? |
| 17:48.58 | jdoles | Your assistance came too late; it already works. |
| 17:52.59 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 18:07.58 | *** join/#maemo japa-fi (~jani@dsl-hkibrasgw4-54f843-160.dhcp.inet.fi) |
| 18:14.33 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 18:14.47 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 18:29.37 | *** join/#maemo node00 (node00@185.25.85.187) |
| 18:31.33 | DocScrutinizer05 | divVerent: on eMMC the controller in card does that. No known-to-me way to read out spare blocks available, nor any other of the internal management data |
| 18:32.03 | DocScrutinizer05 | ooh, ShadowJK beats me |
| 18:32.22 | *** join/#maemo dos1 (~dos@77-254-89-144.adsl.inetia.pl) |
| 18:32.27 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 18:33.50 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 18:35.09 | *** join/#maemo DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 18:36.49 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 18:38.14 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 18:41.13 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 18:41.41 | *** join/#maemo utanapischti (~username@p3EE3E17E.dip0.t-ipconnect.de) |
| 18:47.00 | *** join/#maemo sq-one (~sq-one@p57977E79.dip0.t-ipconnect.de) |
| 18:47.40 | *** join/#maemo Martix_ (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 18:53.31 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 19:04.12 | *** join/#maemo Kabouik (~quassel@20.176.92.79.rev.sfr.net) |
| 19:04.19 | *** join/#maemo arcean (~arcean@aaeq113.neoplus.adsl.tpnet.pl) |
| 19:15.26 | kerio | ShadowJK: so, how do we "fix" emmc? |
| 19:31.11 | *** join/#maemo freemangordon_ (~freemango@46.249.74.23) |
| 19:41.12 | *** join/#maemo shentey (~shentey@p4FF0E097.dip0.t-ipconnect.de) |
| 19:42.49 | *** join/#maemo Neutron115 (~neutron@36.80-202-98.nextgentel.com) |
| 19:50.54 | ShadowJK | I suspect it's more or less unfixable |
| 19:51.14 | ShadowJK | however, data corruptiom doesn't necessarily have to be originating from emmc either |
| 19:51.40 | ShadowJK | usually first symptoms of slightly bad ram/cpu is slowly creeping fs corruption :/ |
| 19:52.02 | *** join/#maemo maybeHere (~cl@p5B1647EE.dip0.t-ipconnect.de) |
| 19:55.59 | dos1 | overclocking? :] |
| 19:57.28 | ShadowJK | Also, running fsck on sd/emmc always caused heavy corruption for me |
| 19:57.38 | ShadowJK | so I'd recommend not fscking at all |
| 19:57.52 | ShadowJK | there's probably a reason why nokia disabled it by default |
| 20:09.02 | *** join/#maemo HylianSavior (~hylian@HYLIANDESKTOP.RES.CMU.EDU) |
| 20:11.18 | sixwheeledbeast | ~weather EGCO |
| 20:11.28 | sixwheeledbeast | ~useless |
| 20:11.28 | infobot | ACTION starts crying and hides from sixwheeledbeast in the darkest corner of the room. :( |
| 20:12.58 | *** join/#maemo Ex-Opesa (~Ex-Opesa@unaffiliated/ex-opesa) |
| 20:20.25 | *** join/#maemo lizardo (lizardo@nat/indt/x-mtvqpsvxtabqcmqz) |
| 20:24.45 | DocScrutinizer05 | tztztzzz |
| 20:24.54 | kerio | ~tz |
| 20:26.06 | DocScrutinizer05 | the main problem seems the URLs that point to rather obsolete or stale sites/pages |
| 20:28.34 | *** join/#maemo gadgetoid (~gadgetoid@cpc11-nrwh9-2-0-cust593.4-4.cable.virginmedia.com) |
| 20:29.01 | DocScrutinizer05 | though EGCO _should_ be valid, maybe the airport simply doesn't provide weather info |
| 20:29.19 | DocScrutinizer05 | http://en.wikipedia.org/wiki/List_of_airports_by_ICAO_code:_E |
| 20:29.52 | DocScrutinizer05 | ~weather EDDN |
| 20:32.58 | sixwheeledbeast | my though too. |
| 20:33.09 | sixwheeledbeast | s/though/thought/ |
| 20:33.20 | DocScrutinizer05 | too small to even get own wiki page? |
| 20:33.50 | DocScrutinizer05 | not every tiny airfield has weather data available in internet |
| 20:34.16 | sixwheeledbeast | ~weather EGCC |
| 20:34.48 | sixwheeledbeast | ~weather EGGP |
| 20:35.12 | sixwheeledbeast | well I split the difference between them then :) |
| 20:37.32 | *** join/#maemo hardfalcon1 (~hardfalco@f049101083.adsl.alicedsl.de) |
| 20:40.30 | *** join/#maemo Vanadis (~vanadis@77-56-167-203.dclient.hispeed.ch) |
| 20:42.47 | *** join/#maemo cybrNaut (cybrNaut@2001:0:53aa:64c:186f:17dd:bcca:66c4) |
| 20:46.14 | *** join/#maemo lexik (~user@ip-213-220-235-252.net.upcbroadband.cz) |
| 20:47.14 | *** join/#maemo Vanadis_ (~vanadis@77-56-167-203.dclient.hispeed.ch) |
| 20:47.22 | *** join/#maemo konelix (~konelix@190.148.216.121) |
| 20:58.23 | *** join/#maemo Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr) |
| 21:09.02 | *** join/#maemo wotan147 (~max@HSI-KBW-46-223-75-129.hsi.kabel-badenwuerttemberg.de) |
| 21:35.48 | *** join/#maemo robotanarchy (~robotanar@g226211254.adsl.alicedsl.de) |
| 21:42.41 | *** join/#maemo tzafrir_laptop (~tzafrir@bzq-218-28-58.cablep.bezeqint.net) |
| 22:11.00 | *** join/#maemo node00 (~node00@host86-180-158-155.range86-180.btcentralplus.com) |
| 22:12.08 | *** join/#maemo konelix (~konelix@190.148.216.121) |
| 22:22.08 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 22:58.55 | *** join/#maemo konelix (~konelix@190.148.216.121) |
| 23:10.50 | *** join/#maemo RiD (Ghost@bl22-2-189.dsl.telepac.pt) |
| 23:27.46 | *** join/#maemo jonwil (~jonwil@27-33-137-199.static.tpgi.com.au) |
| 23:29.50 | *** join/#maemo triggerhappy (~quassel@112.209.53.176) |
| 23:56.02 | *** join/#maemo Hurrian (~Hurrian@unaffiliated/rikanee) |
