public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Overclocking CPU causes segmentation fault
Date: Tue, 22 Jan 2013 11:43:01 +0200	[thread overview]
Message-ID: <kdlmvp$rce$1@ger.gmane.org> (raw)
In-Reply-To: <50FE429A.8060708@nileshgr.com>

On 22/01/13 09:41, Nilesh Govindrajan wrote:
> So I have this old E2180 processor and no money as of now to buy a new
> rig :P
> I'm trying to overclock my CPU using BIOS host clock control and
> everything is fine at 2.6 Ghz up to bootloader.
>
> Kernel segfaults. Any idea why? I'm running pf-kernel 3.7.2 and it
> doesn't work with vanilla kernel either.
>
> Intel MCE is disabled in kernel configuration.

When you raise the "host clock", which is the FSB, you are also raising 
the frequency of your RAM.  So make sure you select a lower FSB:DRAM 
ratio in your BIOS.  To begin with, set it to 1:1.

Also, if you only have the stock CPU cooler that came with it, you won't 
be able to actually get a stable overclock.  Your CPU's stock frequency 
is 2GHz.  Without a better cooler, you might get it to 2.2 or 2.3 maybe. 
  But 2.6?  That's pretty optimistic.  I don't think it'll work in the 
long run, unless you happen to have picked a good chip that can be 
overclocked without raising the VCore.

But first, solve the RAM problem by lowering the FSB:DRAM ratio.



  parent reply	other threads:[~2013-01-22  9:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22  7:41 [gentoo-user] Overclocking CPU causes segmentation fault Nilesh Govindrajan
2013-01-22  9:16 ` Helmut Jarausch
2013-01-22  9:43 ` Nikos Chantziaras [this message]
2013-01-22 11:14   ` [gentoo-user] " Nilesh Govindrajan
2013-01-22 11:43     ` Nikos Chantziaras
2013-01-22 11:46       ` Nilesh Govindrajan
2013-01-22 13:49         ` Nilesh Govindrajan
2013-01-22 18:35 ` [gentoo-user] " Volker Armin Hemmann
2013-01-22 18:45   ` Nilesh Govindrajan
2013-01-23  1:55     ` Dale
2013-01-23  8:21       ` [gentoo-user] " Nikos Chantziaras
2013-01-23 12:09         ` Dale
2013-01-23 14:22           ` Nikos Chantziaras
2013-01-23 15:09             ` Nilesh Govindrajan
2013-01-23 15:35               ` Nikos Chantziaras
2013-01-23 16:22                 ` Bruce Hill
2013-01-23 16:32                   ` Nikos Chantziaras
2013-01-23 17:16                 ` Volker Armin Hemmann
2013-01-23 17:21                   ` Michael Mol
2013-01-23 18:46                   ` Nikos Chantziaras
2013-01-23 17:13         ` Volker Armin Hemmann
2013-01-23 18:52           ` Nikos Chantziaras
2013-01-24  2:23       ` [gentoo-user] " Peter Humphrey
2013-01-24  4:08         ` Dale

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='kdlmvp$rce$1@ger.gmane.org' \
    --to=realnc@gmail.com \
    --cc=gentoo-user@lists.gentoo.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