Description of problem: That is something quite new in dmesg: [ 291.731264] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 85 [ 291.731270] Raw EDID: [ 291.731275] ff 00 48 43 48 59 33 30 35 31 31 34 0a 20 20 00 [ 291.731278] 21 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 291.731282] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 291.731285] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 291.731288] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 291.731292] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 291.731295] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 291.731298] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff As a matter of fact Xorg puts in Xorg.0.log something like this: [ 53.738] (II) RADEON(0): Monitor name: SyncMaster [ 53.738] (II) RADEON(0): Serial No: HCHY305114 [ 53.738] (II) RADEON(0): EDID (in hex): [ 53.738] (II) RADEON(0): 00ffffffffffff004c2d91003132424e [ 53.738] (II) RADEON(0): 0d0f0103802b20a02ad0c4a15a4b9723 [ 53.738] (II) RADEON(0): 174f57bfef80a9408180010101010101 [ 53.738] (II) RADEON(0): 010101010101ed3240a060b023403020 [ 53.738] (II) RADEON(0): 2400b0441100001a000000fd00384b1e [ 53.738] (II) RADEON(0): 510e000a202020202020000000fc0053 [ 53.738] (II) RADEON(0): 796e634d61737465720a2020000000ff [ 53.739] (II) RADEON(0): 00484348593330353131340a20200021 So how these two are supposedly related? The first line of this "invalid EDID" looks, minus few characters, like an ASCI encoded monitor serial number but what about the rest? "ATI Technologies Inc RV280 [Radeon 9200 PRO]" graphics card reported in Xorg.0.log as "Chipset: "ATI Radeon 9250 5960 (AGP)" (ChipID = 0x5960)". Version-Release number of selected component (if applicable): kernel-3.3.0-0.rc3.git6.2.fc18.x86_64 Additional info: I cannot be sure that this showed up only with 3.3.0-0.rc3.git6.2.fc18.x86_64, as I do not look at dmesg output every time, but quite recently nothing of that sort was ever present. BTW - what /usr/bin/edid-decode from xorg-x11-utils expects for an input it is hard to guess. No docs of any kind, a constant response "No such file or directory" to whater option is passed, and it will accept really any input but output seems to be totally disconnected with reality.
I did boot in the meantime 3.3.0-0.rc3.git6.2.fc18.x86_64 and other kernels too and this "*ERROR* EDID checksum is invalid" complaint did not show up. Some race somwhere without real consequnces or somebody truly cares?
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.