From: Robert Cohen <robert@coorong.anu.edu.au>
To: linux-kernel@vger.kernel.org
Subject: Question: Status of VIA chipsets and 2.2 kernels
Date: Wed, 09 May 2001 17:14:02 +1000 [thread overview]
Message-ID: <3AF8EE3A.21932E5D@tltsu.anu.edu.au> (raw)
What with all the various problem reports flying around for via
chipsets, Ive lost track of the state of play as regards via
northbridges and south bridges.
I am thinking of buying a machine with a via chipset and I wan't to know
how stable it is likely to be with Linux.
I would appreciate it if someone who know's whats going on can give a
report on the state of play
as regards to all the problems and their current status with 2.2 kernels
(and 2.4 if their feeling energetic).
Possible machine are:
a P3 machine with a ASUS CUV4X-E motherboard which uses the apollo pro
694X northbridge and a 686B southbridge.
An athlon machine with an ASUS A7V motherboard which uses a KT133
(VT8363) northbridge and a 686A southbridge.
An athlon machine with an ASUS A7V133 motherboard which uses a KT133A
(VT8363A) northbridge and a 686B southbridge.
Problems Ive been hearing about include DMA disk transfers between
channels. Some reports say these only occur with Western digital disks.
The 2 athlon boards listed include an onboard promise IDE controller. So
I should be OK if I use this for disks, right?
Any other problems I should know about?
--
Robert Cohen
Unix Support
TLTSU
Australian National University
Ph: 612 58389
next reply other threads:[~2001-05-09 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 7:14 Robert Cohen [this message]
2001-05-09 10:23 ` Alan Cox
2001-05-09 15:00 ` Gerhard Mack
2001-05-10 2:54 ` Robert Cohen
2001-05-09 16:22 ` God
[not found] <Pine.LNX.4.10.10105091135360.1509-100000@coffee.psychology.mcmaster.ca>
2001-05-10 2:40 ` Robert Cohen
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=3AF8EE3A.21932E5D@tltsu.anu.edu.au \
--to=robert@coorong.anu.edu.au \
--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
all inboxes | Powered by JetHome®