Re: Radeon 9200 & AGP 8x

[Jacob S <stormspotter@6Texans.net>]

On Thu, 7 Oct 2004 19:51:34 +0200
Andrea Vettorello <andrea.vettorello@gmail.com> wrote:

> On Thu, 7 Oct 2004 11:22:01 -0500, Jacob S <stormspotter@6texans.net>
> wrote:
> > On Thu, 07 Oct 2004 09:52:14 +0200
> > Dominique Dumont <domi@komarr.grenoble.hp.com> wrote:
> > 
> > > Jacob S <stormspotter@6Texans.net> writes:
> > >
> > > > I'm running the latest updates in Sarge, with a 2.6.7-1-k7
> > > > kernel. I've modprobed agpgart and nvidia_agp, which according
> > > > to the logs recognize the agp bridge on the motherboard.
> > >
> > > You also have to load a radeon module *after* the agpgart
> > > module. Here's What I use in my modutils:
> > >
> > > # load agpgart before radeon so DRI can work
> > > # when X11 is launched
> > > add below radeon agpgart
> > 
> > Thanks, but X11 is already doing this for me. I am loading agpgart
> > and nvidia_agp via modprobe, and then have a driver line in
> > /etc/X11/XF86Config-4 to tell X to use the radeon driver. After I
> > load X, I can do a lsmod and see that the radeon module is loaded.
> > This is also the same method I use on the computer that's
> > successfully using a Radeon 9200SE right now.
> > 
> > Investigating the problem a little more, it seems the lack of dri
> > support is due to the following errors in dmesg. But google doesn't
> > seem to be helping much there either; all the hits it returns seem
> > to be unrelated to my problem. I've also tried upgrading to
> > 2.6.8-1-k7, instead of 2.6.7, but it returns the same errors in
> > dmesg.
> > 
> > mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x200000
> > mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x200000
> > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
> > [drm:radeon_unlock] *ERROR* Process 2157 using kernel context 0
> > 
> > Does anyone have any more suggestions?
> 
> Yes, use "ati" instead of "radeon" on your XF86Config-4...

Excellent! Thanks, Andrea.

I was googling and found some threads indicating I would need to disable
the vesafb framebuffer, but evidently not, as it's now working. Glxgears
is now showing 2600fps, and tuxracer is getting between 125 & 200 fps
(about the most advanced game I expect this user to play).

Thanks again,
Jacob