Re: athlon/agp issue. fixed or not?!?


Subject: Re: athlon/agp issue. fixed or not?!?
From: Justin Dieters (enderak@yahoo.com)
Date: Tue Feb 26 2002 - 12:29:19 AKST


I can run UT on linux non-accelerated. Albeit very slow. I'm using an
Athlon4 1.0 Ghz, 512 RAM, Trident CyberbladeXPm (m is for mobile - this
is a laptop) and at almost the lowest settings I can barely get the
framerate above 30 fps..

But it IS possible.. just not very pretty :)

Justin

Craig Callender wrote:

> Okay, so I think you just answered my question that I've been having. I'm
> a huge UT fan, but I cannot get it to run in RedHat Linux 7.2. Is this
> because I have not installed an accelerated X Server? If so, how do I (or
> point me in a direction at least). I also have an nVidia (a GeForce 2
> MX). How can I make sure I AM running an accelerated X Server? Thanks
> for the email man, this will be awsome if I can get it running.
>
> On Tue, 26 Feb 2002, Clay Scott wrote:
>
> Date: Tue, 26 Feb 2002 12:15:55 -0900
> From: Clay Scott <mcfeelie@pobox.alaska.net>
> To: aklug@aklug.org
> Subject: Re: athlon/agp issue. fixed or not?!?
>
>
> so far i've tried adding append="mem=nopentium" to my lilo.conf,
> compiling Memory Type Range Resistor support into my kernel as well as
> removing agpgart support and still i get lockups. these are all of the
> fixes i've been able to find mentioned online and here, but none seem to
> work. i'm running an accelerated x server (NVdriver) so i can play
> games, use opengl apps, etc and they seem to run fine, though if i run a
> program that uses a lot of processor resources (i.e. seti@home), instant
> lockup. aside from completely removing agp support and reverting to a
> non-opengl/accelerated x server, i don't know of anything else i can
> do...
>
> clay
>
>
>
> In the beginning there was data. The data was without form and
> null, and darkness was upon the face of the console; and the Spirit of
> IBM was moving over the face of the market. And DEC said, "Let there
> be registers"; and there were registers. And DEC saw that they
> carried; and DEC separated the data from the instructions. DEC called
> the data Stack, and the instructions they called Code. And there was
> evening and there was morning, one interrupt.
> -- Rico Tudor, "The Story of Creation or, The Myth of Urk"
>
>
>
>



This archive was generated by hypermail 2a23 : Tue Feb 26 2002 - 12:35:19 AKST