G
Guest
Guest
Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)
Hi,
I have a KT6V motherboard (model number MSI-7021, I believe), which
has a Via KT600 chipset. I recently got hold of an Athlon XP Mobile
2400+ Barton core. This cpu has a native 13.5 multiplier, and is meant
to run on a 133 MHz bus.
From what I have read, all mobile XPs are multiplier unlocked from the
factory, without exception. However, with my motherboard, changing the
multiplier in the bios has no effect. I've upgraded to the latest
bios, and still no dice. I can overlock the processor by upping the
FSB, but I'd obviously have more options if I could adjust the
multiplier as well.
Is this something that can't be overcome, maybe having to do with the
"5th multiplier bit" I saw referenced while searching the web?
Something to do with the processor having a native multiplier of over
13x and the KT600 being too old a chipset to deal with that?
I know this is probably obvious to many of you, but I have been out of
the hardware loop for quite a while, and haven't really found a
definitive answer in my searching, so I'd appreciate any advice.
Hi,
I have a KT6V motherboard (model number MSI-7021, I believe), which
has a Via KT600 chipset. I recently got hold of an Athlon XP Mobile
2400+ Barton core. This cpu has a native 13.5 multiplier, and is meant
to run on a 133 MHz bus.
From what I have read, all mobile XPs are multiplier unlocked from the
factory, without exception. However, with my motherboard, changing the
multiplier in the bios has no effect. I've upgraded to the latest
bios, and still no dice. I can overlock the processor by upping the
FSB, but I'd obviously have more options if I could adjust the
multiplier as well.
Is this something that can't be overcome, maybe having to do with the
"5th multiplier bit" I saw referenced while searching the web?
Something to do with the processor having a native multiplier of over
13x and the KT600 being too old a chipset to deal with that?
I know this is probably obvious to many of you, but I have been out of
the hardware loop for quite a while, and haven't really found a
definitive answer in my searching, so I'd appreciate any advice.