From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 75203] [NVE6] Asus Maximus IV GENE-Z - Nvidia GTX660 - Strange pink line on left screen side
Date: Wed, 19 Feb 2014 18:22:07 +0000 [thread overview]
Message-ID: <bug-75203-8800-keSQVdevZp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75203-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 866 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=75203
Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Asus Maximus IV GENE-Z - |[NVE6] Asus Maximus IV
|Nvidia GTX660 - Strange |GENE-Z - Nvidia GTX660 -
|pink line on left screen |Strange pink line on left
|side |screen side
--- Comment #6 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
I wonder if playing with xrandr settings will make the line go away.
Take a look at "xrandr --props". Things like "scaling mode" and the various
"underscan" stuff.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2168 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2014-02-19 18:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 12:46 [Bug 75203] New: Asus Maximus IV GENE-Z - Nvidia GTX660 - Strange pink line on left screen side bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-75203-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-02-19 12:47 ` [Bug 75203] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-19 12:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-19 14:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-19 14:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-19 14:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-19 18:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-02-23 14:31 ` [Bug 75203] [NVE6] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-23 14:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-05 17:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-05 17:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-15 16:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-22 22:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-07 8:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-15 23:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-16 6:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-23 6:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-19 5:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-19 5:56 ` 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-75203-8800-keSQVdevZp@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.