[opensuse] misconfigured keyboard: which is correct <keyboard> for HP Envy laptop?
Initially This keyboard was functioning fine on a brand-now installation of Leap 24.3 on an HP Envy laptop (17t-n100 CTO). Trying to solve a completely different problem, I went into YaST2 and ran a hardware scan. After doing that, my keyboard was misconfigured and now has numerous problems. E.g., I now have no CapsLock key, neither of my Ctrl keys works, and the leftside Ctrl key now functions like a Super-L key. And there are many more such problems, none of which I ever had in centos or in suse before running that yast hardware scan. Looking around in logs and configs, I found the keyboard specified in /etc/sysconfig/keyboard to be "pc104". I can't say for certain whether that is correct or incorrect, except that "pc104" was mentioned in the log file "/var/log/YaST2/y2log" several times on or about the date/time I ran the hardware scan. So it is highly suspect. Here's that final line from the "keyboard" file: YAST_KEYBOARD="english-us,pc104" 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: Section "InputClass" Identifier "system-keyboard" MatchIsKeyboard "on" Option "XkbLayout" "us" Option "XkbModel" "pc105+inet" EndSection If I was a wild-ass cowboy of a sysadmin I'd just replace the "pc104" value in the Leap /etc/sysconfig/keyboard file with the "pc105+inet" value from the CentOS config file and reboot. Yahoo! But that might hork things immensely and leave me with a system with a keyboard even more crippled than what I have now. Does anyone have a more cautious and/or informed solution or suggestion? tnx -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/03/18 10:34 PM, ken wrote: I'm on 42.3. What are you running?
[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
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.
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 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 ... Different smarts, eh? But then this is a PC with a generic keyboard. Still, late model openSuse, let the edev libraries figure it out. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2018-03-28 at 09:09 -0400, Anton Aylward wrote:
On 27/03/18 10:34 PM, ken wrote:
I'm on 42.3. What are you running?
[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
There are in mine: YAST_KEYBOARD="spanish,pc104"
Does anyone have a more cautious and/or informed solution or suggestion?
YaST --> hardware setup --> System keyboard layout. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlq7lWYACgkQtTMYHG2NR9U5jACgiOnvEbjV9R03L0Rd8MwEKd21 KKMAnAlnTP2CVtu5fp8pVsI4JRJCSZAS =/zby -----END PGP SIGNATURE-----
On 03/28/2018 09:15 AM, Carlos E. R. wrote:
On Wednesday, 2018-03-28 at 09:09 -0400, Anton Aylward wrote:
On 27/03/18 10:34 PM, ken wrote:
I'm on 42.3. What are you running?
[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
There are in mine:
YAST_KEYBOARD="spanish,pc104"
Yay! I'm not crazy!! :)
Does anyone have a more cautious and/or informed solution or suggestion?
YaST --> hardware setup --> System keyboard layout. Did that... many times... and once again on your suggestion. No change.
I don't, however, think that is the cause of the problem because that same exact screen comes up during install and my keyboard was fine immediately after completing that install.
-- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-03-28 22:40, ken wrote:
On 03/28/2018 09:15 AM, Carlos E. R. wrote:
YAST_KEYBOARD="spanish,pc104" Yay! I'm not crazy!! :)
I think you may need: YAST_KEYBOARD="us,pc104"
Does anyone have a more cautious and/or informed solution or suggestion?
YaST --> hardware setup --> System keyboard layout. Did that... many times... and once again on your suggestion. No change.
I don't, however, think that is the cause of the problem because that same exact screen comes up during install and my keyboard was fine immediately after completing that install.
I would try changing the setting in text mode, and testing it there. If it works there, but not on X after starting them, the issue is different. I would then try as a new user. And perhaps with a different desktop. I don't remember using the hardware scan module. I thought it printed a description only. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 03/28/2018 04:55 PM, Carlos E. R. wrote:
On 2018-03-28 22:40, ken wrote:
On 03/28/2018 09:15 AM, Carlos E. R. wrote:
YAST_KEYBOARD="spanish,pc104" Yay! I'm not crazy!! :) I think you may need: YAST_KEYBOARD="us,pc104" That's what I already have, and what I've had since this problem began... maybe I had it there before the problem occurred also, I don't know. Here's what I noted in my original post here:
Looking around in logs and configs, I found the keyboard specified in /etc/sysconfig/keyboard to be "pc104". I can't say for certain whether that is correct or incorrect, except that "pc104" was mentioned in the log file "/var/log/YaST2/y2log" several times on or about the date/time I ran the hardware scan. So it is highly suspect. Here's that final line from the "keyboard" file:
YAST_KEYBOARD="english-us,pc104"
Does anyone have a more cautious and/or informed solution or suggestion? YaST --> hardware setup --> System keyboard layout. Did that... many times... and once again on your suggestion. No change.
I don't, however, think that is the cause of the problem because that same exact screen comes up during install and my keyboard was fine immediately after completing that install. I would try changing the setting in text mode, and testing it there. If it works there, but not on X after starting them, the issue is different.
I would then try as a new user. And perhaps with a different desktop. Thanks for those suggestions. I just created a new user, logged into
Prior to systemd I'd do "init 3" to get into text mode. Is it the same now? (Remember, I don't have either Alt key anymore.) that account, and the problem remains exactly the same.
I don't remember using the hardware scan module. I thought it printed a description only.
That's what I was expecting. But (surprise!) no. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* ken
On 03/28/2018 04:55 PM, Carlos E. R. wrote:
On 2018-03-28 22:40, ken wrote:
On 03/28/2018 09:15 AM, Carlos E. R. wrote:
YAST_KEYBOARD="spanish,pc104" Yay! I'm not crazy!! :) I think you may need: YAST_KEYBOARD="us,pc104" That's what I already have, and what I've had since this problem began... maybe I had it there before the problem occurred also, I don't know. Here's what I noted in my original post here:
Looking around in logs and configs, I found the keyboard specified in /etc/sysconfig/keyboard to be "pc104". I can't say for certain whether that is correct or incorrect, except that "pc104" was mentioned in the log file "/var/log/YaST2/y2log" several times on or about the date/time I ran the hardware scan. So it is highly suspect. Here's that final line from the "keyboard" file:
YAST_KEYBOARD="english-us,pc104"
Does anyone have a more cautious and/or informed solution or suggestion? YaST --> hardware setup --> System keyboard layout. Did that... many times... and once again on your suggestion. No change.
I don't, however, think that is the cause of the problem because that same exact screen comes up during install and my keyboard was fine immediately after completing that install. I would try changing the setting in text mode, and testing it there. If it works there, but not on X after starting them, the issue is different.
Prior to systemd I'd do "init 3" to get into text mode. Is it the same now? (Remember, I don't have either Alt key anymore.)
I would then try as a new user. And perhaps with a different desktop. Thanks for those suggestions. I just created a new user, logged into that account, and the problem remains exactly the same.
I don't remember using the hardware scan module. I thought it printed a description only.
That's what I was expecting. But (surprise!) no.
do you have a spare keyboard to try? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/28/2018 08:14 PM, Patrick Shanahan wrote:
do you have a spare keyboard to try?
Well, I do have an old Mac (USB) keyboard, and I thought of seeing what would happen to that if I plugged it in. But whether it worked or didn't, I don't see what it would tell me (definitively). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-03-29 01:52, ken wrote:
On 03/28/2018 04:55 PM, Carlos E. R. wrote:
On 2018-03-28 22:40, ken wrote:
On 03/28/2018 09:15 AM, Carlos E. R. wrote:
YAST_KEYBOARD="spanish,pc104" Yay! I'm not crazy!! :) I think you may need: YAST_KEYBOARD="us,pc104" That's what I already have, and what I've had since this problem began... maybe I had it there before the problem occurred also, I don't know. Here's what I noted in my original post here:
Looking around in logs and configs, I found the keyboard specified in /etc/sysconfig/keyboard to be "pc104". I can't say for certain whether that is correct or incorrect, except that "pc104" was mentioned in the log file "/var/log/YaST2/y2log" several times on or about the date/time I ran the hardware scan. So it is highly suspect. Here's that final line from the "keyboard" file:
YAST_KEYBOARD="english-us,pc104"
Yes, but that combo is a little different: "english-us" vs "us". You could also try pc105, I think it exists.
Does anyone have a more cautious and/or informed solution or suggestion? YaST --> hardware setup --> System keyboard layout. Did that... many times... and once again on your suggestion. No change.
I don't, however, think that is the cause of the problem because that same exact screen comes up during install and my keyboard was fine immediately after completing that install. I would try changing the setting in text mode, and testing it there. If it works there, but not on X after starting them, the issue is different.
Prior to systemd I'd do "init 3" to get into text mode. Is it the same now? (Remember, I don't have either Alt key anymore.)
Certainly, init 3 works. Also "chvt 1" in a terminal as root, which does the same as ctrl-alt-F1 -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 03/28/2018 09:48 PM, Carlos E. R. wrote:
On 2018-03-29 01:52, ken wrote:
On 03/28/2018 04:55 PM, Carlos E. R. wrote:
On 2018-03-28 22:40, ken wrote:
On 03/28/2018 09:15 AM, Carlos E. R. wrote:
YAST_KEYBOARD="spanish,pc104" Yay! I'm not crazy!! :) I think you may need: YAST_KEYBOARD="us,pc104" That's what I already have, and what I've had since this problem began... maybe I had it there before the problem occurred also, I don't know. Here's what I noted in my original post here:
Looking around in logs and configs, I found the keyboard specified in /etc/sysconfig/keyboard to be "pc104". I can't say for certain whether that is correct or incorrect, except that "pc104" was mentioned in the log file "/var/log/YaST2/y2log" several times on or about the date/time I ran the hardware scan. So it is highly suspect. Here's that final line from the "keyboard" file:
YAST_KEYBOARD="english-us,pc104" Yes, but that combo is a little different: "english-us" vs "us". You could also try pc105, I think it exists.
Okay, yes, I see what you mean. But I don't know that there exists a keyboard value simply "us". Indeed if we look in /usr/share/YaST2/data/languages/ we find what appears to be all the possible languages which yast can associate with a keyboard. Note there is none simply "us". Moreover, this below would explain the difference in your and my YAST_KEYBOARD values: # diff language_en_US.ycp language_es_ES.ycp ... < "keyboard" : "english-us", ---
"keyboard" : "spanish", ....
Is there a way to set a new YAST_KEYBOARD value and then invoke it, staying in my current gnome session?
... I would try changing the setting in text mode, and testing it there. If it works there, but not on X after starting them, the issue is different. Prior to systemd I'd do "init 3" to get into text mode. Is it the same now? (Remember, I don't have either Alt key anymore.) Certainly, init 3 works.
Also "chvt 1" in a terminal as root, which does the same as ctrl-alt-F1
Very cool. Then how do I come back after "chvt 1"...? "chvt 5"? (I seem to recall (for people with a working "Alt" key) it was "Alt-F9".) And is my previous gnome session still running the entire time...? so I can come back into it? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-03-30 17:58, ken wrote:
On 03/28/2018 09:48 PM, Carlos E. R. wrote:
YAST_KEYBOARD="english-us,pc104" Yes, but that combo is a little different: "english-us" vs "us". You could also try pc105, I think it exists.
Okay, yes, I see what you mean. But I don't know that there exists a keyboard value simply "us". Indeed if we look in /usr/share/YaST2/data/languages/ we find what appears to be all the possible languages which yast can associate with a keyboard. Note there is none simply "us". Moreover, this below would explain the difference in your and my YAST_KEYBOARD values:
# diff language_en_US.ycp language_es_ES.ycp ... < "keyboard" : "english-us", ---
"keyboard" : "spanish", ....
I don't know where is the list of tokens that can be used for this. And as I live in Spain, I can't look at my computer to see what it would have in the USA. I thought it would be plain "us".
Is there a way to set a new YAST_KEYBOARD value and then invoke it, staying in my current gnome session?
Well, my idea was to try in one of the text consoles. Maybe log in as root in one, fir up yast (yes, yast works also in text mode), and see how the keyboard behaves. Try several combinations, one should work.
... I would try changing the setting in text mode, and testing it there. If it works there, but not on X after starting them, the issue is different. Prior to systemd I'd do "init 3" to get into text mode. Is it the same now? (Remember, I don't have either Alt key anymore.) Certainly, init 3 works.
Also "chvt 1" in a terminal as root, which does the same as ctrl-alt-F1
Very cool.
Then how do I come back after "chvt 1"...? "chvt 5"? (I seem to recall (for people with a working "Alt" key) it was "Alt-F9".)
chvt 7 on openSUSE at least.
And is my previous gnome session still running the entire time...? so I can come back into it?
Certainly. :-) -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
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
On 2018-03-28 22:10, ken wrote:
On 03/28/2018 09:09 AM, Anton Aylward wrote:
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.
Yes, but the entry "YAST_KEYBOARD" is specific to openSUSE (yast part in the name). -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 03/28/2018 04:50 PM, Carlos E. R. wrote:
On 2018-03-28 22:10, ken wrote:
On 03/28/2018 09:09 AM, Anton Aylward wrote:
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. Yes, but the entry "YAST_KEYBOARD" is specific to openSUSE (yast part in the name).
What I meant was that, in some hardware configurations the same value must be set in more than one place, the hostname, for instance. And if in such a circumstance there are different and incompatible values set, then that subsystem could become unusable. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 28/03/18 09:09 AM, Anton Aylward wrote:
On 27/03/18 10:34 PM, ken wrote:
I'm on 42.3. What are you running?
[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
All this leads me to believe that this is an irrelevancy.
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.
You asked
Do you have anything in your /etc/sysconfig/keyboard at all?
And I pointed out that all the entries were either "" or "no" which further leads me to believe it is irrelevant. You said
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.
Well, no. FOSS also means that the wheel gets invented many times over, and there are shifts under-way that are dramatic. we've seen the shift with systemd which has rendered abut 90% of what you knew pre-20010 or so about system administration irrelevant. We have Wayland coming and ... Well look at the "what requires" (use Yast if you are so inclined, or zypper if not) for wayland and you'll find such things as 'kwin', 'kwin5', 'plasma-workplace', 'libQt5Compositor5', ... I don't know enough about Gnome to know if the references there are meaningful. You might read up on the "Weston" package. The more I drill down the more I see the system -- openSUSE at any rate -- working around 'event management'. Comparisons with CentOS are obviously not relevant. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Anton Aylward -
Carlos E. R. -
ken -
Patrick Shanahan