Keyboard becomes unresponsive under the GUI.
Hi: being in the GUI, the keyboard suddenly becomes unresponsive and I have no remedy but to press the machine's reset button. I have never observed this failure while in one of text consoles (/dev/ttyN). When booting, the screen first prints data pertaining to the graphics card (Nvidia). Then:
AMIBIOS(c) 2003 American Megatrends, Inc. P4i65G BIOS P1.00 and line 25 reads: <big number sequence>-INTEL-P4i6G013-Y2KC The keyboard is USB. I have it plugged into one of the machine USB jacks. Code:
root@local:~# lspci |
Holy cow...that is strange...
Does it work in single-user mode? Is hal being loaded properly? Are the appropriate hid modules loaded? I know it's probably a software issue of some kind, as you mentioned that unless Legacy USB support is enabled, it won't work, but I've had more than my fair share of bad hardware... Does it happen on ALL USB ports on the system, or just those on one header? I had a board once where the ground pin on one USB header somehow became disconnected. Wiggling the plug would work for a while, then it would quit on me. I eventually repaired it, after I did a little investigation. (Not saying yours is hardware related, but maybe?) Does it happen with all keyboards, or just one? Again, I had a keyboard where some of the internal connections had worked loose. Are other USB devices similarly affected? Does the keyboard work under other operating systems/distributions? I know you've probably been through all these possibilities...I just really have nothing... |
Thanks for your post. I have two machines and two keyboards, both of them USB. Let's call them machine mA and machine mX, keyboard kA and keyboard kX. The failure happens with kdb kX connected to mach mX. Mach mX works fine with kdb kA works fine. Mach mA with kbd kX work fine too. Summarizing:
Code:
mach kbd performance Sometimes the failure includes unresponsiveness of the mouse too. Under Debian 7.4, always under the GUI, both keyboard and mouse stopped responding. As the table above shows, I can't speak of a "guilty" keyboard or a "guilty" machine. Rather, of a guilty machine/keyboard pair. The keyboard is Model no.: GK-070008/U Product name: KB-220e Trade name: KYE SYSTEMS CORP. It comes with a CD labeled KB-220e. But it seems useless for Linux/Unix: there are only two files on it: AUTOEXEC.INF and Setup.exe. Some data gathered during boot. Code:
i8042: PNP: PS/2 Controller [PNP0f03:PS2M] at 0x60, 0x64 irq 12 Code:
[ 5.398415] [drm] Initialized drm 1.1.0 20060810 NOTE: I wonder if tinkering with /etc/X11/xorg.conf, section Input device could be of any use. |
I forgot to answer your questions.
Quote:
Quote:
Quote:
Quote:
|
Well, I'm afraid I don't know where to go with this one. I'm not sure what to tell you...
It might help to fiddle with the xorg.conf...having a section just for that keyboard might help. I mentioned hal because a few posts on other boards mentioned it: http://blog.tpa.me.uk/2009/09/22/if-...-slackware-13/ http://blog.tpa.me.uk/2013/11/11/sla...yboard-issues/ I just really don't know... |
I have had similar troubles and as far as I know it's a KDE issue. Something (kwin?) is locking the keyboard.
To confirm, are you able to drop to console when this happens? (Ctrl-Alt-F1). If so you can at least reset things from there. I imagine REISUB will also work so you don't have to hit the reset button: http://blog.tpa.me.uk/2009/08/31/magic-sysrq-reisub/ The bad news is, I didn't figure out why it was happening and I do not remember the last time it happened; it just fixed itself. |
Just out of curiosity I tried it. It seems kind of a cool reset (equivalent to pressing the reset button), because when it reboot fsck began to check the filesystem. But in my case the entire keyboard is dead. No use to press Cntrl-Alt-F1 or Alt+SysRq. I think it could be fixed by a wise option in xorg.conf. Anyways it's kind of an intermitent or aleatory failure. Also, the machine has a very odd issue: When turning it on, I will have no CRT output. The screen will be blank. I must press the reset button and this time I have output on the monitor. However, with another keyboard, the machine, save the cold start issue, works fine. I think the best solution would be to through the USB keyboard to the trash can and buy a PS/2 one. Thanks for your post.
|
Definitely sounds like time for the keyboard to hit the bitbucket.
FWIW, reisub is always better for your system than the reset button: REISUB: unRaw (take control of keyboard back from X), tErminate (send SIGTERM to all processes, allowing them to terminate gracefully), kIll (send SIGKILL to all processes, forcing them to terminate immediately), Sync (flush data to disk), Unmount (remount all filesystems read-only), reBoot. Reset: DIE DIE DIE MWAHAHAHAHAHAHA! |
I see. Well, glad to know you.
|
All times are GMT -5. The time now is 11:24 AM. |