The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Clevo P370SM-A LCD EDID messed up

    Discussion in 'Sager and Clevo' started by KuroSan, Mar 16, 2018.

  1. KuroSan

    KuroSan Notebook Enthusiast

    Reputations:
    3
    Messages:
    38
    Likes Received:
    4
    Trophy Points:
    16
    hi,

    i accidently messed up my internal screens edid with nvflash bat file, i didn't even know that this is possible.

    anyway, i read in another post that there is something like a linux live distro which is able to fix that.

    my lcd is not recognised.Graphics card is working fine, i can use the computer with windows update driver or older XMG drivers and external monitor, but newer nvidia driver install fails.

    i have some linux experience, xubuntu is installed on my machine, if someone knows how to solve this problem - help would be greatly appreciated.
     
    KuroSan, Mar 16, 2018
    #1
  2. Chastity

    Chastity Company Representative

    Reputations:
    1,295
    Messages:
    6,545
    Likes Received:
    336
    Trophy Points:
    251
    What does CRU tell you?
     
    Chastity, Mar 16, 2018
    #2
    KuroSan likes this.
  3. Prema

    Prema Your Freedom, Your Choice

    Reputations:
    9,368
    Messages:
    6,297
    Likes Received:
    16,485
    Trophy Points:
    681
    Prema, Mar 16, 2018
    #3
    Papusan likes this.
  4. KuroSan

    KuroSan Notebook Enthusiast

    Reputations:
    3
    Messages:
    38
    Likes Received:
    4
    Trophy Points:
    16
    Thank you for your replies.

    Ahh, Costum Resolution Utility - neat little program! it tells me: PNP09FF - Generic non PnP Monitor(active).

    All other fields are blank.

    but i'm not sure what to do now...
     
    KuroSan, Mar 17, 2018
    #4
  5. KuroSan

    KuroSan Notebook Enthusiast

    Reputations:
    3
    Messages:
    38
    Likes Received:
    4
    Trophy Points:
    16
    This is output of linux terminal:

    This is read-edid version 3.0.2. Prepare for some fun.
    Attempting to use i2c interface
    No EDID on bus 0
    No EDID on bus 2
    No EDID on bus 4
    No EDID on bus 5
    No EDID on bus 6
    2 potential busses found: 1 3
    Will scan through until the first EDID is found.
    Pass a bus number as an option to this program to go only for that one.
    256-byte EDID successfully retrieved from i2c bus 1
    Looks like i2c was successful. Have a good day.
    WARNING: Checksum failed
    Trying to continue...
    Section "Monitor"
    Identifier "
    @"
    ModelName "
    @"
    VendorName "CO_"
    # Monitor Manufactured week 5 of 2011
    # EDID version 1.3
    # Analog Display
    DisplaySize 380 210
    Gamma 2.20
    Option "DPMS" "false"
    Modeline "Mode 0" 138.70 1920 1968 2000 2080 1080 1083 1088 1111 -hsync -vsync
    EndSection

    this seems to be my chi mei panel.
     
    KuroSan, Mar 17, 2018
    #5
  6. t456

    t456 1977-09-05, 12:56:00 UTC

    Reputations:
    1,959
    Messages:
    2,588
    Likes Received:
    2,048
    Trophy Points:
    181
    Ok, ' checksum failed' is indeed definitive proof for edid corruption. Please install i2cdump and run ' i2cdump -r 0-255 1 0x50 > somename.txt'. This raw dump will tell us what edid we need to flash for your specific panel.

    Which GPU are your using? Newer generations won't permit us to reflash the edid via software, but an older model might work, depending on whether the panel's edid eeprom is write-protect or not. It probably it isn't, since otherwise the corruption would be a remote, freak occurrence.
     
    t456, Mar 17, 2018
    #6
    Papusan and KuroSan like this.
  7. KuroSan

    KuroSan Notebook Enthusiast

    Reputations:
    3
    Messages:
    38
    Likes Received:
    4
    Trophy Points:
    16
    Hi,

    My GPU is a GTX 970M, and the problem occured when i accidently double clicked (instead of right click) nvflash bat file i created for flashing in windows safe mode.
    After reboot the screen went black and the computer refuses to boot.
     
    KuroSan, Mar 17, 2018
    #7
  8. KuroSan

    KuroSan Notebook Enthusiast

    Reputations:
    3
    Messages:
    38
    Likes Received:
    4
    Trophy Points:
    16
    Ok, here is the raw dump:
     

    Attached Files:

    KuroSan, Mar 17, 2018
    #8
  9. t456

    t456 1977-09-05, 12:56:00 UTC

    Reputations:
    1,959
    Messages:
    2,588
    Likes Received:
    2,048
    Trophy Points:
    181
    Well ... that's one messed-up edid; it claims to be a CRT ... a monochrome one at that :vbeek: . It's a 128-byte edid though, not a 256-byte version. Use this one for reflashing:
    CMO1720 - N173HGE-L11 (GTF, AUO, old).bin
    You can follow this step-by-step guide, if you like (see ' instructions (unabridged)').

    It's interesting to know that nvflash can actually write to the lcd's firmware. Can you upload a copy of the nvflash and all its concomitant files?
     
    t456, Mar 17, 2018
    #9
    Papusan, bennyg, KY_BULLET and 1 other person like this.
  10. KuroSan

    KuroSan Notebook Enthusiast

    Reputations:
    3
    Messages:
    38
    Likes Received:
    4
    Trophy Points:
    16
    You, Sir, saved my day, everything was working flawless - my panel is up and running, thank you, thank you, thank you!

    this is nvflash version I used(including my GTX970M bios):
     

    Attached Files:

    KuroSan, Mar 17, 2018
    #10
    KY_BULLET likes this.
  11. t456

    t456 1977-09-05, 12:56:00 UTC

    Reputations:
    1,959
    Messages:
    2,588
    Likes Received:
    2,048
    Trophy Points:
    181
    Great! Nice job.

    Interesting to see that a vbios flash can corrupt a screen. Part of the vbios binary matches that of the corruption in the screen and your specific errant bytes match 1:1 with the bulk of those affected in these threads:
    The one, single commonality was an Nvidia gpu, Kepler or Maxwell, with direct access to the screen, so not re-routed via the cpu (there was even a Windows-running Apple that was hit). So, presumably, a driver install or installing Precision X can both flash or at least partially modify the vbios? Perhaps @Mr. Fox or @Prema might know more about this possibility?
     
    t456, Mar 18, 2018
    #11
    Papusan and Mr. Fox like this.
  12. KuroSan

    KuroSan Notebook Enthusiast

    Reputations:
    3
    Messages:
    38
    Likes Received:
    4
    Trophy Points:
    16
    That sounds very interesting - that day i had Precision X installed, just to see if it will give me more options than msi afterburner.
    tried it a few minutes, then uninstalled again.

    i use the nvidia 391.01 driver.

    it was this version:
     
    KuroSan, Mar 18, 2018
    #12
  13. KuroSan

    KuroSan Notebook Enthusiast

    Reputations:
    3
    Messages:
    38
    Likes Received:
    4
    Trophy Points:
    16
    KuroSan, Mar 18, 2018
    #13
  14. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist®

    Reputations:
    37,255
    Messages:
    39,347
    Likes Received:
    70,734
    Trophy Points:
    931
    Mr. Fox, Mar 18, 2018
    #14
    Papusan likes this.