SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So after the switch to 13.0 I found out that X cannot handle keycodes over 255.
Well my macbook's FN key, according to various other sites, pushes out a 464 keycode. Because of this my lappy keeps getting stuck at starting X. Returns an error telling me it's unable to handle the keycode 464. How can I remap this so that it's under 255?
Thanks in advance.
Oh, and the FN key works in console, just when running up X does it freeze and give me the error in /var/log/Xorg.0.log.
Distribution: Slackware (personalized Window Maker), Mint (customized MATE)
Posts: 1,309
Rep:
With the new release of Xorg I stated all my old keycodes don't work and xev output isn't reliable. I had to use xmodmap -pke command to determine the appropriate keycodes. Just try it. Maybe it'll be helpful in your case too.
With the new release of Xorg I stated all my old keycodes don't work and xev output isn't reliable. I had to use xmodmap -pke command to determine the appropriate keycodes. Just try it. Maybe it'll be helpful in your case too.
That prints out a long list, which I'm guessing is a list of all my mapped keys and what the translation of them are for the system.
But what can I do with that? If my system is crashing because of a 464 keycode, how can I force my computer to get a different keycode or expand my range past 255??
Distribution: Slackware (personalized Window Maker), Mint (customized MATE)
Posts: 1,309
Rep:
You can try to find on that list the events you're interested in and assign keycodes with keysyms using ~/.Xmodmap file. Then you can put xmodmap ~/.Xmodmap command into ~/.xinitrc file and use these keys in X Window.
As I know Xorg is limited to 255 keycodes. I don't know if there's any method to map higher keycodes to the range acceptable by Xorg.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.