Weird - Mobile XP with Desktop Part Number?

[tcsenter]

This is supposed to be a Desktop Athlon XP 2600+ Model 8 TBred (266FSB). AMD OPN is AXDA2600DKV3C. It POSTs as 'Unknown' CPU Type but WCPUID, AIDA32, and a couple other utilities report:

Mobile AMD Athlon XP-M (Model 8)
CPUID Revision 0681h
Extended CPUID Revision 0781h

I thought the OPN for Mobile XPs contained sequences like "AXMG" or "QQ4". What gives?

 

[tcsenter]

bumpity for the 2nd shift crew.

 

[nick1985]

dont worry, the mobiles are better anyway

OC that sucker!

 

[saechaka]

where did you buy it from?

 

[tcsenter]

Originally posted by: nick1985
dont worry, the mobiles are better anyway

OC that sucker!

Well, I can't disagree with that. Its that I seem to have a Mobile XP-M that does not officially exist. I have searched high and low but cannot find any reference for this OPN associated with a Mobile XP. Even the Desktop Replacement (standard power) XP-M uses a different OPN.

HELP!

 

[deadseasquirrel]

what mobo are you installing it inside? have you updated to the latest bios? does this mobo allow for Tbreds and above?

the OPN is definitely an OPN for a 2600 TbredB. the "C" denotes the 266fsb. and the "3" denotes the the L2 cache at 256k.

as for what wcpuid is saying, i dunno. a model 8 is a tbredB. (barton is a model 10). are you using the latest version of the software?

 

[tcsenter]

Yep, I've considered all that. My mainboard supports the XP2600+ and I've had a Tbred 2600+ installed before.

All those utilities are the latest versions, except perhaps AIDA32, which is version 3.88. I downloaded it about four months ago. But the rest I downloaded within the last three or four weeks.

 

[tcsenter]

Update:

Well my mystery gets more....mysterious. lol!

I had a SOYO K7VME (VIA KM400/VT8235) mainboard sitting around doing nothing, so I put it to work today. I wanted a 'second opinion', in a manner of speaking, on this processor. The K7VME supports the entire XP Desktop line up to 3000+ and 333FSB.

In the K7VME, the processor is reported at POST as "mobile AMD Athlon XP-M". The default multiplier used with the K7VME is now 11, instead of 12.5 that was used by the KM2M.

I noticed a couple things:

The CPU temps were unusually low, I mean like 36' C @ full load. My HSF is a $10 El-Cheapo, not high performance by any means.

Utilities such as SiSoft Sandra were reporting the 'spec' core voltage for this XP-M as 1.45v, but the K7VME was using 1.65v (so did the KM2M).

I suspected this processor was either operating below its rated speed, being over-volted, or both. Since I can't budge the multiplier without modifying something, on a hunch, I set the FSB jumper to 166/333, which I couldn't do on the KM2M.

Here are the results from H-Oda's WCPUID:

mobile AMD Athlon XP-M 2200+ @ 333FSB

I flogged the processor at this speed and temps only slightly increased - 100% stable. Seemed to be more FSB headroom, so I upped the FSB more.

The K7VME doesn't officially support 400FSB, but the BIOS has an overclock feature permitting 1MHz increases in FSB (no core voltage options) up to the next FSB base-line. I began upping the FSB in BIOS:

mobile AMD Athlon XP-M 2400+ @ 360FSB

Still running stable under load, temps have only increased a few degrees. Bump the FSB up again:

mobile AMD Athlon XP-M 2600+ @ 380FSB

Still stable under load, temps are now reaching 'typical' values for an Athlon XP, but still on the low end. The max I could get was 390FSB but the system would either freeze or wouldn't POST after rebooting.

I do not believe this was the processor, but was caused by my RAM being PC2700, or some of my PCI devices were balking at the higher PCI BUS. I have every belief this processor would hit 400MHz FSB if the rest of my system were up to it.

Still have no idea what is going on here. Maybe I'll send AMD a support request.