Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Oops. I must've uploaded shareware version by accident...
I have to turn the power off and back on to get the system to boot again.
I thought the instructions said to power cycle the machine and not to reboot it
That's very unlikely. But feel free to try, say, 235...Is it possible that the board is not liking some numbers like 232 but it would work at say 235?
^^^ pleasetear said:Also, while at 231, can you show me output of tpc -htstatus ?
My board seems to have maxed out with 235. I was running 240 for a day or so and everythign seemed fine, but I started to notice I was getting memory errors. After the unit completed I queried the ht-retries and one of them was up to 160+ Backed it down a bit and it seems happier now. Still all 0's as of this morning, though my TPF increased from 19:45 to 20:30 or so (on 6128's).
I went and increased the voltage to 1.05
The GL boards allow you to change vcore?
My board seems to have maxed out with 235. I was running 240 for a day or so and everythign seemed fine, but I started to notice I was getting memory errors. After the unit completed I queried the ht-retries and one of them was up to 160+ Backed it down a bit and it seems happier now. Still all 0's as of this morning, though my TPF increased from 19:45 to 20:30 or so (on 6128's).
As long as the wu aren't corrupted isn't lower TPF what you want? Seems to me in your case I wouldn't worry about the ht-retries if your TPF is 45 seconds less.
It is not a GL thing. It is an HE chip thing.
Temperature table:
Node 0 C0:31 C1:31 C2:31 C3:31
Node 1 C0:31 C1:31 C2:31 C3:31
Node 2 C0:31 C1:31 C2:31 C3:31
Node 3 C0:31 C1:31 C2:31 C3:31
Node 4 C0:28 C1:28 C2:28 C3:28
Node 5 C0:27 C1:27 C2:27 C3:27
Node 6 C0:26 C1:26 C2:26 C3:26
Node 7 C0:25 C1:25 C2:25 C3:25
Tear, I have a question
Node 0 0000 0000 0000 0000 001c 0000 0000 0000
Node 1 0000 0000 0000 0000 0000 0000 0000 0000
Node 2 0000 0000 0000 0000 0000 0000 0000 0000
Node 3 0000 0000 0000 0000 0000 0000 0000 0000
Node 4 0000 0000 0000 0000 0000 0000 0000 0000
Node 5 0000 51a2 0000 0000 0000 0000 0000 0000
Node 6 0000 0000 3928 0000 0000 0000 0000 0000
Node 7 0000 0000 0000 0000 0000 0000 0000 0000
As you can see, I have three positions with retry numbers. It's always the same three. And this is at a pretty low 10% OC.
Do they correspond to individual memory sticks?
I ordered three new sticks based on the theory that they do.
How would I go about mapping the above output to individual slots?
I had that issue with ie saving as a .mp3. I just deleted it and put the 511 that was there, correct?
^^ what Mr. Firedfly says.HT-retries have nothing to do with ram. The hyper transport (HT) is a way for nodes on the CPUs to communicate with each other. When there is an error sending/receiving a HT packet, an HT-retry occurs.