r700 status?

[agd5f]

Is this a recent happening? I.e., did older kernels work correctly? If so any chance you can track down the change that caused it? Perhaps the edid checks should be relaxed a bit if the edid is mostly useable. I'd suggest filing a bug (https://bugs.freedesktop.org).

[sgcb]

This has so far appeared about 50 times.

[drm:edid_is_valid] *ERROR* EDID checksum is invalid, remainder is 170
[drm:edid_is_valid] *ERROR* Raw EDID:
<3>00 ff ff ff ff ff ff 00 04 72 9d 00 fb 28 20 90 .........r...( .
<3>02 13 01 03 68 2c 19 78 2e ee 95 a3 54 4c 43 26 ....h,.x....TLC&
<3>0f 50 54 bf ee 80 a9 c0 71 4f 81 c0 81 00 01 01 .PT.....qO......
<3>01 01 01 01 01 01 31 2e 40 00 62 84 22 30 58 a8 [email protected]."0X.
<3>35 00 bb f9 10 00 00 04 00 00 00 fd 00 37 4b 1e 5............7K.
<3>50 10 00 0a 20 20 20 20 20 20 00 00 00 fc 00 58 P... .....X
<3>32 30 33 48 0a 20 20 20 20 20 20 20 00 00 00 ff 203H. ....
<3>00 4c 46 50 30 42 30 30 39 33 39 30 30 20 00 ce .LFP0B0093900 ..

radeon 0000:01:00.0: VGA-1: EDID invalid.

I was running into these bad EDID checksum errors a few days ago on my dual head setup, and one of my monitors wouldn't display because of it. I'm not sure what fixed it for me. I was trying various things like switching cables/outputs, and rebooting into earlier kernel versions that had previously worked for me (this didn't work for some reason, I kept on seeing the same errors with these past working kernels). Finally I got fed up and hauled the monitor over to another desktop with an nvidia card. Twin view did work there so I knew the monitor wasn't completely defective. I then brought it back to my main desktop and rebooted for some reason, and all of a sudden it started working again. BIOS displayed its POST messages on the second monitor, my latest git kernel would mirror its start-up messages, and X was able to set up a virtual screen space on the second monitor as well. So everything is now back to normal. I'm not sure what I did, or how this was fixed, but I happy now that I have dual screens back.

[curaga]

Is this a recent happening? I.e., did older kernels work correctly? If so any chance you can track down the change that caused it? Perhaps the edid checks should be relaxed a bit if the edid is mostly useable. I'd suggest filing a bug (https://bugs.freedesktop.org).

I don't know. First this is a new card, I've only had it for about two weeks; and this is the first time I tried KMS on it.

Is the bug the unnecessary repeating? 'Cause everything seems to work fine, including the KMS console.

[bridgman]

The bug would be reporting repeated error messages when the display actually worked OK, and the solution would be trying to find a more tolerant decision-making process for EDID errors. Not sure if agd5f actually has a solution in mind (it seems kinda complicated since the driver doesn't know if the display is coming up properly) or is thinking of an option to shut off the error messages.

[curaga]

OK, filed:

https://bugs.freedesktop.org/show_bug.cgi?id=27708

[curaga]

Update on Wine & CnC: Tiberian Sun. Works great now

Previously I had 1.1.38. Encouraged by the commit mentioned by Q, I tried 1.1.43. Perfect! No slowdowns, everything works.