"SimpleFeatures" Plugin - Version 1.0.11



2848 posts in this topic Last Reply

Recommended Posts

Any hints on where you found the details for sensor configurations for your setup? Trying to work out how to do this for my Supermicro C2SEA, but haven't had any luck so far.

 

Sent from my Nexus 7 using Tapatalk HD

Link to post
  • Replies 2.8k
  • Created
  • Last Reply

Top Posters In This Topic

Thanks dmacias!

 

Before I get started, this is what I see if I type sensors at the command prompt;

 

root@Tower:/etc# sensors

coretemp-isa-0000

Adapter: ISA adapter

Core 0:      +40.0 C  (high = +76.0 C, crit = +100.0 C)

Core 1:      +41.0 C  (high = +76.0 C, crit = +100.0 C)

Core 2:      +37.0 C  (high = +76.0 C, crit = +100.0 C)

Core 3:      +37.0 C  (high = +76.0 C, crit = +100.0 C)

 

It is showing the temps, but they do not show up in SF.

 

Under the path /boot/etc/sensors.d/  I have no files at all.

 

I used the code in your post to create a sensors.conf file, and I placed it in /boot/custom/senors.d/

 

I then put the following in my GO file;

 

#Update Sensors

cp /boot/custom/sensors.d/sensors.conf /etc/sensors.d

modprobe it87 force_id=0x8721

 

I have created the file and edited the GO file, but have not rebooted yet.  I wanted to confirm I have this correct first.

 

Thanks!

 

 

Link to post

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.

Link to post

Any hints on where you found the details for sensor configurations for your setup? Trying to work out how to do this for my Supermicro C2SEA, but haven't had any luck so far.

 

Sent from my Nexus 7 using Tapatalk HD

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.

Link to post

given I don't know what the modprobe actually does, I don't know if I even need it in my GO  file.

 

should I try this in my GO file?

modprobe w83627ehf force_id=0x8860

 

I have the C2SEE, which is the same chipset as the C2SEA.

 

Ok, I just typed "modprobe w83627ehf force_id=0x8860" at the command prompt, and then typed sensors.  I got a ton more data,

 

root@Tower:~# sensors

coretemp-isa-0000

Adapter: ISA adapter

Core 0:      +42.0 C  (high = +76.0 C, crit = +100.0 C)

Core 1:      +42.0 C  (high = +76.0 C, crit = +100.0 C)

Core 2:      +37.0 C  (high = +76.0 C, crit = +100.0 C)

Core 3:      +39.0 C  (high = +76.0 C, crit = +100.0 C)

 

w83627ehf-isa-0290

Adapter: ISA adapter

Vcore:        +1.12 V  (min =  +0.92 V, max =  +1.48 V)

in1:          +1.85 V  (min =  +1.65 V, max =  +1.99 V)

AVCC:        +3.34 V  (min =  +2.96 V, max =  +3.63 V)

+3.3V:        +3.34 V  (min =  +1.09 V, max =  +0.83 V)  ALARM

in4:          +1.57 V  (min =  +1.35 V, max =  +1.65 V)

in5:          +1.27 V  (min =  +1.13 V, max =  +1.38 V)

in6:          +1.43 V  (min =  +1.42 V, max =  +1.52 V)

3VSB:        +3.33 V  (min =  +2.96 V, max =  +3.63 V)

Vbat:        +3.26 V  (min =  +2.96 V, max =  +3.63 V)

in9:          +0.00 V  (min =  +1.24 V, max =  +1.33 V)  ALARM

fan1:        1814 RPM  (min =  712 RPM, div = 8)

fan2:        2033 RPM  (min =  712 RPM, div = 8)

fan3:        1163 RPM  (min =  712 RPM, div = 8)

fan4:        1102 RPM  (min =  712 RPM, div = 8)

fan5:        1016 RPM  (min =  712 RPM, div = 8)

temp1:        +36.0 C  (high = +60.0 C, hyst = +55.0 C)  sensor = thermistor

temp2:        +33.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = CPU diode

temp3:        +0.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = CPU diode

cpu0_vid:    +1.513 V

intrusion0:  ALARM

 

I tried running sensors -detect and got an error.

 

Link to post

How do I uninstall Simple Features? 

 

I searched and saw people say to delete files in the "/extra" directory, but I can't find that directory.  I'm running 5.0-rc11 and Simple Features 1.0.11

Link to post

Any hints on where you found the details for sensor configurations for your setup? Trying to work out how to do this for my Supermicro C2SEA, but haven't had any luck so far.

 

Sent from my Nexus 7 using Tapatalk HD

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.

 

Priceless - I will give this a try.

 

Thanks for sharing the info on this :-)

 

Sent from my Nexus 7 using Tapatalk HD

Link to post

given I don't know what the modprobe actually does, I don't know if I even need it in my GO  file.

 

should I try this in my GO file?

modprobe w83627ehf force_id=0x8860

 

I have the C2SEE, which is the same chipset as the C2SEA.

 

Ok, I just typed "modprobe w83627ehf force_id=0x8860" at the command prompt, and then typed sensors.  I got a ton more data,

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.

 

Link to post

In addition to my previous post, the emhttp process is still running. However, I have two emhttp running.

 

root@Tower:~# lsof -i -n -P
COMMAND     PID   USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
emhttp    10697   root    3u  IPv4   18237      0t0  TCP *:80 (LISTEN)
emhttp    10697   root    5u  IPv4 1423451      0t0  TCP 192.168.178.24:80->192.168.178.29:56963 (ESTABLISHED)

Link to post

given I don't know what the modprobe actually does, I don't know if I even need it in my GO  file.

 

should I try this in my GO file?

modprobe w83627ehf force_id=0x8860

 

I have the C2SEE, which is the same chipset as the C2SEA.

 

Ok, I just typed "modprobe w83627ehf force_id=0x8860" at the command prompt, and then typed sensors.  I got a ton more data,

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.

 

 

Ok I did all of that.  I edited the sensors.conf file, changed the chip line to what you put above.  I then copied to /boot/etc/sensors.d/  I then ran the modprobe command.  I then typed sensors and got this:

 

root@Tower:/etc/sensors.d# cp /boot/custom/sensors.d/sensors.conf /etc/sensors.d

root@Tower:/etc/sensors.d# ls

sensors.conf*

root@Tower:/etc/sensors.d# modprobe w83627ehf force_id=0x8860

root@Tower:/etc/sensors.d# sensors

coretemp-isa-0000

Adapter: ISA adapter

Core 0:      +44.0 C  (high = +76.0 C, crit = +100.0 C)

Core 1:      +44.0 C  (high = +76.0 C, crit = +100.0 C)

Core 2:      +37.0 C  (high = +76.0 C, crit = +100.0 C)

Core 3:      +40.0 C  (high = +76.0 C, crit = +100.0 C)

 

w83627ehf-isa-0290

Adapter: ISA adapter

Vcore:        +1.12 V  (min =  +0.92 V, max =  +1.48 V)

in1:          +1.85 V  (min =  +1.65 V, max =  +1.99 V)

AVCC:        +3.33 V  (min =  +2.96 V, max =  +3.63 V)

+3.3V:        +3.33 V  (min =  +1.09 V, max =  +0.83 V)  ALARM

in4:          +1.57 V  (min =  +1.35 V, max =  +1.65 V)

in5:          +1.27 V  (min =  +1.13 V, max =  +1.38 V)

in6:          +1.43 V  (min =  +1.42 V, max =  +1.52 V)

3VSB:        +3.33 V  (min =  +2.96 V, max =  +3.63 V)

Vbat:        +3.26 V  (min =  +2.96 V, max =  +3.63 V)

in9:          +0.00 V  (min =  +1.24 V, max =  +1.33 V)  ALARM

fan1:        1814 RPM  (min =  712 RPM, div = 8)

fan2:        2057 RPM  (min =  712 RPM, div = 8)

fan3:        1163 RPM  (min =  712 RPM, div = 8)

fan4:        1125 RPM  (min =  712 RPM, div = 8)

fan5:        1028 RPM  (min =  712 RPM, div = 8)

temp1:        +37.0 C  (high = +60.0 C, hyst = +55.0 C)  sensor = thermistor

temp2:        +36.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = CPU diode

temp3:        +0.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = CPU diode

cpu0_vid:    +1.513 V

intrusion0:  ALARM

 

root@Tower:/etc/sensors.d#

 

I didn't rebootyet, but still no readings in SF Main page.

Link to post

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.

 

Link to post

You are the man!  I have temps now in my SF Main page!

 

I changed the labels like you said in the sensors.conf file.  I also changed the GO file to say, modprobe w83627ehf.

 

I think I'm good to go.  Here is what the sensors command says now,

 

root@Tower:~# sensors

coretemp-isa-0000

Adapter: ISA adapter

Core 0:      +46.0 C  (high = +76.0 C, crit = +100.0 C)

Core 1:      +46.0 C  (high = +76.0 C, crit = +100.0 C)

Core 2:      +38.0 C  (high = +76.0 C, crit = +100.0 C)

Core 3:      +44.0 C  (high = +76.0 C, crit = +100.0 C)

 

w83627ehf-isa-0290

Adapter: ISA adapter

3.3V:        +2.24 V  (min =  +1.84 V, max =  +2.96 V)

Vcore:        +1.85 V  (min =  +1.65 V, max =  +1.99 V)

+5V:          +8.23 V  (min =  +7.10 V, max =  +8.65 V)

12V:        +13.99 V  (min = +12.41 V, max = +15.14 V)

3VSB:        +6.66 V  (min =  +5.92 V, max =  +7.26 V)

Battery:      +6.53 V  (min =  +5.92 V, max =  +7.26 V)

in9:          +0.00 V  (min =  +1.24 V, max =  +1.33 V)  ALARM

CPU:        1834 RPM  (min =  712 RPM, div = 8)

System2:    1163 RPM  (min =  712 RPM, div = 8)

fan5:        1028 RPM  (min =  712 RPM, div = 8)

CPU Temp:    +39.0 C  (high = +60.0 C, hyst = +55.0 C)  sensor = thermistor

MB Temp:      +38.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = CPU diode

System:        +0.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = CPU diode

cpu0_vid:    +1.513 V

intrusion0:  ALARM

 

root@Tower:~#

 

and I have this in SF Main page,

 

Thanks!

sensors.jpg.7071f44f528077c2fdc8a071947c20ed.jpg

Link to post

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.

Link to post

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.

 

Thanks again.  I'm not clear on what to do regarding tweaking the conf file to confirm the temps match the bios.  How would I tell?  I just assumed the temp readings are correct, as they seem about right to me.  Any recommendations on how to further confirm the readings are correct?

 

It sure is cool to see readings on the Main page, but I would like to know they are correct.

Link to post

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. :)

 

Thank you for this. I use the same motherboard and this worked, though I tweaked it a little. I'm not sure labeling the temp from the k10temp sensor AND the it8721 sensor as CPU Temp is the right thing to do though. Both temps are obviously different. I renamed them on mine to just have k10temp set as the CPU Temp.

Link to post

It is very likely that your issues lies elsewhere... Simplefeatures is a wrapper around the basic unraid functionality... I have added many drives using it and have not had any issues.. On the other hand, it is quite easy to disable simplefeatures in this way so you can test it yourself.

 

Just move the plg's out of the plugin directory and reboot, do your thing, put them back and reboot again. All your simplefeatures settings will be back.

Link to post

It is very likely that your issues lies elsewhere... Simplefeatures is a wrapper around the basic unraid functionality... I have added many drives using it and have not had any issues.. On the other hand, it is quite easy to disable simplefeatures in this way so you can test it yourself.

 

Just move the plg's out of the plugin directory and reboot, do your thing, put them back and reboot again. All your simplefeatures settings will be back.

 

The only plugin I've got installed are:

-powerdown

-monthly parity check

-airvideo

-jre

-Simple Features

 

My server lost connection via GUI, while preclearing my 3TB drive.  After switching my 2TB to 3TB parity drive, formatting, etc.  I didn't have any control to the server unless I used telnet.  I never had this happened before until I started using Simple Features.

Link to post

i cant access the web interface when i upgraded to 1.0.11 i deleted the old plugins put in the new ones in /boot/plugins

 

i get this in Firefox The connection to the server was reset while the page was loading and in chrome Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.

 

when i remove these plugins the default web interface is back

Link to post

i am on unraid 5rc11

Mem:  1813184k total,  347636k used,  1465548k free,      124k buffers

 

is that to little ram?

 

when i try start ehttp like in the go file it says this

 

error while loading shared libraries: libcrypto.so.0: cannot open shared object file: No such file or directory

Link to post

Thank you for this. I use the same motherboard and this worked, though I tweaked it a little. I'm not sure labeling the temp from the k10temp sensor AND the it8721 sensor as CPU Temp is the right thing to do though. Both temps are obviously different. I renamed them on mine to just have k10temp set as the CPU Temp.

 

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.

 

Link to post
  • Squid locked this topic
Guest
This topic is now closed to further replies.