[Bug 97816] EDID checksum is invalid - PHL 247ELH

https://bugs.freedesktop.org/show_bug.cgi?id=97816 Martin Peres changed: What|Removed |Added Resolution|--- |INVALID Status|NEW

[Bug 97816] EDID checksum is invalid - PHL 247ELH

https://bugs.freedesktop.org/show_bug.cgi?id=97816 --- Comment #1 from Alex Deucher --- The EDID parser is part of the drm core. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL:

[Bug 97816] EDID checksum is invalid - PHL 247ELH

https://bugs.freedesktop.org/show_bug.cgi?id=97816 Alex Deucher changed: What|Removed |Added Version|7.7 (2012.06) |unspecified Product|xorg

"EDID checksum is invalid"

Linus Torvalds writes: > I'm assuming even the hdmi +5V line is under sw control at least for > power management reasons. Maybe dpms off turns it off, and shouldn't? > My monitor actually says "No HDMI (HML) Cable" when I do "xset dpms > force off". Maybe that's normal, but maybe that's indicativ

"EDID checksum is invalid"

On Wed, Jan 7, 2015 at 6:51 PM, Linus Torvalds wrote: > On Tue, Jan 6, 2015 at 11:32 PM, Daniel Vetter wrote: >> >> Yeah if the edid probe fails userspace will get a hotplug and >> autodisable the output. With a failsafe X session (just a dumb >> terminal) we can avoid that to check that dpms on

"EDID checksum is invalid"

On Wed, Jan 7, 2015 at 6:07 PM, Linus Torvalds wrote: > On Tue, Jan 6, 2015 at 10:21 PM, Robert Morell wrote: >> >> FWIW, I've seen that exact symptom on some monitors when the +5V pin on >> the DVI or HDMI cable from the GPU isn't enabled (or isn't providing >> enough current). Some monitors po

"EDID checksum is invalid"

On Wed, Jan 7, 2015 at 9:51 AM, Daniel Vetter wrote: > > Not sure whether that'd be the same voltage rails, but > i915.disable_power_wells=0 disable all the runtime pm we do (which > does kick in for dpms off and shut down the entire display block and a > bunch more) I still get the "No HDMI (MHL

"EDID checksum is invalid"

On Tue, Jan 6, 2015 at 11:32 PM, Daniel Vetter wrote: > > Yeah if the edid probe fails userspace will get a hotplug and > autodisable the output. With a failsafe X session (just a dumb > terminal) we can avoid that to check that dpms on itself would work or > whether the edid probe fail here is ju

"EDID checksum is invalid"

On Tue, Jan 6, 2015 at 10:21 PM, Robert Morell wrote: > > FWIW, I've seen that exact symptom on some monitors when the +5V pin on > the DVI or HDMI cable from the GPU isn't enabled (or isn't providing > enough current). Some monitors power the i2c/edid/DDC logic from that > +5V either exclusively

"EDID checksum is invalid"

hat to check that dpms on itself would work or whether the edid probe fail here is just indicative of more trouble. Also please boot with drm.debug=0xe, repro and grab dmesg, that might shed some more light on what's failing. Thanks, Daniel >[drm:drm_edid_block_valid [drm]] *ERROR* EDID

"EDID checksum is invalid"

Robert Morell writes: > FWIW, I've seen that exact symptom on some monitors when the +5V pin on > the DVI or HDMI cable from the GPU isn't enabled (or isn't providing > enough current). Some monitors power the i2c/edid/DDC logic from that > +5V either exclusively or when in the DPMS off state, a

"EDID checksum is invalid"

On Tue, Jan 06, 2015 at 10:07:58PM -0800, Keith Packard wrote: > * PGP Signed by an unknown key > > Linus Torvalds writes: > > > it looks like the beginning is the same, but then it just turns to all > > ones at a random point (even *within* a byte). > > Looks like the EDID ROM is dropping off

"EDID checksum is invalid"

Linus Torvalds writes: > it looks like the beginning is the same, but then it just turns to all > ones at a random point (even *within* a byte). Looks like the EDID ROM is dropping off the i2c bus in the middle of the transfer. Wonder if it's being 'clever' if things go too slowly at some point,

"EDID checksum is invalid"

dle it. Does anybody have any idea of why it would do this: [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 111 Raw EDID: 00 ff ff ff ff ff ff 00 10 ac 5c f0 4d 54 31 41 24 18 01 03 80 3e 22 78 ea 0a a5 a2 57 4f a2 28 0f 50 54 a5 4b 00 71 4f 81 00 81

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

(Sorry if I'm spawning a very old thread here). After all this time I have been patching my kernels to workaround [0][1] [0] [1] Some time ago I found [2] and today I finally solved th

[radeon] EDID checksum is invalid

On 12/5/11 3:39 PM, Alexander Beregalov wrote: > At boot time: > [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 206 > Raw EDID: > 27 0f 01 03 80 26 1e 78 2a de 95 a3 54 4c 99 26 > 0f 50 54 bf ef 80 81 80 81 40 71 4f 01 01 01 01 >

Re: [radeon] EDID checksum is invalid

On 12/5/11 3:39 PM, Alexander Beregalov wrote: At boot time: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 206 Raw EDID: 27 0f 01 03 80 26 1e 78 2a de 95 a3 54 4c 99 26 0f 50 54 bf ef 80 81 80 81 40 71 4f 01 01 01 01 01 01 01 01 01 01 30

[radeon] EDID checksum is invalid

On Mon, Dec 5, 2011 at 3:39 PM, Alexander Beregalov wrote: > Hi > > 3.2.0-rc3-00015-gaaa0b4f Is this a regression? If so can you bisect? Are you just having problems with one particular monitor or all monitors? You might try this patch: http://people.freedesktop.org/~agd5f/0001-drm-radeon-kms-

Re: [radeon] EDID checksum is invalid

On Mon, Dec 5, 2011 at 3:39 PM, Alexander Beregalov wrote: > Hi > > 3.2.0-rc3-00015-gaaa0b4f Is this a regression? If so can you bisect? Are you just having problems with one particular monitor or all monitors? You might try this patch: http://people.freedesktop.org/~agd5f/0001-drm-radeon-kms-

[radeon] EDID checksum is invalid

ch is 5120 fbcon: radeondrmfb (fb0) is primary device fb0: radeondrmfb frame buffer device drm: registered panic notifier [drm] Initialized radeon 2.12.0 20080528 for :01:00.0 on minor 0 At boot time: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 206 Raw EDID: 27 0f 0

[radeon] EDID checksum is invalid

ch is 5120 fbcon: radeondrmfb (fb0) is primary device fb0: radeondrmfb frame buffer device drm: registered panic notifier [drm] Initialized radeon 2.12.0 20080528 for :01:00.0 on minor 0 At boot time: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 206 Raw EDID: 27 0f 0

Re: Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

On Monday 02 May 2011 12:25:07 Alex Deucher wrote: [snip] > Can you bisect? I really don't know :-) Haven't done it before. On the other hand, I will surely not have time to do it until next sunday (if I have time next sunday). Sucks, yeah :-/ > I suspect the culprit is one of the patches th

Re: Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

On Lun 02 May 2011 11:23:48 Alex Deucher escribió: [snip] > You might try the patch here: > https://bugs.freedesktop.org/show_bug.cgi?id=27708#c7 > > If you are using a DVI or HDMI port, some TV's don't properly update > their checksums for different ports if they have minor edid changes > for th

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

On Monday 02 May 2011 12:25:07 Alex Deucher wrote: [snip] > Can you bisect? I really don't know :-) Haven't done it before. On the other hand, I will surely not have time to do it until next sunday (if I have time next sunday). Sucks, yeah :-/ > I suspect the culprit is one of the patches th

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

On Lun 02 May 2011 11:23:48 Alex Deucher escribi?: [snip] > You might try the patch here: > https://bugs.freedesktop.org/show_bug.cgi?id=27708#c7 > > If you are using a DVI or HDMI port, some TV's don't properly update > their checksums for different ports if they have minor edid changes > for th

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

2011/5/2 Lisandro Dami?n Nicanor P?rez Meyer : > On Lun 02 May 2011 11:23:48 Alex Deucher escribi?: > [snip] >> You might try the patch here: >> https://bugs.freedesktop.org/show_bug.cgi?id=27708#c7 >> >> If you are using a DVI or HDMI port, some TV's don't properly update >> their checksums for di

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

2011/5/1 Lisandro Dami?n Nicanor P?rez Meyer : > On Dom 01 May 2011 18:09:27 Thibaut Girka escribi?: > [snip] >> I'm not talking about ignoring broken EDIDs, but about actually fixing >> them[1]. > > This is clearly not my problem. I have two monitors, both the same brand and > model. One is connec

Re: Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

2011/5/2 Lisandro Damián Nicanor Pérez Meyer : > On Lun 02 May 2011 11:23:48 Alex Deucher escribió: > [snip] >> You might try the patch here: >> https://bugs.freedesktop.org/show_bug.cgi?id=27708#c7 >> >> If you are using a DVI or HDMI port, some TV's don't properly update >> their checksums for di

Re: Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

2011/5/1 Lisandro Damián Nicanor Pérez Meyer : > On Dom 01 May 2011 18:09:27 Thibaut Girka escribió: > [snip] >> I'm not talking about ignoring broken EDIDs, but about actually fixing >> them[1]. > > This is clearly not my problem. I have two monitors, both the same brand and > model. One is connec

Re: Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

On Dom 01 May 2011 18:09:27 Thibaut Girka escribió: [snip] > I'm not talking about ignoring broken EDIDs, but about actually fixing > them[1]. This is clearly not my problem. I have two monitors, both the same brand and model. One is connected to the VGA output and the other one on the DVI. No

Re: Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

Le dimanche 01 mai 2011 à 17:47 -0300, Lisandro Damián Nicanor Pérez Meyer a écrit : [snip] > Did you mean the patch to tell dri to forget about bad checksums? If so, I > already tried it and worked fine. > > If you are talking about something else, please give me some link :-) I'm not talking a

Re: Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

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 wh

Re: Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

On Dom 01 May 2011 17:26:42 Thibaut Girka escribió: [snip] > My bad, overlooked it since Stuart uses nouveau. However, it might be > related nonetheless (and might be a completely different issue as well). > Did your monitor fail right after an upgrade? Yes, but I failed to check the versions of

Re: Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

Le dimanche 01 mai 2011 à 16:51 -0300, Lisandro Damián Nicanor Pérez Meyer a écrit : > On Dom 01 May 2011 16:40:39 Thibaut Girka escribió: > > [Sorry for the duplicate mail sent earlier to debian-kernel] > > > > This whole bug really looks like #615598. > > This might be a bug in nouveau or in the

Re: Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

On Dom 01 May 2011 16:40:39 Thibaut Girka escribió: > [Sorry for the duplicate mail sent earlier to debian-kernel] > > This whole bug really looks like #615598. > This might be a bug in nouveau or in the kernel. > > Did the initial "breakage" of the screens occur with 2.6.38? > If so, you may wan

Re: Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

[Sorry for the duplicate mail sent earlier to debian-kernel] This whole bug really looks like #615598. This might be a bug in nouveau or in the kernel. Did the initial "breakage" of the screens occur with 2.6.38? If so, you may want to try fixing your EDID info has explained in a similar bug repo

Re: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

el: : [4.081142] [drm] nouveau :01:00.0: Setting dpms mode 3 on vga encoder (output 2) May 1 12:26:42 kooka kernel: : [4.081148] [drm] nouveau :01:00.0: Setting dpms mode 3 on TV encoder (output 3) May 1 12:26:42 kooka kernel: : [4.255585] [drm:drm_edid_block_valid]*ERROR*

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

Le dimanche 01 mai 2011 ? 17:47 -0300, Lisandro Dami?n Nicanor P?rez Meyer a ?crit : [snip] > Did you mean the patch to tell dri to forget about bad checksums? If so, I > already tried it and worked fine. > > If you are talking about something else, please give me some link :-) I'm not talking a

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

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

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

Le dimanche 01 mai 2011 ? 16:51 -0300, Lisandro Dami?n Nicanor P?rez Meyer a ?crit : > On Dom 01 May 2011 16:40:39 Thibaut Girka escribi?: > > [Sorry for the duplicate mail sent earlier to debian-kernel] > > > > This whole bug really looks like #615598. > > This might be a bug in nouveau or in the

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

[Sorry for the duplicate mail sent earlier to debian-kernel] This whole bug really looks like #615598. This might be a bug in nouveau or in the kernel. Did the initial "breakage" of the screens occur with 2.6.38? If so, you may want to try fixing your EDID info has explained in a similar bug repo

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

On Dom 01 May 2011 18:09:27 Thibaut Girka escribi?: [snip] > I'm not talking about ignoring broken EDIDs, but about actually fixing > them[1]. This is clearly not my problem. I have two monitors, both the same brand and model. One is connected to the VGA output and the other one on the DVI. No

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

On Dom 01 May 2011 17:26:42 Thibaut Girka escribi?: [snip] > My bad, overlooked it since Stuart uses nouveau. However, it might be > related nonetheless (and might be a completely different issue as well). > Did your monitor fail right after an upgrade? Yes, but I failed to check the versions of

every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

Setting dpms mode 3 on TV encoder (output 3) May 1 12:26:42 kooka kernel: : [4.255585] [drm:drm_edid_block_valid]*ERROR* EDID checksum is invalid, remainder is 34 May 1 12:26:42 kooka kernel: : [4.255598] [drm:drm_edid_block_valid]*ERROR* EDID checksum is invalid, remainder is 34 May 1 12:

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

On Dom 01 May 2011 16:40:39 Thibaut Girka escribi?: > [Sorry for the duplicate mail sent earlier to debian-kernel] > > This whole bug really looks like #615598. > This might be a bug in nouveau or in the kernel. > > Did the initial "breakage" of the screens occur with 2.6.38? > If so, you may wan

Re: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

> except that the kernel tells me that the EDID data is not correct every > 10 seconds. Is there a way to make it stop? [...] > [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder > is 34 > [drm:drm_edid_block_valid] *ERROR* Raw EDID: >

every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

> except that the kernel tells me that the EDID data is not correct every > 10 seconds. Is there a way to make it stop? [...] > [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder > is 34 > [drm:drm_edid_block_valid] *ERROR* Raw EDID: >