On 28/03/18 04:10 PM, ken wrote:
On 03/28/2018 09:09 AM, Anton Aylward wrote:
There is no mention of YAST_KEYBOARD anywhere on my system
Do you have anything in your /etc/sysconfig/keyboard at all?
Everything is set to either "" or "no"
In the backups of this machine's previous CentOS (7.x) system there was no /etc/sysconfig/keyboard, but there was /etc/X11/xorg.conf.d/00-keyboard.conf file (programmatically generated) containing this: The Centos web pages are ... interesting... but this is openSuse. You can't simply paste across arbitrarily like that.
In most instances I would agree with you completely. But I'd also well believe that much of the basic code in many distros is the same... and that would include code that handled keyboards which have been around already for a number of years. It's FOSS, after all... developers borrow code from one another. Indeed, perhaps it was the same developer(s) who wrote the keybd-handling code which trickled into *all* the Linux distros. I'm also partially playing devil's advocate with myself though... as said in my original post, I'm leery of that particular solution and reckless cowboy sysadmining in general. For example, it's possible that the keyboard is specified in two or three different places/files, and changing just one of them could make things worse.
In this case I'd claim my argument is superior. OpenSUSE makes more use of event handling at the kernel level and though the use of various rules, for example in etc/audit/rules.d /etc/polkit-1/rules.d /etc/udev/rules.d and ... /usr/share/X11/xkb/rules and therein .. # more README This directory lists sets of rules which can be used to obtain an exact XKB configuration. and # more xorg // DO NOT EDIT THIS FILE - IT WAS AUTOGENERATED BY merge.sh FROM rules/*.part The file 'base.lst' lists many possible keyboards :-) You might also, in the list of my previous reply, look at /usr/lib/udev/rules.d/60-evdev.rules for keyboard handling and setup.
I don't know anything about edev drivers. This keyboard has a lot of keys for multi-media, so probably requires more than a generic keymapping scheme:
... $ lsmod | grep "key\|kbd" sparse_keymap 16384 1 hp_wmi
Yes. I have a IBM multifunction that I picked up for C$5 at a thrift store that has an additional 20 or so buttons including media and definable strings. But it's in the database and the evdev drivers found it and I didn't have to configure anything. I was, I admit, impressed. -- Anton J Aylward Dodo Flight Research Laboratories Cassowary Division North York, Ontario -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org