From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 33674] New: KMS, kernel, Second Monitor becomes complete blur when loading fullscreen GL
Date: Fri, 28 Jan 2011 15:31:19 -0800 (PST) [thread overview]
Message-ID: <bug-33674-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=33674
Summary: KMS, kernel, Second Monitor becomes complete blur when
loading fullscreen GL
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: highest
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: oyvinds@everdot.org
On affected system:
1. Load fullscreen OpenGL something which thinks fullscreen means both attached
monitors. This includes kwin and warzone.
2. Kernels 2.6.37-git15 2.6.38-rc1-git2 2.6.38-rc2-git7 show expected on first
monitor and complete blur on second monitor. Total messy blur. Everything works
perfectly with stable 2.6.37-gentoo kernel. I do not know what happened with
<=2.6.37-git15, but I do know 2.6.37-git15 kernels and later are defective.
It would be nice if someone could make two monitors work with OpenGL again
(working kwin is nice).
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-01-28 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 23:31 bugzilla-daemon [this message]
2011-01-28 23:34 ` [Bug 33674] KMS, kernel, Second Monitor becomes complete blur when loading fullscreen GL bugzilla-daemon
2011-01-29 13:28 ` bugzilla-daemon
2011-02-22 3:43 ` bugzilla-daemon
2011-02-27 20:28 ` 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-33674-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox