Bug 6540 - Unresponsive keyboard with nvidia libGL
Summary: Unresponsive keyboard with nvidia libGL
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nVidia (proprietary) (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Andy Ritger
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-09 12:16 UTC by Ivan Gyurdiev
Modified: 2006-04-08 23:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Ivan Gyurdiev 2006-04-09 12:16:55 UTC
Versions: This is Fedora Core Rawhide as of Apr 8 (Xorg 7.0+). However, I am
using the xorg server component from FC5, since the latest one causes the nvidia
driver to crash entirely. The driver is 8756 which was just released, as
packaged on livna.org. However, I have seen this problem with the older 8178
driver as well.

Hardware: Nvidia GeForce 6800GS 256.

==================

When playing FPS games, such as the Quake 4 demo, or Call of Duty (via Wine), I
see keyboard glitches - key events would get delayed, and not take effect for a
second or so. For example, if I'm running left, the key would get "stuck" for a
second or so after I stop pressing it, causing me to run into the wall. This
makes FPS games unplayable. 

Today I installed the Mesa libGL by accident, but this showed that the nvidia
glx server with the Mesa glx client do not suffer from the same problem. glxinfo
then shows OpenGL version 1.4, instead of 2.0, but games run without keyboard
problems. After I fixed the issue and loaded the correct nvidia libGL, the
keyboard problem was back.

Will provide further info as necessary..
Comment 1 Ivan Gyurdiev 2006-04-09 16:28:02 UTC
Never mind the report about Mesa vs nvidia-glx - I've been using the nvidia
libGL all along for 32-bit apps. Furthermore when actually trying Mesa, I see
the same bug, so this isn't nvidia's fault.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.