public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Dr NoName <spamacct11@yahoo.com>
Cc: chakkerz_dev@optusnet.com.au,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: NForce 2 support
Date: Tue, 24 Aug 2004 22:22:22 -0400	[thread overview]
Message-ID: <1093400541.5678.9.camel@krustophenia.net> (raw)
In-Reply-To: <20040825020538.55821.qmail@web12306.mail.yahoo.com>

On Tue, 2004-08-24 at 22:05, Dr NoName wrote:
> > nforce 2 works sweet with the exception of sound
> > which has been broken in 2.6.7 and 
> > 2.6.8.1 causing system crashes. If you have a
> > soundcard not to worry, if you are 
> > gonna run onboard ... wait and see with 2.6.9 brings
> 
> 
> is that with the open source drivers or nvidia
> proprietary ones? How do the two sets of drivers
> compare?
> 

The open source sound drivers do not work as well as the binary ones. 
SPDIF/AC3 does not work in the current ALSA driver and nvidia will not
release the required documentation to get it working.  Worse, the
binary-only driver is an OSS and not an ALSA driver!  Unbelievable.

The network driver had to be reverse engineered.  Apparently nvidia
engineers helped to get the gigabit support and some other features
working, but only after people had to reverse engineer the basic
functions.

Stick with VIA.  Nvidia is not Linux friendly.

Lee


  reply	other threads:[~2004-08-25  2:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25  1:02 NForce 2 support chakkerz_dev
2004-08-25  1:24 ` Gene Heskett
2004-08-25  2:05 ` Dr NoName
2004-08-25  2:22   ` Lee Revell [this message]
2004-08-25  3:44   ` Rodrigo F Baroni
2004-08-25 11:25 ` Prakash K. Cheemplavam
  -- strict thread matches above, loose matches on Subject: below --
2004-08-24 23:38 Dr NoName

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=1093400541.5678.9.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=chakkerz_dev@optusnet.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spamacct11@yahoo.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