Announcement

Collapse
No announcement yet.

9600(xt) + xorg-server 1.4 + fglrx 8.42

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

  • 9600(xt) + xorg-server 1.4 + fglrx 8.42

    my question is: has anyone compiz (aiglx) running with an ati radeon 9600xt , xorgserver 1.4 and fglrx 8.42 ? (i use 32bit gentoo)
    i've installed the fglrx driver using the ati-installer. worked fine so far! glxgears is running fine, i have dri and all that stuff running. Xv is also running fine.
    My only problem is aiglx and compiz! i use the xeffects overlay.
    installed programs:
    kde 3.5.8
    x11-wm/compiz-0.6.2 USE="dbus kde svg -fuse -gnome -gtk"
    x11-wm/compiz-fusion-0.6.0 USE="kde -gnome -unsupported"

    when i try to start compiz it says that direct rendering isn't possible, and then it tries to switch to indirect rendering, but that isn't possible as well.

    Xorg.0.log has always these strange messages (don't know what they mean):

    (WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
    (WW) fglrx(0): board is an unknown third party board, chipset is supported
    (WW) fglrx(0): Only one display is connnected,so single mode is enabled
    (WW) fglrx(0): could not detect X server version (query_status=-3)
    (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
    (WW) AIGLX: 3D driver claims to not support visual 0x59
    (WW) AIGLX: 3D driver claims to not support visual 0x5a
    (WW) AIGLX: 3D driver claims to not support visual 0x5b
    (WW) AIGLX: 3D driver claims to not support visual 0x5c
    (WW) AIGLX: 3D driver claims to not support visual 0x5d
    (WW) AIGLX: 3D driver claims to not support visual 0x5e
    (WW) AIGLX: 3D driver claims to not support visual 0x5f
    (WW) AIGLX: 3D driver claims to not support visual 0x60
    (WW) AIGLX: 3D driver claims to not support visual 0x61
    (WW) AIGLX: 3D driver claims to not support visual 0x62
    (WW) AIGLX: 3D driver claims to not support visual 0x63
    (WW) AIGLX: 3D driver claims to not support visual 0x64
    (WW) AIGLX: 3D driver claims to not support visual 0x65
    (WW) AIGLX: 3D driver claims to not support visual 0x66
    (WW) AIGLX: 3D driver claims to not support visual 0x67
    (WW) AIGLX: 3D driver claims to not support visual 0x68
    (WW) AIGLX: 3D driver claims to not support visual 0x69
    (WW) AIGLX: 3D driver claims to not support visual 0x6a
    (WW) AIGLX: 3D driver claims to not support visual 0x6b
    (WW) AIGLX: 3D driver claims to not support visual 0x6c
    (WW) AIGLX: 3D driver claims to not support visual 0x6d
    (WW) AIGLX: 3D driver claims to not support visual 0x6e
    (WW) AIGLX: 3D driver claims to not support visual 0x6f
    (WW) AIGLX: 3D driver claims to not support visual 0x70
    (WW) AIGLX: 3D driver claims to not support visual 0x71
    (WW) AIGLX: 3D driver claims to not support visual 0x72


    this is the rest of the more or less important messages:

    (==) fglrx(0): Backing store disabled
    (II) Loading extension FGLRXEXTENSION
    (**) fglrx(0): Option "XaaNoOffscreenPixmaps" "true"
    (II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
    (II) fglrx(0): Acceleration enabled
    (II) fglrx(0): [DRI] installation complete
    (II) fglrx(0): Direct rendering enabled
    (II) AIGLX: Loaded and initialized /usr/lib/dri/fglrx_dri.so


    i hope someone can solve my problems ... i also tried a lot of different options in the xorg.conf... but there are always these "AIGLX: 3D driver claims to not support visual" messages..


    thank you!

  • #2
    downgrade to xorg-server 1.3
    add to /etc/portage/package.use:
    x11-libs/libX11 xcb
    x11-libs/cairo glitz svg png

    LIBGL_ALWAYS_INDIRECT=true fusion-icon

    Comment


    • #3
      what's the easiest way to downgrade xorg ?
      when i put xorg-server 1.4 into package.mask and xorg-7.3 there are some errors because of dependencies...

      Comment


      • #4
        It's some problems in portage, but try:

        emerge =libXrender-0.9.4
        emerge libX11
        emerge =xorg-server-1.3

        emerge xf86-input-keyboard
        emerge xf86-input-mouse
        emerge xf86-input-evdev

        Comment


        • #5
          thanks.. i'll give it a try

          Comment


          • #6
            that thing is present also on xorg-server 1.3 which i'm using.
            so there's no need to downgrade xorg for some warnings.
            compiz tend to not work well (very slow and some apps bugs).
            if it fails are you sure that you've enabled everything that need to be enabled?! can you post your device, modules, serverlayout, dri and extensions section from xorg.conf?! maybe you've forgotten to enable something.

            Comment


            • #7
              Originally posted by givemesugarr View Post
              that thing is present also on xorg-server 1.3 which i'm using.
              so there's no need to downgrade xorg for some warnings.
              compiz tend to not work well (very slow and some apps bugs).
              if it fails are you sure that you've enabled everything that need to be enabled?! can you post your device, modules, serverlayout, dri and extensions section from xorg.conf?! maybe you've forgotten to enable something.
              yes, but i think compiz doesn't work on xorg-server-1.4 at all.

              Comment


              • #8
                what compiz version are you using?! you should use the xeffects version 0.6.2. that's the only one that works on my board, but is damn slow...
                beryl, instead prett fast...
                and these were my flags:
                dbus -fuse -gnome -gtk kde svg -xcb. remember the svg flag which is fundamental for compiz to work. as well put it on cairo. i've put it ad world flag since is useful to have the packages compiled with it.
                and since you use kde, try beryl, which is faster and doesn't needs some gnome bindings that compiz-fusion needs.
                Last edited by givemesugarr; 11-05-2007, 04:45 PM.

                Comment


                • #9
                  for me AIGLX + xorg-server-1.4 = no chance

                  Comment


                  • #10
                    do you have this in your xorg.conf?

                    Section "ServerFlags"
                    Option "AllowMouseOpenFail" "on"
                    Option "IgnoreABI" "on"
                    Option "AIGLX" "on"
                    EndSection
                    ignoreabi and aiglx are needed to run fglrx and 3d desktop on 1.3 and later.

                    Comment


                    • #11
                      IgnoreABI is no option for xorg.conf. The option is "-ignoreABI". It is for startx, in kdmrc ,gdmrc or xdm/servers and needed for OLDER fglrx drivers and Xserver 1.4 (Xorg 7.3). Also AIGLX "on" is not a requirement for the new fglrx driver as usually every X server is set to AIGLX on by default.

                      Comment


                      • #12
                        The option is "-ignoreABI". It is for startx, in kdmrc ,gdmrc or xdm/servers and needed for OLDER fglrx drivers and Xserver 1.4 (Xorg 7.3).
                        my server doesn't start without it...

                        as for the aiglx, on gentoo you can enable or disable as flag. this option sets it to on for sure.

                        Comment


                        • #13
                          Originally posted by Kano View Post
                          Also AIGLX "on" is not a requirement for the new fglrx driver as usually every X server is set to AIGLX on by default.
                          It's the opposite on OpenSUSE. AIGLX is set to off by default.

                          I'm having the same messages on my xpress 1100/200M. AIGLX is reported as working, however compiz segfaults.

                          Comment


                          • #14
                            It's the opposite on OpenSUSE. AIGLX is set to off by default.
                            because opensuse by default gets with the xf-86-ati-drivers and not with the fgrlx and the default driver doesn't support aiglx for all ati boards and also they don't really support all the drivers. for that reason sax2 turns off aiglx and 3d acceleration setting the default to vesa with only 2d.
                            but if it recognizes the board and the driver supports the various features, 3d and aiglx it enables it by default.

                            Comment


                            • #15
                              why do you need fglrx for aiglx on your old hardware? thats not needed at all to have aiglx.

                              Comment

                              Working...
                              X