fglrx driver 3D graphics offset/displaced

[splinkyhead]

Hi All

Does anyone have any clues on how to fix an 'offset-ed' 3d display when using the fglrx driver. See http://thelonelycow.com/images/fgl_glxgears.jpg for a screenshot of what I am talking about.

I am running Ubuntu Edgy with the ubuntu fglrx drivers (8.28.8) from the universe/multiverse repository. I have a nice Big Desktop setup but this issue is really bugging me ...

- as you can see in the screenshot - I have accelerated 3d because I am able to run fgl_glxgears. The only thing is that anything 3d is offset to the left of window/full screen. This means that I can't play any games (enemy territory or unreal tournament 2004) with this setup because I only see a tiny slice of the right hand edge of the game. This is true whether the game is full screen or windowed-mode.

Anyone else experiencing this or know how to resolve it?

Thanks

pAntZ

[Michael]

I have seen this problem before but don't remember off hand how it was resolved.

Can you start by posting your xorg.conf?

[splinkyhead]

I have seen this problem before but don't remember off hand how it was resolved.

Can you start by posting your xorg.conf?

Sure I can - here it is ...

Section "ServerLayout"
	Identifier     "Default Layout"
	Screen      0  "aticonfig-Screen[0]" 0 0
	InputDevice    "Generic Keyboard"
	InputDevice    "Configured Mouse"
	InputDevice    "stylus" "SendCoreEvents"
	InputDevice    "cursor" "SendCoreEvents"
	InputDevice    "eraser" "SendCoreEvents"
	InputDevice    "Synaptics Touchpad"
EndSection

Section "Files"
	# path to defoma fonts
	FontPath     "/usr/share/X11/fonts/misc"
	FontPath     "/usr/share/X11/fonts/cyrillic"
	FontPath     "/usr/share/X11/fonts/100dpi/:unscaled"
	FontPath     "/usr/share/X11/fonts/75dpi/:unscaled"
	FontPath     "/usr/share/X11/fonts/Type1"
	FontPath     "/usr/share/X11/fonts/100dpi"
	FontPath     "/usr/share/X11/fonts/75dpi"
	FontPath     "/usr/share/fonts/X11/misc"
	FontPath     "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
	Load  "bitmap"
	Load  "ddc"
	Load  "dri"
	Load  "extmod"
	Load  "freetype"
	Load  "glx"
	Load  "int10"
	Load  "type1"
	Load  "vbe"
EndSection

Section "InputDevice"
	Identifier  "Generic Keyboard"
	Driver      "kbd"
	Option	    "CoreKeyboard"
	Option	    "XkbRules" "xorg"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
	Option	    "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
	Identifier  "Configured Mouse"
	Driver      "mouse"
	Option	    "CorePointer"
	Option	    "Device" "/dev/input/mice"
	Option	    "Protocol" "ExplorerPS/2"
	Option	    "ZAxisMapping" "4 5"
	Option	    "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
	Identifier  "Synaptics Touchpad"
	Driver      "synaptics"
	Option	    "SendCoreEvents" "true"
	Option	    "Device" "/dev/psaux"
	Option	    "Protocol" "auto-dev"
	Option	    "HorizScrollDelta" "0"
EndSection

Section "Extensions"
	Option "Composite" "Disable"
	Option "Composite" "false"
EndSection

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]"
	Option	    "VendorName" "ATI Proprietary Driver"
	Option	    "ModelName" "Generic Autodetecting Monitor"
	Option	    "DPMS" "true"
EndSection

Section "Device"
	Identifier  "aticonfig-Device[0]"
	Driver      "fglrx"
	Option	    "VideoOverlay" "on"
	Option	    "OpenGLOverlay" "off"
        Option      "DesktopSetup" "horizontal,reverse"
	Option      "DesktopSetup" "AUTO,AUTO"
	#Option      "DesktopSetup" "LVDS,CRT"
	#Option      "DesktopSetup" "CRT,LVDS"
	Option      "Mode2" "1600x1200"
        Option	    "HSync2" "30.0-96.0"
        Option      "VRefresh2" "50.0-160.0"
EndSection

Section "Screen"
	Identifier "aticonfig-Screen[0]"
	Device     "aticonfig-Device[0]"
	Monitor    "aticonfig-Monitor[0]"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

Section "DRI"
	Mode         0666
EndSection

Thanks for the quick reply!

pAntZ

[Michael]

What happens if you try

aticonfig --initial --force

you sure have a lot of options set in your conf, which could be causing the problems.

[splinkyhead]

Running 'aticonfig --initial --force' gives me an xorg.conf file that allows me to have a single head with fully functional 3d graphics. Meaning that any games and fgl_glxgears run perfectly centered in the middle of the screen/window.

This is ok, and I had previously been able to reproduce this configuration. The problem begins when I add the following two lines to my Device section (which are necessary for my Big Desktop setup) ...

Option "DesktopSetup" "horizontal,reverse"
Option "Mode2" "1600x1200"

Here is my Big Desktop config in its most stipped down possible state - and is still giving the 'offset' display as in the original screenshot ...

Section "ServerLayout"
	Identifier     "Default Layout"
	Screen      0  "aticonfig-Screen[0]" 0 0
	InputDevice    "Generic Keyboard"
	InputDevice    "Configured Mouse"
	InputDevice    "Synaptics Touchpad"
EndSection

Section "Files"
	# path to defoma fonts
	FontPath     "/usr/share/X11/fonts/misc"
	FontPath     "/usr/share/X11/fonts/cyrillic"
	FontPath     "/usr/share/X11/fonts/100dpi/:unscaled"
	FontPath     "/usr/share/X11/fonts/75dpi/:unscaled"
	FontPath     "/usr/share/X11/fonts/Type1"
	FontPath     "/usr/share/X11/fonts/100dpi"
	FontPath     "/usr/share/X11/fonts/75dpi"
	FontPath     "/usr/share/fonts/X11/misc"
	FontPath     "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
	Load  "bitmap"
	Load  "ddc"
	Load  "dri"
	Load  "extmod"
	Load  "freetype"
	Load  "glx"
	Load  "int10"
	Load  "type1"
	Load  "vbe"
EndSection

Section "InputDevice"
	Identifier  "Generic Keyboard"
	Driver      "kbd"
	Option	    "CoreKeyboard"
	Option	    "XkbRules" "xorg"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
	Option	    "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
	Identifier  "Configured Mouse"
	Driver      "mouse"
	Option	    "CorePointer"
	Option	    "Device" "/dev/input/mice"
	Option	    "Protocol" "ExplorerPS/2"
	Option	    "ZAxisMapping" "4 5"
	Option	    "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
	Identifier  "Synaptics Touchpad"
	Driver      "synaptics"
	Option	    "SendCoreEvents" "true"
	Option	    "Device" "/dev/psaux"
	Option	    "Protocol" "auto-dev"
	Option	    "HorizScrollDelta" "0"
EndSection

Section "Extensions"
	Option "Composite" "Disable"
EndSection

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]"
	Option	    "VendorName" "ATI Proprietary Driver"
	Option	    "ModelName" "Generic Autodetecting Monitor"
	Option	    "DPMS" "true"
EndSection

Section "Device"
	Identifier  "aticonfig-Device[0]"
	Driver      "fglrx"
    Option      "DesktopSetup" "horizontal,reverse"
	Option      "Mode2" "1600x1200"
EndSection

Section "Screen"
	Identifier "aticonfig-Screen[0]"
	Device     "aticonfig-Device[0]"
	Monitor    "aticonfig-Monitor[0]"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

Section "DRI"
	Mode         0666
EndSection

Any ideas?

pAntZ

[glussier]

I think you get this problem because the fglrx support 3d opengl on a max width of 2560pixels. Since you have a 3200pixels width, you only get 3d acceleration on the first 2560 pixels. If you move the PBuffer GLXgears box on the other screen you won't see this behavior. The other way to avoir the problem, is to either limit you max width to 2560 of to set your screens in a vertical configuration.

[splinkyhead]

Thanks glussier

You pretty much hit the nail on the head with that one. I forced both of my resolutions to 1280x1024 and was able to have accelerated 3d graphics run perfectly centered in the window it was running in.

*sigh*

Is there any chance that this is a driver limitation that might be resolved in a future release? or is it a hardware limitation - I have a Mobility Radeon X300 in my laptop.

The low resolutions just don't cut it for me - so I am stuck at killing X (and all of my apps) and loading a single head config that works. Not the most convenient practice ...

Thanks

pAntZ

[glussier]

Is there any chance that this is a driver limitation that might be resolved in a future release? or is it a hardware limitation -

I don't know if this will be fixed in the future? Note that nvidia has the same limitation. As for an hardware limitation, I don't know, 'cause if you run dual head, as oppose to extended desktop, each head can display the 2560 resolution.

[splinkyhead]

Interestingly, I just verified with my colleague who has a similar laptop but his is widescreen and has a X1600 card.

He is able to run his Big Desktop with the laptop resolution at 1680x1050 and his second screen at 1280x1024. This gives a combined total of 3360x1050 according to his 'xrandr -q' output (but I would have thought it more like 2960x1050).

Anyway - he has no dead zones, or strange mouse offset issues, and his two lcd screens are running in their native resolutions that give a combined total width that is certainly larger than 2560, and he is able to run 3d apps with no problem at all - ARGGHH.

The worst part of it all is that he took my xorg.conf - changed the resolution of his second monitor - and everything worked for him out of the box! (out of MY box you could say!).

Would the difference in card (X300 vs X1600) explain the discrepancy between the two configurations?

pAntZ

[bugmenot]

Okay, sorry for bringing up this new thread, but I just encountered the same problem, and managed to create a workaround:

The problem is caused in xorg.conf by the line:

Option      "DesktopSetup" "horizontal,reverse"

The 'reverse'-tag marks that your secondary monitor is left to your primary, but it makes your overlay f'ed up.

Here is my easy workaround:

1. Change the line in your xorg.conf to

   Option      "DesktopSetup" "horizontal"

2. swap your monitors physically