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 30086] New: Nouveau fails with unreadable EDID
Date: Wed,  8 Sep 2010 04:55:47 -0700 (PDT)	[thread overview]
Message-ID: <bug-30086-8800@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=30086

           Summary: Nouveau fails with unreadable EDID
           Product: xorg
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: alci-R1JjGarguu0dnm+yROfE0A@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


On a Sony VPCCW2S1E laptop, EDID seems to be somehow unreadable:

get-edid: get-edid version 2.0.0
 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
 Function supported
 Call successful

 VBE version 300
 VBE string at 0x11100 "NVIDIA"

VBE/DDC service about to be called
 Report DDC capabilities

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
 Function supported
 Call successful

 Monitor and video card combination does not support DDC1 transfers
 Monitor and video card combination does not support DDC2 transfers
 0 seconds per 128 byte EDID block transfer
 Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
 Read EDID

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
 Function supported
 Call failed

The EDID data should not be trusted as the VBE call failed
Error: output block unchanged


Video card is a GT 330 M:

01:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 330M]
(rev a2) (prog-if 00 [VGA controller])
    Subsystem: Sony Corporation Device 9072
    Flags: bus master, fast devsel, latency 0, IRQ 16
    Memory at e2000000 (32-bit, non-prefetchable) [size=16M]
    Memory at d0000000 (64-bit, prefetchable) [size=256M]
    Memory at e0000000 (64-bit, prefetchable) [size=32M]
    I/O ports at d000 [size=128]
    Expansion ROM at e3000000 [disabled] [size=512K]
    Capabilities: <access denied>
    Kernel driver in use: nvidia
    Kernel modules: nvidia-current, nouveau, nvidiafb


When loading, nouveau driver can't find the laptop's LCD screen, and display is
black.
Notice that proprietary NVidia driver has the same problem, but it offers a
workaround with the customEDID option:

Option "CustomEDID" "DFP-0:/etc/X11/SNY05FA.bin"


Nouveau does not seem to have such an option... Is there a workaround for
nouveau? Or is there a way to find why the EDID cannot be read?

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

             reply	other threads:[~2010-09-08 11:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 11:55 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-30086-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-09-08 12:37   ` [Bug 30086] Nouveau fails with unreadable EDID bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-08 14:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-09  9:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-09 17:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-09 18:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-09 21:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-09 22:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-09 22:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-13  7:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-13  7:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-13  7:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-13  7:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-13  7:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-13  7:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-13  7:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-13  7:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-13 13:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-13 15:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-13 15:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-13 15:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-13 22:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-14  9:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-14 14:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-10 17:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-24 14:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-12  5:44   ` 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-30086-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.