|
Keyboard freeze
Hi,
I use Debian sid on my laptop and everythings works fine. Some week ago I found your repository and I immediately added it in my sources.list and upgraded to 2.6.31 kernel. However I've a big problem with the lastest two revision that I never rescountered before, after some minutes (15-20) my keyboard won't accept any input and repeat continuously the lastest accepted key. linux-image-2.6.31-1.dmz.2-liquorix-686 is first image with this problem. Back to top |
|||||
|
Maybe this is related:
"Currently known problems? 1. Some keyboard failures with Xorg - needs retesting. Most keyboards are fine 2. More likely to show up bugs in *other* code due to being much more aggressive at using multiple CPUs so race conditions will show up more frequently. I'm working on all of the above now and have no time frame whatsoever for when they might be fixed since I don't know what's causing them (except for 2). ** KNOWN DRIVER INTERACTIONS ** Drivers that are known to break/hang with BFS currently: Some keyboard/Xorg thing - needs retesting on 302 I have a report that switching from xorg-driver-input-keyboard to xorg-driver-input-evdev and changing xorg.conf will make the problem go away for now." ck.kolivas.org/patches/bfs/bfs-faq.txt Back to top |
|||||
|
2.6.31-1.dmz.2 was using CFS.
Also, Con updated his faq to say this. :: Code :: 1. Some keyboard failures with Xorg. Most keyboards are fine. This bug appears
to occur with mainline too only much less frequently, so it's more likely an xorg/hal bug! This is not necessarily a kernel bug, but some sloppiness of how the keyboard is handled in Xorg. I'll keep you guys up2date with this. Most likely, 2.6.32 will expose these issues the most and the bugs will get fixed upstream since 2.6.32 includes all the improvements to increase throughput and reduce latency for CFS at the cost of some racing possibilities. Also, :: Code :: I have a report that switching from xorg-driver-input-keyboard to
xorg-driver-input-evdev and changing xorg.conf will make the problem go away for now. Everyone should be on evdev by now, the old keyboard driver is deprecated and will eventually be removed - let hal handle the keyboard :). Back to top |
|||||
|
I am also showing this behavior on my laptop. I will try the above fix.
Back to top |
|||||
|
|
|||||
|
EDIT: xorg.conf problems fixed. Working fine now with 2.6.31-2.dmz.1-liquorix-686 and xserver-xorg-input-kbd removed.
--- Hello damentz & other Techpatterns people: I also get keyboard freezes when using your latest kernels, but I can't seem to fix the problem using evdev by itself. Here is the description of the problem I'm having which I posted over at the sidux forum; hopefully one of you guys will be able to give me advice on fixing this. === Hello siduxers: I am running a regularly dist-upgraded install of sidux 2009-01 (ouranos) which is working very well except that on one of the dist-upgrades several months back, my non-standard keyboard keys were no longer recognized (e.g., “Play” and “volume” keys that were linked to Amarok & etc). I can't remember exactly what upgrade did this, as I was very sick over the summer and had to go to the hospital a few times. Anyway, while Googling this “keys not recognized” problem, I saw mention that xserver-xorg-input-kbd should be removed and that only xserver-xorg-input-evdev should be installed. They were both installed on my system, but when I removed xserver-xorg-input-kbd, none of the keys worked while in X. Also, the command dpkg-reconfigure xserver-xorg produces no output at all, not the selection of options and choices that I used to get. Can anyone help me with this rather baffling problem? Below are the contents of my xorg.conf: :: Code :: # /etc/X11/xorg.conf (Xorg X Window System server configuration file)
# # This file was generated by fll_xorgconfig, the F.U.L.L.S.T.O.R.Y. # Xorg Configuration tool. # # Edit this file with caution, and see the xorg.conf(5) manual page. # (Type "man xorg.conf" at the shell prompt.) # Section "ServerFlags" Option "AutoAddDevices" "0" Option "AllowEmptyInput" "0" Option "AllowMouseOpenFail" "true" Option "DontZap" "Off" EndSection Section "Device" Identifier "Device 0" Driver "nvidia" Option "Coolbits" "1" Option "AddARGBGLXVisuals" "true" Option "TripleBuffer" "false" Option "DMAForXv" "true" BoardName "nVidia Corporation GeForce 7050/nForce 610i" BusID "PCI:0:16:0" EndSection Section "Monitor" Identifier "Monitor 0" ModelName "Default Monitor" HorizSync 28-96 VertRefresh 50-75 EndSection Section "Screen" Identifier "Screen 0" Monitor "Monitor 0" DefaultColorDepth 24 SubSection "Display" Depth 8 Modes "1440x900" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1440x900" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1440x900" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1440x900" "1152x864" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "Extensions" Option "Composite" "enable" # Option "RENDER" "disable" EndSection ///Dave Back to top |
|||||
|
Fix this by changing keyboard driver to evdev
Don't remove anything. just change the keyboard driver from "keyboard" to "evdev" and the problem is fixed.
Mike Back to top |
|||||
|
sounds like an easy smxi fix, if evdev installed, then check xorg.conf, and update if required.
Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||