You are not logged in.
Pages: 1
I have this message at each boot:
[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128
[ 1.765502] Raw EDID:
[ 1.765530] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 1.765559] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 1.765589] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 1.765618] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 1.765647] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 1.765677] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 1.765706] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 1.765735] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 1.765766] radeon 0000:01:00.0: DVI-D-1: Ignoring invalid EDID block 1.I use the open source ati driver with a 6570 AMD graphic card and a Yamakazi catleap monitor (cheap monitor from Korea). I don't remember having had this error with the catalyst driver. Note that the monitor is correctly detected with the correct resolution (2560x1440) and the correct refresh rate so it is probably harmless. I still wonder what causes this error.
Offline
Is DVI-D-1 the output where your display is plugged? If not, that may be the cause. In any case, it is harmless.
Offline
@Pse I think so, although, it is not the name seen by xrandr (DVI-0), but I see:
[ +0.000001] [drm] Connector 0:
[ +0.000001] [drm] HDMI-A-1
[ +0.000001] [drm] HPD4
[ +0.000001] [drm] DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c
[ +0.000000] [drm] Encoders:
[ +0.000001] [drm] DFP1: INTERNAL_UNIPHY2
[ +0.000001] [drm] Connector 1:
[ +0.000001] [drm] DVI-D-1
[ +0.000000] [drm] HPD1
[ +0.000001] [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
[ +0.000001] [drm] Encoders:
[ +0.000000] [drm] DFP2: INTERNAL_UNIPHY
[ +0.000001] [drm] Connector 2:
[ +0.000000] [drm] VGA-1
[ +0.000001] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c
[ +0.000001] [drm] Encoders:
[ +0.000001] [drm] CRT1: INTERNAL_KLDSCP_DAC1and I have indeed 3 connectors (HDMI, DVI, VGA) on my graphic card and the monitor is connected to the DVI monitor. But as you say, I have the correct resolution with the correct refresh rate and the correct dimension; so it should be totally harmless.
Offline
Sorry for necro bump, but I have the same problem. I also use open source drivers for AMD (HD 7850) and I also have a Korean monitor with 2560x1440 resolution that connects via dual link DVI-D cable (although it's Achieva Shimian - but under the hood it's essentially identical to Yamakasi Catleap).
I know the error is harmless, but I think it makes the boot process ugly. Since it's harmless, is there a way to skip that check or at least the part where it shows the error? If it means anything, my monitor briefly goes blank between early boot and EDID checksum error. Other than that, everything works fine.
Offline
Sorry for necro bump, but I have the same problem. I also use open source drivers for AMD (HD 7850) and I also have a Korean monitor with 2560x1440 resolution that connects via dual link DVI-D cable (although it's Achieva Shimian - but under the hood it's essentially identical to Yamakasi Catleap).
I know the error is harmless, but I think it makes the boot process ugly. Since it's harmless, is there a way to skip that check or at least the part where it shows the error? If it means anything, my monitor briefly goes blank between early boot and EDID checksum error. Other than that, everything works fine.
The monitor briefly going blank is a correct behaviour (I think). It's when kms start. The card have to switch to the correct resolution and this cause the monitor briefly going blank. As for the error, as I boot in graphical mode, I just ignore the message.
Offline
The monitor briefly going blank is a correct behaviour (I think). It's when kms start. The card have to switch to the correct resolution and this cause the monitor briefly going blank. As for the error, as I boot in graphical mode, I just ignore the message.
I see. Well, I ignore the message as well, but I'd like to get rid of it if at all possible.
I've seen people mentioning custom EDID as a possible solution, I'll have to look into that. If anyone has useful info about it, feel free to post it.
Offline
I've seen people mentioning custom EDID as a possible solution, I'll have to look into that. If anyone has useful info about it, feel free to post it.
You know, in the end, at least in my case but in yours too apparently, the monitor is correctly detected (resolution, size, refresh rate, everything). So a custom EDID is IMHO a little overkill to solve what finally is a non-problem.
Last edited by olive (2015-01-29 21:39:32)
Offline
Pages: 1