Not sure if this goes in here or os two o o eight, and Fn is too short a string to search, so here goes...

I'm not sure what I did, but after restarting my tablet my Fn key suddenly stopped working in my cloned Diablo partition...

I had it on for a long while and was actively tweaking alot of stuff throughout, so i'm not sure what could have caused it... the last thing i did was change mce.ini's short home key behavior to disabled and long home key to short.

pushing the fn key lights up the keyboard, and the key works fine in my flash partition, so no hardware failure...

the rx-fourfour file looks to be okay, and changing the fn key's default level three shift to something arbitrary doesn't generate the key event, so its like pushing fn only lights up the keyboard. <having no blue keys suck -_- >

any idea what could be going on here, and where i can glance at to further troubleshoot the issue <question> recloning is always an option, but it'd be nice to learn what's going on under the hood regardless

thanks in advance <exclam>

it appears I have encountered this problem as well. I recently installed the latest diablo version as of this post. I used the following file:

RX-44_DIABLO_4.2008.36-5_PR_COMBINED_MR0_ARM.bin

to summarize what I encounter:
* using top row of keys (intending numbers to be typed) in the boot lock code window yields no response.

* after boot, using the function key once or twice followed by pressing any key with a blue character yields nothing. Shift functionality works fine.

* the Chr button does not bring up the lower third window with various infrequently used characters.

* all of these things used to work in chinook prior to my installing this latest version of diablo.

---

I have found no post in the maemo bugs site that talks about this specific problem or a post on ITT. Help in figuring this out would be great.

bump

a link to the maemo bugs entry.

https://bugs.maemo.org/show_bug.cgi?id=3847

I've just managed to reproduce the bug after having to reflash my N810 yesterday. The problem package (for me) was maemo-pc-connectivity v0.4. I uninstalled it, got my Fn key back and even somehow got to keep the USB mode control(that the package added) in the system tray.

Bug marked as invalid, no solution here, and I found unresolved messages in maemo-pc-commectivity maillist dated about 2009.02.11

This bug causes a lot of inconvinience, though.

Any suggestions how to re-vitalise Fn key and Ctrl-Chr layout switching without reflashing?

"cat /dev/event/input0 " shows that events from those keys are OK but I havn't clue where thay get lost.

Problem solved by restoring original X start file.

maemo-pc-connectivity overwrites file "/etc/init.d/x-server" with additional X options. Replacing it with original file solves problem.

Working file contains following options line:
ARGS="-mouse tslib -nozap -dpi $DISPLAY_DPI -wr -nolisten tcp"

Broken file options are:

ARGS="-mouse tslib -nozap -dpi $DISPLAY_DPI -wr -nolisten tcp -extension XInputExtension"

This has just happened to me: the last few days the Fn key hasn't been working. Removing "-extension XInputExtension" from the top of /etc/init.d/x-server

Rebooted. It worked! :-D