dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart Pook <slp12227@pook.it>
To: Thibaut Girka <thib@sitedethib.com>
Cc: "Lisandro Damián Nicanor Pérez Meyer" <perezmeyer@gmail.com>,
	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:48:59 +0200	[thread overview]
Message-ID: <4DBDC73B.3080808@pook.it> (raw)
In-Reply-To: <1304281602.2461.36.camel@debian-thib>

On 01/05/11 22:26, Thibaut Girka wrote:
> Anyway, I'd be really interested to hear from Stuart Pook: his story
> sounds exactly like mine.

I'm not sure exactly what to say. My screen/PC died on about 23 February. At that time it would not even show BIOS messages. I started to try and understand what was wrong at the end of March. According to a "ls -lrtc /boot" I was probably running 2.6.37-1-amd64 on 23 February. Let me know if you need more information.

I read with interest the report of how to correct a broken EDID. I might give it a go but not before next week.  https://bugs.freedesktop.org/show_bug.cgi?id=34554

> But I'm no expert, and since this method tempers with your hardware, I'd
> recommend you to be cautious.

Yes, especially as I only have one Benq FP241W.

Stuart

  parent reply	other threads:[~2011-05-01 20:48 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
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 [this message]
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=4DBDC73B.3080808@pook.it \
    --to=slp12227@pook.it \
    --cc=622993@bugs.debian.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jrnieder@gmail.com \
    --cc=perezmeyer@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox