From agw at dsm.fordham.edu Fri Jun 5 13:10:23 2015 Content-Type: multipart/mixed; boundary="===============5911689102294960622==" MIME-Version: 1.0 From: Art Werschulz To: users at lists.fedoraproject.org Subject: Re: Xorg -configure problems Date: Wed, 30 Jun 2004 15:15:30 -0400 Message-ID: <200406301915.i5UJFUP8006546@sobolev.dsm.fordham.edu> In-Reply-To: 1088615442.2034.224.camel@lh2.motocompastro.org --===============5911689102294960622== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi. Regarding my X-windows configuration problem, I was told > This information is readily available on the web: > = > http://support.ap.dell.com/docs/monitors/p793/En/specs.htm > = > Resolution = > Horizontal scan range 30 kHz to 96 kHz (automatic) = > Vertical scan range 50 Hz to 160 Hz (automatic) = > Optimal preset resolution 1024 x 768 at 85 Hz = > Highest preset resolution 1600 x 1200 at 75 Hz = AFAICT, all this information is currently present in the xorg.conf file, except for the 85Hz. Currently, the xorg.conf file has Section "Monitor" Identifier "Monitor0" VendorName "DEL" ModelName "DELL P793" HorizSync 30.0 - 96.0 VertRefresh 50 - 160 Option "DPMS" EndSection Following the instructions in the xorg.conf manpage (as I understand them), I changed this to read Section "Monitor" Identifier "Monitor0" VendorName "DEL" ModelName "DELL P793" HorizSync 30.0 - 96.0 VertRefresh 50 - 160 Mode "1024x768" DotClock 85Hz EndMode Option "DPMS" EndSection When I ran Xorg, I got an error msg telling me that there was a parse error ("Unexpected token in verbose Mode entry) in this section. Just for fun, I tried changing the line to DotClock 85 (figuring that perhaps the "Hz" was the unexpected token). I got a different error msg, saying that the horizontal timings are missing. Obviously, I'm misinterpreting the manpage's instructions. Exactly how should I be specifying the 85Hz clock speed? HOWEVER ... I'm wondering if this is a red herring. After all, we're able to launch X windows successfully. The problem only happens when terminating an X windows session, in which case we're getting the abberant behavior: (1) The screen shows a floating box with a complaint. (2) When the X server shuts down, it wedges, and can only be restored by switiching runlevels (init 3; init 5). -- = Art Werschulz (8-{)} "Metaphors be with you." -- bumper sticker GCS/M (GAT): d? -p+ c++ l u+(-) e--- m* s n+ h f g+ w+ t++ r- y? = Net: agw(a)dsm.fordham.edu WWW= Phone: Fordham U. (212) 636-6325, Columbia U. (212) 939-7060 --===============5911689102294960622==--