public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marvin Justice <mjustice@boxxtech.com>
To: "Ion Badulescu" <ionut@cs.columbia.edu>,
	"David S. Miller" <davem@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: What Athlon chipset is most stable in Linux?
Date: Wed, 14 Nov 2001 11:24:56 -0600	[thread overview]
Message-ID: <200111141119328.SM01008@there> (raw)
In-Reply-To: <3B6867E6CB09B24385A73719A50C7C9A797750@athena.boxxtech.com>
In-Reply-To: <3B6867E6CB09B24385A73719A50C7C9A797750@athena.boxxtech.com>

The 762 North Bridge definitely has AGP issues and will lock up with GeForce 
3 and nVidia's latest official drivers. I just got my hands on beta drivers  
and the lockups appear to have gone away --- so far ;-) Their binary only 
kernel module has functions with names ike "AMD_FixupGART", 
"AMD_ApplyChipsetUpdates" etc.

-Marvin


On Wednesday 14 November 2001 10:54 am, Ion Badulescu wrote:
> On Tue, 13 Nov 2001 19:16:07 -0800 (PST), David S. Miller 
<davem@redhat.com> wrote:
>  >   From: Dan Hollis <goemon@anime.net>
>  >   Date: Tue, 13 Nov 2001 19:11:56 -0800 (PST)
>  >
>  >   BTW this bug apparently doesnt affect AMD760MP as I am able to use
>  >   geforce2 with quake and unreal tournament for hours straight without
>  > any problems.
>  >
>  > I'm rather sure the AMD761 problems are motherboard vendor
>  > independant, because I have 2 systems so far, using totally different
>  > AMD761 based motherboards, which both hang pretty reliably with AGP.
>
> As far as I know, the 760MP chipset uses a 762 North Bridge, not a 761.
>  That might explain why the 760MP is stable and the 760 is not.
>
> Ion

       reply	other threads:[~2001-11-14 17:25 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B6867E6CB09B24385A73719A50C7C9A797750@athena.boxxtech.com>
2001-11-14 17:24 ` Marvin Justice [this message]
2001-11-13 17:29 What Athlon chipset is most stable in Linux? Giles Tyson
2001-11-13 18:00 ` Paul G. Allen
2001-11-13 22:41   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-11-13 13:19 Martin Eriksson
2001-11-13 16:06 ` Pascal Schmidt
2001-11-13 17:12 ` Jeffrey W. Baker
2001-11-13 21:08 ` Calin A. Culianu
2001-11-13 21:37   ` Brian
2001-11-13 22:18     ` Paul G. Allen
2001-11-13 22:39       ` Calin A. Culianu
2001-11-14  1:27       ` Stuart Young
2001-11-14 20:08         ` Calin A. Culianu
2001-11-14  2:32     ` David S. Miller
2001-11-14  3:05       ` Dan Hollis
2001-11-14  3:11         ` David S. Miller
2001-11-14  3:11       ` Brian
2001-11-14  2:55         ` Joel Jaeggli
2001-11-14 20:04           ` Calin A. Culianu
2001-11-14  3:13         ` David S. Miller
2001-11-14 14:23           ` Mike Dresser
2001-11-14  3:11       ` Dan Hollis
2001-11-14  3:16         ` David S. Miller
2001-11-14 16:54           ` Ion Badulescu
2001-11-15  1:03           ` Paul G. Allen
2001-11-15  1:15             ` Dan Hollis
2001-11-15  1:23             ` Stuart Young
2001-11-15  1:51               ` Paul G. Allen
     [not found]             ` <20011116144835.A22537@weta.f00f.org>
2001-11-20  7:43               ` Paul G. Allen
2001-11-20 16:49                 ` Gérard Roudier
2001-11-15  0:45         ` Stuart Young
2001-11-15  9:58           ` David S. Miller
2001-11-14  3:19       ` Marvin Justice
2001-11-14 13:27         ` Chris Meadors
2001-11-14  6:38   ` DevilKin
2001-11-13 21:19 ` Dan Hollis
2001-11-14  2:29   ` David S. Miller
2001-11-14 10:51     ` Alan Cox
2001-11-14 10:48       ` David S. Miller
2001-11-15 19:57       ` Marek Mentel
2001-11-15 13:04         ` David S. Miller

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=200111141119328.SM01008@there \
    --to=mjustice@boxxtech.com \
    --cc=davem@redhat.com \
    --cc=ionut@cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.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