From: Thibaut Girka <thib@sitedethib.com>
To: "Lisandro Damián Nicanor Pérez Meyer" <perezmeyer@gmail.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, 01 May 2011 22:26:42 +0200 [thread overview]
Message-ID: <1304281602.2461.36.camel@debian-thib> (raw)
In-Reply-To: <201105011651.30306.perezmeyer@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]
Le dimanche 01 mai 2011 à 16:51 -0300, Lisandro Damián Nicanor Pérez
Meyer a écrit :
> On Dom 01 May 2011 16:40:39 Thibaut Girka escribió:
> > [Sorry for the duplicate mail sent earlier to debian-kernel]
> >
> > This whole bug really looks like #615598.
> > This might be a bug in nouveau or in the kernel.
> >
> > Did the initial "breakage" of the screens occur with 2.6.38?
> > If so, you may want to try fixing your EDID info has explained in a
> > similar bug report[1], but be careful, it may cause more harm if
> > something goes wrong.
> > If you decided to do so, please check if the corruption appears again.
> >
> > [1] https://bugs.freedesktop.org/show_bug.cgi?id=34554
>
> Considering my video card is an Ati, wich I suspect doesn't use nouveau, it
> must not be this last one.
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?
Anyway, I'd be really interested to hear from Stuart Pook: his story
sounds exactly like mine.
> And at least in my case, my card was working with a 2.6.38 kernel without
> problems, except I am missing something here.
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.
But I'm no expert, and since this method tempers with your hardware, I'd
recommend you to be cautious.
Regards,
Thibaut Girka.
[-- 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:26 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 [this message]
2011-05-01 20:47 ` Lisandro Damián Nicanor Pérez Meyer
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=1304281602.2461.36.camel@debian-thib \
--to=thib@sitedethib.com \
--cc=622993@bugs.debian.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jrnieder@gmail.com \
--cc=perezmeyer@gmail.com \
--cc=slp12227@pook.it \
/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.