public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Allen <the3dfxdude@hotmail.com>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is nForce2 good choice under Linux?
Date: Fri, 13 Feb 2004 15:12:30 -0700	[thread overview]
Message-ID: <20040213221230.GA902@tesore.local> (raw)
In-Reply-To: <Pine.LNX.4.58.0402132048330.31906@alpha.polcom.net>

On Fri, Feb 13, 2004 at 09:10:36PM +0100, Grzegorz Kulewski wrote:
> Hi,
> 
> I am recently considering buying Abit AN7 motherboard with NVIDIA nForce2 
> Ultra 400 with MCP-T bridge.


Short answer:  don't.  Nvidia sucks -- they don't support open source at all.

Longer answer:  You can probably get away with it if you make a good choice with
a board.  Read up specifically on which boards work.

My suggestion, based on experience:   Get a Shuttle AN35N and flash the bios 
to the latest to fix the lockup bug.  It's a $40 board and comes with 5 PCI
slots and 1 AGP.  No firewire or SATA, but if you want them you could now buy
quality, supported PCI cards instead.  This motherboard can run vanilla 2.6.2, 
with nforce IDE, sound and net.  The sound and net nforce drivers need some work
done, so if you don't like how they run you still have lots of PCI slots.  It
doesn't have built on video so you have an option here too.  And you should get 
a good supported ATI card anyway if you want 3d.

I use this board. It is stable, cheap, fast, and fully functional.  Though if I
had a choice to buy a board again, it will not be nvidia.

Jesse

  parent reply	other threads:[~2004-02-13 22:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 20:10 is nForce2 good choice under Linux? Grzegorz Kulewski
2004-02-13 20:32 ` Daniel Drake
2004-02-13 21:01   ` aviv bergman
2004-02-13 21:36     ` Grzegorz Kulewski
2004-02-13 22:17     ` Jesse Allen
2004-02-13 22:36       ` Craig Bradney
2004-02-15 11:53       ` Sander
2004-02-14  0:37     ` John Dee
2004-02-13 21:24   ` Grzegorz Kulewski
2004-02-13 22:05     ` Daniel Drake
2004-02-13 22:12 ` Jesse Allen [this message]
     [not found] <1oRXf-7zC-13@gated-at.bofh.it>
     [not found] ` <1oSgx-7QJ-11@gated-at.bofh.it>
     [not found]   ` <1oSJA-8nw-17@gated-at.bofh.it>
     [not found]     ` <1oTPp-YO-25@gated-at.bofh.it>
     [not found]       ` <1pt6s-686-9@gated-at.bofh.it>
2004-02-15 14:59         ` Ryan Reich

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=20040213221230.GA902@tesore.local \
    --to=the3dfxdude@hotmail.com \
    --cc=kangur@polcom.net \
    --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