24 Jul
2004
24 Jul
'04
3:32 p.m.
Ryan Underwood schrieb:
On Sat, Jul 24, 2004 at 11:33:07AM -0400, Matthew
Barber wrote:
ouch yeah I already knew it is a bad idea .. that wasn't really meant as
a recommendation. I might even have killed my old MB that way (didn't
have any use for it anyway ... so it wasn't a big loss :))
generally wants to run at about 33Mhz (unless you
have a very new board
with PCI-X or some such), and AGP at 66Mhz, and these values will
generally be a fraction of the fsb. So if your fsb is 66Mhz, PCI will
be 1/2FSB. If it's 100Mhz, PCI will be 1/3. Setting it to 75Mhz may
cause it to still be in the 66Mhz realm as far as the division is
concerned, and set PCI to around 38Mhz, which may cause a lot of
problems.
<>
Yes, one thing this used to do was to cause data corruption on certain
Maxtor hard drives, at least under windows. I think in linux, you can
pass a idebus= option to the kernel to tell it that the bus is
overclocked.
Also, even when the PCI bus is run asynchronously, while the data
corruption issues aren't around anymore, there is unfortunately a
latency tradeoff, which may make using a 75MHz/83MHz FSB not even worth
it in the end.