public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: victor <ixnay@infonegocio.com>
To: Luigi Genoni <kernel@Expansa.sns.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re[2]: K7/Athlon optimizations again. (The sacrifices worked??) (VIA KT133A chipset)
Date: Fri, 7 Sep 2001 01:55:08 +0200	[thread overview]
Message-ID: <2685246227.20010907015508@infonegocio.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109062352130.26515-100000@Expansa.sns.it>
In-Reply-To: <Pine.LNX.4.33.0109062352130.26515-100000@Expansa.sns.it>

Hello Luigi,

Friday, September 07, 2001, 12:01:50 AM, you wrote:

LG> On KT133A based MBs, I came trought at less 4 bios upgrades, and no
LG> problems at all. Usually I do not oveclock CPUs, so i keep 1.725 volts for
LG> vcore instead of 1.75, and system are just STABLE. In the reality setting
LG> 1.725 volts in the bios gives to my CPUs on abit MBs the right 1.75 volts,
LG> and setting 1.75 gives them 1.78/9. So I would suggest also to investigate
LG> if this light overvolt could be involved to create instabilities.
LG> I just made a test, and saw that on athlon 1.33 Ghz this volts diffecence
LG> creates a 5 degres difference when CPU is idle, and 7/8 when it is full
LG> loaded. And belive me, actually i am keeping thos CPU in a 18 degrees
LG> environment, using delta's fan to dissipate the eath.

look at this
http://bp6.gamesquad.net/Q6fix.phtml
i have a bp6 who has the same problem whit the dual celeron, and here
is the solution for it, looks your motherboard and see if its the same
problem, the celerons are fine whit this overvolt, they are prety
stable

its abit ... it cuold be ;)

LG> I know that a light overvolt should increase stability, and not generate
LG> instability, but maybe if CPUs and north bridge get too hot, (not
LG> so hot to destroy the HW, but anyway hotter in front of the optimal
LG> temperature), that could generate instability on loaded systems.

LG> just my 2 cents

LG> Luigi

-- 
Best regards,
 victor                            mailto:ixnay@infonegocio.com


  reply	other threads:[~2001-09-06 23:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-06 20:55 K7/Athlon optimizations again. (The sacrifices worked??) (VIA KT133A chipset) Nicholas Knight
2001-09-06 21:51 ` Gerbrand van der Zouw
2001-09-06 22:01 ` Luigi Genoni
2001-09-06 23:55   ` victor [this message]
2001-09-07  0:15 ` brian
2001-09-07  0:57 ` Jonathan Morton

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=2685246227.20010907015508@infonegocio.com \
    --to=ixnay@infonegocio.com \
    --cc=kernel@Expansa.sns.it \
    --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