[arch-general] Keyboard and mouse not working in X
Last night, I updated my system with everything from the past week or so. Everything went smoothly. Today, however, I discovered that upon launching X, using, for instance,
xinit /usr/bin/xterm my computer stops responding to my USB keyboard and mouse. I can't even switch back to the console using CTRL-ALT-FN. If I SIGTERM the process from ssh, X closes normally and my keyboard resumes function in the console. I've checked, and none of the files in /etc/X11 were modified anytime recently.
Any advice? pants.
Hi, Am 16.06.2012 00:35, schrieb pants:
Any advice?
What does the logfile say? Any errors or something like that? Best regards, Karol Babioch
On Sat 16 Jun 2012 01:15:07 AM CEST, Karol Babioch wrote:
Hi,
Am 16.06.2012 00:35, schrieb pants:
Any advice?
What does the logfile say? Any errors or something like that?
Best regards, Karol Babioch
Had the same problem one week ago, i was able to switch back to a tty with sysrq r. What i did was reinstall the linux package (compat wireless unistall messed the modules i think) and rebuild the initramfs. Maybe it helps. Cheers, Jonas
What i did was reinstall the linux package (compat wireless unistall messed the modules i think) and rebuild the initramfs.
Unfortunately, I do not think this will help. This morning, before discovering this problem, I installed a new version of the linux package (3.4.2-2) and rebuilt the initramfs without installing any other packages, and haven't installed any other packages since. I can't imagine that repeating this would be a solution. pants.
Sorry for double posting, but this is just to report that the sysreq trick you recommended does not work in my case. Indeed, not even the capslock light responds; it's like the keyboard is being completely ignored by my system. pants.
More double posting, but there's an update: if I unplug the keyboard and mouse and then reconnect them once X is running, they work fine and they continue to work after closing X and reopening it. This does not, however, continue to be true after rebooting. pants. On Fri, Jun 15, 2012 at 05:14:53PM -0700, pants wrote:
Sorry for double posting, but this is just to report that the sysreq trick you recommended does not work in my case. Indeed, not even the capslock light responds; it's like the keyboard is being completely ignored by my system.
pants.
What does the logfile say? Any errors or something like that?
I could find no relevant errors. Have a look for yourself, though: http://pastebin.com/MnCLjL3T pants.
participants (3)
-
Jonas Jelten
-
Karol Babioch
-
pants