From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Front side bus setting
Date: Tue, 12 Sep 2006 09:02:58 +0930 [thread overview]
Message-ID: <1158017578.8546.8.camel@orpheus> (raw)
In-Reply-To: <49bf44f10609110755v4cbaf9fcoeab7793ae8b11a73@mail.gmail.com>
On Mon, 2006-09-11 at 07:55 -0700, Grant wrote:
> The Dell motherboard detects the CPU's FSB and sets it that way. The
> board officially supports 66/100/133. My Celeron 700 runs at 66FSB,
> but I'd like to try 100FSB so my memory will run at full speed and I
> can see if the CPU can handle 1050 (10.5x multiplier).
aaahhh, I don't think you want to do this... My (perhaps limited)
understanding tells em that running a 66MHz chip at 100MHz blow it sky
high.
Although according to this web site[1] that's ok for celerons. I'd make
sure you have some pretty decent cooling though - ie. water cooling, or
move to Alaska.
If all you want to do is run the RAM faster, what you usually have is a
FSB to RAM multiplier (can't remember what it's called - my overclocking
days are long gone :) Which allows you to run the ram at 100 or 133...
> Does anyone know of a way to set the FSB in software?
Not me! My best recommendation would be to buy a really good
overclocking motherboard - one with all these features in the bios. You
should be able to get S370 mbs on ebay for cheap.
[1]
http://www.tomshardware.com/2000/07/28/intel_celeron_overclocking_guide/
HTH,
--
Iain Buchanan <iaindb at netspace dot net dot au>
The University of California Statistics Department; where mean is normal,
and deviation standard.
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-09-11 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 1:51 [gentoo-user] Front side bus setting Grant
2006-09-11 9:45 ` Mick
2006-09-11 14:55 ` Grant
2006-09-11 23:32 ` Iain Buchanan [this message]
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=1158017578.8546.8.camel@orpheus \
--to=iaindb@netspace.net.au \
--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