-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SysReq key not being sent? #168
Comments
Also I for one doesn't use 'System Request' key for anything and honestly don't know much about how the key is recognized in Xorg, Linux and other OS's. Which keycode are you using for 'System Request'? KC_SYSREQ or KC_PSCREEN? (Where is your keymap file?) First, it seems that keycode KC_SYSREQ(0x9A) is not used in Linux and Windows at least. I guess that in PC keyboards 'System Request' key is probably combination of 'Alt' and 'PrintScreen'. Read resouces on the net, try them and report back! I'd like to know your result. http://en.wikipedia.org/wiki/Magic_SysRq_key |
And how about using 'showkey' on console instead of 'xev'? I think you'll be able to get more 'raw' keycodes with that. |
I am using KC_SYSREQ, but I'll try KC_PSCREEN in a minute. The keymap is at https://github.com/frioux/tmk_keyboard/blob/e89161b3b2e5ec20138d2bd0c0d32df1b51f8935/keyboard/ergodox/keymap_frew.h; I was trying to add it to the left hand thumb cluster, the bottom right key there. I am trying to use it for Magic SysRq. I'll also try with showkey too, though xev did show the SysReq on a different keyboard. Making new build now! Will post if KC_PSCREEN works. |
You were right, KC_PSCREEN made it work! Thanks! |
I have a custom layout at http://github.com/frioux/tmk_keyboard, it's a fork of @cub-uanic's ergodox port. I wanted to add a SYSREQ key and for some reason it never seems to send the right keycode. On a regular keyboard, Alt+SysReq sends this:
on my ergodox, Alt+SysReq sends this:
I noticed that no one else ever uses the SYSREQ key, at least in the default tmk
repo. Is it possible that maybe it's incorrectly defined?
The text was updated successfully, but these errors were encountered: