From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 192921] Low frame rates and unrecognized monitor after kernel upgrade
Date: Fri, 20 Jan 2017 03:00:59 +0000 [thread overview]
Message-ID: <bug-192921-2300-rekFad6Imv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-192921-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=192921
--- Comment #4 from stevengruspier@gmail.com ---
xrandr
[CODE]
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 2560 x 1440, current 2560 x 1440, maximum 2560 x 1440
default connected primary 2560x1440+0+0 0mm x 0mm
2560x1440 0.00*
[/CODE]
Glxgears
[CODE]
2799 frames in 5.0 seconds = 559.599 FPS
3023 frames in 5.0 seconds = 604.556 FPS
2909 frames in 5.0 seconds = 581.332 FPS
2969 frames in 5.0 seconds = 593.634 FPS
2996 frames in 5.0 seconds = 598.985 FPS
[/CODE]
I am using wayland, so what is the equivalent of the xorg log file?
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-01-20 3:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 2:39 [Bug 192921] New: Low frame rates and unrecognized monitor after kernel upgrade bugzilla-daemon
2017-01-20 2:40 ` [Bug 192921] " bugzilla-daemon
2017-01-20 2:50 ` bugzilla-daemon
2017-01-20 2:51 ` bugzilla-daemon
2017-01-20 2:57 ` bugzilla-daemon
2017-01-20 3:00 ` bugzilla-daemon [this message]
2017-01-20 3:01 ` bugzilla-daemon
2017-01-20 3:19 ` bugzilla-daemon
2017-01-20 13:21 ` bugzilla-daemon
2017-01-20 16:24 ` bugzilla-daemon
2017-01-20 16:28 ` bugzilla-daemon
2017-01-20 17:03 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-192921-2300-rekFad6Imv@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.