| Summary: | mergedfb broken with xorg-server-1.2.0 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Gilles Dartiguelongue <gilles.dartiguelongue> | ||||||||
| Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> | ||||||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
| Severity: | major | ||||||||||
| Priority: | medium | CC: | bugs, nickbroon | ||||||||
| Version: | 7.2 (2007.02) | ||||||||||
| Hardware: | Other | ||||||||||
| OS: | Linux (All) | ||||||||||
| Whiteboard: | |||||||||||
| i915 platform: | i915 features: | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Gilles Dartiguelongue
2007-01-30 15:36:18 UTC
Created attachment 8546 [details]
xorg.conf
This is my configuration file.
I'm using xf86-video-radeon-6.6.3
Originaly posted as : http://lists.freedesktop.org/archives/xorg/2007-January/021403.html A problem that looks similar : http://lists.freedesktop.org/archives/xorg/2007-January/021287.html Am also having this issue; can recreate and post logs & xorg.conf as necessary. Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. I experienced the same problem after upgrading my ubuntu/feisty x11 packages two or three days ago. I compared the logs and discover quite new message appearing during validation of modes: "mode clock too high". There is only one check that may result, if failed, in such a message: http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=blob;h=fc905dfac38fb7a253b8cd54b1379da430bd635c;hb=39ecd6fff4f946deebe310b4b26b171c842db223;f=hw/xfree86/common/xf86Mode.c#l905 However, a new member of monitor structure named maxPixClock has been introduced, radeon driver does not care about it at all which makes the value completely random. I tried assigning info->CRT2pScrn->monitor->maxPixClock (look the patch below) I got the driver working, i.e. dual head without cloning. Created attachment 8953 [details] [review] prevent maxPixClock from being completely random. maxPixClock should be assigned more reasonable value, possibly DDC detected one. But zero brings back MergedFB. What seems strange is that it doesn't matter if the first monitor's maxPixClock is zero or not. looks like it's fixed with xorg-server 1.3 with xf86-video-ati-6.6.191 could somebody confirm ? Created attachment 10237 [details] [review] Fully zero-initialize CRTC2 monitor struct Łukasz, does this patch help as well? Several people reported my patch to work in the Debian BTS, pushed as commit ac9cbaf32176cf144bc694ac879e7c9e2920f762. |
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.