On Tue, Jun 22, 2010 at 7:07 PM, Alex Deucher <alexdeucher@xxxxxxxxx> wrote: > On Tue, Jun 22, 2010 at 12:39 PM, Corbin Simpson > <mostawesomedude@xxxxxxxxx> wrote: >> On Tue, Jun 22, 2010 at 9:05 AM, Octoploid <Cryptooctoploid@xxxxxxxxx> wrote: >>> Octoploid wrote: >>> >>>> The following EDID checksum errors are spamming my syslog. >>>> (Everything is working fine and there are no other problems >>>> except these somewhat annoying messages): >>>> >>>> drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is >>>> 128 >>> >>> This patch helps: >>> http://lists.freedesktop.org/archives/dri-devel/2010-April/000255.html >> >> Your monitor sucks. Don't take it personally; lots of monitors suck. >> That patch just gives you the option to forcibly use monitors with >> EDIDs that have bad checksums, in case the checksum is the only bad >> part of an otherwise valid EDID. > > IIRC, ajax sent a patch a while back to just ignore bad checksums > since they are so common. Yes, that is the patch I've linked to above. But it just papers over the problem. Where do the changing (corrupted) raw EDID blocks in my first message come from? >From my monitor? -- controlled by gamma light _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
