Re: Hal monitor detection, was hal documentation
On Sun, Apr 26, 2009 at 22:07:22 -0700, Paul Scott wrote:
> Paul Scott wrote:
>> On Apr 25, 2009, at 2:58 PM, Florian Kulzer wrote:
>>> On Sat, Apr 25, 2009 at 08:35:18 -0700, Paul Scott wrote:
>>>> On Apr 25, 2009, at 2:02 AM, Paul Scott wrote:
>>>
>>> [...]
>>>
>>>> So why can 'Xorg -configure' detect my monitor frequencies
>>>> correctly and
>>>> whatever Hal uses can't? get-edid doea correctly get the monitor name.
>>>> Does Hal depend on some kind of database to get the monitor spec's that
>>>> my Dell M770 monitor may not be in?
>>>
>>> What gives you the idea that HAL is now involved in the monitor
>>> detection of Xorg? I run the current Xorg 7.4 on Sid (with an almost
>>> empty xorg.conf) and my Xorg.0.log claims that the video driver module
>>> probes the monitor, just like it was for the older versions.
[...]
> Here's the portion of the log from my current configuration (from Xorg
> -configure) which works fine.
>
> (II) NV(0): I2C device "DDC:E-EDID segment register" registered at
> address 0x60.
> (II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
> (II) NV(0): ... none found
> (II) NV(0): Probing for EDID on I2C bus B...
> (II) NV(0): ... none found
> (--) NV(0): CRTC 0 appears to have a CRT attached
> (II) NV(0): Using CRT on CRTC 0
> (--) NV(0): VideoRAM: 32768 kBytes
> (==) NV(0): Using gamma correction (1.0, 1.0, 1.0)
> (II) NV(0): Monitor0: Using hsync range of 30.00-69.00 kHz
> (II) NV(0): Monitor0: Using vrefresh range of 48.00-160.00 Hz
> (WW) NV(0): Unable to estimate virtual size
> (II) NV(0): Clock range: 12.00 to 350.00 MHz
It looks like the nv driver cannot read the EDID of the attached
monitor. This is not really a problem as long as you specify reasonable
values for the allowed hsync and vrefresh ranges in xorg.conf.
> Here's the same portion from the log which doesn't work:
[...]
> (II) NV(0): <default monitor>: Using default hsync range of 31.50-37.90 kHz
> (II) NV(0): <default monitor>: Using default vrefresh range of 50.00-70.00 Hz
However, if there is no information about hsync and vrefresh in the
configuration file then the driver will use rather conservative default
values to avoid risking damage to the monitor. The narrow ranges of
allowed frequencies limit the possible resolutions.
For reference, here is what the log shows on my system, with the intel
driver retrieving the correct frequency ranges from the EDID:
(II) intel(0): Using EDID range info for horizontal sync
(II) intel(0): Using EDID range info for vertical refresh
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ snip: more valid modelines for other resolutions and frequencies ]
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Reply to: