"SimpleFeatures" Plugin - Version 1.0.11



2848 posts in this topic Last Reply

Recommended Posts

Thx to dmacias and switchblade i got my temp readings working on x9scm-f with core i3 2120T cpu.

 

My go file addition:

 

modprobe w83627ehf
cp /boot/custom/sensors.d/sensors.conf /etc/sensors.d
cp /boot/custom/sensors.d/sensors.conf /etc/sensors3.conf

 

My /boot/custom/sensors.d/sensors.conf file:

 

chip "w83627ehf-*" "w83627dhg-*" "w83667hg-*" "nct6775-*" "nct6776-*"

    label in0 "Vcore"
    label in2 "AVCC"
    label in3 "+3.3V"
    label in7 "3VSB"
    label in8 "Vbat"
    label temp2 "CPU Temp"
    label temp1 "MB Temp"

    set in2_min  3.3 * 0.90
    set in2_max  3.3 * 1.10
    set in3_min  3.3 * 0.90
    set in3_max  3.3 * 1.10
    set in7_min  3.3 * 0.90
    set in7_max  3.3 * 1.10
    set in8_min  3.0 * 0.90
    set in8_max  3.3 * 1.10

 

SF now shows the correct temp readings. Great :)

 

Thank you very much! Worked like a charm!!!!

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

Top Posters In This Topic

Thx to dmacias and switchblade i got my temp readings working on x9scm-f with core i3 2120T cpu.

 

My go file addition:

 

modprobe w83627ehf
cp /boot/custom/sensors.d/sensors.conf /etc/sensors.d
cp /boot/custom/sensors.d/sensors.conf /etc/sensors3.conf

 

My /boot/custom/sensors.d/sensors.conf file:

 

chip "w83627ehf-*" "w83627dhg-*" "w83667hg-*" "nct6775-*" "nct6776-*"

    label in0 "Vcore"
    label in2 "AVCC"
    label in3 "+3.3V"
    label in7 "3VSB"
    label in8 "Vbat"
    label temp2 "CPU Temp"
    label temp1 "MB Temp"

    set in2_min  3.3 * 0.90
    set in2_max  3.3 * 1.10
    set in3_min  3.3 * 0.90
    set in3_max  3.3 * 1.10
    set in7_min  3.3 * 0.90
    set in7_max  3.3 * 1.10
    set in8_min  3.0 * 0.90
    set in8_max  3.3 * 1.10

 

SF now shows the correct temp readings. Great :)

 

Thank you very much! Worked like a charm!!!!

 

Worked great for me too!  Thanks!

Link to post

@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.

Link to post

@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've seen this too, but some people claim to have issues with the machines freezing.

 

I'll enable it to see what happens anyway...

Link to post

@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've seen this too, but some people claim to have issues with the machines freezing.

 

I'll enable it to see what happens anyway...

I have to use this on one of my builds, it never freezes.

 

Sent from my A510 using Tapatalk HD

Link to post

@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've seen this too, but some people claim to have issues with the machines freezing.

 

I'll enable it to see what happens anyway...

I have to use this on one of my builds, it never freezes.

 

Sent from my A510 using Tapatalk HD

 

Seems to have cracked the sensor problem, now just got to see if it freezes!

 

Here is my sensors.conf for Asus P8B-WS with Core i3-3220.

 


# nct6776 values for Asus P8B WS

chip "coretemp-isa-0000"

label temp1 "CPU Temp"

chip "nct6775-*" "nct6776-*"

    label in0 "Vcore"
    set in0_min 1 * 0.8
    set in0_max 1 * 1.2
    
    ignore in1
    
    label in2 "AVCC"
    set in2_min  3.3 * 0.95
    set in2_max  3.3 * 1.05
    
    label in3 "+3.3V"
    set in3_min  3.3 * 0.95
    set in3_max  3.3 * 1.05
    
    ignore in4
    ignore in5
    
    label in7 "3VSB"
    set in7_min  3.3 * 0.95
    set in7_max  3.3 * 1.05

    label in8 "Vbat"
    set in8_min  3.3 * 0.95
    set in8_max  3.3 * 1.05
    
    ignore cpu0_vid
    
    ignore fan1
    label fan2 "Exhaust"
    set fan2_min 1000
    ignore fan3
    ignore fan4
    ignore fan5

    label temp1 "MB Temp"
    set temp1_max 60
    set temp1_max_hyst 55
    
    ignore temp2
    ignore temp3
    ignore temp4
    
    ignore intrusion0
    ignore intrusion1

 

 

Link to post

first of all, thx for a great set of plugins! love it generally... now to the but,

(i have to say i just installed -most- of the plugins some hours ago)... anyway, BUT

is it normal that one of my hdd's (size 3tb) suddenly goes overboard and believes it has 8.98tb and 2.99tb free and the other one of this share (also 3tb) has 3tb used and 3.99tb free?

just the one user share. i mean i would love that kind of magic hdd space explosion, it just seems extremely odd

 

 

Link to post

first of all, thx for a great set of plugins! love it generally... now to the but,

(i have to say i just installed -most- of the plugins some hours ago)... anyway, BUT

is it normal that one of my hdd's (size 3tb) suddenly goes overboard and believes it has 8.98tb and 2.99tb free and the other one of this share (also 3tb) has 3tb used and 3.99tb free?

just the one user share. i mean i would love that kind of magic hdd space explosion, it just seems extremely odd

Screenshot?

Link to post

@ speeding_ant & bonienl

 

Can I ask why it is in the plugin "simpleFeatures.email.notify-1.0.10-noarch-1.plg" you are choosing to delete /usr/include?  I've just spent an hour trying to understand why both nzbget and Denyhosts plugins are no longer working after installing your plugin.  In the case of DenyHosts, it's because standard python2.6.6 files reside under this location. 

 

root@Eddie:/tmp/DenyHosts-2.6# python setup.py install

running install

error: invalid Python installation: unable to open /usr/include/python2.6/pyconfig.h (No such file or directory)

 

In the case of nzbget it's because libpar and libsigc++ packages install to this location.

 

drwxr-xr-x  2 root root 0 2013-03-05 08:11 libpar2/

drwxr-xr-x  2 root root 0 2010-11-27 17:49 python2.6/

drwxr-xr-x  3 root root 0 2010-05-16 07:24 sigc++-2.0/

 

I see no reason why this location needs to be removed via your script.  Please can you advise whether this is intentional and the rationale behind it as at the moment it's killing other plugins and likely impacting on anything which relies on running "python setup.py install".

 

 

EDIT: perhaps unless you have an objection, the plugin is changed with prune set to false by default.  I don't think it should be up to the plugin to automatically decide for the user what directories are classed as unimportant and safe to remove.

 

<!ENTITY prune "true"><!-- set to "false" to suppress pruning -->

 

if [ "&prune;" == "true" ]; then

  rm -rf /usr/doc

  rm -rf /usr/include

  rm -rf /usr/info

  rm -rf /usr/man

fi

 

 

Regards,

overbyrn

 

Link to post

Found something strange. Installed v5-rc11 with simplefeatures 1.05 still on the system, and all worked fine. Parity check was at about 120-140MB/s average for about half an hour. After that i replaced SF 1.05 with 1.0.11, rebooted, and started a parcheck again, but this time it couldnt get above 30MB/s... that is way too slow. So, i removed SF 1.0.11 plugins, rebooted again without SF, and the parcheck was back at 140MB/s...

 

Why does SF has such a big negative influence on parity check?

Link to post

Found something strange. Installed v5-rc11 with simplefeatures 1.05 still on the system, and all worked fine. Parity check was at about 120-140MB/s average for about half an hour. After that i replaced SF 1.05 with 1.0.11, rebooted, and started a parcheck again, but this time it couldnt get above 30MB/s... that is way too slow. So, i removed SF 1.0.11 plugins, rebooted again without SF, and the parcheck was back at 140MB/s...

 

Why does SF has such a big negative influence on parity check?

 

Could this be something to do with the 'blinking activity lights' that others report when the SF 1.0.11 gui is open? Sounds like something is polling the disks, which as I understand it could effect parity check speed.

 

Perhaps a more experienced user can chime in... I'm only going on what I recall reading here and there  ;)

Link to post

Found something strange. Installed v5-rc11 with simplefeatures 1.05 still on the system, and all worked fine. Parity check was at about 120-140MB/s average for about half an hour. After that i replaced SF 1.05 with 1.0.11, rebooted, and started a parcheck again, but this time it couldnt get above 30MB/s... that is way too slow. So, i removed SF 1.0.11 plugins, rebooted again without SF, and the parcheck was back at 140MB/s...

 

Why does SF has such a big negative influence on parity check?

 

Could this be something to do with the 'blinking activity lights' that others report when the SF 1.0.11 gui is open? Sounds like something is polling the disks, which as I understand it could effect parity check speed.

 

Perhaps a more experienced user can chime in... I'm only going on what I recall reading here and there  ;)

I almost posted the same thing.  I remember Tom (limetech) saying (in a post I can't find) that polling the drives was a bad idea - at least with RC10/11 and up anyway.
Link to post

How often do you run a parity check? Im using simplefeatures and even if it slow, I just accept it cause I do not really run parity check that often and never noticed, lol. Seems to me this plugin is getting updated less and less often than it was in the beginning. Maybe time to stop using it even though it is awesome.

Link to post

How often do you run a parity check? Im using simplefeatures and even if it slow, I just accept it cause I do not really run parity check that often and never noticed, lol. Seems to me this plugin is getting updated less and less often than it was in the beginning. Maybe time to stop using it even though it is awesome.

 

I run it at least once a month.  This month I ran it 3 times due to updating parity, and other drives, and adding a new SAS card.  It took forever.  When I was doing the parity check I wasn't able to access any of my videos.  My wife and kids were pretty upset with that.  I also lost connection to the server when I was doing this.  I could only access it via telnet.  So, I had to delete it, and now everything is back to normal.

 

I am with you though.  I like the looks and features of Simple Features.

Link to post

I run a check once a month. But besides that, for me its speed is a measure for the functioning of unraid as a whole. Simply said, if the check is slow, something is wrong...

 

Its like your car dont getting over 30mph while it should do 100, and you dont care because you dont use the car on the freeway anyway, or you are never in a hurry. its just wrong, It should function 100%, whether you use it or not.

Link to post

Dear dmacias

 

i have Gigabyte H77-DS3H with it8728f

 

when i write "sensors" i get this

Linux 3.4.26-unRAID.
root@server:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +35.0 C  (high = +80.0 C, crit = +99.0 C)
Core 0:         +34.0 C  (high = +80.0 C, crit = +99.0 C)
Core 1:         +34.0 C  (high = +80.0 C, crit = +99.0 C)
Core 2:         +32.0 C  (high = +80.0 C, crit = +99.0 C)
Core 3:         +27.0 C  (high = +80.0 C, crit = +99.0 C)

it8728-isa-0a30
Adapter: ISA adapter
in0:          +1.07 V  (min =  +0.00 V, max =  +3.06 V)
in1:          +2.05 V  (min =  +0.00 V, max =  +3.06 V)
in2:          +2.05 V  (min =  +0.00 V, max =  +3.06 V)
in3:          +2.02 V  (min =  +0.00 V, max =  +3.06 V)
in4:          +0.46 V  (min =  +0.00 V, max =  +3.06 V)
in5:          +0.88 V  (min =  +0.00 V, max =  +3.06 V)
in6:          +1.52 V  (min =  +0.00 V, max =  +3.06 V)
3VSB:         +3.36 V  (min =  +0.00 V, max =  +6.12 V)
Vbat:         +3.31 V
fan1:        1169 RPM  (min =   10 RPM)
fan2:           0 RPM  (min =    0 RPM)
fan3:           0 RPM  (min =    0 RPM)
fan4:           0 RPM  (min =    0 RPM)
fan5:           0 RPM  (min =    0 RPM)
temp1:        +32.0 C  (low  = +127.0 C, high = +127.0 C)  sensor = thermistor
temp2:        +25.0 C  (low  = +127.0 C, high = +127.0 C)  sensor = thermistor
temp3:        +26.0 C  (low  =  +0.0 C, high = +70.0 C)  sensor = disabled
intrusion0:  ALARM

 

when i write "sensors -u" i get this

root@server:~# sensors -u
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:
  temp1_input: 34.000
  temp1_max: 80.000
  temp1_crit: 99.000
  temp1_crit_alarm: 0.000
Core 0:
  temp2_input: 34.000
  temp2_max: 80.000
  temp2_crit: 99.000
  temp2_crit_alarm: 0.000
Core 1:
  temp3_input: 32.000
  temp3_max: 80.000
  temp3_crit: 99.000
  temp3_crit_alarm: 0.000
Core 2:
  temp4_input: 33.000
  temp4_max: 80.000
  temp4_crit: 99.000
  temp4_crit_alarm: 0.000
Core 3:
  temp5_input: 27.000
  temp5_max: 80.000
  temp5_crit: 99.000
  temp5_crit_alarm: 0.000

it8728-isa-0a30
Adapter: ISA adapter
in0:
  in0_input: 1.068
  in0_min: 0.000
  in0_max: 3.060
  in0_alarm: 0.000
  in0_beep: 0.000
in1:
  in1_input: 2.052
  in1_min: 0.000
  in1_max: 3.060
  in1_alarm: 0.000
  in1_beep: 0.000
in2:
  in2_input: 2.052
  in2_min: 0.000
  in2_max: 3.060
  in2_alarm: 0.000
  in2_beep: 0.000
in3:
  in3_input: 2.016
  in3_min: 0.000
  in3_max: 3.060
  in3_alarm: 0.000
  in3_beep: 0.000
in4:
  in4_input: 0.456
  in4_min: 0.000
  in4_max: 3.060
  in4_alarm: 0.000
  in4_beep: 0.000
in5:
  in5_input: 0.876
  in5_min: 0.000
  in5_max: 3.060
  in5_alarm: 0.000
  in5_beep: 0.000
in6:
  in6_input: 1.524
  in6_min: 0.000
  in6_max: 3.060
  in6_alarm: 0.000
  in6_beep: 0.000
3VSB:
  in7_input: 3.360
  in7_min: 0.000
  in7_max: 6.120
  in7_alarm: 0.000
  in7_beep: 0.000
Vbat:
  in8_input: 3.312
fan1:
  fan1_input: 1169.000
  fan1_min: 10.000
  fan1_alarm: 0.000
  fan1_beep: 1.000
fan2:
  fan2_input: 0.000
  fan2_min: 0.000
  fan2_alarm: 0.000
  fan2_beep: 1.000
fan3:
  fan3_input: 0.000
  fan3_min: 0.000
  fan3_alarm: 0.000
  fan3_beep: 1.000
fan4:
  fan4_input: 0.000
  fan4_min: 0.000
  fan4_alarm: 0.000
  fan4_beep: 1.000
fan5:
  fan5_input: 0.000
  fan5_min: 0.000
  fan5_alarm: 0.000
  fan5_beep: 1.000
temp1:
  temp1_input: 31.000
  temp1_max: 127.000
  temp1_min: 127.000
  temp1_alarm: 0.000
  temp1_type: 4.000
  temp1_beep: 1.000
temp2:
  temp2_input: 25.000
  temp2_max: 127.000
  temp2_min: 127.000
  temp2_alarm: 0.000
  temp2_type: 4.000
  temp2_beep: 1.000
temp3:
  temp3_input: 25.000
  temp3_max: 70.000
  temp3_min: 0.000
  temp3_alarm: 0.000
  temp3_type: 0.000
  temp3_beep: 1.000
intrusion0:
  intrusion0_alarm: 1.000

root@server:~#

 

i created the folowing folders at the root folder of the flash drive

etc/sensor.d

then i put the sensors.conf in the sensor.d folder

my sensors.conf is

chip "it8728-*"

    label in0 "Vtt"
    set in0_min 1.02    # I'm liberal with these, 2-3% tops
    set in0_max 1.08    # after that, cpu gets very unstable

    ignore in1
#   label in1 "+3.3V"
#   set in1_min 3.14    # Some boards including GA-H67MA-UD2H
#   set in1_max 3.47    # don't have 3.3V voltage reading

    label in2 "+12V"
    set in2_min 11.40   # according to ATX 12V PSU design guide
    set in2_max 12.60   #

    ignore in3          # reports 3VSB

    ignore in4          # really don't know what's this one for

    label in5 "Vcore"
    set in5_min 0.65
    set in5_max 1.50    # heavy o/c

    label in6 "Vdram"
    set in6_min 1.45    # adjust these, 1.35 for LVDDR3
    set in6_max 1.55    # 1.5V is recommended, 1.65 tops
     
    label in7 "3VSB"
    set in7_min 3.14
    set in7_max 3.47

    label in8 "Vbat"

    label fan1 "CPU fan"
    set fan1_min 700

    label fan2 "System fan"
    set fan2_min 0

label temp1 "CPU Temp"
    set temp1_min 10
    set temp1_max 60    # seen those rising to 55C

    label temp2 "MB Temp"
    set temp2_min 10
    set temp2_max 85

    ignore temp3

    compute in1 1.649*@,@/1.649 # multipliers provided by 
    compute in2 4.090*@,@/4.090 # Martin Malik author of hwinfo

 

 

i added this in my go file

 

#Update Sensors

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

modprobe it87

 

and still can not see the temp

 

i will appreciate it if you help me to show my temp in SF

 

thank you.

Link to post

first of all, thx for a great set of plugins! love it generally... now to the but,

(i have to say i just installed -most- of the plugins some hours ago)... anyway, BUT

is it normal that one of my hdd's (size 3tb) suddenly goes overboard and believes it has 8.98tb and 2.99tb free and the other one of this share (also 3tb) has 3tb used and 3.99tb free?

just the one user share. i mean i would love that kind of magic hdd space explosion, it just seems extremely odd

Screenshot?

sorry at the time you ask for a screenshot i had already uninstalled, reinstalled and narrowed the prob down to one user share/ 2 drives. it seemed to have to do with the fact that one of the drives was just 'loaded' with nearly zero space (a screw-up on my end while setting up the share). after solving that and reinstall sofar no more probs.

was hoping my drives just grow magically... ohh well, one can dream :)

Link to post

I would also like to get the sensors working on both of my X9SCM-F boards. Instead of everyone posting in here asking for help would it be possible for someone with some knowledge on the subject to create a separate thread with a how to or maybe put it in the wiki? If I knew exactly what to do I would gladly create it, but it seems I am in the same boat as a few others.

Link to post

Dear dmacias

 

i have Gigabyte H77-DS3H with it8728f

and still can not see the temp

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-*").

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