linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ignacio Vazquez-Abrams <ignacio@openservices.net>
To: "Øystein Haare" <oyhaare@online.no>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Via chipset
Date: Tue, 7 Aug 2001 21:54:26 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0108072147450.11071-100000@terbidium.openservices.net> (raw)
In-Reply-To: <997225828.10528.4.camel@eagle>

On 8 Aug 2001, Øystein Haare wrote:

> I'm sorry if this question has been answered recently (I'm not
> subscribed to the list).
>
> I'm planning on getting a new workstation, and I kinda want an AMD
> system. But it seems that most (all?) motherboards for the amd cpu's use
> VIA chipsets, and some people have experienced problems with via
> chipsets and linux.

My Asus A7V (not 133, not 266) is fine with Red Hat 7.1, but it only supports
B-type (100/200 MHz FSB) Athlons. I haven't yet tested it with kernels newer
than what Red Hat provides, though.

> Have these problems been fixed, or are they still present?

I'm not having any that aren't being caused by my hard drives right now.

> would I be better off getting a P4 system?

Certainly not. I've seen benchmarks where an Athlon 1.4 beats the stuffing out
of a P4 1.8. I realize its just a benchmark, but when it happens in about 70%
of the benchmarks (oriented at different subsytstems) it HAS to be more than
just coincedence.

And have you seen the price difference lately? Even if the Athlon was slower,
it's still a lot cheaper.

> Øystein Haare

-- 
Ignacio Vazquez-Abrams  <ignacio@openservices.net>


  parent reply	other threads:[~2001-08-08  1:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07 23:10 Via chipset Øystein Haare
2001-08-07 18:46 ` Bobby D. Bryant
2001-08-07 23:16 ` Dan Hollis
2001-08-07 23:36 ` Alan Cox
2001-08-07 23:47   ` Larry McVoy
2001-08-08  9:16     ` Janne Pänkälä
2001-08-08 16:09     ` Marco Colombo
2001-08-15  3:25   ` Maxwell Spangler
2001-08-15 11:48     ` Alan Cox
2001-08-15 12:28       ` Bobby D. Bryant
2001-08-15 19:59       ` Dan Hollis
2001-08-15 20:16         ` Alan Cox
2001-08-15 20:27           ` Dan Hollis
2001-08-15 20:32             ` Alan Cox
2001-08-15 21:50               ` Bryan O'Sullivan
2001-08-16 15:35           ` Bob Martin
2001-08-16 21:09             ` Dan Hollis
2001-08-17  3:04               ` Adrian V. Bono
2001-08-20 22:52                 ` Bob Martin
2001-08-08  1:54 ` Ignacio Vazquez-Abrams [this message]
2001-08-15 16:46 Ryan C. Bonham
     [not found] <no.id>
2001-08-15 16:09 ` Alan Cox
2001-08-16 16:02 ` Alan Cox
2001-09-12 18:49 VIA chipset Marco Colombo
2001-09-12 19:22 ` Alan Cox
2001-09-12 20:06 ` Jussi Laako
2001-09-12 20:13   ` Marco Colombo
2001-09-12 20:55     ` Anders Peter Fugmann
2001-09-14 17:29     ` Jussi Laako
2001-10-05 10:20 amit yajurvedi
2001-10-15 11:09 grouch
     [not found] <Pine.LNX.4.10.10110151147340.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 19:01 ` grouch
     [not found] <Pine.LNX.4.10.10110151554040.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 20:31 ` grouch
     [not found] <Pine.LNX.4.10.10110151635040.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 21:22 ` grouch
2001-10-17 11:45 grouch

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=Pine.LNX.4.33.0108072147450.11071-100000@terbidium.openservices.net \
    --to=ignacio@openservices.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oyhaare@online.no \
    /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;
as well as URLs for NNTP newsgroup(s).