Bug#622993: every 10s I get [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ...
On 01/05/2011 21:51, Lisandro Damián Nicanor Pérez Meyer wrote: 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. [..] Considering my video card is an Ati, wich I suspect doesn't use nouveau, it must not be this last one. For info, sometimes ago, I also add a problem with spurious [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ... Sorry, I do not remember from which exact kernel version it was. The problems occurs for a second screen on DVI output of a laptop. It was intermittent (ie most of the time, the EDID was correct but sometimes the EDID was read incorrectly and the output was disabled). I solved this by adding options drm_kms_helper poll=N Using this also ameliorate the stability of my suspend to disk. I did not try to remove this setup recently (do not touch a working system!). My graphic card is an Intel: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) Regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 vdanj...@debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial packages: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622993: every 10s I get [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ...
Vincent Danjean wrote: For info, sometimes ago, I also add a problem with spurious [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ... Sorry, I do not remember from which exact kernel version it was. The problems occurs for a second screen on DVI output of a laptop. It was intermittent (ie most of the time, the EDID was correct but sometimes the EDID was read incorrectly and the output was disabled). There was recently (v2.6.39-rc2~3^2~24) an interesting fix in the area: | $ git show v2.6.39-rc2~3^2~24 | commit 4819d2e4310796c4e9eef674499af9b9caf36b5a | Author: Chris Wilson ch...@chris-wilson.co.uk | Date: Tue Mar 15 11:04:41 2011 + | | drm: Retry i2c transfer of EDID block after failure | | Usually EDID retrieval is fine. However, sometimes, especially when the | machine is loaded, it fails, but succeeds after a few retries. | | Based on a patch by Michael Buesch. | | Reported-by: Michael Buesch m...@bu3sch.de | Signed-off-by: Chris Wilson ch...@chris-wilson.co.uk | Reviewed-by: Alex Deucher alexdeuc...@gmail.com | Signed-off-by: Dave Airlie airl...@redhat.com So I'd be interested in results using the kernel from experimental if you're willing. It would also be interesting to know approximately when sometimes ago is --- one month? one year? five years? I solved this by adding options drm_kms_helper poll=N Someone mentioned this workaround on lkml, too. I'm not so fond of workarounds before fixes; they hide bugs. :) Thanks, this seems useful. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622993: every 10s I get [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ...
On 02/05/2011 14:17, Jonathan Nieder wrote: Vincent Danjean wrote: For info, sometimes ago, I also add a problem with spurious [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ... Sorry, I do not remember from which exact kernel version it was. The problems occurs for a second screen on DVI output of a laptop. It was intermittent (ie most of the time, the EDID was correct but sometimes the EDID was read incorrectly and the output was disabled). There was recently (v2.6.39-rc2~3^2~24) an interesting fix in the area: | $ git show v2.6.39-rc2~3^2~24 | commit 4819d2e4310796c4e9eef674499af9b9caf36b5a | Author: Chris Wilson ch...@chris-wilson.co.uk | Date: Tue Mar 15 11:04:41 2011 + | | drm: Retry i2c transfer of EDID block after failure | | Usually EDID retrieval is fine. However, sometimes, especially when the | machine is loaded, it fails, but succeeds after a few retries. | | Based on a patch by Michael Buesch. | | Reported-by: Michael Buesch m...@bu3sch.de | Signed-off-by: Chris Wilson ch...@chris-wilson.co.uk | Reviewed-by: Alex Deucher alexdeuc...@gmail.com | Signed-off-by: Dave Airlie airl...@redhat.com So I'd be interested in results using the kernel from experimental if you're willing. I'm willing (I usually use the latest packaged kernel). However, if I followed correctly the debian-kernel ML, the current experimental kernel does not have the support for Intel wifi 4965 (new 'legacy intel' config option to enable). So, I'm waiting for the next one. It would also be interesting to know approximately when sometimes ago is --- one month? one year? five years? I would say a few months. I solved this by adding options drm_kms_helper poll=N Someone mentioned this workaround on lkml, too. I'm not so fond of workarounds before fixes; they hide bugs. :) You are right. However, when there is no special log and its not easy to reproduce, I usually prefer to wait and see if this is corrected in next kernels. If you want to know, I still have some problems with s2disk. Some kernel are a better than others but having a failure every 10 s2disk at best is very inconvenient for a day-to-day working laptop. I already reported these bugs (even upstream) but, here again, without specific scenario to reproduce, it is very difficult to even tell if the bug has been fixed or not. I switched about 2 months ago to use s2ram instead of s2disk and I did not experiment any crash since. For this particular bug (EDID checksum), I can easily try a new kernel because: - it is easy to workaround again the problem if the bug is not fixed - if the bug is still here, I will just have a screen that switch-off (and not a crash of the kernel) So, when a experimental kernel with intel wifi will be available, I will try and report. Regards, Vincent Thanks, this seems useful. -- Vincent Danjean Adresse: Laboratoire d'Informatique de Grenoble Téléphone: +33 4 76 61 20 11ENSIMAG - antenne de Montbonnot Fax:+33 4 76 61 20 99ZIRST 51, avenue Jean Kuntzmann Email: vincent.danj...@imag.fr 38330 Montbonnot Saint Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 perezme...@gmail.com: 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 matter wich one I plug into the DVI port, it detetcts the EDID worngly, while the VGA does it correctly. Or the VGA port is ignoring broken edids even without the forget broken edids patch, or somehow the DVI port is getting wrong edids, or checksumming them wrongly. 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 the port. Also, some hdmi receivers/switches mangle the edids. Alex Kinds regards, Lisandro. -- One of the biggest wake-up calls of my career was when I saw a record contract. I said, 'Wait - you sell it for $18.98 and I make 80 cents? And I have to pay you back the money you lent me to make it and then you own it? Who the f**k made that rule? Oh! The record labels made it because artists are dumb and they'll sign anything' - like I did. Trent Reznor, Nine Inch Nails on http://contactmusic.com/ http://tinyurl.com/c2wda4 Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ ___ dri-devel mailing list dri-de...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 the port. Also, some hdmi receivers/switches mangle the edids. Thanks, that's exactly the patch I'm already using. Works perfectly :-) I should mention that both monitors are VGA, so I'm using a VGA←→DVI adpator. And as I said before, it used to work without the patch :-) Kinds regards, Lisandro. -- My favourite poem is the one that starts 'Thirty days hath September' because it actually tells you something. -- Groucho Marx Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
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 perezme...@gmail.com: 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 the port. Also, some hdmi receivers/switches mangle the edids. Thanks, that's exactly the patch I'm already using. Works perfectly :-) I should mention that both monitors are VGA, so I'm using a VGA←→DVI adpator. And as I said before, it used to work without the patch :-) Can you bisect? I suspect the culprit is one of the patches that made the kernel edid parser more strict. Alternatively, you may have been using ums previously which does not have the same strict checks as the kernel. Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 that made the kernel edid parser more strict. Alternatively, you may have been using ums previously which does not have the same strict checks as the kernel. One simple question: is it possible to get the edid info provided by the VGA port? In that way one could compare both raw outputs. -- FAQ del pequeño tomi: P- ¿Porque los programas necesitan tanta RAM hoy? R- Porque los que programamos somos todos unos subnormales que no sabemos optimizar nada y nos gusta tener todo en RAM y hacer mmap a cualquier archivo que queramos acceder en vez de hacerlo como dios manda (mmap: funcion que mapea un archivo en memoria, no usar) Textual de Martín El Ruso Ribelotta Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#622993: every 10s I get [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ...
On 30/04/11 06:11, Jonathan Nieder wrote: Two corrupt-EDID/dmesg-spam puzzles for you. Seems to be a regression, though I'm not sure from when. I have a Benq Product Name FP241W manufactured February 2007 Revision B4-125 and used to use the DVI input. The EDID data in the DVI input suddenly failed and the my PC would not longer boot. I plugged my PC into the HDMI input of the monitor and the machine boots but X does not start at the correct resolution. It appears that the EDID data from HMDI input does not propose 1920x1200. On Vie 29 Abr 2011 22:08:09 Jonathan Nieder escribió: Thanks. Could you try the patch from https://bugs.freedesktop.org/show_bug.cgi?id=27708#c7 and see what happens when booting with the drm.edid_strict=0 option? thanks, I applied the patch to my 2.6.38-2-amd64 kernel and created /etc/modprobe.d/drm-stuart.conf. Now the DVI input of my screen can be used without an xorg.conf. I can now reboot linux (using kexec) and start the X server using the DVI input of my screen. I still have to use the HDMI input to get past the BIOS. This is a good patch. Please include it in the mainline kernel! It appears that it is just the checksum on the DVI-I-1 input of my screen that went bad. I wonder why that happened. I did find reports of this happening to other BenQ 241W screens: http://forums.entechtaiwan.com/index.php?topic=6783.45 I still get a few messages in /var/log/syslog but they stop quickly. :; cat /etc/modprobe.d/drm-stuart.conf options drm edid_strict=0 :; grep drm syslog May 1 12:26:42 kooka kernel: : [3.839230] [drm] Initialized drm 1.1.0 20060810 May 1 12:26:42 kooka kernel: : [3.925883] [drm] nouveau :01:00.0: Detected an NV40 generation card (0x04b300b1) May 1 12:26:42 kooka kernel: : [3.927833] [drm] nouveau :01:00.0: Attempting to load BIOS image from PRAMIN May 1 12:26:42 kooka kernel: : [3.969675] [drm] nouveau :01:00.0: ... appears to be valid May 1 12:26:42 kooka kernel: : [3.969683] [drm] nouveau :01:00.0: BIT BIOS found May 1 12:26:42 kooka kernel: : [3.969687] [drm] nouveau :01:00.0: Bios version 05.73.22.61 May 1 12:26:42 kooka kernel: : [3.969692] [drm] nouveau :01:00.0: TMDS table version 1.1 May 1 12:26:42 kooka kernel: : [3.969696] [drm] nouveau :01:00.0: TMDS table script pointers not stubbed May 1 12:26:42 kooka kernel: : [3.969701] [drm] nouveau :01:00.0: BIT table 'd' not found May 1 12:26:42 kooka kernel: : [3.969705] [drm] nouveau :01:00.0: Found Display Configuration Block version 3.0 May 1 12:26:42 kooka kernel: : [3.969711] [drm] nouveau :01:00.0: Raw DCB entry 0: 01000300 0028 May 1 12:26:42 kooka kernel: : [3.969715] [drm] nouveau :01:00.0: Raw DCB entry 1: 03011312 May 1 12:26:42 kooka kernel: : [3.969720] [drm] nouveau :01:00.0: Raw DCB entry 2: 04011310 0028 May 1 12:26:42 kooka kernel: : [3.969724] [drm] nouveau :01:00.0: Raw DCB entry 3: 020223f1 00c0c080 May 1 12:26:42 kooka kernel: : [3.969729] [drm] nouveau :01:00.0: DCB connector table: VHER 0x30 5 10 2 May 1 12:26:42 kooka kernel: : [3.969734] [drm] nouveau :01:00.0: 0: 0x1030: type 0x30 idx 0 tag 0x07 May 1 12:26:42 kooka kernel: : [3.969739] [drm] nouveau :01:00.0: 1: 0x0100: type 0x00 idx 1 tag 0xff May 1 12:26:42 kooka kernel: : [3.969745] [drm] nouveau :01:00.0: 2: 0x0210: type 0x10 idx 2 tag 0xff May 1 12:26:42 kooka kernel: : [3.969750] [drm] nouveau :01:00.0: 3: 0x0211: type 0x11 idx 3 tag 0xff May 1 12:26:42 kooka kernel: : [3.969755] [drm] nouveau :01:00.0: 4: 0x0213: type 0x13 idx 4 tag 0xff May 1 12:26:42 kooka kernel: : [3.969764] [drm] nouveau :01:00.0: Parsing VBIOS init table 0 at offset 0xCE4E May 1 12:26:42 kooka kernel: : [3.970015] [drm] nouveau :01:00.0: Parsing VBIOS init table 1 at offset 0xD4F8 May 1 12:26:42 kooka kernel: : [4.024025] [drm] nouveau :01:00.0: Parsing VBIOS init table 2 at offset 0xDC2C May 1 12:26:42 kooka kernel: : [4.024049] [drm] nouveau :01:00.0: Parsing VBIOS init table 3 at offset 0xDDB0 May 1 12:26:42 kooka kernel: : [4.048061] [drm] nouveau :01:00.0: Parsing VBIOS init table 4 at offset 0xDFBF May 1 12:26:42 kooka kernel: : [4.069604] [drm] nouveau :01:00.0: 1 available performance level(s) May 1 12:26:42 kooka kernel: : [4.069614] [drm] nouveau :01:00.0: 0: memory 400MHz core 400MHz voltage 1170mV fanspeed 100% May 1 12:26:42 kooka kernel: : [4.069626] [drm] nouveau :01:00.0: c: memory 405MHz core 400MHz May 1 12:26:42 kooka kernel: : [4.069923] [drm] nouveau :01:00.0: Detected 256MiB VRAM May 1 12:26:42 kooka kernel: : [4.078114] [drm] nouveau :01:00.0: 512 MiB GART (aperture) May 1 12:26:42 kooka kernel: : [4.079598] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). May
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 report[1], but be careful, it may cause more harm if something goes wrong. If you decided to do so, please check if the corruption appears again. [1] https://bugs.freedesktop.org/show_bug.cgi?id=34554 signature.asc Description: This is a digitally signed message part
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 want to try fixing your EDID info has explained in a similar bug report[1], but be careful, it may cause more harm if something goes wrong. If you decided to do so, please check if the corruption appears again. [1] https://bugs.freedesktop.org/show_bug.cgi?id=34554 Considering my video card is an Ati, wich I suspect doesn't use nouveau, it must not be this last one. And at least in my case, my card was working with a 2.6.38 kernel without problems, except I am missing something here. Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
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 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 report[1], but be careful, it may cause more harm if something goes wrong. If you decided to do so, please check if the corruption appears again. [1] https://bugs.freedesktop.org/show_bug.cgi?id=34554 Considering my video card is an Ati, wich I suspect doesn't use nouveau, it must not be this last one. 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? Anyway, I'd be really interested to hear from Stuart Pook: his story sounds exactly like mine. And at least in my case, my card was working with a 2.6.38 kernel without problems, except I am missing something here. Your case sounds similar, though. If the bug is the same, you can easily (even more easily since you have an identical screen working just fine) fix your screen, using the method mentioned on fdo. But I'm no expert, and since this method tempers with your hardware, I'd recommend you to be cautious. Regards, Thibaut Girka. signature.asc Description: This is a digitally signed message part
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 the software I upgraded :-( [snip] Your case sounds similar, though. If the bug is the same, you can easily (even more easily since you have an identical screen working just fine) fix your screen, using the method mentioned on fdo. 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 :-) But I'm no expert, and since this method tempers with your hardware, I'd recommend you to be cautious. OK! -- May the source be with you. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
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 what was wrong at the end of March. According to a ls -lrtc /boot I was probably running 2.6.37-1-amd64 on 23 February. Let me know if you need more information. I read with interest the report of how to correct a broken EDID. I might give it a go but not before next week. https://bugs.freedesktop.org/show_bug.cgi?id=34554 But I'm no expert, and since this method tempers with your hardware, I'd recommend you to be cautious. Yes, especially as I only have one Benq FP241W. Stuart -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 about ignoring broken EDIDs, but about actually fixing them[1]. If you're fine as it is now, I wouldn't recommend trying it out, though. [1] https://bugs.freedesktop.org/show_bug.cgi?id=34554#c15 signature.asc Description: This is a digitally signed message part
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 matter wich one I plug into the DVI port, it detetcts the EDID worngly, while the VGA does it correctly. Or the VGA port is ignoring broken edids even without the forget broken edids patch, or somehow the DVI port is getting wrong edids, or checksumming them wrongly. Kinds regards, Lisandro. -- One of the biggest wake-up calls of my career was when I saw a record contract. I said, 'Wait - you sell it for $18.98 and I make 80 cents? And I have to pay you back the money you lent me to make it and then you own it? Who the f**k made that rule? Oh! The record labels made it because artists are dumb and they'll sign anything' - like I did. Trent Reznor, Nine Inch Nails on http://contactmusic.com/ http://tinyurl.com/c2wda4 Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#622993: every 10s I get [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ...
forcemerge 624549 624486 622993 quit Lisandro Damián Nicanor Pérez Meyer wrote: With a dual screen setup. Not so long ago (less than a week) both monitors (ViewSonic VG2021wm) were working fine. Somehow the monitor connected to the DVI port started not being detected correctly on boot (wrong edid?). Dmesg shows: Thanks. Could you try the patch from https://bugs.freedesktop.org/show_bug.cgi?id=27708#c7 and see what happens when booting with the drm.edid_strict=0 option? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622993: every 10s I get [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ...
unmerge 622993 forwarded 622993 dri-de...@lists.freedesktop.org quit Lisandro Damián Nicanor Pérez Meyer wrote: The patch works perfectly, so at least I have a workaround :-) Thank you! Now the question is why the DVI port gets a corrupt EDID while the VGA port gets it right. Or maybe the code processing the EDID of the DVI port is wrong? A puzzle. Thanks for checking. I've passed the report upstream; hopefully upstream received a copy, but I can't be sure if it's just waiting for moderation or was filtered for some reason. If the former, it will be at http://mid.gmane.org/20110430040921.GA7942@elie eventually. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
