[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#287798: config script for xserver-xfree86 limits refresh rates



retitle 287798 xserver-xfree86: debconf doesn't always choose optimal monitor characteristics automatically
thanks

On Thu, Dec 30, 2004 at 01:03:28AM -0500, chris wrote:
> Package:    xserver-xfree86
> Version:     4.3.0.dfsg.1-8_i386  
> 
> xserver-xfree86_4.3.0.dfsg.1-8_i386.deb
> 
>    Linux  2.6.8-1-k7  i686 GNU/Linux
> 
>    libc6 Version: 2.3.2.ds1-18
> 
> The config script for xserver-xfree86 has a Design, which makes
> it impossible to get maximal/optimal HorizSync/VertRefresh ranges.

That's an overstatement, in my opinion.  You can always pick the "Advanced"
monitor selection method and enter whatever horizontal sync and vertical
refresh parameters you want.

> "/var/lib/dpkg/info/xserver-xfree86.config" has limitation of 75 Hz @ 
> 1024x768, why it gets 85 Hz I don't know, but my *Reflex FX*7200 model 
> 1792E [approx. ~ CTX-1785GM] monitor can do 117 Hz.
> "xvidtune" picks up a max of 105 Hz:
> 
> Vendor: , Model:
> Num hsync: 1, Num vsync: 1
> hsync range 0:  30.00 -  95.00
> vsync range 0:  50.00 - 105.00
> "1024x768"    113.31   1024 1096 1208 1392    768  769  772  814 -hsync 
> +vsync

Autodetction is a hard problem, for tedious technical reasons having to do
with the DDC extension to VESA signaling standards, the multiple DDC
implementations out there, the sometimes conflicting versions of those
standards that monitors vs. display adapters choose to support, the
real-mode x86 programming that is required to perform DDC probing, and so
forth.

Due to the above unholy mess, I plan to get Debian's X Window System
packages out of the hardware detection business altogether.  The X server's
maintainer scripts will become a dumb interface to the configuration file,
and it's going to be up to the installation system to get a hardware
detection system in place on the system before configuring the X server.

(Strictly speaking, that's already true, but the fact that the X server's
maintainer scripts actually *try* to do detection today if it hasn't been
done already tempts people to just leave the problem in the X packages'
court.)

The other advantage to decoupling as I propose is that we can just publish
an interface (being a set of debconf templates), and as many "X detectors"
as the Debian Project chooses to write and/or maintain can fight for
supremacy and userbase.

However, don't look for this overhaul before xorg-x11 6.8.2 enters
unstable.

-- 
G. Branden Robinson                |    If the license you accept is
Debian GNU/Linux                   |    oppressive in its terms, that means
branden@debian.org                 |    you can be oppressed.
http://people.debian.org/~branden/ |    -- Pamela Jones

Attachment: signature.asc
Description: Digital signature


Reply to: