[TriLUG] More speed problems (Athlon XP 2200+)

[Jason Tower]

most motherboards have multiplier settings in the bios that may or may not be 
automatically set for all CPUs.  try setting things to autodetect or whatever 
first.

it is also possible that the multiplier is correct but the base frequency is 
not.  in your case, if the bus speed is set to 200mhz instead of 266 mhz, 
that will essentially underclock your CPU.  some boards set bus speed in the 
bios, some use jumpers.

i just bought a MSI K7T turbo board (KT133A chipset) that had the default 
jumper set to a 266mhz bus speed.  so when i stuck in my duron 1000, which 
uses a 200mhz bus speed, it showed up as a duron 1300.  but only for a few 
seconds, after which it would crash or lock up.  setting the board jumper to 
the slower 200mhz speed cleared everything up.  sounds like you have the 
opposite problem.

jason

On Thursday 17 October 2002 12:03, Andrew Perrin wrote:
> Well, I received the replacement motherboard from my earlier question
> (about the XP 2200+ that was seen as a 1500+). I popped it in, moved the
> CPU over, and in the process while the heatsink was off I read the ID on
> the chip itself and confirmed it was a 2200+.
>
> BUT... it still is being seen as a 1500+. It's not strictly a linux/kernel
> issue, because on bootup the BIOS reports it as a 1500+, so something's
> screwy elsewhere. Can someone with more hardware experience point me
> toward what I should try next?
>
> The motherboard is a Gigabyte GA-7VAX which is supposed to be able to
> handle a 2200+ and above.
>
> Thanks-
> ap
>
> ----------------------------------------------------------------------
> Andrew J Perrin - http://www.unc.edu/~aperrin
> Assistant Professor of Sociology, U of North Carolina, Chapel Hill
> clists at perrin.socsci.unc.edu * andrew_perrin (at) unc.edu
>
>
> _______________________________________________
> TriLUG mailing list
>     http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ:
>     http://www.trilug.org/~lovelace/faq/TriLUG-faq.html