Jump to content

RODBORA

Registered User
  • Posts

    2
  • Joined

  • Last visited

Profile Information

  • Location
    Brazil

RODBORA's Achievements

Curious Beginner

Curious Beginner (1/7)

1

Reputation

  1. Amazing project! Very nice. The first working WC in a notebook I ever seen. Can you publish some more pictures? Congratulations! Your project is in the main page of the website!
  2. Hello folks. I'm registered here in the Forum to include my experience and solution with the problem described in the tittle. I have a Clevo P377SM-A, with a i74810MQ + a SLI of GTX870m. I'm using it since 18 months without any importants issues. But in the last days I tried a deadly sequence of software upgrades: The installation of Windows 10, plus, almost in the same time, for a coincidence, the new version of EVGA Precision X (5.3.10) and, too, tried the new version of MSI Afterburner (4.2). I tried too the new version od NVIDIA Driver (361.43). As you can see I made exactly the installation of the specific pieces of software that start the problem of lcd firmware corruption. :-( Well, I never could expect this kind of problem just to try a world wide new SO, or a driver from a world leader manufacturer of GPUs! But after complete the sequence of installations my lcd panel went to the same problem described in this post: no backlight, no boot (and a permanent boot cicle without POST). The original configuration I always used in this equipment was Windows 8.1 + EVGA Precision X version 3.04 (yes, a very a old version) used only to monitor GPU temps. After upgrade to Windows 10 and install the new NVidia drivers and/or Precision X / MSI Afterburner, the lcd died. I did my research to web and I'm very glad because I found this forum and the post from Prema: https://www.techinferno.com/index.php?/forums/topic/8612-possible-lcd-firmware-corrupted-due-to-nvidia-evga-precision-x-help/&do=findComment&comment=129487 I followed (with great care) all the steps, using also the pictures included in .img Linux file) and my LCD is now working again! Thanks Prema. The .img file you did is amazing, Very complete and saved my notebook from RMA. The only thing different was the result of command "sudo ./edid-rw 1 | edid-decode" never returned the informations from my LCD EDID... At the first moments I even could find the exact specific model of my lcd panel. But I found the correct address, the correct I2C bus number of the notebook LCD using the command from the first steps described in the Instructions.txt file, wich use the command i2cdetect (I found the lcd in the bus #1). With this I find the model of my lcd: N173HGE-L11. Nice, but even with the correct bus number, the command "sudo ./edid-rw 1 | edid-decode" does NOT retrieved the informations from the lcd EDID. I decided so to try to write the new (and corrected) .bin firmware file to bus number #1, even this way, because I was sure that the bus number was #1. And it worked. :-) So, the only one point in the procedure that I found different during the recovery process was this one (do not reach the informations from lcd EDID when using the command sudo ./edid-rw 1 | edid-decode. But found using i2cdetect and the write process to the correct bus number worked well. So i'm very glad to found help here, AND THANK YOU PREMA. You gave me a great gift with the .img file with all informations available together in just one place. You did a amazing high high high level work finding a solution to this terrible bug from Microsoft and/or Nvidia. Thanks Prema and all community. RODBORA
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.