Re: SS4000E Fan speed, LEDS and power button
Re,
On Tue, Jul 24, 2012 at 12:12:46PM -0400, Chris Wilkinson wrote:
> Could someone be kind enough to post the output they get from these
> commands?
If it has still an interest, here is output of mine after yours :
> root@Freestor:~# sensors
> w83792d-i2c-0-2d
> Adapter: IOP3xx-I2C
> VcoreA: +1.28 V (min = +0.00 V, max = +2.04 V)
> VcoreB: +0.00 V (min = +0.00 V, max = +2.04 V)
> in2: +2.55 V (min = +0.00 V, max = +4.08 V)
> in3: +3.30 V (min = +0.00 V, max = +4.08 V)
> in4: +0.00 V (min = +0.00 V, max = +4.08 V)
> in5: +1.99 V (min = +0.00 V, max = +4.08 V)
> +5V: +4.92 V (min = +4.49 V, max = +5.50 V)
> 5VSB: +4.93 V (min = +4.49 V, max = +5.50 V)
> Vbat: +0.00 V (min = +2.69 V, max = +3.30 V) ALARM
> fan1: 0 RPM (min = 0 RPM, div = 2)
> fan2: 0 RPM (min = 0 RPM, div = 2)
> fan3: 0 RPM (min = 0 RPM, div = 2)
> fan4: 0 RPM (min = 0 RPM, div = 2)
> fan5: 0 RPM (min = 0 RPM, div = 2)
> temp1: +46.0°C (high = +127.0°C, hyst = +0.0°C)
> temp2: +127.0°C (high = +80.0°C, hyst = +75.0°C) ALARM
> temp3: +127.0°C (high = +80.0°C, hyst = +75.0°C) ALARM
lothar:~# sensors
w83792d-i2c-0-2d
Adapter: IOP3xx-I2C
VcoreA: +1.32 V (min = +0.00 V, max = +2.04 V)
VcoreB: +2.05 V (min = +0.00 V, max = +2.04 V)
in2: +3.30 V (min = +0.00 V, max = +4.08 V)
in3: +2.98 V (min = +0.00 V, max = +4.08 V)
in4: +0.00 V (min = +0.00 V, max = +4.08 V)
in5: +0.00 V (min = +0.00 V, max = +4.08 V)
+5V: +5.01 V (min = +4.49 V, max = +5.50 V)
5VSB: +4.94 V (min = +4.49 V, max = +5.50 V)
Vbat: +0.00 V (min = +2.69 V, max = +3.30 V) ALARM
fan1: 1010 RPM (min = 0 RPM, div = 8)
fan2: 0 RPM (min = 0 RPM, div = 2)
fan3: 0 RPM (min = 0 RPM, div = 2)
fan4: 0 RPM (min = 0 RPM, div = 2)
fan5: 0 RPM (min = 0 RPM, div = 2)
temp1: +53.0°C (high = +127.0°C, hyst = +0.0°C)
temp2: -30.5°C (high = +80.0°C, hyst = +75.0°C)
temp3: -19.5°C (high = +80.0°C, hyst = +75.0°C)
So almost the same as yours, but with fan1 speed (but funny temps').
> root@Freestor:~# modprobe -l | grep 83792
> kernel/drivers/hwmon/w83792d.ko
lothar:~# modprobe -l | grep 83792
kernel/drivers/hwmon/w83792d.ko
> root@Freestor:~# modinfo w83792d
> filename: /lib/modules/2.6.32-5-iop32x/kernel/drivers/hwmon/w83792d.ko
> license: GPL
> description: W83792AD/D driver for linux-2.6
> author: Chunhao Huang @ Winbond <DZShen@Winbond.com.tw>
> alias: i2c:w83792d
> depends:
> vermagic: 2.6.32-5-iop32x mod_unload modversions ARMv5
> parm: force:List of adapter,address pairs to boldly assume to be
> present (array of short)
> parm: force_w83792d:List of adapter,address pairs which are
> unquestionably assumed to contain a `w83792d' chip (array of short)
> parm: probe:List of adapter,address pairs to scan additionally
> (array of short)
> parm: ignore:List of adapter,address pairs not to scan (array of
> short)
> parm: force_subclients:List of subclient addresses: {bus,
> clientaddr, subclientaddr1, subclientaddr2} (array of short)
> parm: init:Set to one to force chip initialization (bool)
lothar:~# modinfo w83792d
filename:
/lib/modules/2.6.32-5-iop32x/kernel/drivers/hwmon/w83792d.ko
license: GPL
description: W83792AD/D driver for linux-2.6
author: Chunhao Huang @ Winbond <DZShen@Winbond.com.tw>
alias: i2c:w83792d
depends:
vermagic: 2.6.32-5-iop32x mod_unload modversions ARMv5
parm: force:List of adapter,address pairs to boldly assume
to be present (array of short)
parm: force_w83792d:List of adapter,address pairs which are
unquestionably assumed to contain a `w83792d' chip (array of short)
parm: probe:List of adapter,address pairs to scan
additionally (array of short)
parm: ignore:List of adapter,address pairs not to scan
(array of short)
parm: force_subclients:List of subclient addresses: {bus,
clientaddr, subclientaddr1, subclientaddr2} (array of short)
parm: init:Set to one to force chip initialization (bool)
(But this is not surprising : we have same kernel).
Hih,
--
JFS.
Reply to: