IRC log for #maemo-ssu on 20120413

01:52.07ShadowJKMight help with race to idle. Not helping the dwindling availability of working N900s
01:53.49DocScrutinizeron same topic: I wonder if omap3530 are available still, for spare/repair&refurbish
01:55.36DocScrutinizerI'd think if you could manage to swap digitizer and SoC, you can happily buy used N900
01:57.00DocScrutinizerpreferably omap3530 with proper POP chip
01:57.39DocScrutinizerwhile swapping whole SoC might be feasible, I'd not like to swap the POP
01:59.00DocScrutinizerI actually even wonder how they managed to avoid the POP "falling off" during reflow. Glued?
01:59.35DocScrutinizersimple adhesion
01:59.39DocScrutinizer?
02:03.12DocScrutinizerdang, a OMAP3530 binned for 1GHz+, with a 1GB RAM (+NAND) POP, that might actually be worth the effort
02:05.18DocScrutinizerI'd get me a poper SMT reworking station and would buy all the N900 I could get
02:06.43DocScrutinizerswap SoC, swap digitizer, put the thing into a new white case, sell -> profit
02:07.18DocScrutinizerof course isbfix :-D
02:07.25DocScrutinizerUSBfix*
02:16.08DocScrutinizerif only TI had put an "odometer" in their CPU
02:16.24DocScrutinizerpersistent one
02:40.08*** join/#maemo-ssu SpacedOut (~SpacedOut@2001:470:ba1b:210:20d:87ff:fe65:9942)
02:43.58*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
06:09.26*** join/#maemo-ssu Pali (~pali@unaffiliated/pali)
07:01.12*** join/#maemo-ssu DocScrutinizer (~halley@openmoko/engineers/joerg)
07:18.22*** join/#maemo-ssu scoobertron (~tom@93.186.147.98)
08:20.00*** join/#maemo-ssu sigkill_ (~sigkill@2.82.35.161)
08:25.02*** join/#maemo-ssu dafox (~dafox@dyn-194208.nbw.tue.nl)
09:06.29*** join/#maemo-ssu arcean (~Arcean@aacw159.neoplus.adsl.tpnet.pl)
09:38.53*** join/#maemo-ssu BCMM (~ben@unaffiliated/bcmm)
10:02.22*** join/#maemo-ssu NIN101 (~NIN@206.253.166.69)
10:23.23dafoxhi all. I just tried to update my phone, but now it seems to have gotten stuck. The screens says '(no updates available)', and only that, no controls etc. It doesn't seem to respond to any keypresses other than turning the screen on again. What do I do now?
10:45.09*** join/#maemo-ssu ekze (~nyan@bakaekze.ru)
10:51.48Lava_Croftapple cleaning cloth > n900 cleaning cloth
10:51.49*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-zyuazrrcwxhqpmxq)
11:32.26*** join/#maemo-ssu arcean_ (~Arcean@aadd24.neoplus.adsl.tpnet.pl)
12:01.18dafoxLava_Croft: any idea on how to handle the above situation?
12:01.44Lava_Croftno:( sounds bad
12:02.32dafoxwhat would happen if I just turned it off in this state?
12:02.45dafoxcould I just try to update again? (assuming it still boots)
12:06.46*** join/#maemo-ssu freemangordon (freemangor@130-204-50-168.2074156771.ddns.cablebg.net)
12:07.13tadzikif I were you I'd just reboot it. What kind of update was it?
12:07.55tadzikalso, do you happen to have an ssh server installed, and the phone connected to the network of some sort?
12:10.32dafoxit was a ssu update, I think, it also included some other packages
12:10.38tadzikah
12:10.43dafoxI do have a ssh, but I didn't connect to wifi
12:10.46*** join/#maemo-ssu andre__ (~andre@dslb-092-076-137-048.pools.arcor-ip.net)
12:10.46*** join/#maemo-ssu andre__ (~andre@Maemo/community/bugmaster/andre)
12:12.45dafoxtadzik: 'ah' as in 'good, nothing serious updated', or 'ah' as in 'critical system components updated' ?
12:13.06tadzikdafox: 'ah' as in "oh, SSU, then I don't know what to do "
12:13.23dafox:(
12:13.30dafoxI can still reach the power-button menu
12:13.47tadzikI'm on SSU for half a day myself, I don't know how much danger could possibly an interrupted SSU update bring
12:13.48dafoxI could try the 'switch off' button
12:14.01tadzikwell, you do have backupmenu, don't you?
12:14.15dafoxno, I haven't set it up yet :/
12:14.19dafoxstupid, I know
12:14.50Lava_Crofti dont use backupmenu:P
12:18.20dafoxDocScrutinizer, merlin1991: hi. You usually know a lot about maemo/ssu . Could you please give me some advice regarding the above problem?
12:23.20freemangordonPali, DocScrutinizer, seems after all dosfslabel is fsked and cannot set fvat label correctly, while mlabel has an option to use device name :)
12:23.28tadziksince a non-zero number of people are watching, did anyone have problems with a "silent" microphone on N900? Nothing SSU related I suppose; it works, but people on the other side tend to barely hear it
12:23.57freemangordonmlabel -i /dev/mmcblk1p1 ::NEWLABEL
12:24.15freemangordongoing to fix that on gitorious
12:24.44freemangordonmerlin1991, sould we push newer dosfstools in that case?
12:40.06Sicelotadzik: #maemo
12:40.28tadzikyeah, probably
12:48.40DocScrutinizerfreemangordon: yes, new recent mlabel is probably bearable
12:49.33freemangordonnoo, the one in maemo supports that
12:49.41freemangordonDocScrutinizer ^^^
12:49.43DocScrutinizero.O
12:49.46freemangordonyep
12:49.59freemangordonanyway, i will try to fix dosfslabel
12:50.22DocScrutinizert900:~# mlabel -V
12:50.24DocScrutinizerMlabel version 3.9.10, dated March 2nd, 2005
12:50.25DocScrutinizerconfigured with the following options: disable-xdf disable-vold disable-new-vold disable-debug enable-raw-term
12:50.52DocScrutinizert900:~# mlabel --help
12:50.54DocScrutinizermlabel: invalid option -- -
12:50.55DocScrutinizerMtools version 3.9.10, dated March 2nd, 2005
12:50.56freemangordoni've tried it with the above command and it works ok
12:50.57DocScrutinizerUsage: mlabel [-vscVn] [-N serial] drive:
12:51.22freemangordonyeah, but look in the code :D
12:51.36freemangordoncase 'i':
12:51.40freemangordonset_cmd_line_image(optarg, 0);
12:52.18DocScrutinizernuts#
13:03.24dafoxDocScrutinizer, freemangordon: hello?
13:03.46freemangordondafox, hi
13:04.13dafoxfreemangordon: could you please give me some advice regarding my phone's situation (as described above)?
13:04.53freemangordondafox, sorry, right now I am burried in dosfstool source code, better ask on #maemo
13:05.26DocScrutinizerdafox: no clue what's going on with your phone
13:05.57dafoxok, but what are my chances and options? Is there anything besides a reboot that I can try?
13:06.03DocScrutinizermight be some process hogging RAM and causing swap hell
13:06.44DocScrutinizerbefore you boot, try taskswitcher, switch to most suspicious task, try "kill current task" from power menu
13:07.10dafoxit still responds somewhat to powerbutton, but for example the ctrl-backspace does not work
13:07.22DocScrutinizerI've seen phone lock up for 90min, when some nasty flash webpage ate all RAM
13:07.22dafoxI think the desktop might have crashed or something
13:07.40DocScrutinizerunlikely
13:08.03DocScrutinizerkeep in mind it probably stacks up all the commands you give to it
13:08.13dafoxI /strongly think/ the desktop has crashed
13:08.16DocScrutinizerand executes them later, with possible huge delay
13:08.56dafoxit still responds quickly to the menu, and I've launched the phone with that, where I can scroll (smoothly)
13:09.04DocScrutinizerI suggest you try shift-ctrl-X
13:09.09DocScrutinizerto get a terminal
13:09.14DocScrutinizerthe launch htop
13:09.37DocScrutinizerthen*
13:09.55dafoxshift-ctrl-x doesn't seem to work
13:10.01dafoxhowever the power-button-menu is on the top-left of the screen, rather than in the center
13:10.27dafoxalso the usual controls (the maximime-window-type button on the top left, battery indicator) are missing
13:10.38DocScrutinizerhmm, sounds like X got confused, possibly even gfx
13:11.06dafoxlock-screen is also not centered on screen
13:11.12DocScrutinizeroften some freaky widget can cause this
13:11.24dafoxit happened during an update
13:11.26DocScrutinizerreboot
13:11.45dafoxand I was afraid to just reboot without getting some advice on what might go wrong first :)
13:12.05DocScrutinizerI dunno what might go wrong
13:12.16DocScrutinizerI friggin dunno even what's wrong now
13:12.42dafoxok, I'll try rebooting then
13:12.55DocScrutinizeryou could try plugging it to USB and make a backup of your MyDocs at least
13:13.02dafoxtoo late
13:13.05dafoxit's off now
13:13.26dafoxthat was the kind of tip I was looking for though, thanks
13:15.01DocScrutinizernah, backup of MyDocs won't be needed
13:15.04dafoxDocScrutinizer: ok, it seems to still boot
13:15.32dafoxlol it even said 'operating system successfully updated'
13:15.52dafoxthere are still updates pending though
13:16.14dafoxdo you think I should try updating again?
13:16.18DocScrutinizeryes
13:16.30dafoxok
13:16.52dafoxthis will take a while, probably
13:17.15DocScrutinizerafk
13:17.35dafoxdon't leave me hanging man :p
13:34.49dafoxok, updated and rebooted, seems to still work
13:36.09freemangordonDocScrutinizer, FUUUUK, again, the case with Qt 4.7.4 DAMN STUPID gcc -Ox flags, that can't be true :(. gcc optimisations screw dosfstools
13:36.24freemangordonwithout -O2 it works
13:36.27dafoxthanks for the encouraging words everyone :)
13:36.50DocScrutinizerbwahahaha
13:36.59dafoxbtw, does anyone know why 90% of the time n900 refuses to boot while charging?
13:37.03freemangordondafox, this is #maemo-ssu developers, contributors, ets channel, not first line of support
13:37.45DocScrutinizerdafox: I never seen any such problem
13:37.55dafoxsorry, I thought it might be related to ssu :/
13:38.04DocScrutinizerit just takes some 30s after USB plugin to settle
13:38.07DocScrutinizerthen it boots
13:38.14DocScrutinizeron powerbutton
13:38.47DocScrutinizerdafox: ignore freemangordon, he's in grumpy mood today ;-)
13:38.52freemangordonDocScrutinizer, please, tell me, why , why the hell it is always the same and always happens to me
13:39.06DocScrutinizerI dunno :-D
13:39.10DocScrutinizertake it easy
13:39.11dafoxfor me it usually starts to boot (nokia logo), then freezes for a while, then reboots into 'offline charging' mode (the state it goes to when you plug in the charging while it's off)
13:39.12freemangordondafox, yeah, DocScrutinizer is right :D
13:39.37dafoxok, you scared me a bit though :)
13:40.01DocScrutinizerdafox: that's absolutely normal behaviour
13:40.17*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
13:40.35DocScrutinizerafter plugin of USB
13:40.42dafoxyou mean you're not supposed to be able to (re)boot the phone while it is connected to the charger?
13:41.03DocScrutinizererr, what do you mean with 'reboot'
13:41.10freemangordondafox, when you power-down the device with charger connected, it actually boots maemo in so-called ACT)DEAD mode, and that takes time
13:41.30freemangordonuntil that mode has settled you cannot power-up the device
13:41.34DocScrutinizeryou can't power down when charging
13:41.47DocScrutinizerand what freemangordon said, too
13:42.44DocScrutinizerwhen you connect to USB, you need to wait 30s til "powering up" via powerbutton
13:43.07DocScrutinizersame after you "powered down" with USB plugged in
13:43.51DocScrutinizerand no, that's no CSSU issue
13:44.14DocScrutinizerpowerkernel has some special issues in that regard
13:44.36dafoxLet me try to explain as clearly as possible what happens: Phone is on. I plug in the charger, it starts charging. Then for some reason (usually updates) I want to reboot the phone. It powers down, then powers up to 'charging mode'. Until it has finished booting the power button won't work (the LED does not turn white). Then I push the power button until the led lights. Then the led turns of, but the vibration does not happen. The phone starts to b
13:44.37dafoxoot, showing the nokia logo ('NOKIA', not the handshake). Then after a while it reboots into 'charging mode' again.
13:45.02DocScrutinizerit seems with powerkernel it actually fails to boot to active state when plugged to USB and you press powerbutton
13:45.03dafoxI am running the power-kernel, and I am allowing (slight, dynamic) overclocking
13:45.56DocScrutinizeryou pressed the power button either too early, or too long
13:46.15DocScrutinizeraaah, and with powerkernel that's actually a known problem
13:46.20freemangordondafox, which version of kernel-power?
13:46.43DocScrutinizeryou should unplug to boot up
13:47.02freemangordonDocScrutinizer, that is fixed in v50, that is wahy I am asking
13:47.06dafoxaha, ok
13:47.14DocScrutinizerunless somebody fixed it n recently'ish kernel
13:47.15dafoxI think it might have just been updated, let me check
13:47.29DocScrutinizer:-D
13:47.36dafoxI have 2.6.28.10-power50
13:47.46freemangordonis it still reproducible?
13:47.47DocScrutinizerfine, so give it a test
13:47.51freemangordon:D
13:48.01dafoxI'll try, it just failed on first boot
13:48.32dafoxSo, 'switch off', wait for it to boot, then wait 30 more seconds, then press power button briefly?
13:48.35DocScrutinizeryou first should boot normally 2 or even 3 times, for system to settle, after flashing/update
13:48.36dafoxHow briefly?
13:49.08DocScrutinizeryou did it right
13:49.08dafoxI didn't flash, just normal over-the-air update
13:49.24dafoxuntil the led turns white and then off?
13:49.30*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.141)
13:49.37DocScrutinizerthen one normal boot aftter the boot involved in update shall suffice
13:49.43DocScrutinizer:nod:
13:49.55DocScrutinizertakes some 3..4s iirc
13:50.01DocScrutinizermaybe less
13:50.56dafoxok so this time it reboots again, let me try once more with a 'unpowered boot' in between
13:51.55DocScrutinizerit's actually some bug "I" introduced with hostmode
13:52.28DocScrutinizerfreemangordon looked into it to fix it
13:52.39DocScrutinizerfreemangordon: didn't you check it?
13:55.14freemangordonif the bug is fixed?
13:55.22freemangordonof course
13:56.09freemangordonbut it could be that dafox has some another problem
13:56.41freemangordonand it is better if he leaves convinced that the bug is no more there
13:57.28freemangordonDocScrutinizer, do you know what dosfstools (>> 3.0.1-1maemo2) is supposed to mean?
13:57.32freemangordonI mean >>
13:57.38dafoxok, it still reboots when booting with the usb charger connected
13:57.40freemangordonin control file
13:58.03freemangordondafox, how many times?
13:58.30freemangordonas actually there should be 2 reboots AFAIK
13:58.35dafox4 reboots so far, since I asked my question here
14:00.14freemangordonhmm, >> means strictly later
14:01.00dafoxdoesn't it normally mean 'much bigger/later/greater'
14:06.10dafoxfreemangordon: anyhow, seems like the reboot issue is still present. Are there any logs you'd like me to peek at?
14:07.44freemangordonthe only thing you can do is to enable framebuffer console and to capture a video of the boot process. search on TMO on how to enable framebuffer console.
14:10.13dafoxI don't have anything on hand to record, sorry.
14:22.22DocScrutinizeryou could do a uname -a
14:22.47DocScrutinizerdafox: ^^
14:23.32dafoxDocScrutinizer: that would give me just the kernel version?
14:23.42DocScrutinizeryep
14:23.58dafox(which is 2.6.28.10-power50, as I said before :)
14:24.08DocScrutinizeraah, k
14:24.38DocScrutinizerif you already did uname -a, then why you're asking what it does? ;-)
14:25.50DocScrutinizerthough this string doesn't look like uname output
14:35.24tadzikaaargh
14:36.04tadzikI had leftover alsamixer process running and it drained my battery in 2 hours
14:36.12tadzikffs
14:39.18dafoxDocScrutinizer: just making sure what you said matched what you meant. The full string is 'Linux nodame 2.6.28.10-power50 #1 PREEMPT Sun March 18 20:10:56 EET 2012 armv71 GNU/Linux'
14:40.14DocScrutinizer51tadzik: weird
14:40.29tadzikso much for geocaching today
14:41.26Lava_Croftprotip: get more batteries
14:41.44DocScrutinizer51I'd rather suspect GPS drqained battery :)
14:42.10tadziknot really, it wasn't even on. I just looked at the battery widget and "wtf". Then htop explained the mystery
14:42.12Lava_Croftthat doesnt matter if you have more batteries!
14:42.20Lava_Crofti always carry around 2 spare ones
14:42.26Lava_Croftand theres another few at home
14:42.28tadzikheh
14:42.34Lava_Croftthey are quite small
14:42.37freemangordonPali, merlin1991, whoever is interested, a new version in ke-recv and dosfstools in cssu-devel repo
14:42.41Lava_Croftjust get em in a ziplock bag and its waterproof too
14:43.01Palifreemangordon, ok, I will change battery and test it
14:43.09Lava_Crofttadzik: n900 batteries arent that expensive
14:43.16Lava_Crofthere its like 7euros orso
14:44.32DocScrutinizer51anyway I'd like to ask for a bit more on-topic
14:44.41DocScrutinizer51generally
14:45.24DocScrutinizer51battery issues on N900 are best discussen in #maemo
14:45.26tadzikLava_Croft: well, I'm not even on a journey of my life, I just went to $dayjob, unaware of the dangers :)
14:45.33tadziksorry
14:45.39Lava_Croftbe prepared
14:56.05*** join/#maemo-ssu wmarone (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
15:03.51Palifreemangordon, working fine
15:26.24freemangordonPali, did you try both fat/ext3?
15:26.52PaliI tried this: sudo dosfslabel /dev/mmcblk1p6 data; echo $?
15:26.53freemangordonBTW I didn't check "format" option
15:26.59Paliand it returned 0
15:27.13Palisudo dosfslabel /dev/mmcblk1p6; echo $?
15:27.18Palidata
15:27.18Pali0
15:27.28Paliso dosfslabel is fixed
15:27.31freemangordonPali, try to rename a volume in filemanager. you did apt-get update/upgrade, aint?
15:27.40Paliyes
15:28.11freemangordonso, rename in filemanager should work too, as is format, but i didn't check latter
15:28.42freemangordoncan you test both rename and forma?
15:28.49freemangordon*format
15:28.55PaliI tested now renaming fat32 via filemanager
15:29.10Paliworking fine, but it renames to UPPER characher
15:29.31Palifilemanager show alwyas first character upper and toher lower
15:29.35freemangordonwell, that is something in ke-recv
15:29.44Palibut dosfslabel show all in upper
15:30.46Paligoing to try rename ext4 part
15:31.36Palisees working (but again renamed to upper chars)
15:32.37Palibut it still umounting mmc device!
15:33.35freemangordonPali, mmc device should not be unmounted, how did you find that
15:33.35PaliIn syslog after renaming I have this line: ke_recv[7175]: device_removed:2684: udi: /org/freedesktop/Hal/devices/volume_uuid_a8fc87cf_2150_4e5b_a5c2_f345fa9d7b4c
15:33.59Paliso seems that hal removing device and ke-recv unmounting it
15:34.03freemangordontaht is because of HAL reprobe, but the device is not unmounted
15:34.39freemangordonyou could check that by opening a file on the volume to rename
15:35.35Palisee my syslog: http://pastebin.com/SUWCGDpw
15:36.31Paliyou can see kernel (dmesg) ext4 output that mmc device was unmounted
16:07.02*** join/#maemo-ssu fw190 (~krzysztof@user-31-175-155-111.play-internet.pl)
16:13.49Palifreemangordon, I have better solution for find_by_property
16:14.13Palimmc_info_t structure has linked list for all volumes
16:14.43Paliso we can find which is device in string dev
16:15.11Palians volume_list_t has stored needed udi
16:24.51*** join/#maemo-ssu NIN101 (~NIN@206.253.166.69)
16:55.02*** part/#maemo-ssu fw190 (~krzysztof@user-31-175-155-111.play-internet.pl)
17:32.56amiconnDocScrutinizer51: You mentioned boot times. When powering down my N900, I *always* have to wait at least 30 seconds before powering on works again. I wonder whether this is normal
17:43.41merlin1991amiconn: yes it is
17:44.19amiconnIs there a faster way to reboot?
17:46.40NIN101I guess dsmetool -b
19:20.43*** join/#maemo-ssu arcean (~arcean@aadd24.neoplus.adsl.tpnet.pl)
20:29.20*** join/#maemo-ssu javispedro (~javier@Maemo/community/contributor/javispedro)
20:29.41*** join/#maemo-ssu psycho_oreos (~no@unaffiliated/tuxsavvy)
20:33.38*** join/#maemo-ssu scoobertron (~tom@93.186.147.98)
21:32.05*** join/#maemo-ssu trbs (~trbs@2001:470:d2ad:1:4a5b:39ff:fe7d:1623)
22:45.14*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
22:50.37*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
23:08.45*** join/#maemo-ssu Jaffa_ (~andrew@badger.bleb.org)
23:38.50*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.141)

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