With the Phenom there was a chip at 0x69 whom I dumped many times. I expected it to be the clock generator. I only have the specs for an similar clock generator and I was not yet able to figure it's registers out. I focuesd on the M2A-VM clock generator yesterday, because i have the specs of that clockgen chip and it is the simplest one.Originally Posted by KTE
Like I said in other post, the app can cause the system to go haywire. Was that first time you tried to get the dump?
With the k8 cpu there was no chip at 0x69 according to i2cdetect 0. I was curious if that chip was just not detected and tried to dump that address 'i2cdump 0 0x69". It was not the first time i tried to dump an nonexistent address and the result was the same as with other nonexistend address dumps. Just XX's and no hex values.
However after that test "i2cdetect 0" did no longer show the 0x2e chip and since then i can not get beyond C1.
This is what I mentioned a few days back. On different boots, different reads. Some apps get them from the same registers though
I've seen their debug dumps, you can ask VVJ.
AOD, CPUZ, CBID, AMDPM, CCPUID label cores differently. Sometimes one core is another in the other app, thats what I said hindered me trying to oc individual cores. Each time you reboot, core arrangement might very well be different
For me, I change it until AMD PWM and CCPUID read similar. Thats worked fine so far...I saw your postings few days ago. Most astonishing to me is that AMD PM uses different labels than the MSR-Registers. I thought it completely relies on those registers. M$ developers should shed some light how they bind threads to cores.
Reply With Quote
Bookmarks