From: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
To: chakkerz_dev@optusnet.com.au
Cc: Dr NoName <spamacct11@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: NForce 2 support
Date: Wed, 25 Aug 2004 13:25:49 +0200 [thread overview]
Message-ID: <412C773D.2040104@gmx.de> (raw)
In-Reply-To: <200408250102.i7P12Bp08783@mail019.syd.optusnet.com.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
chakkerz_dev@optusnet.com.au wrote:
|
| 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
I have no problem with the onboard ac'97 codec. Hopefully NVidea gets
their soundstorm driver into usable state. My Nforce2 runs nicely. Only
in PIC mode cat /proc/interrups gives a lot of error irq. In APIC
everything is fine.
Prakash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBLHc9xU2n/+9+t5gRAtCYAJ9yDjT4Fiaub63hXHhJ40dRj4Y+FgCfVZCF
XHqeBABaw3ca0jKyYuN/COk=
=dZCd
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-08-25 11:26 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
2004-08-25 3:44 ` Rodrigo F Baroni
2004-08-25 11:25 ` Prakash K. Cheemplavam [this message]
-- 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=412C773D.2040104@gmx.de \
--to=prakashkc@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.