error* edid checksum is invalid remainder is 80 Archie Missouri

We serve small, medium and large sized businesses in a wide-variety of industries who realize that technology is an integral part of being a leader in their industry. They realize that a custom solution will help them manage their business which in turn, allows them to provide top-notch service to their customers. Some of the industries our clients represent are railroad, mortgage, manufacturing, retail, medical services, non-profit, county and state government.

Address 10104 w 105th st, Overland Park, KS 66212
Phone (913) 701-7250
Website Link http://www.hccsinc.com
Hours

error* edid checksum is invalid remainder is 80 Archie, Missouri

It seems to almost be confined to the i915 chipset. Of course I do not intend to keep any knowledge about a mainboard that most likely works well with Ubuntu-server 10.10 from you: It is an Asus P7H55D-M PRO. Since it will not detect it, you then need to tell it in the "Modes" line what resolutions the display will support. Comment 5 Cristian Aravena Romero 2015-02-09 13:15:15 UTC Hello Jani, Not problem of "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid," in kernel 3.19-rc7.

I use X11VNC frequently and have a custom autorun entry in my session configuration: Code: x11vnc -usepw -shared -forever -display :0 I'm going to log its outputs and see whether there Note that I think the patch was a bandaid and doesn't really address what started causing the EDID fetching routine to fail repeatedly. x11vnc can no longer perform I/O with the X server.) So I suspect this is a symptom, not a cause. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag.

I fear this sort of tinkering can be filled with unintended consequences. Report a bug This report contains Public information Edit Everyone can see this information. So I figure the fault lies with the CRTs I have, or the H55 chipset is especially error-prone for this type of CRT (I could not check further because I lacked Read more...

Apologies if it has reached you inappropriately; please just reply to this message indicating so.] tags: added: kj-triage Changed in linux (Ubuntu): status: New → Incomplete Erik de Castro Lopo (erikd) So it appears to be an issue of that one CRT model. Anybody got better ideas? I just hate error messages I can't solve as a matter of principle.

No one has been able to identify the root cause of this, but adding the following line to /etc/rc.local works around it for me: # Disable monitor hotplug polling (https://launchpad.net/bugs/712075) echo Your EDID is probably invalid. /var/log/Xorg.0.log says: 552 [ 28.729] (WW) NVIDIA(GPU-0): The EDID read for display device DFP-0 is invalid: the 553 [ 28.729] (WW) NVIDIA(GPU-0): checksum for EDID version Actually, every second LOTS of entries are written to this file (I don't know whether this is normal). However, I do not so much have the "flickering" that is indicated.

Then I needed to reboot into rescue mode, and still got 1024x768 video and no virtual terminals. It does not seem to exist. Report a bug This report contains Public information Edit Everyone can see this information. I decided to wait and see what V10.10 brings. 10/12/10 Update: V10.10 may have taken care of it.

I tried 2.6.38-8 but no change. I see the drm:drm_edid_block_valid error in dmesg. Today this happened for the second or third time. the bug should not appear anymore.

Thanks! So it bothers me less, and I'm becoming increasingly convinced this is a bug because 99.99% of my experience with #! I have to switch to a VT and restart lightdm. I've been googling this for days...

Works, but there's that same error message. Nope, it was still my box whose X server went down repeatedly. Thanks in advance, fleder Last edited by fleder; October 24th, 2010 at 05:57 PM. Thanks, Daniel > [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

pulseaudio CurrentDesktop: GNOME Date: Thu Oct 9 04:41:59 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-09-25 (14 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., It showed the same success rate as my box did with this CRT. Monitor "Unknown"; Back yo Square 1. The 2 other replacement were detected straight-away.

It warries me because when something writes to files (i think) is uses battery. My hardware is the same as indicated in comment #27 however at the moment I am running oneiric with the 3.0-1-generic kernel. Posting in the Forums implies acceptance of the Terms and Conditions. HTH.

Changed in linux (Ubuntu Natty): status: Triaged → Incomplete Kees Cook (kees) wrote on 2011-02-14: #23 So far, so good. Please contact him regarding any issues with the action taken in this bug report.] tags: added: patch Greg Edwards (gedwards) wrote on 2011-10-17: #59 I see this same issue in 11.10 useResa (rdrijsen) wrote on 2011-06-22: #53 I have tried the solution as described by sikkepitje in comment #52 however .... Thanks for testing.

Swapping monitors does not change it. Results 1 to 2 of 2 Thread: [Solved] *ERROR* EDID checksum is invalid, remainder is N Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid gtdaqua (gtdaquitaine) wrote on 2011-04-29: #47 Solved!!!!! useResa (rdrijsen) wrote on 2011-03-18: #35 dmesg (2011.03.18) Edit (68.8 KiB, text/plain) I upgrade to the new kernel 2.6.38-7-generic and also for me the issue is still there.

The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. affects: xserver-xorg-video-intel (Ubuntu) → xdiagnose (Ubuntu) Launchpad Janitor (janitor) wrote on 2013-01-19: #8 This bug was fixed in the package xdiagnose - 3.4 --------------- xdiagnose (3.4) raring; urgency=low * bin/xrotate: Add Which gave me hope of finding a fix. Reply With Quote « Previous Thread | Next Thread » Bookmarks Bookmarks Digg del.icio.us StumbleUpon Google Facebook Twitter Posting Permissions You may not post new threads You may not post replies