From: "Michael B. Allen" <mballen@erols.com>
To: safemode <safemode@voicenet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA chipset problems with 2.2?
Date: Thu, 15 Feb 2001 13:43:26 -0500 [thread overview]
Message-ID: <20010215134326.B1282@angus.foo.net> (raw)
In-Reply-To: <20010215035411.A1599@angus.foo.net> <3A8BBE90.90F52B2A@voicenet.com>
In-Reply-To: <3A8BBE90.90F52B2A@voicenet.com>; from safemode@voicenet.com on Thu, Feb 15, 2001 at 06:33:36AM -0500
On Thu, Feb 15, 2001 at 06:33:36AM -0500, safemode wrote:
> > What's the nature of the VIA chipset problems? I want to get a new system
>
> There are no problems with 2.2.x.
I'm very glad to hear that because the AMD chips are the obvious
choice for a lot of people(all?).
> (classic), get the KA7 by abit. Duron and T-bird should get KT7 or
> something like that . I'd use alan cox's latest patch.
>From kernelnotes? Do you have a link so I'm sure?
> They work great.
> Awesome performance. As good as linux gets.
That sounds favorable :~)
Thanks,
Mike
--
signature pending
prev parent reply other threads:[~2001-02-15 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 8:54 VIA chipset problems with 2.2? Michael B. Allen
2001-02-15 11:33 ` safemode
2001-02-15 18:43 ` Michael B. Allen [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=20010215134326.B1282@angus.foo.net \
--to=mballen@erols.com \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode@voicenet.com \
/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