Chris Ison wrote:
Chris Ison wrote:here is the log as requested ... also pcigart is enabled in the source ... as for x11perf, I may have miss understood the option, but its atleast 3 *text* ones (after the 3rd I gave up), but the dots and lines ones worked. glxgears works fine, so its obviously something glxgears doesn't do ...Could you send your XFree86 log? I suppose it's possible that it's still trying to use AGP to transfer data. Is PCIGART enabled?(II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) RADEON(0): PCI bus 0 card 15 func 0 (**) RADEON(0): Depth 16, (--) framebuffer bpp 16 (II) RADEON(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps) (==) RADEON(0): Default visual is TrueColor (**) RADEON(0): Option "ForcePCIMode" (==) RADEON(0): RGB weight 565 (II) RADEON(0): Using 6 bits per RGB (8 bit DAC)
[snip]
(II) RADEON(0): initializing int10 (II) RADEON(0): Primary V_BIOS segment is: 0xc000 (--) RADEON(0): Chipset: "ATI Radeon 9000 If (AGP)" (ChipID = 0x4966) (--) RADEON(0): Linear framebuffer at 0xd8000000 (--) RADEON(0): MMIO registers at 0xe5000000 (--) RADEON(0): VideoRAM: 65536 kByte (64-bit DDR SDRAM) (**) RADEON(0): Forced into PCI-only mode (II) RADEON(0): CloneDisplay option not set -- defaulting to auto-detect (II) RADEON(0): Primary Display == Type 1
[snip]
Somebody else who has more experience with the PCI Radeons than I will have to answer this. Is this just a bad log message (saying AGP where it should say PCIGART), or is it actually trying to use AGP here?(II) RADEON(0): [drm] created "radeon" driver at busid "PCI:0:15:0" (II) RADEON(0): [drm] added 8192 byte SAREA at 0xcc859000 (II) RADEON(0): [drm] mapped SAREA 0xcc859000 to 0x40012000 (II) RADEON(0): [drm] framebuffer handle = 0xd8000000 (II) RADEON(0): [drm] added 1 reserved context for kernel (II) RADEON(0): [pci] 8192 kB allocated with handle 0xd085d000 (II) RADEON(0): [pci] ring handle = 0xd085d000 (II) RADEON(0): [pci] Ring mapped at 0x4422e000 (II) RADEON(0): [pci] Ring contents 0x00000000 (II) RADEON(0): [pci] ring read ptr handle = 0xd095e000 (II) RADEON(0): [pci] Ring read ptr mapped at 0x40014000 (II) RADEON(0): [pci] Ring read ptr contents 0x00000000 (II) RADEON(0): [pci] vertex/indirect buffers handle = 0xd095f000 (II) RADEON(0): [pci] Vertex/indirect buffers mapped at 0x4432f000 (II) RADEON(0): [pci] Vertex/indirect buffers contents 0x00000000 (II) RADEON(0): [drm] register handle = 0xe5000000 (II) RADEON(0): [dri] Visual configs initialized (II) RADEON(0): CP in BM mode (II) RADEON(0): Using 8 MB AGP aperture (II) RADEON(0): Using 1 MB for the ring buffer (II) RADEON(0): Using 2 MB for vertex/indirect buffers (II) RADEON(0): Using 1 MB for AGP textures
Chris, is it possible for you to try without the AGP driver loaded at all? I don't have any PCI Radeons (of any variety), so I can't test this myself. This really smells like it's still trying to use AGP to do certain transfers to the card. Although, if that were the case it seems like any GL app should lock, and gears works.
You say "the system locks." Is it a total-death hard lock? Do you have another box that could SSH in? It might be intereting to run the app in gdb to see where it's wedged.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
