Unlocked Hard-Locked AXPs? It may be possible...
<b>Read the intro and scroll to edit part two:</b>
It seems that mobile AXPs are free from clock hardlocks. Overclockers.ru theorizes that the multiplier table is sent to the L5 before being sent to all the places overclockers have traditionally been able to unlock their chips at.
It seems that by connecting the certain L5 bridges not only controls SMP/multi-lock, but also prevents the CPU multiplier lock to be transmitted throughout the CPU; which stops US. And when the chip is tricked into going mobile, the multi is free for change!
Rotating the table above 90* CCW, we have the real bridges:
Can't hurt to try it guys.
Yes, I know that there are 5 bridges on the AXP and 4 in the diagram. I assume that it would be like this:
L6> . | | : | :
But you should also try:
L6> . : | | : |
To be sure.
If any of you have a Barton 2500, pull it and look at it: Is the last L6 closed, or second to last? That will tell us which four bridges are being shown in the table.
//EDIT:
There seems to be also some information discrepencies.
The L5 is listed in the table, the L6 is shown on the CPU picture.
We all know that the last L5 is the mod for SMP.. A ton of us have done it.
I need muddockter to tell us the status of his L5 bridges also, that could help us correlate the information into english (It's all currently russian).
I believe in the end that it was probably a mistake in OC.ru's picture, and we need to look at the L5.
//EDIT PART TWO:
The L5 controls the state of single CPU, SMP, or mobile.
L5> . | | : | <--- Mobile L5 state.
The L6 Controls the multipliers for a mobile athlon:
You can HARDCODE a multi, but it might be unnecessary. Here's an L6 table:
<DIV style="margin-right: 5px" class="left"><TABLE summary="mul1" class="data" width="270" border="1" cellspacing="0" cellpadding="3"><COL span="1" align="right"><COL span="3" align="center"><TR class="cap"><TD>Multiplier</TD><TD>Clock<BR>(FSB100)</TD><TD>L6-FID[4:0]</TD><TD>Model#</TD></TR><TR><TD> 5.0x</TD><TD> 500M</TD><TD>CC:CC</TD><TD> - </TD></TR>
<TR><TD> 5.5x</TD><TD> 550M</TD><TD>CC:C:</TD><TD> - </TD></TR>
<TR><TD> 6.0x</TD><TD> 600M</TD><TD>CC::C</TD><TD> - </TD></TR>
<TR><TD> 6.5x</TD><TD> 650M</TD><TD>CC:::</TD><TD> - </TD></TR>
<TR><TD> 7.0x</TD><TD> 700M</TD><TD>C:CCC</TD><TD> - </TD></TR>
<TR><TD> 7.5x</TD><TD> 750M</TD><TD>C:CC:</TD><TD> - </TD></TR>
<TR><TD> 8.0x</TD><TD> 800M</TD><TD>C:C:C</TD><TD> - </TD></TR>
<TR><TD> 8.5x</TD><TD> 850M</TD><TD>C:C::</TD><TD> - </TD></TR>
<TR><TD> 9.0x</TD><TD> 900M</TD><TD>C::CC</TD><TD> - </TD></TR>
<TR><TD> 9.5x</TD><TD> 950M</TD><TD>C::C:</TD><TD> - </TD></TR>
<TR><TD>10.0x</TD><TD> 1.0G</TD><TD>C:::C</TD><TD> - </TD></TR>
<TR><TD>10.5x</TD><TD>1.05G</TD><TD>C::::</TD><TD> - </TD></TR>
<TR><TD>11.0x</TD><TD>1.10G</TD><TD>CCCCC</TD><TD> - </TD></TR>
<TR><TD>11.5x</TD><TD>1.15G</TD><TD>CCCC:</TD><TD> - </TD></TR>
<TR><TD>12.0x</TD><TD>1.20G</TD><TD>CCC:C</TD><TD>1400FQQ3B</TD></TR><TR><TD>12.5x</TD><TD>1.25G</TD><TD>CCC::</TD><TD> - </TD></TR></TABLE></DIV>
<TABLE summary="mul2" class="data" width="270" border="1" cellspacing="0" cellpadding="3"><COL span="1" align="right"><COL span="3" align="center">
<TR class="cap"><TD>Multiplier</TD><TD>Clock<BR>(FSB100)</TD><TD>L6-FID[4:0]</TD><TD>Model#</TD></TR><TR><TD>13.0x</TD><TD>1.30G</TD><TD>:C:CC</TD><TD>1500FQQ3B</TD></TR><TR><TD>13.5x</TD><TD>1.35G</TD><TD>:C:C:</TD><TD> - </TD></TR>
<TR><TD>14.0x</TD><TD>1.40G</TD><TD>:C::C</TD><TD>1600FQQ3B</TD></TR>
<TR><TD class="text-yel">21.0x</TD><TD> - </TD><TD>:C:::</TD><TD> - </TD></TR>
<TR><TD>15.0x</TD><TD>1.50G</TD><TD>::CCC</TD><TD> - </TD></TR>
<TR><TD class="text-yel">22.0x</TD><TD> - </TD><TD>::CC:</TD><TD> - </TD></TR>
<TR><TD>16.0x</TD><TD>1.60G</TD><TD>::C:C</TD><TD> - </TD></TR>
<TR><TD>16.5x</TD><TD>1.65G</TD><TD>::C::</TD><TD> - </TD></TR>
<TR><TD>17.0x</TD><TD>1.70G</TD><TD>:::CC</TD><TD> - </TD></TR>
<TR><TD>18.0x</TD><TD>1.80G</TD><TD>:::C:</TD><TD> - </TD></TR>
<TR><TD class="text-yel">23.0x</TD><TD> - </TD><TD>::::C</TD><TD> - </TD></TR>
<TR><TD class="text-yel">24.0x</TD><TD> - </TD><TD>:::::</TD><TD> - </TD></TR>
<TR><TD> 3.0x</TD><TD> - </TD><TD>:CCCC</TD><TD> - </TD></TR>
<TR><TD class="text-yel">19.0x</TD><TD> - </TD><TD>:CCC:</TD><TD> - </TD></TR>
<TR><TD> 4.0x</TD><TD> - </TD><TD>:CC:C</TD><TD> - </TD></TR>
<TR><TD class="text-yel">20.0x</TD><TD> - </TD><TD>:CC::</TD><TD> - </TD></TR>
</TABLE><BR>
<P class="new"><B>C</B> = Closed , <B>:</B> = Open </P>
<b>THAT SAID</b>.. Making the chip a mobile might be enough for the 5Bit FID override or any l3/pin mod to work once more.
So to recap:
L6 controls mobile multis.
L5 might be in charge of multi hardlock.
Muddockter needs to look at his mobile Barton and tell us which bridges are connected on the L5.
It seems that mobile AXPs are free from clock hardlocks. Overclockers.ru theorizes that the multiplier table is sent to the L5 before being sent to all the places overclockers have traditionally been able to unlock their chips at.
It seems that by connecting the certain L5 bridges not only controls SMP/multi-lock, but also prevents the CPU multiplier lock to be transmitted throughout the CPU; which stops US. And when the chip is tricked into going mobile, the multi is free for change!
Rotating the table above 90* CCW, we have the real bridges:
Can't hurt to try it guys.
Yes, I know that there are 5 bridges on the AXP and 4 in the diagram. I assume that it would be like this:
L6> . | | : | :
But you should also try:
L6> . : | | : |
To be sure.
If any of you have a Barton 2500, pull it and look at it: Is the last L6 closed, or second to last? That will tell us which four bridges are being shown in the table.
//EDIT:
There seems to be also some information discrepencies.
The L5 is listed in the table, the L6 is shown on the CPU picture.
We all know that the last L5 is the mod for SMP.. A ton of us have done it.
I need muddockter to tell us the status of his L5 bridges also, that could help us correlate the information into english (It's all currently russian).
I believe in the end that it was probably a mistake in OC.ru's picture, and we need to look at the L5.
//EDIT PART TWO:
The L5 controls the state of single CPU, SMP, or mobile.
L5> . | | : | <--- Mobile L5 state.
The L6 Controls the multipliers for a mobile athlon:
You can HARDCODE a multi, but it might be unnecessary. Here's an L6 table:
<DIV style="margin-right: 5px" class="left"><TABLE summary="mul1" class="data" width="270" border="1" cellspacing="0" cellpadding="3"><COL span="1" align="right"><COL span="3" align="center"><TR class="cap"><TD>Multiplier</TD><TD>Clock<BR>(FSB100)</TD><TD>L6-FID[4:0]</TD><TD>Model#</TD></TR><TR><TD> 5.0x</TD><TD> 500M</TD><TD>CC:CC</TD><TD> - </TD></TR>
<TR><TD> 5.5x</TD><TD> 550M</TD><TD>CC:C:</TD><TD> - </TD></TR>
<TR><TD> 6.0x</TD><TD> 600M</TD><TD>CC::C</TD><TD> - </TD></TR>
<TR><TD> 6.5x</TD><TD> 650M</TD><TD>CC:::</TD><TD> - </TD></TR>
<TR><TD> 7.0x</TD><TD> 700M</TD><TD>C:CCC</TD><TD> - </TD></TR>
<TR><TD> 7.5x</TD><TD> 750M</TD><TD>C:CC:</TD><TD> - </TD></TR>
<TR><TD> 8.0x</TD><TD> 800M</TD><TD>C:C:C</TD><TD> - </TD></TR>
<TR><TD> 8.5x</TD><TD> 850M</TD><TD>C:C::</TD><TD> - </TD></TR>
<TR><TD> 9.0x</TD><TD> 900M</TD><TD>C::CC</TD><TD> - </TD></TR>
<TR><TD> 9.5x</TD><TD> 950M</TD><TD>C::C:</TD><TD> - </TD></TR>
<TR><TD>10.0x</TD><TD> 1.0G</TD><TD>C:::C</TD><TD> - </TD></TR>
<TR><TD>10.5x</TD><TD>1.05G</TD><TD>C::::</TD><TD> - </TD></TR>
<TR><TD>11.0x</TD><TD>1.10G</TD><TD>CCCCC</TD><TD> - </TD></TR>
<TR><TD>11.5x</TD><TD>1.15G</TD><TD>CCCC:</TD><TD> - </TD></TR>
<TR><TD>12.0x</TD><TD>1.20G</TD><TD>CCC:C</TD><TD>1400FQQ3B</TD></TR><TR><TD>12.5x</TD><TD>1.25G</TD><TD>CCC::</TD><TD> - </TD></TR></TABLE></DIV>
<TABLE summary="mul2" class="data" width="270" border="1" cellspacing="0" cellpadding="3"><COL span="1" align="right"><COL span="3" align="center">
<TR class="cap"><TD>Multiplier</TD><TD>Clock<BR>(FSB100)</TD><TD>L6-FID[4:0]</TD><TD>Model#</TD></TR><TR><TD>13.0x</TD><TD>1.30G</TD><TD>:C:CC</TD><TD>1500FQQ3B</TD></TR><TR><TD>13.5x</TD><TD>1.35G</TD><TD>:C:C:</TD><TD> - </TD></TR>
<TR><TD>14.0x</TD><TD>1.40G</TD><TD>:C::C</TD><TD>1600FQQ3B</TD></TR>
<TR><TD class="text-yel">21.0x</TD><TD> - </TD><TD>:C:::</TD><TD> - </TD></TR>
<TR><TD>15.0x</TD><TD>1.50G</TD><TD>::CCC</TD><TD> - </TD></TR>
<TR><TD class="text-yel">22.0x</TD><TD> - </TD><TD>::CC:</TD><TD> - </TD></TR>
<TR><TD>16.0x</TD><TD>1.60G</TD><TD>::C:C</TD><TD> - </TD></TR>
<TR><TD>16.5x</TD><TD>1.65G</TD><TD>::C::</TD><TD> - </TD></TR>
<TR><TD>17.0x</TD><TD>1.70G</TD><TD>:::CC</TD><TD> - </TD></TR>
<TR><TD>18.0x</TD><TD>1.80G</TD><TD>:::C:</TD><TD> - </TD></TR>
<TR><TD class="text-yel">23.0x</TD><TD> - </TD><TD>::::C</TD><TD> - </TD></TR>
<TR><TD class="text-yel">24.0x</TD><TD> - </TD><TD>:::::</TD><TD> - </TD></TR>
<TR><TD> 3.0x</TD><TD> - </TD><TD>:CCCC</TD><TD> - </TD></TR>
<TR><TD class="text-yel">19.0x</TD><TD> - </TD><TD>:CCC:</TD><TD> - </TD></TR>
<TR><TD> 4.0x</TD><TD> - </TD><TD>:CC:C</TD><TD> - </TD></TR>
<TR><TD class="text-yel">20.0x</TD><TD> - </TD><TD>:CC::</TD><TD> - </TD></TR>
</TABLE><BR>
<P class="new"><B>C</B> = Closed , <B>:</B> = Open </P>
<b>THAT SAID</b>.. Making the chip a mobile might be enough for the 5Bit FID override or any l3/pin mod to work once more.
So to recap:
L6 controls mobile multis.
L5 might be in charge of multi hardlock.
Muddockter needs to look at his mobile Barton and tell us which bridges are connected on the L5.
0
Comments
l5 > | : | |
WOOT.
//EDIT:
Does the mobile 2400 feature the same speeds as the desktop Athlon XP?
//EDIT 2:
Nevermind that.
Someone want to take one of their locked chips and lock bridges according to the picture there?
I think the L6 is irrelevant here unless people want to hardcode a multi.
Trev
Is it new packaging like you see in the pic of Mud's mobile, or old which is smooth?
No... the 2400+ runs at 1.80ghz and has a FSB of 266...here are all the mobile speeds I know of
Athlon XP-M 2500+ 1.87 266fsb 512k
Athlon XP-M 2400+ 1.80 266fsb 512k
Athlon XP-M 2200+ 1.80 266fsb 256k
Athlon XP-M 2000+ 1.67 266fsb 256k
Athlon XP-M 1700+ 1.47 266fsb 256k
my 2400+m booted at 6x133...but all multis r unlocked
Trev
Trev
The real contacts are the dark spots just in between the gold ones; you have to VERY VERY GENTLY scrape the packaging away to reveal those contacts, THEN seal the pit, then connect them.
//EDIT:
Realized the L6 table is correct too.
Looks like we have all the facts we need.
You might be on to something here, Thrax. :thumbup
(Side note here) They have me set up next to the sat equipment out here and I tied into the 24 port switch on it so I have some communications, at least at night. :woowoo:
Q: I left the FSB and cache mods intact, should I remove them and try again?
I have this mod confirmed now on several tbreds by someone who can read the russian at overclockers.ru.
I was hoping not to redo all my mods but I guess I'll have to...
Oh well, anything in the name of OC'ing but not until tomorrow...
I read a few threads over at overclockers.com of late made Tbreds being locked also. I think they were made sometimes in the week 40-42 range.
There's a littany of locked editions over at a forum which is keeping track of those locked; I'll have to remember where I saw it.
ok, more testing tomorrow then.
Trev
Deleted all mods, started from scratch on the L5's but the chip won't boot.
I'll put it back to its original state and live with it...