ATI SurroundView MulitMonitor Support

[Michael Krufky]

Alex Deucher wrote:

>On 9/22/05, Michael Krufky <mkrufky at m1k.net> wrote:
>  
>
>>I have made some progress, but still not perfect.  Please see the
>>updated configuration:
>>
>>http://techsounds.org/Xorg.0.log
>>
>>http://techsounds.org/xorg.conf
>>
>>Now I have messages from 3 Radeon(x) devices ... The error log above is
>>produced by the "Triple" layout. (doesn't work, but contains good info)
>>The "Single" isn't working either.  I have even tried replacing
>>"Screen1" with "Screen2" or "Screen3"... neither work in "Single" layout.
>>
>>The "Double" Layout DOES work, except I can only see a picture on the
>>primary monitor.  X seems to think that there is a second monitor
>>functioning, as the mouse moves off the screen, but I dont see a picture
>>on either of the other two screens.  This is working with it setup to
>>use the 2 screens hooked up to 9600XT (screen1 and screen2).  I've tried
>>using Screen1+Screen3 and it doesnt work.  Same as Screen2+Screen3.
>>
>>errors like this jump out at me:
>>
>>Requesting insufficient memory window!: start: 0xb000 end: 0xb0ff size 0xd4000100
>>Requesting insufficient memory window!: start: 0xb400 end: 0xb4ff size 0xd4000100
>>Requesting insufficient memory window!: start: 0xb800 end: 0xb8ff size 0xd4000100
>>Requesting insufficient memory window!: start: 0xbc00 end: 0xbcff size 0xd4000100
>>(EE) Cannot find a replacement memory range
>>(WW) ****INVALID IO ALLOCATION**** b: 0xb400 e: 0xb500 correcting
>>
>>[...]
>>
>>Requesting insufficient memory window!: start: 0xb0000000 end: 0xdfffffff size 0xd4020000
>>Requesting insufficient memory window!: start: 0xe8000000 end: 0xe80fffff size 0xd4020000
>>Requesting insufficient memory window!: start: 0xb0000000 end: 0xdfffffff size 0xd4020000
>>Requesting insufficient memory window!: start: 0xe8000000 end: 0xe80fffff size 0xd4020000
>>Requesting insufficient memory window!: start: 0xb0000000 end: 0xdfffffff size 0xd4020000
>>Requesting insufficient memory window!: start: 0xe8000000 end: 0xe80fffff size 0xd4020000
>>(EE) RADEON(0): Cannot read V_BIOS
>>
>>[...]
>>
>>(EE) RADEON(2): Cannot read V_BIOS
>>
>
>Could be a posting problem.  In the bios try changing which card gets
>posted by the bios.
>
>>So, on the bright side, now I don't have to disable surroundview in BIOS
>>in order to get X working.  I'd like to get dual and triple monitors
>>working.  Any more suggestions?
>>
>another thing to try is to disable the dri.  just comment out the load
>dri line in your modules section.
>
Getting better..... After disabling dri, now both Triple layout and 
Double layout load up.  Under both of these configurations, I can only 
see one screen, but X seems to think that I have 3 or 2 screens, 
respectively.  I verified this by peeking into kinfocenter.

new log (using triple layout):
http://techsounds.org/Xorg.0.log

My BIOS doesnt let me change which card gets posted, but it does let be 
change which card inits first by the bios (i thought that would be the 
same thing, but it always posts to the agp card regardless)
This had no effect on the situation. 

Single layout still doesnt work.  This is what I get:

This is a pre-release version of the The X.Org Foundation X11.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the The X.Org Foundation "monolithic tree" CVS
repository hosted at http://www.freedesktop.org/Software/xorg/
X Window System Version 6.8.99.15
Release Date: 16 July 2005 + cvs
X Protocol Version 11, Revision 0, Release 6.8.99.15
Build Operating System: Linux 2.6.13.1 i686 [ELF]
Current Operating System: Linux aftermath 2.6.13.1 #1 SMP Sun Sep 18 
10:06:33 EST 2005 i686
Build Date: 18 September 2005
        Before reporting problems, check http://wiki.X.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/Xorg.0.log", Time: Thu Sep 22 19:10:14 2005
(==) Using config file: "/etc/X11/xorg.conf"
(WW) RADEON: No matching Device section for instance (BusID PCI:1:5:1) found
(WW) RADEON: No matching Device section for instance (BusID PCI:1:7:0) found
(WW) ****INVALID IO ALLOCATION**** b: 0xb000 e: 0xb100 correcting
Requesting insufficient memory window!: start: 0xb000 end: 0xb0ff size 
0xd4000100
Requesting insufficient memory window!: start: 0xb400 end: 0xb4ff size 
0xd4000100
Requesting insufficient memory window!: start: 0xb800 end: 0xb8ff size 
0xd4000100
Requesting insufficient memory window!: start: 0xbc00 end: 0xbcff size 
0xd4000100
(EE) Cannot find a replacement memory range
Requesting insufficient memory window!: start: 0xb0000000 end: 
0xdfffffff size 0xd4020000
Requesting insufficient memory window!: start: 0xe8000000 end: 
0xe80fffff size 0xd4020000
Requesting insufficient memory window!: start: 0xb0000000 end: 
0xdfffffff size 0xd4020000
Requesting insufficient memory window!: start: 0xe8000000 end: 
0xe80fffff size 0xd4020000
Requesting insufficient memory window!: start: 0xb0000000 end: 
0xdfffffff size 0xd4020000
Requesting insufficient memory window!: start: 0xe8000000 end: 
0xe80fffff size 0xd4020000
(EE) RADEON(0): Cannot read V_BIOS
Requesting insufficient memory window!: start: 0xb0000000 end: 
0xdfffffff size 0xd4020000
Requesting insufficient memory window!: start: 0xe8000000 end: 
0xe80fffff size 0xd4020000
Requesting insufficient memory window!: start: 0xb0000000 end: 
0xdfffffff size 0xd4020000
Requesting insufficient memory window!: start: 0xe8000000 end: 
0xe80fffff size 0xd4020000

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Backtrace:
0: X(xf86SigHandler+0x81) [0x8087380]

Fatal server error:
Caught signal 11.  Server aborting


Please consult the The X.Org Foundation support
         at http://wiki.X.Org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.

XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.

-- 
Michael Krufky