All of lore.kernel.org
 help / color / mirror / Atom feed
From: Csillag Kristof <csillag.kristof-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: is there a way to override EDID detection? (for monitor with broken EDID)
Date: Tue, 30 Aug 2011 06:51:10 +0200	[thread overview]
Message-ID: <4E5C6C3E.8040505@gmail.com> (raw)

Dear Nouveau users,

I am stuck with a bogus (but otherwise, great) monitor that can no 
longer properly reports back it's EDID block via a digital connection.
(With most of the video cards, anyway. I suspect a low-level (maybe 
voltage) issue here.)

I can get it to work with the proprietary NVIDIA driver by specifying 
the "ConnectedMonitor" option (to override detecting the monitor, which 
also fails most of the time), and the "CustomEDID" option (to pass in 
the binary EDID info I have captured using one of the rare cards that 
could drive it properly).

With this setup, it works reliably and flawlessly.

The question is, can I do the same thing with free Nouveou driver somehow?

The current statis is that when I try to load the nouveau kernel module, 
it fails to read the EDID, and then the monitor is no longer available.
(The box does not crash, I can still login via the network, and read dmesg.)

Could you please advise me how to proceed?
(Other that replace than fixing the hardware error, which is something I 
can not do now, because of various reasons.)

Thank you for your help:

    Kristof Csillag

             reply	other threads:[~2011-08-30  4:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30  4:51 Csillag Kristof [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-30  5:00 is there a way to override EDID detection? (for monitor with broken EDID) Csillag Kristof

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=4E5C6C3E.8040505@gmail.com \
    --to=csillag.kristof-re5jqeeqqe8avxtiumwx3w@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.