Results 1 to 3 of 3

Thread: [drm:drm_edid_block_valid] *ERROR* Raw EDID:

  1. #1
    Just burned his ISO
    Join Date
    Jun 2011

    Default [drm:drm_edid_block_valid] *ERROR* Raw EDID:

    On my notebook ("Asus G73S" which is extremely new and has a built-in Nvidia GTX460M) the console is spamming 1-2x per second errormessages like this one:
    [xx.xxxxx] [drm:drm_edid_block_valid] *ERROR* Raw EDID:
    where the xx.xxxxx in the beginning of the line is numbers which are continually increasing.
    I need to press CTRL+C to see the root-prompt and (if I am fast enough) I am able to enter "startx" (or any other command) and press enter. If I don't do that within 0.5 seconds, the prompt disappears and the console
    continues to flood me with the above mentioned errormessages.
    After successfully executing startx I can use the terminal within KDE (and there I don't have this problem).
    My question: What is this massive amount of errormessages and how do I get rid of them? Is my notebook incompatible with BT5??

    P.S. Tryed 64-bit and 32-bit version of the LiveDVD, same error with both of them on this hardware.

  2. #2
    Just burned his ISO
    Join Date
    Jun 2011

    Default Re: [drm:drm_edid_block_valid] *ERROR* Raw EDID:

    After ages, the moderators finally approved my thread. In the meantime i found out at least something about this issue:
    - EDID is a kind of informationstring which is published by the LCDs (in this case, the built-in screen of the notebook)
    - The way how BT is polling for EDID (and handling the result) is implemented totally noobish and buggy. It simply doesn't work with a lot of displays, escpecially those built-in LCDs in newer notebooks.
    - I didn't find a solution/patch
    - I found a workaround:

    echo 0 > /sys/module/drm_kms_helper/parameters/poll

    This stops polling for hotplug-devices, therefore also stops polling+missinterpreting the EDID of the display, therefore stops flooding useless errormessages.
    Does anybody have a more sane solution?

  3. #3
    Just burned his ISO
    Join Date
    Apr 2012

    Default Re: [drm:drm_edid_block_valid] *ERROR* Raw EDID:

    I was having the same issue and had to create an account just to thank you for this workaround softize...until there is an actual solution this definitely does save my sanity

Similar Threads

  1. Replies: 0
    Last Post: 01-27-2011, 04:06 AM
  2. Replies: 3
    Last Post: 10-18-2010, 11:00 PM
  3. NTOP **WARNING** gzflush error -2(stream error)
    By Larika in forum OLD BackTrack 4 (pre) Final
    Replies: 8
    Last Post: 07-18-2009, 07:41 PM
  4. SEND L3 ERROR/Ettercap error?
    By sunking in forum OLD Newbie Area
    Replies: 7
    Last Post: 07-01-2009, 10:31 PM
  5. metasploit -msfupdate error - svn : PROFIND request error
    By aisketui in forum OLD BT3beta Software related issues
    Replies: 2
    Last Post: 02-11-2009, 03:23 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts