Thanks. As suspected, GPM does not grab keycode 213, which is the event coming from your suspend key. That explains why Fn+F1 doesn't work. However, GPM has never grabbed that key (or at least it didn't in Hardy), so I don't think that this is the fault of GPM.
Could you switch to a terminal (CTRL+ALT+F1), and try the following:
Run "sudo /etc/init.d/hotkey-setup stop" and then "showkey -s". Press the Fn+F1 combination and note the scancodes. Now run "showkey -k" and press the same key combination again, noting the keycodes that appear.
Then could you run "sudo /etc/init.d/hotkey-setup start", and repeat the above test with "showkey -k" and "showkey -s".
When you run "showkey -s", scancodes will appear for both press and release. It might be useful if you could annotate the output so I know where you pressed and released keys.
Thanks. As suspected, GPM does not grab keycode 213, which is the event coming from your suspend key. That explains why Fn+F1 doesn't work. However, GPM has never grabbed that key (or at least it didn't in Hardy), so I don't think that this is the fault of GPM.
Could you switch to a terminal (CTRL+ALT+F1), and try the following:
Run "sudo /etc/init. d/hotkey- setup stop" and then "showkey -s". Press the Fn+F1 combination and note the scancodes. Now run "showkey -k" and press the same key combination again, noting the keycodes that appear.
Then could you run "sudo /etc/init. d/hotkey- setup start", and repeat the above test with "showkey -k" and "showkey -s".
When you run "showkey -s", scancodes will appear for both press and release. It might be useful if you could annotate the output so I know where you pressed and released keys.
Thanks