agp mode 2 and tdfx driver for Voodoo 3 3000 AGP

agp mode 2 and tdfx driver for Voodoo 3 3000 AGP

Post by Thomas Mukunnemkeri » Fri, 08 Feb 2002 10:10:28



Just curious what agp mode 2 does and why the tdfx module ignores the
option "AGP Mode 2" when I specify it in the XF86Config:

Section "Device"
     Identifier  "Voodoo3"
     Driver      "tdfx"
     Option     "AGPMode" "2"
     #VideoRam    16384
     # Insert Clocks lines here if appropriate
EndSection

Here is what /var/log/XFree86.0.log says:

(II) TDFX(0): [drm] loaded kernel module for "tdfx" driver
(II) TDFX(0): [drm] created "tdfx" driver at busid "PCI:1:0:0"
(II) TDFX(0): [drm] added 8192 byte SAREA at 0xe09fe000
(II) TDFX(0): [drm] mapped SAREA 0xe09fe000 to 0x40017000
(II) TDFX(0): [drm] framebuffer handle = 0xdc000000
(II) TDFX(0): [drm] added 1 reserved context for kernel
(II) TDFX(0): [drm] Registers = 0xd8000000
(II) TDFX(0): visual configs initialized
(II) TDFX(0): Using XFree86 Acceleration Architecture (XAA)
        Screen to screen bit blits
        Solid filled rectangles
        8x8 mono pattern filled rectangles
        Indirect CPU to Screen color expansion
        Solid Lines
        Dashed Lines
        Offscreen Pixmaps
        Driver provided NonTEGlyphRenderer replacement
        Setting up tile and stipple cache:
                32 128x128 slots
                9 256x256 slots
(==) TDFX(0): Backing store disabled
(==) TDFX(0): Silken mouse enabled
(II) TDFX(0): X context handle = 0x00000001
(II) TDFX(0): [drm] installed DRM signal handler
(II) TDFX(0): [DRI] installation complete
(==) TDFX(0): Direct rendering enabled
(WW) TDFX(0): Option "AGPMode" is not used

I checked google for this newsgroup, but just about every search I have
was posts mentioning to add it in or delete it.

The reason I have been looking at all this is that I recently got DRI
working (after getting glide 3.0 and X recompiled).  However, I was
getting a frame rate of half of what someone else posted (instead of
getting 1400 frames/sec, I was only getting about 700 with DRI enabled.

So I was thinking it was because perhaps I need to specify AGPMode 2.

The bios has it enabled, and agpart was actually compiled into the
kernel (it wasn't compiled as a module).  In fact, here is what dmesg
says about agpart:
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro chipset

so the question is, does the tdfx use the agp mode option at all, or am
I missing something else that needs to be enabled or compiled in?

Tom Mukunnemkeril

 
 
 

agp mode 2 and tdfx driver for Voodoo 3 3000 AGP

Post by FateSWar » Sat, 09 Feb 2002 06:50:53


Just dropping by and I think I can give some help on that.

Your DRI gets disabled and it seems compiled correctly. I would change the
color depth and resolutions (not with ctrl+alt-+) and see if it works that
way.

I had a similar problem when my voodoo's DRI couldn't start because the
resolution was not proper.

Check these things.

- mike,
www0.org

One ring for Thomas Mukunnemkeril under the sky:

> Just curious what agp mode 2 does and why the tdfx module ignores the
> option "AGP Mode 2" when I specify it in the XF86Config:

> Section "Device"
>      Identifier  "Voodoo3"
>      Driver      "tdfx"
>      Option   "AGPMode" "2"
>      #VideoRam    16384
>      # Insert Clocks lines here if appropriate
> EndSection

> Here is what /var/log/XFree86.0.log says:

> (II) TDFX(0): [drm] loaded kernel module for "tdfx" driver
> (II) TDFX(0): [drm] created "tdfx" driver at busid "PCI:1:0:0"
> (II) TDFX(0): [drm] added 8192 byte SAREA at 0xe09fe000
> (II) TDFX(0): [drm] mapped SAREA 0xe09fe000 to 0x40017000
> (II) TDFX(0): [drm] framebuffer handle = 0xdc000000
> (II) TDFX(0): [drm] added 1 reserved context for kernel
> (II) TDFX(0): [drm] Registers = 0xd8000000
> (II) TDFX(0): visual configs initialized
> (II) TDFX(0): Using XFree86 Acceleration Architecture (XAA)
> Screen to screen bit blits
> Solid filled rectangles
> 8x8 mono pattern filled rectangles
> Indirect CPU to Screen color expansion
> Solid Lines
> Dashed Lines
> Offscreen Pixmaps
> Driver provided NonTEGlyphRenderer replacement
> Setting up tile and stipple cache:
> 32 128x128 slots
> 9 256x256 slots
> (==) TDFX(0): Backing store disabled
> (==) TDFX(0): Silken mouse enabled
> (II) TDFX(0): X context handle = 0x00000001
> (II) TDFX(0): [drm] installed DRM signal handler
> (II) TDFX(0): [DRI] installation complete
> (==) TDFX(0): Direct rendering enabled
> (WW) TDFX(0): Option "AGPMode" is not used

> I checked google for this newsgroup, but just about every search I have
> was posts mentioning to add it in or delete it.

> The reason I have been looking at all this is that I recently got DRI
> working (after getting glide 3.0 and X recompiled).  However, I was
> getting a frame rate of half of what someone else posted (instead of
> getting 1400 frames/sec, I was only getting about 700 with DRI enabled.

> So I was thinking it was because perhaps I need to specify AGPMode 2.

> The bios has it enabled, and agpart was actually compiled into the
> kernel (it wasn't compiled as a module).  In fact, here is what dmesg
> says about agpart:
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory: 439M
> agpgart: Detected Via Apollo Pro chipset

> so the question is, does the tdfx use the agp mode option at all, or am
> I missing something else that needs to be enabled or compiled in?

> Tom Mukunnemkeril


 
 
 

agp mode 2 and tdfx driver for Voodoo 3 3000 AGP

Post by Thomas Mukunnemkeri » Sat, 09 Feb 2002 09:08:50



> Just dropping by and I think I can give some help on that.

> Your DRI gets disabled and it seems compiled correctly. I would change the
> color depth and resolutions (not with ctrl+alt-+) and see if it works that
> way.

Actually, I got DRI working and I do have the default depth setup at 16.
I'm just curious what the normal frame rate is when you have DRI enabled.

For example, if I run glxgears, I get a frame rate of about 770 FPS.

Another post mentioned getting a frame rate of about 1400 FPS.  So I was
just trying to determine if perhaps there is something more I gotta do
to my configuration, or maybe their 3DFX card is super enhanced :P.

I never mentioned it, but I am running XFree 4.2.0.

> I had a similar problem when my voodoo's DRI couldn't start because the
> resolution was not proper.

> One ring for Thomas Mukunnemkeril under the sky:

>>Just curious what agp mode 2 does and why the tdfx module ignores the
>>option "AGP Mode 2" when I specify it in the XF86Config:

>>Section "Device"
>>     Identifier  "Voodoo3"
>>     Driver      "tdfx"
>>     Option   "AGPMode" "2"
>>     #VideoRam    16384
>>     # Insert Clocks lines here if appropriate
>>EndSection

>>Here is what /var/log/XFree86.0.log says:

>>(II) TDFX(0): [drm] loaded kernel module for "tdfx" driver
>>(II) TDFX(0): [drm] created "tdfx" driver at busid "PCI:1:0:0"
>>(II) TDFX(0): [drm] added 8192 byte SAREA at 0xe09fe000
>>(II) TDFX(0): [drm] mapped SAREA 0xe09fe000 to 0x40017000
>>(II) TDFX(0): [drm] framebuffer handle = 0xdc000000
>>(II) TDFX(0): [drm] added 1 reserved context for kernel
>>(II) TDFX(0): [drm] Registers = 0xd8000000
>>(II) TDFX(0): visual configs initialized
>>(II) TDFX(0): Using XFree86 Acceleration Architecture (XAA)
>>Screen to screen bit blits
>>Solid filled rectangles
>>8x8 mono pattern filled rectangles
>>Indirect CPU to Screen color expansion
>>Solid Lines
>>Dashed Lines
>>Offscreen Pixmaps
>>Driver provided NonTEGlyphRenderer replacement
>>Setting up tile and stipple cache:
>>32 128x128 slots
>>9 256x256 slots
>>(==) TDFX(0): Backing store disabled
>>(==) TDFX(0): Silken mouse enabled
>>(II) TDFX(0): X context handle = 0x00000001
>>(II) TDFX(0): [drm] installed DRM signal handler
>>(II) TDFX(0): [DRI] installation complete
>>(==) TDFX(0): Direct rendering enabled
>>(WW) TDFX(0): Option "AGPMode" is not used

>>I checked google for this newsgroup, but just about every search I have
>>was posts mentioning to add it in or delete it.

>>The reason I have been looking at all this is that I recently got DRI
>>working (after getting glide 3.0 and X recompiled).  However, I was
>>getting a frame rate of half of what someone else posted (instead of
>>getting 1400 frames/sec, I was only getting about 700 with DRI enabled.

>>So I was thinking it was because perhaps I need to specify AGPMode 2.

>>The bios has it enabled, and agpart was actually compiled into the
>>kernel (it wasn't compiled as a module).  In fact, here is what dmesg
>>says about agpart:
>>Linux agpgart interface v0.99 (c) Jeff Hartmann
>>agpgart: Maximum main memory to use for agp memory: 439M
>>agpgart: Detected Via Apollo Pro chipset

>>so the question is, does the tdfx use the agp mode option at all, or am
>>I missing something else that needs to be enabled or compiled in?

>>Tom Mukunnemkeril

 
 
 

agp mode 2 and tdfx driver for Voodoo 3 3000 AGP

Post by Stef Bo » Sat, 09 Feb 2002 17:25:40


Well,
I think there is some misunderstanding:

- first, I'm not sure about your videocard, but in my case (NIVIDIA TNT2) my
card can handle AGP, it is build in.
If you use that AGP, you don't have to use the AGP compiled in the kernel,
as you can see in your listning. You'll
have to compile it as an module. And you'll need the driver of your
videocard to offer it to your kernel as an module.

- obviously, your card doesn't reckognize the option AGPMode to activate the
right AGPmode. Check the documentation
of your videocard to do so. In my case I can let the X-server choose to use
AGPGart of the kernel first, and then the AGP of my
videocard, or anly AGPGart, or first the AGP of my videocard. Check out
what's used at your card.

Greetings,

Stef Bon
Holland
Den Haag



> Just curious what agp mode 2 does and why the tdfx module ignores the
> option "AGP Mode 2" when I specify it in the XF86Config:

> Section "Device"
>      Identifier  "Voodoo3"
>      Driver      "tdfx"
>      Option "AGPMode" "2"
>      #VideoRam    16384
>      # Insert Clocks lines here if appropriate
> EndSection

> Here is what /var/log/XFree86.0.log says:

> (II) TDFX(0): [drm] loaded kernel module for "tdfx" driver
> (II) TDFX(0): [drm] created "tdfx" driver at busid "PCI:1:0:0"
> (II) TDFX(0): [drm] added 8192 byte SAREA at 0xe09fe000
> (II) TDFX(0): [drm] mapped SAREA 0xe09fe000 to 0x40017000
> (II) TDFX(0): [drm] framebuffer handle = 0xdc000000
> (II) TDFX(0): [drm] added 1 reserved context for kernel
> (II) TDFX(0): [drm] Registers = 0xd8000000
> (II) TDFX(0): visual configs initialized
> (II) TDFX(0): Using XFree86 Acceleration Architecture (XAA)
> Screen to screen bit blits
> Solid filled rectangles
> 8x8 mono pattern filled rectangles
> Indirect CPU to Screen color expansion
> Solid Lines
> Dashed Lines
> Offscreen Pixmaps
> Driver provided NonTEGlyphRenderer replacement
> Setting up tile and stipple cache:
> 32 128x128 slots
> 9 256x256 slots
> (==) TDFX(0): Backing store disabled
> (==) TDFX(0): Silken mouse enabled
> (II) TDFX(0): X context handle = 0x00000001
> (II) TDFX(0): [drm] installed DRM signal handler
> (II) TDFX(0): [DRI] installation complete
> (==) TDFX(0): Direct rendering enabled
> (WW) TDFX(0): Option "AGPMode" is not used

> I checked google for this newsgroup, but just about every search I have
> was posts mentioning to add it in or delete it.

> The reason I have been looking at all this is that I recently got DRI
> working (after getting glide 3.0 and X recompiled).  However, I was
> getting a frame rate of half of what someone else posted (instead of
> getting 1400 frames/sec, I was only getting about 700 with DRI enabled.

> So I was thinking it was because perhaps I need to specify AGPMode 2.

> The bios has it enabled, and agpart was actually compiled into the
> kernel (it wasn't compiled as a module).  In fact, here is what dmesg
> says about agpart:
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory: 439M
> agpgart: Detected Via Apollo Pro chipset

> so the question is, does the tdfx use the agp mode option at all, or am
> I missing something else that needs to be enabled or compiled in?

> Tom Mukunnemkeril

 
 
 

agp mode 2 and tdfx driver for Voodoo 3 3000 AGP

Post by Andy Furnis » Mon, 04 Mar 2002 00:53:57



> Just curious what agp mode 2 does and why the tdfx module ignores the
> option "AGP Mode 2" when I specify it in the XF86Config:

> Section "Device"
>      Identifier  "Voodoo3"
>      Driver      "tdfx"
>      Option   "AGPMode" "2"
>      #VideoRam    16384
>      # Insert Clocks lines here if appropriate
> EndSection

> Here is what /var/log/XFree86.0.log says:

> (II) TDFX(0): [drm] loaded kernel module for "tdfx" driver
> (II) TDFX(0): [drm] created "tdfx" driver at busid "PCI:1:0:0"
> (II) TDFX(0): [drm] added 8192 byte SAREA at 0xe09fe000
> (II) TDFX(0): [drm] mapped SAREA 0xe09fe000 to 0x40017000
> (II) TDFX(0): [drm] framebuffer handle = 0xdc000000
> (II) TDFX(0): [drm] added 1 reserved context for kernel
> (II) TDFX(0): [drm] Registers = 0xd8000000
> (II) TDFX(0): visual configs initialized
> (II) TDFX(0): Using XFree86 Acceleration Architecture (XAA)
> Screen to screen bit blits
> Solid filled rectangles
> 8x8 mono pattern filled rectangles
> Indirect CPU to Screen color expansion
> Solid Lines
> Dashed Lines
> Offscreen Pixmaps
> Driver provided NonTEGlyphRenderer replacement
> Setting up tile and stipple cache:
> 32 128x128 slots
> 9 256x256 slots
> (==) TDFX(0): Backing store disabled
> (==) TDFX(0): Silken mouse enabled
> (II) TDFX(0): X context handle = 0x00000001
> (II) TDFX(0): [drm] installed DRM signal handler
> (II) TDFX(0): [DRI] installation complete
> (==) TDFX(0): Direct rendering enabled
> (WW) TDFX(0): Option "AGPMode" is not used

> I checked google for this newsgroup, but just about every search I have
> was posts mentioning to add it in or delete it.

> The reason I have been looking at all this is that I recently got DRI
> working (after getting glide 3.0 and X recompiled).  However, I was
> getting a frame rate of half of what someone else posted (instead of
> getting 1400 frames/sec, I was only getting about 700 with DRI enabled.

> So I was thinking it was because perhaps I need to specify AGPMode 2.

> The bios has it enabled, and agpart was actually compiled into the
> kernel (it wasn't compiled as a module).  In fact, here is what dmesg
> says about agpart:
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory: 439M
> agpgart: Detected Via Apollo Pro chipset

> so the question is, does the tdfx use the agp mode option at all, or am
> I missing something else that needs to be enabled or compiled in?

> Tom Mukunnemkeril

Voodoo cards do not use AGP the AGP ones behave exactly the same as PCI -
you don't need (shouldn't use - with more than one card) AGPGART in kernel.

Andy.

 
 
 

agp mode 2 and tdfx driver for Voodoo 3 3000 AGP

Post by Thomas Mukunnemkeri » Mon, 04 Mar 2002 07:32:23




>> Just curious what agp mode 2 does and why the tdfx module ignores the
>> option "AGP Mode 2" when I specify it in the XF86Config:

>> Section "Device"
>>      Identifier  "Voodoo3"
>>      Driver      "tdfx"
>>      Option   "AGPMode" "2"
>>      #VideoRam    16384
>>      # Insert Clocks lines here if appropriate
>> EndSection

> Voodoo cards do not use AGP the AGP ones behave exactly the same as PCI -
> you don't need (shouldn't use - with more than one card) AGPGART in
> kernel.

Thanks for the info.

--
Tom Mukunnemkeril
Registered Linux User # 256999