Hey, Charlie here, Comp TIA A+ Certified, so I do know what I’m doing for the most part.
Trying to upgrade an Acer Aspire 3100 from a “AMD 3500+ mobile Sempron” CPU (SMS3500HAX4CM Keene) to an “AMD Turion 64 x2” CPU (TMRM72DAM22GG Lion) and it's not wanting to take. It won't even POST after the transplant. Looking at the hardware the Aspire 3100 has an ATI Radeon Xpress 1100 chipset (read right off the die), which according to the documentation at the ATI web site is 100% fully compatible with the new CPU's so long as the CPU's HyperTransport clock can go down to 1Ghz. So silicon compatibility does not seem to be the issue as far as I can tell. CPU-world.com also tells a similar story. The biggest thing, and the most likely to be the problem is that the socket in the Aspire 3100 is a S1g1 socket, and the new CPU's are made for S1g2 sockets. Also just as true but of much less concern, the new CPU has significantly faster clocks than the older one (Which, the clocks should be able to underclock just fine you would think) and a slightly lower voltage (voltages actually overlap). Other than these small issues I can see no difference that would prevent it from at least clearing POST with one of the new CPU's. Despite this assumption, after several attempts with two different new CPU's I have yet to get the unit to beep and then POST like a good lappy should. Only after I reinstall the Sempron does it clear POST once again.
I may be grasping at straws here, since I'm really tired (it's 4:30 AM). But the only explanation I have for this so far is that either (1) the stupid difference between socket S1g1 vs the S1g2 is all it takes to make it not work. Or (2) some REALLY stupid small thing that would normally not effect any real system is preventing this Acer POS from working right. Or (3) Acer has intentionally blocked the CPU ID's of better processors from being installed for marketing reasons.
Any constructive thoughts?
I made a small mistake. The one new CPU is certainly the "Lion" die for sure. However the other new CPU was actually a Turion 64 X2 TL-56, either a "Trinidad" or a "Tyler" die. Which according to Wikipidea both are 800Mhz Hyper Transport and S1g1 socket, just like the laptop. And of course it would not POST with that either, so it's most likely not the S1g2 socket issue. Since both the Tyler and Trinidad are S1g1 CPU's.
Edited by Charles86 - 12/9/11 at 11:21pm