From: Grzegorz Kulewski <kangur@polcom.net>
To: linux-kernel@vger.kernel.org
Subject: is nForce2 good choice under Linux?
Date: Fri, 13 Feb 2004 21:10:36 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.58.0402132048330.31906@alpha.polcom.net> (raw)
Hi,
I am recently considering buying Abit AN7 motherboard with NVIDIA nForce2
Ultra 400 with MCP-T bridge. But I found some posts on the Internet that
states there are some problems with nForce2 chipsets under Linux.
So my questions:
1. What is the status of nForce2 support under Linux? What works what not?
2. Are the drivers binary or source or open source? Are the drivers in
mainline kernels or do I need a patch?
3. Are there any problems with this chipset? Are the problems hardware
based or soft based (= will/can be fixed)? Are ACPI, APIC, IRQ and so on
working OK?
4. Are there any workarounds in the kernel for hardware bugs? Do they
affect performance/stability?
5. Should I choose other mainboard? Why? Which?
6. Any comments from people which use this mainboard/chipsets under Linux?
I am mainly interested in 2.6 kernels, if it does change anything.
thanks in advance and sorry for my english
Grzegorz Kulewski
next reply other threads:[~2004-02-13 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 20:10 Grzegorz Kulewski [this message]
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
[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.0402132048330.31906@alpha.polcom.net \
--to=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
all inboxes | Powered by JetHome®