All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 17138] New: Randr12 on nv34m causes colour corruption on laptop panel.
Date: Thu, 14 Aug 2008 11:13:36 -0700 (PDT)	[thread overview]
Message-ID: <bug-17138-8800@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=17138

           Summary: Randr12 on nv34m causes colour corruption on laptop
                    panel.
           Product: xorg
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: murray-Xhi4+0Yxd7rk1uMJSBkQmQ@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Created an attachment (id=18284)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=18284)
vbtracetool vBIOS dump

Starting X with git nouveau and Randr12 disabled works perfectly.
Enabling Randr12 gives a somewhat corrupted screen which is predominantly red.

My system is a Dell Inspiron 5150 with a 1600x1200 screen and an nv34m.

The corruption is only on the internal panel. Any external screen on the VGA
output seems to be fine.

Bug #14403 seemed to be the closest to my experience and so I messed around
with nv_bios.c.

In the function parse_lvds_manufacturer_table_init the section labeled:

   /* adjust some things if straps are invalid (implies the panel has EDID) */

resets the lvdsmanufacturerindex from 3 to 0.

Putting in a line to set this back to 3 (or indeed 1 or 2) makes everything
seem to work fine.

I did a BIOS dump with vbtracetool. Does this help?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2008-08-14 18:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14 18:13 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-17138-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-08-14 18:32   ` [Bug 17138] Randr12 on nv34m causes colour corruption on laptop panel bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-14 19:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-14 19:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-14 19:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-15 18:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-15 21:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-15 23:33   ` 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-17138-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.