Announcement

Collapse
No announcement yet.

Dual monitors on fglrx 10.5 / Slackare 13.1

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Dual monitors on fglrx 10.5 / Slackare 13.1

    I can't get fglrx to let me run two monitors at 1280x1024. If I try to adjust the resolution, I get the dreaded: "xrandr: screen cannot be larger than 2048x2048 (desired size 2560x1024)"

    Fglrx, however, has chosen to ignore the Virual I have in my xorg.conf file:

    Code:
    Section "ServerLayout"
    	Identifier     "aticonfig Layout"
    	Screen      0  "aticonfig-Screen[0]-0" 0 0
    EndSection
    
    Section "Files"
    EndSection
    
    Section "Module"
    EndSection
    
    Section "Monitor"
    	Identifier "DFP2"
    EndSection
    
    Section "Monitor"
    	Identifier "CRT2"
        	Option "RightOf" "DFP2"
    EndSection
    
    Section "Device"
    	Identifier  "aticonfig-Device[0]-0"
    	Driver      "fglrx"
    	BusID       "PCI:7:0:0"
    	Option 	"Monitor-DFP2" "DFP2"
    	Option	"Monitor-CRT2" "CRT2"
    EndSection
    
    Section "Screen"
    	Identifier "aticonfig-Screen[0]-0"
    	Device     "aticonfig-Device[0]-0"
    	DefaultDepth     24
    	SubSection "Display"
    		Viewport   0 0
    		Depth     24
    		Virtual	     2560 1024
    	EndSubSection
    EndSection[
    And the /var/log/Xorg.0.log file: http://pastebin.com/c2XZucGd

    There's no mention of "Virtual" in that log file.

    How can I get this working?

    Adam

  • #2
    Do you get the same error message when you use the xorg.conf created by aticonfig --initial -f ?

    Comment


    • #3
      Yes, I get the error message then, too. I have managed to fix it, though. I had to set the Virtual to 2560 2560 rather than 2560 1024. Not sure why as I was just trying to run the two monitors at 1280x1024. I think fglrx needs a little work on its math and logic skills :-)

      Adam

      Comment


      • #4
        Hi Adam.

        Have you applied any patch to the 10.5 catalyst driver before installing it? Or have you just installed the vanilla drivers from ATI's website?

        Thanks.

        Comment


        • #5
          I, personally, did not apply any patch, though the installer included a patch to get the driver to compile on > 2.6.33.

          Adam

          Comment


          • #6
            Hmmm...you mean, not only the original install program from ATI, but a third part one?

            Comment


            • #7
              No, the original install program. It says:

              Code:
              Found internal patch:
                      patch-8.73x-2.6.33+
              When it builds the slackware packages.

              Adam

              Comment


              • #8
                Nice...
                I've just extracted the file with the --extract option:

                sh ati-driver-installer-10-5-x86.x86_64.run --extract

                and then, I've found the files related to the patch you are referring to:

                find . -name "*patch*"
                (...)
                ./packages/Slackware/patch
                ./packages/Slackware/patch/patch-8.73x-2.6.33+
                ./packages/Slackware/patch_functions.sh
                (...)

                So I'll start to upgrade now. I also have a multi-monitor setup (3 monitor), and perhaps the same card as you do (4850). If I get into the same problem as you, I hope I can solve it and help you to.

                Thanks!

                Comment


                • #9
                  Well, well, well...

                  I've successfully installed Slackware 13.1 and Catalyst 10.5, thanks to your hint about building a Slackware package:

                  PHP Code:
                  sh ati-driver-installer-10-5-x86.x86_64.run --buildpkg Slackware/All
                  but I had no joy configuring my 3 monitor xinerama setup:

                  PHP Code:
                  aticonfig --initial=dual-head ---adapter=all --xinerama=on 
                  command status is OK, xorg.conf is created, but whenever I start X, I get three blank screens and an irresponsible system. Xorg.0.log shows a nice segmentation fault:

                  PHP Code:
                  (IIAIGLXLoaded and initialized /usr/X11R6/lib64/modules/dri/fglrx_dri.so
                  (IIGLXInitialized DRI GL provider for screen 1

                  Backtrace
                  :
                  0: /usr/bin/(xorg_backtrace+0x28) [0x461c78]
                  1: /usr/bin/(0x400000+0x5a799) [0x45a799]
                  2: /lib64/libpthread.so.0 (0x7fca4e3d2000+0xf770) [0x7fca4e3e1770]
                  3: /usr/lib64/xorg/modules/glesx.so (0x7fca48b5a000+0x1204f8) [0x7fca48c7a4f8]
                  4: /usr/lib64/xorg/modules/glesx.so (0x7fca48b5a000+0x1208b7) [0x7fca48c7a8b7]
                  5: /usr/lib64/xorg/modules/glesx.so (0x7fca48b5a000+0x120e3f) [0x7fca48c7ae3f]
                  6: /usr/lib64/xorg/modules/glesx.so (0x7fca48b5a000+0xa657b) [0x7fca48c0057b]
                  7: /usr/lib64/xorg/modules/glesx.so (0x7fca48b5a000+0xa6772) [0x7fca48c00772]
                  8: /usr/lib64/xorg/modules/glesx.so (0x7fca48b5a000+0xcb67e) [0x7fca48c2567e]
                  9: /usr/lib64/xorg/modules/glesx.so (0x7fca48b5a000+0xd6ab9) [0x7fca48c30ab9]
                  10: /usr/lib64/xorg/modules/glesx.so (0x7fca48b5a000+0xd82ed) [0x7fca48c322ed]
                  11: /usr/lib64/xorg/modules/glesx.so (0x7fca48b5a000+0x3f8fd) [0x7fca48b998fd]
                  12: /usr/lib64/xorg/modules/glesx.so (0x7fca48b5a000+0x36c12) [0x7fca48b90c12]
                  13: /usr/lib64/xorg/modules/glesx.so (0x7fca48b5a000+0x36d99) [0x7fca48b90d99]
                  14: /usr/lib64/xorg/modules/glesx.so (esutInit+0x8b) [0x7fca48b8f71b]
                  15: /usr/lib64/xorg/modules/glesx.so (0x7fca48b5a000+0x2749c) [0x7fca48b8149c]
                  16: /usr/lib64/xorg/modules/glesx.so (GlesxExtensionInit+0x75) [0x7fca48b81805]
                  17: /usr/bin/(InitExtensions+0x89) [0x482b29]
                  18: /usr/bin/(0x400000+0x22587) [0x422587]
                  19: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7fca4d211b6d]
                  20: /usr/bin/(0x400000+0x222c9) [0x4222c9]
                  Segmentation fault at address (nil)

                  Fatal server error:
                  Caught signal 11 (Segmentation fault). 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.

                  (
                  IIAIGLXSuspending AIGLX clients for VT switch
                  (
                  IIfglrx(0): Backup framebuffer data.
                  (
                  IIfglrx(0): Backup complete
                  Look like there are some regressions in 10.5 with 2.6.33 and no luck for dual or triple monitor users

                  Comment


                  • #10
                    all I can tell you is that the "Virtual" line works for me (HD 5770, fglrx 10.5, gentoo). The only real difference I see between our xorg.conf's is that you don't specify the Monitor in your Screen section.

                    My xorg.0.log doesn't mention the "Virtual" line, either.


                    In any case, try to get the 1-card-2-monitor-setup working before trying Xinerama.

                    Comment


                    • #11
                      I think that in Adamīs case Xinerama is disabled already.

                      Comment


                      • #12
                        oh sorry, I completely missed that pflynn wasn't the OP.

                        in that case, the first two paragraphs of my last post go to adam while the third goes to pflynn.

                        Comment


                        • #13
                          Well, Iīm not sure, but maybe Adam could try to explicitly disable the XRandr extension in xorg.conf. Sometimes this extension conflicts with some resources in the Catalyst driver. But it is just a possibility...
                          And in my case, I canīt disable de Xinerama extension, unfortunatelly, since It is needed in cases when one have a multi-card setup and one large desktop (ATIīs Big Desktop does not work in multi-card setup).

                          Comment


                          • #14
                            Originally posted by pflynn View Post
                            And in my case, I canīt disable de Xinerama extension, unfortunatelly, since It is needed in cases when one have a multi-card setup and one large desktop (ATIīs Big Desktop does not work in multi-card setup).
                            I'm aware of that. Just saying that you should try to get working xorg.conf's for each of the cards, make sure each card is working fine on it's own. Once that's done, you can try joining them and add Xinerama. That'll help you narrow down the problems.

                            No matter what, Xinerama is a pile of bugs. Prepare for pain and don't expect compositing to work.

                            Btw, that segfault you posted seems to come from within X, not from fglrx.

                            Comment


                            • #15
                              Originally posted by rohcQaH View Post
                              I'm aware of that. Just saying that you should try to get working xorg.conf's for each of the cards, make sure each card is working fine on it's own. Once that's done, you can try joining them and add Xinerama. That'll help you narrow down the problems.
                              Yes. Both cards work individually. If I configure my setup as

                              Code:
                              aticonfig --initial
                              everything runs fine (but as a single, one monitor desktop). Also, the three monitor setup was working fine too, until the upgrade to 13.1 (using the same Catalyst 10.5).

                              Originally posted by rohcQaH View Post
                              No matter what, Xinerama is a pile of bugs. Prepare for pain and don't expect compositing to work.
                              Yep. You are right. This is why I always disable compositing in my setup. By the way, compositing is not that important to me.

                              Originally posted by rohcQaH View Post
                              Btw, that segfault you posted seems to come from within X, not from fglrx.
                              Agreed. This segfault seens to be related to X itself. And probably it has to do with, guess what? Composite Iīm not sure, but I think composite is now enabled by default in the newer versions of Xorg. Iīm trying to disable it in xorg.conf file, but Iīm not sure if Xorg cares about it, since it look like itīs just ignoring my configuration.

                              Comment

                              Working...
                              X