From: John Dee <antitux@antitux.net>
To: aviv bergman <bergmana@barak-online.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is nForce2 good choice under Linux?
Date: Fri, 13 Feb 2004 17:37:02 -0700 [thread overview]
Message-ID: <402D6DAE.7010905@antitux.net> (raw)
In-Reply-To: <200402132301.45324.bergmana@barak-online.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have a shuttle FN41G2. It works well for my needs.
have an extra ethernet card handy, though, because without the forcedeth
patch, you won't have ethernet.
aviv bergman wrote:
| On Friday 13 February 2004 22:32, Daniel Drake wrote:
|
|>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.
|
|
| the shuttle FN41 (sn41g2 xpc) is probably safe - i had very frequent
lockups
| after upgrading to 2.6.0, flashed to the latest bios, and the system
is rock
| stable since (2.6.1 w/apic)
|
| you better check if the specific board you are going to buy has a
fixed bios.
|
| aviv
| -
| 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/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFALW2thf6hBevzxKARAoofAJwInRCuqxdCu0567X2PVonTjeMzMwCeOfBJ
wuyv2bXTbFw2DISWiiSSGZQ=
=1RaN
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-02-14 0:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 20:10 is nForce2 good choice under Linux? 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 [this message]
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=402D6DAE.7010905@antitux.net \
--to=antitux@antitux.net \
--cc=bergmana@barak-online.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