Bug 2601 - Matrox G550 gets too low vertical frequencies.
Summary: Matrox G550 gets too low vertical frequencies.
Status: RESOLVED DUPLICATE of bug 4249
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/mga (show other bugs)
Version: 6.8.2
Hardware: Other Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-23 09:23 UTC by Bernhard R. Link
Modified: 2006-12-16 09:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Bernhard R. Link 2005-02-23 09:23:11 UTC
The Matrox G550 card in use here have a VGA output on head 1 and a DVI
output on head 2. (At least I guess those are 1 and 2). When booted with
only a device attached to the DVI output, it seems to switch to this
at boot time and all console output is at the DVI-out.
In this situation the mga driver (without HALlib) generates too low
vertical refresh rates. (The driver says it uses 60Hz, but the TFTs
either say out of range or the better model show something about 29 Hz)
Adding another output device to the VGA output also shows wrong frequencies
then.
Comment 1 Adam Jackson 2005-12-22 03:34:55 UTC

*** This bug has been marked as a duplicate of 4249 ***
Comment 2 Tilman Sauerbeck 2006-11-19 13:36:53 UTC
I believe I'm seeing the same problem on a G550 dual dvi (the card has one DVI
connector, but with that dual dvi cable you can connect two DFPs).

When I start X, the monitor says the frequencies are out of range. Not sure how
to test what frequency the driver is trying to use. Switching off the monitor
and switching it on again "fixes" the problem. Not sure whether that means I'm
slowly frying my monitor that way though.

The patch from #4249 does not help here.
Comment 3 Tilman Sauerbeck 2006-12-16 09:43:20 UTC
Disregard my comment above, it has nothing to do with Bernhard's problem.


*** This bug has been marked as a duplicate of 4249 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.