public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: a.verweij@student.tudelft.nl
Cc: "Craig Bradney" <cbradney@zip.com.au>,
	"Daniel Drake" <dan@reactivated.net>,
	"Luis Miguel García" <ktech@wanadoo.es>,
	david+challenge-response@blue-labs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [ACPI] acpi problem with nforce motherboards and ethernet
Date: Fri, 06 Feb 2004 14:41:34 +0100	[thread overview]
Message-ID: <4023998E.9040404@gmx.de> (raw)
In-Reply-To: <Pine.GHP.4.44.0402061433510.7943-100000@elektron.its.tudelft.nl>

Arjen Verweij wrote:
 > It would probably be more useful if I included the URL as well duh... 
(thx
 > Craig)
 >
 > http://atlas.et.tudelft.nl/verwei90/nforce2/
 > http://atlas.et.tudelft.nl/verwei90/nforce2/index.html

     * 3.2 Turning off the CPU bus disconnect in the BIOS? (verify) 
(drawback: causes cpu to run significantly hotter)

Inprecice: CPU runs as hot as without disconnect, only without load, cpu 
disconnect lets the cpu cool down.

With athcool you can alsao turn it off, or there is a quirk-patch 
available from Bart.

     * 3.3 Apply patches cooked up by Ross Dickson, possibly in 
conjunction with 3.2? (verify)
           o 3.3.1 Seems to work for Craig Bradney (hardware unknown, 
some Asus board?) and Prakash K. Cheemplavam (Abit NF7-S)

I have Rev2 (2.0) board and d22 (or 2.2 ? Abit has a strange way of 
numbering.) Bios. I only applied first patch. I already use an 
equivalent to the second one.

Prakash

  reply	other threads:[~2004-02-06 13:41 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
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 [this message]
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=4023998E.9040404@gmx.de \
    --to=prakashkc@gmx.de \
    --cc=a.verweij@student.tudelft.nl \
    --cc=cbradney@zip.com.au \
    --cc=dan@reactivated.net \
    --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