On 03/28/2018 09:09 AM, Anton Aylward wrote:
On 27/03/18 10:34 PM, ken wrote:
I'm on 42.3. What are you running? The same. If it matters, the very fresh install was of Leap 42.3 NET X86_64.
[snip]
Looking around in logs and configs, I found the keyboard specified in /etc/sysconfig/keyboard to be "pc104". Unspecified in any/all of mine
[...] Here's that final line from the "keyboard" file:
YAST_KEYBOARD="english-us,pc104" There is no mention of YAST_KEYBOARD anywhere on my system
Do you have anything in your /etc/sysconfig/keyboard at all?
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.
Does anyone have a more cautious and/or informed solution or suggestion? That's interesting. I don't use yast for setup and I've never to my recall had to configure a "keyboard.conf" file one way or another.
I guess I didn't mention: I never attempted to configure the "keyboard.conf" file. I was fine with the keyboard as it was. I'm pretty sure the problem arose when I went into YaST2 and ran a "hardware scan"... I thought it would just display hardware settings, not that it would change anything.
I grep and I find
/etc/X11/xorg.conf.d # grep -C 5 keyboard * ... 10-evdev.conf-Section "InputClass" 10-evdev.conf: Identifier "evdev keyboard catchall" 10-evdev.conf- MatchIsKeyboard "on" 10-evdev.conf- MatchDevicePath "/dev/input/event*" 10-evdev.conf- Driver "evdev" 10-evdev.conf-EndSection ...
Running the same grep, there's many more configuration statements. E.g., the only time I recall specifying a US keyboard was in the install program. .... /etc/X11/xorg.conf.d $ grep -C 5 keyboard * 00-keyboard.conf-# Read and parsed by systemd-localed. It's probably wise not to edit this file 00-keyboard.conf-# manually too freely. 00-keyboard.conf-Section "InputClass" 00-keyboard.conf: Identifier "system-keyboard" 00-keyboard.conf- MatchIsKeyboard "on" 00-keyboard.conf- Option "XkbLayout" "us" 00-keyboard.conf- Option "XkbModel" "microsoftpro" 00-keyboard.conf- Option "XkbOptions" "terminate:ctrl_alt_bksp" 00-keyboard.conf-EndSection -- 10-evdev.conf- MatchDevicePath "/dev/input/event*" 10-evdev.conf- Driver "evdev" 10-evdev.conf-EndSection 10-evdev.conf- 10-evdev.conf-Section "InputClass" 10-evdev.conf: Identifier "evdev keyboard catchall" 10-evdev.conf- MatchIsKeyboard "on" 10-evdev.conf- MatchDevicePath "/dev/input/event*" 10-evdev.conf- Driver "evdev" 10-evdev.conf-EndSection 10-evdev.conf- -- 40-libinput.conf- MatchDevicePath "/dev/input/event*" 40-libinput.conf- Driver "libinput" 40-libinput.conf-EndSection 40-libinput.conf- 40-libinput.conf-Section "InputClass" 40-libinput.conf: Identifier "libinput keyboard catchall" 40-libinput.conf- MatchIsKeyboard "on" 40-libinput.conf- MatchDevicePath "/dev/input/event*" 40-libinput.conf- Driver "libinput" 40-libinput.conf-EndSection ....
Different smarts, eh? But then this is a PC with a generic keyboard. Still, late model openSuse, let the edev libraries figure it out.
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 .... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org