Help... "unknow cpu type"

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

Okay, here goes. I had a k7t turbo 2 with a 1 gig duron CPU. I recently
picked up an athlon XP 2600 to replace the duron. It's the 266 MHz fsb
version, not the 333 MHz Barton. I'm sure you know the rest... the "unknow
cpu type error" seems a common problem from what I've been able to find, but
I can't seem to fix it.

I've updated to the latest bios (3.6), which is spposed to support the XP
2600 on the K7T turbo 2. The CPU worked, but the "unknow cpu type" showed at
start-up, and in also Windows system properties (I'm using Windows 98 SE).
The speed was detected at around 1 gigahertz (11xx... can't remember what
exactly). But it seemed to be working work fine at least. Of course it was
at the 100 MHz FSB setting, so I opened jumper J17.

Now when I boot up, I get the same "Unknow CPU Type" error but the speed is
detected at 1533 Mhz, which is still wrong. The multiplier setting in the
BIOS is set to "default". And now, the PC locks up now and then, when
visiting certain websites (ones that worked fine when the FSB was still set
as 100 MHz).

So what's going on? I've found from googling that people have had similar
problems, but the answer always seems to be "update the BIOS". Well, I've
updated the BIOS, and the VIA chipset drivers also. Anyone know what's wrong
or had the same problem?

Why can't it just detect the CPU correctly and use the right settings?

LH

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

"Luke Hooft" <nobodyliveshere@ozemail.com.au> wrote in message
news:OPEod.450$2j4.5608@nnrp1.ozemail.com.au...
> Okay, here goes. I had a k7t turbo 2 with a 1 gig duron CPU. I recently
> picked up an athlon XP 2600 to replace the duron. It's the 266 MHz fsb
> version, not the 333 MHz Barton. I'm sure you know the rest... the "unknow
> cpu type error" seems a common problem from what I've been able to find,
> but
> I can't seem to fix it.
>
> I've updated to the latest bios (3.6), which is spposed to support the XP
> 2600 on the K7T turbo 2. The CPU worked, but the "unknow cpu type" showed
> at
> start-up, and in also Windows system properties (I'm using Windows 98 SE).
> The speed was detected at around 1 gigahertz (11xx... can't remember what
> exactly). But it seemed to be working work fine at least. Of course it was
> at the 100 MHz FSB setting, so I opened jumper J17.
>
> Now when I boot up, I get the same "Unknow CPU Type" error but the speed
> is
> detected at 1533 Mhz, which is still wrong. The multiplier setting in the
> BIOS is set to "default". And now, the PC locks up now and then, when
> visiting certain websites (ones that worked fine when the FSB was still
> set
> as 100 MHz).
>
> So what's going on? I've found from googling that people have had similar
> problems, but the answer always seems to be "update the BIOS". Well, I've
> updated the BIOS, and the VIA chipset drivers also. Anyone know what's
> wrong
> or had the same problem?
>
> Why can't it just detect the CPU correctly and use the right settings?
>
> LH
>

My K7N2 Delta with a Barton 2800+ also shows Unknown CPU type despite
updating the BIOS etc.

The system works fine and gets all the settings correct, but it is annoying.

Boony

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

"Boony" <winpro@nospam.internode.on.net> wrote in message
news:41a39867$1@duster.adelaide.on.net...

> My K7N2 Delta with a Barton 2800+ also shows Unknown CPU type despite
> updating the BIOS etc.
>
> The system works fine and gets all the settings correct, but it is
annoying.

Well, mine isn't even getting the settings correct, which is doubly
annoying. I'll try to set thme manually I suppose. The multiplier should be
16, right (133 * 16 = 2.13 gig) but what should the voltage be? Fiddling
with the voltage makes me a little uneasy which is why I wish the thing
would detect properly and put the settings right by itself.

Oh yeah, I forgot to mention I have a 250 W power supply. I was told this
would be fine for an Athlon CPU but perhaps I should upgrade?

LH