From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thibaut Girka 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 Message-ID: <1304281602.2461.36.camel@debian-thib> References: <201104292156.32388.perezmeyer@gmail.com> <4DBD7B90.8080509@pook.it> <1304278839.2461.18.camel@debian-thib> <201105011651.30306.perezmeyer@gmail.com> Reply-To: Thibaut Girka , 622993@bugs.debian.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-T90dD5eDgo8qIHqLhQ7d" Return-path: Resent-To: debian-bugs-dist@lists.debian.org Resent-Message-ID: In-Reply-To: <201105011651.30306.perezmeyer@gmail.com> List-URL: List-Post: List-Help: List-Subscribe: List-Unsubscribe: To: Lisandro =?UTF-8?Q?Dami=C3=A1n?= Nicanor =?UTF-8?Q?P=C3=A9rez?= Meyer Cc: Stuart Pook , 622993@bugs.debian.org, Jonathan Nieder , dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --=-T90dD5eDgo8qIHqLhQ7d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Le dimanche 01 mai 2011 =C3=A0 16:51 -0300, Lisandro Dami=C3=A1n Nicanor P= =C3=A9rez Meyer a =C3=A9crit : > On Dom 01 May 2011 16:40:39 Thibaut Girka escribi=C3=B3: > > [Sorry for the duplicate mail sent earlier to debian-kernel] > >=20 > > This whole bug really looks like #615598. > > This might be a bug in nouveau or in the kernel. > >=20 > > 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. > >=20 > > [1] https://bugs.freedesktop.org/show_bug.cgi?id=3D34554 >=20 > Considering my video card is an Ati, wich I suspect doesn't use nouveau, = it=20 > 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= =20 > 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. --=-T90dD5eDgo8qIHqLhQ7d Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAABCAAGBQJNvcH9AAoJEOY0VNOn/l3W2OUQAIuJEuwkPkjcX3rLDRt5Fh3S T5Nb2dAezwVomz2dzVn6nWvtRCsZuz8KTO6ue74Aw2VdVSZtr/iJ+5LSf5cIu1pr oYUTGBXY7125bKDjI5JnbBNCfEoaAj/qnl/ko+mhZ/ZoujFBVifHhT6TnxjMd+yU 7ecUswpaVx8MJKac9xKnBJvY2HwqzusOwx82AF8tUEC8WgS6tUuMaVFbLH7FIM+k tl4zhj8+hmsclytrWo2jaTL3MlvJd84idsoP1K+4hlFnxn5SjDQmu1F+Q5oBNcIH cG3SCgU794t2ttSYXwnUFVIL8ejM0w54L3PFm404IQLqk8tYBtE58gxCf2bRuCtP kPaZBWOwuiPQJEtK0svzov1qgzwfQgC2UwmSD5Wg7BY2qnI1C0qozJUp8X7Mzr+N XdxBGimh/PHTQpHcFQQvz/kZOX8l1BfdOhWsvudXdxGRuDRmOxyb5NbP5EOgaKPv LKQN+7WHFIaUTnzAxKQfPtL6di4CXGMBzE9BGI9vEb88p1jYzspXKQmY6BQ3wAxZ RKP5FKKFHUPuCmCXMhRemthinFxI9+UUHbIPsbxe7KQK5w2kwi6c7Zno6NRXaJkY SGfo4Fh7nyPxJrsE1gsnSNP1D4nrOhImP5LAztvlJ3AjCEvPR3kI4I3VDuljtkLn 9xWTFfvCeHxbDHAmxrHk =FSEu -----END PGP SIGNATURE----- --=-T90dD5eDgo8qIHqLhQ7d--