I bought this monitor a long time ago. It always worked fine, but last week it started behaving strangely:
This is a secondary monitor on a two monitor system that runs Linux Fedora 22.
The primary monitor is connected via HDMI, the secondary one (the viewsonic in question) via DVI cable. Both are connected to the same video card.
Since a couple of days, the screen works fine as long as the contents shown on the screen are not modified. As soon as its contents are changed (like moving a window or changing its content), it gets noisy for about 2 seconds after the change, than works fine again. The noise shows a pattern of vertical noisy lines over the whole screen. During this time the screen contents remain readable. This only happens on the viewsonic. The primary Samsung does not have this problem.
To make sure this is not a cable or cable contact issue, I changed the DVI cable and connected the monitor with an analog cable (DSub). This did not improve this noisy behaviour.
I wonder if this could be a capacitor issue, since I could not find other posts describing the same behaviour as above.... ??
Regards,
Geert
This is a secondary monitor on a two monitor system that runs Linux Fedora 22.
The primary monitor is connected via HDMI, the secondary one (the viewsonic in question) via DVI cable. Both are connected to the same video card.
Since a couple of days, the screen works fine as long as the contents shown on the screen are not modified. As soon as its contents are changed (like moving a window or changing its content), it gets noisy for about 2 seconds after the change, than works fine again. The noise shows a pattern of vertical noisy lines over the whole screen. During this time the screen contents remain readable. This only happens on the viewsonic. The primary Samsung does not have this problem.
To make sure this is not a cable or cable contact issue, I changed the DVI cable and connected the monitor with an analog cable (DSub). This did not improve this noisy behaviour.
I wonder if this could be a capacitor issue, since I could not find other posts describing the same behaviour as above.... ??
Regards,
Geert
Comment