From: Grzegorz Kulewski <kangur@polcom.net>
To: Daniel Drake <dan@reactivated.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is nForce2 good choice under Linux?
Date: Fri, 13 Feb 2004 22:24:40 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.58.0402132205510.31906@alpha.polcom.net> (raw)
In-Reply-To: <402D3448.7080105@reactivated.net>
Thanks for your fast response!
> I haven't tried the SATA or firewire capabilities of my board, but I believe
> both work. Everything else (sound, network, ...) works OK.
Is anybody using these features? I am thinking about connecting two 120GB
WD SATA drives (raid) to improve performance and seek times. But I have to
know if SATA controller works under Linux... (i think it is Silicon Image
controller or something like that...) Is TCQ supported on these
controllers? Or it depends on disks being used?
> Apparently, nvidia are working on new (binary) drivers for nforce-audio which
> will do hardware mixing and the likes.
Hope it will work with ALSA...
> Yes, there is a problem. This is a hardware problem, which can likely be fixed
> in a BIOS update. Those who have tried contacting manufacturers have basically
> failed.
> There is a bug relating to the C1 disconnect feature of AMD CPU's. It causes a
> total system freeze. There is some quite detailed info on this in recent
> threads, search the archive if you are interested.
>
> For the majority of people (as I understand it), these lockups can be totally
> avoided by *not* using APIC/IOAPIC. I never met a lockup until I enabled APIC
> for the first time. The older XTPIC paths are generally not fast enough to
> trigger the C1 bug. Ross Dickson has done some great work here, and he has
> produced patches which workaround this particular bug. His last two revisions
> of patches have worked great for me (and others), not a lockup since.
You mean that kernel 2.6-mm with this patch with APIC and ACPI enabled
works OK? Is this patch a complete fix or a workaround?
Btw. Is CPU frequency scaling supported on this board (with ACPI)? What
about other power saving technologies?
> I have been perfectly happy with my NF7-S, except from the one time it failed
> on me (didn't boot up), and I had to get it replaced. I think there is a
> general risk involved in buying nforce2 boards, their rate of failure is
> fairly high. Still, the benefits are nice.
Wow! This fringtens me! What do you mean? Why are they so failure-able?
Are they worse than other new boards in it? Are they, at least, easily,
fast and free replaced (under warranty)?
Thanks again!
Grzegorz Kulewski
next prev parent reply other threads:[~2004-02-13 21:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 20:10 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 [this message]
2004-02-13 22:05 ` Daniel Drake
2004-02-13 22:12 ` Jesse Allen
[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=Pine.LNX.4.58.0402132205510.31906@alpha.polcom.net \
--to=kangur@polcom.net \
--cc=dan@reactivated.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
all inboxes | Powered by JetHome®