IRC log for #neo900 on 20150315

02:57.29*** join/#neo900 Humpelstilzchen (erik@f050161202.adsl.alicedsl.de)
04:25.31*** join/#neo900 dal2 (~ubuntu@37.252.254.27)
05:04.40*** join/#neo900 ashneo76 (~ashneo76@c-71-194-247-250.hsd1.il.comcast.net)
05:32.51*** join/#neo900 dal2 (~ubuntu@37.252.254.27)
08:34.01freemangordonDocScrutinizer05: Pali is subscribed to neo900-devel, ain't?
08:34.11freemangordonthe ML that is
08:41.16bencohfreemangordon: did he get his mail account back ?
09:15.35*** join/#neo900 paulk-aldrin (~paulk@armstrong.paulk.fr)
09:18.18*** join/#neo900 nicksydney (~quassel@24.169.dsl.syd.iprimus.net.au)
09:24.33*** join/#neo900 mvaenskae (~mvaenskae@unaffiliated/mvaenskae)
09:38.12*** join/#neo900 Pali (~pali@Maemo/community/contributor/Pali)
09:47.53*** join/#neo900 SylvieLorxu (~SylvieLor@dhcp-077-251-165-191.chello.nl)
11:05.29*** join/#neo900 norly (~norly@enpas.org)
11:27.10*** join/#neo900 nicksydney_ (~quassel@183.100.dsl.syd.iprimus.net.au)
11:32.41*** join/#neo900 norly (~norly@enpas.org)
11:33.37*** join/#neo900 norly (~norly@enpas.org)
11:36.40*** join/#neo900 norly (~norly@enpas.org)
11:37.38*** join/#neo900 norly (~norly@enpas.org)
11:37.46*** join/#neo900 norly (~norly@enpas.org)
13:07.03*** join/#neo900 Kabouik (~quassel@65.76.93.92.rev.sfr.net)
13:57.40*** join/#neo900 che11 (~che@p5B070A31.dip0.t-ipconnect.de)
14:16.14*** join/#neo900 ajhc (~alfred@cpc72301-sgyl29-2-0-cust871.18-2.cable.virginm.net)
14:16.39*** join/#neo900 che11 (~che@g231.tum.vpn.lrz.de)
14:20.49*** join/#neo900 mda3 (4ef3e98b@gateway/web/freenode/ip.78.243.233.139)
14:21.42mda3Wow ! a lot of people here; active persons or all zombies ?
14:23.11mda3I'm following the neo900.org since it started, I like the project and would like to help
14:24.16mda3I don't have any electronic capabilities, I'm a web developer (php/javascript), if you need I can help in this area, or unitTests, or translations ?
14:26.42mda3I'll write to contact email so we keep in touch later
14:26.45mda3@++
14:27.36paulk-aldrinmoney perhaps :)
14:28.05mda3:) already backed for a neo900 :)
14:28.21mda3(190 if I remember)
14:28.50mda3there's need for more for sourcing parts ?
14:35.01jake42yes, Doc is in the process of setting up a webshop so everybody can "order" their components
14:47.48*** join/#neo900 ajhc (~alfred@cpc72301-sgyl29-2-0-cust871.18-2.cable.virginm.net)
14:50.50mda3jake42, you mean every person who has backed for a device could give resources (money) so we can source the parts ?
14:52.03*** join/#neo900 kerio_ (~kerio@sorcerer.xd.cm)
15:04.04*** part/#neo900 mda3 (4ef3e98b@gateway/web/freenode/ip.78.243.233.139)
15:11.37freemangordonbencoh: no idea
15:31.19mvaenskaehm, this might be not neo900 related but what does a constantly yellow charging light indicate on the n900?
15:31.30mvaenskaewhile the adapter is plugged in
15:34.47mvaenskaeok, no idea what went wrong, it is booting now :)
15:39.00bencohnot enough battery to boot linux, something like that
15:55.15DocScrutinizer05steady amber == emergency charging
15:55.47DocScrutinizer05or what bencoh said
16:10.52*** join/#neo900 arcean (~arcean@apn-77-115-50-32.dynamic.gprs.plus.pl)
16:16.49*** join/#neo900 kerio_ (~kerio@sorcerer.xd.cm)
16:19.19*** join/#neo900 Guest40222 (~xenophile@unaffiliated/xenophile7x7)
16:21.42mvaenskaecan the n900 therefore flatline and the battery needs to be initiated with some juice for it to finish boot until the battery loading mechanism can be initiated?
16:26.00DocScrutinizer05that's exactly what emergency charging does
16:26.48kerioexcept that it doesn't work if it can't boot
16:27.13DocScrutinizer05to be precise, steady amber means: charging circuitry initialized and charging, main CPU not booted yet
16:27.28DocScrutinizer05kerio: stop spreading BS
16:27.59kerioemergency charging won't bring the voltage up enough for NOLO to allow flashing
16:28.00keriowill it
16:28.14DocScrutinizer05that's another problem
16:29.54DocScrutinizer05when CPU boots then the main CPU eventually takes over control over charging. at that point in time steady yellow stops. When then the system doesn't establish stable charging process, that's the system's problem, not the hardware's
16:30.41keriousers don't particularly care about the hardware
16:30.45keriothey care about the system working
16:30.46kerioas a whole
16:31.14DocScrutinizer05whatever, off topic for this chan
16:32.14DocScrutinizer05Neo900 charging works best when left alone
16:33.21MonkeyofDoomgood :D
16:33.54DocScrutinizer05anyway mvaenskae asked if battery needs some kickstart to make N900 start charging, aiui. No it doesn't
16:35.27DocScrutinizer05the flatbat-deadlock is another problem
16:35.49DocScrutinizer05related to usually bootloops
16:36.00DocScrutinizer05~flatbatrecover
16:36.01infobotRemove 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 shut off -> start over again with ~flatbatrecover while already searching for a new battery. CAVEAT! Only works when ~rootfs OK (no ~bootloop)
16:36.17DocScrutinizer05~bootloop
16:36.34DocScrutinizer05~#maemo bootloop
16:36.34infobot[#maemo bootloop] when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing. E.g. using ~rescueOS. Or external charger or BL-5J compatible other device.
16:39.31DocScrutinizer05I *really* wish Nokia had integrated a charge mode into xLoader or at least NOLO already
16:40.01DocScrutinizer05for N9 they did ;-P
16:40.46DocScrutinizer05but then, for N9 it would be pretty inconvenient to charge battery externally X-P
16:43.25DocScrutinizer05I really wonder what a certain (ex-)Nokia employee tested with flasher-3.5(!) on N9 that made him mumble "thought as much, they were lazy"
16:45.24DocScrutinizer05mind you, flasher-3.5 is for N900 and before, for N9 you're supposed to use 3.12
16:48.25DocScrutinizer05probably certain cert/checksum tests were not yet implemented in flasher-3.5
16:54.11*** join/#neo900 ddark (~ddark@ddark.ws)
16:59.53DocScrutinizer05((wish Nokia had integrated)) at very least into 2nd/secondary needed for coldflashing. They easily could have added a batt charge mode into that, and patch flasher-3.5 so that it reboots device into "rescue&charge / coldflashing mode" when battery too low for regular NOLO based flashing
17:00.27*** join/#neo900 mda3 (4ef3e98b@gateway/web/freenode/ip.78.243.233.139)
17:01.49DocScrutinizer05ohmy "haette haette Fahrradkette"
17:02.12DocScrutinizer05Like a german politician once said
17:04.56DocScrutinizer05idly wonders if Neo900 flashing will support DFU, and/or Nokia "mark2"(?), or only boot from auxiliary system via uSD
17:07.04DocScrutinizer05while Pali kicked 0xFFFF into shape and thus we have FOSS flasher for the Nokia protocol, it seems we completely lack any implementation on bootloader side that supports it, right?
17:08.13Paliyes, server side of nokia flashing protocol is missing...
17:08.16DocScrutinizer05then otoh I'm not educated about how DFU is implemented. Is it part of UBoot?
17:08.35Palino idea
17:09.49DocScrutinizer05I'm pretty sure an unpatched NOLO won't work on any other device but N900, not even on a Neo900
17:10.27DocScrutinizer05and we just seen that detection of our awesome 1GB RAM depends on uboot as well
17:11.36DocScrutinizer05so despite all efforts of your humble EE team, Neo900 compatibility to N900 most certainly ends at NOLO
17:12.31DocScrutinizer05IOW we won't be able to support the "use flasher-3.5 to flash a slightly tweaked FIASCO image to Neo900" scenario
17:13.24DocScrutinizer05not even in coldflashing mode
17:17.08DocScrutinizer05Pali: how much of your time and Neo900 UG's money would it cost to have you (re-)implement http://www.omappedia.com/wiki/Maemo_Getting_Started on a BB-xM we send to you?
17:19.08*** join/#neo900 dal2 (~ubuntu@37.252.238.67)
17:19.42Paliright now I do not have enough of free time :-(
17:21.37DocScrutinizer05OK, this is a public job offer now. Who's first and cheapest will make the deal
17:22.20*** join/#neo900 joecool (~joecool@no-sources/joecool)
17:22.48DocScrutinizer05(when we consider her/him sufficiently qualified to actually accomplishh the job)
17:23.24joecoolDocScrutinizer05: neo900.org down?
17:23.31DocScrutinizer05o.O
17:23.37joecooli cannot resolve the host
17:23.45DocScrutinizer05not for me
17:24.01DocScrutinizer05some DNS hickup once again?
17:24.13DocScrutinizer05dos1: could you check please
17:24.56DocScrutinizer05joecool: please pastebin your complete "host -a neo900.org"
17:25.36joecoolDocScrutinizer05: working now -_-
17:25.45joecool(only after running that command)
17:26.21dos1yep, everything looks fine for me
17:27.16DocScrutinizer05yep, here too
17:27.29DocScrutinizer05even on primary DNS
17:27.44DocScrutinizer05-D
17:28.01DocScrutinizer05host -a neo900.org ns106.ovh.net
17:28.26joecoolhttp://pastebin.com/raw.php?i=yJTTjTFi
17:29.34DocScrutinizer05joecool: that looks odd nevertheless
17:30.51joecoolall of the gentoo domains seem to hit this problem too for my dns (either with comcast or google public dns)
17:31.43DocScrutinizer05http://pastebin.com/swDJutFA
17:33.38DocScrutinizer05I know many sysops love to bash me for using host instead dig... Well, old dog ... ;-)
17:34.13joecoolDocScrutinizer05: dig often hangs in this situation, host doesn't
17:34.21DocScrutinizer05yes
17:35.03DocScrutinizer05I've also seen dig deliver weird bogus results when sth been screwed up
17:36.47DocScrutinizer05anyway here you are: http://pastebin.com/wiuVwnV5
17:38.10DocScrutinizer05UGH, missed to point to primary NS
17:38.24DocScrutinizer05nm
17:41.55*** join/#neo900 SylvieLorxu (~SylvieLor@dhcp-077-251-165-191.chello.nl)
17:42.29DocScrutinizer05joecool: host -a neo900.org 8.8.8.8 ; looks good here too
17:42.50DocScrutinizer05(((either with comcast or google public dns))
17:50.35*** join/#neo900 vakkov (~vakkov@s3n104.brunel.ac.uk)
18:18.37*** join/#neo900 vakkov (~vakkov@s3n104.brunel.ac.uk)
18:45.02*** join/#neo900 sparetire_ (~sparetire@unaffiliated/sparetire)
18:46.00*** join/#neo900 vakkov (~vakkov@134.83.207.20)
19:18.37*** join/#neo900 joecool (~joecool@no-sources/joecool)
19:23.43*** join/#neo900 dal2 (~ubuntu@37.252.238.67)
20:46.30*** join/#neo900 nicksydney (~quassel@183.100.dsl.syd.iprimus.net.au)
20:59.18*** join/#neo900 Wizzup (~Wizzup@a82-161-36-93.adsl.xs4all.nl)
21:04.39*** join/#neo900 DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
21:04.39*** mode/#neo900 [+v DocScrutinizer05] by ChanServ
21:13.37DocScrutinizer05"this reboot delivered to you by courtesy of systemd"
21:17.41DocScrutinizer05https://bugzilla.opensuse.org/show_bug.cgi?id=918226
21:18.03*** join/#neo900 che11 (~che@g232.tum.vpn.lrz.de)
21:26.48*** join/#neo900 phre4k (~phre4k@55d4150c.access.ecotel.net)
21:30.08DocScrutinizer05~botsnack
21:30.08infobotaw, gee, DocScrutinizer05
21:30.38DocScrutinizer05wow, that's even more scary. IRC completely silent on 20 channels since reboot
21:30.44keriopenis
21:30.56kerioARE YOU FEELING BETTER
21:31.03DocScrutinizer05YES :-D
21:32.24DocScrutinizer05above bug is incredible. Opensuse/cabal messed up an arbitrary number of machines incl servers running 13.1
21:32.44DocScrutinizer05gotta love systemd, no?
21:33.43DocScrutinizer05what however bothers me even more is: I wasn't able to find this ticket or other notes about the bug. Seems my google fu also sucks meanwhile
21:34.31DocScrutinizer05finally the fine people of Suse inc in #opensuse helped ;-)
21:36.07kerioi'm not installing the backported libvirt 1.something because it wants to install libsystemd-something
21:36.21kerioand consolekit
21:38.01DocScrutinizer05yes, soon you'll find zilch linux packages that could run on a systemd-free system
21:46.34kerioDocScrutinizer05: do you have ipv6
21:47.24DocScrutinizer05well, prolly no
21:47.27keriogoddammit
21:47.47kerioi don't want to fire up a DO droplet just to ping
21:48.17DocScrutinizer05my DSL provider offers IPv6 but my landlord and router/DSL-owner doesn't really like to use it
21:48.31dos1kerio: what do you need?
21:48.42keriodos1: http://[2a01:4f8:120:940d::4242:4242]:8000/
21:48.48keriodoes it do anything?
21:48.50DocScrutinizer05err
21:49.23dos1kerio: connection refused
21:49.27keriofuck
21:50.00dos1there are only ports 22 and 111 open on that address
21:50.13keriooh
21:50.19kerioServing HTTP on 0.0.0.0 port 8000 ...
21:50.23keriohow do i tell python to listen on ::
21:54.06keriodos1: alright, http://[2a01:4f8:120:940d::4242:4242]/
21:54.11keriodo you see the "welcome to nginx" page
21:54.56dos1still nope, and nmap result is the same
21:54.59keriodear lord
21:55.04keriowhy doesn't nginx listen to ipv6 by default
21:55.31keriodos1: ok go
21:55.40kerioALRIGHT
21:55.44kerioyou have no idea how happy this makes me
21:55.46kerio^_^
21:55.51kerioalso i got ur ip lol
21:55.51dos1port 80 is now open
21:55.54kerioperfect
21:56.36keriodos1: tyvm
21:57.04dos1it's ip of my vps :P
22:04.17*** join/#neo900 Oksana (~chatzilla@129.94.239.199)
22:25.28DocScrutinizer05curses bash alias. totally ANNOYING USELESS option -p, results in ``alias -='bla' ´´ throwing error "bash: alias: -=: invalid option"
22:26.30DocScrutinizer05which looks negligible but spoils your day when you have such alias defined in .bash_aliases
22:27.37DocScrutinizer05solution: test -s ~/.aliases && alias alias='alias --' && . ~/.aliases || true
22:28.31enycDocScrutinizer05: lol
22:28.43enyclike the redefinition of alias using itself ;p
22:31.43DocScrutinizer05which jackass invented redundant option -p for alias?
22:34.46DocScrutinizer05background info: Opensuse bash comes with stuff like >> alias +='pushd ; .' alias -='popd' ; alias ..='cd ..' ; ...<< predefined
22:35.39DocScrutinizer05like another goodie invented by me? ;-)
22:35.42DocScrutinizer05alias ?='man $(history -p "!!:0")'
22:36.23DocScrutinizer05opens manpage for last command entered
22:37.44DocScrutinizer05http://paste.opensuse.org/74646659
22:38.12*** join/#neo900 kerio (~kerio@2a01:4f8:120:940d::cafe:babe)
22:42.21DocScrutinizer05maybe -p option was useful for an extension of POSIXLY_CORRECT alias, but for sure a posixly correct alias shouldn't accept any -option. For bash's extended alias builtin the "reusable format" for output is default, so -p is useless there either
22:43.39DocScrutinizer05<PROTECTED>
22:43.41DocScrutinizer05<PROTECTED>
22:43.52DocScrutinizer05from BASH_BUILTINS(1)
22:44.29DocScrutinizer05shakes fist
22:44.38FIQlol
22:44.43FIQso basically
22:44.50FIQ-p is there to make your life harder
22:44.54DocScrutinizer05yes
22:47.26DocScrutinizer05pun on me: I forgot about unalias and tried to undefine my ``alias alias='alias --'´´ by giving a ``alias alias=´´.  Guess what resulted ;-)
22:49.10DocScrutinizer05((tried to undefine...)) for testing alias -p
22:52.19DocScrutinizer05<PROTECTED>
22:54.16*** join/#neo900 vakkov (~vakkov@134.83.207.20)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.