t a more significant increase.
What tests do you recommend?
--
Trond Eivind Glomsrød
Red Hat, Inc.
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
X with a rock solid, crystal clear image. I now have
a Radeon in the system. The performance is a lot faster, there are no
more artifacts in UT and the 2D image is just as good as with the G400
MAX .
--
Trond Eivind Glomsrød
Red Hat, Inc.
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
) on
> a Abit KT7A mobo, which is based on the VIA KT133A
> chipset. When I run the Soldier of Fortune Demo, or
> the Descent 3 demo using Linux 2.2.16 and XFree86 4.1
Just use the commandline switch to turn of multitexturing.
--
Trond Eivind Glomsrød
Red Hat, Inc.
___
Joseph Carter <[EMAIL PROTECTED]> writes:
> On Fri, Jun 08, 2001 at 05:10:56PM -0400, Trond Eivind Glomsrød wrote:
> > > They extend beyond that. VIA KT133A-based Abit KT7A (friend has KT7-RAID
> > > which is KT133 based and has the same problem..) 30 seconds or
s KT133 based and has the same problem..) 30 seconds or so after
> we start any serious 3D app, down goes the entire box.
FTR, I've not had this problem on an Asus A7V133 or MSI K7V Turbo,
both having the KT133A chipset.
--
Trond Eivind Glomsrød
Red Hat, Inc.
ipset is totally genuine.
You've misunderstood - Mike is talking about the "DESIGN" file
included with XFree86.
--
Trond Eivind Glomsrød
Red Hat, Inc.
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
x, which has an ASUS A7V (KT133 chipset). I'll let
> you know how I go.
Can you try running the demo in Descent3 on this? I'm seeing
weird stuff on the end (objects keep getting "stamped" on the screen -
previous instances aren't removed)
--
Trond Eivind Glomsrø
Alan Hourihane <[EMAIL PROTECTED]> writes:
> On Fri, Apr 06, 2001 at 11:04:20AM -0400, Trond Eivind Glomsrød wrote:
> > When building the DRI tree with DRM module for the kernel, the default
> > location to look for headers should be (this is the way Linus started
> &g
-`uname -r` and /usr/src/linux
--
Trond Eivind Glomsrød
Red Hat, Inc.
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
From XFree86.org's driver status page:
>
> 4.0.3: Accelerated support is provided for Mach64, Rage, Rage 128 and Radeon
> chips.
That's 2D - no 3D support.
> I believe you said you were on a Via Apollo chipset?
Wrong person - I&
's
> > not quite true..)
> > CVS drm has its up()'s and down()'s (pun intended) still and that
> > needs to
> > change with more recent kernels. I just haven't had much time to do
> > anything with it yet.
>
> Here is my recommendation:
> use
Jeff Hartmann <[EMAIL PROTECTED]> writes:
> Trond Eivind Glomsrød wrote:
>
> > Jeff Hartmann <[EMAIL PROTECTED]> writes:
> >
> >> Are you using the radeon module from the kernel? If you are this
> >> could possibly be a source of the problem
DRI CVS anyway,
so there is no backwards compatibility problems - and having a working
drm module after a kernel build would be nice.
--
Trond Eivind Glomsrød
Red Hat, Inc.
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
ngelog for the latest ac kernels.
> Radeon support is not even pre-alpha quality right now IMO. =(
It (well, yesterdays) works fine on Red Hat Linux Wolverine + rawhide updates, except
for
Descent 3. This has been a problem with all Radeon drivers I've tried, though.
x27;ve
seen with any drivers, from X CVS and DRI CVS) - after running for
some time in the demo, the driver seems to forget to remove old
objects, and they thus leave trails, making the screen hard to make
sense of rather soon.
http://people.redhat.com/teg/dri/ contains (big) images of this, from a
15 matches
Mail list logo
