I have been running OpenSUSE on a System 76 Darter laptop for the last several years on OpenSUSE 13.1, 13.2 and now Leap 42.1. I have never had a problem and everything has worked perfectly until last week when the keyboard stopped working properly after resuming from sleep/suspend (probably because of a software update). Something wonky is going on with the keyboard, however, I am able to get the keyboard to start working properly by pressing the Num Lock key twice. Pressing the Num Lock key once puts the keyboard into Num Lock mode and pressing it again turns Num Lock off and goes back to “regular” mode. It appears that the only keys affected by this are the Num Lock character keys such as I, J, K, M, etc. As best as I can tell, those keys appear to be generating an escaped sequence following resume from suspend until I press the Num Lock key twice. My login screen is presented upon resume from suspend and so I cannot determine what characters these keys are generating. Very odd…
So, any ideas on how to fix this? I think that systemd will execute a script on resume from suspend if you put the script in /usr/lib/systemd/system-sleep. Therefore, I created the following script as /usr/lib/systemd/system-sleep/numlock.sh:
#! /bin/sh
numlockx on
numlockx off
I set the file to be executable with chmod a+x, however, it doesn’t work to fix this problem. Any suggestions would be appreciated.
follow those steps:
1- sudo gedit /etc/default/grub
2- find “GRUB_CMDLINE_LINUX_RECOVERY=single” then press enter after that past this "GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash atkbd.reset” http://i.imgur.com/Dy79Eek.png
3-then apply this command to update your grub configuration sudo grub2-mkconfig -o /boot/grub2/grub.cfg
4- reboot your laptop.
after latest update, its not possible to login after Suspend or Hibernate
after several attempts the screen states its impossible to login directly
advises cmd
ctl-alt-f1 for a terminal
then after logging as user, use cmd
sudo loginctl unlock-sessions
then ctl-alt-f7 for the gui (which works)
OK, I figured out what the problem is. Its a new kernel that doesn’t work with my hardware for resuming from suspend. The new kernel that does not work is 4.1.31-30-default whereas the previous kernel works which is 4.1.27-27-default. In fact, all previous kernels have worked since I purchased the System76 Darter laptop almost 3 years ago. I believe that the new 4.1.31-30-default kernel was added within the last 2 weeks. So, I will be filing a bug report on that kernel version.