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