IRC log for #maemo on 20140504

00:09.00*** join/#maemo LjL-Laplet (~ljl@93-32-49-69.ip32.fastwebnet.it)
00:27.23*** join/#maemo bugzy (~bugzy@29palms119.chapman.edu)
00:57.56*** join/#maemo felipe` (~felipe@unaffiliated/felipe)
01:01.05*** join/#maemo _jester_ (~user@host-168-net-119-160-119.mobilinkinfinity.net.pk)
01:01.14_jester_hello world
01:01.23_jester_anyone alive ?
01:02.07_jester_cause i was seriously thinking of starting development on the platform but the sdk links to the nokia site are all dead
01:02.28_jester_so only wondering where i could get the files from
01:06.56bef0rd~vm
01:06.56infobotEmacs-based mail reader. URL: http://www.wonderworks.com/vm/
01:07.02bef0rd~maemo-vm
01:07.10bef0rd~maemo-sdk
01:07.10infobotfrom memory, maemo-sdk is the development environment for the Nokia Internet Tablets, found here: http://maemo.org/development/
01:07.15bef0rd~maemo-sdk-vm
01:07.22Maxdamantushttp://maemo.merlin1991.at/files/SB
01:08.05Maxdamantus(the VM image)
01:08.22bef0rd_jester_: there is a vm image, the one that linked Maxdamantus
01:08.45Luke-Jr_jester_: that's because this platform is long dead
01:09.11*** join/#maemo rosseaux (~BeRo@228.66.238.89.in-addr.arpa.manitu.net)
01:14.30*** join/#maemo rosseaux (~BeRo@228.66.238.89.in-addr.arpa.manitu.net)
01:18.03*** join/#maemo kolp (~quassel@55d45cb9.access.ecotel.net)
01:23.48*** join/#maemo protem (~protem@ks3100918.kimsufi.com)
01:23.48*** join/#maemo protem (~protem@unaffiliated/protem)
01:31.49*** join/#maemo valeriusL (~valerius@85.26.180.142)
01:37.12_jester_thanks
01:39.42_jester_well, i wont call it dead, some of its applications just need an upgrade
01:40.39_jester_if i had the environment set up, id probably update a few of em or make new ones
01:54.02*** join/#maemo bugzy (~bugzy@29palms126.chapman.edu)
01:56.44*** join/#maemo uen| (~uen@p50843793.dip0.t-ipconnect.de)
01:59.01*** join/#maemo mschlens (~mschlens@p5DC16326.dip0.t-ipconnect.de)
02:02.10*** join/#maemo silviof2 (~silviof@ppp-82-135-91-243.dynamic.mnet-online.de)
02:04.11*** join/#maemo LauRoman (~LauRoman@5-14-195-26.residential.rdsnet.ro)
02:07.41*** join/#maemo Luke-Jr (~luke-jr@gateway/tor-sasl/luke-jr)
02:11.51*** join/#maemo amizraa (~amizraa@gateway/tor-sasl/amizraa)
02:52.11DocScrutinizer05<PROTECTED>
02:54.55DocScrutinizer05~scratchbox
02:54.56infobotextra, extra, read all about it, scratchbox is a cross-compiling system that uses binfmt_misc, rpc calls, and an nfs mount to make a cross-build appear to be 100% native, and is found at http://www.scratchbox.org/, hosted by maemo now. Also at http://maemo.merlin1991.at/files/SB
02:55.44*** mode/#maemo [+o DocScrutinizer05] by ChanServ
02:57.29*** topic/#maemo by DocScrutinizer05 -> Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~combined ~emmc ~flasher sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet
02:58.06*** mode/#maemo [-o DocScrutinizer05] by ChanServ
02:58.09DocScrutinizer05~sb
02:58.09infobothmm... scratchbox is a cross-compiling system that uses binfmt_misc, rpc calls, and an nfs mount to make a cross-build appear to be 100% native, and is found at http://www.scratchbox.org/, hosted by maemo now. Also at http://maemo.merlin1991.at/files/SB
03:13.36*** join/#maemo SAiF (7aa6417e@gateway/web/freenode/ip.122.166.65.126)
03:20.35*** join/#maemo Gh0sty (~ghosty@fosdem/staff/gh0sty)
03:31.11*** join/#maemo maybeArgh (~cl@p5B162F3E.dip0.t-ipconnect.de)
03:47.20*** join/#maemo erlehmann (~erlehmann@89.204.130.189)
04:51.01*** join/#maemo Luke-Jr (~luke-jr@gateway/tor-sasl/luke-jr)
05:44.12*** join/#maemo janemba (~101@unaffiliated/janemba)
05:47.39*** join/#maemo jmlich (~jmlich@ip-94-112-168-157.net.upcbroadband.cz)
05:48.20*** join/#maemo b1101 (~b@216.155.131.71)
06:02.50*** join/#maemo lbt (~david@78-32-229-233.static.enta.net)
06:02.50*** join/#maemo lbt (~david@Maemo/community/contributor/lbt)
06:05.01*** join/#maemo silviof (~silviof@unaffiliated/silviof)
06:13.31*** join/#maemo eMHa (~mh@2a02:8071:2e81:c500:d6be:d9ff:fe2b:f21b)
06:24.56*** join/#maemo remarc (~sequantz@194.11.24.44)
07:07.10*** join/#maemo uros1 (~uros@ubuntu/member/uros1)
07:33.08*** join/#maemo totalizator (~totalizat@89-69-49-198.dynamic.chello.pl)
07:50.52*** join/#maemo mp_ (~mp@87-205-249-198.adsl.inetia.pl)
07:59.26*** join/#maemo wotan147 (~max@HSI-KBW-109-193-012-252.hsi7.kabel-badenwuerttemberg.de)
08:01.23*** join/#maemo cpt_nemo (cpt_nemo@rfc1459.de)
08:05.50*** join/#maemo amizraa4 (~amizraa@gateway/tor-sasl/amizraa)
08:13.31*** join/#maemo fortytwo_ (~thomas@who.let.this.bloody.dropbear.in)
08:17.16*** join/#maemo till- (till@vispillo.org)
08:30.22*** join/#maemo Guest22253 (~rd@p5088F6B9.dip0.t-ipconnect.de)
08:31.27*** join/#maemo janemba (~101@unaffiliated/janemba)
08:36.24*** join/#maemo janemba (~101@unaffiliated/janemba)
08:50.02*** join/#maemo janemba (~101@unaffiliated/janemba)
08:55.22*** join/#maemo uros1 (~uros@ubuntu/member/uros1)
08:59.38*** join/#maemo janemba (~101@unaffiliated/janemba)
08:59.49*** join/#maemo Venemo (~venemo@fedora/Venemo)
09:28.46*** join/#maemo Guest22253 (~rd@p5088F6B9.dip0.t-ipconnect.de)
09:30.55*** join/#maemo e2718 (~hdesk@p54849946.dip0.t-ipconnect.de)
09:36.19*** join/#maemo pdz (~paul@c-67-169-80-116.hsd1.ca.comcast.net)
09:36.28*** join/#maemo eMHa (~mh@2a02:8071:2e81:c500:d6be:d9ff:fe2b:f21b)
09:46.02*** join/#maemo vdv (~vdv@f051136143.adsl.alicedsl.de)
09:46.08vdvhi all
09:47.10vdvhave a problem with my old n900, display is turning off/on randomly, any idea if that is hardware or software problem?
09:47.47vdvgoogled a lot, found no one with such problem
09:49.58vdvhow can deactivate lock button on the right side of n900?
09:51.54*** join/#maemo eMHa_ (~mh@2a02:8071:2e81:c500:d6be:d9ff:fe2b:f21b)
09:53.19*** join/#maemo uros1 (~uros@ubuntu/member/uros1)
09:56.19*** join/#maemo eMHa__ (~mh@2a02:8071:2e81:c500:d6be:d9ff:fe2b:f21b)
10:00.04*** join/#maemo janemba (~101@unaffiliated/janemba)
10:00.10vdvmaybe it's proximity sensor failure?
10:00.56DocScrutinizer05did you reflash?
10:02.27DocScrutinizer05please cover up upper left (portrait) corner of screen
10:03.06DocScrutinizer05screen backlight is supposed to shut down at very high ambient light
10:03.41DocScrutinizer05probe for ambient light is done every maybe 10s
10:03.59DocScrutinizer05ALS sensor is upper left corner
10:06.03*** join/#maemo Guest22253 (~rd@p5088F6B9.dip0.t-ipconnect.de)
10:12.43*** join/#maemo janemba (~101@unaffiliated/janemba)
10:13.53DocScrutinizer05proximity shouldn't dim screen except when on phonecall
10:14.28DocScrutinizer05but there are apps to do that nevertheless. That's why I asked if you did a reflash
10:21.37*** join/#maemo T_X (~T_X@unaffiliated/t-x/x-1456208)
10:23.12vdvDocScrutinizer05, i did reflash two or three years ago
10:23.24vdvto get latest official release
10:23.44*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
10:23.52vdvdidn't expriment with device last two years
10:28.31*** join/#maemo valeriusL (~valerius@85.26.180.132)
10:36.43DocScrutinizer05when screen goes "dark" is it only the backlight or also the complete content of LCD vanishing?
10:36.58vdvcomplete content
10:37.03DocScrutinizer05or maybe even only LCD goes black but backlight stays on?
10:37.16vdvnope
10:37.23vdvkeyboard is turn off too
10:37.26DocScrutinizer05the latter only visible in the dark
10:37.39vdvDocScrutinizer05, noticed, that issue first appeared after some small square and black piece fall from the back of the device
10:37.46DocScrutinizer05the former only visible in bright daylight
10:38.00DocScrutinizer05o.O
10:38.02vdvback cover was opened
10:38.04vdv))
10:38.19vdvit was approx 3mmx3mm square
10:38.32DocScrutinizer05a black square on screen?
10:38.36vdvnope
10:38.42DocScrutinizer05sharp edges?
10:38.45vdvunder the back cover
10:38.51vdvplastic
10:38.56DocScrutinizer05sorry?
10:39.53vdvi don't know how to name it )
10:40.34vdvwhere battery located
10:40.58vdvi opened cover to change sim
10:41.07vdvwanted to close again
10:41.10DocScrutinizer05lemme re-read what you posted
10:41.36DocScrutinizer05oooh
10:41.53DocScrutinizer05dang!
10:42.02vdvsmall square piece from plastic, approx 3mmx3mm
10:42.10vdvmaybe little bigger
10:42.28vdvsuppose it was covering some sensor or so
10:42.48DocScrutinizer05with a few silver dots on one side and a ying&yang alike line on the other?
10:43.15vdvnope, it was pure plastic, no parts from the inside )
10:43.24DocScrutinizer05errr
10:43.30DocScrutinizer05weird
10:44.27vdvi don't know maybe it doesn't influence issue with display
10:44.33DocScrutinizer05any such plastic for all I can imagine is completely unrelated to display light. Unless it's been the slider magnet
10:44.47vdvjust coincidence
10:44.52DocScrutinizer05but that ould hardly fall out of backside of phone
10:44.58DocScrutinizer05would*
10:45.01vdvright
10:45.12DocScrutinizer05is your slider properly detected
10:45.15DocScrutinizer05?
10:45.35vdvyes, display turns on/unlocks when opened
10:45.42DocScrutinizer05ok
10:45.44vdvand off when closed
10:45.45torindelmost probably he broke one of holding clips from backcover
10:45.55DocScrutinizer05aaah possibly
10:46.00vdvyes
10:46.04vdvthink so
10:46.21DocScrutinizer05there's one such thing at camera end of back cover
10:46.44vdvanother hypothesis is lock switch is broken
10:46.50vdvon the right side
10:47.01DocScrutinizer05hmm, can't see that
10:47.14vdvand triggers on/off spontaneously
10:47.23DocScrutinizer05well, *maybe*
10:47.50DocScrutinizer05but that would be quite weird a failure pattern
10:48.04vdvis it possible to turn it off on the software side?
10:48.16vdvdisable it
10:48.30DocScrutinizer05err, in theory for sure
10:48.52DocScrutinizer05hey, I know: do a `stop mce`
10:49.08vdvand?
10:49.38DocScrutinizer05and see what happens
10:50.21DocScrutinizer05it reliably stops most of all ways to dim screen
10:50.36vdvi see
10:50.41vdvi'll try
10:50.41DocScrutinizer05no more lockslider button, no more timeout, no ALS
10:50.50DocScrutinizer05screen should stay on
10:50.53vdvbad news are, that issue is not such easy to reproduce by intention
10:50.56DocScrutinizer05you need root
10:51.15vdvi.e. i cannot trigger it
10:51.16DocScrutinizer05ooh
10:51.22DocScrutinizer05that's bad
10:51.29vdvnot easy to test
10:51.45vdvsometimes i think that it's gone
10:51.47DocScrutinizer05tbh I suspect flex breakage
10:52.07vdvbut next day i find device discharged in case
10:52.22vdvbecause of display was on whole day
10:52.36DocScrutinizer05oooh, yes. when it's locked it for sure mustn't  unlock
10:52.58DocScrutinizer05unless some shitty app for proximity sensor got installed
10:53.13DocScrutinizer05I suggest reflash
10:53.45vdvwould be time kill if it's a hardware problem
10:54.12vdvi'll try first with deactivating mce
10:55.08*** join/#maemo erlehmann (~erlehmann@89.204.130.189)
10:58.16vdvDocScrutinizer05, power button is also not working with stopped mce ))
10:58.37bencohseems reasonable
10:59.36vdvif it would work, then my problem could be considered as solved
11:00.19vdvhow can disable automatic display turn off? in settings it's possible only set maximum timeout of 2 minutes
11:03.32vdvlock switch is very sensitive
11:03.45vdvi don't have to slide it maximum to lock/unlock
11:04.13vdvjust small shift triggers lock
11:05.28vdvDocScrutinizer05, if i post dpkg -l somewhere can you take a look at it? maybe some obscure app indeed "plays" with display
11:08.33*** join/#maemo uros1 (~uros@ubuntu/member/uros1)
11:09.16vdvjust in case: http://pastebin.com/XyEHRtW3
11:09.57DocScrutinizer05vdv: your lockslider switch is defect, disassemble and check!
11:11.55vdvDocScrutinizer05, could be defect in such a way, that it's triggered even if i don't touch it?
11:12.52vdvbecause sometimes display turns off/on if device is on table and i don't even touch it
11:13.07vdvand also no calls, no usb connection
11:16.35*** join/#maemo hxka (~hxka@95-28-228-189.broadband.corbina.ru)
11:19.40*** join/#maemo Guest37296 (~FIQ@fiq.se)
11:22.19*** join/#maemo xes (~xes@unaffiliated/xes)
11:27.30*** join/#maemo okias (~okias@berger.cust.centro-net.cz)
11:28.07DocScrutinizer05check your syslog (install it when you didn't yet) - it logs all lockslider events on kernel level
11:28.50vdvmakes sense, thanks
11:29.04DocScrutinizer05Apr  9 01:24:39 IroN900 kernel: [    3.100524] kb_lock (GPIO 113) is now open
11:29.38DocScrutinizer05Apr  9 01:26:06 IroN900 kernel: [   93.730346] kb_lock (GPIO 113) is now open
11:29.39DocScrutinizer05Apr  9 01:26:11 IroN900 kernel: [   98.910156] kb_lock (GPIO 113) is now closed
11:29.58vdvi see
11:29.58DocScrutinizer05sorry
11:30.01vdvthanks
11:30.07DocScrutinizer05Apr  9 01:44:35 IroN900 kernel: [ 1203.050720] kb_lock (GPIO 113) is now closed
11:30.09DocScrutinizer05Apr  9 01:44:35 IroN900 kernel: [ 1203.292877] kb_lock (GPIO 113) is now open
11:31.23DocScrutinizer05Apr  9 01:51:59 IroN900 kernel: [ 1646.628936] kb_lock (GPIO 113) is now closed
11:31.25DocScrutinizer05Apr  9 01:51:59 IroN900 systemui-tklock[1226]: Method call received from: :1.10, iface: com.nokia.system_ui.request, method: tklock_open
11:31.26DocScrutinizer05Apr  9 01:51:59 IroN900 kernel: [ 1647.089752] kb_lock (GPIO 113) is now open
11:33.29*** join/#maemo janemba (~101@unaffiliated/janemba)
11:34.08DocScrutinizer05http://privatepaste.com/1c4727f130
11:46.07*** join/#maemo janemba (~101@unaffiliated/janemba)
11:48.40DocScrutinizer05actually a slightly more comprehensive view of stop mce; start mce with a number of lockslider events: http://privatepaste.com/b38e022d6b
11:49.12DocScrutinizer05blocking lockslider on kernel level is also possible, but not exactly trivial
11:49.52DocScrutinizer05sth along echo foo >/sys/*/*/buttons/113/*/*
11:54.57DocScrutinizer05less '+F' /var/log/syslog   is fun
12:05.08vdvDocScrutinizer05, does value written in /sys/*/*/buttons/113/*/* also persisted?
12:05.26vdvi.e. will not disappear after restart
12:06.54vdvDocScrutinizer05, "start mce with a number of lockslider events" <-- what do you mean?
12:07.14*** join/#maemo XenonXZ (~rich@client-86-23-127-25.brhm.adsl.virginm.net)
12:07.14vdvthere's only log in paste
12:07.30vdvno commands to start mce with a number of lockslider events
12:08.09DocScrutinizer05http://maemo.cloud-7.de/share-service/20140504_003.jpg http://maemo.cloud-7.de/share-service/20140504_004.jpg  http://maemo.cloud-7.de/share-service/20140504_005.jpg lockslider switch
12:08.43DocScrutinizer05there's stop mce, a number of lockslider events, and start mce event in log
12:09.22vdvah, ok
12:10.20DocScrutinizer05((does value written in /sys/*/*/buttons/113/*/* also persisted?)) no
12:10.35vdvis it possible that lockslider oscillate if i even don't touch device?
12:11.12DocScrutinizer05yes, I see this every few days with a mechanical movement detector in a remote-control
12:12.01vdvok
12:12.34DocScrutinizer05suddenly it activates button backlight even while sitting calmly on the shelf. For sure a walking in the room suffices to trigger it then, when it got that hypernervous state
12:13.02DocScrutinizer05when the spring in the switch is broken, it will behave exactly similar
12:13.56DocScrutinizer05in the photos you see a triangle notch which gets pushed down by slider motion from right to left
12:14.28DocScrutinizer05err left to right, sorry
12:15.52DocScrutinizer05it must have a noticable spring loaded force when you operate it by sliding your nail from left to right over it. And it has a audible ping tone when it gets released and snaps up again
12:20.08*** join/#maemo XenonXZ (~rich@client-86-23-127-25.brhm.adsl.virginm.net)
12:20.48vdvi see
12:21.19*** join/#maemo dos1 (~dos@unaffiliated/dos1)
12:28.03DocScrutinizer05you can probbaly trigger the problem by slightly knocking the device backside under the lockslider, while holding device with screen facing upward
12:28.35DocScrutinizer05you should definitely install and check syslog
12:31.57*** join/#maemo LjL-Laplet (~ljl@93-32-49-69.ip32.fastwebnet.it)
12:34.33*** join/#maemo Guest22253 (~rd@p5088F6B9.dip0.t-ipconnect.de)
12:38.51*** join/#maemo BCMM (~BCMM@unaffiliated/bcmm)
12:42.19vdvDocScrutinizer05, thanks a lot, i'll definitely debug with syslog
12:44.19*** join/#maemo emma (~em@unaffiliated/emma)
12:49.57*** join/#maemo at1as (~at1as@kurios.r4780y.com)
12:51.38DocScrutinizer05yw
12:55.58*** join/#maemo r00t^home (~r00t@port-92-196-49-241.dynamic.qsc.de)
12:56.35vdvDocScrutinizer05, display turns on, but syslog says: ".. is now closed"
12:56.55DocScrutinizer05sorry?
12:57.37vdvi monitoring now with tail -f /var/log/syslog
12:57.48DocScrutinizer05kb_lock (GPIO 113) is now closed -> the slider is engaged
12:58.05DocScrutinizer05kb_lock (GPIO 113) is now open -> the slider switch got released again
12:58.31vdvah, then makes sense
12:59.48vdvi pressed power button two times to turn display off, put device on shelf and observed line with "... is now closed" on my terminal
13:00.08vdvlooked at my n900 and display was on
13:00.14vdvand it's still on )
13:00.42DocScrutinizer05to test lockslider it doesn't help to operate powerbutton
13:00.45vdvnow turned off, maybe because of 2 minutes setting
13:01.11vdvi see
13:02.01DocScrutinizer05engage lock slider button, watch for kb_lock (GPIO 113) is now closed. Release it and watch for kb_lock (GPIO 113) is now open
13:02.06*** join/#maemo at1as (~at1as@kurios.r4780y.com)
13:02.13DocScrutinizer05both shall show up instantly in syslog
13:02.36DocScrutinizer05see timestamps in http://privatepaste.com/1c4727f130
13:02.58DocScrutinizer05I engaged lockslider switch for 0.2 .. 1s
13:03.56DocScrutinizer05thus you always see a
13:03.58DocScrutinizer05May  4 13:56:35 IroN900 kernel: [108029.025146] kb_lock (GPIO 113) is now closed
13:04.00DocScrutinizer05May  4 13:56:36 IroN900 systemui-tklock[1239]: Method call received from: :1.1408, iface: com.nokia.system_ui.request, method: tklock_open
13:04.01DocScrutinizer05May  4 13:56:36 IroN900 kernel: [108029.329559] kb_lock (GPIO 113) is now open
13:04.05DocScrutinizer05sequence
13:04.57*** join/#maemo LauRoman (~LauRoman@5-14-195-26.residential.rdsnet.ro)
13:05.31DocScrutinizer05sometimes I'm faster than the system, so the systemui-tklock message shows up after the kb_lock (GPIO 113) is now open
13:05.42vdvthink, it's now clear, that lockslider is triggered randomly without engaging or releasing it explicitly
13:05.45DocScrutinizer05but it's triggered by the kb_lock (GPIO 113) is now closed
13:05.54DocScrutinizer05toldya
13:06.05vdvand that wakes up display
13:06.09DocScrutinizer05sure
13:06.20DocScrutinizer05your switch is broken
13:06.22*** join/#maemo LauRoman|Laptop (~LauRoman@5-14-195-26.residential.rdsnet.ro)
13:06.25vdvnow i'll try to disable it in kernel
13:06.33DocScrutinizer05good luck!
13:06.56vdvand if it works maybe put command somewhere in boot script?
13:10.47DocScrutinizer05sure
13:11.52DocScrutinizer05google searchterm /sys/bus/platform/drivers/gpio-switch/unbind
13:12.36vdvthere's no buttons node in /sys
13:14.10DocScrutinizer05there's /sys/devices/platform/gpio-switch
13:15.26vdvGPIO 0x48002110 is the CAM_B_EN signal of N900, which could change the camera to A or B.
13:15.47vdvor it's some other "gpio"
13:16.04DocScrutinizer05there's roundabout 250 GPIO on SoC
13:16.23DocScrutinizer05we're talking about GPIO113 here
13:16.43vdv))
13:16.50vdvunderstood )
13:17.12DocScrutinizer05~gpio
13:17.26DocScrutinizer05~ping
13:17.26infobot~pong
13:17.34DocScrutinizer05~wtf gpio
13:18.23DocScrutinizer05~gpio is General Purpose Input/Output (a CPU pin for universal configurable use as either input or output)
13:18.23infobotDocScrutinizer05: okay
13:19.26DocScrutinizer05infobot: no, gpio is General Purpose Input/Output (a CPU pin for universal configurable use as either input or output). A CPU (particularly SoC) has hundreds of them, usually
13:19.26infobotokay, DocScrutinizer05
13:20.42DocScrutinizer05infobot: no, gpio is General Purpose Input/Output (a CPU pin for universal configurable use as either input or output). A CPU (particularly SoC) has hundreds of them, usually. On linux, see /sys/devices/platform/gpio-switch
13:20.42infobotDocScrutinizer05: okay
13:21.34vdvthere's slide node in gpio-switch
13:21.42vdvand it has disable with value 0
13:21.50vdvmaybe set it to 1?
13:21.56*** join/#maemo Guest22253 (~rd@p5088F6B9.dip0.t-ipconnect.de)
13:21.58vdvand see what happens? )
13:22.18vdvor kb_lock
13:22.28vdvprobably kb_lock
13:23.06vdvexactly
13:23.10vdvit's kb_lock
13:23.53vdvlockslider doesn't work now
13:24.07vdvhope it'll solve my original problem
13:26.19vdvDocScrutinizer05, where should i put "echo 1 > /sys/devices/platform/gpio-switch/kb_lock/disable" now? not in rcS, right? )
13:26.45DocScrutinizer05wow!
13:26.52DocScrutinizer05echo 1>disable works?
13:27.00vdvyes
13:27.05DocScrutinizer05coolo!
13:27.18DocScrutinizer05wait
13:27.18vdvis that sarcasm? ))
13:27.23DocScrutinizer05no
13:27.27vdvok )
13:30.22*** join/#maemo FlameReaper-PC (~FR@bth-202-111.tm.net.my)
13:31.20DocScrutinizer05actually yes, I'd add it to /etc/init.d/rcS, way to the buttom, among the other echo commands you find there
13:31.56DocScrutinizer05prolly directly before "exit 0" line
13:32.44*** join/#maemo Kabouik (~quassel@123.22.95.79.rev.sfr.net)
13:33.21DocScrutinizer05I got some funny garbage heritage there:
13:33.47DocScrutinizer05echo 5 > /proc/sys/vm/page-cluster                                                                                                                                                            
13:33.48DocScrutinizer05echo 500 > /proc/sys/vm/dirty_expire_centisecs                                                                                                                                                
13:33.50DocScrutinizer05echo 4 >/sys/block/mmcblk0/queue/nr_requests || echo "ohnoes, hope it boots1"                                                                                                                
13:33.51DocScrutinizer05echo 4 >/sys/block/mmcblk1/queue/nr_requests || echo "ohnoes, hope it boots2"                                                                                                                
13:33.53DocScrutinizer05echo 65536 > /proc/sys/net/core/rmem_default                                                                                                                                                  
13:34.35DocScrutinizer05the echo "ohnoes, hope it boots1" should give you some idea about the risks involved in editing this file ;-)
13:35.30*** join/#maemo RedM (~redw@89-73-179-171.dynamic.chello.pl)
13:35.31vdv))
13:40.27*** join/#maemo troulouliou_dev (~troulouli@unaffiliated/troulouliou-dev/x-4757952)
13:41.29*** join/#maemo cyborg-one (~cyborg-on@130-0-45-238.broadband.tenet.odessa.ua)
13:48.11*** join/#maemo sixwheeledbeast (~paul@2a01:348:6:860a:9524:8873:c8fb:33e6)
13:50.44*** join/#maemo e2718 (~hdesk@p54849946.dip0.t-ipconnect.de)
13:56.24DocScrutinizer05vdv: you still alive?
13:56.51vdvyep
13:57.02DocScrutinizer05vdv: wouldn't be the first time we never again heard of somebody trying to edit initscripts ;-)
13:57.40DocScrutinizer05you already edited and booted?
13:57.51DocScrutinizer05you should get BM installed before you do
13:57.56DocScrutinizer05~bm
13:57.56infobotsomebody said backupmenu was http://talk.maemo.org/showthread.php?t=63975
13:57.56vdv)) i'm not a guru of course, but also not a newbie )
13:58.38DocScrutinizer05also recoveryOS should come in handy, just in case
13:58.49DocScrutinizer05~recoveros
13:58.54DocScrutinizer05~recoveryos
13:59.00DocScrutinizer05duh
13:59.04DocScrutinizer05~rescueos
13:59.04infobotextra, extra, read all about it, rescueos is http://n900.quitesimple.org/rescueOS/
13:59.50DocScrutinizer05for sure BM is simpler and more convenient to use
14:00.32DocScrutinizer05rescueOS is prolly smarter, using BM shell is even more smart
14:02.03vdvnever heard of both, seems rescueOS is like livecd
14:02.53vdvrescueOS must not be flashed on device in advance right?
14:03.29vdvfailed boot -> boot rescueOS -> fix -> boot normally , right?
14:05.10*** join/#maemo Anz_ (~Anz_@234.33.78.188.dynamic.jazztel.es)
14:05.14vdvand BootMenu is like lilo or grub?
14:06.51*** join/#maemo Maxdamantus (~Maxdamant@2001:470:f078::dead:beef:cafe)
14:14.50*** join/#maemo japa-fi (~jani@dsl-hkibrasgw4-50dc4f-215.dhcp.inet.fi)
14:16.58jon_yvdv: actually rescueOS can be put on-device
14:17.02jon_yvia uboot
14:17.22jon_ymy n900 has it onboard
14:29.14*** join/#maemo e2718 (~hdesk@p54849946.dip0.t-ipconnect.de)
14:31.38*** join/#maemo erlehmann (~erlehmann@89.204.130.189)
14:31.48*** join/#maemo FReaper-PC (~FR@60.51.96.84)
15:21.23*** join/#maemo Guest22253 (~rd@p5088F6B9.dip0.t-ipconnect.de)
15:36.57*** join/#maemo Guest37296 (~FIQ@prgmr/customer/fiq)
15:42.17*** join/#maemo FlameReaper-PC (~FR@60.51.96.84)
15:52.16*** join/#maemo pcfe (~pcfe@2a02:8109:a2c0:794:beee:7bff:fed9:8f1b)
15:52.21*** join/#maemo pcfe (~pcfe@redhat/pcfe)
16:21.43*** join/#maemo nox- (noident@freebsd/developer/nox)
16:23.40*** join/#maemo ddark (~ddark@5.102.198.248)
16:29.55*** join/#maemo FReaper-PC (~FR@60.51.96.84)
16:51.56*** join/#maemo mavhc (~mavhc@86.18.126.205)
16:52.02*** join/#maemo ArGGu^^ (~ArGGu^^@89.106.52.253)
17:04.14*** join/#maemo Guest22253 (~rd@p5088F6B9.dip0.t-ipconnect.de)
17:24.04*** join/#maemo japa-fi (~jani@dsl-hkibrasgw4-50dc4f-215.dhcp.inet.fi)
17:29.48*** join/#maemo SmilyOrg (Smily@BSN-61-6-138.dial-up.dsl.siol.net)
17:31.33*** join/#maemo remarc (~sequantz@194.11.24.44)
17:41.09*** join/#maemo LjL-Laplet (~ljl@unaffiliated/ljl)
17:48.22*** join/#maemo mp_ (~mp@87-205-249-198.adsl.inetia.pl)
17:49.48*** join/#maemo wotan147 (~max@HSI-KBW-109-193-012-252.hsi7.kabel-badenwuerttemberg.de)
17:55.03*** join/#maemo Guest22253 (~rd@p5088F6B9.dip0.t-ipconnect.de)
18:03.05*** join/#maemo pcfe (~pcfe@2a02:8109:a2c0:794:beee:7bff:fed9:8f1b)
18:03.10*** join/#maemo pcfe (~pcfe@redhat/pcfe)
18:06.57*** join/#maemo bef0rd (~bef0rd@unaffiliated/beford)
18:10.54*** join/#maemo pcfe (~pcfe@2a02:8109:a2c0:794:beee:7bff:fed9:8f1b)
18:10.59*** join/#maemo pcfe (~pcfe@redhat/pcfe)
18:19.23*** join/#maemo pcfe (~pcfe@2a02:8109:a2c0:794:beee:7bff:fed9:8f1b)
18:19.29*** join/#maemo pcfe (~pcfe@redhat/pcfe)
18:24.11*** join/#maemo at1as (~at1as@24-231-230-53.static.trcy.mi.charter.com)
18:34.51*** join/#maemo okias (~okias@berger.cust.centro-net.cz)
19:14.19*** join/#maemo bennis (~bennis@unaffiliated/bennis)
19:18.02*** part/#maemo bennis (~bennis@unaffiliated/bennis)
19:18.25*** join/#maemo bennis (~bennis@unaffiliated/bennis)
19:25.19*** join/#maemo Anz_ (~Anz_@234.33.78.188.dynamic.jazztel.es)
19:27.47*** join/#maemo Guest22253 (~rd@p5088F6B9.dip0.t-ipconnect.de)
19:36.10*** join/#maemo Luke-Jr (~luke-jr@gateway/tor-sasl/luke-jr)
19:46.04*** join/#maemo jmlich (~jmlich@ip-94-112-168-157.net.upcbroadband.cz)
19:50.39*** join/#maemo erlehmann (~erlehmann@89.204.130.189)
20:08.35*** join/#maemo shentey (~shentey@f052237137.adsl.alicedsl.de)
20:10.54*** join/#maemo _rd (~rd@p57B49111.dip0.t-ipconnect.de)
20:11.32*** join/#maemo shentey (~shentey@f052237137.adsl.alicedsl.de)
20:24.26*** join/#maemo goldkatze (~nobody@unaffiliated/goldkatze)
20:39.13*** join/#maemo xes (~xes@unaffiliated/xes)
20:40.15*** join/#maemo valeriusL (~valerius@85.26.180.161)
20:46.14*** join/#maemo M4rtinK (~M4rtinK@ip-78-102-146-131.net.upcbroadband.cz)
20:48.40*** join/#maemo remarc_ (~sequantz@194.11.24.44)
20:58.06*** join/#maemo Luke-Jr (~luke-jr@gateway/tor-sasl/luke-jr)
21:06.03*** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr)
21:07.20*** join/#maemo mp_ (~mp@87-205-249-198.adsl.inetia.pl)
21:31.28*** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr)
21:40.22*** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr)
21:44.26Luke-Jrhow can I use WPA2 from CLI (so I don't interrupt GPRS)?
21:46.36freemangordonLuke-Jr: you want to have both wifi and gprs up?
21:47.17Luke-Jrfreemangordon: yes
21:47.43freemangordonhmm, I am not exactly person to help you, but what about iwconfig?
21:47.48freemangordonjust an idea
21:48.40Luke-Jryeah, that's what I'm hoping for..but iwconfig is the furthest thing from easy to use
21:48.57Luke-Jrand I can only barely get on IRC right now; webpages are hopeless
21:49.27freemangordonLuke-Jr: hmm, maybe you could download qtmobilehotspot source and read through the magic id does
21:49.39freemangordonI suspect there are dbus calls to bting the interfaces
21:49.47freemangordon*bring
21:49.53freemangordonup that is
21:50.14freemangordonwtf is with my typing today ?!?
21:52.13freemangordonLuke-Jr: what about http://wiki.maemo.org/N900_dbus#com.nokia.icd2 ?
21:52.37freemangordonesp #define ICD_DBUS_API_CONNECT_REQ "connect_req"
21:55.43Luke-JrI wish I could open links
21:56.11*** join/#maemo Anz_ (~Anz_@234.33.78.188.dynamic.jazztel.es)
21:56.40freemangordonooh
21:57.29freemangordonsorry, can't help further, I have the same problem with iwconfig as yours :)
22:01.05*** join/#maemo valeriusL (~valerius@85.26.180.180)
22:05.18*** join/#maemo florian (~fuchs@sign-4db6b4ce.pool.mediaWays.net)
22:05.18*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
22:05.36*** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr)
22:45.36*** join/#maemo at1as (~at1as@kurios.r4780y.com)
22:58.22DocScrutinizer05hmm, seems route is the first thing to think about, eh?
22:58.36*** join/#maemo protem (~protem@ks3100918.kimsufi.com)
22:58.36*** join/#maemo protem (~protem@unaffiliated/protem)
23:01.39DocScrutinizer05but honestly why not just use mobilehotspot?
23:02.26DocScrutinizer05you still can fite a matching set of route configs after starting it
23:02.35DocScrutinizer05fire*
23:03.17DocScrutinizer05prolly pointless monologues since he left, eh?
23:09.40*** join/#maemo bef0rd (~bef0rd@unaffiliated/beford)
23:35.30triggerhappy=q/quit
23:49.08*** join/#maemo protem` (~protem@ks3100918.kimsufi.com)
23:52.27*** join/#maemo janemba (~101@unaffiliated/janemba)

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