On Tuesday 18 December 2001 13:27, Constant Brouerius van Nidek wrote:
Thanks for the reminder. Reading and rereading and somewhere along the process you forget some things. But. Having read the sensors.conf for another time I am hopelessly unsure as to where to change the specs for my mainboard. I have a w83781d chip so that part is easily found. After that I do not know further. I have found the min and max settings but although the maker of sensors has a nice and entertaining style in this config, I do not understand a word from his calculations and so on. If I give you the data, could you return me a updated file. Or could you describe the process so clear that I could do it myself? Groetjes
Kind of depends on what you want to do. You really shouldn't have to mess with the calculations - at least I cannot see any reason to. Looking at the voltages section (for the w83781d) of the sensors.conf file, you find out that: label in0 "VCore 1" label in1 "VCore 2" label in2 "+3.3V" label in3 "+5V" label in4 "+12V" label in5 "-12V" label in6 "-5V" So, from that information, you know what these values represent. set in0_min vid*0.95 set in0_max vid*1.05 set in1_min vid*0.95 set in1_max vid*1.05 and so on..... all the min/max thing does is calculate a +/- 5% tolerance in the reported value. You can adjust the accepted range here. If you just want to set the ranges to something a bit more in line with yout MB and processor, you need to do a bit of digging. What kind of CPU are you using? What are your BIOS and hardware settings? Are you overclocking? Underclocking? You can get a lot of basic information about temperatures and voltage ranges by just browsing your BIOS screens.... look at what is being reported back to you in the PC Health section of the BIOS. How does that compare to the results you are getting in sensors or gkrellm? Also, have you set up gkrellm correctly? I don't use it, and when I started it up, the default sensor corrections were set to values that put the reported values way out of range. I have to reset most of them back to 1.0 as the multiplier - this may have something to do with the twiddling I did with my .conf file. C.