From: "Lisandro Damián Nicanor Pérez Meyer" <perezmeyer@gmail.com>
To: Thibaut Girka <thib@sitedethib.com>
Cc: Stuart Pook <slp12227@pook.it>,
622993@bugs.debian.org, Jonathan Nieder <jrnieder@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."
Date: Sun, 1 May 2011 17:47:34 -0300 [thread overview]
Message-ID: <201105011747.40542.perezmeyer@gmail.com> (raw)
In-Reply-To: <1304281602.2461.36.camel@debian-thib>
[-- Attachment #1: Type: Text/Plain, Size: 995 bytes --]
On Dom 01 May 2011 17:26:42 Thibaut Girka escribió:
[snip]
> My bad, overlooked it since Stuart uses nouveau. However, it might be
> related nonetheless (and might be a completely different issue as well).
> Did your monitor fail right after an upgrade?
Yes, but I failed to check the versions of the software I upgraded :-(
[snip]
> Your case sounds similar, though.
> If the bug is the same, you can easily (even more easily since you have
> an identical screen working just fine) fix your screen, using the method
> mentioned on fdo.
Did you mean the patch to tell dri to forget about bad checksums? If so, I
already tried it and worked fine.
If you are talking about something else, please give me some link :-)
> But I'm no expert, and since this method tempers with your hardware, I'd
> recommend you to be cautious.
OK!
--
May the source be with you.
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-05-01 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201104292156.32388.perezmeyer@gmail.com>
[not found] ` <20110430010752.GA6907@elie>
[not found] ` <201104292359.45739.perezmeyer@gmail.com>
2011-04-30 4:11 ` every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..." Jonathan Nieder
2011-05-01 15:26 ` Bug#622993: " Stuart Pook
2011-05-01 19:40 ` Thibaut Girka
2011-05-01 19:51 ` Lisandro Damián Nicanor Pérez Meyer
2011-05-01 20:26 ` Thibaut Girka
2011-05-01 20:47 ` Lisandro Damián Nicanor Pérez Meyer [this message]
2011-05-01 21:09 ` Thibaut Girka
2011-05-01 21:31 ` Lisandro Damián Nicanor Pérez Meyer
2011-05-02 14:23 ` Alex Deucher
2011-05-02 14:50 ` Lisandro Damián Nicanor Pérez Meyer
2011-05-02 15:25 ` Alex Deucher
2011-05-02 16:56 ` Lisandro Damián Nicanor Pérez Meyer
2011-05-01 20:48 ` Stuart Pook
2014-02-17 3:39 ` Lisandro Damián Nicanor Pérez Meyer
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=201105011747.40542.perezmeyer@gmail.com \
--to=perezmeyer@gmail.com \
--cc=622993@bugs.debian.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jrnieder@gmail.com \
--cc=slp12227@pook.it \
--cc=thib@sitedethib.com \
/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.