[Bug 95200] New: IOQuake is jerky

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Apr 29 08:17:31 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=95200

            Bug ID: 95200
           Summary: IOQuake is jerky
           Product: DRI
           Version: unspecified
          Hardware: x86 (IA32)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: sitsofe at yahoo.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Description of the problem:
Running IOQuake shows very low frame rates even on the title screen with the
animated logo.

Steps to reproduce:
1. Boot Ubuntu 16.04 with a 4.6.0-994-generic #201604282201 kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2016-04-29-wily/
on an EeePC 900.
2. Run IOQuake.
3. Skip past opening video.

Expected results:
Rendering to be smooth.

Actual results:
Rendering is noticeably laggy showing only a frame per second if that. This
persists when a game match is started.

How reproducible is the problem?
It is reproducible every time.

Additional information:
Opening the console with ~ makes things a little bit better. Turning on the
TearFree option in Xorg.conf and restarting X seems to resolve the issue.

Version information:
EeePC 900
Xubuntu 16.04 i686
Intel 915GM
xorg 1:7.7+13ubuntu3
xserver-xorg 1:7.7+13ubuntu3
xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
4.6.0-994-generic #201604282201 kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2016-04-29-wily/

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160429/0a017bdf/attachment.html>


More information about the intel-gfx-bugs mailing list