From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 14857] New: randr12 on nv34 broken
Date: Thu, 6 Mar 2008 11:06:08 -0800 (PST) [thread overview]
Message-ID: <bug-14857-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=14857
Summary: randr12 on nv34 broken
Product: xorg
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: peter-sWXtQFFYX8bYtjvyW6yDsg@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=14882)
--> (http://bugs.freedesktop.org/attachment.cgi?id=14882)
Xorg log
When enabling randr12 on my nv34 the image on the screen is unstable. This is
with a single CRT output.
lspci -nn
03:00.0 VGA compatible controller [0300]: nVidia Corporation NV34 [GeForce FX
5500] [10de:0326] (rev a1)
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2008-03-06 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 19:06 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-14857-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-03-06 19:12 ` [Bug 14857] randr12 on nv34 broken bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-06 20:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-08 20:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-15 19:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-27 0:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-29 23:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-14857-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.