From: chakkerz_dev@optusnet.com.au
To: Dr NoName <spamacct11@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NForce 2 support
Date: Wed, 25 Aug 2004 11:02:11 +1000 [thread overview]
Message-ID: <200408250102.i7P12Bp08783@mail019.syd.optusnet.com.au> (raw)
Heya
Not a kernel hacker but and nforce2 user
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
> Dr NoName <spamacct11@yahoo.com> wrote:
>
> Hello kernel hackers,
>
> I have a quick question: what is the current state of
> support for NVidia NForce 2 chipset? I am planning to
> get a new Athlon XP rig and just wondering if NForce
> (specifically Abit NF7-S) is a good choice. I can
> compile a custom kernel and don't mind installing
> nvidia drivers separately but I do want everything to
> work and be rock-solid (ide, agp, sound, network,
> etc.). So will NForce work or should I stick with VIA?
>
> thanks in advance,
>
> Eugene
>
>
>
> _______________________________
> Do you Yahoo!?
> Win 1 of 4,000 free domain names from Yahoo! Enter now.
> http://promotions.yahoo.com/goldrush
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2004-08-25 1:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 1:02 chakkerz_dev [this message]
2004-08-25 1:24 ` Gene Heskett
2004-08-25 2:05 ` Dr NoName
2004-08-25 2:22 ` Lee Revell
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=200408250102.i7P12Bp08783@mail019.syd.optusnet.com.au \
--to=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
all inboxes | Powered by JetHome®