This is a discussion on keyboard and evdev: MIRACLE! within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Following an old suggestion coming from Israel: http://mirror.hamakor.org.il/archive...2003/2873.html I launched this command xprop -root -remove _XKB_RULES_NAMES and my Italian ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Following an old suggestion coming from Israel: http://mirror.hamakor.org.il/archive...2003/2873.html I launched this command xprop -root -remove _XKB_RULES_NAMES and my Italian keyboard resuscitate! Now I can type àèìòù again, even if the arrow keys, the ins/del block and alt-gr still don't work (a lesser annoyance). I think this could be a starting point for somebody else to fix that bloody evdev bug. HTH Cyrus (the /euphoric/ virus) -- I love to be mailed just by smart people: perl -we 'print "\12\142\145\162\156\141\155\141\100\151". "\164\167\145\142\56\151\164\12\12";' |
| |||
| cyrusthevirus wrote: > Following an old suggestion coming from Israel: > http://mirror.hamakor.org.il/archive...2003/2873.html > I launched this command > xprop -root -remove _XKB_RULES_NAMES > and my Italian keyboard resuscitate! > Now I can type àèìòù again, even if the arrow keys, the ins/del block > and alt-gr still don't work (a lesser annoyance). > I think this could be a starting point for somebody else to fix that > bloody evdev bug. > Any progress on this? I have my JP106 keyboard working but without arrow keys, insert/delete, home, page* it's pretty crippled. AFAICT there are no errors anywhere; those keys just don't work. I wonder if evdev changes the scancodes somehow.... --Yan |
| ||||
| Il 01/02/2007 19:06, CptDondo dixit: > Any progress on this? What about this, Yan? ¹²³ä×È¡½¾¼¿ I'm writing another HOWTO about it. > I have my JP106 keyboard working but without > arrow keys, insert/delete, home, page* it's pretty crippled. My problem was the same, until I had the idea to check every key with xev. Oddly, on my IBM type M keyboard, 18 years old¹, arrows and other edit keys have different keycodes from the standard /etc/X11/kbd/keyvodes/xfree86 So I made a copy of that file, using my own keycodes, and now it works smoothly. To launch the keyboard I use this bash script: ------------%< --------------- %< ------------------ #!/bin/bash # reset _XKB_RULES_NAMES property to xfree86 - 8s is the string length xprop -root -f _XKB_RULES_NAMES 8s -set _XKB_RULES_NAMES "xorg" echo -e "\n------------\nxprop done\n\n"; # set xkb parameters: setxkbmap -v 10 -keycodes "MyCodes" -types "default" -compat "default" -symbols "MySymbols" -geometry "pc(pc102)" echo -e "\n------------\nsetxbmap done\n\n"; # save xkb parameters for debug: xmodmap -pm -pk > /tmp/MyCharlist.tmp ------------%< --------------- %< ------------------ > AFAICT there are no errors anywhere; those keys just don't work. Frustrating, uh? > I wonder if evdev changes the scancodes somehow.... Who knows? Maybe it is a side effect. Have fun Cyrus (the /UTF-8/ virus) ¹ just like the spam: wonderful eighteen... -- I love to be mailed by smart people: perl -we 'print "\12\142\145\162\156\141\155\141\100\151". "\164\167\145\142\56\151\164\12\12";' Spammers scratch here with a diamond to find my address: ||||||||||||||||||||||||||||||||||||||||||||||| |