Page 5 of 7 FirstFirst ... 34567 LastLast
Results 41 to 50 of 64

Thread: AGP PCI-E Issues (Rialto chip) No Interupt (IRQ) assigned, Poor performance.

  1. #41
    Join Date
    Oct 2007
    Posts
    73

    Default

    I've tried these settings before (amongst the hundreds of xorg.conf and linux settings I've tried) but I thought I'd give it a go again. I copied jlambrecht's xorg.conf only changing the fontpath, keyboard and mouse sections. I get the same error .

  2. #42
    Join Date
    Oct 2007
    Posts
    14

    Default

    These options didn't help here too.
    I begin to think that we can't do anything to fix the problem and must wait for the next release

    But i'll try every little thing, to track this down, if it helps.

    I've commented out all modules in the module section, but the xorg.log says that most modules are still being loaded, not only the buildins, so i have no idea to go further on this topic.
    Last edited by uzi-; 12-06-2007 at 12:25 PM.

  3. #43
    Join Date
    Jan 2007
    Posts
    418

    Default

    was affraid of that .. guess we'll be hopin' on 7.12/8.44.*

  4. #44
    Join Date
    Mar 2007
    Location
    MN, United States
    Posts
    285

    Default

    Quote Originally Posted by uzi- View Post
    These options didn't help here too.
    I begin to think that we can't do anything to fix the problem and must wait for the next release
    Even I could had told you that a long time ago hehe. Any issues like this that you come across with fglrx, there is no magical setting that can fix it. At least based off my experience with 99% of the issues I've had, its all about the waiting game unfortunately.

  5. #45
    Join Date
    Dec 2007
    Posts
    1

    Default

    Code:
    Option "TexturedVideo" "ON"
    Option "AGPMask" "0x00000210"
    
    Option "AGPv3Mask" "0x00000002"
    #Option "KernelModuleParm" "agplock=3"
    Option "BusType" "AGP"
    Option "KernelModuleParm" "agpgart=2"
    Option "KernelModuleParm" "agp_try_unsupported=1" 
    Option "KernelModuleParm" "debug=1"
    Option "KernelModuleParm" "maxlockedmem=512"
    Option "Stereo" "off"
    # not used Option "EnableLogo" "true"
    # not used Option "FSAAEnable" "1"
    Option "UseInternalAGPGart" "no"
    Option "MaxGARTSize" "512"
    Option "mtrr" "0"
    # not used Option "PBuffer" "0"
    Option "UseFastTLS" "2"
    it's my option and no error!!
    Code:
    (II) [drm] DRM interface version 1.0
    (II) [drm] DRM open master succeeded.
    (II) fglrx(0): [drm] Using the DRM lock SAREA also for drawables.
    (II) fglrx(0): [drm] framebuffer handle = 0x39d000
    (II) fglrx(0): [drm] added 1 reserved context for kernel
    (II) fglrx(0): X context handle = 0x1
    (II) fglrx(0): [drm] installed DRM signal handler
    (II) fglrx(0): DRIScreenInit done
    (II) fglrx(0): Kernel Module Version Information:
    (II) fglrx(0):     Name: fglrx
    (II) fglrx(0):     Version: 8.43.2
    (II) fglrx(0):     Date: Nov  9 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 = 0x0039f000
    (II) fglrx(0): [pci] find AGP GART
    (II) fglrx(0): [agp] Mode=0x1f004a1b bridge: 0x8086/0x2570
    (II) fglrx(0): [agp] AGP v1/2 disable mask 0x00000210
    (II) fglrx(0): [agp] AGP v3 disable mask   0x00000002
    (II) fglrx(0): [agp] enabling AGP with mode=0x1f004b19
    (II) fglrx(0): [agp] Remapping MC AGP space (new MCAGPBase = 0xe0000000)
    (II) fglrx(0): [agp] AGP protocol is enabled for graphics board. (cmd=0x1f004311)
    (II) fglrx(0): [agp] graphics chipset has AGP v3.0 (native mode)
    (II) fglrx(0): DRI initialization successfull!
    (II) fglrx(0): front overlay:  0xc1001400
    (II) fglrx(0): back overlay:   0xc11b0000
    (II) fglrx(0): video overlay:  0xc135ec00
    (II) fglrx(0): FBADPhys: 0xc0000000 FBMappedSize: 0x01001400
    (II) fglrx(0): FBMM initialized for area (0,0)-(1728,2428)
    (II) fglrx(0): FBMM auto alloc for area (0,0)-(1728,1050) (front color buffer - assumption)
    (II) fglrx(0): Largest offscreen area available: 1728 x 1378
    (==) fglrx(0): Backing store disabled
    old
    Code:
    Nov 30 16:08:35 localhost [fglrx] Maximum main memory to use for locked dma buffers: 1899 MBytes.
    Nov 30 16:08:35 localhost [fglrx] IRQ_MGR is disabled untill GART_CACHABLE memory will be implemented<6>[fglrx] AGP detected, AgpState   = 0x1f004a1b (hardware caps of chipset)
    Nov 30 16:08:35 localhost agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
    Nov 30 16:08:35 localhost agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
    Nov 30 16:08:35 localhost agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
    Nov 30 16:08:35 localhost [fglrx] AGP enabled,  AgpCommand = 0x1f004311 (selected caps)
    new
    Code:
    Nov 30 16:09:50 localhost [fglrx] Maximum main memory to use for locked dma buffers: 1899 MBytes.
    Nov 30 16:09:50 localhost [fglrx] AGP detected, AgpState   = 0x1f004a1b (hardware caps of chipset)
    Nov 30 16:09:50 localhost agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
    Nov 30 16:09:50 localhost agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
    Nov 30 16:09:50 localhost agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
    Nov 30 16:09:50 localhost [fglrx] AGP enabled,  AgpCommand = 0x1f004311 (selected caps)
    but this not fix slow speed and buggy graphics

    ps
    video x1950gt 512mb agp
    Last edited by NIKE; 12-07-2007 at 01:23 PM.

  6. #46
    Join Date
    Jan 2007
    Posts
    418

    Default

    Quote Originally Posted by NIKE View Post
    Code:
    Option "TexturedVideo" "ON"
    Option "AGPMask" "0x00000210"
    
    Option "AGPv3Mask" "0x00000002"
    #Option "KernelModuleParm" "agplock=3"
    Option "BusType" "AGP"
    Option "KernelModuleParm" "agpgart=2"
    Option "KernelModuleParm" "agp_try_unsupported=1" 
    Option "KernelModuleParm" "debug=1"
    Option "KernelModuleParm" "maxlockedmem=512"
    Option "Stereo" "off"
    # not used Option "EnableLogo" "true"
    # not used Option "FSAAEnable" "1"
    Option "UseInternalAGPGart" "no"
    Option "MaxGARTSize" "512"
    Option "mtrr" "0"
    # not used Option "PBuffer" "0"
    Option "UseFastTLS" "2"
    it's my option and no error!!
    Code:
    (II) [drm] DRM interface version 1.0
    (II) [drm] DRM open master succeeded.
    (II) fglrx(0): [drm] Using the DRM lock SAREA also for drawables.
    (II) fglrx(0): [drm] framebuffer handle = 0x39d000
    (II) fglrx(0): [drm] added 1 reserved context for kernel
    (II) fglrx(0): X context handle = 0x1
    (II) fglrx(0): [drm] installed DRM signal handler
    (II) fglrx(0): DRIScreenInit done
    (II) fglrx(0): Kernel Module Version Information:
    (II) fglrx(0):     Name: fglrx
    (II) fglrx(0):     Version: 8.43.2
    (II) fglrx(0):     Date: Nov  9 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 = 0x0039f000
    (II) fglrx(0): [pci] find AGP GART
    (II) fglrx(0): [agp] Mode=0x1f004a1b bridge: 0x8086/0x2570
    (II) fglrx(0): [agp] AGP v1/2 disable mask 0x00000210
    (II) fglrx(0): [agp] AGP v3 disable mask   0x00000002
    (II) fglrx(0): [agp] enabling AGP with mode=0x1f004b19
    (II) fglrx(0): [agp] Remapping MC AGP space (new MCAGPBase = 0xe0000000)
    (II) fglrx(0): [agp] AGP protocol is enabled for graphics board. (cmd=0x1f004311)
    (II) fglrx(0): [agp] graphics chipset has AGP v3.0 (native mode)
    (II) fglrx(0): DRI initialization successfull!
    (II) fglrx(0): front overlay:  0xc1001400
    (II) fglrx(0): back overlay:   0xc11b0000
    (II) fglrx(0): video overlay:  0xc135ec00
    (II) fglrx(0): FBADPhys: 0xc0000000 FBMappedSize: 0x01001400
    (II) fglrx(0): FBMM initialized for area (0,0)-(1728,2428)
    (II) fglrx(0): FBMM auto alloc for area (0,0)-(1728,1050) (front color buffer - assumption)
    (II) fglrx(0): Largest offscreen area available: 1728 x 1378
    (==) fglrx(0): Backing store disabled
    old
    Code:
    Nov 30 16:08:35 localhost [fglrx] Maximum main memory to use for locked dma buffers: 1899 MBytes.
    Nov 30 16:08:35 localhost [fglrx] IRQ_MGR is disabled untill GART_CACHABLE memory will be implemented<6>[fglrx] AGP detected, AgpState   = 0x1f004a1b (hardware caps of chipset)
    Nov 30 16:08:35 localhost agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
    Nov 30 16:08:35 localhost agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
    Nov 30 16:08:35 localhost agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
    Nov 30 16:08:35 localhost [fglrx] AGP enabled,  AgpCommand = 0x1f004311 (selected caps)
    new
    Code:
    Nov 30 16:09:50 localhost [fglrx] Maximum main memory to use for locked dma buffers: 1899 MBytes.
    Nov 30 16:09:50 localhost [fglrx] AGP detected, AgpState   = 0x1f004a1b (hardware caps of chipset)
    Nov 30 16:09:50 localhost agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
    Nov 30 16:09:50 localhost agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
    Nov 30 16:09:50 localhost agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
    Nov 30 16:09:50 localhost [fglrx] AGP enabled,  AgpCommand = 0x1f004311 (selected caps)
    but this not fix slow speed and buggy graphics

    ps
    video x1950gt 512mb agp
    So maybe that options hides the interupt error? Worth a try, but I don't have any hopes at this point anymore.

  7. #47
    Join Date
    Dec 2007
    Posts
    146

    Default

    I had pulled my FX5900 and installed my AGP X1600 Pro back when Phoronix was pushing the new ATi drivers as the next coming. I tried a lot of stuff, and don't recall ever even getting the IRQ errors, but performance was still horrible.

    I'm back to my FX5900 now and am about to build a new system with an 8800 GT.

  8. #48
    Join Date
    Jan 2007
    Posts
    418

    Default

    Quote Originally Posted by psycho_driver View Post
    I had pulled my FX5900 and installed my AGP X1600 Pro back when Phoronix was pushing the new ATi drivers as the next coming. I tried a lot of stuff, and don't recall ever even getting the IRQ errors, but performance was still horrible.

    I'm back to my FX5900 now and am about to build a new system with an 8800 GT.
    It appears that maybe this option may hide the error?

    Performance was ... weird for me with the error. It was fast, n slow, sluggish, short spikes of performance, then, just slow. 8 more days! (i hope)

  9. #49

    Default

    Quote Originally Posted by NIKE View Post
    Code:
    Option "TexturedVideo" "ON"
    Option "AGPMask" "0x00000210"
    
    Option "AGPv3Mask" "0x00000002"
    <snip>
    Option "UseFastTLS" "2"
    but this not fix slow speed and buggy graphics

    ps
    video x1950gt 512mb agp
    I've tried it, and it doesn't even stop my interrupt error on my geforce k8ns ultra939 board.

    Where do you get a listing of all those parameters that explains them???

    Not that I would waste any more time trying. My respect for Radeon is done till they produce a documented driver that works right.

  10. #50
    Join Date
    Jan 2007
    Posts
    418

    Default

    Quote Originally Posted by IrradeoActive View Post
    I've tried it, and it doesn't even stop my interrupt error on my geforce k8ns ultra939 board.

    Where do you get a listing of all those parameters that explains them???

    Not that I would waste any more time trying. My respect for Radeon is done till they produce a documented driver that works right.
    Which may be tomorrow! or wednesday, this week anyway

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •