yep, this is what i get...
#----cut here----
# Chip drivers
# no driver for AMD K10 thermal sensors yet
#----cut here----
Printable View
yep, this is what i get...
#----cut here----
# Chip drivers
# no driver for AMD K10 thermal sensors yet
#----cut here----
Says it all, really. Gotta wait for the update OR go get the latest source and roll your own ;)
Wish I knew how...
It will defineatly be reporting frequency wrong if the reading is under load. The chip would never allow 3.6Ghz on all cores loaded at stock.
What does do though is essentially sit in Turbo mode whenever it's completely idle or less than 50% CPU usage(load distributed across any cores). when load goes above that it'll be at 3.2.
I
-edit , my mistake, it does only boost active cores!
It was definitely under load when I checked. When I enabled CnQ everything went to 3.2 though.
just edited my post, it does only boost the 3 cores.
CnQ is a bit screwy at the moment, I haven't seen anyone be able to disable it fully, I think the HW turbo mode overrides
It might use CnQ to regulate itself to 3.2, running up to 3.6 with the controls disabled. I really don't know, but it wouldn't surprise me.
In the BIOS screen when I was Re-enabling CnQ it mentioned that in processors which support turbo mode CnQ should be set to disabled. I had it disabled though and got an error message on boot-up in Ubuntu saying it would be unable to scale the frequency properly. I actually set CnQ to "auto" instead of enabled or disabled. No freq. scaling error message and it runs at 3.2 under load. When I go to overclock it all this will be moot anyway, but until LM-sensors works I'm going to refrain. It ran 24 hours at 3.6 to the best of my knowledge and it didn't seem to be running very hot, but without the sensor working properly there is no real way to tell yet. Not one available to me, anyway.
mm I need to get AMD Overdrive to work with my mobo so I can check it out. No other freq reporting tool reports what's going on properly.
But I think that all totally idle cores will always drop into a lower P state / frequency even with CnQ off. Perhaps Turning it OFF just prevents the legacy operation of CNQ from occuring..
Try this:
enter "sudo modprobe k10temp" (then your password of course)
then "sensors" and see what it says.
Gave it a shot D_A this is what returned
Code:$ sudo modprobe k10temp
[sudo] password for XXXXXX:
FATAL: Module k10temp not found.
What kernel version are you running?
(type "uname -r" in the terminal)
2.6.31-21-generic
Code:$ uname -r
2.6.31-21-generic
The K10temp module is listed as being included in the 2.6.33 kernel series .... how much do you want it?
A bit, but as I don't plan on bringing this computer down until supercomputer week is over I can wait a week. Ive found a few websites with instructions on adding k10temp manually, but I'm afraid I have run out of time to do it right now. Later tonight I will be back to mess it up :p:
Honestly I think you're better off just compiling the kernel from source. I can help you with that, it's actually not that hard (when you have a script to work from ;) )
Wait till after the challenge, though, so you have time to tinker with the MANY new settings you'll discover.
Sounds good, I look forward to it.
Just a reminder, when compiling the kernel, don't forget to build in support for your file system, network, and SATA. I've done it before, and it is not fun to debug when you're totally new to it:D
Just take your time in menuconfig. I love compiling my own kernel now. Compiling gnome or KDE on the other hand...
So I am up and running on my WHS server with a 1055T, however I have one quick question, when I go and stream from the server what happens? Does WCG suspend, share or other?
Thanks.
usually it suspends until your cpu is freed back up. i can leave boinc crunching, start a game and never miss a frame.. i hope that's what you're asking
Yep. Just want to make sure it doesn't mess with my streaming. Thanks.
Hello, Just got home, checked stats after a little over 26 hrs running, results upload 1 hour ago and shows average points per calander day as 1,266.83 but probably because I joined 3 days before actually running. Points generated shows 7,601 but did not start running till 27hrs ago. Team History and stats updated 5 hour ago so does that make it 22 hours? 345.5 points per hour?Quote:
Originally Posted by sierra_bound
Edit: My Up Time now shows 1:04.43.33
Don't remember benchmark, sorry. Wanted to get some idea of performance before activating other machines.
Found it, Thanks soya! 3275Whetstone/8011 Dhrystone for stock speed, volts, cooler +2600NB
My intention was/is to nurse folk through the process the first time and just build a new kernel with everything the same as the original generic kernel. That way everything should work straight away, but they get the additional modules that come with the new kernel version.Quote:
Originally Posted by jspace
For my own kernels, I strip them worse than an open cut mine. I even cut multicore support down to only and exactly the number of cores in the precise rig the kernel is for, just to save a little bit more memory.
Well, thats the Bench at 4GHz. I do know that it's quite much voltage, but it isn't stable at all beyond 3,6GHz.
W7 64 Bit
http://www.abload.de/img/x694j5.png
For some reason I'm getting better results with less Mhz
1055T @ 3.92Ghz NB @ 2800 RAM 1120 CAS 7
3246 FP (whetstone)
10344 INT (Dhrystone)
so at 4 I'd expect a couple % higher even.. Sensitive to NB/L3 cache ??