Zaphod mode with the Open Source Driver?

[pal15]

Is there a way to find out which command is used in this distro to configure Xorg?

[pal15]

I found something: sax2 command is gone from 11.3 and there is no replacement. Well, that's a big help. But there is more, xorg.conf is now replaced by snippets in xorg.conf.d directory. I see now why people like Gentoo.

[Chewi]

aticonfig is for use with ATI's proprietary driver. Don't use it for anything else.

The xorg.conf.d snippets are not SUSE-specific. This is now the preferred way to configure X.Org Server as of 1.8. To be honest, you should at least have a basic working setup with no xorg.conf at all. Autodetection works pretty well these days.

For Zaphod, you need to use the ZaphodHeads option. It is in the radeon man page but I'm feeling generous. Here's my xorg.conf. If your monitors are not called DVI-0 and DVI-1 (they probably are) then you'll need to adjust these.

Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen	0	"Screen0" 0 0
	Screen		"Screen1" LeftOf "Screen0"
EndSection

Section "Monitor"
	Identifier "DIN"
EndSection

Section "Monitor"
	Identifier   "DVI-0"
EndSection

Section "Monitor"
	Identifier   "DVI-1"
EndSection

Section "Device"
	Identifier  "Card0"
	Driver      "radeon"
	VendorName  "ATI Technologies Inc"
	BoardName   "RV730XT [Radeon HD 4670]"
	BusID       "PCI:1:0:0"

	Option "ZaphodHeads" "DVI-1"
	Screen 0
EndSection

Section "Device"
	Identifier  "Card1"
	Driver      "radeon"
	BusID       "PCI:1:0:0"

	Option "ZaphodHeads" "DVI-0"
	Screen 1
EndSection

Section "Screen"
	Identifier "Screen0"
	Device "Card0"
	Monitor "DVI-1"
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

Section "Screen"
	Identifier "Screen1"
	Device "Card1"
	Monitor "DVI-0"
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

Section "DRI"
	Group "video"
	Mode 0660
EndSection

I don't know what OpenSUSE uses to configure xorg.conf now but I highly doubt it knows about the ZaphodHeads option, especially given that radeonhd is still the official driver for that distribution. Gentoo wouldn't help you much in this regard. Most configuration is done by hand. But you start to like it that way.

[droste]

pal15:
You can still use a xorg.conf and don't have to use xorg.conf.d. sax2 was dropped because autodetection works for the most setups. Switching the distro doesn't help you to get sax2 back, because only suse used it.

chewi:
as far as i know openSUSE 11.3 uses radeon+kms (not radeonhd) for all radeon cards

[Chewi]

as far as i know openSUSE 11.3 uses radeon+kms (not radeonhd) for all radeon cards

Okay. I just couldn't find it on their packages site, only radeonhd.

[adamk]

Okay. I just couldn't find it on their packages site, only radeonhd.

They seem to package all their video drivers (aside from radeonhd) together:

[adamk@sorrow ~]$ rpm -qf /usr/lib64/xorg/modules/drivers/radeon_drv.so
xorg-x11-driver-video-7.5-15.2.x86_64
[adamk@sorrow ~]$ rpm -ql xorg-x11-driver-video | grep modules | grep drv.so
/usr/lib64/xorg/modules/drivers/apm_drv.so
/usr/lib64/xorg/modules/drivers/ark_drv.so
/usr/lib64/xorg/modules/drivers/ast_drv.so
/usr/lib64/xorg/modules/drivers/ati_drv.so
/usr/lib64/xorg/modules/drivers/chips_drv.so
/usr/lib64/xorg/modules/drivers/cirrus_drv.so
/usr/lib64/xorg/modules/drivers/dummy_drv.so
/usr/lib64/xorg/modules/drivers/fbdev_drv.so
/usr/lib64/xorg/modules/drivers/glint_drv.so
/usr/lib64/xorg/modules/drivers/i128_drv.so
/usr/lib64/xorg/modules/drivers/i740_drv.so
/usr/lib64/xorg/modules/drivers/intel_drv.so
/usr/lib64/xorg/modules/drivers/mach64_drv.so
/usr/lib64/xorg/modules/drivers/mga_drv.so
/usr/lib64/xorg/modules/drivers/neomagic_drv.so
/usr/lib64/xorg/modules/drivers/newport_drv.so
/usr/lib64/xorg/modules/drivers/nv_drv.so
/usr/lib64/xorg/modules/drivers/r128_drv.so
/usr/lib64/xorg/modules/drivers/radeon_drv.so
/usr/lib64/xorg/modules/drivers/rendition_drv.so
/usr/lib64/xorg/modules/drivers/s3_drv.so
/usr/lib64/xorg/modules/drivers/s3virge_drv.so
/usr/lib64/xorg/modules/drivers/savage_drv.so
/usr/lib64/xorg/modules/drivers/siliconmotion_drv.so
/usr/lib64/xorg/modules/drivers/sis_drv.so
/usr/lib64/xorg/modules/drivers/sisusb_drv.so
/usr/lib64/xorg/modules/drivers/tdfx_drv.so
/usr/lib64/xorg/modules/drivers/tga_drv.so
/usr/lib64/xorg/modules/drivers/trident_drv.so
/usr/lib64/xorg/modules/drivers/tseng_drv.so
/usr/lib64/xorg/modules/drivers/v4l_drv.so
/usr/lib64/xorg/modules/drivers/vesa_drv.so
/usr/lib64/xorg/modules/drivers/vmware_drv.so
/usr/lib64/xorg/modules/drivers/voodoo_drv.so
/usr/lib64/xorg/modules/multimedia/theatre200_drv.so
/usr/lib64/xorg/modules/multimedia/theatre_detect_drv.so
/usr/lib64/xorg/modules/multimedia/theatre_drv.so

[pal15]

Configured snippets and was able to get only one scree with incorrect resolution. Moved all config into single xorg.conf file rebooted and black screened.

Now trying to resolve that. But in the mean time I have question:

In 11.2 sax2 was generating Sections Files, Modules, etc. Then I was able just to tweak it a bit, add ZapfodHeads statement, etc. Here in 11.3 xorg.conf.d snippets sections Files, Modules are absent. Are they required or optional?

[pal15]

How does X.org autoconfig work? When I booted 11.3 after install snippets in xorg.conf.d where defaulted, unconfigured. But, the screen was authdetected and configured right. Where X.org server keep that info? Some temp file? So, every time it boots up it redetects, and generate current config? If I could copy that content created by autocinfig and tweak it for ZaphodMode I think I could have much better chance getting it to work. Is there a way to get that code generated bu autoconfig which operantly is not getting written into xorg.conf nor xorg.conf.d snippets.

[adamk]

It doesn't store that as a configuration file. You can create one, essentially the same as what Xorg autoconfigured, by running 'Xorg -configure'.

Adam

[Chewi]

The Files and Modules sections aren't really needed any more. It doesn't really generate a config file anywhere, it just builds the config structure internally as it would do if it were reading from a file. The config I posted above is pretty much the minimum that is required so use that. Check the log for the detected monitor names in case they aren't DVI-0 and DVI-1. You might need to remove the DIN monitor as well as that is for my TV out.