public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dan@reactivated.net>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is nForce2 good choice under Linux?
Date: Fri, 13 Feb 2004 22:05:12 +0000	[thread overview]
Message-ID: <402D4A18.5090708@reactivated.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0402132205510.31906@alpha.polcom.net>

Hi,

Grzegorz Kulewski wrote:
> 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?
Yep, it works fine. The patch is a workaround, I think it disables going into 
C1 disconnect state too early, and refuses to go into C1 disconnect state when 
  we know we will reconnect right afterwards. I'm not too sure on the details 
here, check Ross Dicksons previous posts for clarification.

>>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)?

Before I bought this board, I was doing some reading up, as you do. I found 
quite a few cases of people having problems (DOA, bootup trouble, bios not 
saving settings on reboots, etc.). The general word going around at the time 
was that the boards were great, but failures and problems were quite common. 
This was quite a while ago (June-July 2003) so you might want to check around 
for newer opinions. You will probably also discover the word going around 
about the very first AN7s, involving gashes in the board to fix late bugs, and 
hand soldered components.

As for getting replacements, yes, I got a replacement with my supplier, even 
though they said they wouldn't guarantee any returns after 3 months. After I 
purchased the board I discovered that the Abit UK offices are very near me, 
and when I approached them to get it repaired, they refused - they will only 
repair boards that came directly from them. So, check with your supplier 
before you buy, because you probably wont have any luck with Abit directly.

Daniel

  reply	other threads:[~2004-02-13 22:05 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
2004-02-13 21:24   ` Grzegorz Kulewski
2004-02-13 22:05     ` Daniel Drake [this message]
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=402D4A18.5090708@reactivated.net \
    --to=dan@reactivated.net \
    --cc=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