From owner-freebsd-doc@FreeBSD.ORG Wed Jul 4 03:52:45 2012 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8C22D106564A; Wed, 4 Jul 2012 03:52:45 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 4AB938FC0A; Wed, 4 Jul 2012 03:52:45 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q643qi6p016375; Tue, 3 Jul 2012 21:52:44 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q643qiP4016372; Tue, 3 Jul 2012 21:52:44 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 3 Jul 2012 21:52:44 -0600 (MDT) From: Warren Block To: Benjamin Kaduk In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Tue, 03 Jul 2012 21:52:44 -0600 (MDT) Cc: doc@freebsd.org Subject: Re: Handbook update: HorizSync and VertRefresh X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2012 03:52:45 -0000 On Wed, 4 Jul 2012, Benjamin Kaduk wrote: > On Mon, 2 Jul 2012, Warren Block wrote: > >> The X11 configuration chapter of the Handbook has some very old >> information which is confusing users. Manually setting HorizSync and >> VertRefresh has been mostly useless for many years, and should be >> deemphasized. >> >> This patch does that. Instead of saying the sync frequencies must >> always be entered, it adds some information about autodetection and >> points out that almost all monitors support it. Also added is a note >> not to guess about sync frequencies. On the CRT monitors where it >> matters, it can matter a lot. Some of those monitors might still be >> functional. > > One does hear the occasional tale of a CRT which exploded when the wrong > frequencies were configured ... it might be worth mentioning that guessing > values could lead to hardware damage. It's such a rare situation that I'm hesitant to mention it. This might be better: Most monitors support sync frequency autodetection, making manual entry of these values unnecessary. For the few monitors that do not support autodetection, avoid potential damage by only entering values provided by the manufacturer.