public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Asfand Yar Qazi <ay1204@qazi.f2s.com>
To: linux-kernel@vger.kernel.org
Subject: How's the nforce4 support in Linux?
Date: Thu, 24 Mar 2005 09:20:29 +0000	[thread overview]
Message-ID: <4242865D.90800@qazi.f2s.com> (raw)

Hi,

I'm currently contemplating going for an Athlon 64 system.  However, 
I'll primarily be using a Linux-based OS (Gentoo, namely), so I need 
to know how well the chipsets are supported currently.

I'd really like to go Via - but the crummy KT890 / VT8237 combo sucks 
- mainly due to the lack of SATA II with NCQ.  I share the sentiments 
of the person in a post in the AnandTech forums 
(http://tinyurl.com/6d9bx) who says:

"The feature set on the K8T890 sucks. It was supposed to use the 
VT8251 southbridge, bringing SATA-II/NCQ, HD Audio, etc. 
Unfortunately, this southbridge has since dissappeared off the face of 
the earth, and all the current K8T890 boards use the old VT8237. 
nForce4, on the other hand, has SATA-II/NCQ, hardware firewall, nice 
software overclocking/monitoring tools (ntune), gigabit lan, etc. On 
top of that, performance and overclocking is pretty damn good. I was 
at one point looking forward to the K8T890, but considering how much 
of a joke the whole product line has been (lacking features, months of 
delays with no explanation, lack of any variety of retail boards), I 
have to say I'd avoid it like the plague."

NForce4 Ultra is brilliant - in many ways.  Except it requires binary 
drivers, which I really don't want to use.  And apparently, the 
hardware firewall seems to restrict bandwidth a bit.  And even when 
its off, external chips that end up being faster 
(http://tinyurl.com/4zssp)

So, I'm wondering, are my assumptions correct?  Do I have to use 
binary drivers to make absolutely full use of the Nforce4 chipset?  Or 
is there sufficient support for me to make use of the features on it 
without using binary drivers?

Sorry for asking something that may have been asked before, but I've 
tried searching several times through the mailing list and on a search 
engine, but have had little luck.

Thanks,
	Asfand Yar

p.s. Here's something for the search engines to latch on to, so this 
post and any repies are easier to find: via nvidia nforce4 nforce 4 
kt890 kt 890 vt8237 comparison feature set supported compatibility 
binary drivers

             reply	other threads:[~2005-03-24  9:13 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24  9:20 Asfand Yar Qazi [this message]
2005-03-24  9:30 ` How's the nforce4 support in Linux? Jeff Garzik
2005-03-24  9:34   ` Arjan van de Ven
2005-03-24 10:03     ` Tupshin Harper
2005-03-24 16:27   ` Lennart Sorensen
2005-03-24 21:01     ` Jeff Garzik
2005-03-28 15:31       ` Andi Kleen
2005-03-30 19:42         ` Jeff Garzik
2005-03-30 20:17           ` Indrek Kruusa
2005-03-30 20:25             ` Jeff Garzik
2005-03-30 20:48               ` Indrek Kruusa
2005-03-30 21:06           ` Francois Romieu
2005-03-30 21:47             ` Jeff Garzik
     [not found] <3Lxis-5a0-29@gated-at.bofh.it>
     [not found] ` <3Lxis-5a0-31@gated-at.bofh.it>
     [not found]   ` <3Lxis-5a0-33@gated-at.bofh.it>
     [not found]     ` <3Lxis-5a0-27@gated-at.bofh.it>
2005-03-24 10:11       ` Asfand Yar Qazi
     [not found] <3LwFC-4Ko-15@gated-at.bofh.it>
     [not found] ` <3LwYW-4Xx-11@gated-at.bofh.it>
     [not found]   ` <3LwYZ-4Xx-25@gated-at.bofh.it>
2005-03-24 10:00     ` Asfand Yar Qazi
2005-03-24 10:11       ` Arjan van de Ven
2005-03-24 16:29       ` Lennart Sorensen
2005-03-24 16:41         ` Raphael Jacquot
2005-03-24 20:41       ` Jeff Garzik
2005-03-25  2:15 ` Robert Hancock
2005-03-25  2:40   ` Lee Revell
  -- strict thread matches above, loose matches on Subject: below --
2005-03-25  9:37 Chuck Ebbert
2005-03-25 22:59 Julien Wajsberg
2005-03-25 23:14 ` Lee Revell
2005-03-26  0:38   ` Julien Wajsberg
2005-03-26  0:48     ` Lee Revell
2005-03-29 18:58   ` Tomasz Torcz
2005-03-29 20:40     ` Lee Revell
2005-03-30 15:00       ` Tomasz Torcz
2005-03-30 16:45         ` Lennart Sorensen
2005-03-30 19:19         ` Martin Schlemmer
2005-03-30 21:01           ` Lee Revell
2005-03-31  5:58             ` Martin Schlemmer
2005-03-25 23:20 ` Lee Revell
2005-03-26  0:17   ` Julien Wajsberg
2005-03-26 14:13     ` Michal Schmidt
2005-03-29  6:47       ` Julien Wajsberg
2005-03-25 23:21 ` Lee Revell
2005-03-25 23:41   ` Julien Wajsberg
2005-04-05 13:42 ` Julien Wajsberg
2005-04-05 14:10   ` Richard B. Johnson
2005-04-05 22:58     ` Julien Wajsberg
2005-04-06 11:41       ` Richard B. Johnson
2005-04-06 16:02         ` Bartlomiej Zolnierkiewicz
2005-04-10 23:43           ` Julien Wajsberg
2005-04-10 23:27         ` Julien Wajsberg
2005-03-26 16:01 Chuck
2005-03-26 15:19 ` Arjan van de Ven
2005-03-26 17:32   ` Marcin Dalecki
2005-03-27 12:26     ` Chuck
2005-04-02 23:55     ` Julien Wajsberg

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=4242865D.90800@qazi.f2s.com \
    --to=ay1204@qazi.f2s.com \
    --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