Direct Rendering Infrastructure

Doug wrote:

> if you notice anything out of the ordinary please help me fix it
> Thanks!

The sections below seem relevent, but I'm not sure what could cause the 
"could not bind".  Just for giggles, could you try adding the following 
line to your device section:

	Option	"ForcePCIMode" "true"

>>(II) RADEON(0): [drm] loaded kernel module for "radeon" driver
>>(II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:0:0"
>>(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe0995000
>>(II) RADEON(0): [drm] mapped SAREA 0xe0995000 to 0x40017000
>>(II) RADEON(0): [drm] framebuffer handle = 0xd0000000
>>(II) RADEON(0): [drm] added 1 reserved context for kernel
>>(II) RADEON(0): [agp] Mode 0x1f000207 [AGP 0x1039/0x0646; Card 0x1002/0x4966]
>>(II) RADEON(0): [agp] 8192 kB allocated with handle 0xe8999000
>>(EE) RADEON(0): [agp] Could not bind
>>(II) RADEON(0): [drm] removed 1 reserved context for kernel
>>(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xe0995000 at 0x40017000
>>(II) RADEON(0): Memory manager initialized to (0,0) (1600,8191)
>>(II) RADEON(0): Reserved area from (0,1200) to (1600,1202)
>>(II) RADEON(0): Largest offscreen area available: 1600 x 6989
>>(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)

[snip]

>>(WW) RADEON(0): Option "dri" is not used
>>(II) RADEON(0): Direct rendering disabled

Doug wrote:

>>(II) RADEON(0): [agp] Mode 0x1f000207 [AGP 0x1039/0x0646; Card 0x1002/0x4966]
>>(II) RADEON(0): [agp] 8192 kB allocated with handle 0xe8999000
>>(EE) RADEON(0): [agp] Could not bind
>>(II) RADEON(0): [drm] removed 1 reserved context for kernel
>>(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xe0995000 at 0x40017000

Doug,

I think Ian's on the right track...that the AGP bind failure is causing 
the X server to disable direct rendering.

What's the output of:

   dmesg | grep agpgart

Maybe your host bridge is unsupported.

-- 
                                /\
          Jens Owen            /  \/\ _
   jens@...  /    \ \ \   Steamboat Springs, Colorado

actually now i get this error when i try to play "UT2003"
Xlib:  extension "XiG-SUNDRY-NONSTANDARD" missing on display ":0.0".
OpenGL renderer relies on DXTC/S3TC support.

History:

Exiting due to error

do you know how to fix that?
Thanks

> On Wed, 2003-04-09 at 10:19, Jens Owen wrote:
> > Doug wrote:
> > 
> > >>(II) RADEON(0): [agp] Mode 0x1f000207 [AGP 0x1039/0x0646; Card 0x1002/0x4966]
> > >>(II) RADEON(0): [agp] 8192 kB allocated with handle 0xe8999000
> > >>(EE) RADEON(0): [agp] Could not bind
> > >>(II) RADEON(0): [drm] removed 1 reserved context for kernel
> > >>(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xe0995000 at 0x40017000
> > 
> > Doug,
> > 
> > I think Ian's on the right track...that the AGP bind failure is causing 
> > the X server to disable direct rendering.
> > 
> > What's the output of:
> > 
> >    dmesg | grep agpgart
> > 
> > Maybe your host bridge is unsupported.
-- 
Doug <admin@...>

Doug wrote:
> actually now i get this error when i try to play "UT2003"
> Xlib:  extension "XiG-SUNDRY-NONSTANDARD" missing on display ":0.0".
> OpenGL renderer relies on DXTC/S3TC support.
> 
> History:
> 
> Exiting due to error

There's two issues here.  The first is a COMPLETELY HARMLESS WARNING. 
Basically, it's checking for an extension that only exists on XiG's 
implementation.  The way that it checks for it causes Xlib to generate a 
message.  The second means that you have an older version of UT2k3 that 
still requires S3TC.  If you upgrade to a more recent version that 
problem should go away.

However, UT2k3 will NOT WORK on any open-source driver that I know of. 
We have bugs in our driver code, and people are working on it.  They're 
just hard bugs and nobody seems to have very much time to dig that deep. :(