* Re: [lm-sensors] Support for Intel DG33FB main board?
2009-01-01 2:56 [lm-sensors] Support for Intel DG33FB main board? Stephen Clark
@ 2009-01-08 12:44 ` Jean Delvare
2009-01-08 16:42 ` Stephen Clark
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Jean Delvare @ 2009-01-08 12:44 UTC (permalink / raw)
To: lm-sensors
Hi Steve,
On Wed, 31 Dec 2008 21:56:47 -0500, Stephen Clark wrote:
> I have a new intel DG33FB mainboard when I run sensors-detect I get the following:
> ...
> Trying family `SMSC'... Yes
> Found `SMSC LPC47M182 Super IO Fan Sensors'
> (but not activated)
> ...
> Intel Core family thermal sensor... Success!
> (driver `coretemp')
>
> This lets me see the temps of the cores on my q6600 but not
> voltages or fan speeds. Are there any plans to support this
> main boards further?
>
> sensors version 3.0.2 with libsensors version 3.0.2
The hardware monitoring features of the LPC47M182 are very often
nut used (and thus disabled), we don't even have a driver for them.
This means that hardware monitoring is done by either a chip on the
SMBus (Did sensors-detect find an SMBus to scan? Did it find any
unknown chip there maybe? Including the full output of sensors-detect
helps) or, if the board is based on an ICH8 or later Intel south
bridge, by the south bridge itself. We don't yet support the ICH8
integrated sensors, unfortunately [1].
[1] http://lists.lm-sensors.org/pipermail/lm-sensors/2009-January/025045.html
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [lm-sensors] Support for Intel DG33FB main board?
2009-01-01 2:56 [lm-sensors] Support for Intel DG33FB main board? Stephen Clark
2009-01-08 12:44 ` Jean Delvare
@ 2009-01-08 16:42 ` Stephen Clark
2009-01-08 16:46 ` Jean Delvare
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Stephen Clark @ 2009-01-08 16:42 UTC (permalink / raw)
To: lm-sensors
Jean Delvare wrote:
> Hi Steve,
>
> On Wed, 31 Dec 2008 21:56:47 -0500, Stephen Clark wrote:
>> I have a new intel DG33FB mainboard when I run sensors-detect I get the following:
>> ...
>> Trying family `SMSC'... Yes
>> Found `SMSC LPC47M182 Super IO Fan Sensors'
>> (but not activated)
>> ...
>> Intel Core family thermal sensor... Success!
>> (driver `coretemp')
>>
>> This lets me see the temps of the cores on my q6600 but not
>> voltages or fan speeds. Are there any plans to support this
>> main boards further?
>>
>> sensors version 3.0.2 with libsensors version 3.0.2
>
> The hardware monitoring features of the LPC47M182 are very often
> nut used (and thus disabled), we don't even have a driver for them.
>
> This means that hardware monitoring is done by either a chip on the
> SMBus (Did sensors-detect find an SMBus to scan? Did it find any
> unknown chip there maybe? Including the full output of sensors-detect
> helps) or, if the board is based on an ICH8 or later Intel south
> bridge, by the south bridge itself. We don't yet support the ICH8
> integrated sensors, unfortunately [1].
>
> [1] http://lists.lm-sensors.org/pipermail/lm-sensors/2009-January/025045.html
>
Hi Jean,
Thanks for the reply, here is the complete output of sensors-detect:
# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)
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.
We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9
We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported I2C/SMBus adapters, you can have
them scanned by manually loading the modules before running this script.
We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.
Next adapter: SMBus I801 adapter at 3000 (i2c-0)
Do you want to scan it? (YES/no/selectively):
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 0x51
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)
Probing for `EDID EEPROM'... No
Client found at address 0x53
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
Some chips are also 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 LM78-J' 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
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some Super I/O chips may also contain 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'... No
Trying family `SMSC'... Yes
Found `SMSC LPC47M182 Super IO Fan Sensors'
(but not activated)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp' (should be inserted):
Detects correctly:
* Chip `Intel Core family thermal sensor' (confidence: 9)
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
Starting lm_sensors: loading module coretemp [ OK ]
[root@joker20 ~]#
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [lm-sensors] Support for Intel DG33FB main board?
2009-01-01 2:56 [lm-sensors] Support for Intel DG33FB main board? Stephen Clark
2009-01-08 12:44 ` Jean Delvare
2009-01-08 16:42 ` Stephen Clark
@ 2009-01-08 16:46 ` Jean Delvare
2009-01-08 20:25 ` Stephen Clark
2009-02-01 22:35 ` Stefan Brüns
4 siblings, 0 replies; 6+ messages in thread
From: Jean Delvare @ 2009-01-08 16:46 UTC (permalink / raw)
To: lm-sensors
On Thu, 08 Jan 2009 11:42:27 -0500, Stephen Clark wrote:
> Thanks for the reply, here is the complete output of sensors-detect:
>
> # sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)
>
> 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.
>
> We can start with probing for (PCI) I2C or SMBus adapters.
> Do you want to probe now? (YES/no):
> Probing for PCI bus adapters...
> Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9
>
> We will now try to load each adapter module in turn.
> Module `i2c-i801' already loaded.
> If you have undetectable or unsupported I2C/SMBus adapters, you can have
> them scanned by manually loading the modules before running this script.
>
> We are now going to do the I2C/SMBus adapter probings. Some chips may
> be double detected; we choose the one with the highest confidence
> value in that case.
> If you found that the adapter hung after probing a certain address,
> you can specify that address to remain unprobed.
>
> Next adapter: SMBus I801 adapter at 3000 (i2c-0)
> Do you want to scan it? (YES/no/selectively):
SMBus adapter found, but...
> 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 0x51
> 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)
> Probing for `EDID EEPROM'... No
> Client found at address 0x53
> 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
... nothing on the SMBus that remotely looks like a hardware monitoring
chip. This suggests the hardware monitoring is done by the ICH9,
meaning you're out of luck, sorry.
Maybe you can check the motherboard documentation (Intel make good
ones) for confirmation.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [lm-sensors] Support for Intel DG33FB main board?
2009-01-01 2:56 [lm-sensors] Support for Intel DG33FB main board? Stephen Clark
` (2 preceding siblings ...)
2009-01-08 16:46 ` Jean Delvare
@ 2009-01-08 20:25 ` Stephen Clark
2009-02-01 22:35 ` Stefan Brüns
4 siblings, 0 replies; 6+ messages in thread
From: Stephen Clark @ 2009-01-08 20:25 UTC (permalink / raw)
To: lm-sensors
Jean Delvare wrote:
> On Thu, 08 Jan 2009 11:42:27 -0500, Stephen Clark wrote:
>> Thanks for the reply, here is the complete output of sensors-detect:
>>
>> # sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)
>>
>> 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.
>>
>> We can start with probing for (PCI) I2C or SMBus adapters.
>> Do you want to probe now? (YES/no):
>> Probing for PCI bus adapters...
>> Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9
>>
>> We will now try to load each adapter module in turn.
>> Module `i2c-i801' already loaded.
>> If you have undetectable or unsupported I2C/SMBus adapters, you can have
>> them scanned by manually loading the modules before running this script.
>>
>> We are now going to do the I2C/SMBus adapter probings. Some chips may
>> be double detected; we choose the one with the highest confidence
>> value in that case.
>> If you found that the adapter hung after probing a certain address,
>> you can specify that address to remain unprobed.
>>
>> Next adapter: SMBus I801 adapter at 3000 (i2c-0)
>> Do you want to scan it? (YES/no/selectively):
>
> SMBus adapter found, but...
>
>> 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 0x51
>> 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)
>> Probing for `EDID EEPROM'... No
>> Client found at address 0x53
>> 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
>
> ... nothing on the SMBus that remotely looks like a hardware monitoring
> chip. This suggests the hardware monitoring is done by the ICH9,
> meaning you're out of luck, sorry.
>
> Maybe you can check the motherboard documentation (Intel make good
> ones) for confirmation.
>
From the product guide:
"Intel Desktop Board DG33FB Product Guide
Hardware Management Features
The hardware management features of Desktop Board DG33FB enable the board to be
compatible with the Wired for Management (WfM) specification. The board has
several hardware management features including the following:
• Fan speed monitoring and control
• Thermal and voltage monitoring
• Chassis intrusion detection
Hardware Monitoring and Fan Speed Control
The features of the hardware monitoring and fan speed control include:
• Monitoring of power supply voltages to detect levels above and below acceptable
values
• Intel Quiet System Technology fan speed control, delivering acoustically-optimized
thermal management
NOTE
Memory must be installed in the Channel A, DIMM 0 socket to enable Intel
Quiet System Technology.
• Fan speed controllers and sensors integrated into the ICH9DH
• Thermal sensors in the processor, GMCH, and ICH9DH, plus an onboard remote
sensor
• Thermally monitored closed-loop fan control, for all onboard fans, that can adjust
fan speed or switch the fans off as needed"
Doesn't mean much to me.
Anyway thanks for taking the time to respond and keep up the great work.
Regards,
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [lm-sensors] Support for Intel DG33FB main board?
2009-01-01 2:56 [lm-sensors] Support for Intel DG33FB main board? Stephen Clark
` (3 preceding siblings ...)
2009-01-08 20:25 ` Stephen Clark
@ 2009-02-01 22:35 ` Stefan Brüns
4 siblings, 0 replies; 6+ messages in thread
From: Stefan Brüns @ 2009-02-01 22:35 UTC (permalink / raw)
To: lm-sensors
Monitoring _should_ be supported via the HECI driver. If it actually works
depends (for now) on the MB having an AMT engine or not (Everything labeled with
vPro has one, other ones dont know ...).
For AMT, have a look at www.openamt.org
For everything else, sensors are supported via QST over HECI - unfortunately,
there is no support for this yet, but have a look at
http://software.intel.com/en-us/forums/manageability-software-
the (near) future.
Regards,
Stefan
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 6+ messages in thread