Announcement

Collapse
No announcement yet.

AMD 8.42.3 Driver Released -- The Baby Is Born!

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • looking through the thread so far - good thing i didn't put my r500 card back in.

    looks like r300 with opensource driver is still a better solution for me.

    Comment


    • Ok guys, I'm still having problems running compiz, even after trying all the solutions provided here.

      I'm running Debian sid with Xpress 200M, xorg 7.3, compiz 0.5.2. I'm getting the same GLX_EXT_texture_from_pixmap problem many people here seem to have:

      Code:
      compiz --replace
      GLX_EXT_texture_from_pixmap is not available with direct rendering.
      GLX_EXT_texture_from_pixmap is not available with indirect rendering. Aborting!
      The proposed solutions using LD_PRELOAD and LIBGL_ALWAYS_INDIRECT don't do a thing. Looking at /usr/bin/compiz, I see that it's a wrapper script for compiz.real. It first greps glxinfo for GLX_EXT_texture_from_bitmap and checks if it return at least three lines - no idea why! Checking glxinfo manually shows me that GLX_EXT_texture_from_pixmap occurs only twice. Anyway, if the above fails, the script exports LIBGL_ALWAYS_INDIRECT=true and tries again. If neither check succeeds, it exits with the above errors.

      Now the fun part. I tried manually exporting LIBGL_ALWAYS_INDIRECT=true and running compiz.real directly. This gives me a seg fault. Moreover, after LIBGL_ALWAYS_INDIRECT=true glxinfo produces the following instead of the expect result:

      Code:
      export LIBGL_ALWAYS_INDIRECT=true
      glxinfo
      name of display: :0.0
      X Error of failed request:  GLXBadContext
        Major opcode of failed request:  162 (GLX)
        Minor opcode of failed request:  5 (X_GLXMakeCurrent)
        Serial number of failed request:  16
        Current serial number in output stream:  16
      Any ideas?

      Comment


      • Problems with Indirect rendering

        I have ATI Mobility Radeon X1300. I am using Debian sid. I have installed fglrx driver 8.42.3. Compiz version is 0.5.2 and Xorg is 7.3.

        I am able to find AIGLX and Composite enabled in Xorg.0.log.

        Code:
        ...
        (**) Extension "Composite" is enabled
        ...
        (==) AIGLX enabled
        ...
        The output of fglrxinfo reports the following.

        Code:
        display: :0.0  screen: 0
        OpenGL vendor string: ATI Technologies Inc.
        OpenGL renderer string: ATI Mobility Radeon X1300
        OpenGL version string: 2.0.6958 Release
        The output of glxinfo confirms direct rendering.

        Code:
        name of display: :0.0
        display: :0  screen: 0
        direct rendering: Yes
        server glx vendor string: SGI
        server glx version string: 1.2
        server glx extensions:
        ...
        I am able to run fgl_glxgears and amdcccle reports right driver version.

        However there is problem starting compiz. I figured out that the root cause being not able to support Indirect rendering.

        Code:
        $ export LIBGL_ALWAYS_INDIRECT=1
        
        $ glxinfo 
        name of display: :0.0
        X Error of failed request:  GLXBadContext
          Major opcode of failed request:  144 (GLX)
          Minor opcode of failed request:  5 (X_GLXMakeCurrent)
          Serial number of failed request:  16
          Current serial number in output stream:  16
        
        $ unset LIBGL_ALWAYS_INDIRECT
        
        $ glxinfo
        name of display: :0.0
        display: :0  screen: 0
        direct rendering: Yes
        server glx vendor string: SGI
        server glx version string: 1.2
        ...
        Looking at the behavior above, I am seeing that forcing Indirect rendering doesn't work with fglrx 8.42.3. Is this an expected behavior? I supposed that AIGLX support would facilitate Indirect rendering.

        Compiz fails to start as the wrapper script searches for three occurrences of GLX_EXT_texture_from_pixmap in the glxinfo output. However we get only two occurrences when we use fglrx driver.

        Code:
        $ glxinfo | grep -c GLX_EXT_texture_from_pixmap
        2
        Because of this, the wrapper script tries to use Indirect rendering and eventually it fails. I have clearly ensured that I am not mixing old versions of the driver. All log files seem to be perfect.

        I see a bunch of warnings in Xorg.0.log. Does it bother someone?

        Code:
        (WW) AIGLX: 3D driver claims to not support visual 0x23
        (WW) AIGLX: 3D driver claims to not support visual 0x24
        (WW) AIGLX: 3D driver claims to not support visual 0x25
        (WW) AIGLX: 3D driver claims to not support visual 0x26
        (WW) AIGLX: 3D driver claims to not support visual 0x27
        (WW) AIGLX: 3D driver claims to not support visual 0x28
        (WW) AIGLX: 3D driver claims to not support visual 0x29
        (WW) AIGLX: 3D driver claims to not support visual 0x2a
        (WW) AIGLX: 3D driver claims to not support visual 0x2b
        (WW) AIGLX: 3D driver claims to not support visual 0x2c
        (WW) AIGLX: 3D driver claims to not support visual 0x2d
        (WW) AIGLX: 3D driver claims to not support visual 0x2e
        (WW) AIGLX: 3D driver claims to not support visual 0x2f
        (WW) AIGLX: 3D driver claims to not support visual 0x30
        (WW) AIGLX: 3D driver claims to not support visual 0x31
        (WW) AIGLX: 3D driver claims to not support visual 0x32
        (WW) AIGLX: 3D driver claims to not support visual 0x33
        (WW) AIGLX: 3D driver claims to not support visual 0x34
        (WW) AIGLX: 3D driver claims to not support visual 0x35
        (WW) AIGLX: 3D driver claims to not support visual 0x36
        (WW) AIGLX: 3D driver claims to not support visual 0x37
        (WW) AIGLX: 3D driver claims to not support visual 0x38
        (WW) AIGLX: 3D driver claims to not support visual 0x39
        (WW) AIGLX: 3D driver claims to not support visual 0x3a
        (WW) AIGLX: 3D driver claims to not support visual 0x3b
        (WW) AIGLX: 3D driver claims to not support visual 0x3c
        (WW) AIGLX: 3D driver claims to not support visual 0x3d
        (WW) AIGLX: 3D driver claims to not support visual 0x3e
        (WW) AIGLX: 3D driver claims to not support visual 0x3f
        (WW) AIGLX: 3D driver claims to not support visual 0x40
        (WW) AIGLX: 3D driver claims to not support visual 0x41
        (WW) AIGLX: 3D driver claims to not support visual 0x42
        (WW) AIGLX: 3D driver claims to not support visual 0x43
        (WW) AIGLX: 3D driver claims to not support visual 0x44
        (WW) AIGLX: 3D driver claims to not support visual 0x45
        (WW) AIGLX: 3D driver claims to not support visual 0x46
        (WW) AIGLX: 3D driver claims to not support visual 0x47
        (WW) AIGLX: 3D driver claims to not support visual 0x48
        (WW) AIGLX: 3D driver claims to not support visual 0x49
        (WW) AIGLX: 3D driver claims to not support visual 0x4a
        (WW) AIGLX: 3D driver claims to not support visual 0x4b
        (WW) AIGLX: 3D driver claims to not support visual 0x4c
        (WW) AIGLX: 3D driver claims to not support visual 0x4d
        (WW) AIGLX: 3D driver claims to not support visual 0x4e
        (WW) AIGLX: 3D driver claims to not support visual 0x4f
        (WW) AIGLX: 3D driver claims to not support visual 0x50
        (WW) AIGLX: 3D driver claims to not support visual 0x51
        (WW) AIGLX: 3D driver claims to not support visual 0x52
        (WW) AIGLX: 3D driver claims to not support visual 0x53
        (WW) AIGLX: 3D driver claims to not support visual 0x54
        (WW) AIGLX: 3D driver claims to not support visual 0x55
        (WW) AIGLX: 3D driver claims to not support visual 0x56
        (WW) AIGLX: 3D driver claims to not support visual 0x57
        (WW) AIGLX: 3D driver claims to not support visual 0x58
        Looks like a lot of people are stuck on the same issue. Can someone throw light on what is happening? Any help is appreciated. Thank you.
        Last edited by InfiniteZero; 24 October 2007, 03:03 AM. Reason: Added more information from Xorg.0.log

        Comment


        • I got this installed on my X1950 Pro AGP with a few problems:

          Error in Xorg.0.log:
          Code:
          (II) fglrx(0): [drm] register handle = 0x00004000
          (EE) fglrx(0): Failed to enable interrupts.
          (II) fglrx(0): [pci] find AGP GART
          (II) fglrx(0): [agp] Mode=0x1f00421b bridge: 0x10de/0x00e1
          (II) fglrx(0): [agp] AGP v1/2 disable mask 0x00000000
          (II) fglrx(0): [agp] AGP v3 disable mask   0x00000000
          (II) fglrx(0): [agp] enabling AGP with mode=0x1f00431a
          (II) fglrx(0): [agp] Remapping MC AGP space (new MCAGPBase = 0xdc000000)
          (II) fglrx(0): [agp] AGP protocol is enabled for graphics board. (cmd=0x1f004312)
          (II) fglrx(0): [agp] graphics chipset has AGP v3.0 (native mode)
          (II) fglrx(0): DRI initialization successfull!
          I also got the warnings from AIGLX about 3D driver not supporting lots of visuals.

          I noticed this message in dmesg:
          Code:
          ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
          ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 21
          [fglrx] IRQ_MGR is disabled untill GART_CACHABLE memory will be implemented<6>[fglrx] AGP detected, AgpState   = 0x1f00421b (hardware caps of chipset)
          agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
          agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
          agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
          [fglrx] AGP enabled,  AgpCommand = 0x1f004312 (selected caps)
          It looks to me as the driver is saying it doesn't (yet) support something that is required for IRQ interrupts. I might try and disable ACPI tomorrow and see if that helps.

          On the positive glxinfo, fglrxinfo are telling me acceleration is on. ATI CCC is working nicely and tells me AGP is on at 8x (before it was 0x as the driver thought it was a PCIE card).

          Video is slooow, 3D is slower than with 8.40.x too . Glxgears gives 600 odd fps instead of 1210.

          Anyone have any suggestions on getting interrupts to work?

          Comment


          • I'm certainly looking forward to testing this driver, but judging by previous ATi/AMD-driver releases, I'm not expecting too much of an improvement.

            Comment


            • @Crunchy

              Seems to be Xserver 1.4 related, right?

              Comment


              • Originally posted by lgoral View Post
                Ok guys, I'm still having problems running compiz, even after trying all the solutions provided here.

                I'm running Debian sid with Xpress 200M, xorg 7.3, compiz 0.5.2. I'm getting the same GLX_EXT_texture_from_pixmap problem many people here seem to have:

                Code:
                compiz --replace
                GLX_EXT_texture_from_pixmap is not available with direct rendering.
                GLX_EXT_texture_from_pixmap is not available with indirect rendering. Aborting!
                The proposed solutions using LD_PRELOAD and LIBGL_ALWAYS_INDIRECT don't do a thing. Looking at /usr/bin/compiz, I see that it's a wrapper script for compiz.real. It first greps glxinfo for GLX_EXT_texture_from_bitmap and checks if it return at least three lines - no idea why! Checking glxinfo manually shows me that GLX_EXT_texture_from_pixmap occurs only twice. Anyway, if the above fails, the script exports LIBGL_ALWAYS_INDIRECT=true and tries again. If neither check succeeds, it exits with the above errors.

                Now the fun part. I tried manually exporting LIBGL_ALWAYS_INDIRECT=true and running compiz.real directly. This gives me a seg fault. Moreover, after LIBGL_ALWAYS_INDIRECT=true glxinfo produces the following instead of the expect result:

                Code:
                export LIBGL_ALWAYS_INDIRECT=true
                glxinfo
                name of display: :0.0
                X Error of failed request:  GLXBadContext
                  Major opcode of failed request:  162 (GLX)
                  Minor opcode of failed request:  5 (X_GLXMakeCurrent)
                  Serial number of failed request:  16
                  Current serial number in output stream:  16
                Any ideas?
                mine was working fine until i upgraded to xserver 1.4, since then my results are like yours.

                i will downgrade to xserver 1.3 and see what happen.

                by the way i'm usin gentoo.

                Comment


                • Finally

                  Light at the end of the tunnel!

                  Comment


                  • Originally posted by InfiniteZero View Post
                    I have ATI Mobility Radeon X1300. I am using Debian sid. I have installed fglrx driver 8.42.3. Compiz version is 0.5.2 and Xorg is 7.3....
                    Do you have 64bit kernel? Cause it seems that it's only problem x86_64 fglrx

                    Comment


                    • Well, I loaded up 8.42 on my 9700 Pro and while the performance was greatly improved my long-term complaint is still not addressed. There are artifacts when FSAA is enabled in OpenGL applications. 8.42 has different patterns, the artifact blocks are much bigger (hinting to why the performance is increased, internally the driver uses larger tile slices) and they are in different places. However, they are still there. I now also get watermark in the corner. (though it doesn't show up with Ksnapshot). If this is possibly some kind of settings issue, I'd like to know what might cause it (or how to clear out all settings from previous drivers, as the driver no longer uses the options in /etc/X11/xorg.conf exclusively). Anyway... this is a picture of my issue: http://img136.imageshack.us/my.php?i...apshot2kt5.png

                      It is an OpenInventor file being viewed in ivview. I can provide the .iv for testing, OpenInventor is an open source scientific visualization tool and part of nearly every major distribution. Source is here: ftp://oss.sgi.com/projects/inventor/download

                      On Debian or Ubuntu:
                      apt-get install inventor-clients

                      Michael, if you could mention this to your ATI developer friends I'd love to get to the bottom of why the ATI driver has always had artifacts with this program. Possibly this would also point to much more minor artifacting when FSAA is enabled in many games. I'm using Debian Etch (stock except for fglrx, so 2.6.18-5-686, X.org 7.1.0-19)

                      Comment

                      Working...
                      X