Reply
Thread Tools
Posts: 2 | Thanked: 0 times | Joined on May 2010 @ Bratislava, Slovakia
#1281
Hi guys,
I'm new around here, so if this is not a good topic for this, please let me know (I saw people asking similar questions here).

I've been trying to install easy debian on my N900 tonight, and now it got to a state when I'm not sure if it's extracting the image or if it bricked my phone.

I was downloading the image over wi-fi, and had my phone connected to the PC whole time in PC Suite mode (but without actually doing anything with the phone via PC).

What happened:
1.) I installed Easy Debian
2.) I went into the menu and clicked on Debian Image Installer
3.) It started downloading the image...

The last I saw it was still downloading the image with 10 seconds remaining, then I went away for a bit and when I came back the screen was black. The LED was flashing with orange as if the phone was still being charged.

I read on the web that the extraction of the image can take a very long time (up to an hour). I expected to see this after the download, but I didn't see it:
http://www.flickr.com/photos/andrewc...7623428654651/

The phone is completely non-responsive now. I tried disconnecting it from the PC, and heard the classic disconnection beep (on the PC). When I plug it back, the orange LED starts flashing again (charge mode).

Thinking that the phone turned off / froze, I tried starting it with the power button, but there is no reaction.

Please do you think that the image extraction started without the confirmation and that the phone is so busy with the extraction that it just appears dead?

I'm still hoping that's the case, so I'll leave it be for an hour or so in order to give it time to finish the extraction. If it won't help, I'll try to remove the battery and boot it up again. If that won't work, I think that I'm about to try my first reflash

Any ideas / hints please?


Will sincerely appreciate any help / tips / guidance - thank you!
 
rebhana's Avatar
Posts: 579 | Thanked: 471 times | Joined on Jan 2010 @ Austria
#1282
mice, I don't know what troubles PC mode could cause, but downloading and extracting an Easy Debian image should not do anything to your Maemo system that could require a reflash.
__________________
Need more apps for the N900? Check out Qole's Easy Debian and read the wiki!
My Easy Debian installation log
 

The Following User Says Thank You to rebhana For This Useful Post:
Posts: 2 | Thanked: 0 times | Joined on May 2010 @ Bratislava, Slovakia
#1283
Hi rebhana,
fortunately I can confirm that now - all is well, thank you! Phone is now back online after an hour or so. The screen must have turned off as part of power saving, and the phone was too busy with extraction that it didn't want to turn it on in either way (touching the screen, the slider at the right side, etc).

If that's OK, I'll leave the original question + answer here, hoping that it gets indexed for anybody who might encounter the problem. Somebody might also want to put that in the installation notes ;-)
 
rebhana's Avatar
Posts: 579 | Thanked: 471 times | Joined on Jan 2010 @ Austria
#1284
Originally Posted by qole View Post
Run "Set Deb HW Keys" and then you can toggle the Styles and Formatting by pressing Fn (blue arrow) + Shift + "=" (top row, second from right). This is mapped to F11.

(EDIT: After trying it a few times, it seems to work best when you press the Fn key and then rock your finger down to press the Shift key as well; it doesn't seem to work pressing Shift first)
After experimenting a lot with xbindkeys+xvkbd for use in debbie (mostly in vain, see above), I discovered that F1-F12 for some reason work reliably only when the option -xsendevent is included. So all entries in /home/user/.xbindkeysrc like
Code:
"xvkbd -text "\[F1]""
 m:0x81 + c:24
...
should be replaced by
Code:
"xvkbd -xsendevent -text "\[F1]""                                   
 m:0x81 + c:24                                                      
...
Without -xsendevent, it seems to work reliably the first time used, but then only after several further attempts. With -xsendevent, it never failed me.
__________________
Need more apps for the N900? Check out Qole's Easy Debian and read the wiki!
My Easy Debian installation log

Last edited by rebhana; 2010-05-24 at 11:09.
 
Posts: 1,873 | Thanked: 4,529 times | Joined on Mar 2010 @ North Potomac MD
#1285
Originally Posted by rebhana View Post
I encountered some glitches with xvkbd+xbindkeys that I don't fully understand. Perhaps somebody can educate me:

For example an entry
Code:
"xvkbd -xsendevent -text "\[percent]"" 
 Shift+Mod5 + d
in .xbindkeysrc and activated by "debbie xbindkeys" does not produce the % character when I press Fn+Shift+d. Except for F1-F12, escape, and tab, only the characters that I anyway have on my (rx51-tailored) hw keyboard seem to work. (synchroot didn't help btw.)

However, when I start LXDE, open a terminal there, do
Code:
killall xbindkeys
xbindkeys
it does work (but only there, not outside of LXDE). It also doesn't work with "@xbindkeys -f /home/user/.xbindkeysrc" in the autostart file.


By the way, I found a way to take advantage of the virtual keyboard from within debbie applications. Backing out to the Maemo XTerminal, I produce a special character with the virtual keyboard there, copy the character, and can then paste it in the debbie application when the latter has a paste menu item. Fortunately, I need that only rarely because of my suitably remapped hw keyboard. But I would definitely prefer a more elegant solution.
I've had similar problems. Also If I used Mod5 + up or other arrow
keys more than a few times in .xbindkeysrc, the new key
definition did not work. I have no clue why.
I eventually used control +g and
control +t to define the additional characters (control + g is normally the bell and control +t is transpose, which I do not normally use). Regardless I am not happy with this solution. I've come around and think it is better to leave the traditional definitions of control sequences alone. So combining the Shift + Mod5 + "something ", as suggested, is a better solution. Unfortunately it did not work when "something" was an arrow key. Aesthetically it is nice
to use the left or right arrow for say <, >, or { , }. If you have success let me know.

Last edited by mscion; 2010-05-24 at 14:39.
 
Posts: 2 | Thanked: 3 times | Joined on May 2010
#1286
I have a "bug" to report: the base image should have a policy-rc.d which prevents services from being started/stopped inside the chroot (as detailed here: http://people.debian.org/~hmh/invoke...cification.txt )

Otherwise, certain package manager operations inside the chroot (e.g. apt-get remove dbus) will crash the N900 itself, as some service stop scripts will mistakenly kill the N900's own version of that service (and apparently stopping dbus causes the watchdog to reset the system).

Generally there's no reason to let invoke-rc.d actually do anything for a chroot system... services can still be started/stopped manually by running /etc/init.d/foo start|stop if the user wants them.

Thanks for the work!
 

The Following 2 Users Say Thank You to torne For This Useful Post:
qole's Avatar
Moderator | Posts: 7,109 | Thanked: 8,820 times | Joined on Oct 2007 @ Vancouver, BC, Canada
#1287
torne: Thank you very much for your help. That's great information.

So what should the image's policy-rc.d file look like?

EDIT: Should the policy-rc.d script simply have "exit 101" ?

Most people using chroot jails just need an one-line script which returns an exit status of 101 as the jailed /usr/sbin/policy-rc.d script.
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!

Last edited by qole; 2010-05-24 at 17:36.
 
rebhana's Avatar
Posts: 579 | Thanked: 471 times | Joined on Jan 2010 @ Austria
#1288
Originally Posted by mscion View Post
I've had similar problems. Also If I used Mod5 + up or other arrow
keys more than a few times in .xbindkeysrc, the new key
definition did not work. I have no clue why.
Actually my problem is xvkbd, not xbindkeys. If I just type
Code:
xvkbd -xsendevent -text "a"
in the Debian chroot terminal, I get (after a bunch of warning messages) "a" on the next command line. Similarly when I use "\[parenleft]" I get "(". But with a lot of other special characters such as "\[percent]", I get nothing at all. Most but not all of the characters that I can compose with Fn are not produced, plus all that are on the virtual keyboard.

mscion, do you have the same phenomenon or is it just me?

The warnings that xvkbd issues look unrelated to my problem:

Code:
Warning: Cannot convert string "-*-lucidatypewriter-bold-r-*-*-12-*-*-*-*-*-iso8859-1" to type FontStruct
Warning: Cannot convert string "-*-helvetica-bold-r-*-*-12-*-*-*-*-*-iso8859-1" to type FontStruct
Warning: Cannot convert string "-*-helvetica-medium-r-*-*-12-*-*-*-*-*-iso8859-1" to type FontStruct
Warning: Cannot convert string "-*-helvetica-medium-r-*-*-10-*-*-*-*-*-iso8859-1" to type FontStruct
xvkbd: Mode_switch not available as a modifier
xvkbd: although ISO_Level3_Shift is used instead, AltGr may not work correctly
__________________
Need more apps for the N900? Check out Qole's Easy Debian and read the wiki!
My Easy Debian installation log
 
Posts: 2 | Thanked: 3 times | Joined on May 2010
#1289
Originally Posted by qole View Post
torne: Thank you very much for your help. That's great information.

So what should the image's policy-rc.d file look like?

EDIT: Should the policy-rc.d script simply have "exit 101" ?
That should be sufficient, yes.
 

The Following User Says Thank You to torne For This Useful Post:
Posts: 45 | Thanked: 24 times | Joined on May 2010 @ Washington, DC
#1290
Anyone been able to confirm that PR1.2 plays well with Easy Debian? qole, any advice as to whether OTA or reflash-and-reinstall will work better?
 
Reply

Tags
beta, debian, easy debian, extras-devel, fremantle, i <3 qole, squeeze

Thread Tools

 
Forum Jump


All times are GMT. The time now is 10:37.