Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://freedesktop.org/bugzilla/show_bug.cgi?id=1374
------- Additional Comments From [EMAIL PROTECTED] 2004-09-14 07:31 ------- 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 [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 :( -- Configure bugmail: https://freedesktop.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
