dmacias

Did you run this from the command line?

You could try changing the label on the coretemp reading but not sure what to put in place of temp1. "Core 0" maybe. # lm-sensors config chip "nct6776-*" label CPUTIN "CPU Temp" label SYSTIN "MB Temp" chip "coretemp-*" label temp1 "CPU Temp" Also how and where are copying sensors.conf. I just tested using an WinSCP that any changes made to sensors.conf happen immediately.

I have an it8771 sensor and I got a similar message. I had to force it to be seen as an it8721 with this command modprobe it87 force_id=0x8721 You would need to do something similar for your sensor chip. What does sensors command show? Also I don't know if this would help: http://www.spinics.net/lists/lm-sensors/msg08505.html specifically the modprobe commands

Create a file called sensors.conf and place the following text in it. # lm-sensors config chip "nct6776-isa-0290" label CPUTIN "CPU Temp" label SYSTIN "MB Temp" You can put it where ever you want on your flash drive. I just chose to make a "custom" folder and mirror the folder structure to the same as where I would be copying the file. You need to copy that sensors.conf to the empty (root)/etc/sensors.d folder you found. And if that fixes it then you put a copy command in your go file so it copies when you reboot.

@Switchblade. Only thing I can think is if you edited with a text editor and messed up some syntax somewhere. Also boot/etc/sensors.d would be on your flash drive. It needs to be in etc/sensors.d. You can navigate from a command prompt or use ssh and an ssh client like winscp. I use both along with mc (midnight commander?) from the command prompt.

I upgraded with no problems. I'm not sure what might have changed. Check your log for errors. You could try going back.

I haven't updated but maybe I will. I would double check through telnet and something like winscp. I'll try here in a little bit. Does the modprobe w83627ehf give an error from the command prompt?

Haha look above your post at my last post, I think we replied at the same time but I think I figured it out. You just have your conf file in a different location and it's not getting copied over by the command in your go script.

Oh I think I see the problem now. I manually created sensors.conf and placed it in "/custom/etc/sensors.d" where "custom" is a folder in the root of your sd card.

Try what beire did. As far as another thread I tend to agree as this thread could easily be overrun with sensor info. But a tutorial is kinda hard since there are so many different motherboard and configurations. A good place for some good info is lm-sensors.org under their FAQ.

What does modprobe it87 do from the command prompt? If it just goes to the next line then what does sensors say afterwards. Also did you check if sensors.conf is actually copied to /etc/sensors.d. Only other thing I could think to do would be to force it8721 (modprobe it87 force_id=0x8721) and change the chip line to match (chip "it8721-*").

@Concorde rules try googling about "acpi_enforce_resources=lax" or modprobe device busy. I remember reading some people having your problem and that fixed it but I don't remember the whole command for your go script.

I think bonienl is responsible for the temp plugin and I think it should be more of a unRaid thing or separate project just for hardware monitoring than just Simple Features. I originally just wanted all sensors from the command prompt then maybe a page of raw sensor data in system profiler like in unmenu with maybe mem usage but I love the temps on the main menu. If you've ever used speedfan in windows I think it would be a huge task and hard to manage all the different MB combos.

Not really, other than observing and recording the voltages, fan speeds and temps in the bios and then comparing after you boot up and it had been idle for a bit. Or find one that has already been made for your exact MB.

I agree. I found this conf on avsforum the other day when I upgraded to 11. It was almost exactly like the conf I already had but I liked the format it was in so I just copied it exactly. I had k10temp labeled GPU Temp b4, don't remember how I determined that.

Good I'm glad it worked. Maybe this will help some others as well. Now you just have to figure out if the computed values are right and the temps actually match like the core and the cpu. You might have to tweak the conf. But then again I just use mine as a baseline now and quit caring if they matched the bios exactly.

You are not seeing anything because I think the temp plugin is looking for a label of CPU and MB Temp like I have in mine. So you have to have sensors.conf label temp1 to CPU Temp and temp2 to MB Temp. I'm not sure if you need the force 8860 part. Maybe just the modprobe w83627ehf and I would change the chip part to w83627ehf-* since thats what shows when you run sensors. Also you don't need everything from the conf, I would just put a chip part and label parts to test. Just so CPU Temp shows up when you run sensors and not temp1. Also you can add a -r to the modprobe command to undo it I believe. You guys can check out lm-sensors.org under faqs esp. chapter 1&2 for a better explanation than me.

My previous post was more for Jack0w but seems like your getting somewhere. I would put that conf I gave you earlier for the fintek chip, which is what you have, in the /etc/sensors.d/ folder and change the chip line to: chip "w8860-*" or something like that and make sure the values match up to what they should read and ignore sensors with invalid readings.

I just googled it (sensors.conf, modprobe, or lm_sensors along with my MB name). Just now I did C2SEA and modprobe. First site had from phoronix site had this: modprobe w83627ehf force_id=0x8860 I originally did this a while ago in order to display more sensors than just the cpu temp. I wanted to monitor my volts, fans and temps. I have a lian li q08 with a seasonic fanless power supply with just a front 120mm. I ended up adding a cpu fan and may add a 120 to the top. You guys can try this stuff from the command prompt and edit a sensors.conf in etc/sensors.d till you get it to display what you want from the sensors command.

I wouldn't use the same modprobe code in the go script that I used. It was just an example of what works for my MB. I think you have a fintek chip and I have an ITE chip (it8771). Mines not supported so the modprobe forces it to see it as an it8721 and in conjunction with my conf show the proper values. You could just use a config that relabels one of the core temps to "CPU Temp". I had to change my original conf because it had a label of "M/B Temp" instead of "MB Temp". You might run sensors-detect and see what that says. I'm not sure what modprobe command you would use for your chip to get more sensors showing.

I found this for your chip. Dont know if it will be accurate. What does sensors output show now. # # sample configuration for the Fintek f71882fg for MSI X58 Pro (7522-040R, # like seen in Hetzner's EQ6 servers). To load the driver module, append a # single line (without the #) to /etc/modules: # f71882fg # chip "f71882fg-*" # never change the in0, in7 and in8 compute, these are hardwired in the chip! compute in0 (@ * 2), (@ / 2) compute in2 (@ * 2), (@ / 2) compute in3 (@ * 2), (@ / 2) compute in4 (@ * 5.25), (@ / 5.25) compute in5 (@ * 11), (@ / 11) compute in6 (@ * 5.25), (@ / 5.25) compute in7 (@ * 2), (@ / 2) compute in8 (@ * 2), (@ / 2) # Temperature # cpu temp is about 35 deg celsius (linux, idle) label temp1 "CPU" set temp1_max 70 set temp1_crit 80 # the IOH runs rather hot, even with an idle system 60..65 deg celsius # are seen. DO NOT ACTIVATE CPU SMART FAN OR IT WILL GET EVEN HOTTER! label temp2 "IOH" set temp2_max 80 set temp2_crit 90 # system is about 40 deg celsius (linux, idle) label temp3 "System" set temp3_max 50 set temp3_crit 55 # Fans # value (CPU smart fan disabled!) is about 2300 rpm (linux, idle) label fan1 "CPU" ignore fan2 # value is about 2200 rpm (linux, idle) label fan3 "System2" ignore fan4 # Voltage label in0 "3.3V" label in1 "Vcore" # BIOS (loaded) in1 == 1.25V # linux idle in1 == 1.05V (?) set in1_max 1.35 ignore in2 ignore in3 label in4 "+5V" label in5 "12V" ignore in6 label in7 "3VSB" label in8 "Battery"

You need a custom sensors.conf for your motherboard. You can google your MB and sensors.conf and someone probably has made one. I have an ASUS C60M1-I with an ITE IT8771E. If you run sensors-detect there is no driver for IT8771E. If I execute"modprobe it87 force_id=0x8721" I force it to use IT8721 which is supported and then the sensors show up. But you need a custom sensors.conf to format the output correctly. So I put this in my go script. It copies my custom conf to /etc/sensors.d and then forces its use. #Update Sensors cp /boot/custom/etc/sensors.d/sensors.conf /etc/sensors.d modprobe it87 force_id=0x8721 And here is my sensors.conf: # lm-sensors config for Asus C60M1-I board chip "it8721-*" label in0 "Vcore" ignore in1 label in2 "+12V" ignore in4 label in5 "+5V" ignore in6 compute in2 @ * (50/12), @ / (50/12) compute in5 @ * (205/120), @ / (205/120) compute temp1 @ + 10, @ - 10 label fan1 "CPU Fan" label fan2 "Chassis Fan" label temp1 "CPU Temp" label temp2 "MB Temp" ignore temp3 set in0_min 0.5 set in0_max 1.5 set in2_min 12 * 0.95 set in2_max 12 * 1.05 set in3_min 3.3 * 0.95 set in3_max 3.3 * 1.05 set in5_min 5 * 0.95 set in5_max 5 * 1.95 set in7_min 3.3 * 0.95 set in7_max 3.3 * 1.05 set temp1_min 0 set temp1_max 70 set temp2_min 0 set temp2_max 60 set fan1_min 0 set fan2_min 0 chip "k10temp-*" label temp1 "CPU Temp" Also running sensors at command prompt outputs this: k10temp-pci-00c3 Adapter: PCI adapter CPU Temp: +50.4 C (high = +70.0 C) (crit = +100.0 C, hyst = +97.0 C) it8721-isa-0290 Adapter: ISA adapter Vcore: +1.09 V (min = +0.50 V, max = +1.50 V) +12V: +12.20 V (min = +11.40 V, max = +12.60 V) +3.3V: +3.38 V (min = +3.14 V, max = +3.46 V) +5V: +5.00 V (min = +4.76 V, max = +5.23 V) 3VSB: +3.36 V (min = +3.14 V, max = +3.46 V) Vbat: +3.36 V CPU Fan: 2163 RPM (min = 0 RPM) Chassis Fan: 736 RPM (min = 0 RPM) CPU Temp: +54.0 C (low = +0.0 C, high = +70.0 C) sensor = thermistor MB Temp: +40.0 C (low = +0.0 C, high = +60.0 C) sensor = thermistor intrusion0: ALARM It would be nice to have this parsed and formatted under System Profiler like the other info there. I have previously hacked it to show the raw output but a formatted sensors output would be nicer.