[lm-sensors] Intel SRSH4 Motherboard Sensors

[lm-sensors] Intel SRSH4 Motherboard Sensors

[Keith Romberg]

Hello,

I have a Quad MP Xeon Intel SRSH4 system where the motherboard has 
BMC/IPMI onboard sensors.  I would really like to be able to monitor the 
sensors with lm_sensors.  The system is running FC6 with all the latest 
versions including lm_sensors.  The kernel is 2.6.20 patched with the

'ipmisensors experimental'

kernel patch from

http://bmcsensors-26.sourceforge.net/

Running sensors-detect find these sensors, but does not know about the 
chips.

- IPMI BMC KCS ( confidence 4, driver bmcsensors )
- ITE ( unknown chip with ID 0xee19 )
- PC8741x ( unknown chip with ID 0xee19 )
- SMSC ( unknown chip with ID 0xee19 )
- VIA/Winbond/Fintek ( unknown chip with ID 0xee19 )

After loading all the modules it says to, running sensors gives the 
classic message that no sensors where found.  Does anyone know if the 
sensors and/or chips are supported or ever will be?

I have also read that Xeon processors have an onboard temperature sensor 
and that the xeontemp module could be used to read it.  Looking at my 
kernel modules, I do not see it in the i2c directories or do I see an 
option for it in the kernel config file.  How do I get that module?

Thanks,
Keith

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel SRSH4 Motherboard Sensors

[Keith Romberg]

No one has any experience with these board or the sensors on it?  I was 
kind of hoping for something....

Keith

Keith Romberg wrote:
> Hello,
> 
> I have a Quad MP Xeon Intel SRSH4 system where the motherboard has 
> BMC/IPMI onboard sensors.  I would really like to be able to monitor the 
> sensors with lm_sensors.  The system is running FC6 with all the latest 
> versions including lm_sensors.  The kernel is 2.6.20 patched with the
> 
> 'ipmisensors experimental'
> 
> kernel patch from
> 
> http://bmcsensors-26.sourceforge.net/
> 
> Running sensors-detect find these sensors, but does not know about the 
> chips.
> 
> - IPMI BMC KCS ( confidence 4, driver bmcsensors )
> - ITE ( unknown chip with ID 0xee19 )
> - PC8741x ( unknown chip with ID 0xee19 )
> - SMSC ( unknown chip with ID 0xee19 )
> - VIA/Winbond/Fintek ( unknown chip with ID 0xee19 )
> 
> After loading all the modules it says to, running sensors gives the 
> classic message that no sensors where found.  Does anyone know if the 
> sensors and/or chips are supported or ever will be?
> 
> I have also read that Xeon processors have an onboard temperature sensor 
> and that the xeontemp module could be used to read it.  Looking at my 
> kernel modules, I do not see it in the i2c directories or do I see an 
> option for it in the kernel config file.  How do I get that module?
> 
> Thanks,
> Keith
> 

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel SRSH4 Motherboard Sensors

[Juerg Haefliger]

Keith,

Make sure you have the ipmisensors and ipmi_msghandler modules
installed. Check if there are any entries under /sys/class/hwmon.
Check /var/log/messages, it should read something like the following
after loading the ipmisensors module:

May 30 14:37:54 clim1 kernel: ipmisensors - IPMI BMC sensors interface
May 30 14:37:54 clim1 kernel: ipmisensors: Registered IPMI 2.0 BMC
over interface 0
May 30 14:37:54 clim1 kernel: ipmisensors: Skipping SDR type 0xc0
May 30 14:37:54 clim1 kernel: ipmisensors: Skipping SDR type 0x8
May 30 14:37:54 clim1 kernel: ipmisensors: skipping non-threshold sensor "Fan 1"
May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor "Fan 2"
May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor "Fan 3"
May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor "Fan 4"
May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor "Fan 5"
May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor "Fan 6"
May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor "Fan 7"
May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor "Fan 8"
May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor "Fan 9"
May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold
sensor "Fan 10"
May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold
sensor "Fan 11"
May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold
sensor "Fan 12"
May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor "Fans"
May 30 14:37:55 clim1 kernel: ipmisensors: Skipping SDR type 0x8
May 30 14:37:55 clim1 kernel: ipmisensors: all sensors detected
May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 27:
(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp1 "Temp 6"
May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
threshold for upper limit
May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 26:
(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp2 "Temp 5"
May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
threshold for upper limit
May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 25:
(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp3 "Temp 4"
May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
threshold for upper limit
May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 24:
(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp4 "Temp 3"
May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
threshold for upper limit
May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 23:
(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp5 "Temp 2"
May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
threshold for upper limit
May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 22:
(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp6 "Temp 1"
May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
threshold for upper limit
May 30 14:37:55 clim1 kernel: ipmisensors: registered 6 temp, 0 volt,
0 current, 0 fan sensors


Running sensors works fine for me:

clim1:~# sensors
bmc-isa-0000
Adapter: ISA adapter
temp1:      +0.0°C  (high =    +7°C, hyst =    +0°C)
temp2:     +44.0°C  (high =    +6°C, hyst =    +0°C)
temp3:     +40.0°C  (high =    +6°C, hyst =    +0°C)
temp4:     +31.0°C  (high =   +10°C, hyst =    +0°C)
temp5:      +0.0°C  (high =   +10°C, hyst =    +0°C)
temp6:     +18.0°C  (high =    +4°C, hyst =    +0°C)


...juerg




On 5/30/07, Keith Romberg <romberg@ucar.edu> wrote:
> No one has any experience with these board or the sensors on it?  I was
> kind of hoping for something....
>
> Keith
>
> Keith Romberg wrote:
> > Hello,
> >
> > I have a Quad MP Xeon Intel SRSH4 system where the motherboard has
> > BMC/IPMI onboard sensors.  I would really like to be able to monitor the
> > sensors with lm_sensors.  The system is running FC6 with all the latest
> > versions including lm_sensors.  The kernel is 2.6.20 patched with the
> >
> > 'ipmisensors experimental'
> >
> > kernel patch from
> >
> > http://bmcsensors-26.sourceforge.net/
> >
> > Running sensors-detect find these sensors, but does not know about the
> > chips.
> >
> > - IPMI BMC KCS ( confidence 4, driver bmcsensors )
> > - ITE ( unknown chip with ID 0xee19 )
> > - PC8741x ( unknown chip with ID 0xee19 )
> > - SMSC ( unknown chip with ID 0xee19 )
> > - VIA/Winbond/Fintek ( unknown chip with ID 0xee19 )
> >
> > After loading all the modules it says to, running sensors gives the
> > classic message that no sensors where found.  Does anyone know if the
> > sensors and/or chips are supported or ever will be?
> >
> > I have also read that Xeon processors have an onboard temperature sensor
> > and that the xeontemp module could be used to read it.  Looking at my
> > kernel modules, I do not see it in the i2c directories or do I see an
> > option for it in the kernel config file.  How do I get that module?
> >
> > Thanks,
> > Keith
> >
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel SRSH4 Motherboard Sensors

[KEITH ROMBERG]

[-- Attachment #1: Type: text/plain, Size: 4995 bytes --]

Hey Juerg,

OK, I also loaded ipmi_msghandler as I was not loading it before.  I am not 
loading these modules in my rc.local file:

i2c-piix4
i2c-ipmi
eeprom
ipmisensors
ipmi_msghandler
hwmon

in that order.  Looking at /sys/classes, it is empty.  When I manually load 
the modules, via rmmod & modprobe, and look at /var/log/messages the only 
entries are:

May 31 15:01:26 smaug kernel: ipmi message handler version 39.1
May 31 15:01:26 smaug kernel: ipmisensors - IPMI BMC sensors interface


As I said before I am using 2.6.21 patched with the experimential ipmi 
patch.  Juerg what kernel are you using and do you also have a SRSH4 based 
system?  Any other pointers are things to try?

Thanks,
Keith

>
>Keith,
>
>Make sure you have the ipmisensors and ipmi_msghandler modules
>installed. Check if there are any entries under /sys/class/hwmon.
>Check /var/log/messages, it should read something like the following
>after loading the ipmisensors module:
>
>May 30 14:37:54 clim1 kernel: ipmisensors - IPMI BMC sensors interface
>May 30 14:37:54 clim1 kernel: ipmisensors: Registered IPMI 2.0 BMC
>over interface 0
>May 30 14:37:54 clim1 kernel: ipmisensors: Skipping SDR type 0xc0
>May 30 14:37:54 clim1 kernel: ipmisensors: Skipping SDR type 0x8
>May 30 14:37:54 clim1 kernel: ipmisensors: skipping non-threshold sensor 
>"Fan 1"
>May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor 
>"Fan 2"
>May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor 
>"Fan 3"
>May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor 
>"Fan 4"
>May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor 
>"Fan 5"
>May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor 
>"Fan 6"
>May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor 
>"Fan 7"
>May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor 
>"Fan 8"
>May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor 
>"Fan 9"
>May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold
>sensor "Fan 10"
>May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold
>sensor "Fan 11"
>May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold
>sensor "Fan 12"
>May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor 
>"Fans"
>May 30 14:37:55 clim1 kernel: ipmisensors: Skipping SDR type 0x8
>May 30 14:37:55 clim1 kernel: ipmisensors: all sensors detected
>May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 27:
>(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
>May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp1 "Temp 
>6"
>May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
>threshold for upper limit
>May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 26:
>(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
>May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp2 "Temp 
>5"
>May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
>threshold for upper limit
>May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 25:
>(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
>May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp3 "Temp 
>4"
>May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
>threshold for upper limit
>May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 24:
>(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
>May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp4 "Temp 
>3"
>May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
>threshold for upper limit
>May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 23:
>(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
>May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp5 "Temp 
>2"
>May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
>threshold for upper limit
>May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 22:
>(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
>May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp6 "Temp 
>1"
>May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
>threshold for upper limit
>May 30 14:37:55 clim1 kernel: ipmisensors: registered 6 temp, 0 volt,
>0 current, 0 fan sensors
>
>
>Running sensors works fine for me:
>
>clim1:~# sensors
>bmc-isa-0000
>Adapter: ISA adapter
>temp1:      +0.0���C  (high =    +7���C, hyst =    +0���C)
>temp2:     +44.0���C  (high =    +6���C, hyst =    +0���C)
>temp3:     +40.0���C  (high =    +6���C, hyst =    +0���C)
>temp4:     +31.0���C  (high =   +10���C, hyst =    +0���C)
>temp5:      +0.0���C  (high =   +10���C, hyst =    +0���C)
>temp6:     +18.0���C  (high =    +4���C, hyst =    +0���C)
>
>
>...juerg
>
>
>




[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel SRSH4 Motherboard Sensors

[Juerg Haefliger]

Hi Keith,

On 5/31/07, KEITH ROMBERG <k_romberg@msn.com> wrote:
> Hey Juerg,
>
> OK, I also loaded ipmi_msghandler as I was not loading it before.  I am not
> loading these modules in my rc.local file:
>
> i2c-piix4
> i2c-ipmi
> eeprom
> ipmisensors
> ipmi_msghandler
> hwmon

You should load ipmi_msghandler and hwmon first, ipmisensors depends on them.


> in that order.  Looking at /sys/classes, it is empty.

That;s unlikely. There should be lots of stuff in /sys/classes. What
about /sys/classes/hwmon?


> When I manually load
> the modules, via rmmod & modprobe, and look at /var/log/messages the only
> entries are:
>
> May 31 15:01:26 smaug kernel: ipmi message handler version 39.1
> May 31 15:01:26 smaug kernel: ipmisensors - IPMI BMC sensors interface

Hmm... That doesn't look good. Can you try to just modprobe
ipmi_msghandler? You should see something like the following in the
log. It almost looks like ipmi doens't find a BMC on your system. And
could you please send the output of lsmod to the list?

May 30 14:51:54 clim1 kernel: ipmi message handler version 39.0
May 30 14:51:54 clim1 kernel: IPMI System Interface driver.
May 30 14:51:54 clim1 kernel: ipmi_si: Trying SMBIOS-specified KCS
state machine at I/O address 0xca2, slave address 0x20, irq 0
May 30 14:51:54 clim1 kernel: ipmi: Found new BMC (man_id: 0x00000b,
prod_id: 0x0000, dev_id: 0x11)
May 30 14:51:54 clim1 kernel:  IPMI KCS interface initialized
May 30 14:51:54 clim1 kernel: ipmi_si: Trying ACPI-specified KCS state
machine at memory address 0xca2, slave address 0x0, irq 0
May 30 14:51:54 clim1 kernel:  Could not set up I/O space
May 30 14:51:54 clim1 kernel: Trying to free nonexistent resource
<0000000000000ca2-0000000000000ca3>
May 30 14:51:54 clim1 kernel: Trying to free nonexistent resource
<0000000000000ca4-0000000000000ca5>
May 30 14:51:54 clim1 kernel: GSI 27 sharing vector 0xA2 and IRQ 27
May 30 14:51:54 clim1 kernel: ACPI: PCI Interrupt 0000:00:04.6[A] ->
GSI 46 (level, low) -> IRQ 162
May 30 14:51:54 clim1 kernel: ipmi_si: Trying PCI-specified KCS state
machine at memory address 0xf5ef0000, slave address 0x0, irq 162
May 30 14:51:54 clim1 kernel:   Using irq 162
May 30 14:51:54 clim1 kernel: ipmi: interfacing existing BMC (man_id:
0x00000b, prod_id: 0x0000, dev_id: 0x11)
May 30 14:51:54 clim1 kernel:  IPMI KCS interface initialized
May 30 14:51:54 clim1 kernel: ipmi device interface


>
> As I said before I am using 2.6.21 patched with the experimential ipmi
> patch.  Juerg what kernel are you using and do you also have a SRSH4 based
> system?  Any other pointers are things to try?

I'm running 2.6.20.9 with the experimental ipmisensors patch on an HP
DL385G2. This is not an SRSH4 based system.

...juerg


> Thanks,
> Keith
>
> >
> >Keith,
> >
> >Make sure you have the ipmisensors and ipmi_msghandler modules
> >installed. Check if there are any entries under /sys/class/hwmon.
> >Check /var/log/messages, it should read something like the following
> >after loading the ipmisensors module:
> >
> >May 30 14:37:54 clim1 kernel: ipmisensors - IPMI BMC sensors interface
> >May 30 14:37:54 clim1 kernel: ipmisensors: Registered IPMI 2.0 BMC
> >over interface 0
> >May 30 14:37:54 clim1 kernel: ipmisensors: Skipping SDR type 0xc0
> >May 30 14:37:54 clim1 kernel: ipmisensors: Skipping SDR type 0x8
> >May 30 14:37:54 clim1 kernel: ipmisensors: skipping non-threshold sensor
> >"Fan 1"
> >May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor
> >"Fan 2"
> >May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor
> >"Fan 3"
> >May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor
> >"Fan 4"
> >May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor
> >"Fan 5"
> >May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor
> >"Fan 6"
> >May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor
> >"Fan 7"
> >May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor
> >"Fan 8"
> >May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor
> >"Fan 9"
> >May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold
> >sensor "Fan 10"
> >May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold
> >sensor "Fan 11"
> >May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold
> >sensor "Fan 12"
> >May 30 14:37:55 clim1 kernel: ipmisensors: skipping non-threshold sensor
> >"Fans"
> >May 30 14:37:55 clim1 kernel: ipmisensors: Skipping SDR type 0x8
> >May 30 14:37:55 clim1 kernel: ipmisensors: all sensors detected
> >May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 27:
> >(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
> >May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp1 "Temp
> >6"
> >May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
> >threshold for upper limit
> >May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 26:
> >(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
> >May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp2 "Temp
> >5"
> >May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
> >threshold for upper limit
> >May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 25:
> >(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
> >May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp3 "Temp
> >4"
> >May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
> >threshold for upper limit
> >May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 24:
> >(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
> >May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp4 "Temp
> >3"
> >May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
> >threshold for upper limit
> >May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 23:
> >(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
> >May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp5 "Temp
> >2"
> >May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
> >threshold for upper limit
> >May 30 14:37:55 clim1 kernel: ipmisensors: registering sensor 22:
> >(type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0xc9; mask=0x0030)
> >May 30 14:37:55 clim1 kernel: ipmisensors: sensors.conf: label temp6 "Temp
> >1"
> >May 30 14:37:55 clim1 kernel: ipmisensors: using upper critical
> >threshold for upper limit
> >May 30 14:37:55 clim1 kernel: ipmisensors: registered 6 temp, 0 volt,
> >0 current, 0 fan sensors
> >
> >
> >Running sensors works fine for me:
> >
> >clim1:~# sensors
> >bmc-isa-0000
> >Adapter: ISA adapter
> >temp1:      +0.0°C  (high =    +7°C, hyst =    +0°C)
> >temp2:     +44.0°C  (high =    +6°C, hyst =    +0°C)
> >temp3:     +40.0°C  (high =    +6°C, hyst =    +0°C)
> >temp4:     +31.0°C  (high =   +10°C, hyst =    +0°C)
> >temp5:      +0.0°C  (high =   +10°C, hyst =    +0°C)
> >temp6:     +18.0°C  (high =    +4°C, hyst =    +0°C)
> >
> >
> >...juerg
> >
> >
> >
>
>
>
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel SRSH4 Motherboard Sensors

[KEITH ROMBERG]

>
>Hi Keith,
>
>>
>
>You should load ipmi_msghandler and hwmon first, ipmisensors depends on 
>them.
>
>

OK, I changed the order and now load them

2c-piix4
2c-ipmi
eprom
ipmi_msghandler
hwmon
ipmisensors



>
>That;s unlikely. There should be lots of stuff in /sys/classes. What
>about /sys/classes/hwmon?

That directory is still empty.

>
>
>
>Hmm... That doesn't look good. Can you try to just modprobe
>ipmi_msghandler? You should see something like the following in the
>log. It almost looks like ipmi doens't find a BMC on your system. And
>could you please send the output of lsmod to the list?
>

/var/log/messages still only contains:

Jun  2 00:11:02 smaug kernel: ipmi message handler version 39.1
Jun  2 00:11:20 smaug kernel: ipmisensors - IPMI BMC sensors interface

Here is the output of lsmod:

[root@smaug ~]# lsmod
Module                  Size  Used by
ipmisensors            21896  0
hwmon                   7556  1 ipmisensors
ipmi_msghandler        39856  1 ipmisensors
autofs4                25092  2
eeprom                 11280  0
sunrpc                160092  1
ipv6                  275904  46
dm_multipath           21896  0
video                  21128  0
sbs                    19392  0
ibm_acpi               34968  0
i2c_ec                  9344  1 sbs
dock                   14200  0
button                 12176  0
battery                14212  0
asus_acpi              20636  0
ac                      9476  0
lp                     16456  0
st                     39836  0
scb2_flash              8844  0
floppy                 59236  0
mtdcore                10628  1 scb2_flash
sg                     37532  0
chipreg                 7552  1 scb2_flash
e1000                 117824  0
map_funcs               6016  1 scb2_flash
pcspkr                  7296  0
e100                   37640  0
mii                     9472  1 e100
i2c_piix4              12812  0
i2c_core               24960  3 eeprom,i2c_ec,i2c_piix4
tulip                  53152  0
ide_cd                 40736  0
parport_pc             30244  1
parport                38728  2 lp,parport_pc
cdrom                  37408  1 ide_cd
serio_raw              11012  0
dm_snapshot            20784  0
dm_zero                 6144  0
dm_mirror              25236  0
dm_mod                 58060  9 dm_multipath,dm_snapshot,dm_zero,dm_mirror
aic7xxx               137272  0
scsi_transport_spi     27136  1 aic7xxx
qla1280               120588  0
megaraid_mbox          35088  2
sd_mod                 24192  3
scsi_mod              138668  7 
st,sg,aic7xxx,scsi_transport_spi,qla1280,megaraid_mbox,sd_mod
megaraid_mm            15020  1 megaraid_mbox
ext3                  125704  2
jbd                    60712  1 ext3
ehci_hcd               35468  0
ohci_hcd               24068  0
uhci_hcd               26896  0

--------------------------------------------------------------------

I have played around with the Intel ISM cdrom package Intel has.   I am only 
able to get a little of it working.  It is looking for a specific version of 
RHEL 4.0 which I do not have.  I am able to get the one util to run called 
something like smbios that dumps a whole lot of info about the system out.  
I currently have all of it removed off, but I can install it again if anyone 
would find it helpful.

Keith



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel SRSH4 Motherboard Sensors

[KEITH ROMBERG]

Another problem I think is that the i2c-ipmi module is not getting loaded.  
The module is not in the /lib/modules directory and I can not find any trace 
and/or reference to it in the kernel source.  Is this one need?  It says it 
should be loaded by sensors-detech which is version 2.10.1


>>
>>OK, I also loaded ipmi_msghandler as I was not loading it before.  I am 
>>not
>>loading these modules in my rc.local file:
>>
>>i2c-piix4
>>i2c-ipmi
>>eeprom
>>ipmisensors
>>ipmi_msghandler
>>hwmon
>
>You should load ipmi_msghandler and hwmon first, ipmisensors depends on 
>them.
>
>



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel SRSH4 Motherboard Sensors

[Jean Delvare]

Hi Keith,

On Mon, 04 Jun 2007 02:26:51 +0000, KEITH ROMBERG wrote:
> Another problem I think is that the i2c-ipmi module is not getting loaded.  
> The module is not in the /lib/modules directory and I can not find any trace 
> and/or reference to it in the kernel source.  Is this one need?  It says it 
> should be loaded by sensors-detech which is version 2.10.1

As far as I know, i2c-ipmi no longer exists (nor is needed) when running
a 2.6 kernel.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel SRSH4 Motherboard Sensors

[Keith Romberg]

So that is more just an artifact of sensors-detect reporting something 
that is no longer needed.  I assume so since it also reports bmcsesnors 
is needed rather than ipmisensors.

Keith

Jean Delvare wrote:
> 
> As far as I know, i2c-ipmi no longer exists (nor is needed) when running
> a 2.6 kernel.
> 

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel SRSH4 Motherboard Sensors

[Juerg Haefliger]

Keith,

You also need to load ipmi_si. I thought ipmi_msghandler depends on
ipmi_si but it's actually the other way around.
Let us know what the log shows after loading the module.
And try to reload ipmisensors after ipmi_si.

...juerg


On 6/1/07, KEITH ROMBERG <k_romberg@msn.com> wrote:
>
>
>
> >
> >Hi Keith,
> >
> >>
> >
> >You should load ipmi_msghandler and hwmon first, ipmisensors depends on
> >them.
> >
> >
>
> OK, I changed the order and now load them
>
> 2c-piix4
> 2c-ipmi
> eprom
> ipmi_msghandler
> hwmon
> ipmisensors
>
>
>
> >
> >That;s unlikely. There should be lots of stuff in /sys/classes. What
> >about /sys/classes/hwmon?
>
> That directory is still empty.
>
> >
> >
> >
> >Hmm... That doesn't look good. Can you try to just modprobe
> >ipmi_msghandler? You should see something like the following in the
> >log. It almost looks like ipmi doens't find a BMC on your system. And
> >could you please send the output of lsmod to the list?
> >
>
> /var/log/messages still only contains:
>
> Jun  2 00:11:02 smaug kernel: ipmi message handler version 39.1
> Jun  2 00:11:20 smaug kernel: ipmisensors - IPMI BMC sensors interface
>
> Here is the output of lsmod:
>
> [root@smaug ~]# lsmod
> Module                  Size  Used by
> ipmisensors            21896  0
> hwmon                   7556  1 ipmisensors
> ipmi_msghandler        39856  1 ipmisensors
> autofs4                25092  2
> eeprom                 11280  0
> sunrpc                160092  1
> ipv6                  275904  46
> dm_multipath           21896  0
> video                  21128  0
> sbs                    19392  0
> ibm_acpi               34968  0
> i2c_ec                  9344  1 sbs
> dock                   14200  0
> button                 12176  0
> battery                14212  0
> asus_acpi              20636  0
> ac                      9476  0
> lp                     16456  0
> st                     39836  0
> scb2_flash              8844  0
> floppy                 59236  0
> mtdcore                10628  1 scb2_flash
> sg                     37532  0
> chipreg                 7552  1 scb2_flash
> e1000                 117824  0
> map_funcs               6016  1 scb2_flash
> pcspkr                  7296  0
> e100                   37640  0
> mii                     9472  1 e100
> i2c_piix4              12812  0
> i2c_core               24960  3 eeprom,i2c_ec,i2c_piix4
> tulip                  53152  0
> ide_cd                 40736  0
> parport_pc             30244  1
> parport                38728  2 lp,parport_pc
> cdrom                  37408  1 ide_cd
> serio_raw              11012  0
> dm_snapshot            20784  0
> dm_zero                 6144  0
> dm_mirror              25236  0
> dm_mod                 58060  9 dm_multipath,dm_snapshot,dm_zero,dm_mirror
> aic7xxx               137272  0
> scsi_transport_spi     27136  1 aic7xxx
> qla1280               120588  0
> megaraid_mbox          35088  2
> sd_mod                 24192  3
> scsi_mod              138668  7
> st,sg,aic7xxx,scsi_transport_spi,qla1280,megaraid_mbox,sd_mod
> megaraid_mm            15020  1 megaraid_mbox
> ext3                  125704  2
> jbd                    60712  1 ext3
> ehci_hcd               35468  0
> ohci_hcd               24068  0
> uhci_hcd               26896  0
>
> --------------------------------------------------------------------
>
> I have played around with the Intel ISM cdrom package Intel has.   I am only
> able to get a little of it working.  It is looking for a specific version of
> RHEL 4.0 which I do not have.  I am able to get the one util to run called
> something like smbios that dumps a whole lot of info about the system out.
> I currently have all of it removed off, but I can install it again if anyone
> would find it helpful.
>
> Keith
>
>
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel SRSH4 Motherboard Sensors

[Jean Delvare]

On Mon, 04 Jun 2007 06:48:46 -0600, Keith Romberg wrote:
> So that is more just an artifact of sensors-detect reporting something 
> that is no longer needed.  I assume so since it also reports bmcsesnors 
> is needed rather than ipmisensors.

Correct. If anybody cares, that person should send a patch to address
the problem.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel SRSH4 Motherboard Sensors

[Keith Romberg]

I am happy to report success.  First off I would like to thank everyone 
that helped.  I am using kernel 2.6.21 with the ipmi experimental patch 
from http://bmcsensors-26.sourceforge.net/.  The main issue was loading 
the right modules in the right order.  Here is what I loading in 
/etc/rc.local:

#########################################################################
# I2C adapter drivers
modprobe i2c-piix4
modprobe eeprom
modprobe ipmp_si
modprobe ipmi_msghandler
modprobe ipmisensors

# sleep 2 # optional
/usr/bin/sensors -s # recommended
##########################################################################

Here is the output of sensors:

romberg@smaug > sensors
bmc-isa-0000
Adapter: ISA adapter
in1:       +0.39 V  (min =  +1.43 V, max =  +1.87 V)
in2:       +2.23 V  (min =  +2.54 V, max =  +3.45 V)
in3:       +2.23 V  (min = -13.81 V, max = -10.21 V)
in4:       -1.64 V  (min = +10.21 V, max = +13.80 V)
in5:       +3.53 V  (min =  +4.26 V, max =  +5.75 V)
in6:       +4.99 V  (min =  +2.77 V, max =  +3.78 V)
in7:       +3.72 V  (min =  +2.80 V, max =  +3.79 V)
in8:       +2.96 V  (min =  +2.14 V, max =  +3.15 V)
in9:       +3.74 V  (min =  +1.07 V, max =  +1.43 V)
fan1:        0 RPM  (min = 1920 RPM)
fan2:     3840 RPM  (min = 1920 RPM)
fan3:     3750 RPM  (min = 1830 RPM)
fan4:     3600 RPM  (min = 1830 RPM)
fan5:     4200 RPM  (min = 1830 RPM)
fan6:     4200 RPM  (min = 1830 RPM)
temp1:     -12.8°C  (high =    +5°C, hyst =   -13°C)
temp2:    +138.0°C  (high =    +8°C, hyst =    +0°C)
temp3:     +41.0°C  (high =    +8°C, hyst =    +0°C)
temp4:     +39.0°C  (high =    +8°C, hyst =    +0°C)
temp5:     +39.0°C  (high =    +8°C, hyst =    +0°C)
temp6:     +40.0°C  (high =    +4°C, hyst =    +0°C)
temp7:     +27.0°C  (high =    +5°C, hyst =    +0°C)

The voltages look fine or I do not see anything too out of the norm. 
fan1's rpms for some reason is not reported.  The fan is spinning fine 
and no fan faults are reported on the case status panel.  For temp1 and 
temp2, I have no idea what they are.  The CPUs are temp3 through temp6. 
  I am guessing temp7 is a hard drive.  The system has a Dell PERC 3DC 
raid controller with a single 108GB raid5 array.

Overall I am happy that I can at least now monitor the CPU temps.  Now I 
just need to find a nice graphical client since xsensors does not work 
with BMC based systems.

Keith

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel SRSH4 Motherboard Sensors

[Jean Delvare]

Keith,

On Tue, 05 Jun 2007 06:50:40 -0600, Keith Romberg wrote:
> Overall I am happy that I can at least now monitor the CPU temps.  Now I 
> just need to find a nice graphical client since xsensors does not work 
> with BMC based systems.

Adding support for a new device in xsensors is pretty simple, I've done
it several times already.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors