Forum > Linux

SETI MB CUDA for Linux

<< < (118/162) > >>

riofl:
interesting.. didnt know freesoft had a prime95 for linux 64. got that too just to have it. could be useful.

sunu:

--- Quote from: riofl on 21 Jan 2010, 05:24:58 am ---if i remember correctly (it has been almost 2 yrs since i did this) i believe i upped the VID to 1.3 v or so.

--- End quote ---
Please refer to it as vcore. VID is constant something like a characteristic printed on the chip. 1.3 volts is very very good for 3.6Ghz. I also use 1.3 volts but for 3.24 Ghz.


--- Quote from: riofl on 21 Jan 2010, 05:24:58 am ---but since i always really wanted a 3.0 ghz machine but at the time could not afford the processor, and this can safely go to that speed i decided to go against my beliefs so that i had the best of both worlds for myself. :)

--- End quote ---
That was also the reasoning beside my decision. I settled for 3.24Ghz. I didn't want to go beyond that since my motherboard is very basic.


--- Quote from: riofl on 21 Jan 2010, 06:01:58 am ---interesting.. didnt know freesoft had a prime95 for linux 64. got that too just to have it. could be useful.

--- End quote ---

Yes, though I've never used it. Yes, it could be useful.

riofl:
i have discovered the following:

in0 = VCore
in1 = DDR2
in2 = 3.3v
in3 = Vcc
in8 = VBatt.

i have changed the labels accordingly in the lmsensors config. the rest are way off calibration and could not possibly be even close.

the temp1 and temp2 that i think are mosfet and southbridge based solely on hair dryer proximity, may be those or they may be what this guy listed. unfortunately he did not have my motherboard, but a close model gigabyte.. he claims they are

temp1 current system temperature
temp2 current cpu casing temperature

i dont know for sure... gigabyte cannot help at all. the guy sounded like i was crazy. they arent too awfully important anyway as the hottest runner, temp2 has never exceeded 55c on peaks and typically runs 45-50c.

so in0 is the Vcore and its voltage matches the  cpu0_vid... which i find out appears to be a static listing. it never moves so maybe it reads something from the cpu? dunno.

sunu:
The most important temperatures are the four coretemps. If these are good the rest (almost) don't matter
.

--- Quote from: riofl on 21 Jan 2010, 04:52:44 pm ---so in0 is the Vcore and its voltage matches the  cpu0_vid... which i find out appears to be a static listing. it never moves so maybe it reads something from the cpu? dunno.

--- End quote ---

That's why I said that cpu0_vid might be the real VID after all. We'll find out if/when you fire up windows and see what Core Temp says.

riofl:
VERY interesting!

the sensors core0VID is the VID as reported by the chip itself. still there is a difference between linux and windows.
linux says it is 1.219 while coretemp reports it as 1.2500

results of tests:

idle
core0 = 35
core1=35
core2=33
core3=33
cpuz reports coreV = 1.232

under load after 4 iterations of the smal fft test
core0=56
core1=56
core2=51
core3=51
cpuz coreV=1.2500 initially then after a few seconds drops to 1.216

the motherboard health status states the VCore=1.252

i decided to give myself a "newer" computer to celebrate its 2 yr old birthday  :P

played around at 3.6ghz but since i have changed ram from the last time (old ram was crucial ballistix new ram is OCZ low voltage Blade series) I find that at 3.6ghz the lowest besides 1000 i can go is 1200 which the ram plainly complains even upped from 1.8 to 2.0 volts which is .1 v higher than recommended maximum. so i had no success in stability at 3.6ghz so i dropped it to 3.45ghz along with 1152 on the ram (base is 1066) and VCore set at 1.312v. it appears to be rock stable. I also found that there is a 5c approx difference now between auto and max on the cpu fan so it is set at max and my temps are not much different than at 3.0ghz. maybe 2c higher.. basically nothing... the system passed small fft , large ffp and mixed bag with flying colors. i then booted into memtest86 and ran 2 iterations of its test and all passed just fine.

so i am leaving it at 3.45ghz for now and will run all my apps, test movies, audio, everything.

interersting day :D

edit addition:
interesting ... the vid cards are running hotter. does that mean maybe my 0.35cpu settings in app_info file and the faster cpu are driving the vid card harder? the 285 is averaging maybe 2c higher than normal but the tesla is running a good 10c hotter! it is now averaging 73-77c at max fan! maybe i jarred it a bit too much in cleaning the system and caused some of the thermalpads to fall or a break in the gpu paste... it shouldnt do that but that thing has been one of those 'jiggle it till it works then dont touch it and hope it stays that way' items.... guess i need to replace it sooner than i wanted to...

20 min later...:   it appears that the problem was with the cpu fan running full bore now (2750rpm approx instead of 2480 approx), it upset the rather delicate airflow balance i had achieved in the case. i had to readjust all fans :( now the tesla is peaking at 68c which is approx 2c or so warmer than it used to and more than acceptable).

Navigation

[0] Message Index

[#] Next page

[*] Previous page