IRC log for #maemo on 20140810

00:01.35*** join/#maemo pdz (~paul@c-67-169-80-116.hsd1.ca.comcast.net)
00:03.14*** join/#maemo Venusaur (~wdwrwf@wikipedia/Antonio-Lopez)
00:21.36DocScrutinizer51when for some reason you want to change the way maemo community and organizationl entites work, then there's exactly ONE way to push that: start a thread on tmo or even better on ML and and begin with explaining the problem you think you spotted. Then list your ideas how to improve/fix the issue, first things first. And finally ask for (constructive) criticism, create a synthesis from your and other members' contributions and notions and tr
00:21.37DocScrutinizer51y to convince *the community* to support your plan/synthesis. This regularly will result in *council* starting a referendum to fulfill what *community* wants
00:25.20DocScrutinizer51suggesting a referenum to council in a private email doesn't make sense since council would at least need to do the same first 3 steps like I suggested to you above
00:28.25*** join/#maemo pdz (~paul@c-67-169-80-116.hsd1.ca.comcast.net)
00:47.53*** join/#maemo bef0rd (~bef0rd@unaffiliated/beford)
00:53.59*** join/#maemo astr (~astr@79-69-194-249.dynamic.dsl.as9105.com)
01:30.32*** join/#maemo shamus (~shmaus@ip-206-192-193-180.marylandheights.ip.cablemo.net)
01:59.24*** join/#maemo Humpelstilzchen (erik@e177143221.adsl.alicedsl.de)
02:21.19*** join/#maemo qwazix (~qwazix@Maemo/community/council/qwazix)
02:32.31*** join/#maemo maybeArgh (~cl@p5790F2BA.dip0.t-ipconnect.de)
03:21.13*** join/#maemo Gh0sty (~ghosty@fosdem/staff/gh0sty)
03:52.12*** join/#maemo flynx (~flynx@70-139-50-84.lightspeed.hstntx.sbcglobal.net)
03:53.57*** join/#maemo flynx (~flynx@70-139-50-84.lightspeed.hstntx.sbcglobal.net)
03:57.42*** join/#maemo erlehmann (~erlehmann@82.113.99.207)
04:03.05*** join/#maemo AndrewX192 (~andrew@unaffiliated/andrewx192)
04:04.07*** join/#maemo AndrewX192 (~andrew@unaffiliated/andrewx192)
05:16.25*** join/#maemo vakkov (~vakko@vlan-174-game-235.comnet.bg)
05:16.29*** join/#maemo vakkov_ (~vakko@vlan-174-game-235.comnet.bg)
05:22.10*** join/#maemo FlameReaper-PC (~FR@64.34.48.60.klj03-home.tm.net.my)
05:22.57*** join/#maemo kraft (kraft@gateway/shell/blinkenshell.org/x-tsajsfuerdwhzcge)
05:43.04*** join/#maemo dhbiker (~dhbiker@APN-122-89-154-gprs.simobil.net)
05:59.26*** join/#maemo nico_07 (~nico@93.37.90.239)
06:00.15*** join/#maemo doc|home (~doc@69.172.145.146)
06:00.24*** join/#maemo doc|home (~doc@gentoo/contributor/doc-007)
06:06.06*** join/#maemo LauRoman|Laptop (~LauRoman@5-14-57-68.residential.rdsnet.ro)
06:14.20*** join/#maemo SAiF1 (~SAiF@59.96.204.182)
06:19.06*** join/#maemo LauRoman (~LauRoman@5-14-57-68.residential.rdsnet.ro)
06:24.37*** join/#maemo mavhc (~mavhc@cpc65310-basf8-2-0-cust204.12-3.cable.virginm.net)
06:30.07*** join/#maemo mavhc (~mavhc@cpc65310-basf8-2-0-cust204.12-3.cable.virginm.net)
06:30.27*** join/#maemo vakkov (~vakko@vlan-174-game-235.comnet.bg)
06:33.45*** join/#maemo DrCode (~DrCode@gateway/tor-sasl/drcode)
07:09.07*** join/#maemo lowkyalur (~no@dslb-088-070-141-187.088.070.pools.vodafone-ip.de)
07:14.03DarkFoxHello world, just wondering if anyone here could give me a number to expect to charge a N900 from flat to bootable ?
07:14.50DarkFoxhas had an N900 charging for a good 5-10 minutes now and not booting... Not sure the exact power given from my laptop but I haven't had this issue with my other N900 [when that worked].
07:15.45kerio~flatbatrecovery
07:16.04keriohrmpf
07:16.07sixwheeledbeast~flatbattrecover
07:16.14sixwheeledbeast~ping
07:16.14infobot~pong
07:16.14kerio~flatbatrecover
07:16.14infobotRemove 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)
07:16.19keriogot it
07:16.23sixwheeledbeast;)
07:16.48DarkFoxHehe
07:16.49DarkFoxSweet
07:16.52DarkFoxThanks guys
07:16.54DarkFoxI shall try this
07:17.06DarkFoxwas trying different batteries; but wallcharger... Let me find that ;)
07:18.55DarkFoxWait; I see amber light now with USB; didn't have this before.
07:19.00DarkFoxShould I just leave it with USB power ?
07:19.20DarkFoxdid find the charger :P
07:20.52DarkFoxSwapped over
07:21.01DarkFoxleaves it for 30 minutes
07:21.27DarkFoxsets up a backup battery (N95 + it's charger)
07:21.40kerioDarkFox: it will barely charge via usb during emergency charging
07:21.45kerioit's like 100mA
07:22.03keriothe wallcharger (in emergency charging) charges 250mA
07:22.53DarkFoxkerio: I've switched, so charger is active; I'm just about to plug in my N95 to the UPS as well.
07:23.13DarkFoxN95 = great backup N900 charger... As proven with my first N900 whose USB port is dead.
07:23.43DarkFoxI'd soldier it back on - if the screws weren't butchered.
07:23.53DarkFoxHence I have 2 :)
07:24.08DarkFoxBeep -> Naww, just the N95 :C Lol
07:24.12*** join/#maemo arcean (~arcean@aaen16.neoplus.adsl.tpnet.pl)
07:25.01DarkFox~/n900 >> flasher-3.5 -F RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin -u  
07:25.03DarkFoxError reading FIASCO header: Success
07:25.29DarkFox> Not finished downloading; ignore that. Error still misleading
07:26.41DarkFoxlets phone charge and image download.
07:26.47DarkFoxgoes afk. Thanks kerio
07:30.12Sicelo~bootloop
07:30.12infobotit has been said that 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. E.g. using ~rescueOS. Or external charger or BL-5J compatible other device.
07:30.45DarkFoxBack
07:31.07DarkFox~rescueOS
07:31.07infobotrumour has it, rescueos is http://n900.quitesimple.org/rescueOS/
07:31.19DarkFoxNice
07:32.16kerioSicelo: can't even load rescueos if the battery's too low
07:33.15Siceloyes, i am aware. my N900 is fine ;)
07:36.06Sicelobut of course, it is BME which 'rushes' to shut the device down, so you actually can load rescueOS when the battery is less than BME Threshold (3248mV, right?), but as long as it is above 3000mV
07:51.45DarkFox~/n900 >> sudo flasher-3.5 --enable-rd-mode
07:51.58DarkFox^ While holding 'u' when trying to power it on. Shouldn't this simply work?
07:53.29DarkFoxBus 003 Device 025: ID 0421:01c7 Nokia Mobile Phones N900 (Storage Mode)
07:53.33DarkFoxlsusb ^
07:54.54Sicelowhy you want rd-mode by the way?
07:55.31DarkFoxSicelo: Trying to test communication to the phone currently; soon to reflash it.
07:55.48Sicelothe best way to get into flashing mode is to start the flasher before connecting the device
07:55.52DarkFoxIt's been a couple of years since I last used this.
07:56.03DarkFoxSicelo: Yea... That's what I'm trying :)
07:56.17DarkFox<PROTECTED>
07:56.29DarkFox~/n900 >> flasher-3.5 -i                
07:56.30DarkFoxflasher v2.5.2 (Oct 21 2009)
07:56.30DarkFoxSuitable USB device not found, waiting.
07:56.35DarkFoxboots phone while holding 'u'
07:56.48DarkFox"Nokia"
07:56.52DarkFoxNo usb symbol
07:57.01Siceloi must say i'm also no longer too sure about the 'u' thing (my device has only been flashed once in its entire life) .. but i don't remember needing to use "u" key
07:57.03DarkFoxErm
07:57.38DarkFoxWorked this time; didn't before. and forgot to run this as root this time; so... device is busy now...
07:58.25DarkFoxTrying again
07:58.26DarkFox:P
07:58.50DarkFoxNope...
07:59.43DarkFoxError claiming USB interface: Device or resource busy
08:04.38DarkFox~busy
08:04.45DarkFox~resourcebusy
08:04.46DarkFox:P
08:05.21DarkFoxmodprobe -r cdc_phonet
08:05.22DarkFoxYay
08:05.48kerioyay
08:07.00DarkFoxDownload ETA 30 seconds...
08:08.45DarkFoxFlashing kernel
08:08.48keriobut why
08:08.49DarkFoxSending rootfs
08:08.50DarkFox^,^
08:09.08DarkFoxkerio: This second N900 of mine was (also) 2nd hand and the previous owner forgot the pin.
08:09.12DarkFoxAnd so; reflash to fix :P
08:09.13kerioi see
08:09.51DarkFoxGot the first N900 for $120 off eBay couple years back; this second one for $35 from the local LUG here. :D
08:10.18DarkFoxRebooting! \o/
08:10.29DarkFoxKernel infos in green on white \o/
08:11.10DarkFoxhugs N900
08:11.12DarkFoxWorks :D
08:11.12kerio\o/
08:11.23kerioDUDE DON'T HUG THE N900 WHILE THE USB CABLE IS CONNECTED
08:11.24kerioJEEZ
08:11.28DarkFoxThis dot animation :P
08:11.34DarkFoxLol
08:11.35*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
08:11.46DarkFoxLong long animation
08:11.50DarkFoxdeosn't remember it taking this long
08:12.19DarkFoxAlso, second reason to flashing is complementary to being 2nd hand; who knows what the previous owner had on the phone. Could have spyware or private data.
08:12.22DarkFoxGone
08:12.30DarkFoxNot that the image I pushed would preserve /home...
08:12.31DarkFoxOh well
08:12.32DarkFox:P
08:12.49DarkFoxErm
08:13.04DarkFoxkerio: To get rid of the pin; must I reflash the entire device? D:
08:13.21DarkFoxJust flashed it 'RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin' but pin still active...
08:13.36DarkFox~pincode
08:13.40DarkFox~pin
08:13.40infobotsomebody said pin was $1 <action> laughs as darkfox gets $1 in a headlock while screaming 'Say Uncle!'
08:13.51DarkFoxfacepaw
08:14.16DarkFox!pin kerio
08:14.18DarkFox~pin kerio
08:14.18infobotACTION laughs as darkfox gets kerio in a headlock, screaming 'Say Uncle!'
08:14.24DarkFoxLol
08:15.08bencoh:D
08:15.10DarkFox~lockcode
08:15.10infobotlockcode is, like, http://talk.maemo.org/showthread.php?p=524522#post524522
08:15.25DarkFoxHow fun
08:16.00DarkFoxssh kinda not doable atm :D
08:16.24kerioDarkFox: yeah it wasn't a good idea tbh
08:16.30kerioanyway, you just need rescueOS
08:16.33kerioand you can easily crack the pin
08:16.36kerioby reading CAL
08:16.43DarkFoxOh?
08:16.48DarkFoxRescueOS sounds useful ;)
08:16.51DarkFox~rescueos
08:16.51infobotmethinks rescueos is http://n900.quitesimple.org/rescueOS/
08:16.54kerioyou need to read CAL
08:17.01kerioaka /dev/mtd2?
08:17.17DarkFoxkerio: Sounds like booting from SD card?
08:17.22kerionah, usb
08:17.28DarkFoxOh
08:17.30DarkFoxVia flasher?
08:17.40kerioyep
08:17.42kerioyou just load it
08:17.43DarkFoxhttp://n900.quitesimple.org/rescueOS/documentation.txt
08:17.44DarkFox:)
08:17.52DarkFoxSweet
08:18.05DarkFoxTINY RESCUE DOWNLOAD FASTER :D
08:18.11DarkFoxETA: 1 minute
08:21.53DarkFox"No initfs \o/" - N900
08:21.55DarkFoxWow
08:25.21DarkFox~/n900 >> sudo flasher-3.5 -k 2.6.37 -n rescueOS-1.1.img -l -b"rootdelay root=/dev/ram0"
08:25.24DarkFoxkerio: This look right?
08:25.33DarkFoxMethod is not supported in the current mode
08:25.35DarkFoxSU_VERIFY_COMMS_REQ timed out.
08:28.42DarkFoxGetting the same problem with -i now
08:28.46DarkFoxflasher not working :/
08:29.20DarkFoxThink I got it to work now
08:29.20DarkFoxYay
08:29.40DarkFoxkerio: Powered off phone, removed battery; now I have rescue; thanks. :)
08:32.52*** join/#maemo dhbiker (~dhbiker@APN-123-3-157-gprs.simobil.net)
08:35.23DarkFox~/n900 >> john -format:DES -i:digits lock-code
08:36.00DarkFoxwaits
08:40.40DarkFoxLoaded 1 password hash (Traditional DES [128/128 BS SSE2-16])
08:40.40DarkFoxguesses: 0  time: 0:00:00:38 DONE (Sun Aug 10 18:40:10 2014)  c/s: 2880K  trying: 83593867 - 83536784
08:40.43DarkFox~/n900 >> john -show lock-code
08:40.44DarkFox0 password hashes cracked, 1 left
08:40.45DarkFox:/
08:42.37DarkFoxIf this doesn't work; I'm gonna edit it so it uses something that someone else already cracked :P
08:43.36keriodon't edit /dev/mtd devices directly
08:44.28DarkFoxkerio: Naww ;)
08:44.35bencoh:]
08:44.42DarkFoxroot:vFPJSgPXY5G7o:
08:44.46DarkFoxWhat am I doing wrong ^
08:44.47DarkFox:P
08:45.05*** join/#maemo bluelupo (~quassel@2a02:810d:1600:7f0:e2cb:4eff:fe8b:b2f1)
08:45.38DarkFoxWAIT
08:45.43DarkFoxWhat...
08:45.48kerioWAIt
08:45.51keriowhat?
08:45.58DarkFoxMy N900 decided to partiall load the firstboot setup
08:46.01DarkFoxBut then it rebooted
08:46.02DarkFoxo_0
08:46.19keriofriday night, another round of shots
08:46.24kerioTURN DOWN FOR WHAT
08:47.07bencohwhat what what
08:47.17DarkFoxloading rescue again
08:47.28DarkFoxlooked away from his computer to look back to see it was done already :P
08:51.20Luke-Jrwonders how to interpret http://jsfiddle.net/eM2Mg/3837/embedded/result/
08:51.50*** join/#maemo astr (~astr@79-69-199-175.dynamic.dsl.as9105.com)
08:53.19DarkFoxEvil typo in the FP vs PF
09:02.00DarkFoxLuke-Jr: Good question
09:02.26DarkFoxAnyhow; thanks again kerio  ^,^
09:07.37DarkFoxkerio: How difficult do you think it would be to have an sd card in my other N900 (broken usb port) to turn the wifi or bluetooth into a remote loader? :3
09:11.23DarkFoxI think it might be a fun project after I end up playing with nanobsd on this phone :P
09:14.23DarkFox's booted phone doesn't charge... Hmmm
09:15.30DarkFoxLooks like it's fine now that I've removed the battery :)
09:16.00Luke-Jrwait, it's charging without the battery?
09:16.05Luke-Jrhow does that work?
09:16.13DarkFoxLuke-Jr: Removed, and reinserted*
09:16.36Luke-Jrah ok
09:16.38Luke-Jr:P
09:16.39DarkFox:D
09:17.09DarkFoxhad to just john --show lock-code ;)
09:17.21DarkFoxshould change it :D
09:17.23*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
09:17.42DarkFoxCharging \o/
09:17.43DarkFox:D
09:18.44DarkFoxshould have setup usbnetworking+ftp in that rescueos... passphrase for wifi is crazy long and well... random :D
09:31.47*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
09:59.52DarkFox~rescueos
09:59.52infobothmm... rescueos is http://n900.quitesimple.org/rescueOS/
10:03.37*** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au)
10:06.56kerioDarkFox: there's usb networking and ftp
10:07.03DarkFoxkerio: I'm trying that :P
10:07.35DarkFoxkerio: What commands on my host system to even get this? :D
10:07.51DarkFoxI like it's scripts that it has itself... But need a host script :P
10:08.20kerioanyway, you should've installed uboot on the n900 with the broken usb
10:08.33DarkFoxkerio: Indeed
10:08.35DarkFoxkerio: Too late now
10:08.38DarkFoxI was going to
10:08.39kerionow it's too risky
10:08.40DarkFoxAnd then it broke
10:08.41DarkFox:C
10:10.29DarkFoxkerio: After running the scripts in the rescue os...
10:10.38DarkFoxkerio: How to get it to connect to my lan? :P
10:12.40DarkFoxOr at least; let my host connect to it's ftp :P
10:24.33*** join/#maemo jmlich (~jmlich@188.75.179.29)
10:43.17*** join/#maemo freemangordon (~ivo@46.249.74.23)
10:55.36*** join/#maemo amizraa (~amizraa@gateway/tor-sasl/amizraa)
11:09.35*** join/#maemo shentey (~shentey@f053042083.adsl.alicedsl.de)
11:09.44kerioDarkFox: ifconfig usb0 192.168.2.42 up
11:40.10*** join/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de)
11:40.56*** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil)
12:15.08DocScrutinizer51only if your local LAN isn't already on 192.168.2.x
12:16.16*** join/#maemo Kabouik (~quassel@221.77.69.86.rev.sfr.net)
12:16.30DocScrutinizer51ultimately instructs to use 192.168.51.51 for N900 USB IP *only*
12:20.33Palior use some private ipv6 prefix
12:20.33DocScrutinizer51when you try to ifup a NIC with an IP in range of already established network, you're begging for trouble
12:20.34DarkFoxkerio: Yea, that wasn't it; I did get it a while back.
12:21.08*** part/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de)
12:21.14DarkFoxIt gives me two interfaces (on my host) I just had to assign myself an ip and setup the route on the virtual ethernet (not the peer-to-peer,noarp device which I first tried)
12:21.24DocScrutinizer51hi Pali - long time no see! :))
12:21.25DarkFoxkerio: But yea; thanks anyway. :)
12:21.29DarkFoxlikes the rescueOS :D
12:21.36Palihi!
12:21.49DarkFoxHai!
12:21.50DocScrutinizer51good to see you aeround
12:22.23DocScrutinizer51maemo isn't same without you
12:24.01DarkFoxwonders if anyone has a minimal nanobsd image that works on the N900?
12:24.47jon_yBSD? Why would you use that? :)
12:24.51DocScrutinizer51wgat for?
12:25.13DarkFoxjon_y: Because it's a great system?
12:25.18jon_yGPL4evar!
12:25.41DocScrutinizer51errrr forgetit
12:25.51DarkFoxDocScrutinizer51: Nice base system that I could use for testing a custom operating system that I intend to design.
12:26.06DarkFoxOr rather, I've designed most of it; and would like to use the N900 as a test platform. :P
12:26.22DocScrutinizer51~fptf
12:26.22infobot[fptf] the Fremantle Porting Task Force, see http://talk.maemo.org/showthread.php?t=91308
12:26.49DocScrutinizer51also about freeing fremantle
12:27.07DarkFoxWhat's this?
12:27.17DocScrutinizer51there's a reason for some of the closed blobs
12:27.54DarkFoxIndeed
12:28.18jon_yBSD is the last thing I think of when Freedom is involved :)
12:28.22DocScrutinizer51maemo is as free as it gets already, nothing a bsd could do better
12:28.30DarkFoxjon_y: Why?
12:28.35jon_yat least proprietory software is up front about it
12:28.36DarkFoxjon_y: BSD is more free..
12:28.43jon_yBSD is enabler of proprietary
12:28.55DarkFoxjon_y: Enables, but it is less restrictive.
12:28.58*** join/#maemo shentey (~shentey@f053042083.adsl.alicedsl.de)
12:29.08DarkFoxSimplier and you don't need to be a lawyer to read the license.
12:29.12jon_yexactly, it is poisonous to Free software
12:29.23jon_ybecause it doesn't stay Free
12:29.26DarkFoxNo it doesn't...
12:29.45jon_ypersonally, I don't consider BSD Free software
12:30.06jon_ybut nvm me, I'm starting to rant
12:30.29DarkFoxPlease; no license wars... BSD is an open source license. FreeBSD is an operating system where basically everything is licensed BSD. This allows you to create something propritary (such as sony's playstation) without the requirement to return the code.
12:30.45DarkFoxEven in Sony's case, they do send code back to the community.
12:30.46DarkFoxApple too.
12:30.49DocScrutinizer51please no os wars here
12:30.59DarkFoxDocScrutinizer51: License even.
12:31.06jon_yno os wars, just license wars
12:31.11DarkFoxLol
12:31.15DarkFoxjon_y: None of this either!
12:31.41jon_ypssh Apple
12:31.46jon_yor Sony
12:31.51DocScrutinizer51on N900 fremantle with powerkernel is best you can get regarding support for all hw and openness as well
12:31.55DarkFoxjon_y: BSD is more free (less restrictive) then GPL.
12:32.07DarkFoxjon_y: Fact is over.
12:32.07jon_yif they're sending back code then there is no problem with GPL
12:32.29jon_ynope, it is less Free because it does not protect Freedom at all
12:32.42DarkFoxjon_y: GPL is a problem with licensing... It puts restraints on anyone who wants to do anything with it.
12:32.57DarkFoxHassle and can lead to ugly legal issues.
12:33.10DocScrutinizer51please move it to #bsd
12:33.13DarkFoxjon_y: IF you want to continue the license war then please /msg me
12:33.19jon_ysure
12:33.22DarkFoxDocScrutinizer51: Hell no, jon_y would probally get kicked
12:33.27DarkFoxOr worse, banned.
12:33.53DocScrutinizer51or you both begg be to kick you here ;-P
12:34.03DocScrutinizer51beg me
12:35.51DocScrutinizer51please consider I'm paying for each singe byte of data roaming to read what you write while I'm supposed to enjoy my holidays
12:36.44DocScrutinizer51and hell they still charge an arm and a leg for that
12:38.55DocScrutinizer51when you want moden kernel see what freemangordon achieved already, reports are on fptf thread
12:39.44DocScrutinizer51when you want an os without closed blobs youre free to delete them from maemo to end up with a plain debian
12:40.15DarkFoxDocScrutinizer51: LOL
12:40.18DocScrutinizer51no need for bsd or openwrt just to go 'more free'
12:40.29DarkFoxCharging us for the ineffecient text-based protocol known as IRC.
12:44.53DarkFoxUh oh...
12:45.09DarkFoxApp manager on a fresh maemo install; no updates.
12:45.19DarkFoxIs this due to Nokia not renewing their certificate?
12:45.21DocScrutinizer51I think IRC prot is quite efficient as long as chanops take care of layer8 noise ;)
12:46.08DocScrutinizer51DarkFox: there are no 'updates' on maemo
12:46.16DocScrutinizer51go for CSSU
12:46.23DarkFoxWhat?
12:46.28DocScrutinizer51~cssu
12:46.28infobotwell, cssu is http://wiki.maemo.org/Community_SSU
12:47.14*** join/#maemo arcean (~arcean@aaen16.neoplus.adsl.tpnet.pl)
12:47.19DocScrutinizer51even there no rolling updates though I pushed for that since years
12:48.55DocScrutinizer51you however get updayes on maemo-extras(-*) but only for packages you installed from there. On a fresh install zilch is from extras on ur system
12:49.22*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
12:50.19DocScrutinizer51and even when u install sth now from extras, it will be newest version and any update will come up in days or weeks the fastest
12:50.47DocScrutinizer51maemo stock didn't change since PR1.3?q
12:50.59DocScrutinizer511.3.1 even
12:51.26DocScrutinizer51so:
12:51.42DocScrutinizer51~pr131
12:51.42infobotwell, combined is the rootfs fiasco image of maemo. For N900 latest (PR1.3.1) see http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/9/--FID--A0A22MVWFVFAM/--LID--FiRe1317015685654/RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin, or http://galif.eu/nokia/
12:52.10DocScrutinizer51no updates expected on that
12:53.12DocScrutinizer51maemo is special in that it's a single huge metapackage aka PR
12:53.16*** join/#maemo hurrian (~hurrian@112.205.54.27)
12:53.16*** join/#maemo hurrian (~hurrian@unaffiliated/rikanee)
12:53.52DocScrutinizer51and NEVER do apt-get upgrade or even dist-upgrade!
12:55.22DocScrutinizer51I think nobody everwrote the much needed "what's maemo" 20p primer
12:56.35DocScrutinizer51Nokia seems to always have thought it all 'just works' and users are too stupid to even grok the concept of pathbanes
12:57.32DocScrutinizer51see incredibly fsckdup-by-design meta filesystem based on tracker
13:00.12DocScrutinizer51CSSU antway is supposed to come in where Nokia left, providing security fixes and *compatible* functionality updates that Nokia missed to ever deliver
13:01.49DocScrutinizer51"d powerkernel brings back expert functons that nokia kicked out in favor for a more lean easier to maintain kenel
13:01.59DocScrutinizer51and*
13:03.03DocScrutinizer51andeven kernel bugfixes
13:04.54DocScrutinizer51and now even a workaround for a silicon error that rendered thumb ISA useless
13:05.58DocScrutinizer51kudos to freemangordon who pulled this thumb stuff off despite *everybody* antagonizing him
13:06.31DocScrutinizer51even I did, to a certain degree
13:14.35drathirin short cssu rocks...
13:16.23drathirgoin to reflash n900 with broken screen...
13:18.35DocScrutinizer51broken screen? LCD or touchpanel aka digitizer, or even just the main flex?
13:35.01*** join/#maemo sunny_s (~sunny_s@pd95c1f18.dip0.t-ipconnect.de)
13:53.52*** join/#maemo flynx (~flynx@70-139-50-84.lightspeed.hstntx.sbcglobal.net)
13:54.43drathirDocScrutinizer51: connector from lcd not egsist sadly when i checked reason of no video output...
13:55.43drathirscreen maybe works but w/o plug at end not possible to connect...
13:56.00DocScrutinizer51duh!
13:56.18DocScrutinizer51where the plug gone?
13:56.56drathirdigitizer maybe works but no possibility to check - no output on the tv-out...
13:57.18drathirDocScrutinizer51: no idea i buyed that...
13:59.03drathirbut motherboard looks ok i switched upper slider with screen from my second n900 with broken usb port and motherboard work camera works...
14:00.08drathirmaybe soon i buy once more with broken usb and switch the upper slider with screen only...
14:01.36drathirnow i using that with broken screen for battery charging...
14:02.09drathirhave 2 batteries that switch them time to time...
14:02.22DocScrutinizer51I still don't understand if it's the main fleex cable that ripped off
14:02.59DocScrutinizer51or actually that tiny cable frm LCD to main flex inside upper half
14:07.07DocScrutinizer51you can get replacement main flex xable for a few bucks
14:11.01drathiroh thats good description the correct is tiny one from main to lcd...
14:11.21drathirsadly have no plug at end...
14:15.16drathirand main bigger connection from motherboard to inside where lcd is connected to (by thin one which is damaged not plug at end) looks ok...
14:17.23DocScrutinizer51aah. A pity
14:18.26APicB-(
14:18.26drathiryea...
14:18.54DocScrutinizer51probably somebody made plug come off the cable when trying to unplug it
14:19.36APic.o0(SOMEBODY SET UP US THE BOMB.)
14:20.03drathirdont know why lcd-s not have also plugs at bottom side which could be easy to replace if damaged, propably to expensive i guess...
14:21.18drathirDocScrutinizer51: yea for sure because when opening the scrub from screen was in back case where shorter one antenna is ;p
14:21.25DocScrutinizer51new LCD is some 25 to 49EUR
14:22.30drathirDocScrutinizer51: yea cheaper is buy damaged phone with working lcd, and improve amount of parts for exchange in future...
14:23.03DocScrutinizer51:nod:
14:23.14drathirmostly with damaged phone battery and charger included...
14:24.14drathirthat one i buy ~10-12EUR
14:25.39bencohwow, chheap
14:25.54APick
14:38.01drathirbencoh: yea that why i take it almost in blind... battery looks like new one...
14:41.39DocScrutinizer51batteries always *look* like new ;) You tell if they really *re* by doing a full charge from emty to full and then back to empty while recording the output of bq27200 60
14:42.20DocScrutinizer51~bq27200
14:42.21infobotwell, bq27k-detail is http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail2
14:46.21drathirDocScrutinizer51: thanks i goin to check...
14:47.35DocScrutinizer51use bq27200.sh, not bq27k-detail2
14:48.03drathircurently at n900 monitor show more than 1000mAh after full charhe...
14:48.12drathirok
14:48.24*** join/#maemo at1as (~at1as@216.222.83.66)
14:49.22*** join/#maemo protem (~protem@ks3100918.kimsufi.com)
14:49.22*** join/#maemo protem (~protem@unaffiliated/protem)
14:49.38*** join/#maemo sixwheeledbeast (~paul@host-92-28-79-1.as13285.net)
14:51.16DocScrutinizer51<PROTECTED>
14:51.37DocScrutinizer5116:03 4153 100  100  -12  1110 1110 1110 65535 2773  40  NOACT:0 IMIN:0 CI:0 CALIP:0 VDQ:1 EDV1:0 EDVF:0
14:58.21*** join/#maemo sixwheeledbeast1 (~paul@host-89-243-129-147.as13285.net)
14:59.06*** join/#maemo _rd (~rd@p57B49B32.dip0.t-ipconnect.de)
15:00.30drathirDocScrutinizer51: which one vaule is important?
15:01.12DocScrutinizer51NAC
15:01.51drathirlol show 0 ;p
15:01.54DocScrutinizer51which is plain charge in mAh now metered to have gone into cell
15:02.10drathiroh when connected...
15:02.47drathirneed to first end reflashing and enable sshd usbip and wlan connection...
15:02.48DocScrutinizer51it's an incremental integrating value
15:04.58DocScrutinizer51after swapping battery it will start at bogus value. then you discharge cell complely and then charge it. BQ27200 chip will integrate the charge going into cell during charge and showing it as NAC
15:05.40drathirhttp://pastebin.com/NiqBCqt5
15:05.49DocScrutinizer51so during charging empty cell NAC goes up from 0 to ideally 1300
15:06.25drathirthanks i check great script btw...
15:07.57DocScrutinizer51I'm running bq27200.sh 60 | tee batlog.txt
15:24.40drathirDocScrutinizer51: thanks logging..
15:37.26drathirwonder need to switch the working screen when perform to flashing device?
15:38.39DocScrutinizer51actually after completing charging it tells you the amount that went *into* the cell during charging. But the really interesting value is the difference of this value minus the last value it reads before it shuts down on DIScharge. NAC will count down from e.g. 1266 during discharge but may shut down when NAC claims there were 200 left over. So true discharge capacity of cell is 1266-200=1066
15:41.42DocScrutinizer51a valid discharge cycle (VDQ=1) will ake bq27200 chip *learn* this value of 1066 as new real max capacity of cell
15:45.18drathiroh... in that case is possible that chip have incorrect data and not charging the battery to full?
15:47.05ShadowJKNo it doesn't control charging
15:47.22drathirShadowJK: thats good...
15:47.47*** join/#maemo cpt_nemo (cpt_nemo@rfc1459.de)
16:03.36*** join/#maemo SAiF (~SAiF@117.217.137.229)
16:34.44kerioDocScrutinizer51: you paid for this!
16:35.07DocScrutinizer51huh?
16:35.41keriothat message, and this one too
16:37.26keriodrathir: when doc says "integrate" he means "sum"
16:46.05drathirkerio: thanks...
16:47.07drathirnow waitin to full charge battery and perform flash-ing n900 that one with broken screen...
16:49.16drathirbut guess is too old RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin
16:49.42*** join/#maemo javispedro (~javier@Maemo/community/contributor/javispedro)
16:50.24drathirand that one too RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin
16:52.47DocScrutinizer51both looks good to me
16:53.11DocScrutinizer51without betting my ass on me being right
16:53.51DocScrutinizer5136-2 is PR1.3
16:53.59DocScrutinizer51good enough
16:54.47DocScrutinizer5113-2VANILLA prolly also OK, as new as it gets
16:57.53drathirO.o im was almost sure that much newest available because of date 14.11.2012... but looks im bad thinking...
16:59.30drathirand yes if good remember its PR1.3
17:01.09drathirneed only refresh procedure and which one keys to press...
17:03.23*** join/#maemo BCMM (~BCMM@unaffiliated/bcmm)
17:12.59DocScrutinizer51~flashing
17:13.00infobotrumour has it, maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware
17:15.50DocScrutinizer51in short: BLACKLIST the phonet* crap on your PC! Start flasher for COMBINED. Only then plug in the N900 with battery removed. Insert battery. Watch flashing to start. Wait for flashing process to complete. Unplug and remove battery.
17:15.56*** join/#maemo at1as (~at1as@216.222.83.66)
17:16.00DocScrutinizer51Redo for VANILLA
17:16.18DocScrutinizer51Then *again* for COMBINED
17:17.01keriocan 0xFFFF flash everything? or are we still tied to the closed-source flasher to flash VANILLA?
17:17.50DocScrutinizer510xFFFF *can* flash everything afaik
17:18.13DocScrutinizer51ask Pali
17:18.46Pali0xFFFF cannot flash eMMC
17:18.53bencohhmm
17:19.30Palifor eMMC flashing is used Mk II protocol and it is not implemented
17:19.35Palisome info is in doc/
17:19.45Palianybody has time for it? :-)
17:19.57keriomh
17:20.00keriodo we even need that?
17:20.18kerioPali: can it boot from ram?
17:20.27Pali0xFFFF? yes
17:20.45keriowell then it's more than enough
17:21.10Paliyes, you can create kernel+init image ready for flashing via standard usb mass storage interface
17:25.33*** join/#maemo nox- (noident@freebsd/developer/nox)
17:28.44kerioyeah, just load rescueOS and then restore a BM backup or something like htat
17:28.44keriothat
17:33.43DocScrutinizer51actually that's pretty much exactly what flasher mk II protocol does as well
17:34.20DocScrutinizer51aiui
17:35.30DocScrutinizer51just it uses the existing rootfs OS on target, that's why you need a semi-decent rootfs aka COMBINED to flash VANILLA
17:37.17*** join/#maemo bluelupo (~quassel@2a02:810d:1600:7f0:e2cb:4eff:fe8b:b2f1)
17:45.39DocScrutinizer51actually 'flashing' vanilla only means: partition and format the eMMC, then copy a few files to /home and to MyDocs
17:51.46kerioyeah yeah
17:52.01keriodoes it even copy files to /home?
17:52.06kerioi thought it was done during firstboot
17:55.27DocScrutinizer51prolly
17:55.51DocScrutinizer51I'm not sure
17:56.13DocScrutinizer51it*could* copy files to /home
17:58.43Palidir /opt is some symlink to /home
17:59.02Paliand it /home/user is created at boot time if does not exists
17:59.29Paliand stock rootfs has some script which will rm -rf opt && optify
17:59.47Paliand that script is run only once (store some info if was started or not)
18:00.38Paliflashing eMMC should call mkfs on /home partition and equivalanet of dd if=mmc_image of=/dev/...
18:01.10Paliso if /opt (/home) FS is damaged (because of FS errors), flashing only rootfs does not help
18:02.04Pali(any idea how to write regular IRC message to channel which starting with slash?)
18:03.18Humpelstilzchentry /say /opt
18:03.32Humpelstilzchenif irssi
18:03.36Pali/opt
18:03.42Palinice :-)
18:03.54Palithx
18:05.14drathirDocScrutinizer51: thanks a lot
18:05.19nox-some clients also understand // or \/
18:07.01DocScrutinizer51or use double/
18:07.12DocScrutinizer51/like this
18:07.24Pali/test
18:07.29Pali\/test
18:07.33DocScrutinizer51actually I typed //like this
18:07.42Paliright //test working too
18:08.09DocScrutinizer51or simply us leading space
18:09.12DocScrutinizer51Pali: for sure no dd if=sth of=/dev/... is used
18:10.02DocScrutinizer51rather some tar -x
18:10.30*** join/#maemo arcean (~arcean@aaen16.neoplus.adsl.tpnet.pl)
18:21.44drathirif nokia sound able to hear flashing sucessfull?
18:25.17drathiror space before /
18:26.15DocScrutinizer51sorry?
18:27.33drathirw/o  screen replace not able to check if flashed successfully... hrhr
18:27.51drathirbut flasher end w/o problems...
18:31.39drathiri guess no possibility to connect from linux w/o screen replace ;p
18:32.31bencohI guess you could load rescueos and edit your rootfs to enable usb0 on boot
18:33.07DocScrutinizer51yes
18:33.41drathir~rescueos
18:33.41infobotsomebody said rescueos was http://n900.quitesimple.org/rescueOS/
18:34.47DocScrutinizer51shift+ctrl+X gives you a shell aka xterm
18:35.00DocScrutinizer51you could type blindly there
18:35.05bencohbtw do you guys really use osso-xterm ?
18:35.38DocScrutinizer51sure, what else?
18:36.02bencohI settled for ("real") xterm
18:43.14DocScrutinizer51hmm, I prolly never even tested that
18:49.22bencohit's faster than libvte (gnome implementation, used in osso-xterm) ... really noticeable with curses applications (hello irssi over ssh), and huge impact when scrolling, especially with "small" fonts
18:50.08bencoh(libvte is not the only one to blame, freetype has its part in this ... and xterm can use fixed fonts without freetype)
18:57.11*** join/#maemo Kabouik (~quassel@221.77.69.86.rev.sfr.net)
18:59.28*** join/#maemo falk1 (~falk@kilbeggan.fourecks.de)
19:03.38*** join/#maemo falk1 (~falk@kilbeggan.fourecks.de)
19:14.42*** join/#maemo totalizator (~totalizat@89-69-49-198.dynamic.chello.pl)
19:17.16*** join/#maemo cpt_nemo (cpt_nemo@rfc1459.de)
19:18.04*** join/#maemo erlehmann (~erlehmann@82.113.99.35)
19:29.30drathirok looks like also gsm damaged...
19:30.50*** join/#maemo cpt_nemo (cpt_nemo@rfc1459.de)
19:32.44PaliDocScrutinizer51: no, fiasco emmc image contains *raw* fat32 fs dump and that is imaged directly as MyDocs
19:33.05Palino tar is used
19:33.12Palithis is reason why mmc image is too big
19:33.22Paliit is not compressed and contains empty fat blocks....
19:35.17DocScrutinizer51Pali: then resizing partitions by imply editing numeric size in vanilla image would be a terribly bad idea, nevertheless it allegedly works
19:36.40DocScrutinizer51also when you want to do a raw fat32 data transfer then you invariably of used size of data need to dd the size of whole 28GB of volume
19:37.34DocScrutinizer51which wouldn't make *any* sense
19:39.34DocScrutinizer51maybe you could dd a complete fat32 volume of only 500MB size and then resize it with some parted tool
19:44.24*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
19:44.43DocScrutinizer51anyway afaik flashing vanilla is mostly cruft spamming your mydocs with useless 'content', except of the partitioning and mkfs which you could do without any vanilla image as well
19:46.11DocScrutinizer51so discussing how that cruft content gets stored in vanilla imae and how it's written to eMMC is maybe just of academic interest
19:48.53Palithat is part of mk II protocol
19:48.53DocScrutinizer51the partitioning and mkfs is clearly the more useful part of this 'flashing' procedure and it would help a lot to come up with an alternative to using flasher and flashing vanilla to get this established
19:49.08Palisome info how cfdisk and mkfs is called
19:49.16Paliplus dump of image which is dd-ed
19:49.22DocScrutinizer51exactly
19:49.25Palithis is in mmc fiasco image
19:53.36DocScrutinizer51I guess mkII is putting maemo into some single-user mode (init 1 or init s) and then transfers a few cli commads to it, to make cfdisk and mhfs of maemo do their job on eMMC
19:58.12Paliit is packet orientated protocol it support transfering commands and data...
19:58.28Palilook at 0xFFFF doc/ dir
19:59.06Paliand that protocol is used via usb (for normal flashing) and also via TCP for local on device flashing
19:59.29Paliyou have "flasher" command on n900
19:59.35Paliused with param --local
19:59.48Palibut it use TCP connection to localhost
19:59.57Paliand not using raw /dev/... access
20:00.11Paliserver is called softupd (which listening on usb and on localhost port)
20:00.39*** join/#maemo LauRoman|Laptop (~LauRoman@5-14-57-68.residential.rdsnet.ro)
20:01.48*** join/#maemo LauRoman (~LauRoman@5-14-57-68.residential.rdsnet.ro)
20:02.47*** join/#maemo Venusaur (~wdwrwf@wikipedia/Antonio-Lopez)
20:05.13*** join/#maemo Venusaur (~wdwrwf@wikipedia/Antonio-Lopez)
20:10.16*** join/#maemo pdz (~paul@c-67-169-80-116.hsd1.ca.comcast.net)
20:12.28*** join/#maemo BCMM (~BCMM@unaffiliated/bcmm)
20:14.27*** join/#maemo LauRoman (~LauRoman@5-14-57-68.residential.rdsnet.ro)
20:14.56*** join/#maemo LauRoman|Laptop (~LauRoman@5-14-57-68.residential.rdsnet.ro)
20:16.13keriolibvte is fucking pathetic
20:16.48kerioit violates the basic principle of terminal control codes
20:16.52keriowhich is "ignore shit you don't know of"
20:26.45drathirwhat is the easiest way to gain root access?
20:26.45*** join/#maemo sixwheeledbeast1 (~paul@host-89-243-140-229.as13285.net)
20:26.59drathir~cssu
20:26.59infobot[cssu] http://wiki.maemo.org/Community_SSU
20:27.09drathir~root
20:27.09infobot[root] not a Good Thing to use when using IRC. Please use a different account.
20:27.42drathirwifi working...
20:28.01*** join/#maemo _LauRoman (~LauRoman@5-14-57-68.residential.rdsnet.ro)
20:33.38bef0rd~rootsh
20:33.38infobotwell, rootsh is an easy way to get root and it's found here: http://maemo.org/downloads/product/OS2008/rootsh/, or http://maemo.org/downloads/product/Maemo5/rootsh/, or <ShadowJK> rootsh gives you "sudo gainroot", to get root privs but user environment (similar as "su"), and "root", which gives you root privs root env (similar to "su -")
20:33.52keriorootsh is fucking awful
20:34.07bef0rdcan't remember the name of the alternative
20:34.13kerioopenssh
20:39.03drathirfrom fast checking camera working, memory working...
20:39.17drathirbef0rd: thanks...
20:39.30drathirkerio: installed
20:39.35keriowhat
20:39.45keriooh, openssh
20:39.46keriowell now you have root
20:39.49keriossh root@localhost
20:40.04kerioand then add a file in /etc/sudoers.d/ and update-sudoers
20:40.11*** join/#maemo pdz (~paul@c-67-169-80-116.hsd1.ca.comcast.net)
20:41.32*** join/#maemo _LauRoman (~LauRoman@5-14-57-68.residential.rdsnet.ro)
20:42.41sixwheeledbeast1well it's better than sudser...
20:42.52DocScrutinizer51please forget about that!
20:43.03kerioplease forget about rootsh as well!
20:43.46drathirkerio: thanks a lot openssh looks like little better idea... no offence bef0rd ofc...
20:43.48DocScrutinizer51about both manual adding of files to sudoers and particularly sudser which needs to get killed with fire
20:43.57keriohuh
20:44.09kerioyou're *supposed* to add stuff to /etc/sudoers.d/ and then call update-sudoers
20:44.19kerioany changes to /etc/sudoers will be reset on the first call to update-sudoers
20:44.27DocScrutinizer51no, you're not
20:44.44DocScrutinizer51unless you're  developer or admin
20:44.53DocScrutinizer51drathir is neither
20:44.57keriomh
20:45.21drathirDocScrutinizer51: in previous i have too root access...
20:45.36DocScrutinizer51and he's dealimg with a device with broken screen
20:45.53keriodrathir: i think he means "admin" in a more general sense
20:45.58drathirneed chroot to archlinux arm installation at sd too...
20:46.01kerioas in "some dude who knows how to unix"
20:46.09DocScrutinizer51drathir: opessh gives you root access
20:47.01drathirDocScrutinizer51: yes ofc i using openssh...
20:49.11*** join/#maemo bugzy (~bugzy@99-191-138-94.lightspeed.irvnca.sbcglobal.net)
21:06.04*** join/#maemo astr (~astr@79-69-201-52.dynamic.dsl.as9105.com)
21:08.05*** join/#maemo pdz (~paul@c-67-169-80-116.hsd1.ca.comcast.net)
21:12.33*** join/#maemo javispedro (~javier@Maemo/community/contributor/javispedro)
21:22.04*** join/#maemo flynx (~flynx@70-139-50-84.lightspeed.hstntx.sbcglobal.net)
21:27.37*** join/#maemo Mr_Stupid (~Marshall_@x2f2e158.dyn.telefonica.de)
21:33.22drathirgoin to install cssu...
21:42.04drathir50.5M nice update... a lot of things fixed...
21:55.18*** join/#maemo astr (~astr@79-69-206-241.dynamic.dsl.as9105.com)
22:15.00*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
22:28.00astrhows the neo900 doing? i'm hoping some easy funds might become available within a year for buying one :D
22:32.23sixwheeledbeastneo900.org or #neo900
22:37.40*** join/#maemo erlehmann (~erlehmann@82.113.99.35)
22:38.21astrarr thanks
22:39.28drathirLinux Nokia-N900 2.6.28-omap1 #1 PREEMPT Fri Aug 6 11:50:00 EEST 2010 armv7l unknown
22:40.15drathirVersion: 21.2011.38-1Tmaemo9.1
22:58.26bencoh:)
23:06.25*** join/#maemo erlehmann (~erlehmann@82.113.99.35)
23:07.23*** join/#maemo erlehmann (~erlehmann@82.113.99.35)
23:34.11*** join/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de)
23:34.59*** part/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de)
23:35.34*** join/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de)
23:43.27*** join/#maemo e27182 (~quassel@p4FD370D2.dip0.t-ipconnect.de)

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