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

Bug#372918: negative refresh rates in xrandr



On Mon, Jun 12, 2006 at 02:43:34PM +0200, Soeren Sonnenburg wrote:
> when I look at the output of xrandr I see negative refresh rates not
> only confusing me but also e.g. gnome-display-properties (i.e. I can
> no longer change resolutions on the fly with that tool)

This is a known issue with MergedFB, since there is no good way to
express one refresh rate for two displays which almost certainly have
differing refresh rates.

> Section "Device"
>         Identifier      "ATI Radeon Internal"
>         Driver          "radeon"
>         BusID           "PCI:0:16:0"
>         Option          "UseFBDev"              "false"

IIRC this is the default.

>         Option          "AllowGLXWithComposite" "true"

This option is only useful with the nvidia driver.

>         Option          "AccelMethod" "xaa"

This option is also the default.

>         Option      	"backingstore" "true"

This option will not help your performance.

>         Option          "EnablePageFlip"        "true"

This option is highly problematic.

>         Option          "AGPMode" "4"

This option is almost certainly unnecessary.

>         Option          "AGPFastWrite" "true"

This option could well kill your machine.

>         Option          "MonitorLayout" "LVDS,TMDS"

This option is almost certainly unnecessary, unless you really need to
force it when you don't have a second monitor.

>         Option          "PanelSize" "1280x854"

This option is almost certainly unnecessary.

>         Screen 0
> EndSection
> 
> Section "Device"
>         Identifier      "ATI Radeon External"
>         [... more insanity ...]
>         Screen 1
> EndSection

You don't need to have separate Device sections for MergedFB: that's the
entire point behind it.

Attachment: signature.asc
Description: Digital signature


Reply to: