Bug 5097

Summary:

resolution clipped to 640x480

Product:

xorg

Reporter:

Dave Jones <davej>

Component:

Driver/Radeon

Assignee:

Xorg Project Team <xorg-team>

Status:

RESOLVED WORKSFORME

QA Contact:

Severity:

normal

Priority:

high

Version:

6.99.99.902 (7.0 RC2)

Hardware:

x86 (IA32)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Bug Depends on:

Bug Blocks:

1690

Attachments:

Description	Flags
config file that worked with the monolithic tree.	none
/var/log/Xorg.0.log	none

Description Dave Jones 2005-11-19 10:43:35 UTC

I think what's happening here is that for some reason, the frequency ranges for
the 2nd head in the config file are being ignored, and it fails to read ddc info
from the monitor (I dont think that ever worked). As a result, it falls back to
a "safe" mode.

(Xinerama is also busted, but I'm more concerned about the 1995's-esque display
right now).

I'll attach the conf/log later.

Comment 1 Dave Jones 2005-11-19 10:44:41 UTC

Created attachment 3845 [details]
config file that worked with the monolithic tree.

Comment 2 Dave Jones 2005-11-19 10:45:34 UTC

Created attachment 3846 [details]
/var/log/Xorg.0.log

Comment 3 Adam Jackson 2005-11-19 13:19:01 UTC

and you claim that worked before?  i was under the impression that the radeon
driver would refuse to claim the X:Y.1 device since it's a pseudo.  can you
attach an X log where that config worked in the monolith?

i think what you really want is:

Section "Device"
    Identifier  "Videocard0"
    Driver      "radeon"
    VendorName  "Videocard vendor"
    BoardName   "ATI Technologies Inc RV370 [Radeon X300SE]"
    BusID       "PCI:5:0:0"
    Option      "MonitorLayout" "TMDS,CRT"
    Option      "CRT2Hsync" "30-98"
    Option      "CRT2VRefresh" "50-160"
EndSection

Comment 4 Dave Jones 2005-11-19 13:43:08 UTC

that did the trick.

(For the benefit of others who may read this, my dual-head display also came
back with the addition of

Option "CRT2Position" "RightOf"

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.