[SOLVED] *ERROR* EDID checksum is invalid, remainder is 130

bootstrap · 2011-10-05 07:04:07

Whenever I connect my Lenovo T61 laptop (CrunchBang Statler Openbox) to a Samsung 943NWX external monitor, I get the following message before the login screen:

[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 130
[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 130
[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 130
[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 130

It does not show on my laptop screen if/when I disconnect from the external monitor. Connected, I have an extended display setting which runs without any issue.

I have tried Googling for a solution to remove the error message without success.

My machine has an Intel GMA X3100 graphics chip.

Has anyone come across this problem and found a way to remove the error message?

Last edited by bootstrap (2011-10-07 19:51:46)

machinebacon · 2011-10-05 07:20:09

Hello, i try to give you some pointers so you can maybe find a solution (until somebody else comes up with a better idea than mine)

You can try to make a custom EDID file, though I don't know if Intel supports custom/ignore EDID files (this option is usually added in xorg.conf)

Another option would be creating a custom xorg.conf (probably you have no xorg.conf on your system, don't worry about it) - in this case the additional monitor would be written into the configuration (be very careful with the Modeline and HorizSync/VertRefresh values!)

It is also possible that xrandr can help you: http://wiki.debian.org/XStrikeForce/HowToRandR12

Hope you can find a fix

bootstrap · 2011-10-05 22:23:59

@machinebacon: Thank you. You're right - I don't have an xorg.conf file (not one I can find anyway). I tried a custom xorg.conf two days ago but that created more problems... but I might try again.

If I find a solution, I'll post it here.

Neil · 2011-10-05 23:24:31

Don't know if you've looked at the Thinkwiki page below, but there might be some helpful info there. It doesn't mention your specific problem, though. But, that's about as much help as I can offer...

http://www.thinkwiki.org/wiki/Intel_Gra … ator_X3100

bootstrap · 2011-10-07 07:07:01

Neil wrote:

Don't know if you've looked at the Thinkwiki page below, but there might be some helpful info there. It doesn't mention your specific problem, though. But, that's about as much help as I can offer...
http://www.thinkwiki.org/wiki/Intel_Gra … ator_X3100

@Neil: Thanks! I've had a look at the page. It seems like my best bet to fix he issue is to mess around with the xorg.conf file.

In the meantime, I've managed to cut boot time to about 25 secs, so the error message is there for only a second or less. So it bothers me less, and I'm becoming increasingly convinced this is a bug because 99.99% of my experience with #! has been very good. The monitors have been working fine, with or without the external monitor attached.

Something I didn't mention was that #! is the only distro that has given me this issue. In the past, I've tried Ubuntu, Lubuntu, PCLinuxOS, openSUSE, LMDE, and Debian - none of these gave the above error message. Which gave me hope of finding a fix.

bootstrap · 2011-10-07 19:43:34

I found a solution! (sort of)

I tried generating an xorg.conf file:

sudo Xorg :1 -configure
sudo cp /root/xorg.conf.new /etc/X11/xorg.conf
sudo gedit  /etc/X11/xorg.conf

I then entered the following in the 'Monitor' section:

Section "Monitor"
    # HorizSync source: builtin, VertRefresh source: builtin
    Identifier          "Monitor0"
    VendorName     "Unknown"
    ModelName       "VGA1"
    HorizSync           30.0 - 81.0
    VertRefresh       56.0 - 75.0
    ModeLine          "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync
    Option               "Preferred Mode" "1440x900"
EndSection

The above did not get rid of the error message.

So I entered the following in the 'Device' section of xorg.conf:

Option "UseEDID" "False"

Still no change.

I then edited /etc/default/grub, changing the line

GRUB_CMDLINE_LINUX_DEFAULT="quiet"

to

GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"

The error messages are gone. There is a whole bunch of text running up the screen on boot and a bit more on shutting down, but no more error messages. Boot time is a little faster - by about 2 seconds.

Come to think of it, I should have tried nomodeset earlier - here's a short description of nomodeset for anyone who's interested.

Last edited by bootstrap (2011-10-07 19:53:11)

NicePics13 · 2011-10-07 22:19:30

Yes, one effect of nomodeset is getting rid of the EDID spam and more:

Older Radeons get video overlay back (besides textured video)

GNOME3 only works in fallback mode

often needs manual monitor setup in xorg.conf.d (refresh rates etc)

Xorg just crashes in Scientific Linux 6.1

Last edited by NicePics13 (2011-10-07 23:33:28)

CrunchBang Linux

SEARCH

#1 2011-10-05 07:04:07