public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Webb <webbb@desertscenes.net>
To: Greg Frank <frank@juniperlaw.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] AMD/AGP issues
Date: 31 Jul 2002 19:20:19 -0700	[thread overview]
Message-ID: <1028168435.26944.16.camel@bwpc.local> (raw)
In-Reply-To: <3D4892A8.7030105@juniperlaw.com>

I've been running a dual Athlon system at work for about a year without
a single problem.  I have long processing jobs running on it pretty much
continuously, so it's not lightly loaded either.  My main server at home
is also an Athlon system that runs 24/7, and I haven't had a single
problem with it either.  Both systems use NVidia graphics cards.

Brian


On Wed, 2002-07-31 at 18:45, Greg Frank wrote:
> Hi.  I remember when the AMD/AGP issues with Linux were first being 
> reported, you guys had some of the most comprehensive info on your site. 
>  Lately, I haven't seen very much info about it... although I have seen 
> several people commenting online recently that they have been using 
> Linux on recently  built AMD systems with no problems.  Since I am 
> considering putting together an AMD system pretty soon, I am curious 
> about how the situation stands at this point.  Can you please tell me if 
> there is a new kernel version that addresses the problem?  Also, if not, 
> does it help at all if you compile the kernel specifically on an AMD 
> processor?  (I'm guessing not, but it's nice to hope).
> 
> Thanks for any info you can pass along.
> 
> Greg Frank




      parent reply	other threads:[~2002-08-01  2:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-01  1:45 [gentoo-dev] AMD/AGP issues Greg Frank
2002-08-01  2:04 ` Jonathan Kelly
2002-08-01  2:20 ` Brian Webb [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1028168435.26944.16.camel@bwpc.local \
    --to=webbb@desertscenes.net \
    --cc=frank@juniperlaw.com \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox