[lm-sensors] Intel DG45FC

[lm-sensors] Intel DG45FC

[Anthony Arobone]

[-- Attachment #1.1: Type: text/plain, Size: 966 bytes --]

I apologize if this was already brought up on the list.

I just purchased an Intel DG45FC mini-itx board (I believe this is
considered ICH10, or some variation).  I can't seem to get lm_sensors to
report the temps/fans/volts of the board.  Everything is zero.  The cpu
temps are working via the coretemp module, but nothing else.  Here is what
I'm doing:

Gentoo 2.6.26-r1 kernel; using i2c-i801 as module, lm85 as module.
SVN lm_sensors as of maybe a week ago, just the apps

When I run sensors-detect it tells me I should be using lm85.  I modprobe
lm85 successfully but when I run sensors everything is zero.

Is this the correct module for this board?  I can't seem to find any info
about the chip/sensor on board.
You probably want to see the output of lspci -v but I don't have the board
hooked up right now, will hookup this weekend.  What I can tell you is that
the device id is "3a30" from the lspci output.  And the chipset is the G45.

Any ideas?  Thanks

[-- Attachment #1.2: Type: text/html, Size: 1101 bytes --]

[-- 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 DG45FC

[Jean Delvare]

Hi Anthony,

On Thu, 18 Sep 2008 16:58:23 -0700, Anthony Arobone wrote:
> I apologize if this was already brought up on the list.
> 
> I just purchased an Intel DG45FC mini-itx board (I believe this is
> considered ICH10, or some variation).  I can't seem to get lm_sensors to
> report the temps/fans/volts of the board.  Everything is zero.  The cpu
> temps are working via the coretemp module, but nothing else.  Here is what
> I'm doing:
> 
> Gentoo 2.6.26-r1 kernel; using i2c-i801 as module, lm85 as module.
> SVN lm_sensors as of maybe a week ago, just the apps
> 
> When I run sensors-detect it tells me I should be using lm85.  I modprobe
> lm85 successfully but when I run sensors everything is zero.

Can you please provide the complete output of sensors-detect?

When you say "everything is 0", do you mean that nothing is displayed,
or many lines are displayed but all values are 0? In the latter case,
that would be the same problem as reported there:
http://www.lm-sensors.org/ticket/2182
I have no clue what is causing this, sorry.

> Is this the correct module for this board?  I can't seem to find any info
> about the chip/sensor on board.

In general we don't know which board has what sensor chip. There are
simply too many boards out there to keep track. sensors-detect should
tell you. Or look into the vendor-provided documentation. Or try to
take a physical look at the board (not easy in your case, the LM85 is
relatively small.)

> You probably want to see the output of lspci -v but I don't have the board
> hooked up right now, will hookup this weekend.  What I can tell you is that
> the device id is "3a30" from the lspci output.  And the chipset is the G45.

-- 
Jean Delvare

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

Re: [lm-sensors] Intel DG45FC

[Anthony Arobone]

[-- Attachment #1.1: Type: text/plain, Size: 2042 bytes --]

Finally got the board all hooked up again.  I've attached a text file with
all the output I could think of.  Notice the dmesg warning when modprobing
lm85.

Thanks for your help.


On Sun, Sep 21, 2008 at 7:56 AM, Jean Delvare <khali@linux-fr.org> wrote:

> Hi Anthony,
>
> On Thu, 18 Sep 2008 16:58:23 -0700, Anthony Arobone wrote:
> > I apologize if this was already brought up on the list.
> >
> > I just purchased an Intel DG45FC mini-itx board (I believe this is
> > considered ICH10, or some variation).  I can't seem to get lm_sensors to
> > report the temps/fans/volts of the board.  Everything is zero.  The cpu
> > temps are working via the coretemp module, but nothing else.  Here is
> what
> > I'm doing:
> >
> > Gentoo 2.6.26-r1 kernel; using i2c-i801 as module, lm85 as module.
> > SVN lm_sensors as of maybe a week ago, just the apps
> >
> > When I run sensors-detect it tells me I should be using lm85.  I modprobe
> > lm85 successfully but when I run sensors everything is zero.
>
> Can you please provide the complete output of sensors-detect?
>
> When you say "everything is 0", do you mean that nothing is displayed,
> or many lines are displayed but all values are 0? In the latter case,
> that would be the same problem as reported there:
> http://www.lm-sensors.org/ticket/2182
> I have no clue what is causing this, sorry.
>
> > Is this the correct module for this board?  I can't seem to find any info
> > about the chip/sensor on board.
>
> In general we don't know which board has what sensor chip. There are
> simply too many boards out there to keep track. sensors-detect should
> tell you. Or look into the vendor-provided documentation. Or try to
> take a physical look at the board (not easy in your case, the LM85 is
> relatively small.)
>
> > You probably want to see the output of lspci -v but I don't have the
> board
> > hooked up right now, will hookup this weekend.  What I can tell you is
> that
> > the device id is "3a30" from the lspci output.  And the chipset is the
> G45.
>
> --
> Jean Delvare
>

[-- Attachment #1.2: Type: text/html, Size: 2729 bytes --]

[-- Attachment #2: sensors-detect.txt --]
[-- Type: text/plain, Size: 18130 bytes --]


# sensors-detect 
revision 5291 (2008-06-23 23:40:46 -0700)

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 ICH10

We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no):
Module loaded successfully.
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 f000 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x2e
Probing for `Myson MTP008'...                               No
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM78-J'...              No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM85 or LM96000'...     Success!
    (confidence 7, driver `lm85')
Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... No
Probing for `SMSC EMC6D100, EMC6D101 or EMC6D102'...        No
Probing for `Analog Devices ADT7462'...                     No
Probing for `Analog Devices ADT7467 or ADT7468'...          No
Probing for `Analog Devices ADT7470'...                     No
Probing for `Analog Devices ADT7473'...                     No
Probing for `Analog Devices ADT7475'...                     No
Probing for `Analog Devices ADT7476'...                     No
Probing for `Andigilog aSC7611'...                          No
Probing for `Andigilog aSC7621'...                          No
Probing for `National Semiconductor LM87'...                No
Probing for `National Semiconductor LM93'...                No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83792D'...                            No
Probing for `Winbond W83793R/G'...                          No
Probing for `Winbond W83791SD'...                           No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG'...                          No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Winbond W83L786NR/NG/R/G'...                   No
Probing for `Winbond W83L785TS-S'...                        No
Probing for `Analog Devices ADM9240'...                     No
Probing for `Dallas Semiconductor DS1780'...                No
Probing for `National Semiconductor LM81'...                No
Probing for `Analog Devices ADM1026'...                     No
Probing for `Analog Devices ADM1025'...                     No
Probing for `Analog Devices ADM1029'...                     No
Probing for `Analog Devices ADM1030'...                     No
Probing for `Analog Devices ADM1031'...                     No
Probing for `Analog Devices ADM1022'...                     No
Probing for `Texas Instruments THMC50'...                   No
Probing for `Analog Devices ADM1028'...                     No
Probing for `ITE IT8712F'...                                No
Probing for `SMSC DME1737'...                               No
Probing for `SMSC SCH5027D-NW'...                           No
Probing for `Fintek F75373S/SG'...                          No
Probing for `Fintek F75375S/SP'...                          No
Probing for `Fintek F75387SG/RG'...                         No
Probing for `Analog Devices ADM1024'...                     No
Probing for `Winbond W83791D'...                            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)
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'...                   Yes
Found `Nat. Semi. PC8374L Super IO 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
VIA C7 thermal and voltage sensors...                       No

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `lm85' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at f000'
    Busdriver `i2c-i801', I2C address 0x2e
    Chip `National Semiconductor LM85 or LM96000' (confidence: 7)

Driver `coretemp' (should be inserted):
  Detects correctly:
  * Chip `Intel Core family thermal sensor' (confidence: 9)

To load everything that is needed, execute the commands below...

#----cut here----
# I2C adapter drivers
modprobe i2c-i801
# Chip drivers
modprobe lm85
# Warning: the required module coretemp is not currently installed
# on your system. For status of 2.6 kernel ports check
# http://www.lm-sensors.org/wiki/Devices. If driver is built
# into the kernel, or unavailable, comment out the following line.
modprobe coretemp
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----end cut here----
Do you want to overwrite /etc/conf.d/lm_sensors? Enter s for other filename (YES/no/s):
Done.
You should now start the lm_sensors service to load the required
kernel modules.








# modprobe lm85
dmesg output:
i2c-adapter i2c-0: Unrecognized version/stepping 0x68 Defaulting to LM85.








# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +37 C  (high =  +100 C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +37 C  (high =  +100 C)

lm85-i2c-0-2e
Adapter: SMBus I801 adapter at f000
V1.5:       +0.00 V  (min =  +0.00 V, max =  +3.32 V)
VCore:      +0.00 V  (min =  +0.00 V, max =  +2.99 V)
V3.3:       +0.00 V  (min =  +0.00 V, max =  +4.38 V)
V5:         +0.00 V  (min =  +0.00 V, max =  +6.64 V)
V12:        +0.00 V  (min =  +0.00 V, max = +15.94 V)
CPU_Fan:      0 RPM  (min =    0 RPM)                     ALARM
fan2:         0 RPM  (min =    0 RPM)                     ALARM
fan3:         0 RPM  (min =    0 RPM)                     ALARM
fan4:         0 RPM  (min =    0 RPM)                     ALARM
CPU Temp:     +0 C  (low  =  -127 C, high =  +127 C)
Board Temp:
              +0 C  (low  =  -127 C, high =  +127 C)
Remote Temp:
              +0 C  (low  =  -127 C, high =  +127 C)
CPU_PWM:   255
Fan2_PWM:  255
Fan3_PWM:  255
vid:      +2.050 V  (VRM Version 8.2)







# lspci
00:00.0 Host bridge: Intel Corporation Device 2e20 (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Device 2e22 (rev 03)
00:02.1 Display controller: Intel Corporation Device 2e23 (rev 03)
00:03.0 Communication controller: Intel Corporation Device 2e24 (rev 03)
00:19.0 Ethernet controller: Intel Corporation Device 10cd
00:1a.0 USB Controller: Intel Corporation Device 3a37
00:1a.1 USB Controller: Intel Corporation Device 3a38
00:1a.2 USB Controller: Intel Corporation Device 3a39
00:1a.7 USB Controller: Intel Corporation Device 3a3c
00:1b.0 Audio device: Intel Corporation Device 3a3e
00:1d.0 USB Controller: Intel Corporation Device 3a34
00:1d.1 USB Controller: Intel Corporation Device 3a35
00:1d.2 USB Controller: Intel Corporation Device 3a36
00:1d.7 USB Controller: Intel Corporation Device 3a3a
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation Device 3a16
00:1f.2 IDE interface: Intel Corporation Device 3a20
00:1f.3 SMBus: Intel Corporation Device 3a30
00:1f.5 IDE interface: Intel Corporation Device 3a26








# lspci -v
00:00.0 Host bridge: Intel Corporation Device 2e20 (rev 03)
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, fast devsel, latency 0
        Capabilities: [e0] Vendor Specific Information <?>
        Kernel driver in use: agpgart-intel
        Kernel modules: intel-agp

00:02.0 VGA compatible controller: Intel Corporation Device 2e22 (rev 03) (prog-if 00 [VGA controller])
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at ff400000 (64-bit, non-prefetchable) [size=4M]
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at f1c0 [size=8]
        Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
        Capabilities: [d0] Power Management version 2

00:02.1 Display controller: Intel Corporation Device 2e23 (rev 03)
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, fast devsel, latency 0
        Memory at ff800000 (64-bit, non-prefetchable) [size=1M]
        Capabilities: [d0] Power Management version 2

00:03.0 Communication controller: Intel Corporation Device 2e24 (rev 03)
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at ff970000 (64-bit, non-prefetchable) [size=16]
        Capabilities: [50] Power Management version 3
        Capabilities: [8c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-

00:19.0 Ethernet controller: Intel Corporation Device 10cd
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, fast devsel, latency 0, IRQ 223
        Memory at ff900000 (32-bit, non-prefetchable) [size=128K]
        Memory at ff960000 (32-bit, non-prefetchable) [size=4K]
        I/O ports at f0e0 [size=32]
        Capabilities: [c8] Power Management version 2
        Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
        Capabilities: [e0] Vendor Specific Information <?>
        Kernel driver in use: e1000e

00:1a.0 USB Controller: Intel Corporation Device 3a37 (prog-if 00 [UHCI])
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, medium devsel, latency 0, IRQ 16
        I/O ports at f0c0 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd

00:1a.1 USB Controller: Intel Corporation Device 3a38 (prog-if 00 [UHCI])
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, medium devsel, latency 0, IRQ 21
        I/O ports at f0a0 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd

00:1a.2 USB Controller: Intel Corporation Device 3a39 (prog-if 00 [UHCI])
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, medium devsel, latency 0, IRQ 18
        I/O ports at f080 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd

00:1a.7 USB Controller: Intel Corporation Device 3a3c (prog-if 20 [EHCI])
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, medium devsel, latency 0, IRQ 18
        Memory at ff950000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] Debug port: BAR=1 offset=00a0
        Capabilities: [98] Vendor Specific Information <?>
        Kernel driver in use: ehci_hcd

00:1b.0 Audio device: Intel Corporation Device 3a3e
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, fast devsel, latency 0, IRQ 22
        Memory at ff940000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
        Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
        Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
        Capabilities: [100] Virtual Channel <?>
        Capabilities: [130] Root Complex Link <?>
        Kernel driver in use: HDA Intel
        Kernel modules: snd-hda-intel

00:1d.0 USB Controller: Intel Corporation Device 3a34 (prog-if 00 [UHCI])
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, medium devsel, latency 0, IRQ 23
        I/O ports at f060 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd

00:1d.1 USB Controller: Intel Corporation Device 3a35 (prog-if 00 [UHCI])
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, medium devsel, latency 0, IRQ 19
        I/O ports at f040 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd

00:1d.2 USB Controller: Intel Corporation Device 3a36 (prog-if 00 [UHCI])
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, medium devsel, latency 0, IRQ 18
        I/O ports at f020 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd

00:1d.7 USB Controller: Intel Corporation Device 3a3a (prog-if 20 [EHCI])
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, medium devsel, latency 0, IRQ 23
        Memory at ff930000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] Debug port: BAR=1 offset=00a0
        Capabilities: [98] Vendor Specific Information <?>
        Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) (prog-if 01 [Subtractive decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
        Capabilities: [50] Subsystem: Gammagraphx, Inc. Device 0000

00:1f.0 ISA bridge: Intel Corporation Device 3a16
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, medium devsel, latency 0
        Capabilities: [e0] Vendor Specific Information <?>

00:1f.2 IDE interface: Intel Corporation Device 3a20 (prog-if 8f [Master SecP SecO PriP PriO])
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 11
        I/O ports at f1b0 [size=8]
        I/O ports at f1a0 [size=4]
        I/O ports at f190 [size=8]
        I/O ports at f180 [size=4]
        I/O ports at f170 [size=16]
        I/O ports at f160 [size=16]
        Capabilities: [70] Power Management version 3
        Capabilities: [b0] Vendor Specific Information <?>

00:1f.3 SMBus: Intel Corporation Device 3a30
        Subsystem: Intel Corporation Device 5003
        Flags: medium devsel, IRQ 18
        Memory at ff920000 (64-bit, non-prefetchable) [size=256]
        I/O ports at f000 [size=32]
        Kernel driver in use: i801_smbus
        Kernel modules: i2c-i801

00:1f.5 IDE interface: Intel Corporation Device 3a26 (prog-if 85 [Master SecO PriO])
        Subsystem: Intel Corporation Device 5003
        Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 11
        I/O ports at f150 [size=8]
        I/O ports at f140 [size=4]
        I/O ports at f130 [size=8]
        I/O ports at f120 [size=4]
        I/O ports at f110 [size=16]
        I/O ports at f100 [size=16]
        Capabilities: [70] Power Management version 3
        Capabilities: [b0] Vendor Specific Information <?>












[-- Attachment #3: 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 DG45FC

[Jean Delvare]

Hi Anthony,

On Thu, 25 Sep 2008 17:13:17 -0700, Anthony Arobone wrote:
> Finally got the board all hooked up again.  I've attached a text file with
> all the output I could think of.  Notice the dmesg warning when modprobing
> lm85.
> (...)
> lm85-i2c-0-2e
> Adapter: SMBus I801 adapter at f000
> V1.5:       +0.00 V  (min =  +0.00 V, max =  +3.32 V)
> VCore:      +0.00 V  (min =  +0.00 V, max =  +2.99 V)
> V3.3:       +0.00 V  (min =  +0.00 V, max =  +4.38 V)
> V5:         +0.00 V  (min =  +0.00 V, max =  +6.64 V)
> V12:        +0.00 V  (min =  +0.00 V, max = +15.94 V)
> CPU_Fan:      0 RPM  (min =    0 RPM)                     ALARM
> fan2:         0 RPM  (min =    0 RPM)                     ALARM
> fan3:         0 RPM  (min =    0 RPM)                     ALARM
> fan4:         0 RPM  (min =    0 RPM)                     ALARM
> CPU Temp:     +0 C  (low  =  -127 C, high =  +127 C)
> Board Temp:
>               +0 C  (low  =  -127 C, high =  +127 C)
> Remote Temp:
>               +0 C  (low  =  -127 C, high =  +127 C)
> CPU_PWM:   255
> Fan2_PWM:  255
> Fan3_PWM:  255
> vid:      +2.050 V  (VRM Version 8.2)

As I suspected, this is exactly the same case as in ticket #2182:
http://www.lm-sensors.org/ticket/2182

I've updated wiki/Devices to mention this known issue. At this point we
have no idea how to solve it.

Does your BIOS display (non-zero) hardware monitoring information?

-- 
Jean Delvare

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

Re: [lm-sensors] Intel DG45FC

[Jean Delvare]

Hi again Anthony,

On Thu, 25 Sep 2008 17:13:17 -0700, Anthony Arobone wrote:
> Finally got the board all hooked up again.  I've attached a text file with
> all the output I could think of.  Notice the dmesg warning when modprobing
> lm85.

Can you please provide a dump of your chip? You should be able to get
it the following way:

# rmmod lm85
# modprobe i2c-dev
# i2cdump 0 0x2e b

Thanks,
-- 
Jean Delvare

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

Re: [lm-sensors] Intel DG45FC

[Anthony Arobone]

[-- Attachment #1.1: Type: text/plain, Size: 2068 bytes --]

Hi Jena,  thanks a lot for your help.

My BIOS does display all the correct values for temps and voltage for
everything.


On Fri, Sep 26, 2008 at 4:42 AM, Jean Delvare <khali@linux-fr.org> wrote:

> Hi again Anthony,
>
> On Thu, 25 Sep 2008 17:13:17 -0700, Anthony Arobone wrote:
> > Finally got the board all hooked up again.  I've attached a text file
> with
> > all the output I could think of.  Notice the dmesg warning when
> modprobing
> > lm85.
>

>
> Can you please provide a dump of your chip? You should be able to get
> it the following way:
>
> # rmmod lm85
> # modprobe i2c-dev
> # i2cdump 0 0x2e b
>

I have i2c-dev built into kernel. Hope that's not a problem.

# i2cdump 0 0x2e b
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/0, address 0x2e, mode byte
Continue? [Y/n] Y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
20: 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff    ................
30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 01 68    ..............?h
40: 04 00 00 00 00 ff 00 ff 00 ff 00 ff 00 ff 81 7f    ?.............??
50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 c4    ????........bbb?
60: c4 c4 00 00 80 80 80 00 00 00 64 64 64 44 44 a4    ??..???...dddDD?
70: ff ff ff 00 00 00 08 00 00 22 6e 6e 6e 00 00 00    ......?.."nnn...
80: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ?...............
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00    ........?.......

[-- Attachment #1.2: Type: text/html, Size: 3065 bytes --]

[-- 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 DG45FC

[Jean Delvare]

Hi Anthony,

On Fri, 26 Sep 2008 10:19:31 -0700, Anthony Arobone wrote:
> Hi Jena,  thanks a lot for your help.
> 
> My BIOS does display all the correct values for temps and voltage for
> everything.

OK. So either the LM96000 can be re-enabled, or there's another
monitoring chip on your motherboard.

Can you please list the labels and values displayed by your BIOS? To
check whether this corresponds to the LM96000 inputs or not.

> > Can you please provide a dump of your chip? You should be able to get
> > it the following way:
> >
> > # rmmod lm85
> > # modprobe i2c-dev
> > # i2cdump 0 0x2e b
> >
> 
> I have i2c-dev built into kernel. Hope that's not a problem.

It's OK.

> # i2cdump 0 0x2e b
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c/0, address 0x2e, mode byte
> Continue? [Y/n] Y
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
> 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> 20: 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff    ................
> 30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 01 68    ..............?h
> 40: 04 00 00 00 00 ff 00 ff 00 ff 00 ff 00 ff 81 7f    ?.............??
> 50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 c4    ????........bbb?
> 60: c4 c4 00 00 80 80 80 00 00 00 64 64 64 44 44 a4    ??..???...dddDD?
> 70: ff ff ff 00 00 00 08 00 00 22 6e 6e 6e 00 00 00    ......?.."nnn...
> 80: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ?...............
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> f0: 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00    ........?.......

OK, so this is basically the same case as in ticket 2182: first version
of the LM96000, and strange value in register 0x6f. So please do the
same test I suggested in this ticket:

# rmmod lm85
# i2cset -y 0 0x2e 0x40 0x04
# i2cset -y 0 0x2e 0x6f 0x00
# i2cset -y 0 0x2e 0x40 0x05
# modprobe lm85

And report if it helps or not.

-- 
Jean Delvare

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

Re: [lm-sensors] Intel DG45FC

[Anthony Arobone]

[-- Attachment #1.1: Type: text/plain, Size: 3276 bytes --]

On Sat, Sep 27, 2008 at 4:47 AM, Jean Delvare <khali@linux-fr.org> wrote:

> Hi Anthony,
>
> On Fri, 26 Sep 2008 10:19:31 -0700, Anthony Arobone wrote:
> > Hi Jena,  thanks a lot for your help.
> >
> > My BIOS does display all the correct values for temps and voltage for
> > everything.
>
> OK. So either the LM96000 can be re-enabled, or there's another
> monitoring chip on your motherboard.
>
> Can you please list the labels and values displayed by your BIOS? To
> check whether this corresponds to the LM96000 inputs or not.



Here is what my BIOS list, the "xxx" is just a replacement for that actual 3
decimal numbers that i didn't capture:

CPU Die/Package Temp         Prochot-49C
Motherboard Temp                 38C
ICH Temp                              65C
MCH Temp                            45C

+12v                                     12.xxxv
+5v                                       5.xxxv
+3.3v Standby                       3.3xxv
MCH Vcc                              1.1135v
CPU 1 Vccp                          1.218v

CPU Cooling FAN                  836 RPM
Chassis Inlet FAN                  3061 RPM



>
>
> > > Can you please provide a dump of your chip? You should be able to get
> > > it the following way:
> > >
> > > # rmmod lm85
> > > # modprobe i2c-dev
> > > # i2cdump 0 0x2e b
> > >
> >
> > I have i2c-dev built into kernel. Hope that's not a problem.
>
> It's OK.
>
> > # i2cdump 0 0x2e b
> > WARNING! This program can confuse your I2C bus, cause data loss and
> worse!
> > I will probe file /dev/i2c/0, address 0x2e, mode byte
> > Continue? [Y/n] Y
> >      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
> > 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> > 20: 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff    ................
> > 30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 01 68    ..............?h
> > 40: 04 00 00 00 00 ff 00 ff 00 ff 00 ff 00 ff 81 7f    ?.............??
> > 50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 c4    ????........bbb?
> > 60: c4 c4 00 00 80 80 80 00 00 00 64 64 64 44 44 a4    ??..???...dddDD?
> > 70: ff ff ff 00 00 00 08 00 00 22 6e 6e 6e 00 00 00    ......?.."nnn...
> > 80: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ?...............
> > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> > a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
> > f0: 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00    ........?.......
>
> OK, so this is basically the same case as in ticket 2182: first version
> of the LM96000, and strange value in register 0x6f. So please do the
> same test I suggested in this ticket:
>
> # rmmod lm85
> # i2cset -y 0 0x2e 0x40 0x04
> # i2cset -y 0 0x2e 0x6f 0x00
> # i2cset -y 0 0x2e 0x40 0x05
> # modprobe lm85
>
> And report if it helps or not.
>

Didn't help.  Everything is still zero.  :(

[-- Attachment #1.2: Type: text/html, Size: 5747 bytes --]

[-- 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 DG45FC

[Jean Delvare]

On Sat, 27 Sep 2008 11:08:12 -0700, Anthony Arobone wrote:
> On Sat, Sep 27, 2008 at 4:47 AM, Jean Delvare <khali@linux-fr.org> wrote:
> > OK. So either the LM96000 can be re-enabled, or there's another
> > monitoring chip on your motherboard.
> >
> > Can you please list the labels and values displayed by your BIOS? To
> > check whether this corresponds to the LM96000 inputs or not.
> 
> Here is what my BIOS list, the "xxx" is just a replacement for that actual 3
> decimal numbers that i didn't capture:
> 
> CPU Die/Package Temp         Prochot-49C
> Motherboard Temp                 38C
> ICH Temp                              65C
> MCH Temp                            45C
> 
> +12v                                     12.xxxv
> +5v                                       5.xxxv
> +3.3v Standby                       3.3xxv
> MCH Vcc                              1.1135v
> CPU 1 Vccp                          1.218v
> 
> CPU Cooling FAN                  836 RPM
> Chassis Inlet FAN                  3061 RPM

This seems to match the LM96000 features (assuming "CPU Die/Package
Temp" is from the Intel Core internal sensor.)

> > (...)
> > OK, so this is basically the same case as in ticket 2182: first version
> > of the LM96000, and strange value in register 0x6f. So please do the
> > same test I suggested in this ticket:
> >
> > # rmmod lm85
> > # i2cset -y 0 0x2e 0x40 0x04
> > # i2cset -y 0 0x2e 0x6f 0x00
> > # i2cset -y 0 0x2e 0x40 0x05
> > # modprobe lm85
> >
> > And report if it helps or not.
> 
> Didn't help.  Everything is still zero.  :(

OK... No other idea for now.


-- 
Jean Delvare

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

Re: [lm-sensors] Intel DG45FC

[Anthony Arobone]

[-- Attachment #1.1: Type: text/plain, Size: 2120 bytes --]

On Sat, Sep 27, 2008 at 1:16 PM, Jean Delvare <khali@linux-fr.org> wrote:

> On Sat, 27 Sep 2008 11:08:12 -0700, Anthony Arobone wrote:
> > On Sat, Sep 27, 2008 at 4:47 AM, Jean Delvare <khali@linux-fr.org>
> wrote:
> > > OK. So either the LM96000 can be re-enabled, or there's another
> > > monitoring chip on your motherboard.
> > >
> > > Can you please list the labels and values displayed by your BIOS? To
> > > check whether this corresponds to the LM96000 inputs or not.
> >
> > Here is what my BIOS list, the "xxx" is just a replacement for that
> actual 3
> > decimal numbers that i didn't capture:
> >
> > CPU Die/Package Temp         Prochot-49C
> > Motherboard Temp                 38C
> > ICH Temp                              65C
> > MCH Temp                            45C
> >
> > +12v                                     12.xxxv
> > +5v                                       5.xxxv
> > +3.3v Standby                       3.3xxv
> > MCH Vcc                              1.1135v
> > CPU 1 Vccp                          1.218v
> >
> > CPU Cooling FAN                  836 RPM
> > Chassis Inlet FAN                  3061 RPM
>
> This seems to match the LM96000 features (assuming "CPU Die/Package
> Temp" is from the Intel Core internal sensor.)
>
> > > (...)
> > > OK, so this is basically the same case as in ticket 2182: first version
> > > of the LM96000, and strange value in register 0x6f. So please do the
> > > same test I suggested in this ticket:
> > >
> > > # rmmod lm85
> > > # i2cset -y 0 0x2e 0x40 0x04
> > > # i2cset -y 0 0x2e 0x6f 0x00
> > > # i2cset -y 0 0x2e 0x40 0x05
> > > # modprobe lm85
> > >
> > > And report if it helps or not.
> >
> > Didn't help.  Everything is still zero.  :(
>
> OK... No other idea for now.
>
>
> --
> Jean Delvare
>


Would the tech docs on this sensor be helpful?  I found them on the Intel
site.  It describes all the registers in detail.

See Chapter 23.
http://www.intel.com/Assets/PDF/datasheet/319973.pdf

Let me know if I can do any debugging or coding to help out.  I'm proficient
in C and C++.  Just don't understand how all this sensor stuff works ;)

[-- Attachment #1.2: Type: text/html, Size: 3620 bytes --]

[-- 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 DG45FC

[Jean Delvare]

Hi Anthony,

On Tue, 21 Oct 2008 12:06:43 -0700, Anthony Arobone wrote:
> Would the tech docs on this sensor be helpful?  I found them on the Intel
> site.  It describes all the registers in detail.
> 
> See Chapter 23.
> http://www.intel.com/Assets/PDF/datasheet/319973.pdf

This is the ICH10 (south bridge) datasheet. The ICH10 does indeed
include sensors for temperature and fans, but we don't support them.
And I doubt that's what your board uses though, as your BIOS also
displays voltage values while I don't think the ICH10 has voltage
sensors.

> Let me know if I can do any debugging or coding to help out.  I'm proficient
> in C and C++.  Just don't understand how all this sensor stuff works ;)

I just had a new idea. All users who reported the mysterious all-zero
LM96000 chip also have a PC8374L or compatible super-I/O chip. I am
almost certain that what sensors-detect identifies as an LM96000 is
actually the PC8374L super-I/O chip, as it is documented as exposing
its hardware monitoring registers on the SMBus.

Please provide a dump of the logical device 8 of your Super-I/O:

isadump 0x2e 0x2f 8

-- 
Jean Delvare

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

Re: [lm-sensors] Intel DG45FC

[Anthony Arobone]

[-- Attachment #1.1: Type: text/plain, Size: 3278 bytes --]

On Wed, Oct 29, 2008 at 3:43 AM, Jean Delvare <khali@linux-fr.org> wrote:

> Hi Anthony,
>
> On Tue, 21 Oct 2008 12:06:43 -0700, Anthony Arobone wrote:
> > Would the tech docs on this sensor be helpful?  I found them on the Intel
> > site.  It describes all the registers in detail.
> >
> > See Chapter 23.
> > http://www.intel.com/Assets/PDF/datasheet/319973.pdf
>
> This is the ICH10 (south bridge) datasheet. The ICH10 does indeed
> include sensors for temperature and fans, but we don't support them.
> And I doubt that's what your board uses though, as your BIOS also
> displays voltage values while I don't think the ICH10 has voltage
> sensors.
>
> > Let me know if I can do any debugging or coding to help out.  I'm
> proficient
> > in C and C++.  Just don't understand how all this sensor stuff works ;)
>
> I just had a new idea. All users who reported the mysterious all-zero
> LM96000 chip also have a PC8374L or compatible super-I/O chip. I am
> almost certain that what sensors-detect identifies as an LM96000 is
> actually the PC8374L super-I/O chip, as it is documented as exposing
> its hardware monitoring registers on the SMBus.
>
> Please provide a dump of the logical device 8 of your Super-I/O:
>
> isadump 0x2e 0x2f 8
>


# isadump 0x2e 0x2f 8
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0x2e and data register 0x2f.
Probing bank 8 using bank register 0x07.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41
20: f1 01 00 00 01 01 00 91 00 11 2e 00 00 10 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 03 00 00 04 04 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


So I was looking into this a little more and I came across an Intel driver
called HECI.  I guess it was submitted to the linux kernel, but hasn't made
it in yet.  At any rate, I downloaded it and some other goodies from
http://www.openamt.org/.  In short, I tweaked a few places to get it to
compile and load for my kernel, 2.6.27 (actually on .28-rc3 now).  But I
think this is the new way to access all the Intel sensors, etc.  I don't
know much about it yet, looks like it can do alot.  But I didn't see a way
to get the temp assets from any of the examples, and I don't think I'll have
anymore time to look into this further.

Thanks for all your help though, but I think you are right.  Accessing the
temps via the tradional drivers (for lack of better word) is never going to
happen.  I think its going to be through this HECI driver, but it looks like
whatever support was being put into that has flat lined.

Thanks again

[-- Attachment #1.2: Type: text/html, Size: 4090 bytes --]

[-- 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 DG45FC

[Jean Delvare]

Hi Anthony,

On Fri, 7 Nov 2008 17:38:00 -0800, Anthony Arobone wrote:
> # isadump 0x2e 0x2f 8
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will probe address register 0x2e and data register 0x2f.
> Probing bank 8 using bank register 0x07.
> Continue? [Y/n] y
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41
> 20: f1 01 00 00 01 01 00 91 00 11 2e 00 00 10 00 00
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 03 00 00 04 04 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

OK, so as expected, the logical device with the hardware monitoring
features is disabled. If you look at ticket #2182 starting at:
http://www.lm-sensors.org/ticket/2182#comment:13

You'll see what we tried with the other user to enable the logical
device and see if it "woke up" the "emulated" LM96000. It did not work
for him, but feel free to try too and see if it helps on your board:

isaset -y 0x2e 0x2f 0x07 8
isaset -y 0x2e 0x2f 0x60 0x02
isaset -y 0x2e 0x2f 0x61 0x90
isaset -y 0x2e 0x2f 0x30 1

(After checking in /proc/ioports that there's nothing at 0x290 on your
system.) Then:

rmmod lm85
modprobe lm85

That being said, I'm not holding my breath. Maybe your system has the
same chip variant (WPCD377i) without the hardware monitoring feature
and that's the reason why all the readings are 0 and the actual
monitoring is done by the Intel ICH chip.

> So I was looking into this a little more and I came across an Intel driver
> called HECI.  I guess it was submitted to the linux kernel, but hasn't made
> it in yet.  At any rate, I downloaded it and some other goodies from
> http://www.openamt.org/.  In short, I tweaked a few places to get it to
> compile and load for my kernel, 2.6.27 (actually on .28-rc3 now).  But I
> think this is the new way to access all the Intel sensors, etc.  I don't
> know much about it yet, looks like it can do alot.  But I didn't see a way
> to get the temp assets from any of the examples, and I don't think I'll have
> anymore time to look into this further.
> 
> Thanks for all your help though, but I think you are right.  Accessing the
> temps via the tradional drivers (for lack of better word) is never going to
> happen.  I think its going to be through this HECI driver, but it looks like
> whatever support was being put into that has flat lined.

Yes, I think you are right here, we need Intel's AMT/HECI stuff in the
kernel first and then we can start working on support for the hardware
monitoring features on top of that framework. That's a long way to go
though so you'll have to be patient. Oh well, maybe by then I will have
access to one of these motherboards so I can start helping Intel with
the code.

-- 
Jean Delvare

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

Re: [lm-sensors] Intel DG45FC

[Jean Delvare]

Hi Anthony,

On Tue, 11 Nov 2008 10:45:10 +0100, Jean Delvare wrote:
> On Fri, 7 Nov 2008 17:38:00 -0800, Anthony Arobone wrote:
> > # isadump 0x2e 0x2f 8
> > WARNING! Running this program can cause system crashes, data loss and worse!
> > I will probe address register 0x2e and data register 0x2f.
> > Probing bank 8 using bank register 0x07.
> > Continue? [Y/n] y
> >      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> > 00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00
> > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41
> > 20: f1 01 00 00 01 01 00 91 00 11 2e 00 00 10 00 00
> > 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 70: 00 03 00 00 04 04 00 00 00 00 00 00 00 00 00 00
> > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > f0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 
> OK, so as expected, the logical device with the hardware monitoring
> features is disabled. If you look at ticket #2182 starting at:
> http://www.lm-sensors.org/ticket/2182#comment:13
> 
> You'll see what we tried with the other user to enable the logical
> device and see if it "woke up" the "emulated" LM96000. It did not work
> for him, but feel free to try too and see if it helps on your board:
> 
> isaset -y 0x2e 0x2f 0x07 8
> isaset -y 0x2e 0x2f 0x60 0x02
> isaset -y 0x2e 0x2f 0x61 0x90
> isaset -y 0x2e 0x2f 0x30 1
> 
> (After checking in /proc/ioports that there's nothing at 0x290 on your
> system.) Then:
> 
> rmmod lm85
> modprobe lm85

Did you ever try this?

> That being said, I'm not holding my breath. Maybe your system has the
> same chip variant (WPCD377i) without the hardware monitoring feature
> and that's the reason why all the readings are 0 and the actual
> monitoring is done by the Intel ICH chip.

Can you please look at your board (physically) and search for the
Super-I/O chip? This should be one of:

PC8374L
WPCD374L
WPCD376I
WPCD377I

I would like to know which one you have.

Thanks,
-- 
Jean Delvare

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

Re: [lm-sensors] Intel DG45FC

[Tony Bones]

[-- Attachment #1.1: Type: text/plain, Size: 2937 bytes --]

On Fri, Feb 20, 2009 at 2:11 AM, Jean Delvare <khali@linux-fr.org> wrote:

> Hi Anthony,
>
> On Tue, 11 Nov 2008 10:45:10 +0100, Jean Delvare wrote:
> > On Fri, 7 Nov 2008 17:38:00 -0800, Anthony Arobone wrote:
> > > # isadump 0x2e 0x2f 8
> > > WARNING! Running this program can cause system crashes, data loss and
> worse!
> > > I will probe address register 0x2e and data register 0x2f.
> > > Probing bank 8 using bank register 0x07.
> > > Continue? [Y/n] y
> > >      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> > > 00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00
> > > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41
> > > 20: f1 01 00 00 01 01 00 91 00 11 2e 00 00 10 00 00
> > > 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 70: 00 03 00 00 04 04 00 00 00 00 00 00 00 00 00 00
> > > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > f0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> >
> > OK, so as expected, the logical device with the hardware monitoring
> > features is disabled. If you look at ticket #2182 starting at:
> > http://www.lm-sensors.org/ticket/2182#comment:13
> >
> > You'll see what we tried with the other user to enable the logical
> > device and see if it "woke up" the "emulated" LM96000. It did not work
> > for him, but feel free to try too and see if it helps on your board:
> >
> > isaset -y 0x2e 0x2f 0x07 8
> > isaset -y 0x2e 0x2f 0x60 0x02
> > isaset -y 0x2e 0x2f 0x61 0x90
> > isaset -y 0x2e 0x2f 0x30 1
> >
> > (After checking in /proc/ioports that there's nothing at 0x290 on your
> > system.) Then:
> >
> > rmmod lm85
> > modprobe lm85
>
> Did you ever try this?
>
> > That being said, I'm not holding my breath. Maybe your system has the
> > same chip variant (WPCD377i) without the hardware monitoring feature
> > and that's the reason why all the readings are 0 and the actual
> > monitoring is done by the Intel ICH chip.
>
> Can you please look at your board (physically) and search for the
> Super-I/O chip? This should be one of:
>
> PC8374L
> WPCD374L
> WPCD376I
> WPCD377I
>
> I would like to know which one you have.


Sorry for the long delay, its the WPCD376I  (which apparently is based on
the WPCD374L but without the legacy components).  So maybe they are similar
in how you interface with them.

See here:
http://www.nuvoton.com/hq/enu/ProductAndSales/ProductLines/ComputerIC/SuperIO/AdvancedSuperIOforDesktop/WPCD376I.htm

[-- Attachment #1.2: Type: text/html, Size: 3927 bytes --]

[-- 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 DG45FC

[Jean Delvare]

Hi Tony,

On Fri, 27 Mar 2009 11:14:16 -0700, Tony Bones wrote:
> On Fri, Feb 20, 2009 at 2:11 AM, Jean Delvare <khali@linux-fr.org> wrote:
> > Can you please look at your board (physically) and search for the
> > Super-I/O chip? This should be one of:
> >
> > PC8374L
> > WPCD374L
> > WPCD376I
> > WPCD377I
> >
> > I would like to know which one you have.
> 
> Sorry for the long delay, its the WPCD376I  (which apparently is based on
> the WPCD374L but without the legacy components).  So maybe they are similar
> in how you interface with them.
> 
> See here:
> http://www.nuvoton.com/hq/enu/ProductAndSales/ProductLines/ComputerIC/SuperIO/AdvancedSuperIOforDesktop/WPCD376I.htm

OK, thanks for the information. This confirms my guess that devices
without the hardware monitoring block have revision ID 0x91. Please
give a try to the latest version of sensors-detect:
http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect

It should detect a WPCD376I/377I and tell you it doesn't have hardware
monitoring features.

-- 
Jean Delvare

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

Re: [lm-sensors] Intel DG45FC

[Jiri Horky]

Hi all,

I too have Intel DG45FC board and I am very interested in getting
sensors working (and even more in PWM control of board, I am able to
monitor temperatures with external thermometer). From what I understand,
it would require "QST SDK" from Intel to be realeased, am I right (does
that apply to PWM control too?) ? See [1].

And to answer Jean Delvare question. I have tried mentioned
sensors-detect and the output was:

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

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

Driver `lm85':
  * Bus `SMBus I801 adapter at f000'
    Busdriver `i2c_i801', I2C address 0x2e
    Chip `lm85' (confidence: 6)


Jiri Horky

[1]
http://software.intel.com/en-us/forums/manageability-software-development/topic/54851/



> OK, thanks for the information. This confirms my guess that devices
> without the hardware monitoring block have revision ID 0x91. Please
> give a try to the latest version of sensors-detect:
> http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect
>
> It should detect a WPCD376I/377I and tell you it doesn't have hardware
> monitoring features.
>
> -- 
> Jean Delvare


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