But lets say that we get a working solution that by using hardware JTAG-programmers, you can unlock a cpu. Then what? Would we all build those devies or would we send our cpu:s across the world to be unlocked?
Would AMD try to shoot us all?
Printable View
But lets say that we get a working solution that by using hardware JTAG-programmers, you can unlock a cpu. Then what? Would we all build those devies or would we send our cpu:s across the world to be unlocked?
Would AMD try to shoot us all?
Hey there Warship!
Looks like u've got kinda nice ideas.
But some say that it's impossible to tamper with the registers.
Maybe in a little while we see cpu flashing tools written by warship who worships warships!
Go on. Any other ideas?
BTW no pin mod possible with venice?
I that case AMD tries to hang us. Then we will become Extreme Overclockers.
Mehran: Well, as I see it there are 2 possible ways AMD could have made it "impossible" to change the values.
1. They fried the JTAG-port before they shipped the CPU.
2. They have specced some registers as read-onyl, which would mean that they won't let us tamper with some registers individually, HOWEVER, in that case, I think there's a big chance we'll be able to flash ALL registers at the same time, instead of just fiddling with MAX_MULTI on it's own.
So my hope now stands to Tin-EOF, so we can see wether the JTAG-interface on the cpus is in order or not.
You won't be able to flash the CPU in a mainboard where the CPU is operating as the main CPU.Quote:
Originally Posted by Mehran
As for the actual procedure, the main problem is fiding out which register contains the setting you want to change.
That is probably most easily done by diffing a complete register dump from a 3200+ and a 3000+ which should be almost identical except for the max multiplier, and other sections that you should be able to identify by their memory contents in a hexdump.
I don't think AMD has an legal basis to prevent anybody from doing so, if you legally bought both CPUs you can do whatever the heck you want with them.
Your right. It's maybe possible to flash all registers.Quote:
Originally Posted by Warship
And about the first one, I don't think thats true. I mean I just don't think thats true. At least some CPUs I think are the same as each other. like in 6800nu and le. They r the same just diffrent in pipelines and speeds.
Or lets say about those duron processors with a disabled cache. U can easily open the fried cache and use it as a regular Athlon XP.
So, u maybe run a 3000 at x10 and use it just as a 3200.
What do u say?
BTW some kinda irrelevant thing! It's just a question and it's not the right place to ask. Does super Pi run faster on Intel machines?
A guy sent me a screenshot of it runnig it on an Intel machine (3.2GHz LGA775 1MB L2) and it finnished 1M calculation within 17 seconds! :eek: AND without overclocking!
I can hardly finish it under 30s even with overclocking.
Why is that?
Yeah u r actually right.Quote:
Originally Posted by Martin Cracauer
But I have a question here.
How does programs like CBI and CPUID change cpu string?
For example from AMD Athlon(tm)...... to ABC team?!
They operate while the CPU is on the board.
This guy smokes a lot :rolleyes:Quote:
Originally Posted by Mehran
Cheating on SuperPI makes baby Jeebus cry. He's a fake lamer, kill it!Quote:
Originally Posted by Mehran
Seriously, though, I think you guys are great. I hope, when I've got enough money, I can unlock my new 3800+ CPU with the excellent guide you most certainly will produce. :)
Goddamnit, are we going to start this discussion all over again?
Warship and others: READ THE TOPIC!
We've been all over this.
1 - Interfacing with the JTAG interface is easy
2 - Without specs provided by AMD you can't do anything with the JTAG interface
3 - The JTAG interface is nothing new, it has been on AMD's as well as Intel's chips for ever
4 - I use JTAG interfaces every day to repair dead PDAs, without the correct values for the shift registers you have no idea what hardware you are talking to inside the chip and no idea what the h*ll you are telling it to do.
5 - I measured the clock line of the JTAG interface shorted to ground, trying to interface with it will prolly kill something
In short: Don't expect the JTAG interface to be any help... Don't speculate it only gives people false hope. Just try to expiriment with the JTAG interface and try sending some data to it, maybe you'll get lucky.
If you read this topic you'll see I've posted JTAG interface schematics + pin specifications for A64 CPUs (939 as well as 754) so you can interface with the CPU for about 5 dollars worth of equipment.
Chances are very very great AMD just had a error in one of the processing machines for certain batches. Allowing some of those CPUs to get unlocked under certain conditions. Be sure the error has been spotted and has since be fixed.
Since we don't know what batch numbers they were (I found only one batch number, you need more to prove anything) you have no way of telling your CPU will become unlocked.
If we are talking about 300 CPUs only 3 or 4 people will notice their CPU being unlocked and will post it here. Since we've already seen 2 it's unlikely there will be more.
I don't say you shouldn't try, but as I've said earlier it isn't helpfull to reply in this topic if you are not trying something out or have thought of something new.
Repeating the same questions and discussions is utterly useless...
Also for people that haven't figured it out:
Changing the CPU name string has absolutely nothing to do with unlocking the CPU. All it is is a string in the flash memory on the CPU. Even if you can change it in the CPU itself it will not change the multiplier.
For people saying thing like "reading the JTAG" etc.
Read up on what JTAG is, it's simply put a debug and testing interface for complex circuits which can also be used to program or command certain parts.
JTAG works by a writing a couple of shift registers into the JTAG part of the circuit. These registers determain what component inside the circuit you are talking to and what you are saying to it.
For example JTAG can be used to talk to the memory controller, on PDAs I often use this function to test dead memory. That way I can disable pieces of the memory or know what chip te replace. If you are talking to the A64 you could be talking to it's memory controller. Since JTAG is slooooow testing 512MB of memory will take forever.
Even if you find the correct component (some piece of flash memory or EEPROM) you will then have to figure out what it's reading and writing commands are. If you've done that you have to figure out what registers control the max MP and then you have to be able to write a new value into it.
This task without AMD's specs is like trying to find one specific grain of sand in the Sahara desert...
Thorry you seem to know what your talking about as far as the jtag but wouldn't the jtag use the same instruction set as the cpu or would it have it's own language? Basic x86 and machine code is pretty well documented isn't it?
question!
how do u "flash registers" ?
form wha ti understand, i need external jtag hardware inerface, right?
what about dual-processor (not dual core) boards? can one cpu be running a prog to jtag the other?
thru assembly lets say
I'm reading the topic for quite a while and a question walks my mind. If we unlock a socket 939 then the rest of them (all s.939 cpus) are unlockable? I mean if we onlock an A64 can we unlock an Opteron 144 as well. Or do the jtags and stuff changes and we would have to start from the begining?
When we unlock the first one, no doubt it will help us with unlocking the other ones very quickly...
(and Kohan...."I helped my Uncle Jack, off his horse" shouldn't have a comma, it's an unnecessary pause, although we use it in speach for the reason you listed ;))
If that's all it takes, who's ready to goto the Sahara with me?! :explode2:Quote:
Originally Posted by Thorry
Nope, I saw it my self. He doesn't know anything about overclocking or that kinda thing.Quote:
Originally Posted by misteroadster
He didn't even know what is SuperPI!
I just wanted to check his CPU's power and that result!!! :slobber:
It's very strange. Believe me. I will put a screen shot of it in a little while.
Don't know what to do. Frankly I'm dissapointed. :(
Guys, JTAG doesn't use any language as such.
I think I've post a big PDF with all the JTAG specs in this thread somewhere. Anyways, it is a IEEE standard so for like 5$ you can get all the specs.
However all you'll be able to do is write values to the shift registers.
You will need to input the correct values in the registers to access the flash/EEPROM inside the CPU, then input the correct values to get it to read or write something.
So it's not like anybody with great expertise has a better chance of finding the magic numbers.
What is true however, once you've done one you can do them all. And anybody can do it at home for 5$.
You sound like a lzy salesman Thorry
I'm still bettin on the decompiling the Cool 'n' Quiet program.
Since it changes the multis in windows, thru software, it may as well unlock 'em
LOL, that's what we call jumping the gun.Quote:
Since it changes the multis in windows, thru software, it may as well unlock 'em
Changing the multiplier of a A64 CPU is easy, it is done by writing the correct values in the CPU's MSR registers. There are a lot of programs (even open source programs) that can change the multiplier of a A64 CPU. AMD has documented the MSR registers of their processors so that's no problem.
By no means is it possible to unlock the multiplier of a A64 by using the MSR registers or any kind of software available to the public today.
FIY the FIDVID MSR controlling voltage and multipliers via software is 0xC001_0042
To be able to write to MSR registers in Windows you need a kernel driver, this is because access to MSR instructions as well as some other instructions is limited to the inner most kernel shell.
ah... I see. Well, Clocker DID have a problem WITH the CnQ AFTER his spu got unlocked.
THerefore, what caused it to unlock corrupted CnQ, or vice versa
KoHaN69: I suggested earlier that a power-surge could have caused the internal registers of the CPU to flip, thus making it look like the CPU wasn't CnQ-enabled, which would make the OS to skip the CnQ-option.
Hi all.
Thorry
plz send me JTAG interface schematics + pin specifications for A64 CPUs (939 as well as 754) to tin@topmods.net. I have no too much time now to look thru all thread. sorry
I want to compare our methods.
ALL
dead mobos and dead 3500+ don't not arrive to me right now. So I wait. When they come I will post here as soon as I can and begin trying jtag with that pieces of silicone. I will try using bsdl from K6-2 , geode and amd flash memory.
I use this cable:
http://www.xilinx.com/support/programr/jtag_cable.pdf
With these pins on 939:
TCK - AG7 - I-IOS JTAG Clock
TMS - AG6 - I-IOS JTAG Mode Select
TRST_L - AF8 - I-IOS JTAG Reset
TDI - AJ9 - I-IOS JTAG Data Input
TDO - AG8 - O-IOS JTAG Data Output
These on 754:
TCK - E17
TMS - E10
TRST_L - B21
TDI - A21
TDO - A22
I found 2 problems stopping me:
- TCK is connected to ground potentially killing any CPU I connect to my interface
- Lack of internal CPU specs, so no idea what to tell it to do
I keep the TMS pin high following the docs to enable the interface.
The DB_REQ_L and DBRDY pins work into this as well, not sure how.
I've not yet connected any CPU to my setup as I'm not sure if this will kill the CPU given the TCK problem.
As for software, there is a lot of open source Linux software for JTAG interfaces available. However without correct specs you have no idea what you are doing increasing the chance of a dead CPU.
Buy a CPU, try it, if it kills the cpu, then RMA it.
Yes it's questionable ethics, but all is fair in love and OC:ing.
I'm not like that, besides it won't help.
If I now go out and buy a cpu and kill it by hooking it up to my JTAG interface I could go and RMA it. But then I'd have an extra CPU which I have no use for.
If I kill it twice I wouldn't be able to RMA it (or at least with great difficulty).
So you see, the end result is at best me ending up with an extra CPU which I have no use for. So it's too much trouble with most probably no result.
I'll just wait for TIN_EOF to test it for me, I've given him some of my ideas about how to safely test this. If his rig doesn't blow up I'll give mine a try.
Will someone test this thing?
too bad loose 939 sockets are BGA.. (?) would be nice if you could mod one and just put it in between the cpu and the socket on the mainboard. kinda like that dothan/p4 adapter.
It is still very likely that we can identify the register holding the multiplier by comparing all the registers from a 3000+ and a 3200+ from precisely the same stepping/week.
If so, we wouldn't know how to tell it to unlock, but we can write a speculative value to set the limit to 20 or whatever.
TIN_EOF will shortly, if he has any luck without blowing everything up I'll test it myself.Quote:
Originally Posted by MonkSP
Then I'll post a guide on how to help.
There are such devices, however I don't see how this would help. It's very easy to pop open the socket and solder some wires. I've been doing that since socket 370. Also when we've found the correct methode (which is a very slim chance) I'll post how to do it, it will not be hard.Quote:
Originally Posted by Gogar
I already posted what register holds the multiplier and voltage, there is also a lot of software able to change it. The stepping and week has nothing to do with this.Quote:
Originally Posted by Martin Cracauer
As stated before it is not possible to unlock a cpu using the MSR registers or software publicly available today.
Please keep this thread clean, only post if you've read the thread (all of it) and/or are experimenting (and have made some progress).
Please let me know if anybody has hooked up their JTAG cable to the TCK pin, I believe there is a big chance this will kill the chip and/or the cable/attached system. If somebody has attached it and gotten a response please let me know, I'll hook up my system and start the tests.
Hi Thorry ! Can you tell us "how to safely test this" ? Is it possible to read those BITS out without screw up the data in those register ? Thank you very much !Quote:
Originally Posted by Thorry
I had read your posts in this thread , and I still very interesting about this JTAG interface . Many thanks to you for the information for JTAG !
PS: Sorry for my bad english ..
How to do this as safe as possible:Quote:
Originally Posted by mola
- Use USB->LPT cable
- Connect to CPU with specs I provided
- Write software (use open source JTAG interface software for linux)
- Keep TMS high when powering on CPU
- Write random values to JTAG registers
- Read JTAG response
- Read JTAG response again, value changed = not good
- Write random values to JTAG registers
- Read JTAG response, same as previous value = not good
- Read JTAG response, same as previous read (and thus different from previous value) = good
If at any of these steps everything explodes or something is not working please let me know. Be sure to check for shorts in the meantime.
Do this at your own risk, you risk destroying your PC, cable, the test CPU and motherboard.
Note: This is just one small step in getting unlocked CPUs, much more needs to be done (if possible at all)
Or you could buy it at Fry's/BestBuy, if it dies return it.Quote:
Originally Posted by Thorry
I don't believe in ethics much, besides it's all for the cause of OCing... :toast:
AND ON ANOTHER NOTE,
Why make a jtag interface?
Is it not possible to use a dual-cpu motherboard?
Running off one processor and using jtag software to F around with the other?
:stick:
As I said, I'm not like that. Also we don't have any of those stores around here.Quote:
Originally Posted by KoHaN69
On the other note:
The JTAG pins aren't connected to the motherboard in any way.
Also if they were and we were able to unlock 940 CPUs chances are 939 and 754 CPUs don't work in the same way so we'll be screwed.
I see... i thought jtag is thru pins, but hmm...
*stares at the matrix code for inspiration*
So what about them voltages? underclocking, changing multis /voltage, undervolting, overvolting
any1 tried that?
Kohan, I think you are reaching a bit.
Just wait until people have started working with the JTAG interface. This will prolly not yield a unlock key, but it just might.
People have been trying to unlock Intel chips for years and nobody has ever been succesfull. This is prolly due to Intel frying a connection after programming, this is once been said by somebody working at Intel manufacturing and it seemed to be true.
It is very likely AMD has done the same. It's likely there was a error in one batch yielding unlocked CPUs in certain conditions. If this is the case there are only 200 CPUs max worldwide that can potentially be unlocked and only 3 or 4 that actually will become unlocked.
So don't expect there to be something magic allowing for unlocks. The JTAG interface might just do the trick, but it's a long shot at best.
Also once we've unlock one Venice core for example it's not sure we'll be able to unlock other cores. Or when we've unlocked a 939 cpu we might not be able to unlock 754 cpus.
So just hang tight and don't start reaching for crazy unlocking methods. I've seen and done a lot of torturing to CPUs and never seen one get unlocked so it's not likely torturing will unlock CPUs.
OK.
An Earlier Post mentioned, that on an MSI board, the MSI overclcking utility accadently unlocked multis.
One person had a glitch in the prog (it wasnt really unlocked, so they thought)
ANother person checked with cpuz and it was unlocked thru msi unlocking utility, but that glitch didnt occur again after restart.
Therefore, combine that with CnQ, I'm firmly sticking to my Softmoding Venice Theory
KoHaN69: Just because an application displays the different multis doesn't mean that they're usable.
I think he understands that, he mentioned the MSI CoreCenter glitch.Quote:
Originally Posted by Warship
you make me arghQuote:
Originally Posted by KoHaN69
Sorry, my bad.
A core center glitch? No way! I was running strait liquid hydrogen.. :rofl:
http://home.comcast.net/~aicjofs/corecenter.jpg
Idd, I wouldn't put my faith in software. If software craps up the registers other programs will read incorrect values as well. Verifying via CPUZ doesn't do much either, if I'm running core center my CPUZ always gives off strange readings and cannot give me any info about my memory.
Everybody knows core center is p00p
Quote:
Originally Posted by aicjofs
:clap:
This is a big *if* but *if* I can, I have some old crappy OCing S939 CPUs lying around somewhere that work... albeit not awesomely.
I would be glad to give them up as beaters...
I had a 3500+ Venice for RMA because she were not stable at all.
It's a 0517 E3 Stepping. She came back and now it's a E6.
The Testdocument tells me that they have overworked the Cpu.
njkid32 !
Today I received your mobos.
Thanks A LOT. I begin to work.
JTAG TCK on my CPU is not shorted with GND.
One of njkid32's mobo powering up CPU as needed, it's enough to start trying.
Good I am glad you got it. You can also thank Mrslinky as well. Now I dont know if that mobo is really dead but its missing a few little ic's around the socket. I just hope that you can figure this thing out. NOW, I am getting one of the unlocked venice's so TiN_EOF get in touch with me! On aim at njkidzona or msn njkid31.Quote:
Originally Posted by TiN_EOF
Yes, NJKid is getting my unlocked Venice which I just got back.
Also, the board I was using when my Venice became unlocked (resulting in the RMA of the board) is coming back to me after being serviced (I assume serviced) by AOpen. According to the AOpen website, the board they are sending me has the same S/N as the one I sent to them. I should have it on the 23rd. I have no idea what to do with it since I already have a new board. I guess I might ebay it.
rock on
Why have you got your Venice back? Have they refused your RMA? :eek:Quote:
Originally Posted by Clocker
:slapass:
Sorry to hear your unfortunate circumstances, but hey things happen for a reason, maybe there is a reason why the CPU has come back to the community, heheheee. Greatest death for a CPU is to die in a ground breaking experiment, heheheee
:cool:
Have you told them it was unlocked too? I'm sure some of the guys that work there would have wanted to keep it if they had known about it.Quote:
Originally Posted by Clocker
Yes. I mentioned that the lock 'was not working'. ;)
I'm glad someone in these forums saw I was trying to sell it here before my posts got pulled. :toast:
Now I just need to get rid of this magic motherboard. :p:
CxP
The lock was not working, haha... That's like, "hey, I got a bad CPU, the multiplier is not locked, I want my 'lock' back".Quote:
Originally Posted by Clocker
Seriously, I hope your unlocked CPU helps to resolve this mystery.
i hope it helps too :)
o.O
props to TIN_EOF
All our hope hangs on one Ukranian.
And Clocker - it must be faith ;)
I was wondering if there were some ES unlocked venices that could be used to make a guide for unlocking other venices.
Check this out, these dudes at sun, are watching closely over the processors they put in there machine, more then temps and such, but threw a specailized chip on the mobo to watch the cpu in realtime for errors and such, at the cpu leave. how does it talk to the cpu, threw some kind of cpu diagnoseis and monitoring port?
link? :stick:Quote:
Originally Posted by 4rory
Watcha talkin' 'bout? :confused:Quote:
Originally Posted by 4rory
Tin Eof do you have any results?
Quote:
Originally Posted by 4rory
:with: :toast: to confusing ppl :D :woot:
bump :confused:
Lol my bad, I forgot to post the link, it was to a video i found on sun's website about some of there new computers. I'll try to find the link again so you guys cant watch it, i think it was a a64cpu.
:lastweek:
Looks like this thread is winding up unless there's a breakthrough by TIN_EOF.
:horse:
Well, this is getting kinda boring...
Newsflash: njkid32 backed out of buying my unlocked 3200+ Venice. So, per Ugly&Gray's recommendation, I'm putting it up on eBay and letting AMD know about it. Anybody have a good email address I can use to let AMD know about the auction?
C
Quote:
Originally Posted by Clocker
NJkid dident "backout" of anything..he lost his job! That is a pretty damn good reason to not buy the chip! :rolleyes:
Unlocked 3000+ thats strange.
Did some one unlock it or it was orignally unlocked out of the box.
Is there a particular batch of unlocked venice , which week and stepping was this.
Also did ne one find a similar unlocked one or this is the only one.
If there is a procedure to unclock venice multipliers where can i find it.
Note: I didnt go through the entire thread , just the first and last page.
You should.Quote:
Originally Posted by Quad Master
Its seems will have to read the entire thread to unfold the mystery.Quote:
Originally Posted by MonkSP
Can some one tell me in short , please. :)
Read the thread if you're curious.
He DID backout. I never said it wasn't for a good reason & I never bad-mouthed him. Chill out.Quote:
Originally Posted by BB mods's
Poops....it just bounched back to me at that address. :(Quote:
Originally Posted by Thorry
C
Yeah I know that one...this is the reply I get from them :
Except there is no emial address for the processor department.Quote:
Hi,
Warm wishes.
You have reached embedded product support. In order to get an answer to your query please visit link
http://support.amd.com/consumer/EN and send your query to the relevant department.
Regards
Applications support
I'm sure AMD already has unlocked CPUs... Oh, wait, yes... they made them.
Lol, I think he thinks he is getting away with some kind of blackmail or something.Quote:
Originally Posted by Daved+
"Dont buy this unlocked venice and the secret is out of the bag!"
Something like that.
AMD doesnt care......
AMD has unlocked CPU's but its the FX SeriesQuote:
Originally Posted by Daved+
not the Normal Venice Cores that are unlocked.
I was intrested as i had never come across a Unlocked Venice Core.
How do you know they don't have unlocked venice's? I bet they do.Quote:
Originally Posted by Quad Master
Hi Daved+
Have you seen this (Opteron 146 unlocked).
http://xtremesystems.org/forums/showthread.php?t=78109
Gigabyte k8t800 based board unlocked 754 cpus...
"Cool & Quiet" can be hacked as well to get higher multi's.
Quote:
Originally Posted by cadaveca
source? :confused:
Quote:
Originally Posted by cadaveca
Please elaborate.
Do some research. i opsted about hte gigabyte board a long time ago, and that it might be fubarred bioses from changing cpu's as well. It got no notice then, so i give no notice now. I just hate to see the thread die.
It is possible. When i get time, i will find the references to the gigabyte board, although that was almost 2 years ago now, the best i remember is blue background or dark background for the site for the gigabyte board, and i have heard it from a person working with a mobo company when he posted a weird multi that it was cool and quiet hack. also note in DFI bios that you can set the CNQ max multi to higher than stock multi. never tried it with CnQ driver installed tho...I fold 24/7.
But it isn't workingQuote:
Originally Posted by cadaveca
nono
No matter what multi is displayed as options in the BIOS, this has _absolutely_ _nothing_ to do with whatever [multis] the processor can utilize.
MAX_MULTI is stored in non-volatile register inside the cpu.
That is read by the bios on boot.... :rolleyes:
Quote:
Do some research.
I "researched" the CnQ idea before when someone suggested it in this thread but I didn't find any proof, just rumors. That's why I asked you if you knew more. :rolleyes:Quote:
and i have heard it from a person working with a mobo company when he posted a weird multi that it was cool and quiet hack.
Was it Epox Tech you were talking about?
http://www.aoaforums.com/forum/showthread.php?t=28718
Personally, i think CnQ is the way to go. MAX FID and VID are based on what the driver/bios read from the cpu, and the bios/driver then deems what the max is. I am unsure whether the bios prevents the higher multi selection, or the driver, but I was able to get powernow working on Nforce2 boards when it was said it couldn't be done. This involved modding the cpu traces to other than what has been shown to unlock "superlocked" AXP's, and getting the cpu recognized by the bios as something other than what it really was.
So maybe a combination of a proper bios, and the right CnQ driver, would enable higher multi selection from within windows.
I siad "do some research", becasue although one person may not be able to find anything, another may just by having a different perspective on things. It wasn't meant as a slight in any way; but ot just give up is not how the problem can be solved.
In regards to the gigabyte board, i'm pretty sure that the site that had the review on it was tbreak, but i have not been able to find that article. The way it may have been done could have been nixed by current cpu revisions, anyway, as socket 754 is an old beast.
In regards to actually getting you hands on the "CnQ hack" referenced in many places, i doubt that it would be something you could just download, although i'm fairly certaina programmer with enough ambition could make the nessecary changes to make it happen...why else would this option be in the DFI bios?
so did we finally figure out what's with the unlocked venice?
Nope. :(Quote:
Originally Posted by k3n.chu
No shat, Sherlock. But, maybe they would like to know how one became unlocked 'in the wild' without their process. It could be something totally different than what they are doing to unlock their processors. Man, there are some pretty simple minds around here....!Quote:
Originally Posted by Daved+
C
No, dude... Do you really think they don't know how they made the unlocked venice's by mistake? They designed and made the whole CPU, they know it pretty well. Anyhow, let's go back to the topic.Quote:
Originally Posted by Clocker
I'll chaulk up your comments to you not reading this thread and understanding the circumstances of how the chip was locked initially and then became unlocked by a motherboard that died. Or maybe they would want to understand why the cpu is unlocked but CnQ doesn't work anymore?
But, maybe you're right. I'm sure they know exactly what happened to the motherboard and/or CPU to make this happen out of the blue even though they have never see the CPU or motherboard in question. lol.
Any decent engineer of any product that failed in an uncommon way would be curious as to what caused it and would like to see it. The unlocking is a failure in the CPU as well as the non-working CnQ. Are you saying that there could be only one cause for these design failures and AMD already knows it? I think not, but maybe you're an expert on CPUs or something.
Last word.
/me thinks it's a good idea to lock this thread. When there is new serious news people can always start a new thread or ask a mod to reopen it.
This is going nowhere.... to bad people don't take the effort to read the thread. In a thread of 36 pages you can be damn sure whatever you have to say has been said already.
i read throught this whole entire thread and i say for the first 20Pages every thing was good and from then on, bleh it went downhill.
I hope someone finds this secret out.
Well I had my "know-it-all" motions on this thread, but I didn't say anything.
Because I might be wrong and the gang of young hooligans might be on to something.
And find the "Holy Grail".
And who knows if that will not happened.
Let they try, and give them the positive support of knowledge you have.
But lock it ?
Nej ...
If this thread has over 900 replies and almost 80 K views, let it ride on.
This is XS and nothing else.
Hell some of XS threads should been cast away after the first thread.
So keep this thread alive and pumping, you are the proof that we all old farts lost 20 years ago.
So come on .... and create miracle
http://members.cox.net/bwm211/oldfart.gif