Strange problem: lcd monitor highest resolution stopped working due to OCD changes
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Strange problem: lcd monitor highest resolution stopped working due to OCD changes
I have a pentium4 pc with an intel 810 graphics adaptor and a HP 1530 flatscreen 15 " monitor (I use the analog VGA connection)
I installed Dapper Drake 6.06 without problem, and the highest resolution (1024x768 @ 75Hz) was supported.
Then, one day, I played around with the OCD screen (the little monitor menu that pops up if you press the buttons on the monitor).
Since then, the screen simply does not work in the highest resolution any more. You see a garbled screen, it is like
the horizontally lines are too long, and thus every line just does not 'fit' on the screen.
The 'auto adjustment' does not help. And manually playing with the clock phase helps to create a regular image, but it is only half the width then normally.
The monitor is not broken, it works still fine on a windows PC.
If I boot a Ubuntu live CD, I have exactly the same problem. Thus it is not due to my software setting either.
xserver-xorg reconfiguration does not fix the problem either.
The monitor works still fine in 800x600 and 640x400, too. But what can I do to fix the high resolution.
Please help.
I have enclosed my /etc/X11/xorg.conf and my lspci
---------------------------------------------------------
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
If it worked before you made changes to the settings in the monitor, have you tried using the FACTORY RESET option in the OSD menu to set everything in the monitor back to the default settings ?
From the User Manual
Quote:
When adjusting the Clock and Clock Phase value if the monitor images become distorted, continue adjusting the values until the distortion disappears. To restore the Factory Settings, Select YES from the Factory Reset menu in the on-screen display
I would start with that.. undo whatever it is that you done did...
Yes, I tried the factory reset. It is really weird, but fortunately I fixed the problem.
I rebooted with the SimplyMepis 6.0 Live CD and that distro (like Ubuntu with Xorg) used different Xorg settings. It worked though.
I copied the xorg.conf from the live CD distro to my Ubuntu system and restarted X and now it works again. Really strange.
The upshot is, aparently, that even though SimplyMepis 6.0 and Ubuntu 6.06 and Knoppix 5.0 all use relatively new X versions, only SimplyMepis recognized it right.
Out of curiousity, if you run a diff between the two files, it will identify the differences. It might be useful to determine exactly which parameters created the original problem
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
