Ddigit
08-22-2015, 02:45 PM
Hi,
So after a frustrating couple of hours of crashes, corrupt installations, trashed registry I finally got my Lenovo LT1421w working.
TLDR: Don't use the newer versions of the driver, what finally worked for me was a complete removal of both windows drivers and the display-link software, then an installation of version 7.4 M4
First, I'm on a Win7 x64 installation, have 2x hd6870 in crossfire.
So, Windows recognizing the display and downloaded the drivers.
They did however, not work with the screen, the Displaylink software (which came with the windows driver) reported that the WDDM (windows display driver model) of my gfx drivers used was to new, and that I should download a newer driver from displaylink.com/software.
So, I did just that, but with negative results, nothing happened. I got neither any (active) confirmation that the installation worked nor that it had failed.
In any case the display did not appear. (This is when I generated the report)
After searching I found someone else with the exact same problem:
http://displaylink.org/forum/showthread.php?t=61461&highlight=LT1421
It simply did not detect even though everything I could examine said it was working as intended (Correct names on devices, correct pid/vid's), unfortunately no one ever responded to that post.
I thought something might have happened during the installation (I had to skip the "plug in your display" step), so I uninstalled, unplugged and ran the installation again.
This time i plugged in the display, the software seemed to react but then suddenly caused the computer to reboot.
Great...
So I uninstalled the (incomplete) installation and tried again...
Same results, except this time it corrupted my filesystem, in particular the installation of the drivers. Every time i connected or disconnected the screen i got multiple error dialog boxes.
I could not uninstall the driver or application, because the install information was corrupted, neither could I re-install because it was already installed.
Sigh-
So I traversed the registry and removed most keys that was displaylink related.
I continued to try various variations of the windows driver, the displaylink driver, installation, removal, safemode etc.
After all this I finally decided that my particular configuration must be causing some undefined behaviour in the installation process or what not and decided to try different older versions.
Lo and behold, the first older version I tried works flawlessly! (7.4 M4)
The thing that irritated me the most is that you get almost no feedback from the displaylink driver, there isn't even some sort of about screen to see what version was installed, and binary log files... something I hate with a passion.
It would have helped me a lot just to know if the driver was correctly installed and that it had detected my screen as a device (I mean there was a EDID file in the debug directory, so it did detect Something).
Anyway sorry for going on about it, guess I just need to vent a bit.
In any case, hopes this helps someone with the same problem.
I also include the report the support tool generated after I noticed the first installation attempt succeeded but did not detect my screen.
So after a frustrating couple of hours of crashes, corrupt installations, trashed registry I finally got my Lenovo LT1421w working.
TLDR: Don't use the newer versions of the driver, what finally worked for me was a complete removal of both windows drivers and the display-link software, then an installation of version 7.4 M4
First, I'm on a Win7 x64 installation, have 2x hd6870 in crossfire.
So, Windows recognizing the display and downloaded the drivers.
They did however, not work with the screen, the Displaylink software (which came with the windows driver) reported that the WDDM (windows display driver model) of my gfx drivers used was to new, and that I should download a newer driver from displaylink.com/software.
So, I did just that, but with negative results, nothing happened. I got neither any (active) confirmation that the installation worked nor that it had failed.
In any case the display did not appear. (This is when I generated the report)
After searching I found someone else with the exact same problem:
http://displaylink.org/forum/showthread.php?t=61461&highlight=LT1421
It simply did not detect even though everything I could examine said it was working as intended (Correct names on devices, correct pid/vid's), unfortunately no one ever responded to that post.
I thought something might have happened during the installation (I had to skip the "plug in your display" step), so I uninstalled, unplugged and ran the installation again.
This time i plugged in the display, the software seemed to react but then suddenly caused the computer to reboot.
Great...
So I uninstalled the (incomplete) installation and tried again...
Same results, except this time it corrupted my filesystem, in particular the installation of the drivers. Every time i connected or disconnected the screen i got multiple error dialog boxes.
I could not uninstall the driver or application, because the install information was corrupted, neither could I re-install because it was already installed.
Sigh-
So I traversed the registry and removed most keys that was displaylink related.
I continued to try various variations of the windows driver, the displaylink driver, installation, removal, safemode etc.
After all this I finally decided that my particular configuration must be causing some undefined behaviour in the installation process or what not and decided to try different older versions.
Lo and behold, the first older version I tried works flawlessly! (7.4 M4)
The thing that irritated me the most is that you get almost no feedback from the displaylink driver, there isn't even some sort of about screen to see what version was installed, and binary log files... something I hate with a passion.
It would have helped me a lot just to know if the driver was correctly installed and that it had detected my screen as a device (I mean there was a EDID file in the debug directory, so it did detect Something).
Anyway sorry for going on about it, guess I just need to vent a bit.
In any case, hopes this helps someone with the same problem.
I also include the report the support tool generated after I noticed the first installation attempt succeeded but did not detect my screen.