Jump to content
bonienl

Dynamix - V6 Plugins

2476 posts in this topic Last Reply

Recommended Posts

I just updated, and now I don't have any temps, and none of the dropdowns allow me to select them.  I can find the driver okay, but now can't select anything.

Share this post


Link to post

I just updated, and now I don't have any temps, and none of the dropdowns allow me to select them.  I can find the driver okay, but now can't select anything.

 

After 'detect' you must 'save' the driver names.

Share this post


Link to post

Looks like it is only detecting "coretemp" for me. There was some recent change in the detect script that finally made it work to find "nct6791" on my MB, but looks like it is not working with this. So I will not "Save" since I do have readings now and I expect if I save I will be back to having only coretemp.

Share this post


Link to post

I didn't even notice the detect button changed to save.  i tried hitting apply and load, but they obviously didn't work.

 

hitting save did work  :D

 

I have 4 cores, all showing in the list, and something else at the top of the list.  I can't remember what it said, since after saving it to the processor temp, it changed what it had showed before.  Anyway, I'm not sure which one is my MB and which one is my CPU (or why the 4 cores seem to vary by as much as 3 degrees.)  I also don't have any fan speed info, even though the motherboard does provide the info.

 

Not a big deal, just providing feedback.

 

Thanks again.

Share this post


Link to post

Looks like it is only detecting "coretemp" for me. There was some recent change in the detect script that finally made it work to find "nct6791" on my MB, but looks like it is not working with this. So I will not "Save" since I do have readings now and I expect if I save I will be back to having only coretemp.

 

You can add the "nct6791" name in the driver field and then save. It allows you to load the module manually in the next step.

 

Btw did you use a newer version of sensors-detect previously, because that script hasn't changed (plugin relies on the version installed together with unRAID).

 

Share this post


Link to post

I also only get coretemp.  How would I know what driver I should have for my motherboard?

 

The 'sensors-detect' script is used to find the available drivers, the names of these drivers appear only when the actual module is present (a check is made).

 

You can run sensors-detect in a telnet session and see its output directly. Sometimes it is possible to use an alternative driver to the one 'detected' by sensors-detect, see therefore the website.

Share this post


Link to post

I have 4 cores, all showing in the list, and something else at the top of the list.  I can't remember what it said, since after saving it to the processor temp, it changed what it had showed before.  Anyway, I'm not sure which one is my MB and which one is my CPU (or why the 4 cores seem to vary by as much as 3 degrees.)

 

What is what can not be automatically detected, just what sensors are present. You need to choose what is most likely the CPU and MB, or decide not to use it.

 

I also don't have any fan speed info, even though the motherboard does provide the info.

 

Do you mean no fan speed is shown ('##') eventhough a probe is selected or do you expect to see fan probes in the dropdown menu which are not present ?

 

Share this post


Link to post

...or do you expect to see fan probes in the dropdown menu which are not present ?

 

This.  There is nothing in the dropdown.  There is nothing in the fanspeed status bar (as expected).

 

None of this is a big deal to me, I'm just reporting my findings, to hopefully help with development.

Share this post


Link to post

...  I can't remember what it said, since after saving it to the processor temp, it changed what it had showed before.

 

When "Not used" is selected and applied, it will show the original text again for previously selected probe!

 

(thought to mention it in case someone is curious).

Share this post


Link to post

Ah, yes, that did it.  Attached is the dropdown after 'resetting'...

 

I'm assuming the top one is the MB, and will just pick one of the cores as the CPU temp.

 

One of these days, I'll try to figure out which driver will give me fan speeds also.

 

thanks again!

temps.png.0bef96db8947ee6789b802eb9a12efa6.png

Share this post


Link to post

Looks like it is only detecting "coretemp" for me. There was some recent change in the detect script that finally made it work to find "nct6791" on my MB, but looks like it is not working with this. So I will not "Save" since I do have readings now and I expect if I save I will be back to having only coretemp.

 

You can add the "nct6791" name in the driver field and then save. It allows you to load the module manually in the next step.

 

Btw did you use a newer version of sensors-detect previously, because that script hasn't changed (plugin relies on the version installed together with unRAID).

I am using the sensors-detect.sh from here, so not the one built-in to unRAID.

Share this post


Link to post

I updated to the latest from the plugin settings and now everything is busted.

 

I clicked on 'detect' and waited until that came back. After two minutes the following is shown with absolutely nothing available in any of the drop-down boxes to select from. The Load drivers and Add to Startup buttons do nothing. The only buttons that do anything are Apply and Done.

 

dynamix_system_temp_busted.png.78f59af9516ab225623479c5531556d2.png

Share this post


Link to post

FYI: here is the result of the following command that seems to be invoked from the page. As you can see nothing matched on the awk statement.

 

#  yes ''|/usr/sbin/sensors-detect 2>&1|awk '/^modprobe/{print $2}'
#

 

Now output of "sensors"

# sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +27.8 C  (crit = +95.0 C)
temp2:        +29.8 C  (crit = +95.0 C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +28.0 C  (high = +74.0 C, crit = +94.0 C)
Core 0:         +24.0 C  (high = +74.0 C, crit = +94.0 C)
Core 1:         +25.0 C  (high = +74.0 C, crit = +94.0 C)
Core 2:         +26.0 C  (high = +74.0 C, crit = +94.0 C)
Core 3:         +24.0 C  (high = +74.0 C, crit = +94.0 C)

 

Contents of lm_sensors:

# cat /etc/sysconfig/lm_sensors
# Generated by sensors-detect on Tue Feb  3 17:52:45 2015
# This file is sourced by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded.
#
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).

HWMON_MODULES="coretemp"

 

Share this post


Link to post

BRiT, please try this:

 

yes ''|perl /usr/sbin/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*"

Share this post


Link to post

BRiT, please try this:

 

yes ''|perl /usr/sbin/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*"

 

That results in finding the 2 drivers, where one is yet to-be-written.  :)

~# yes ''|perl /usr/sbin/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*"
coretemp
to-be-written

Share this post


Link to post

BRiT, please try this:

 

yes ''|perl /usr/sbin/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*"

 

That results in finding the 2 drivers, where one is yet to-be-written.  :)

~# yes ''|perl /usr/sbin/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*"
coretemp
to-be-written

 

Try again with the svn version:

 

wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect
yes ''|perl /tmp/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*"

Share this post


Link to post

BRiT, please try this:

 

yes ''|perl /usr/sbin/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*"

 

That results in finding the 2 drivers, where one is yet to-be-written.  :)

~# yes ''|perl /usr/sbin/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*"
coretemp
to-be-written

 

Try again with the svn version:

 

wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect
yes ''|perl /tmp/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*"

 

Similar results, but when I put the change into the dynamix page setting I get 1 more to select in the dropdown (acpitz)

 

wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect
--2015-02-03 19:02:16--  http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect
Resolving www.lm-sensors.org (www.lm-sensors.org)... 160.45.254.26
Connecting to www.lm-sensors.org (www.lm-sensors.org)|160.45.254.26|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 209836 (205K) [text/plain]
Saving to: ‘/tmp/sensors-detect’

100%[=====================================================>] 209,836      172KB/s   in 1.2s

2015-02-03 19:02:18 (172 KB/s) - ‘/tmp/sensors-detect’ saved [209836/209836]

# yes ''|perl /tmp/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*"
to-be-written
coretemp

 

For completeness, here's the patched changes into TempSettings.page

function detect_modules(){
  $mods = array();
  exec("yes ''|perl /usr/sbin/sensors-detect 2>&1|grep -Po \"^Driver.{2}\K[^\']*\"", $matches);
  foreach ($matches as $mod) if (exec("modprobe -D $mod 2>/dev/null")) $mods[]=$mod ;
  return $mods;
}

dynamix_temp_patched.png.c9baaae58cbdae86df710df8921073b5.png

Share this post


Link to post

Out of curiosity (and trying to understand what is happening), can you post the output of

 

yes ''|sensors-detect

 

How long does it take for the command to complete on your system ?

 

Share this post


Link to post

Out of curiosity (and trying to understand what is happening), can you post the output of

 

yes ''|sensors-detect

 

How long does it take for the command to complete on your system ?

 

It takes anywhere from 2 to 3 minutes to complete all because of the 1 sensor it's trying to probe. I'll have that output in a couple minutes.  ;)

Share this post


Link to post

Out of curiosity (and trying to understand what is happening), can you post the output of

 

yes ''|sensors-detect

 

How long does it take for the command to complete on your system ?

 

It takes anywhere from 2 to 3 minutes to complete all because of the 1 sensor it's trying to probe. I'll have that output in a couple minutes.  ;)

 

The part that takes the 2-3 minutes is this driver:

Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH)

 

The real driver that I used when I ran my own kernel on full slackware64bit was ipmi (something), which I have asked to be compiled and included in the next unRAID release.

 

And now the full output...

 

# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# System: TYAN S5512 [empty]

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT5577D/NCT6776F Super IO Sensors'          
    (but not activated)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): Found `IPMI BMC KCS' at 0xca8...                            Success!
    (confidence 8, driver `to-be-written')

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH)

Now follows a summary of the probes I have just done.
Just press ENTER to continue: 
Driver `to-be-written':
  * ISA bus, address 0xca8
    Chip `IPMI BMC KCS' (confidence: 

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Note: there is no driver for IPMI BMC KCS yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.

 

 

Share this post


Link to post

Hmm, I was just prompted to update to the 2015.02.03 version of Dynamix System Temperature, and the /Settings/TempSettings page no longer works.

 

The "available drivers" is empty by default, although if I click "Detect" it does display the correct ones (coretemp nct6775).  Load / Add to Startup don't seem to do anything, but my go script already contains them, so nothing additional should be needed:

 

modprobe coretemp
modprobe nct6775
/usr/bin/sensors -s

 

All of the dropdowns on the page are disabled, and nothing I do allows me to select anything:

 

<select name="cpu_temp" disabled>

 

I made the mistake of hitting "Apply" and all of the values changed to "not used" when the page reloaded, and the temperatures disappeared from the footer. 

 

The dropdowns are still disabled, although when I view the source of the page the correct values are listed, I just can't choose them:

<select name="cpu_temp" disabled>
<option>Not used</option>
<option value='coretemp-isa-0000|temp1|CPU Temp' >coretemp - Physical id 0 - 37.0 °C</option>
<option value='coretemp-isa-0000|temp2|CPU Temp' >coretemp - Core 0 - 37.0 °C</option>
<option value='coretemp-isa-0000|temp3|CPU Temp' >coretemp - Core 1 - 34.0 °C</option>
<option value='coretemp-isa-0000|temp4|CPU Temp' >coretemp - Core 2 - 33.0 °C</option>
<option value='coretemp-isa-0000|temp5|CPU Temp' >coretemp - Core 3 - 36.0 °C</option>
<option value='nct6776-isa-0290|temp1|CPU Temp' >nct6776 - SYSTIN - 35.0 °C</option>
<option value='nct6776-isa-0290|temp2|CPU Temp' >nct6776 - CPUTIN - 37.0 °C</option>
<option value='nct6776-isa-0290|temp3|CPU Temp' >nct6776 - AUXTIN - 26.0 °C</option>
</select>

 

Hopefully that is enough information to help figure out what happened?

Share this post


Link to post

Hmm, I was just prompted to update to the 2015.02.03 version of Dynamix System Temperature, and the /Settings/TempSettings page no longer works.

 

The "available drivers" is empty by default, although if I click "Detect" it does display the correct ones (coretemp nct6775).  Load / Add to Startup don't seem to do anything, but my go script already contains them, so nothing additional should be needed:

 

modprobe coretemp
modprobe nct6775
/usr/bin/sensors -s

 

All of the dropdowns on the page are disabled, and nothing I do allows me to select anything:

 

<select name="cpu_temp" disabled>

 

I made the mistake of hitting "Apply" and all of the values changed to "not used" when the page reloaded, and the temperatures disappeared from the footer. 

 

The dropdowns are still disabled, although when I view the source of the page the correct values are listed, I just can't choose them:

<select name="cpu_temp" disabled>
<option>Not used</option>
<option value='coretemp-isa-0000|temp1|CPU Temp' >coretemp - Physical id 0 - 37.0 °C</option>
<option value='coretemp-isa-0000|temp2|CPU Temp' >coretemp - Core 0 - 37.0 °C</option>
<option value='coretemp-isa-0000|temp3|CPU Temp' >coretemp - Core 1 - 34.0 °C</option>
<option value='coretemp-isa-0000|temp4|CPU Temp' >coretemp - Core 2 - 33.0 °C</option>
<option value='coretemp-isa-0000|temp5|CPU Temp' >coretemp - Core 3 - 36.0 °C</option>
<option value='nct6776-isa-0290|temp1|CPU Temp' >nct6776 - SYSTIN - 35.0 °C</option>
<option value='nct6776-isa-0290|temp2|CPU Temp' >nct6776 - CPUTIN - 37.0 °C</option>
<option value='nct6776-isa-0290|temp3|CPU Temp' >nct6776 - AUXTIN - 26.0 °C</option>
</select>

 

Hopefully that is enough information to help figure out what happened?

 

After you hit [Detect] did you hit [save]? The detect button switches to save after it's finished.

Share this post


Link to post

After you hit [Detect] did you hit [save]? The detect button switches to save after it's finished.

 

Oh dang, you're right.  Thanks, it is working now.

 

Share this post


Link to post

After you hit [Detect] did you hit [save]? The detect button switches to save after it's finished.

 

Oh dang, you're right.  Thanks, it is working now.

 

There was an internal change in the plugin, which requires the drivers to be selected and saved first, this information is stored in a file next to the existing file for the selected sensors. This is a one time operation only,unless new drivers are made available of course.

 

I understand it may confuse people expecting to do the upgrade without further actions.

 

 

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.