Dynamix - V6 Plugins

ColonialRaptor · August 8, 2015

Howdy guys... I'm probably being really stupid here but I just don't understand what I'm doing wrong.

When trying to install any of the new plugins I get this happen and then the plugin doesn't appear to work?

bonienl · August 8, 2015

What is required to get Auto Fan Control working? My system has a SuperMicro X10SLL-F mobo that supports PWM fan speed control via IPMI. When I try to auto detect a controller nothing is detected. Is there something else needed for this plugin to work? Maybe something must be configured first?

No nothing else is needed to install. Detect scans the folder /sys/devices and lists all pwm controllers it finds. You can do a manual scan with this command to see what is available for your motherboard:

find /sys/devices -type f -iname 'pwm[0-9]'

bonienl · August 8, 2015

Howdy guys... I'm probably being really stupid here but I just don't understand what I'm doing wrong.

When trying to install any of the new plugins I get this happen and then the plugin doesn't appear to work?

The proper way of installation is to copy and paste the URL links in the OT one-by-one and put them in the installation box (2nd tab of the plugins page). Click install to start installation

ColonialRaptor · August 8, 2015

Howdy guys... I'm probably being really stupid here but I just don't understand what I'm doing wrong.

When trying to install any of the new plugins I get this happen and then the plugin doesn't appear to work?

The proper way of installation is to copy and paste the URL links in the OT one-by-one and put them in the installation box (2nd tab of the plugins page). Click install to start installation

That is exactly what I did!

RobJ · August 8, 2015

I believe I've seen similar in the Docker world here, make sure your DNS is configured and working. One test is to ping google.com at a command prompt.

ColonialRaptor · August 8, 2015

I believe I've seen similar in the Docker world here, make sure your DNS is configured and working. One test is to ping google.com at a command prompt.

My DNS is definitely configured and working.

wgstarks · August 8, 2015

What is required to get Auto Fan Control working? My system has a SuperMicro X10SLL-F mobo that supports PWM fan speed control via IPMI. When I try to auto detect a controller nothing is detected. Is there something else needed for this plugin to work? Maybe something must be configured first?

No nothing else is needed to install. Detect scans the folder /sys/devices and lists all pwm controllers it finds. You can do a manual scan with this command to see what is available for your motherboard:
find /sys/devices -type f -iname 'pwm[0-9]'

That doesn't seem to do anything-

maggie:~ wgstarks$ telnet 10.0.1.20
Trying 10.0.1.20...
Connected to 10.0.1.20.
Escape character is '^]'.
Password: 
Login incorrect

Brunnhilde login: root
Linux 4.0.4-unRAID.
root@Brunnhilde:~# find /sys/devices -type f -iname 'pwm[0-9]'
root@Brunnhilde:~#

Frank1940 · August 8, 2015

I believe I've seen similar in the Docker world here, make sure your DNS is configured and working. One test is to ping google.com at a command prompt.

My DNS is definitely configured and working.

You might want to go to the Tools page and run the 'Diagnostics' package and attach the resulting file to your next post.

bonienl · August 8, 2015

What is required to get Auto Fan Control working? My system has a SuperMicro X10SLL-F mobo that supports PWM fan speed control via IPMI. When I try to auto detect a controller nothing is detected. Is there something else needed for this plugin to work? Maybe something must be configured first?

No nothing else is needed to install. Detect scans the folder /sys/devices and lists all pwm controllers it finds. You can do a manual scan with this command to see what is available for your motherboard:
find /sys/devices -type f -iname 'pwm[0-9]'
That doesn't seem to do anything-
maggie:~ wgstarks$ telnet 10.0.1.20
Trying 10.0.1.20...
Connected to 10.0.1.20.
Escape character is '^]'.
Password: 
Login incorrect

Brunnhilde login: root
Linux 4.0.4-unRAID.
root@Brunnhilde:~# find /sys/devices -type f -iname 'pwm[0-9]'
root@Brunnhilde:~# 

Seems you don't have any pwm controllers.

As an example on my system:

#find /sys/devices -type f -iname 'pwm[0-9]'
/sys/devices/platform/nct6775.656/hwmon/hwmon1/pwm1
/sys/devices/platform/nct6775.656/hwmon/hwmon1/pwm2
/sys/devices/platform/nct6775.656/hwmon/hwmon1/pwm3

johnodon · August 8, 2015

Why is the UPS Status plugin no longer available? Is it because it is being rolled into 6.1 final?

bonienl · August 8, 2015

Why is the UPS Status plugin no longer available? Is it because it is being rolled into 6.1 final?

Yep

Squid · August 8, 2015

I believe I've seen similar in the Docker world here, make sure your DNS is configured and working. One test is to ping google.com at a command prompt.

My DNS is definitely configured and working.

Seems to be a recurring problem, but once its fixed it stays fixed. You might want to try this: (or read the entire thread): http://lime-technology.com/forum/index.php?topic=41996.msg399195#msg399195

wgstarks · August 8, 2015

What is required to get Auto Fan Control working? My system has a SuperMicro X10SLL-F mobo that supports PWM fan speed control via IPMI. When I try to auto detect a controller nothing is detected. Is there something else needed for this plugin to work? Maybe something must be configured first?

No nothing else is needed to install. Detect scans the folder /sys/devices and lists all pwm controllers it finds. You can do a manual scan with this command to see what is available for your motherboard:
find /sys/devices -type f -iname 'pwm[0-9]'
That doesn't seem to do anything-
maggie:~ wgstarks$ telnet 10.0.1.20
Trying 10.0.1.20...
Connected to 10.0.1.20.
Escape character is '^]'.
Password: 
Login incorrect

Brunnhilde login: root
Linux 4.0.4-unRAID.
root@Brunnhilde:~# find /sys/devices -type f -iname 'pwm[0-9]'
root@Brunnhilde:~# 
Seems you don't have any pwm controllers.

As an example on my system:
#find /sys/devices -type f -iname 'pwm[0-9]'
/sys/devices/platform/nct6775.656/hwmon/hwmon1/pwm1
/sys/devices/platform/nct6775.656/hwmon/hwmon1/pwm2
/sys/devices/platform/nct6775.656/hwmon/hwmon1/pwm3

So I would need a different mother board?

optiman · August 8, 2015

I too am trying to get the Autofan working. My motherboard for sure has a pwm fan port and yet I get nothing at all when running that command - find /sys/devices -type f -iname 'pwm[0-9]'

So why isn't Detect finding my pwm controller and how can I make it find it?

gfjardim · August 8, 2015

I too am trying to get the Autofan working. My motherboard for sure has a pwm fan port and yet I get nothing at all when running that command - find /sys/devices -type f -iname 'pwm[0-9]'

So why isn't Detect finding my pwm controller and how can I make it find it?

Try running this:

curl -skL http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect | perl

optiman · August 8, 2015

Ok weird, now it would seem I do not have perl installed.

root@Tower:~# curl -skL http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect | perl

-bash: perl: command not found

I'll have to install again. Is there a plugin for perl or install the old fashion way?

gfjardim · August 8, 2015

Ok weird, now it would seem I do not have perl installed.

root@Tower:~# curl -skL http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect | perl

-bash: perl: command not found

I'll have to install again. Is there a plugin for perl or install the old fashion way?

I think the old way.

http://mirrors.slackware.com/slackware/slackware64-14.1/slackware64/d/perl-5.18.1-x86_64-1.txz

Into /boot/extra .

optiman · August 8, 2015

ok, so I can just create the Extra folder again (it was removed when I upgraded to ver6) and reboot?

Or do I need to run the installpkg command on the console? I thought with unraid ver6, that we were not supposed to use the manual way and the EXtra folder??

Edit: I went ahead and created the Extra folder and put there, rebooted and it is now installed. I still get nothing when running the find /sys/devices -type f -iname 'pwm[0-9]'

Still does not Detect anything??

gfjardim · August 8, 2015

ok, so I can just create the Extra folder again (it was removed when I upgraded to ver6) and reboot?

Or do I need to run the installpkg command on the console? I thought with unraid ver6, that we were not supposed to use the manual way and the EXtra folder??

Edit: I went ahead and created the Extra folder and put there, rebooted and it is now installed. I still get nothing when running the find /sys/devices -type f -iname 'pwm[0-9]'

Still does not Detect anything??

Did you tried again in the web interface?

bonienl · August 8, 2015

ok, so I can just create the Extra folder again (it was removed when I upgraded to ver6) and reboot?

Or do I need to run the installpkg command on the console? I thought with unraid ver6, that we were not supposed to use the manual way and the EXtra folder??

Edit: I went ahead and created the Extra folder and put there, rebooted and it is now installed. I still get nothing when running the find /sys/devices -type f -iname 'pwm[0-9]'

Still does not Detect anything??

You actually need to install the Dynamix System Temperature plugin to do detection and installation of drivers (this is using perl to do so).

After drivers have been installed they will be used by the AutoFan plugin.

optiman · August 8, 2015

I had already done that, system temps been working for weeks.

I will dig through the BIOS settings again and make sure I didn't miss anything. I may be disabled in the BIOS.

wgstarks · August 8, 2015

I too am trying to get the Autofan working. My motherboard for sure has a pwm fan port and yet I get nothing at all when running that command - find /sys/devices -type f -iname 'pwm[0-9]'

So why isn't Detect finding my pwm controller and how can I make it find it?

Try running this:
curl -skL http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect | perl

Here is the result I got, I don't have a clue what to do with the info-

Last login: Sat Aug  8 15:50:37 on console
maggie:~ wgstarks$ telnet 10.0.1.20
Trying 10.0.1.20...
Connected to 10.0.1.20.
Escape character is '^]'.
Password: 
Login incorrect

Brunnhilde login: root
Linux 4.0.4-unRAID.
root@Brunnhilde:~# curl -skL http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect | perl
# sensors-detect revision $Revision$
# System: Supermicro X10SLL-F [0123456789]
# Kernel: 4.0.4-unRAID x86_64
# Processor: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz (6/60/3)

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 16h 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
Intel 5500/5520/X58 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'...               No
Trying family `ITE'...                                      No
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 0xca2...                            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 Lynx Point (PCH)

Next adapter: SMBus I801 adapter at 0580 (i2c-0)
Do you want to scan it? (YES/no/selectively): Client found at address 0x18
Handled by driver `jc42' (already loaded), chip type `jc42'
Client found at address 0x1a
Handled by driver `jc42' (already loaded), chip type `jc42'
Client found at address 0x48
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)


Now follows a summary of the probes I have just done.
Just press ENTER to continue: 
Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Driver `jc42':
  * Bus `SMBus I801 adapter at 0580'
    Busdriver `i2c_i801', I2C address 0x18
    Chip `jc42' (confidence: 6)
  * Bus `SMBus I801 adapter at 0580'
    Busdriver `i2c_i801', I2C address 0x1a
    Chip `jc42' (confidence: 6)

Driver `to-be-written':
  * ISA bus, address 0xca2
    Chip `IPMI BMC KCS' (confidence: 

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

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----
# Chip drivers
modprobe coretemp
modprobe jc42
/usr/bin/sensors -s
#----cut here----

You really should try these commands right now to make sure everything
is working properly. Monitoring programs won't work until the needed
modules are loaded.

***************************************************************
Warning: the preferred way to run this script non-interactively
is with option --auto. Other methods are discouraged and may
stop working at some point in the future.
***************************************************************

root@Brunnhilde:~#

optiman · August 8, 2015

Looked through the bios, found nothing.

Here is my output from running that command:

root@Tower:~# curl -skL http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect | perl

# sensors-detect revision $Revision$

# System: Gigabyte Technology Co., Ltd. X58A-UD3R

# Kernel: 4.0.4-unRAID x86_64

# Processor: Intel® Core i7 CPU 960 @ 3.20GHz (6/26/5)

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 16h 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

Intel 5500/5520/X58 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'... No

Trying family `ITE'... Yes

Found `ITE IT8720F Super IO Sensors' Success!

(address 0x290, driver `it87')

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): Probing for `IPMI BMC KCS' at 0xca0... No

Probing for `IPMI BMC SMIC' at 0xca8... No

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

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 ICH10

YES

Next adapter: SMBus I801 adapter at 0500 (i2c-0)

Do you want to scan it? (yes/NO/selectively):

Now follows a summary of the probes I have just done.

Just press ENTER to continue:

Driver `it87':

* ISA bus, address 0x290

Chip `ITE IT8720F Super IO Sensors' (confidence: 9)

Driver `coretemp':

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

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): To load everything that is needed, add this to one of the system

initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----

# Chip drivers

modprobe coretemp

modprobe it87

/usr/bin/sensors -s

#----cut here----

You really should try these commands right now to make sure everything

is working properly. Monitoring programs won't work until the needed

modules are loaded.

***************************************************************

Warning: the preferred way to run this script non-interactively

is with option --auto. Other methods are discouraged and may

stop working at some point in the future.

***************************************************************

temps show fine, but Detect under fan does nothing

ColonialRaptor · August 9, 2015

Howdy... I'm still having trouble installing the Dynamix Plugin extras and I was asked to attach my diagnostics information to my next post so here it is...

Still having the same problem when trying to use the install tab on the V6 GUI.

tower-diagnostics-20150809-1109.zip

trurl · August 9, 2015

Howdy... I'm still having trouble installing the Dynamix Plugin extras and I was asked to attach my diagnostics information to my next post so here it is...

Still having the same problem when trying to use the install tab on the V6 GUI.

Probably not related, but you have filesystem corruption on disk3

Aug  8 12:12:32 Tower kernel: REISERFS error (device md3): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 184385536 is corrupted: first bit must be 1
Aug  8 12:12:32 Tower kernel: REISERFS (device md3): Remounting filesystem read-only
Aug  8 12:12:32 Tower kernel: REISERFS warning (device md3): clm-6006 reiserfs_dirty_inode: writing inode 1507 on readonly FS

Dynamix - V6 Plugins

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

bonienl

bonienl

bonienl

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation