Announcement

Collapse
No announcement yet.

[8.42.3] X1950Pro AGP vs 9500Pro AGP the winner? Clearly the 9500Pro! ... what?!

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

  • [8.42.3] X1950Pro AGP vs 9500Pro AGP the winner? Clearly the 9500Pro! ... what?!

    Hi all,

    some might remember me complaining about the lack of X1950Pro AGP (realto) support on the 8.41 driver series, making it segfault etc, which was ok, it wasn't a supported card. The 'crappy' thing was that the only driver that DID work was the 8.34.4 one, and only with a secret special trick at that.

    I was getting corruptions on 2d surfaces (ff etc) and 3d didn't work or work highly corrupted (this actually even on 8.42 in ut2004). Setting my AGP-Gart from 128mb to 256 fixed that for the 8.34, and changing it to 512mb fixed it on the 8.42 driver. (the card is a 512mb model, i temp had a 256 model where coincidently i could go to/from 64mb -> 128 -> 256)

    Back to now, I tried using the 8.42.3 driver and got horrible performance, I mentioned it in the big 'the baby is born' thread but that got quickly lost, with 1 comment wether I was having AIGLX/composite issues (i have both disabled). I can play et (not qw) at 20 - 90FPS but it's never smooth. It feels choppy, looks choppy and i got some minor texture corruption on the minimap and map.

    So instead of mindlessly complaining, I put back my old old 9500Pro AGP thatI borrowed my brother (his own was being RMAed) and I tried that one out with 8.42.3

    I now get what all the fuss is about. I get smooth 90FPS without a hiss in ET, it looks smooth, it feels smooth.

    In WoW (wine -opengl) i got marginal performance on the X1950Pro, 5 - 10FPS where 'normal' for busy areas and i've seen anything from 3 fps to 60fps depending on the area. (small narrow buildings/hallways got me up, busy large area's where .. grinding to halt almost) but avg. would be i say anything between 10 - 25fps.

    With the 9500 i'm gettin 25 - 100fps, with 100 more then the 25. Yeah, weird huh

    I'll attach 3 xorg logs, 8.34 and 8.42 - 1950 and the 8.42 for the 9500 Pro

    It seems to me, there's an issue somewhere with the AGP thing still. Since it's the same system/settings, and only video card swapped, I can either be hardware, or driver related, not kernel etc, and the hardware works. (the card is fine in, *sigh* windos)

    Thanks for your reads

    Since phoronix won't let me post my 3 uber big logs, i hosted them myself:
    http://oliver.schinagl.nl/~oliver/xorg.logs

    I 'snipped' the important part from the X1950Pro on the 8.42.3 for those who don't like to read big logs

    Code:
    (II) fglrx(0): [drm] DRM interface version 1.0
    (II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
    (II) fglrx(0): [drm] added 8192 byte SAREA at 0x2000
    (II) fglrx(0): [drm] mapped SAREA 0x2000 to 0xb7edf000
    (II) fglrx(0): [drm] framebuffer handle = 0x3000
    (II) fglrx(0): [drm] added 1 reserved context for kernel
    (II) fglrx(0): DRIScreenInit done
    (II) fglrx(0): Kernel Module Version Information:
    (II) fglrx(0):     Name: fglrx
    (II) fglrx(0):     Version: 8.42.3
    (II) fglrx(0):     Date: Oct 19 2007
    (II) fglrx(0):     Desc: ATI FireGL DRM kernel module
    (II) fglrx(0): Kernel Module version matches driver.
    (II) fglrx(0): Kernel Module Build Time Information:
    (II) fglrx(0):     Build-Kernel UTS_RELEASE:        2.6.22-gentoo-r8
    (II) fglrx(0):     Build-Kernel MODVERSIONS:        no
    (II) fglrx(0):     Build-Kernel __SMP__:            yes
    (II) fglrx(0):     Build-Kernel PAGE_SIZE:          0x1000
    (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=0x1f000a1b bridge: 0x1106/0x0282
    (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=0x1f000b1a
    (II) fglrx(0): [agp] Remapping MC AGP space (new MCAGPBase = 0xc0000000)
    (II) fglrx(0): [agp] AGP protocol is enabled for graphics board. (cmd=0x1f000312)
    (II) fglrx(0): [agp] graphics chipset has AGP v3.0 (native mode)
    (II) fglrx(0): DRI initialization successfull!
    (II) fglrx(0): FBADPhys: 0xe0100000 FBMappedSize: 0x01000400
    (II) fglrx(0): FBMM initialized for area (0,0)-(1280,3277)
    (II) fglrx(0): FBMM auto alloc for area (0,0)-(1280,1024) (front color buffer - assumption)
    (II) fglrx(0): Largest offscreen area available: 1280 x 2253
    Last edited by oliver; 10-28-2007, 11:02 AM. Reason: It i the fault of (EE) fglrx(0): Failed to enable interrupts. !!

  • #2
    I'm still getting the same error. I've tried:

    Kernel option: pci=routeirq
    Turned off vesafb in kernel
    Turned on MSI in kernel
    Turned on i2c module in xorg.conf (said it was built in)

    I might try turning on PCIE support in the kernel and disabling i2c in the kernel.

    I still think this message in /var/log/messages might be the root of the problem:

    Code:
    Oct 28 13:47:43 merry acpid: client connected from 3960[0:1000]
    Oct 28 13:47:43 merry acpid: 1 client rule loaded
    Oct 28 13:47:43 merry ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
    Oct 28 13:47:43 merry ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 21
    Oct 28 13:47:44 merry [fglrx] IRQ_MGR is disabled untill GART_CACHABLE memory will be implemented<6>[fglrx] AGP detected, AgpState   = 0x1f00421b (hardware caps of chipset)
    Oct 28 13:47:44 merry agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
    Oct 28 13:47:44 merry agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
    Oct 28 13:47:44 merry agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
    Oct 28 13:47:44 merry [fglrx] AGP enabled,  AgpCommand = 0x1f004312 (selected caps)

    Comment


    • #3
      My 9500Pro gives me this (and works beautifully)

      Code:
      fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
      [fglrx] Maximum main memory to use for locked dma buffers: 1898 MBytes.
      [fglrx] ASYNCIO init succeed!
      [fglrx] PAT is enabled successfully!
      [fglrx] module loaded - fglrx 8.42.3 [Oct 19 2007] on minor 0
      ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 19
      [fglrx] Internal AGP support requested, but kernel AGP support active.
      [fglrx] Have to use kernel AGP support to avoid conflicts.
      [fglrx] AGP detected, AgpState   = 0x1f000a1b (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 = 0x1f000312 (selected caps)
      I'll pop in my X1950 To see my dmesg there, didn't pay attention to that tbh

      Code:
      fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
      [fglrx] Maximum main memory to use for locked dma buffers: 1898 MBytes.
      [fglrx] ASYNCIO init succeed!
      [fglrx] PAT is enabled successfully!
      [fglrx] module loaded - fglrx 8.42.3 [Oct 19 2007] on minor 0
      ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 19
      eth0: no IPv6 routers present
      [fglrx] IRQ_MGR is disabled untill GART_CACHABLE memory will be implemented
      [fglrx] Internal AGP support requested, but kernel AGP support active.
      [fglrx] Have to use kernel AGP support to avoid conflicts.
      [fglrx] AGP detected, AgpState   = 0x1f000a1b (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 = 0x1f000312 (selected caps)
      Last edited by oliver; 10-28-2007, 02:25 PM.

      Comment


      • #4
        X1950 PRO AGP 512 Same thing here

        I got the same error, and not-so-satisfying performance (a little better than 8.40.4)
        don't know what's the meaning of that frickin error
        and by the end of the week I can tell:
        on gutsy 7.10 I couldn't get 3d acceleration (famous MESA crap)
        and on PCLinuxOS 2007 8.42.3 is some kind of working; 3d acceleration, performance didn't leaped from 8.40.4 as they promised, when I log out PC hangs (reset baby!) and when I try to pick the screensaver tab on KDE (right click on desktop), the window closes itself.

        there are slight speed improvements on X-Moto (now playable), Nexuiz, and in some games. on OpenArena I had to migrate to Gnome because when I try to change system settings in OpenArena on KDE, the thing crashes.
        GL-117 has better performance(no more low-fps warnings!), but when I move the target with the mouse, the whole thing freezes for a second or more so It takes me a minutes just to start a game.
        Miss my 9800 PRO

        conclusion: as I said before ATI made their great products useless. go green!!
        Last edited by tsarig; 10-28-2007, 12:58 PM.

        Comment


        • #5
          Originally posted by tsarig View Post
          I got the same error, and not-so-satisfying performance (a little better than 8.40.4)
          don't know what's the meaning of that frickin error
          and by the end of the week I can tell:
          on gutsy 7.10 I couldn't get 3d acceleration (famous MESA crap)
          and on PCLinuxOS 2007 8.42.3 is some kind of working; 3d acceleration, performance didn't leaped from 8.40.4 as they promised, when I log out PC hangs (reset baby!) and when I try to pick the screensaver tab on KDE (right click on desktop), the window closes itself.

          there are slight speed improvements on X-Moto (now playable), Nexuiz, and in some games. on OpenArena I had to migrate to Gnome because when I try to change system settings in OpenArena on KDE, the thing crashes.
          GL-117 has better performance(no more low-fps warnings!), but when I move the target with the mouse, the whole thing freezes for a second or more so It takes me a minutes just to start a game.
          Miss my 9800 PRO

          conclusion: as I said before ATI made their great products useless. go green!!
          Don't be so harsh. My 9500Pro works like a charm now

          It looks like an AGP interrupt problem or the like.

          Let's jsut hope someone of some importance noticeses.

          Comment


          • #6
            Here is my xorg.conf which works great for me on Fedora Core 7 with ATI X1950 Pro AGP and 8.42.3.

            I had pretty much the same symptoms.

            XGL has still problem :

            Code:
            fgl_glxgears 
            Using GLX_SGIX_pbuffer
            X Error of failed request:  GLXUnsupportedPrivateRequest
              Major opcode of failed request:  144 (GLX)
              Minor opcode of failed request:  16 (X_GLXVendorPrivate)
              Serial number of failed request:  42
              Current serial number in output stream:  43
            Bu AIGLX is very fast!

            I had also corruption on screen, which are fixed now.
            compiz has a problem with windows manager. If I use instead beryl, all is fine. I tested OpenGL Performance with Quake4... compare to 8.40.4 it's turbo bust!

            here my xorg.conf

            Code:
            # Xorg configuration created by system-config-display
            
            Section "ServerLayout"
                    Identifier     "aticonfig-Layout[all]"
                    Screen      0  "aticonfig-Screen[0]" 0 0
                    InputDevice    "Keyboard[0]" "CoreKeyboard"
                    InputDevice    "Mouse[1]" "CorePointer"
            EndSection
            
            Section "Files"
                    FontPath     "unix/:7100"
            EndSection
            
            Section "Module"
                    Load  "dbe"
                    Load  "i2c"
                    Load  "bitmap"
                    Load  "ddc"
                    Load  "dri"
                    Load  "extmod"
                    Load  "freetype"
                    Load  "glx"
                    Load  "vbe"
            EndSection
            
            Section "ServerFlags"
                    Option      "AIGLX" "on"
            EndSection
            
            
            Section "InputDevice"
                    Identifier  "Keyboard[0]"
                    Driver      "kbd"
                    Option      "XkbModel" "pc105"
                    Option      "XkbLayout" "ch"
                    Option      "XkbVariant" "de_nodeadkeys"
            EndSection
            
            Section "InputDevice"
                    Identifier  "Mouse[1]"
                    Driver      "mouse"
                    Option      "Buttons" "10"
                    Option      "Device" "/dev/input/mice"
                    Option      "Name" "A4Tech USB-PS/2 Optical Mouse"
            EndSection
            
            Section "Monitor"
                    Identifier   "aticonfig-Monitor[0]"
                    Option      "VendorName" "ATI Proprietary Driver"
                    Option      "ModelName" "Generic Autodetecting Monitor"
                    Option      "DPMS" "true"
            EndSection
            
            Section "Device"
                    Identifier  "aticonfig-Device[0]"
                    Driver      "fglrx"
                    Option      "AccelMethod" "xaa"
                    Option      "OpenGLOverlay" "off"
                    Option      "VideoOverlay" "on"
                    Option      "XAANoOffscreenPixmaps" "true"
                    Option      "ForceGenericCPU" "off"
                    Option      "Centermode" "on"
                    Option      "PseudoColorVisuals" "off"
                    Option      "KernelModuleParm" "locked-userpages=0"
                    Option      "no_accel" "no"
                    Option      "no_dri" "no"
                    Option      "ForceMonitors" "notv"
                    Option      "ForceGenericCPU"   "no"
            EndSection
            
            Section "Screen"
                    Identifier "aticonfig-Screen[0]"
                    Device     "aticonfig-Device[0]"
                    Monitor    "aticonfig-Monitor[0]"
                    DefaultDepth     24
                    SubSection "Display"
                            Viewport   0 0
                            Depth     24
                    EndSubSection
            EndSection
            
            Section "DRI"
                    Group        "video"
                    Mode         0666
            EndSection
            
            Section "Extensions"
                    Option      "Composite" "Enabled"
                    Option      "XVideo" "Enable"
            EndSection

            Comment


            • #7
              Ops,
              I forgeted to mension, I downgraded my fedora 7 xorg Server from last update back to xorg-x11-server-Xorg-1.3.0.0-5.fc7

              Comment


              • #8
                Thanks for this soundworks2. I just tried your xorg.conf, I only changed the mouse and keyboard settings and fired up X, still the same error . I presume it's not to do with the mouse/keyboard?!

                I'm using the current stable xorg in Gentoo:
                x11-base/xorg-server-1.3.0.0-r1
                x11-base/xorg-x11-7.2

                I'm using kernel 2.6.22-gentoo-r8, I've also tried 2.6.23-gentoo and had the same problem.

                Incidentally I just reinstalled to re jig my partitions and I get the same error but even worse all 3D results in a black screen .

                I've checked through my dmesg and can't see any errors at all, theres plenty of stuff about interrupts being handled by ACPI.

                soundworks2 do you use ACPI?

                Comment


                • #9
                  I've at least managed to sort the black/blank 3D. Setting AGP Aperture to 256MB or higher sorts it. I see my card gets detected as a 256MB card where its actually 512MB, I wonder if that's the problem?

                  Comment


                  • #10
                    I tried upgrading to:

                    x11-base/xorg-server-1.4-r2
                    x11-base/xorg-x11-7.3

                    Still the same error, bleh.

                    Comment


                    • #11
                      Originally posted by Crunchy View Post
                      I've at least managed to sort the black/blank 3D. Setting AGP Aperture to 256MB or higher sorts it. I see my card gets detected as a 256MB card where its actually 512MB, I wonder if that's the problem?
                      I think i mentioned this here, or in other posts, the driver bugs out with the wrong AGP apperture size. You need to have atleast half your mem. Anything less and you get missing 3d Surfaces, and slow/buggy 2d acceleration.

                      Comment


                      • #12
                        Did you try to set this option in Device section allready?

                        Code:
                        Option      "MaxGARTSize" "512"
                        Check also in Bios if AGP size is set to 512M
                        Last edited by soundworks2; 10-29-2007, 03:40 PM.

                        Comment


                        • #13
                          I just tried that soundworks2 and it didn't help :/

                          Comment


                          • #14
                            I wonder if any of you have VIA based motherboard?

                            I'm currently looking into purchasing X1950Pro AGP, and after much googling, it appears all problematic motherboards are based on NVIDIA or SiS chipsets, while those with VIA chipsets do not have any problems. These ovservations are all from the Windows systems though.

                            Comment


                            • #15
                              In somewhat related news, ATI/AMD has replaced their own AGP driver with the one from the current kernel in the latest driver release:
                              http://kernelslacker.livejournal.com/96680.html

                              Comment

                              Working...
                              X