Date: 25 Oct 2002 11:18:53 -0700 From: swear@attbi.com (Gary W. Swearingen) To: Chip Wiegand <chip@wiegand.org> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Xfree86 Setup problem continued with changes Message-ID: <ba4rbaxtyq.rba@localhost.localdomain> In-Reply-To: <20021025064112.4d0c0e07.chip@wiegand.org> References: <3DB8D805.5080304@wiegand.org> <5.1.0.14.2.20021025090708.00aaae60@pop51.bellnet.ca> <20021025064112.4d0c0e07.chip@wiegand.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Chip Wiegand <chip@wiegand.org> writes: > It's working now, I did have to set the HorizSync and VertRefresh > info manually. Seems I recall reading something about X not needing > those anymore after v4.1.0, but maybe not. My /var/log/XFree86.0.log has this line (II) RADEON(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 95 kHz, PixClock max 210 MHz which seems to be related to this nearby prior line (II) RADEON(0): I2C bus "DDC" initialized. Note that the lines have "(II)", not "(**)". I suppose that if your monitor supports the I2C/DDC protocol (AKA PnP?), then X can get the "Ranges" as above and use it. I had hand-entered the same numbers from the Monitor's spec sheet, so I don't know if it actually works automatically. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ba4rbaxtyq.rba>