Here's the log: 
 
------------------------------------------------------------------------ 
X: warning; process set to priority -1 instead of requested priority 0 
 
This is a pre-release version of XFree86, and is not supported in any 
way.  Bugs may be reported to XFree86@XFree86.Org and patches submitted 
to fixes@XFree86.Org.  Before reporting bugs in pre-release versions, 
please check the latest version in the XFree86 CVS repository 
(http://www.XFree86.Org/cvs). 
 
XFree86 Version 4.3.99.12 (DRI trunk) 
Release Date: 10 September 2003 
X Protocol Version 11, Revision 0, Release 6.6 
Build Operating System: Linux 2.4.21 i686 [ELF] 
Current Operating System: Linux billy 2.6.7 #1 SMP Fri Jul 30 12:26:03 CEST 
2004 i686 
Build Date: 23 September 2003 
Changelog Date: 10 September 2003 
        Before reporting problems, check http://www.XFree86.Org/ 
        to make sure that you have the latest version. 
Module Loader present 
Markers: (--) probed, (**) from config file, (==) default setting, 
        (++) from command line, (!!) notice, (II) informational, 
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown. 
(==) Log file: "/var/log/XFree86.0.log", Time: Tue Sep 14 16:15:16 2004 
(==) Using config file: "/etc/X11/XF86Config-4" 
(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found 
Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo, removing 
from list! 
Could not init font path element /var/lib/defoma/x-ttcidfont-conf.d/dirs/CID, 
removing from list! 
Could not init font path element /usr/share/fonts/afms, removing from list! 
Could not init font path element /usr/share/fonts/override, removing from 
list! 
Could not init font path element /usr/local/share/fonts, removing from list! 
Could not init font path element /usr/share/fonts, removing from list! 
Could not init font path element /usr/X11R6/lib/X11/fonts, removing from list! 
SetClientVersion: 0 8 
------------------------------------------------------------------------ 
 
BTW: I also tried every combination of "screen" and "BusID" 
 

do not use BusID "PCI:1:0:1" that is just a placeholder for the windows drivers.
 Use BusID "PCI:1:0:0" for both device sections.  if that doesn't fix it, try
adding the appropriate "monitorlayout" option to your device section (see the
radeon man page for more)
e.g.,
option "monitorlayout" "tmds,crt"
for dvi plus crt, or
option "monitorlayout" "crt,crt"
for two crts.

Also not that crtc1 (screen 0) always drives the dvi port, while crtc2 (screen
1) drives the vga port.  You may need to adjust your monitors accordingly.

Also if you are using dri cvs or xorg cvs you can use mergedfb rather than
xinerama for multihead.  it has some advantages and is more flexible in many ways.

Thx for the fast reply 
 
(In reply to comment #2) 
> do not use BusID "PCI:1:0:1" that is just a placeholder for the windows 
drivers. 
>  Use BusID "PCI:1:0:0" for both device sections. 
 
I tried that and get a sig11 
1 Device has option "screen 0" and the other "screen 1" 
both have 'BusID "PCI:1:0:0"' now. 
 
------------------------------------------------------------------------ 
This is a pre-release version of XFree86, and is not supported in any 
way.  Bugs may be reported to XFree86@XFree86.Org and patches submitted 
to fixes@XFree86.Org.  Before reporting bugs in pre-release versions, 
please check the latest version in the XFree86 CVS repository 
(http://www.XFree86.Org/cvs). 
 
XFree86 Version 4.3.99.12 (DRI trunk) 
Release Date: 10 September 2003 
X Protocol Version 11, Revision 0, Release 6.6 
Build Operating System: Linux 2.4.21 i686 [ELF] 
Current Operating System: Linux billy 2.6.7 #1 SMP Fri Jul 30 12:26:03 CEST 
2004 i686 
Build Date: 23 September 2003 
Changelog Date: 10 September 2003 
        Before reporting problems, check http://www.XFree86.Org/ 
        to make sure that you have the latest version. 
Module Loader present 
Markers: (--) probed, (**) from config file, (==) default setting, 
        (++) from command line, (!!) notice, (II) informational, 
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown. 
(==) Log file: "/var/log/XFree86.0.log", Time: Tue Sep 14 16:22:13 2004 
(==) Using config file: "/etc/X11/XF86Config-4" 
 
(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found 
 
   *** If unresolved symbols were reported above, they might not 
   *** be the reason for the server aborting. 
 
Fatal server error: 
Caught signal 11.  Server aborting 
 
 
When reporting a problem related to a server crash, please send 
the full server output, not just the last messages. 
This can be found in the log file "/var/log/XFree86.0.log". 
Please report problems to xfree86@xfree86.org. 
 
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0" 
      after 0 requests (0 known processed) with 0 events remaining. 
----------------------------------------------------------------------- 
 
 
>  if that doesn't fix it, try 
> adding the appropriate "monitorlayout" option to your device section (see 
the 
> radeon man page for more) 
> e.g., 
> option "monitorlayout" "tmds,crt" 
> for dvi plus crt, or 
> option "monitorlayout" "crt,crt" 
> for two crts. 
 
 
Tried that, same problem. 
 
  
> Also not that crtc1 (screen 0) always drives the dvi port, while crtc2 
(screen 
> 1) drives the vga port.  You may need to adjust your monitors accordingly. 
>  
> Also if you are using dri cvs or xorg cvs you can use mergedfb rather than 
> xinerama for multihead.  it has some advantages and is more flexible in many 
ways. 
>  
 
I guess when I use mergedfb maximizing windows will maximize across all 
screens :( 
 

(In reply to comment #3)
> Thx for the fast reply 
>  
> (In reply to comment #2) 
> > do not use BusID "PCI:1:0:1" that is just a placeholder for the windows 
> drivers. 
> >  Use BusID "PCI:1:0:0" for both device sections. 
>  
> I tried that and get a sig11 
> 1 Device has option "screen 0" and the other "screen 1" 
> both have 'BusID "PCI:1:0:0"' now. 

I'm not quite sure why that is happening...

>  
>  
> I guess when I use mergedfb maximizing windows will maximize across all 
> screens :( 
>  

no. mergedfb provides it's own xinerama extension so it will work like regular
xinerama, however, you can't use the pseudo-xinerama extention in conjunction
with real xinerama (ie, 2 heads of the radeon and another card for 3 heads, etc.).

(In reply to comment #4) 
> (In reply to comment #3) 
> > I guess when I use mergedfb maximizing windows will maximize across all  
> > screens :(  
> >   
>  
> no. mergedfb provides it's own xinerama extension so it will work like 
regular 
> xinerama, however, you can't use the pseudo-xinerama extention in 
conjunction 
> with real xinerama (ie, 2 heads of the radeon and another card for 3 heads, 
etc.). 
 
That's the reason why I don't use the fglrx drivers. I need 3 heads. 
I'd hate to switch back to my aged matrox g550 :( 
 

Created attachment 898 [details]
strace of sig11 for command X

This is the output of `strace X` sig11'ing when both devices take the same
BusID for Xinerama purpose.

this is a DDX problem.

*** This bug has been marked as a duplicate of 1559 ***