DRI and the radeon.o kernel module -- Joy

[Bill Fink]

On Fri Apr 11 2003, Stefan Bruda wrote:

> Joy, well, sort of: DRI is now up and running, the FPS jumped about
> three times, yay.  Thanks for the solution.
> 
> However, there is a problem in the sense that I am no longer use AGP.
> The same /var/log/XFree86.0.log now says:
> 
> (II) RADEON(0): [drm] created "radeon" driver at busid "PCI:0:16:0"
> (II) RADEON(0): [drm] added 8192 byte SAREA at 0xe3013000
> (II) RADEON(0): [drm] mapped SAREA 0xe3013000 to 0x30019000
> (II) RADEON(0): [drm] framebuffer handle = 0xb8000000
> (II) RADEON(0): [drm] added 1 reserved context for kernel
> (II) RADEON(0): [agp] Mode 0x07000207 [AGP 0x106b/0x002d; Card 0x1002/0x4c57]
> (II) RADEON(0): [agp] 8192 kB allocated with handle 0xe3016000
> (II) RADEON(0): [agp] ring handle = 0x00000000
> (EE) RADEON(0): [agp] Could not map ring
> (WW) RADEON(0): [agp] AGP failed to initialize -- falling back to PCI mode.
> (WW) RADEON(0): [agp] If this is an AGP card, you may want to make sure the agpgart
> kernel module is loaded before the radeon kernel module.
> 
> and then goes on and does the right thing, but on PCI instead of AGP.
> I doubt the solution is the one sugggested above, both agpgart and
> radeon are compiled into the kernel instead of being modules.

As reported in an earlier message, I experience the exact same behavior.
After doing some googling, several others have reported the same, and
there was never a solution given, so I guess this is just the state of
affairs on PPC.  Despite the warning message, everything in X seems to
be running well so I'm happy and won't worry about it anymore, at least
until someone ever reports a fix or workaround.

Now that you've got DRI working, try out tuxracer or chromium.  They're
a nice pleasant diversion at times.

						-Bill