From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: Craig Bradney <cbradney@zip.com.au>
Cc: "Luis Miguel García" <ktech@wanadoo.es>,
david+challenge-response@blue-labs.org,
linux-kernel@vger.kernel.org, a.verweij@student.tudelft.nl
Subject: Re: [ACPI] acpi problem with nforce motherboards and ethernet
Date: Fri, 06 Feb 2004 10:26:18 +0100 [thread overview]
Message-ID: <40235DBA.4030408@gmx.de> (raw)
In-Reply-To: <1076029281.23586.36.camel@athlonxp.bradney.info>
Craig Bradney wrote:
> On Fri, 2004-02-06 at 01:58, Prakash K. Cheemplavam wrote:
>
>>>There is a way to "activate" cpu Disconnect? or it gets enabled by
>>>simply applying it?
>>
>>In newer Abit BIOSes there is an option, or you use athcool.
>>
>>
>>
>>>Yes, I have a Abit motherboards, perhaps it's the problem with the bios.
>>
>>I have an Abit NF7-S Rev2 with latest Bios.
>
>
> As noted in my last post.. you dont NEED athcool OR Disconnect to get
> stability..
>
> I've only ever run athcool to check the status.. and my BIOS doesnt have
> disconnect.
>
> A7N8X Deluxe V2 BIOS 1007.. 11 days uptime here.. haven had a crash
> since Ross released those patches ages ago.
WITHOUT Disconnect my System is stable, but hotter when idle, so that is
not the point. Ross wanted the patched to work with APIC and Disconnect.
DO you guys use APIC (not ACPI)? I use both APIC (and local APIC) and
ACPI. ACPI is not the problem (unless they break something...) but APIC
and CPU Disconnect makes trouble on nforce2.
Prakash
next prev parent reply other threads:[~2004-02-06 9:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 19:25 [ACPI] acpi problem with nforce motherboards and ethernet Luis Miguel García
2004-02-05 19:44 ` David Ford
2004-02-05 21:27 ` Luis Miguel García
2004-02-05 23:40 ` Andrew Morton
2004-02-06 0:08 ` Prakash K. Cheemplavam
2004-02-06 0:14 ` Craig Bradney
2004-02-06 0:22 ` Luis Miguel García
2004-02-06 0:38 ` Prakash K. Cheemplavam
2004-02-06 0:46 ` Luis Miguel García
2004-02-06 0:58 ` Prakash K. Cheemplavam
2004-02-06 1:01 ` Craig Bradney
2004-02-06 1:09 ` Luis Miguel García
2004-02-06 9:28 ` Prakash K. Cheemplavam
2004-02-06 9:26 ` Prakash K. Cheemplavam [this message]
2004-02-06 10:07 ` Craig Bradney
2004-02-06 10:40 ` Prakash K. Cheemplavam
2004-02-06 9:44 ` Daniel Drake
2004-02-06 11:04 ` Prakash K. Cheemplavam
2004-02-06 11:15 ` Prakash K. Cheemplavam
2004-02-06 12:51 ` Craig Bradney
2004-02-06 13:10 ` Arjen Verweij
2004-02-06 13:20 ` Prakash K. Cheemplavam
2004-02-06 13:34 ` Arjen Verweij
2004-02-06 13:41 ` Prakash K. Cheemplavam
2004-02-06 13:43 ` Prakash K. Cheemplavam
2004-02-06 11:08 ` Craig Bradney
2004-02-06 0:59 ` Craig Bradney
2004-02-06 0:56 ` Craig Bradney
2004-02-06 23:33 ` Maciej W. Rozycki
2004-02-07 2:50 ` Andi Kleen
2004-02-07 6:39 ` Josh McKinney
2004-02-07 10:04 ` Maciej W. Rozycki
2004-02-07 6:29 ` Luis Miguel García
2004-02-06 9:47 ` Daniel Drake
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 17:41 Luis Miguel García
2004-02-05 18:41 ` [ACPI] " Arjen Verweij
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=40235DBA.4030408@gmx.de \
--to=prakashkc@gmx.de \
--cc=a.verweij@student.tudelft.nl \
--cc=cbradney@zip.com.au \
--cc=david+challenge-response@blue-labs.org \
--cc=ktech@wanadoo.es \
--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