Re: [lm-sensors] dme1737 module

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Juergen,

I'm copying the list so others can profit.


> Dear Juerg,
>
> I own a barebone made by asus which needs the dme1737 module for lm-sensors to
> work correctly. Since it had been included in kernel 2.6.23 and I am running 2.6.18 (from
> debian etch) I was wondering if there is a stand alone version of the module, that I could
> compile for my kernel? Is there any way to use it with 2.6.18?

Copy the file dme1737.c from the 2.6.23 kernel to a temp directory and
create a Makefile in the same directory that contains the following
lines:

obj-m := dme1737.o
all:
        make -C /lib/modules/`uname -r`/build M=$(PWD) modules

Then run 'make' which will compile the module. You also need to have
the kernel headers installed to be able to compile.
Additionally, you will also need the latest 'lm-sensors' package
(2.10.4 ) or the dme1737 will not be recognized.

Let me know if you need additional help.
...juerg


> Jürgen
> _______________________________________________________________________
> Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate
> kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc\x022220
>
>

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

Re: [lm-sensors] dme1737 module

[Juergen.Bausa]

Juerg Haefliger <juergh <at> gmail.com> writes:

> 
> > I own a barebone made by asus which needs the dme1737 module for 
> > lm-sensors to work correctly. Since it had been included in kernel 
> > 2.6.23 and I am running 2.6.18 (from
> > debian etch) I was wondering if there is a stand alone version 
> > of the module, that I could
> > compile for my kernel? Is there any way to use it with 2.6.18?
> 
> Copy the file dme1737.c from the 2.6.23 kernel to a temp directory and
> create a Makefile in the same directory that contains the following
> lines:
> 
> obj-m := dme1737.o
> all:
>         make -C /lib/modules/`uname -r`/build M=$(PWD) modules
> 
> Then run 'make' which will compile the module. You also need to have
> the kernel headers installed to be able to compile.
> Additionally, you will also need the latest 'lm-sensors' package
> (2.10.4 ) or the dme1737 will not be recognized.
> 

Thanks a lot, the module seems to work fine. I used the newest sensors-detect
and it found out the modules I have to use. However, the output of sensors
is quite short:

jba@lisa:~$ sensors
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:
              -1째C
Core0 Temp:
              +1째C
Core1 Temp:
              +6째C
Core1 Temp:
              +6째C

dme1737-i2c-0-2e
Adapter: SMBus nForce2 adapter at 4c00

k8temp values are wrong, but that is another problem. But why doent
dme1737 display anything? Is it because of the older lm-sensors version in
debian (2.10.1-3). Or will it be sufficiant to update the config file?
If possible I would like to keep the etch version of lm-sensors.

Juergen


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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Juergen,


> Juerg Haefliger <juergh <at> gmail.com> writes:
>
> >
> > > I own a barebone made by asus which needs the dme1737 module for
> > > lm-sensors to work correctly. Since it had been included in kernel
> > > 2.6.23 and I am running 2.6.18 (from
> > > debian etch) I was wondering if there is a stand alone version
> > > of the module, that I could
> > > compile for my kernel? Is there any way to use it with 2.6.18?
> >
> > Copy the file dme1737.c from the 2.6.23 kernel to a temp directory and
> > create a Makefile in the same directory that contains the following
> > lines:
> >
> > obj-m := dme1737.o
> > all:
> >         make -C /lib/modules/`uname -r`/build M=$(PWD) modules
> >
> > Then run 'make' which will compile the module. You also need to have
> > the kernel headers installed to be able to compile.
> > Additionally, you will also need the latest 'lm-sensors' package
> > (2.10.4 ) or the dme1737 will not be recognized.
> >
>
> Thanks a lot, the module seems to work fine. I used the newest sensors-detect
> and it found out the modules I have to use. However, the output of sensors
> is quite short:
>
> jba@lisa:~$ sensors
> k8temp-pci-00c3
> Adapter: PCI adapter
> Core0 Temp:
>               -1°C
> Core0 Temp:
>               +1°C
> Core1 Temp:
>               +6°C
> Core1 Temp:
>               +6°C
>
> dme1737-i2c-0-2e
> Adapter: SMBus nForce2 adapter at 4c00
>
> k8temp values are wrong, but that is another problem. But why doent
> dme1737 display anything? Is it because of the older lm-sensors version in
> debian (2.10.1-3). Or will it be sufficiant to update the config file?
> If possible I would like to keep the etch version of lm-sensors.

You need a newer lm-sensors. 2.10.1 doesn't know about the dme1737.
Just updating the config file is not enough.

...juerg


> Juergen
>
>
> _______________________________________________
> 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] dme1737 module

[Kushal Koolwal]

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


Hello,

Actually I have tried the newest version of lm-sensors on Debian sid and dme1737 does not show any output for my SCH3114 Super I/O chip.

I have also opened a ticket for the same last week.

Here is the URL of the ticket:
http://www.lm-sensors.org/ticket/2243

Thanks

Kushal Koolwal

> Date: Mon, 27 Aug 2007 14:26:16 -0700
> From: juergh@gmail.com
> To: Juergen.Bausa@web.de
> CC: lm-sensors@lm-sensors.org
> Subject: Re: [lm-sensors] dme1737 module
> 
> Hi Juergen,
> 
> 
> > Juerg Haefliger <juergh <at> gmail.com> writes:
> >
> > >
> > > > I own a barebone made by asus which needs the dme1737 module for
> > > > lm-sensors to work correctly. Since it had been included in kernel
> > > > 2.6.23 and I am running 2.6.18 (from
> > > > debian etch) I was wondering if there is a stand alone version
> > > > of the module, that I could
> > > > compile for my kernel? Is there any way to use it with 2.6.18?
> > >
> > > Copy the file dme1737.c from the 2.6.23 kernel to a temp directory and
> > > create a Makefile in the same directory that contains the following
> > > lines:
> > >
> > > obj-m := dme1737.o
> > > all:
> > >         make -C /lib/modules/`uname -r`/build M=$(PWD) modules
> > >
> > > Then run 'make' which will compile the module. You also need to have
> > > the kernel headers installed to be able to compile.
> > > Additionally, you will also need the latest 'lm-sensors' package
> > > (2.10.4 ) or the dme1737 will not be recognized.
> > >
> >
> > Thanks a lot, the module seems to work fine. I used the newest sensors-detect
> > and it found out the modules I have to use. However, the output of sensors
> > is quite short:
> >
> > jba@lisa:~$ sensors
> > k8temp-pci-00c3
> > Adapter: PCI adapter
> > Core0 Temp:
> >               -1°C
> > Core0 Temp:
> >               +1°C
> > Core1 Temp:
> >               +6°C
> > Core1 Temp:
> >               +6°C
> >
> > dme1737-i2c-0-2e
> > Adapter: SMBus nForce2 adapter at 4c00
> >
> > k8temp values are wrong, but that is another problem. But why doent
> > dme1737 display anything? Is it because of the older lm-sensors version in
> > debian (2.10.1-3). Or will it be sufficiant to update the config file?
> > If possible I would like to keep the etch version of lm-sensors.
> 
> You need a newer lm-sensors. 2.10.1 doesn't know about the dme1737.
> Just updating the config file is not enough.
> 
> ...juerg
> 
> 
> > Juergen
> >
> >
> > _______________________________________________
> > 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

_________________________________________________________________
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx

[-- Attachment #1.2: Type: text/html, Size: 3837 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] dme1737 module

[Juergen Bausa]

So, which version is needed to run the dme1737 on the asus board (Which I think doesnt have the 
SCH3114 Super I/O chip)?

debian testing and unstable both have 2.10.4 at the moment, which is the same version as 
http://www.lm-sensors.org/wiki/Download. Will it be enough to install this version?

By the way: Does anyone know of backports to etch?

Juergen


> -----Ursprüngliche Nachricht-----
> Von: Kushal Koolwal <kushalkoolwal@hotmail.com>
> Gesendet: 28.08.07 00:56:24
> An:  "Juergen. Bausa" <juergen.bausa@web.de>
> CC: <lm-sensors@lm-sensors.org>
> Betreff: RE: [lm-sensors] dme1737 module

Hello,
> 
> Actually I have tried the newest version of lm-sensors on Debian sid and dme1737 does not show any output for my SCH3114 Super I/O chip.
> 
> I have also opened a ticket for the same last week.
> 
> Here is the URL of the ticket:
> http://www.lm-sensors.org/ticket/2243
> 
> Thanks
> 
> Kushal Koolwal
> 
> > Date: Mon, 27 Aug 2007 14:26:16 -0700
> > From: juergh@gmail.com
> > To: Juergen.Bausa@web.de
> > CC: lm-sensors@lm-sensors.org
> > Subject: Re: [lm-sensors] dme1737 module
> > 
> > Hi Juergen,
> > 
> > 
> > > Juerg Haefliger <juergh <at> gmail.com> writes:
> > >
> > > >
> > > > > I own a barebone made by asus which needs the dme1737 module for
> > > > > lm-sensors to work correctly. Since it had been included in kernel
> > > > > 2.6.23 and I am running 2.6.18 (from
> > > > > debian etch) I was wondering if there is a stand alone version
> > > > > of the module, that I could
> > > > > compile for my kernel? Is there any way to use it with 2.6.18?
> > > >
> > > > Copy the file dme1737.c from the 2.6.23 kernel to a temp directory and
> > > > create a Makefile in the same directory that contains the following
> > > > lines:
> > > >
> > > > obj-m := dme1737.o
> > > > all:
> > > > make -C /lib/modules/`uname -r`/build M=$(PWD) modules
> > > >
> > > > Then run 'make' which will compile the module. You also need to have
> > > > the kernel headers installed to be able to compile.
> > > > Additionally, you will also need the latest 'lm-sensors' package
> > > > (2.10.4 ) or the dme1737 will not be recognized.
> > > >
> > >
> > > Thanks a lot, the module seems to work fine. I used the newest sensors-detect
> > > and it found out the modules I have to use. However, the output of sensors
> > > is quite short:
> > >
> > > jba@lisa:~$ sensors
> > > k8temp-pci-00c3
> > > Adapter: PCI adapter
> > > Core0 Temp:
> > > -1°C
> > > Core0 Temp:
> > > +1°C
> > > Core1 Temp:
> > > +6°C
> > > Core1 Temp:
> > > +6°C
> > >
> > > dme1737-i2c-0-2e
> > > Adapter: SMBus nForce2 adapter at 4c00
> > >
> > > k8temp values are wrong, but that is another problem. But why doent
> > > dme1737 display anything? Is it because of the older lm-sensors version in
> > > debian (2.10.1-3). Or will it be sufficiant to update the config file?
> > > If possible I would like to keep the etch version of lm-sensors.
> > 
> > You need a newer lm-sensors. 2.10.1 doesn't know about the dme1737.
> > Just updating the config file is not enough.
> > 
> > ...juerg
> > 
> > 
> > > Juergen
> > >
> > >
> > > _______________________________________________
> > > 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
> 
> 
> -----------------------------------------------------------------
> Get news, entertainment and everything you care about at Live.com. Check it out!


_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc\x100071&distributionid\00000000066


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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Juergen,


> So, which version is needed to run the dme1737 on the asus board (Which I think doesnt have the
> SCH3114 Super I/O chip)?
>
> debian testing and unstable both have 2.10.4 at the moment, which is the same version as
> http://www.lm-sensors.org/wiki/Download. Will it be enough to install this version?

2.10.4 and kernel 2.6.23 is sufficient if you don't have the sch311x.


> By the way: Does anyone know of backports to etch?

No.

...juerg


> Juergen
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Kushal Koolwal <kushalkoolwal@hotmail.com>
> > Gesendet: 28.08.07 00:56:24
> > An:  "Juergen. Bausa" <juergen.bausa@web.de>
> > CC: <lm-sensors@lm-sensors.org>
> > Betreff: RE: [lm-sensors] dme1737 module
>
> Hello,
> >
> > Actually I have tried the newest version of lm-sensors on Debian sid and dme1737 does not show any output for my SCH3114 Super I/O chip.
> >
> > I have also opened a ticket for the same last week.
> >
> > Here is the URL of the ticket:
> > http://www.lm-sensors.org/ticket/2243
> >
> > Thanks
> >
> > Kushal Koolwal
> >
> > > Date: Mon, 27 Aug 2007 14:26:16 -0700
> > > From: juergh@gmail.com
> > > To: Juergen.Bausa@web.de
> > > CC: lm-sensors@lm-sensors.org
> > > Subject: Re: [lm-sensors] dme1737 module
> > >
> > > Hi Juergen,
> > >
> > >
> > > > Juerg Haefliger <juergh <at> gmail.com> writes:
> > > >
> > > > >
> > > > > > I own a barebone made by asus which needs the dme1737 module for
> > > > > > lm-sensors to work correctly. Since it had been included in kernel
> > > > > > 2.6.23 and I am running 2.6.18 (from
> > > > > > debian etch) I was wondering if there is a stand alone version
> > > > > > of the module, that I could
> > > > > > compile for my kernel? Is there any way to use it with 2.6.18?
> > > > >
> > > > > Copy the file dme1737.c from the 2.6.23 kernel to a temp directory and
> > > > > create a Makefile in the same directory that contains the following
> > > > > lines:
> > > > >
> > > > > obj-m := dme1737.o
> > > > > all:
> > > > > make -C /lib/modules/`uname -r`/build M=$(PWD) modules
> > > > >
> > > > > Then run 'make' which will compile the module. You also need to have
> > > > > the kernel headers installed to be able to compile.
> > > > > Additionally, you will also need the latest 'lm-sensors' package
> > > > > (2.10.4 ) or the dme1737 will not be recognized.
> > > > >
> > > >
> > > > Thanks a lot, the module seems to work fine. I used the newest sensors-detect
> > > > and it found out the modules I have to use. However, the output of sensors
> > > > is quite short:
> > > >
> > > > jba@lisa:~$ sensors
> > > > k8temp-pci-00c3
> > > > Adapter: PCI adapter
> > > > Core0 Temp:
> > > > -1°C
> > > > Core0 Temp:
> > > > +1°C
> > > > Core1 Temp:
> > > > +6°C
> > > > Core1 Temp:
> > > > +6°C
> > > >
> > > > dme1737-i2c-0-2e
> > > > Adapter: SMBus nForce2 adapter at 4c00
> > > >
> > > > k8temp values are wrong, but that is another problem. But why doent
> > > > dme1737 display anything? Is it because of the older lm-sensors version in
> > > > debian (2.10.1-3). Or will it be sufficiant to update the config file?
> > > > If possible I would like to keep the etch version of lm-sensors.
> > >
> > > You need a newer lm-sensors. 2.10.1 doesn't know about the dme1737.
> > > Just updating the config file is not enough.
> > >
> > > ...juerg
> > >
> > >
> > > > Juergen
> > > >
> > > >
> > > > _______________________________________________
> > > > 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
> >
> >
> > -----------------------------------------------------------------
> > Get news, entertainment and everything you care about at Live.com. Check it out!
>
>
> _____________________________________________________________________
> Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
> http://smartsurfer.web.de/?mc\x100071&distributionid\00000000066
>
>

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

Re: [lm-sensors] dme1737 module

[Juergen Bausa]

> -----Ursprüngliche Nachricht-----
> Von: "Juerg Haefliger" <juergh@gmail.com>
> Gesendet: 28.08.07 17:07:38
> An: "Juergen Bausa" <Juergen.Bausa@web.de>
> CC: "Kushal Koolwal" <kushalkoolwal@hotmail.com>, lm-sensors@lm-sensors.org
> Betreff: Re: [lm-sensors] dme1737 module


> 
> 
> > So, which version is needed to run the dme1737 on the asus board (Which I think doesnt have the
> > SCH3114 Super I/O chip)?
> >
> > debian testing and unstable both have 2.10.4 at the moment, which is the same version as
> > http://www.lm-sensors.org/wiki/Download. Will it be enough to install this version?
> 
> 2.10.4 and kernel 2.6.23 is sufficient if you don't have the sch311x.
> 

Now it works with lm-sensors 2.10.4 which can easily backported drom debian testing.

However, I get strange temperatures for the cpu. With the fan at 3000 rpm and idle cpu I get a temperature
of 17 °C, while room temperature is 20°C. I think this is not possible. 

I now use fancontrol which turns fan speed to 0 rpm. Here is the output of sensors:

dme1737-i2c-0-2e
Adapter: SMBus nForce2 adapter at 4c00
V5stby:    +0.00 V  (min =  +0.00 V, max =  +6.64 V)  ALARM
Vccp:      +1.10 V  (min =  +0.00 V, max =  +2.99 V)
V3.3:      +3.28 V  (min =  +0.00 V, max =  +4.38 V)
V5:        +4.94 V  (min =  +0.00 V, max =  +6.64 V)
V12:      +11.80 V  (min =  +0.00 V, max = +15.94 V)
V3.3stby:  +3.29 V  (min =  +0.00 V, max =  +4.38 V)
Vbat:      +2.98 V  (min =  +0.00 V, max =  +4.38 V)
Int Temp:    +34°C  (low  =  -127°C, high =  +127°C)
CPU Temp:    +29°C  (low  =  -127°C, high =  +127°C)
CPU_Fan:     0 RPM  (min =    0 RPM)
ERROR: Can't get fan3 data!
ERROR: Can't get fan5 data!
ERROR: Can't get fan6 data!
CPU_PWM:     0      (enable = 1, freq =  25000 Hz)
ERROR: Can't get pwm5 data!
ERROR: Can't get pwm6 data!
cpu0_vid: +1.550 V  (VRM Version 2.4)

I think 29 °C is also very low for idle and no fan, even for my AMD BE-2350 
(45 w maximum power consumption). Also, Int-Temperature (is this board temperature?)
is higher than cpu- temperature. This changes only for high load, where
cpu-temperature increases more than int-temperature.

At first I thought that temperature calculation is wrong in lm-sensors. However,
BIOS shows nearly the same temperatures.

So, is there anything wrong here?

Juergen
_________________________________________________________________________
In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! 
Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc\x021114


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

Re: [lm-sensors] dme1737 module

[Jean Delvare]

On Sun, 02 Sep 2007 14:57:32 +0200, Juergen Bausa wrote:
> dme1737-i2c-0-2e
> Adapter: SMBus nForce2 adapter at 4c00
> V5stby:    +0.00 V  (min =  +0.00 V, max =  +6.64 V)  ALARM
> Vccp:      +1.10 V  (min =  +0.00 V, max =  +2.99 V)
> V3.3:      +3.28 V  (min =  +0.00 V, max =  +4.38 V)
> V5:        +4.94 V  (min =  +0.00 V, max =  +6.64 V)
> V12:      +11.80 V  (min =  +0.00 V, max = +15.94 V)
> V3.3stby:  +3.29 V  (min =  +0.00 V, max =  +4.38 V)
> Vbat:      +2.98 V  (min =  +0.00 V, max =  +4.38 V)
> Int Temp:    +34°C  (low  =  -127°C, high =  +127°C)
> CPU Temp:    +29°C  (low  =  -127°C, high =  +127°C)
> CPU_Fan:     0 RPM  (min =    0 RPM)
> ERROR: Can't get fan3 data!
> ERROR: Can't get fan5 data!
> ERROR: Can't get fan6 data!
> CPU_PWM:     0      (enable = 1, freq =  25000 Hz)
> ERROR: Can't get pwm5 data!
> ERROR: Can't get pwm6 data!
> cpu0_vid: +1.550 V  (VRM Version 2.4)

Juerg, sensors shouldn't be displaying these errors for optional fans
and pwms. Can you please provide a patch fixing this? It should be
pretty easy.

Thanks,
-- 
Jean Delvare

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

Re: [lm-sensors] dme1737 module

[Juergen Bausa]

Ok, board-temperature might be higher then cpu-temperature.

But the question remains, who cpu-temperature can be below room temperature. In addition, 
your cpu-temperatures are significant higher than mine. Even at full load I dont get 60 °C.

Juergen


> -----Ursprüngliche Nachricht-----
> Von: Krzysztof Helt <krzysztof.h1@wp.pl>
> Gesendet: 02.09.07 15:26:42
> An: Juergen Bausa <Juergen.Bausa@web.de>
> Betreff: Re: [lm-sensors] dme1737 module


> 
> On Sun, 02 Sep 2007 14:57:32 +0200
> Juergen Bausa <Juergen.Bausa@web.de> wrote:
> 
> > I think 29 °C is also very low for idle and no fan, even for my AMD BE-2350 
> > (45 w maximum power consumption). Also, Int-Temperature (is this board temperature?)
> > is higher than cpu- temperature. This changes only for high load, where
> > cpu-temperature increases more than int-temperature.
> > 
> > At first I thought that temperature calculation is wrong in lm-sensors. However,
> > BIOS shows nearly the same temperatures.
> 
> It is ok. I have something similar with the Compaq AP550 (Pentium3 CPUs - not mobile version), which has no fans on CPU and only case fan. 
> Even with minimal speed of fan I got around 30 to 35 degrees for CPUs while
> motherboard temperature is 36 and even 41 degrees (but I don't know where - could be close to memory or chipset).
> 
> Room temperature is 24 degrees now. The read values (no load):
> 
> adm1022-i2c-0-2d
> Adapter: SMBus I801 adapter at fc00
> M/B Temp: +36.0°C (low = -128.0°C, high = +127.0°C) 
> AUX Temp: +41.0°C (low = -128.0°C, high = +127.0°C) 
> 
> adm1022-i2c-0-2e
> Adapter: SMBus I801 adapter at fc00
> M/B Temp (near CPUs): +37.0°C (low = -128.0°C, high = +127.0°C) 
> CPU1 Temp: +34.0°C (low = +0.0°C, high = +127.0°C) 
> CPU2 Temp: +36.0°C (low = +0.0°C, high = +127.0°C) 
> 
> The CPUs temperature goes up to 60 degrees under load then return to the 30 degree range when CPUs are idle.
> 
> Regards,
> Krzysztof
> 

 
 
 

> -----Ursprüngliche Nachricht-----
> Von: Jean Delvare <khali@linux-fr.org>
> Gesendet: 02.09.07 19:46:00
> An: Juerg Haefliger <juergh@gmail.com>
> CC: lm-sensors@lm-sensors.org
> Betreff: Re: [lm-sensors] dme1737 module


> 
> On Sun, 02 Sep 2007 14:57:32 +0200, Juergen Bausa wrote:
> > dme1737-i2c-0-2e
> > Adapter: SMBus nForce2 adapter at 4c00
> > V5stby:    +0.00 V  (min =  +0.00 V, max =  +6.64 V)  ALARM
> > Vccp:      +1.10 V  (min =  +0.00 V, max =  +2.99 V)
> > V3.3:      +3.28 V  (min =  +0.00 V, max =  +4.38 V)
> > V5:        +4.94 V  (min =  +0.00 V, max =  +6.64 V)
> > V12:      +11.80 V  (min =  +0.00 V, max = +15.94 V)
> > V3.3stby:  +3.29 V  (min =  +0.00 V, max =  +4.38 V)
> > Vbat:      +2.98 V  (min =  +0.00 V, max =  +4.38 V)
> > Int Temp:    +34°C  (low  =  -127°C, high =  +127°C)
> > CPU Temp:    +29°C  (low  =  -127°C, high =  +127°C)
> > CPU_Fan:     0 RPM  (min =    0 RPM)
> > ERROR: Can't get fan3 data!
> > ERROR: Can't get fan5 data!
> > ERROR: Can't get fan6 data!
> > CPU_PWM:     0      (enable = 1, freq =  25000 Hz)
> > ERROR: Can't get pwm5 data!
> > ERROR: Can't get pwm6 data!
> > cpu0_vid: +1.550 V  (VRM Version 2.4)
> 
> Juerg, sensors shouldn't be displaying these errors for optional fans
> and pwms. Can you please provide a patch fixing this? It should be
> pretty easy.
> 
> Thanks,
> -- 
> Jean Delvare
> 


__________________________________________________________________________
Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach!		
Mehr Infos unter http://produkte.web.de/club/?mc\x021131


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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

> On Sun, 02 Sep 2007 14:57:32 +0200, Juergen Bausa wrote:
> > dme1737-i2c-0-2e
> > Adapter: SMBus nForce2 adapter at 4c00
> > V5stby:    +0.00 V  (min =  +0.00 V, max =  +6.64 V)  ALARM
> > Vccp:      +1.10 V  (min =  +0.00 V, max =  +2.99 V)
> > V3.3:      +3.28 V  (min =  +0.00 V, max =  +4.38 V)
> > V5:        +4.94 V  (min =  +0.00 V, max =  +6.64 V)
> > V12:      +11.80 V  (min =  +0.00 V, max = +15.94 V)
> > V3.3stby:  +3.29 V  (min =  +0.00 V, max =  +4.38 V)
> > Vbat:      +2.98 V  (min =  +0.00 V, max =  +4.38 V)
> > Int Temp:    +34°C  (low  =  -127°C, high =  +127°C)
> > CPU Temp:    +29°C  (low  =  -127°C, high =  +127°C)
> > CPU_Fan:     0 RPM  (min =    0 RPM)
> > ERROR: Can't get fan3 data!
> > ERROR: Can't get fan5 data!
> > ERROR: Can't get fan6 data!
> > CPU_PWM:     0      (enable = 1, freq =  25000 Hz)
> > ERROR: Can't get pwm5 data!
> > ERROR: Can't get pwm6 data!
> > cpu0_vid: +1.550 V  (VRM Version 2.4)
>
> Juerg, sensors shouldn't be displaying these errors for optional fans
> and pwms. Can you please provide a patch fixing this? It should be
> pretty easy.

Hmm... An ignore statement would take care of this. Do you have
something else in mind?

...juerg

> Thanks,
> --
> Jean Delvare
>

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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Juergen,


> > -----Ursprüngliche Nachricht-----
> > Von: "Juerg Haefliger" <juergh@gmail.com>
> > Gesendet: 28.08.07 17:07:38
> > An: "Juergen Bausa" <Juergen.Bausa@web.de>
> > CC: "Kushal Koolwal" <kushalkoolwal@hotmail.com>, lm-sensors@lm-sensors.org
> > Betreff: Re: [lm-sensors] dme1737 module
>
>
> >
> >
> > > So, which version is needed to run the dme1737 on the asus board (Which I think doesnt have the
> > > SCH3114 Super I/O chip)?
> > >
> > > debian testing and unstable both have 2.10.4 at the moment, which is the same version as
> > > http://www.lm-sensors.org/wiki/Download. Will it be enough to install this version?
> >
> > 2.10.4 and kernel 2.6.23 is sufficient if you don't have the sch311x.
> >
>
> Now it works with lm-sensors 2.10.4 which can easily backported drom debian testing.
>
> However, I get strange temperatures for the cpu. With the fan at 3000 rpm and idle cpu I get a temperature
> of 17 °C, while room temperature is 20°C. I think this is not possible.

That is strange indeed. Can you reproduce this and then unload the
dme1737 module and run 'i2cdump 0 0x2e' and post the output?


> I now use fancontrol which turns fan speed to 0 rpm. Here is the output of sensors:
>
> dme1737-i2c-0-2e
> Adapter: SMBus nForce2 adapter at 4c00
> V5stby:    +0.00 V  (min =  +0.00 V, max =  +6.64 V)  ALARM
> Vccp:      +1.10 V  (min =  +0.00 V, max =  +2.99 V)
> V3.3:      +3.28 V  (min =  +0.00 V, max =  +4.38 V)
> V5:        +4.94 V  (min =  +0.00 V, max =  +6.64 V)
> V12:      +11.80 V  (min =  +0.00 V, max = +15.94 V)
> V3.3stby:  +3.29 V  (min =  +0.00 V, max =  +4.38 V)
> Vbat:      +2.98 V  (min =  +0.00 V, max =  +4.38 V)
> Int Temp:    +34°C  (low  =  -127°C, high =  +127°C)
> CPU Temp:    +29°C  (low  =  -127°C, high =  +127°C)
> CPU_Fan:     0 RPM  (min =    0 RPM)
> ERROR: Can't get fan3 data!
> ERROR: Can't get fan5 data!
> ERROR: Can't get fan6 data!
> CPU_PWM:     0      (enable = 1, freq =  25000 Hz)
> ERROR: Can't get pwm5 data!
> ERROR: Can't get pwm6 data!
> cpu0_vid: +1.550 V  (VRM Version 2.4)
>
> I think 29 °C is also very low for idle and no fan, even for my AMD BE-2350
> (45 w maximum power consumption). Also, Int-Temperature (is this board temperature?)
> is higher than cpu- temperature. This changes only for high load, where
> cpu-temperature increases more than int-temperature.

That's possible. The Int-temp is the dme1737 internal temperature, not
the 'board' temperature. Depending on how hot the chip itself is this
temperature can be rather high.


> At first I thought that temperature calculation is wrong in lm-sensors. However,
> BIOS shows nearly the same temperatures.

There's not much that can be done wrong here. All the driver does is
convert from unsigned to signed. Sensors itself doesn't do any
conversion.

...juerg


> So, is there anything wrong here?
>
> Juergen
> _________________________________________________________________________
> In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten!
> Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc\x021114
>
>

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

Re: [lm-sensors] dme1737 module

[Juergen Bausa]

> -----Ursprüngliche Nachricht-----
> Von: "Juerg Haefliger" <juergh@gmail.com>
> 
> > On Sun, 02 Sep 2007 14:57:32 +0200, Juergen Bausa wrote:
> > > dme1737-i2c-0-2e
> > > Adapter: SMBus nForce2 adapter at 4c00
> > > V5stby:    +0.00 V  (min =  +0.00 V, max =  +6.64 V)  ALARM
> > > Vccp:      +1.10 V  (min =  +0.00 V, max =  +2.99 V)
> > > V3.3:      +3.28 V  (min =  +0.00 V, max =  +4.38 V)
> > > V5:        +4.94 V  (min =  +0.00 V, max =  +6.64 V)
> > > V12:      +11.80 V  (min =  +0.00 V, max = +15.94 V)
> > > V3.3stby:  +3.29 V  (min =  +0.00 V, max =  +4.38 V)
> > > Vbat:      +2.98 V  (min =  +0.00 V, max =  +4.38 V)
> > > Int Temp:    +34°C  (low  =  -127°C, high =  +127°C)
> > > CPU Temp:    +29°C  (low  =  -127°C, high =  +127°C)
> > > CPU_Fan:     0 RPM  (min =    0 RPM)
> > > ERROR: Can't get fan3 data!
> > > ERROR: Can't get fan5 data!
> > > ERROR: Can't get fan6 data!
> > > CPU_PWM:     0      (enable = 1, freq =  25000 Hz)
> > > ERROR: Can't get pwm5 data!
> > > ERROR: Can't get pwm6 data!
> > > cpu0_vid: +1.550 V  (VRM Version 2.4)
> >
> > Juerg, sensors shouldn't be displaying these errors for optional fans
> > and pwms. Can you please provide a patch fixing this? It should be
> > pretty easy.
> 
> Hmm... An ignore statement would take care of this. Do you have
> something else in mind?
> 

I get these warnings allthough I have ignore statements in my sensors.conf:

chip "dme1737-*"

....

ignore fan2
ignore fan3
ignore fan4
ignore fan5
ignore fan6

ignore pwm2
ignore pwm3
ignore pwm4
ignore pwm5
ignore pwm6

ignore temp1

Jürgen
_______________________________________________________________________
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc\x022220


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

Re: [lm-sensors] dme1737 module

[Juergen Bausa]

> Von: "Juerg Haefliger" <juergh@gmail.com>
> 
> Hi Juergen,
> 
> 
> > > Von: "Juerg Haefliger" <juergh@gmail.com>
> > >
> > > > So, which version is needed to run the dme1737 on the asus board (Which I think doesnt have the
> > > > SCH3114 Super I/O chip)?
> > > >

> >
> > However, I get strange temperatures for the cpu. With the fan at 3000 rpm and idle cpu I get a temperature
> > of 17 °C, while room temperature is 20°C. I think this is not possible.
> 
> That is strange indeed. Can you reproduce this and then unload the
> dme1737 module and run 'i2cdump 0 0x2e' and post the output?
> 

Here it is. First sensors output (I installed a patch to make k8temp work on my brandnew AMD BE-2350 and 
results seem to be reasonable. However there is a discussion about this patch and I am not sure it is ok):
dme1737-i2c-0-2e
Adapter: SMBus nForce2 adapter at 4c00
V5stby:    +0.00 V  (min =  +0.00 V, max =  +6.64 V)  ALARM
Vccp:      +1.09 V  (min =  +0.00 V, max =  +2.99 V)
V3.3:      +3.27 V  (min =  +0.00 V, max =  +4.38 V)
V5:        +4.94 V  (min =  +0.00 V, max =  +6.64 V)
V12:      +11.77 V  (min =  +0.00 V, max = +15.94 V)
V3.3stby:  +3.29 V  (min =  +0.00 V, max =  +4.38 V)
Vbat:      +2.98 V  (min =  +0.00 V, max =  +4.38 V)
Int Temp:    +31°C  (low  =  -127°C, high =  +127°C)
CPU Temp:    +16°C  (low  =  -127°C, high =  +127°C)
CPU_Fan:  3010 RPM  (min =    0 RPM)
ERROR: Can't get fan3 data!
ERROR: Can't get fan5 data!
ERROR: Can't get fan6 data!
CPU_PWM:   255      (enable = 0, freq =  25000 Hz)
ERROR: Can't get pwm5 data!
ERROR: Can't get pwm6 data!
cpu0_vid: +1.550 V  (VRM Version 2.4)

k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:
             +29°C
Core0 Temp:
             +32°C
Core1 Temp:
             +36°C
Core1 Temp:
             +34°C

And here the output from i2cdump. I had to modprobe i2c-dev to make it work. Is this normal?

lisa:/home/jba# i2cdump 0 0x2e
No size specified (using byte-data access)
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 5d be bd bc 80 1e 0f fe 06 ff ff ff ff ff ff    .]????????......
30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 5c 8a    ..............\?
40: 05 91 40 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 cb    ????........bbb?
60: cb bb e0 00 55 80 80 5a 5a 33 64 64 45 40 40 00    ???.U??ZZ3ddE@@.
70: ff ff ff 09 09 09 09 09 09 00 30 00 40 00 ec 18    ...??????.0.@.??
80: 7e a4 0e 00 42 90 3d 90 35 00 4d 4d 0b 0b 0c 00    ~??.B?=?5.MM???.
90: 04 04 04 04 0c 0c 0c 5a f1 bf ad 00 ff 00 ff 00    ???????Z???.....
a0: 00 00 0c 00 02 00 00 0b 0b fe ff fe ff ff ff ff    ..?.?..???.?....
b0: ff 00 00 00 00 00 28 28 0e 0e 2b 2b 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 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00    .?..............
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................



> 
> > I now use fancontrol which turns fan speed to 0 rpm. Here is the output of sensors:
> >
> > dme1737-i2c-0-2e
> > Adapter: SMBus nForce2 adapter at 4c00
> > V5stby:    +0.00 V  (min =  +0.00 V, max =  +6.64 V)  ALARM
> > Vccp:      +1.10 V  (min =  +0.00 V, max =  +2.99 V)
> > V3.3:      +3.28 V  (min =  +0.00 V, max =  +4.38 V)
> > V5:        +4.94 V  (min =  +0.00 V, max =  +6.64 V)
> > V12:      +11.80 V  (min =  +0.00 V, max = +15.94 V)
> > V3.3stby:  +3.29 V  (min =  +0.00 V, max =  +4.38 V)
> > Vbat:      +2.98 V  (min =  +0.00 V, max =  +4.38 V)
> > Int Temp:    +34°C  (low  =  -127°C, high =  +127°C)
> > CPU Temp:    +29°C  (low  =  -127°C, high =  +127°C)
> > CPU_Fan:     0 RPM  (min =    0 RPM)
> > ERROR: Can't get fan3 data!
> > ERROR: Can't get fan5 data!
> > ERROR: Can't get fan6 data!
> > CPU_PWM:     0      (enable = 1, freq =  25000 Hz)
> > ERROR: Can't get pwm5 data!
> > ERROR: Can't get pwm6 data!
> > cpu0_vid: +1.550 V  (VRM Version 2.4)
> >
> > I think 29 °C is also very low for idle and no fan, even for my AMD BE-2350
> > (45 w maximum power consumption). Also, Int-Temperature (is this board temperature?)
> > is higher than cpu- temperature. This changes only for high load, where
> > cpu-temperature increases more than int-temperature.
> 
> That's possible. The Int-temp is the dme1737 internal temperature, not
> the 'board' temperature. Depending on how hot the chip itself is this
> temperature can be rather high.
> 
> 
> > At first I thought that temperature calculation is wrong in lm-sensors. However,
> > BIOS shows nearly the same temperatures.
> 
> There's not much that can be done wrong here. All the driver does is
> convert from unsigned to signed. Sensors itself doesn't do any
> conversion.
> 

So maybe the reason for the low temperature is just the measurement error? Maybe the real
temperature is 23 ° and the error is 7 K?

Juergen
______________________________________________________________________________
Jetzt neu! Im riesigen WEB.DE Club SmartDrive Dateien freigeben und mit 
Freunden teilen! http://www.freemail.web.de/club/smartdrive_ttc.htm/?mc\x021134


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

Re: [lm-sensors] dme1737 module

[Jean Delvare]

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

Hi Juerg,

On Tue, 4 Sep 2007 11:54:20 -0700, Juerg Haefliger wrote:
> > On Sun, 02 Sep 2007 14:57:32 +0200, Juergen Bausa wrote:
> > > dme1737-i2c-0-2e
> > > Adapter: SMBus nForce2 adapter at 4c00
> > > V5stby:    +0.00 V  (min =  +0.00 V, max =  +6.64 V)  ALARM
> > > Vccp:      +1.10 V  (min =  +0.00 V, max =  +2.99 V)
> > > V3.3:      +3.28 V  (min =  +0.00 V, max =  +4.38 V)
> > > V5:        +4.94 V  (min =  +0.00 V, max =  +6.64 V)
> > > V12:      +11.80 V  (min =  +0.00 V, max = +15.94 V)
> > > V3.3stby:  +3.29 V  (min =  +0.00 V, max =  +4.38 V)
> > > Vbat:      +2.98 V  (min =  +0.00 V, max =  +4.38 V)
> > > Int Temp:    +34°C  (low  =  -127°C, high =  +127°C)
> > > CPU Temp:    +29°C  (low  =  -127°C, high =  +127°C)
> > > CPU_Fan:     0 RPM  (min =    0 RPM)
> > > ERROR: Can't get fan3 data!
> > > ERROR: Can't get fan5 data!
> > > ERROR: Can't get fan6 data!
> > > CPU_PWM:     0      (enable = 1, freq =  25000 Hz)
> > > ERROR: Can't get pwm5 data!
> > > ERROR: Can't get pwm6 data!
> > > cpu0_vid: +1.550 V  (VRM Version 2.4)
> >
> > Juerg, sensors shouldn't be displaying these errors for optional fans
> > and pwms. Can you please provide a patch fixing this? It should be
> > pretty easy.
> 
> Hmm... An ignore statement would take care of this. Do you have
> something else in mind?

No, users shouldn't have to add ignore statements to hide these errors,
the errors shouldn't be displayed in the first place. And as reported
by Juergen, adding ignore statements doesn't even work in the case of
the dme1737.

We must rework the checks in the dme1737 printing functions to process
the ignore statements properly, and to only display errors for missing
features, not missing channels. I'm attaching the patch I have come up
with. I can't test it as I do not have the hardware. Juergen, can you
please test and report?

Juerg, can you please review and test too?

Admittedly this libsensors interface is confusing, the good news is
that the future library handles the ignore statements all by itself so
all these problems are gone :)

-- 
Jean Delvare

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: sensors-dme1737-hide-errors.patch --]
[-- Type: text/x-patch; name=sensors-dme1737-hide-errors.patch, Size: 4279 bytes --]

Index: prog/sensors/chips.c
===================================================================
--- prog/sensors/chips.c	(révision 4783)
+++ prog/sensors/chips.c	(copie de travail)
@@ -6016,17 +6016,17 @@
 
   if (!sensors_get_label_and_valid(*name, SENSORS_DME1737_IN(i), &label,
 				   &valid) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_IN(i), &cur) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_IN_MIN(i), &min) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_IN_MAX(i), &max) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_IN_ALARM(i), &alarm)) {
-    if (valid) {
+      valid) {
+    if (!sensors_get_feature(*name, SENSORS_DME1737_IN(i), &cur) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_IN_MIN(i), &min) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_IN_MAX(i), &max) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_IN_ALARM(i), &alarm)) {
       print_label(label, 10);
       printf("%+6.2f V  (min = %+6.2f V, max = %+6.2f V)  %s\n",
 	     cur, min, max, alarm ? "ALARM" : "");
+    } else {
+      printf("ERROR: Can't get in%d data!\n", i);
     }
-  } else {
-    printf("ERROR: Can't get in%d data!\n", i);
   }
   free(label);
 }
@@ -6039,18 +6039,18 @@
 
   if (!sensors_get_label_and_valid(*name, SENSORS_DME1737_TEMP(i), &label,
 				   &valid) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_TEMP(i), &cur) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_TEMP_MIN(i), &min) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_TEMP_MAX(i), &max) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_TEMP_ALARM(i), &alarm) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_TEMP_FAULT(i), &fault)) {
-    if (valid) {
+      valid) {
+    if (!sensors_get_feature(*name, SENSORS_DME1737_TEMP(i), &cur) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_TEMP_MIN(i), &min) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_TEMP_MAX(i), &max) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_TEMP_ALARM(i), &alarm) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_TEMP_FAULT(i), &fault)) {
       print_label(label, 10);
       print_temp_info(cur, max, min, MINMAX, 0, 0);
       printf("%s%s\n", fault ? "FAULT  " : "", alarm ? "ALARM" : "");
+    } else {
+      printf("ERROR: Can't get temp%d data!\n", i);
     }
-  } else {
-    printf("ERROR: Can't get temp%d data!\n", i);
   }
   free(label);
 }
@@ -6063,16 +6063,16 @@
 
   if (!sensors_get_label_and_valid(*name, SENSORS_DME1737_FAN(i), &label,
 				   &valid) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_FAN(i), &cur) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_FAN_MIN(i), &min) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_FAN_ALARM(i), &alarm)) {
-    if (valid) {
+      valid) {
+    if (!sensors_get_feature(*name, SENSORS_DME1737_FAN(i), &cur) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_FAN_MIN(i), &min) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_FAN_ALARM(i), &alarm)) {
       print_label(label, 10);
       printf("%4.0f RPM  (min = %4.0f RPM)  %s\n", 
 	     cur, min, alarm ? "ALARM" : "");
+    } else {
+      printf("ERROR: Can't get fan%d data!\n", i);
     }
-  } else {
-    printf("ERROR: Can't get fan%d data!\n", i);
   }
   free(label);
 }
@@ -6085,15 +6085,15 @@
 
   if (!sensors_get_label_and_valid(*name, SENSORS_DME1737_PWM(i), &label,
 				   &valid) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_PWM(i), &cur) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_PWM_ENABLE(i), &enable) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_PWM_FREQ(i), &freq)) {
-    if (valid) {
+      valid) {
+    if (!sensors_get_feature(*name, SENSORS_DME1737_PWM(i), &cur) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_PWM_ENABLE(i), &enable) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_PWM_FREQ(i), &freq)) {
       print_label(label, 10);
       printf("%4.0f      (enable = %1.0f, freq = %6.0f Hz)\n", cur, enable, freq);
+    } else {
+      printf("ERROR: Can't get pwm%d data!\n", i);
     }
-  } else {
-    printf("ERROR: Can't get pwm%d data!\n", i);
   }
   free(label);
 }

[-- 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] dme1737 module

[Juergen Bausa]

> Von: Jean Delvare <khali@linux-fr.org>
> Gesendet: 06.09.07 11:51:43
> An: "Juerg Haefliger" <juergh@gmail.com>
> CC: lm-sensors@lm-sensors.org
> Betreff: Re: [lm-sensors] dme1737 module

> 
> We must rework the checks in the dme1737 printing functions to process
> the ignore statements properly, and to only display errors for missing
> features, not missing channels. I'm attaching the patch I have come up
> with. I can't test it as I do not have the hardware. Juergen, can you
> please test and report?
> 

Sorry I cant test it because I have the debian package installed. The patch doesnt
apply cleanly to my debian lm-sensors-2.10.4 and I dont want to install the source 
package.

Juergen
_______________________________________________________________________
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc\x022220


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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Jean,


> Hi Juerg,
>
> On Tue, 4 Sep 2007 11:54:20 -0700, Juerg Haefliger wrote:
> > > On Sun, 02 Sep 2007 14:57:32 +0200, Juergen Bausa wrote:
> > > > dme1737-i2c-0-2e
> > > > Adapter: SMBus nForce2 adapter at 4c00
> > > > V5stby:    +0.00 V  (min =  +0.00 V, max =  +6.64 V)  ALARM
> > > > Vccp:      +1.10 V  (min =  +0.00 V, max =  +2.99 V)
> > > > V3.3:      +3.28 V  (min =  +0.00 V, max =  +4.38 V)
> > > > V5:        +4.94 V  (min =  +0.00 V, max =  +6.64 V)
> > > > V12:      +11.80 V  (min =  +0.00 V, max = +15.94 V)
> > > > V3.3stby:  +3.29 V  (min =  +0.00 V, max =  +4.38 V)
> > > > Vbat:      +2.98 V  (min =  +0.00 V, max =  +4.38 V)
> > > > Int Temp:    +34°C  (low  =  -127°C, high =  +127°C)
> > > > CPU Temp:    +29°C  (low  =  -127°C, high =  +127°C)
> > > > CPU_Fan:     0 RPM  (min =    0 RPM)
> > > > ERROR: Can't get fan3 data!
> > > > ERROR: Can't get fan5 data!
> > > > ERROR: Can't get fan6 data!
> > > > CPU_PWM:     0      (enable = 1, freq =  25000 Hz)
> > > > ERROR: Can't get pwm5 data!
> > > > ERROR: Can't get pwm6 data!
> > > > cpu0_vid: +1.550 V  (VRM Version 2.4)
> > >
> > > Juerg, sensors shouldn't be displaying these errors for optional fans
> > > and pwms. Can you please provide a patch fixing this? It should be
> > > pretty easy.
> >
> > Hmm... An ignore statement would take care of this. Do you have
> > something else in mind?
>
> No, users shouldn't have to add ignore statements to hide these errors,
> the errors shouldn't be displayed in the first place. And as reported
> by Juergen, adding ignore statements doesn't even work in the case of
> the dme1737.
>
> We must rework the checks in the dme1737 printing functions to process
> the ignore statements properly, and to only display errors for missing
> features, not missing channels. I'm attaching the patch I have come up
> with. I can't test it as I do not have the hardware. Juergen, can you
> please test and report?
>
> Juerg, can you please review and test too?

Ok I'm officially confused now. Your patch only prevents error
messages if ignore statements are added. Is that the intended
behavior?


...juerg


> Admittedly this libsensors interface is confusing, the good news is
> that the future library handles the ignore statements all by itself so
> all these problems are gone :)
>
> --
> Jean Delvare
>
>

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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Juergen,

On 9/5/07, Juergen Bausa <Juergen.Bausa@web.de> wrote:
>
> > Von: "Juerg Haefliger" <juergh@gmail.com>
> >
> > Hi Juergen,
> >
> >
> > > > Von: "Juerg Haefliger" <juergh@gmail.com>
> > > >
> > > > > So, which version is needed to run the dme1737 on the asus board (Which I think doesnt have the
> > > > > SCH3114 Super I/O chip)?
> > > > >
>
> > >
> > > However, I get strange temperatures for the cpu. With the fan at 3000 rpm and idle cpu I get a temperature
> > > of 17 °C, while room temperature is 20°C. I think this is not possible.
> >
> > That is strange indeed. Can you reproduce this and then unload the
> > dme1737 module and run 'i2cdump 0 0x2e' and post the output?
> >
>
> Here it is. First sensors output (I installed a patch to make k8temp work on my brandnew AMD BE-2350 and
> results seem to be reasonable. However there is a discussion about this patch and I am not sure it is ok):
> dme1737-i2c-0-2e
> Adapter: SMBus nForce2 adapter at 4c00
> V5stby:    +0.00 V  (min =  +0.00 V, max =  +6.64 V)  ALARM
> Vccp:      +1.09 V  (min =  +0.00 V, max =  +2.99 V)
> V3.3:      +3.27 V  (min =  +0.00 V, max =  +4.38 V)
> V5:        +4.94 V  (min =  +0.00 V, max =  +6.64 V)
> V12:      +11.77 V  (min =  +0.00 V, max = +15.94 V)
> V3.3stby:  +3.29 V  (min =  +0.00 V, max =  +4.38 V)
> Vbat:      +2.98 V  (min =  +0.00 V, max =  +4.38 V)
> Int Temp:    +31°C  (low  =  -127°C, high =  +127°C)
> CPU Temp:    +16°C  (low  =  -127°C, high =  +127°C)
> CPU_Fan:  3010 RPM  (min =    0 RPM)
> ERROR: Can't get fan3 data!
> ERROR: Can't get fan5 data!
> ERROR: Can't get fan6 data!
> CPU_PWM:   255      (enable = 0, freq =  25000 Hz)
> ERROR: Can't get pwm5 data!
> ERROR: Can't get pwm6 data!
> cpu0_vid: +1.550 V  (VRM Version 2.4)
>
> k8temp-pci-00c3
> Adapter: PCI adapter
> Core0 Temp:
>              +29°C
> Core0 Temp:
>              +32°C
> Core1 Temp:
>              +36°C
> Core1 Temp:
>              +34°C
>
> And here the output from i2cdump. I had to modprobe i2c-dev to make it work. Is this normal?
>
> lisa:/home/jba# i2cdump 0 0x2e
> No size specified (using byte-data access)
> 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 5d be bd bc 80 1e 0f fe 06 ff ff ff ff ff ff    .]????????......
> 30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 5c 8a    ..............\?
> 40: 05 91 40 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 cb    ????........bbb?
> 60: cb bb e0 00 55 80 80 5a 5a 33 64 64 45 40 40 00    ???.U??ZZ3ddE@@.
> 70: ff ff ff 09 09 09 09 09 09 00 30 00 40 00 ec 18    ...??????.0.@.??
> 80: 7e a4 0e 00 42 90 3d 90 35 00 4d 4d 0b 0b 0c 00    ~??.B?=?5.MM???.
> 90: 04 04 04 04 0c 0c 0c 5a f1 bf ad 00 ff 00 ff 00    ???????Z???.....
> a0: 00 00 0c 00 02 00 00 0b 0b fe ff fe ff ff ff ff    ..?.?..???.?....
> b0: ff 00 00 00 00 00 28 28 0e 0e 2b 2b 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 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00    .?..............
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
>

The contents of the temperature registers match the output of sensors,
so it's not a conversion/display issue. The dme1737 does advertise the
measured temp as 16C. The only thing that's left is that the CPU diode
is not a 3904-type diode and the dme1737 gets the calculation wrong.
It wants to see a 3904 diode attached to its remote diode pins. If you
want closure, you need to check the docs for your CPU.

...juerg


>
> >
> > > I now use fancontrol which turns fan speed to 0 rpm. Here is the output of sensors:
> > >
> > > dme1737-i2c-0-2e
> > > Adapter: SMBus nForce2 adapter at 4c00
> > > V5stby:    +0.00 V  (min =  +0.00 V, max =  +6.64 V)  ALARM
> > > Vccp:      +1.10 V  (min =  +0.00 V, max =  +2.99 V)
> > > V3.3:      +3.28 V  (min =  +0.00 V, max =  +4.38 V)
> > > V5:        +4.94 V  (min =  +0.00 V, max =  +6.64 V)
> > > V12:      +11.80 V  (min =  +0.00 V, max = +15.94 V)
> > > V3.3stby:  +3.29 V  (min =  +0.00 V, max =  +4.38 V)
> > > Vbat:      +2.98 V  (min =  +0.00 V, max =  +4.38 V)
> > > Int Temp:    +34°C  (low  =  -127°C, high =  +127°C)
> > > CPU Temp:    +29°C  (low  =  -127°C, high =  +127°C)
> > > CPU_Fan:     0 RPM  (min =    0 RPM)
> > > ERROR: Can't get fan3 data!
> > > ERROR: Can't get fan5 data!
> > > ERROR: Can't get fan6 data!
> > > CPU_PWM:     0      (enable = 1, freq =  25000 Hz)
> > > ERROR: Can't get pwm5 data!
> > > ERROR: Can't get pwm6 data!
> > > cpu0_vid: +1.550 V  (VRM Version 2.4)
> > >
> > > I think 29 °C is also very low for idle and no fan, even for my AMD BE-2350
> > > (45 w maximum power consumption). Also, Int-Temperature (is this board temperature?)
> > > is higher than cpu- temperature. This changes only for high load, where
> > > cpu-temperature increases more than int-temperature.
> >
> > That's possible. The Int-temp is the dme1737 internal temperature, not
> > the 'board' temperature. Depending on how hot the chip itself is this
> > temperature can be rather high.
> >
> >
> > > At first I thought that temperature calculation is wrong in lm-sensors. However,
> > > BIOS shows nearly the same temperatures.
> >
> > There's not much that can be done wrong here. All the driver does is
> > convert from unsigned to signed. Sensors itself doesn't do any
> > conversion.
> >
>
> So maybe the reason for the low temperature is just the measurement error? Maybe the real
> temperature is 23 ° and the error is 7 K?
>
> Juergen
> ______________________________________________________________________________
> Jetzt neu! Im riesigen WEB.DE Club SmartDrive Dateien freigeben und mit
> Freunden teilen! http://www.freemail.web.de/club/smartdrive_ttc.htm/?mc\x021134
>
>

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

Re: [lm-sensors] dme1737 module

[Jean Delvare]

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

Hi Juerg,

On Thu, 6 Sep 2007 20:01:04 -0700, Juerg Haefliger wrote:
> > We must rework the checks in the dme1737 printing functions to process
> > the ignore statements properly, and to only display errors for missing
> > features, not missing channels. I'm attaching the patch I have come up
> > with. I can't test it as I do not have the hardware. Juergen, can you
> > please test and report?
> >
> > Juerg, can you please review and test too?
> 
> Ok I'm officially confused now. Your patch only prevents error
> messages if ignore statements are added. Is that the intended
> behavior?

No, it's not. See how confusing the API is, it managed to fool me.
sensors_get_label() succeeds even for missing features!

Attached is an updated patch. Voltages and temperatures part is
unchanged (honor ignore statements), fans and pwms part is much more
simple (simply ignore errors). Please test and report.

-- 
Jean Delvare

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: sensors-dme1737-hide-errors-v2.patch --]
[-- Type: text/x-patch; name=sensors-dme1737-hide-errors-v2.patch, Size: 2941 bytes --]

Index: prog/sensors/chips.c
===================================================================
--- prog/sensors/chips.c	(révision 4791)
+++ prog/sensors/chips.c	(copie de travail)
@@ -6016,17 +6016,17 @@
 
   if (!sensors_get_label_and_valid(*name, SENSORS_DME1737_IN(i), &label,
 				   &valid) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_IN(i), &cur) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_IN_MIN(i), &min) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_IN_MAX(i), &max) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_IN_ALARM(i), &alarm)) {
-    if (valid) {
+      valid) {
+    if (!sensors_get_feature(*name, SENSORS_DME1737_IN(i), &cur) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_IN_MIN(i), &min) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_IN_MAX(i), &max) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_IN_ALARM(i), &alarm)) {
       print_label(label, 10);
       printf("%+6.2f V  (min = %+6.2f V, max = %+6.2f V)  %s\n",
 	     cur, min, max, alarm ? "ALARM" : "");
+    } else {
+      printf("ERROR: Can't get in%d data!\n", i);
     }
-  } else {
-    printf("ERROR: Can't get in%d data!\n", i);
   }
   free(label);
 }
@@ -6039,18 +6039,18 @@
 
   if (!sensors_get_label_and_valid(*name, SENSORS_DME1737_TEMP(i), &label,
 				   &valid) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_TEMP(i), &cur) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_TEMP_MIN(i), &min) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_TEMP_MAX(i), &max) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_TEMP_ALARM(i), &alarm) &&
-      !sensors_get_feature(*name, SENSORS_DME1737_TEMP_FAULT(i), &fault)) {
-    if (valid) {
+      valid) {
+    if (!sensors_get_feature(*name, SENSORS_DME1737_TEMP(i), &cur) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_TEMP_MIN(i), &min) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_TEMP_MAX(i), &max) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_TEMP_ALARM(i), &alarm) &&
+        !sensors_get_feature(*name, SENSORS_DME1737_TEMP_FAULT(i), &fault)) {
       print_label(label, 10);
       print_temp_info(cur, max, min, MINMAX, 0, 0);
       printf("%s%s\n", fault ? "FAULT  " : "", alarm ? "ALARM" : "");
+    } else {
+      printf("ERROR: Can't get temp%d data!\n", i);
     }
-  } else {
-    printf("ERROR: Can't get temp%d data!\n", i);
   }
   free(label);
 }
@@ -6071,8 +6071,6 @@
       printf("%4.0f RPM  (min = %4.0f RPM)  %s\n", 
 	     cur, min, alarm ? "ALARM" : "");
     }
-  } else {
-    printf("ERROR: Can't get fan%d data!\n", i);
   }
   free(label);
 }
@@ -6092,8 +6090,6 @@
       print_label(label, 10);
       printf("%4.0f      (enable = %1.0f, freq = %6.0f Hz)\n", cur, enable, freq);
     }
-  } else {
-    printf("ERROR: Can't get pwm%d data!\n", i);
   }
   free(label);
 }

[-- 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] dme1737 module

[Juergen Bausa]

> -----Ursprüngliche Nachricht-----
> Von: "Juerg Haefliger" <juergh@gmail.com>
> Gesendet: 08.09.07 15:41:35
> An: "Juergen Bausa" <Juergen.Bausa@web.de>
> CC: lm-sensors@lm-sensors.org
> Betreff: Re: [lm-sensors] dme1737 module

> 
> The contents of the temperature registers match the output of sensors,
> so it's not a conversion/display issue. The dme1737 does advertise the
> measured temp as 16C. The only thing that's left is that the CPU diode
> is not a 3904-type diode and the dme1737 gets the calculation wrong.
> It wants to see a 3904 diode attached to its remote diode pins. If you
> want closure, you need to check the docs for your CPU.
> 

So the actual sensor is on the cpu and the processing is done on the board?

Is processing done by the bios or by dme1737?

The type of my cpu  is very new.  At boot up, the bios displays "unknown 
cpu type". So, this might be the reason why it does not know how to handle 
the sensor output. If this is true, next bios revision might solve the problem.

Is this correct?

Juergen
______________________________________________________________________
XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club!		
Jetzt testen! http://produkte.web.de/club/?mc\x021130


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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Juergen,


>
> > -----Ursprüngliche Nachricht-----
> > Von: "Juerg Haefliger" <juergh@gmail.com>
> > Gesendet: 08.09.07 15:41:35
> > An: "Juergen Bausa" <Juergen.Bausa@web.de>
> > CC: lm-sensors@lm-sensors.org
> > Betreff: Re: [lm-sensors] dme1737 module
>
> >
> > The contents of the temperature registers match the output of sensors,
> > so it's not a conversion/display issue. The dme1737 does advertise the
> > measured temp as 16C. The only thing that's left is that the CPU diode
> > is not a 3904-type diode and the dme1737 gets the calculation wrong.
> > It wants to see a 3904 diode attached to its remote diode pins. If you
> > want closure, you need to check the docs for your CPU.
> >
>
> So the actual sensor is on the cpu and the processing is done on the board?

Yes.


> Is processing done by the bios or by dme1737?

In the dme1737.


> The type of my cpu  is very new.  At boot up, the bios displays "unknown
> cpu type". So, this might be the reason why it does not know how to handle
> the sensor output.

Can you send the output of 'cat /proc/cpuinfo'?


> If this is true, next bios revision might solve the problem.

A BIOS upgrade might fix the display of the temp numbers on the BIOS
config screen it will not affect the output of sensors. The Linux
driver reads the temp directly from the dme1737, the BIOS is not
involved at all. If it turns out that the temp diode in your CPU is
not a 3904 type, the only 2 options are:
1) Tweak the dme1737 to recognize the diode type (not sure if that's
possible, I have to look at the datasheet).
2) Come up with a conversion algorithm and put it into sensors.conf.

...juerg


> Is this correct?
>
> Juergen
> ______________________________________________________________________
> XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club!
> Jetzt testen! http://produkte.web.de/club/?mc\x021130
>
>

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

Re: [lm-sensors] dme1737 module

[Jean Delvare]

Hi Juerg, Juergen,

On 9/12/2007, Juerg Haefliger wrote:
>> If this is true, next bios revision might solve the problem.
>
>A BIOS upgrade might fix the display of the temp numbers on the BIOS
>config screen it will not affect the output of sensors. The Linux
>driver reads the temp directly from the dme1737, the BIOS is not
>involved at all. If it turns out that the temp diode in your CPU is
>not a 3904 type, the only 2 options are:
>1) Tweak the dme1737 to recognize the diode type (not sure if that's
>possible, I have to look at the datasheet).
>2) Come up with a conversion algorithm and put it into sensors.conf.

This isn't totally correct in the case of the DME1737, as it has
temperature offset registers. It would be possible for the BIOS to set
the CPU temperature offset depending on the CPU model, and that would
affect Linux as well. That would mean a very well written BIOS, that's
rather rare in my experience.

If the BIOS doesn't write the offset, you can do it. But of course you
have to know the correction factor for your CPU, and I'm not sure where
you can find this information.

--
Jean Delvare

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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

On 9/12/07, Jean Delvare <khali@linux-fr.org> wrote:
>
> Hi Juerg, Juergen,
>
> On 9/12/2007, Juerg Haefliger wrote:
> >> If this is true, next bios revision might solve the problem.
> >
> >A BIOS upgrade might fix the display of the temp numbers on the BIOS
> >config screen it will not affect the output of sensors. The Linux
> >driver reads the temp directly from the dme1737, the BIOS is not
> >involved at all. If it turns out that the temp diode in your CPU is
> >not a 3904 type, the only 2 options are:
> >1) Tweak the dme1737 to recognize the diode type (not sure if that's
> >possible, I have to look at the datasheet).
> >2) Come up with a conversion algorithm and put it into sensors.conf.
>
> This isn't totally correct in the case of the DME1737, as it has
> temperature offset registers. It would be possible for the BIOS to set
> the CPU temperature offset depending on the CPU model, and that would
> affect Linux as well. That would mean a very well written BIOS, that's
> rather rare in my experience.

Yes, that's what I meant by tweaking the dme1737, just poorly
formulated. I'm not sure if there's other registers besides the offset
registers. And you're right, if the BIOS does it we're OK.


> If the BIOS doesn't write the offset, you can do it. But of course you
> have to know the correction factor for your CPU, and I'm not sure where
> you can find this information.
>
> --
> Jean Delvare
>

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

Re: [lm-sensors] dme1737 module

[Juergen Bausa]

> -----Ursprüngliche Nachricht-----
> Von: "Juerg Haefliger" <juergh@gmail.com>


> 
> > The type of my cpu  is very new.  At boot up, the bios displays "unknown
> > cpu type". So, this might be the reason why it does not know how to handle
> > the sensor output.
> 
> Can you send the output of 'cat /proc/cpuinfo'?
> 

It is a amd athlon x2 BE-2350

jba@lisa:~$ cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 107
model name      : AMD Processor model unknown
stepping        : 1
cpu MHz         : 1000.000
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8legacy ts fid vid ttp tm stc [6]
bogomips        : 2011.01

processor       : 1
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 107
model name      : AMD Processor model unknown
stepping        : 1
cpu MHz         : 1000.000
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8legacy ts fid vid ttp tm stc [6]
bogomips        : 2011.01


Juergen
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc\x100071&distributionid\00000000066


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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Jean,

On 9/9/07, Jean Delvare <khali@linux-fr.org> wrote:
> Hi Juerg,
>
> On Thu, 6 Sep 2007 20:01:04 -0700, Juerg Haefliger wrote:
> > > We must rework the checks in the dme1737 printing functions to process
> > > the ignore statements properly, and to only display errors for missing
> > > features, not missing channels. I'm attaching the patch I have come up
> > > with. I can't test it as I do not have the hardware. Juergen, can you
> > > please test and report?
> > >
> > > Juerg, can you please review and test too?
> >
> > Ok I'm officially confused now. Your patch only prevents error
> > messages if ignore statements are added. Is that the intended
> > behavior?
>
> No, it's not. See how confusing the API is, it managed to fool me.
> sensors_get_label() succeeds even for missing features!
>
> Attached is an updated patch. Voltages and temperatures part is
> unchanged (honor ignore statements), fans and pwms part is much more
> simple (simply ignore errors). Please test and report.

This one behaves correctly.

Acked-by: Juerg Haefliger <juergh at gmail.com>

...juerg


> Jean Delvare
>
>

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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Juergen,


> > -----Ursprüngliche Nachricht-----
> > Von: "Juerg Haefliger" <juergh@gmail.com>
>
>
> >
> > > The type of my cpu  is very new.  At boot up, the bios displays "unknown
> > > cpu type". So, this might be the reason why it does not know how to handle
> > > the sensor output.
> >
> > Can you send the output of 'cat /proc/cpuinfo'?
> >
>
> It is a amd athlon x2 BE-2350
>
> jba@lisa:~$ cat /proc/cpuinfo
> processor       : 0
> vendor_id       : AuthenticAMD
> cpu family      : 15
> model           : 107
> model name      : AMD Processor model unknown
> stepping        : 1
> cpu MHz         : 1000.000
> cache size      : 512 KB
> physical id     : 0
> siblings        : 2
> core id         : 0
> cpu cores       : 2
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8legacy ts fid vid ttp tm stc [6]
> bogomips        : 2011.01
>
> processor       : 1
> vendor_id       : AuthenticAMD
> cpu family      : 15
> model           : 107
> model name      : AMD Processor model unknown
> stepping        : 1
> cpu MHz         : 1000.000
> cache size      : 512 KB
> physical id     : 0
> siblings        : 2
> core id         : 1
> cpu cores       : 2
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8legacy ts fid vid ttp tm stc [6]
> bogomips        : 2011.01
>

No specs available for this processor, sorry.

...juerg


> Juergen
> _____________________________________________________________________
> Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
> http://smartsurfer.web.de/?mc\x100071&distributionid\00000000066
>
>

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

Re: [lm-sensors] dme1737 module

[Werner Goebl]

Dear Juerg,

I am running Gutsy on an Optiplex 745 (Kernel 2.6.22-14, 
Intel Q965 chipset) and in order to quiet my always spinning 
fan, I wanted to add the dme1737 module to my old kernel.
So, I did what you suggested (copy dmel1713.c + create 
Makefile).

When I type "make" it says:
"make: Nothing to be done for `all'."

BTW: You mention to have "the kernel headers intalled to be 
able to compile". Are you referring to "Kconfig" and 
"Makefile" in 
/usr/src/linux-headers-2.6.22-14/drivers/hwmon? (which I 
updated according to
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h”31996f55f8a3c04cdcb63895cf7661e135fadb

Thanks for your patience!!

Werner

---------------------------------------------
From: Juerg Haefliger <juergh <at> gmail.com>
Subject: Re: dme1737 module
Newsgroups: gmane.linux.drivers.sensors
Date: 2007-08-22 16:11:13 GMT (16 weeks, 4 days, 5 hours and 
35 minutes ago)

Hi Juergen,

I'm copying the list so others can profit.


 > Dear Juerg,
 >
 > I own a barebone made by asus which needs the dme1737 
module for lm-sensors to
 > work correctly. Since it had been included in kernel 
2.6.23 and I am running 2.6.18 (from
 > debian etch) I was wondering if there is a stand alone 
version of the module, that I could
 > compile for my kernel? Is there any way to use it with 
2.6.18?

Copy the file dme1737.c from the 2.6.23 kernel to a temp 
directory and
create a Makefile in the same directory that contains the 
following
lines:

obj-m := dme1737.o
all:
         make -C /lib/modules/`uname -r`/build M=$(PWD) modules

Then run 'make' which will compile the module. You also need 
to have
the kernel headers installed to be able to compile.
Additionally, you will also need the latest 'lm-sensors' package
(2.10.4 ) or the dme1737 will not be recognized.

Let me know if you need additional help.
...juerg

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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Werner,


On Dec 16, 2007 2:41 PM, Werner Goebl <werner.goebl@mail.mcgill.ca> wrote:
> Dear Juerg,
>
> I am running Gutsy on an Optiplex 745 (Kernel 2.6.22-14,
> Intel Q965 chipset) and in order to quiet my always spinning
> fan, I wanted to add the dme1737 module to my old kernel.
> So, I did what you suggested (copy dmel1713.c + create
> Makefile).
>
> When I type "make" it says:
> "make: Nothing to be done for `all'."

Make sure you're using tabs and not whitespaces in your makefile. I.e.:

all:
<TAB>make -C /lib/modules/`uname -r`/build M=$(PWD) modules


>
> BTW: You mention to have "the kernel headers intalled to be
> able to compile". Are you referring to "Kconfig" and
> "Makefile" in
> /usr/src/linux-headers-2.6.22-14/drivers/hwmon? (which I
> updated according to
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h”31996f55f8a3c04cdcb63895cf7661e135fadb

No that's not what I meant. What you need are the kernel headers that
are part of the kernel source (or devel) package for your
distribution. Check the /lib/modules/`uname -r`/build directory. If
you find header files in that tree you're all set. Otherwise you have
to locate the package that provides these header files. For Ubuntu,
the package name is something like 'linux-headers-2.6.22-14'.

...juerg


> Thanks for your patience!!
>
> Werner
>
> ---------------------------------------------
> From: Juerg Haefliger <juergh <at> gmail.com>
> Subject: Re: dme1737 module
> Newsgroups: gmane.linux.drivers.sensors
> Date: 2007-08-22 16:11:13 GMT (16 weeks, 4 days, 5 hours and
> 35 minutes ago)
>
> Hi Juergen,
>
> I'm copying the list so others can profit.
>
>
>  > Dear Juerg,
>  >
>  > I own a barebone made by asus which needs the dme1737
> module for lm-sensors to
>  > work correctly. Since it had been included in kernel
> 2.6.23 and I am running 2.6.18 (from
>  > debian etch) I was wondering if there is a stand alone
> version of the module, that I could
>  > compile for my kernel? Is there any way to use it with
> 2.6.18?
>
> Copy the file dme1737.c from the 2.6.23 kernel to a temp
> directory and
> create a Makefile in the same directory that contains the
> following
> lines:
>
> obj-m := dme1737.o
> all:
>          make -C /lib/modules/`uname -r`/build M=$(PWD) modules
>
> Then run 'make' which will compile the module. You also need
> to have
> the kernel headers installed to be able to compile.
> Additionally, you will also need the latest 'lm-sensors' package
> (2.10.4 ) or the dme1737 will not be recognized.
>
> Let me know if you need additional help.
> ...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] dme1737 module

[Juerg Haefliger]

Hi Werner,

Please keep the list in the loop so others can profit from this information.


On Dec 19, 2007 8:30 AM, Werner Goebl <werner.goebl@mail.mcgill.ca> wrote:
> Hi Juerg,
>
> good point -- I relied on informations from the web about
> the Q965 chipset, but I learned that I was wrong!
>
> So: I have a SMSC SCH5514D-NS chip (which is not on the list
> unfortunately). I guess I am stuck now?

Good information, thanks. At least we can update sensors-detect to
correctly identify your chip. Unfortunately, this being a Dell
machine, SMSC won't provide technical information for this chip to me
since I'm an HP person :-)

Let's try to figure out if it's compatible to any other supported SMSC
chip before we give up. Can you run 'isadump -k 0x55 0x2e 0x2f 0xa'
and post the output?

...juerg


>
> Thanks for all your help!
> Werner
>
>
> > Silly question: What makes you think your system has a dme1737? The
> > device ID of the dme1737 is 0x78 or 0x77, not 0x83. Can you open up
> > the machine and look for an SMSC branded chip and tell us the chip
> > name?
>
>

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

Re: [lm-sensors] dme1737 module

[Werner Goebl]

Hi Juerg,

>> good point -- I relied on informations from the web about
>> the Q965 chipset, but I learned that I was wrong!
>>
>> So: I have a SMSC SCH5514D-NS chip (which is not on the list
>> unfortunately). I guess I am stuck now?
> 
> Good information, thanks. At least we can update sensors-detect to
> correctly identify your chip. Unfortunately, this being a Dell
> machine, SMSC won't provide technical information for this chip to me
> since I'm an HP person :-)

Ah, I didn't think of such things. I saw on the SMSC webpage 
that there is information only to a very limited number of 
chips.

> Let's try to figure out if it's compatible to any other supported SMSC
> chip before we give up. Can you run 'isadump -k 0x55 0x2e 0x2f 0xa'
> and post the output?

eh voila:
 > sudo isadump -k 0x55 0x2e 0x2f 0xa
WARNING! Running this program can cause system crashes, data 
loss and worse!
I will probe address register 0x2e and data register 0x2f.
Probing bank 10 using bank register 0x07.
Continue? [Y/n]
      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: 00 00 00 00 00 00 00 0a 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: 83 0f 38 00 04 00 2e 00 00 00 00 00 10 00 00 00
30: 01 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: 0c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 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 ff ff ff ff ff ff
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 00 00 00 00 00 00 00 00

All the best
Werner

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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Werner,


On Dec 19, 2007 11:21 AM, Werner Goebl <werner.goebl@mail.mcgill.ca> wrote:
> Hi Juerg,
>
> >> good point -- I relied on informations from the web about
> >> the Q965 chipset, but I learned that I was wrong!
> >>
> >> So: I have a SMSC SCH5514D-NS chip (which is not on the list
> >> unfortunately). I guess I am stuck now?
> >
> > Good information, thanks. At least we can update sensors-detect to
> > correctly identify your chip. Unfortunately, this being a Dell
> > machine, SMSC won't provide technical information for this chip to me
> > since I'm an HP person :-)
>
> Ah, I didn't think of such things. I saw on the SMSC webpage
> that there is information only to a very limited number of
> chips.
>
> > Let's try to figure out if it's compatible to any other supported SMSC
> > chip before we give up. Can you run 'isadump -k 0x55 0x2e 0x2f 0xa'
> > and post the output?
>
> eh voila:
>  > sudo isadump -k 0x55 0x2e 0x2f 0xa
> WARNING! Running this program can cause system crashes, data
> loss and worse!
> I will probe address register 0x2e and data register 0x2f.
> Probing bank 10 using bank register 0x07.
> Continue? [Y/n]
>       0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00: 00 00 00 00 00 00 00 0a 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: 83 0f 38 00 04 00 2e 00 00 00 00 00 10 00 00 00
> 30: 01 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: 0c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 00 00 00 00 00 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 ff ff ff ff ff ff
> 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 00 00 00 00 00 00 00 00

Very good, now can you do  'isadump -f 0xc00'?

...juerg


> All the best
> Werner
>

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

Re: [lm-sensors] dme1737 module

[Werner Goebl]

> Very good, now can you do  'isadump -f 0xc00'?
> 
> ...juerg

isadump -f 0xc00
WARNING! Running this program can cause system crashes, data loss 
and worse!
I will probe address range 0xc00 to 0xcff.
Continue? [Y/n]
        0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00

Best
Werner


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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Werner,


On Dec 19, 2007 12:34 PM, Werner Goebl <werner.goebl@mail.mcgill.ca> wrote:
> > Very good, now can you do  'isadump -f 0xc00'?
> >
> > ...juerg
>
> isadump -f 0xc00
> WARNING! Running this program can cause system crashes, data loss
> and worse!
> I will probe address range 0xc00 to 0xcff.
> Continue? [Y/n]
>         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
> 0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
> 0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
> 0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
> 0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
> 0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
> 0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
> 0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00

That looks promising so far. Now can you run a cpu stress test like
cpuburn and take a couple of register dumps so that we can see which
register values change over time while the CPU is heating up?

...juerg


> Best
> Werner
>
>

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

Re: [lm-sensors] dme1737 module

[Werner Goebl]

> That looks promising so far. Now can you run a cpu stress test like
> cpuburn and take a couple of register dumps so that we can see which
> register values change over time while the CPU is heating up?
> 
> ...juerg
> 
> 
Hi Juerg,

so I documented the command: sudo isadump -f 0xc00 for core 
temperatures from 44 to 52 degrees.

Greetings
Werner

idle...

[sudo] password for werner:
WARNING! Running this program can cause system crashes, data loss 
and worse!
I will probe address range 0xc00 to 0xcff.
Continue? [Y/n]
        0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00


Dellibes:~> sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +44°C  (high =  +100°C)

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

Dellibes:~> sudo isadump -f 0xc00
WARNING! Running this program can cause system crashes, data loss 
and worse!
I will probe address range 0xc00 to 0xcff.
Continue? [Y/n]
        0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00


Dellibes:~> sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +45°C  (high =  +100°C)

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

Dellibes:~> sudo isadump -f 0xc00
WARNING! Running this program can cause system crashes, data loss 
and worse!
I will probe address range 0xc00 to 0xcff.
Continue? [Y/n]
        0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00

Dellibes:~> sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +46°C  (high =  +100°C)

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

Dellibes:~> sudo isadump -f 0xc00
WARNING! Running this program can cause system crashes, data loss 
and worse!
I will probe address range 0xc00 to 0xcff.
Continue? [Y/n]
        0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00

Dellibes:~> sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +47°C  (high =  +100°C)

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

Dellibes:~> sudo isadump -f 0xc00
WARNING! Running this program can cause system crashes, data loss 
and worse!
I will probe address range 0xc00 to 0xcff.
Continue? [Y/n]
        0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00


Dellibes:~> sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +48°C  (high =  +100°C)

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

Dellibes:~> sudo isadump -f 0xc00
WARNING! Running this program can cause system crashes, data loss 
and worse!
I will probe address range 0xc00 to 0xcff.
Continue? [Y/n]
        0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00




Dellibes:~> sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +50°C  (high =  +100°C)

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

Dellibes:~> sudo isadump -f 0xc00
WARNING! Running this program can cause system crashes, data loss 
and worse!
I will probe address range 0xc00 to 0xcff.
Continue? [Y/n]
        0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00




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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Werner,

On Dec 19, 2007 1:26 PM, Werner Goebl <werner.goebl@mail.mcgill.ca> wrote:
>
> > That looks promising so far. Now can you run a cpu stress test like
> > cpuburn and take a couple of register dumps so that we can see which
> > register values change over time while the CPU is heating up?
> >
> > ...juerg
> >
> >
> Hi Juerg,
>
> so I documented the command: sudo isadump -f 0xc00 for core
> temperatures from 44 to 52 degrees.
>
> Greetings
> Werner
>
> idle...
>
> [sudo] password for werner:
> WARNING! Running this program can cause system crashes, data loss
> and worse!
> I will probe address range 0xc00 to 0xcff.
> Continue? [Y/n]
>         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
> 0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
> 0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
> 0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
> 0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
> 0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
> 0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
> 0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00
>
>
> Dellibes:~> sensors
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +44°C  (high =  +100°C)
>
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +45°C  (high =  +100°C)
>
> Dellibes:~> sudo isadump -f 0xc00
> WARNING! Running this program can cause system crashes, data loss
> and worse!
> I will probe address range 0xc00 to 0xcff.
> Continue? [Y/n]
>         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
> 0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
> 0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
> 0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
> 0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
> 0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
> 0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
> 0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00
>
>
> Dellibes:~> sensors
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +45°C  (high =  +100°C)
>
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +47°C  (high =  +100°C)
>
> Dellibes:~> sudo isadump -f 0xc00
> WARNING! Running this program can cause system crashes, data loss
> and worse!
> I will probe address range 0xc00 to 0xcff.
> Continue? [Y/n]
>         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
> 0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
> 0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
> 0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
> 0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
> 0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
> 0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
> 0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00
>
> Dellibes:~> sensors
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +46°C  (high =  +100°C)
>
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +48°C  (high =  +100°C)
>
> Dellibes:~> sudo isadump -f 0xc00
> WARNING! Running this program can cause system crashes, data loss
> and worse!
> I will probe address range 0xc00 to 0xcff.
> Continue? [Y/n]
>         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
> 0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
> 0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
> 0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
> 0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
> 0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
> 0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
> 0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00
>
> Dellibes:~> sensors
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +47°C  (high =  +100°C)
>
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +49°C  (high =  +100°C)
>
> Dellibes:~> sudo isadump -f 0xc00
> WARNING! Running this program can cause system crashes, data loss
> and worse!
> I will probe address range 0xc00 to 0xcff.
> Continue? [Y/n]
>         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
> 0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
> 0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
> 0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
> 0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
> 0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
> 0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
> 0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00
>
>
> Dellibes:~> sensors
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +48°C  (high =  +100°C)
>
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +50°C  (high =  +100°C)
>
> Dellibes:~> sudo isadump -f 0xc00
> WARNING! Running this program can cause system crashes, data loss
> and worse!
> I will probe address range 0xc00 to 0xcff.
> Continue? [Y/n]
>         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
> 0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
> 0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
> 0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
> 0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
> 0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
> 0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
> 0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00
>
>
>
>
> Dellibes:~> sensors
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +50°C  (high =  +100°C)
>
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +52°C  (high =  +100°C)
>
> Dellibes:~> sudo isadump -f 0xc00
>
> WARNING! Running this program can cause system crashes, data loss
> and worse!
> I will probe address range 0xc00 to 0xcff.
> Continue? [Y/n]
>         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 0c00: 00 00 01 00 18 00 60 08 00 00 00 00 00 00 00 00
> 0c10: 02 00 60 08 00 00 40 40 00 00 00 00 00 00 03 02
> 0c20: 00 00 00 05 05 00 05 84 05 00 00 80 01 01 01 00
> 0c30: 05 05 00 01 05 01 05 00 09 84 84 04 04 08 00 05
> 0c40: 05 05 04 05 04 05 04 86 86 00 00 2b 67 2f 00 57
> 0c50: 00 e1 00 04 00 00 04 04 84 01 01 04 04 00 0f 00
> 0c60: 00 01 00 06 00 c0 00 03 00 e0 00 00 00 00 00 00
> 0c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff b9 ec 00 00

Shoot, the register values didn't change. So we're looking at the
wrong thing here. Darn...

Please run 'isadump -k 0x55 0x2e 0x2f 0x8' and 'isadump -k 0x55 0x2e
0x2f 0x9' and post the output. We have to look at a different logical
device.
And please also post the output of 'lspci -vv -nn' and the full output
of 'sensors-detect'.

...juerg

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

Re: [lm-sensors] dme1737 module

[Werner Goebl]

> Shoot, the register values didn't change. So we're looking at the
> wrong thing here. Darn...
> 
> Please run 'isadump -k 0x55 0x2e 0x2f 0x8' and 'isadump -k 0x55 0x2e
> 0x2f 0x9' and post the output. We have to look at a different logical
> device.
> And please also post the output of 'lspci -vv -nn' and the full output
> of 'sensors-detect'.
> 
> ...juerg

Here is all the listings!
Best
Werner


sudo isadump -k 0x55 0x2e 0x2f 0x8
[sudo] password for werner:
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]
      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 00 00
20: 83 0f 38 00 04 00 2e 00 00 00 00 00 10 00 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 00 00 00 00 00 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 ff ff ff ff ff ff
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 00 00 00 00 00 00 00 00

  sudo isadump -k 0x55 0x2e 0x2f 0x9
WARNING! Running this program can cause system crashes, data loss 
and worse!
I will probe address register 0x2e and data register 0x2f.
Probing bank 9 using bank register 0x07.
Continue? [Y/n]
      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: 00 00 00 00 00 00 00 09 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: 83 0f 38 00 04 00 2e 00 00 00 00 00 10 00 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 00 00 00 00 00 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 ff ff ff ff ff ff
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 00 00 00 00 00 00 00 00



sudo lspci -vv -nn
00:00.0 Host bridge [0600]: Intel Corporation 82Q963/Q965 Memory 
Controller Hub [8086:2990] (rev 02)
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR+ FastB2B-
         Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSELúst 
 >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
         Latency: 0
         Capabilities: [e0] Vendor Specific Information

00:02.0 VGA compatible controller [0300]: Intel Corporation 
82Q963/Q965 Integrated Graphics Controller [8086:2992] (rev 02) 
(prog-if 00 [VGA])
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR- FastB2B-
         Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSELúst 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Interrupt: pin A routed to IRQ 16
         Region 0: Memory at dfe00000 (32-bit, non-prefetchable) 
[size=1M]
         Region 2: Memory at c0000000 (64-bit, prefetchable) 
[size%6M]
         Region 4: I/O ports at ecb8 [size=8]
         Capabilities: [90] Message Signalled Interrupts: Mask- 
64bit- Queue=0/0 Enable-
                 Address: 00000000  Data: 0000
         Capabilities: [d0] Power Management version 2
                 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.1 Display controller [0380]: Intel Corporation 82Q963/Q965 
Integrated Graphics Controller [8086:2993] (rev 02)
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR- FastB2B-
         Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSELúst 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Region 0: Memory at dff00000 (32-bit, non-prefetchable) 
[size=1M]
         Capabilities: [d0] Power Management version 2
                 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Contoller #4 [8086:2834] (rev 02) (prog-if 00 
[UHCI])
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR- FastB2B-
         Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Interrupt: pin A routed to IRQ 16
         Region 4: I/O ports at ff20 [size2]

00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #5 [8086:2835] (rev 02) (prog-if 00 
[UHCI])
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR- FastB2B-
         Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Interrupt: pin B routed to IRQ 17
         Region 4: I/O ports at ff00 [size2]

00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB2 EHCI Controller #2 [8086:283a] (rev 02) (prog-if 20 
[EHCI])
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR+ FastB2B-
         Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Interrupt: pin C routed to IRQ 20
         Region 0: Memory at dfdfbc00 (32-bit, non-prefetchable) 
[size=1K]
         Capabilities: [50] Power Management version 2
                 Flags: PMEClk- DSI- D1- D2- AuxCurrent75mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
         Capabilities: [58] Debug port

00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 
Family) HD Audio Controller [8086:284b] (rev 02)
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR+ FastB2B-
         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0, Cache Line Size: 64 bytes
         Interrupt: pin A routed to IRQ 16
         Region 0: Memory at dfdfc000 (64-bit, non-prefetchable) 
[size\x16K]
         Capabilities: [50] Power Management version 2
                 Flags: PMEClk- DSI- D1- D2- AuxCurrentUmA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
         Capabilities: [60] Message Signalled Interrupts: Mask- 
64bit+ Queue=0/0 Enable-
                 Address: 0000000000000000  Data: 0000
         Capabilities: [70] Express Unknown type IRQ 0
                 Device: Supported: MaxPayload 128 bytes, 
PhantFunc 0, ExtTag-
                 Device: Latency L0s <64ns, L1 <1us
                 Device: Errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
                 Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
                 Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                 Link: Supported Speed unknown, Width x0, ASPM 
unknown, Port 0
                 Link: Latency L0s <64ns, L1 <1us
                 Link: ASPM Disabled CommClk- ExtSynch-
                 Link: Speed unknown, Width x0

00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 1 [8086:283f] (rev 02) (prog-if 00 [Normal decode])
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR+ FastB2B-
         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0, Cache Line Size: 64 bytes
         Bus: primary\0, secondary\x01, subordinate\x01, sec-latency=0
         Memory behind bridge: dfc00000-dfcfffff
         Secondary status: 66MHz- FastB2B- ParErr- DEVSELúst 
 >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
         BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- 
FastB2B-
         Capabilities: [40] Express Root Port (Slot+) IRQ 0
                 Device: Supported: MaxPayload 128 bytes, 
PhantFunc 0, ExtTag-
                 Device: Latency L0s unlimited, L1 unlimited
                 Device: Errors: Correctable+ Non-Fatal+ Fatal+ 
Unsupported+
                 Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                 Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                 Link: Supported Speed 2.5Gb/s, Width x1, ASPM 
L0s, Port 1
                 Link: Latency L0s <256ns, L1 <4us
                 Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
                 Link: Speed 2.5Gb/s, Width x0
                 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- 
HotPlug+ Surpise+
                 Slot: Number 4, PowerLimit 10.000000
                 Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- 
CmdCplt- HPIrq-
                 Slot: AttnInd Unknown, PwrInd Unknown, Power-
                 Root: Correctable- Non-Fatal- Fatal- PME-
         Capabilities: [80] Message Signalled Interrupts: Mask- 
64bit- Queue=0/0 Enable-
                 Address: 00000000  Data: 0000
         Capabilities: [90] Subsystem: Dell Unknown device 
[1028:01da]
         Capabilities: [a0] Power Management version 2
                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 5 [8086:2847] (rev 02) (prog-if 00 [Normal decode])
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR+ FastB2B-
         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0, Cache Line Size: 64 bytes
         Bus: primary\0, secondary\x02, subordinate\x02, sec-latency=0
         Memory behind bridge: dfb00000-dfbfffff
         Secondary status: 66MHz- FastB2B- ParErr- DEVSELúst 
 >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
         BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- 
FastB2B-
         Capabilities: [40] Express Root Port (Slot+) IRQ 0
                 Device: Supported: MaxPayload 128 bytes, 
PhantFunc 0, ExtTag-
                 Device: Latency L0s unlimited, L1 unlimited
                 Device: Errors: Correctable+ Non-Fatal+ Fatal+ 
Unsupported+
                 Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                 Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                 Link: Supported Speed 2.5Gb/s, Width x1, ASPM 
L0s, Port 5
                 Link: Latency L0s <256ns, L1 <4us
                 Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
                 Link: Speed 2.5Gb/s, Width x1
                 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- 
HotPlug+ Surpise+
                 Slot: Number 0, PowerLimit 10.000000
                 Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- 
CmdCplt- HPIrq-
                 Slot: AttnInd Unknown, PwrInd Unknown, Power-
                 Root: Correctable- Non-Fatal- Fatal- PME-
         Capabilities: [80] Message Signalled Interrupts: Mask- 
64bit- Queue=0/0 Enable-
                 Address: 00000000  Data: 0000
         Capabilities: [90] Subsystem: Dell Unknown device 
[1028:01da]
         Capabilities: [a0] Power Management version 2
                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #1 [8086:2830] (rev 02) (prog-if 00 
[UHCI])
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR- FastB2B-
         Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Interrupt: pin A routed to IRQ 18
         Region 4: I/O ports at ff80 [size2]

00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #2 [8086:2831] (rev 02) (prog-if 00 
[UHCI])
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR- FastB2B-
         Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Interrupt: pin B routed to IRQ 17
         Region 4: I/O ports at ff60 [size2]

00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #3 [8086:2832] (rev 02) (prog-if 00 
[UHCI])
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR- FastB2B-
         Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Interrupt: pin C routed to IRQ 19
         Region 4: I/O ports at ff40 [size2]

00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB2 EHCI Controller #1 [8086:2836] (rev 02) (prog-if 20 
[EHCI])
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR+ FastB2B-
         Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Interrupt: pin A routed to IRQ 18
         Region 0: Memory at ff980800 (32-bit, non-prefetchable) 
[size=1K]
         Capabilities: [50] Power Management version 2
                 Flags: PMEClk- DSI- D1- D2- AuxCurrent75mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
         Capabilities: [58] Debug port

00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge 
[8086:244e] (rev f2) (prog-if 01 [Subtractive decode])
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR+ FastB2B-
         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Bus: primary\0, secondary\x03, subordinate\x03, 
sec-latency2
         Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
         BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- 
FastB2B-
         Capabilities: [50] Subsystem: Dell Unknown device 
[1028:01da]

00:1f.0 ISA bridge [0601]: Intel Corporation 82801HB/HR (ICH8/R) 
LPC Interface Controller [8086:2810] (rev 02)
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR+ FastB2B-
         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Capabilities: [e0] Vendor Specific Information

00:1f.2 IDE interface [0101]: Intel Corporation 82801H (ICH8 
Family) 4 port SATA IDE Controller [8086:2820] (rev 02) (prog-if 
8f [Master SecP SecO PriP PriO])
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR- FastB2B-
         Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Interrupt: pin C routed to IRQ 21
         Region 0: I/O ports at fe00 [size=8]
         Region 1: I/O ports at fe10 [size=4]
         Region 2: I/O ports at fe20 [size=8]
         Region 3: I/O ports at fe30 [size=4]
         Region 4: I/O ports at fec0 [size\x16]
         Region 5: I/O ports at ecc0 [size\x16]
         Capabilities: [70] Power Management version 3
                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot+,D3cold-)
                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1f.3 SMBus [0c05]: Intel Corporation 82801H (ICH8 Family) 
SMBus Controller [8086:283e] (rev 02)
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR+ FastB2B-
         Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Interrupt: pin C routed to IRQ 21
         Region 0: Memory at dfdfbb00 (32-bit, non-prefetchable) 
[size%6]
         Region 4: I/O ports at ece0 [size2]

00:1f.5 IDE interface [0101]: Intel Corporation 82801H (ICH8 
Family) 2 port SATA IDE Controller [8086:2825] (rev 02) (prog-if 
85 [Master SecO PriO])
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR- FastB2B-
         Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Interrupt: pin C routed to IRQ 21
         Region 0: I/O ports at fe40 [size=8]
         Region 1: I/O ports at fe50 [size=4]
         Region 2: I/O ports at fe60 [size=8]
         Region 3: I/O ports at fe70 [size=4]
         Region 4: I/O ports at fed0 [size\x16]
         Region 5: I/O ports at ecd0 [size\x16]
         Capabilities: [70] Power Management version 3
                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot+,D3cold-)
                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-

02:00.0 Ethernet controller [0200]: Broadcom Corporation 
NetXtreme BCM5754 Gigabit Ethernet PCI Express [14e4:167a] (rev 02)
         Subsystem: Dell Unknown device [1028:01da]
         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- 
VGASnoop- ParErr- Stepping- SERR- FastB2B-
         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0, Cache Line Size: 64 bytes
         Interrupt: pin A routed to IRQ 16
         Region 0: Memory at dfbf0000 (64-bit, non-prefetchable) 
[sizedK]
         Capabilities: [48] Power Management version 3
                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot+,D3cold+)
                 Status: D0 PME-Enable- DSel=0 DScale=1 PME-
         Capabilities: [50] Vital Product Data
         Capabilities: [58] Vendor Specific Information
         Capabilities: [e8] Message Signalled Interrupts: Mask- 
64bit+ Queue=0/0 Enable-
                 Address: 270010008484420c  Data: 087e
         Capabilities: [d0] Express Endpoint IRQ 0
                 Device: Supported: MaxPayload 128 bytes, 
PhantFunc 0, ExtTag+
                 Device: Latency L0s <4us, L1 unlimited
                 Device: AtnBtn- AtnInd- PwrInd-
                 Device: Errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
                 Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                 Device: MaxPayload 128 bytes, MaxReadReq 4096 bytes
                 Link: Supported Speed 2.5Gb/s, Width x1, ASPM 
L0s, Port 0
                 Link: Latency L0s <4us, L1 <64us
                 Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
                 Link: Speed 2.5Gb/s, Width x1





sudo sensors-detect
# sensors-detect revision 4609 (2007-07-14 09:28:39 -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 82801H ICH8

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
Do you want to load `i2c-dev' now? (YES/no):
Module loaded successfully.

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 ece0 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              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 `Silicon Integrated Systems SIS5595'...         No
Probing for `VIA VT82C686 Integrated Sensors'...            No
Probing for `VIA VT8231 Integrated Sensors'...              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 unknown chip with ID 0x830f
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 CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no):
AMD K8 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)

I will now generate the commands needed to load the required modules.
Just press ENTER to continue:

To make the sensors modules behave correctly, add these lines to
/etc/modules:

#----cut here----
# Chip drivers
coretemp
#----cut here----


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

Re: [lm-sensors] dme1737 module

[Juerg Haefliger]

Hi Werner,


On Dec 19, 2007 2:24 PM, Werner Goebl <werner.goebl@mail.mcgill.ca> wrote:
>
> > Shoot, the register values didn't change. So we're looking at the
> > wrong thing here. Darn...
> >
> > Please run 'isadump -k 0x55 0x2e 0x2f 0x8' and 'isadump -k 0x55 0x2e
> > 0x2f 0x9' and post the output. We have to look at a different logical
> > device.
> > And please also post the output of 'lspci -vv -nn' and the full output
> > of 'sensors-detect'.
> >
> > ...juerg
>
> Here is all the listings!
> Best
> Werner
>
>
> sudo isadump -k 0x55 0x2e 0x2f 0x8
> [sudo] password for werner:
> 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]
>       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 00 00
> 20: 83 0f 38 00 04 00 2e 00 00 00 00 00 10 00 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 00 00 00 00 00 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 ff ff ff ff ff ff
> 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 00 00 00 00 00 00 00 00


No IO space configured.


>   sudo isadump -k 0x55 0x2e 0x2f 0x9
> WARNING! Running this program can cause system crashes, data loss
> and worse!
> I will probe address register 0x2e and data register 0x2f.
> Probing bank 9 using bank register 0x07.
> Continue? [Y/n]
>       0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00: 00 00 00 00 00 00 00 09 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: 83 0f 38 00 04 00 2e 00 00 00 00 00 10 00 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 00 00 00 00 00 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 ff ff ff ff ff ff
> 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 00 00 00 00 00 00 00 00

No IO space configured either. So it looks like the SCH5514 doesn't
have any HW monitoring capabilities, unless it uses a different
logical device which is unlikely given that all the other SMSC
Super-IOs use one of 8, 9, or 0xa.


>
>
>
> sudo lspci -vv -nn
> 00:00.0 Host bridge [0600]: Intel Corporation 82Q963/Q965 Memory
> Controller Hub [8086:2990] (rev 02)
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>          Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSELúst
>  >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
>          Latency: 0
>          Capabilities: [e0] Vendor Specific Information
>
> 00:02.0 VGA compatible controller [0300]: Intel Corporation
> 82Q963/Q965 Integrated Graphics Controller [8086:2992] (rev 02)
> (prog-if 00 [VGA])
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>          Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSELúst
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0
>          Interrupt: pin A routed to IRQ 16
>          Region 0: Memory at dfe00000 (32-bit, non-prefetchable)
> [size=1M]
>          Region 2: Memory at c0000000 (64-bit, prefetchable)
> [size%6M]
>          Region 4: I/O ports at ecb8 [size=8]
>          Capabilities: [90] Message Signalled Interrupts: Mask-
> 64bit- Queue=0/0 Enable-
>                  Address: 00000000  Data: 0000
>          Capabilities: [d0] Power Management version 2
>                  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:02.1 Display controller [0380]: Intel Corporation 82Q963/Q965
> Integrated Graphics Controller [8086:2993] (rev 02)
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>          Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSELúst
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0
>          Region 0: Memory at dff00000 (32-bit, non-prefetchable)
> [size=1M]
>          Capabilities: [d0] Power Management version 2
>                  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8
> Family) USB UHCI Contoller #4 [8086:2834] (rev 02) (prog-if 00
> [UHCI])
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>          Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0
>          Interrupt: pin A routed to IRQ 16
>          Region 4: I/O ports at ff20 [size2]
>
> 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8
> Family) USB UHCI Controller #5 [8086:2835] (rev 02) (prog-if 00
> [UHCI])
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>          Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0
>          Interrupt: pin B routed to IRQ 17
>          Region 4: I/O ports at ff00 [size2]
>
> 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8
> Family) USB2 EHCI Controller #2 [8086:283a] (rev 02) (prog-if 20
> [EHCI])
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>          Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0
>          Interrupt: pin C routed to IRQ 20
>          Region 0: Memory at dfdfbc00 (32-bit, non-prefetchable)
> [size=1K]
>          Capabilities: [50] Power Management version 2
>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent75mA
> PME(D0+,D1-,D2-,D3hot+,D3cold+)
>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>          Capabilities: [58] Debug port
>
> 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8
> Family) HD Audio Controller [8086:284b] (rev 02)
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0, Cache Line Size: 64 bytes
>          Interrupt: pin A routed to IRQ 16
>          Region 0: Memory at dfdfc000 (64-bit, non-prefetchable)
> [size\x16K]
>          Capabilities: [50] Power Management version 2
>                  Flags: PMEClk- DSI- D1- D2- AuxCurrentUmA
> PME(D0+,D1-,D2-,D3hot+,D3cold+)
>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>          Capabilities: [60] Message Signalled Interrupts: Mask-
> 64bit+ Queue=0/0 Enable-
>                  Address: 0000000000000000  Data: 0000
>          Capabilities: [70] Express Unknown type IRQ 0
>                  Device: Supported: MaxPayload 128 bytes,
> PhantFunc 0, ExtTag-
>                  Device: Latency L0s <64ns, L1 <1us
>                  Device: Errors: Correctable- Non-Fatal- Fatal-
> Unsupported-
>                  Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
>                  Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
>                  Link: Supported Speed unknown, Width x0, ASPM
> unknown, Port 0
>                  Link: Latency L0s <64ns, L1 <1us
>                  Link: ASPM Disabled CommClk- ExtSynch-
>                  Link: Speed unknown, Width x0
>
> 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family)
> PCI Express Port 1 [8086:283f] (rev 02) (prog-if 00 [Normal decode])
>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0, Cache Line Size: 64 bytes
>          Bus: primary\0, secondary\x01, subordinate\x01, sec-latency=0
>          Memory behind bridge: dfc00000-dfcfffff
>          Secondary status: 66MHz- FastB2B- ParErr- DEVSELúst
>  >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
>          BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset-
> FastB2B-
>          Capabilities: [40] Express Root Port (Slot+) IRQ 0
>                  Device: Supported: MaxPayload 128 bytes,
> PhantFunc 0, ExtTag-
>                  Device: Latency L0s unlimited, L1 unlimited
>                  Device: Errors: Correctable+ Non-Fatal+ Fatal+
> Unsupported+
>                  Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
>                  Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
>                  Link: Supported Speed 2.5Gb/s, Width x1, ASPM
> L0s, Port 1
>                  Link: Latency L0s <256ns, L1 <4us
>                  Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
>                  Link: Speed 2.5Gb/s, Width x0
>                  Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd-
> HotPlug+ Surpise+
>                  Slot: Number 4, PowerLimit 10.000000
>                  Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet-
> CmdCplt- HPIrq-
>                  Slot: AttnInd Unknown, PwrInd Unknown, Power-
>                  Root: Correctable- Non-Fatal- Fatal- PME-
>          Capabilities: [80] Message Signalled Interrupts: Mask-
> 64bit- Queue=0/0 Enable-
>                  Address: 00000000  Data: 0000
>          Capabilities: [90] Subsystem: Dell Unknown device
> [1028:01da]
>          Capabilities: [a0] Power Management version 2
>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0+,D1-,D2-,D3hot+,D3cold+)
>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family)
> PCI Express Port 5 [8086:2847] (rev 02) (prog-if 00 [Normal decode])
>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0, Cache Line Size: 64 bytes
>          Bus: primary\0, secondary\x02, subordinate\x02, sec-latency=0
>          Memory behind bridge: dfb00000-dfbfffff
>          Secondary status: 66MHz- FastB2B- ParErr- DEVSELúst
>  >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
>          BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset-
> FastB2B-
>          Capabilities: [40] Express Root Port (Slot+) IRQ 0
>                  Device: Supported: MaxPayload 128 bytes,
> PhantFunc 0, ExtTag-
>                  Device: Latency L0s unlimited, L1 unlimited
>                  Device: Errors: Correctable+ Non-Fatal+ Fatal+
> Unsupported+
>                  Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
>                  Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
>                  Link: Supported Speed 2.5Gb/s, Width x1, ASPM
> L0s, Port 5
>                  Link: Latency L0s <256ns, L1 <4us
>                  Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
>                  Link: Speed 2.5Gb/s, Width x1
>                  Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd-
> HotPlug+ Surpise+
>                  Slot: Number 0, PowerLimit 10.000000
>                  Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet-
> CmdCplt- HPIrq-
>                  Slot: AttnInd Unknown, PwrInd Unknown, Power-
>                  Root: Correctable- Non-Fatal- Fatal- PME-
>          Capabilities: [80] Message Signalled Interrupts: Mask-
> 64bit- Queue=0/0 Enable-
>                  Address: 00000000  Data: 0000
>          Capabilities: [90] Subsystem: Dell Unknown device
> [1028:01da]
>          Capabilities: [a0] Power Management version 2
>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0+,D1-,D2-,D3hot+,D3cold+)
>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8
> Family) USB UHCI Controller #1 [8086:2830] (rev 02) (prog-if 00
> [UHCI])
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>          Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0
>          Interrupt: pin A routed to IRQ 18
>          Region 4: I/O ports at ff80 [size2]
>
> 00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8
> Family) USB UHCI Controller #2 [8086:2831] (rev 02) (prog-if 00
> [UHCI])
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>          Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0
>          Interrupt: pin B routed to IRQ 17
>          Region 4: I/O ports at ff60 [size2]
>
> 00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8
> Family) USB UHCI Controller #3 [8086:2832] (rev 02) (prog-if 00
> [UHCI])
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>          Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0
>          Interrupt: pin C routed to IRQ 19
>          Region 4: I/O ports at ff40 [size2]
>
> 00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8
> Family) USB2 EHCI Controller #1 [8086:2836] (rev 02) (prog-if 20
> [EHCI])
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>          Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0
>          Interrupt: pin A routed to IRQ 18
>          Region 0: Memory at ff980800 (32-bit, non-prefetchable)
> [size=1K]
>          Capabilities: [50] Power Management version 2
>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent75mA
> PME(D0+,D1-,D2-,D3hot+,D3cold+)
>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>          Capabilities: [58] Debug port
>
> 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge
> [8086:244e] (rev f2) (prog-if 01 [Subtractive decode])
>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0
>          Bus: primary\0, secondary\x03, subordinate\x03,
> sec-latency2
>          Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium
>  >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
>          BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset-
> FastB2B-
>          Capabilities: [50] Subsystem: Dell Unknown device
> [1028:01da]
>
> 00:1f.0 ISA bridge [0601]: Intel Corporation 82801HB/HR (ICH8/R)
> LPC Interface Controller [8086:2810] (rev 02)
>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0
>          Capabilities: [e0] Vendor Specific Information
>
> 00:1f.2 IDE interface [0101]: Intel Corporation 82801H (ICH8
> Family) 4 port SATA IDE Controller [8086:2820] (rev 02) (prog-if
> 8f [Master SecP SecO PriP PriO])
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>          Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0
>          Interrupt: pin C routed to IRQ 21
>          Region 0: I/O ports at fe00 [size=8]
>          Region 1: I/O ports at fe10 [size=4]
>          Region 2: I/O ports at fe20 [size=8]
>          Region 3: I/O ports at fe30 [size=4]
>          Region 4: I/O ports at fec0 [size\x16]
>          Region 5: I/O ports at ecc0 [size\x16]
>          Capabilities: [70] Power Management version 3
>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot+,D3cold-)
>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:1f.3 SMBus [0c05]: Intel Corporation 82801H (ICH8 Family)
> SMBus Controller [8086:283e] (rev 02)
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>          Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Interrupt: pin C routed to IRQ 21
>          Region 0: Memory at dfdfbb00 (32-bit, non-prefetchable)
> [size%6]
>          Region 4: I/O ports at ece0 [size2]


The ICH8 SMBus is visible. That was one of my other concerns. On some
machines, the ICH8 SMBus is hidden and sensors-detect won't find HW
monitor devices attached to it. That's not the case for your system
though.


> 00:1f.5 IDE interface [0101]: Intel Corporation 82801H (ICH8
> Family) 2 port SATA IDE Controller [8086:2825] (rev 02) (prog-if
> 85 [Master SecO PriO])
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>          Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0
>          Interrupt: pin C routed to IRQ 21
>          Region 0: I/O ports at fe40 [size=8]
>          Region 1: I/O ports at fe50 [size=4]
>          Region 2: I/O ports at fe60 [size=8]
>          Region 3: I/O ports at fe70 [size=4]
>          Region 4: I/O ports at fed0 [size\x16]
>          Region 5: I/O ports at ecd0 [size\x16]
>          Capabilities: [70] Power Management version 3
>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot+,D3cold-)
>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 02:00.0 Ethernet controller [0200]: Broadcom Corporation
> NetXtreme BCM5754 Gigabit Ethernet PCI Express [14e4:167a] (rev 02)
>          Subsystem: Dell Unknown device [1028:01da]
>          Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 0, Cache Line Size: 64 bytes
>          Interrupt: pin A routed to IRQ 16
>          Region 0: Memory at dfbf0000 (64-bit, non-prefetchable)
> [sizedK]
>          Capabilities: [48] Power Management version 3
>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot+,D3cold+)
>                  Status: D0 PME-Enable- DSel=0 DScale=1 PME-
>          Capabilities: [50] Vital Product Data
>          Capabilities: [58] Vendor Specific Information
>          Capabilities: [e8] Message Signalled Interrupts: Mask-
> 64bit+ Queue=0/0 Enable-
>                  Address: 270010008484420c  Data: 087e
>          Capabilities: [d0] Express Endpoint IRQ 0
>                  Device: Supported: MaxPayload 128 bytes,
> PhantFunc 0, ExtTag+
>                  Device: Latency L0s <4us, L1 unlimited
>                  Device: AtnBtn- AtnInd- PwrInd-
>                  Device: Errors: Correctable- Non-Fatal- Fatal-
> Unsupported-
>                  Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
>                  Device: MaxPayload 128 bytes, MaxReadReq 4096 bytes
>                  Link: Supported Speed 2.5Gb/s, Width x1, ASPM
> L0s, Port 0
>                  Link: Latency L0s <4us, L1 <64us
>                  Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
>                  Link: Speed 2.5Gb/s, Width x1
>
>
>
>
>
> sudo sensors-detect
> # sensors-detect revision 4609 (2007-07-14 09:28:39 -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 82801H ICH8
>
> We will now try to load each adapter module in turn.
> Module `i2c-i801' already loaded.
> If you have undetectable or unsupported adapters, you can have them
> scanned by manually loading the modules before running this script.
>
> To continue, we need module `i2c-dev' to be loaded.
> Do you want to load `i2c-dev' now? (YES/no):
> Module loaded successfully.
>
> 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 ece0 (i2c-0)
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x44
> Probing for `Maxim MAX6633/MAX6634/MAX6635'...              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 `Silicon Integrated Systems SIS5595'...         No
> Probing for `VIA VT82C686 Integrated Sensors'...            No
> Probing for `VIA VT8231 Integrated Sensors'...              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 unknown chip with ID 0x830f
> 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

The SCH5514 really seems to be the only device. It's possible that
your system uses the ICH8 built-in HW monitoring features instead of
relying on a dedicated chip. We don't support that (yet) due to lack
of technical information. The only other suggestion I can make is to
run Speedfan under Windows to see if it can find something but I doubt
it. You can also load the acpi drivers (thermal and fan) and check if
you get some info from them via /proc/acpi/.

Sorry looks like you're out of luck.
...juerg




> Some CPUs or memory controllers may also contain embedded sensors.
> Do you want to scan for them? (YES/no):
> AMD K8 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)
>
> I will now generate the commands needed to load the required modules.
> Just press ENTER to continue:
>
> To make the sensors modules behave correctly, add these lines to
> /etc/modules:
>
> #----cut here----
> # Chip drivers
> coretemp
> #----cut here----
>
>

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

Re: [lm-sensors] dme1737 module

[Werner Goebl]

Hi Juerg,

Juerg Haefliger wrote:
> Hi Werner,
> 
> 
> On Dec 19, 2007 2:24 PM, Werner Goebl <werner.goebl@mail.mcgill.ca> wrote:
>>> Shoot, the register values didn't change. So we're looking at the
>>> wrong thing here. Darn...
>>>
>>> Please run 'isadump -k 0x55 0x2e 0x2f 0x8' and 'isadump -k 0x55 0x2e
>>> 0x2f 0x9' and post the output. We have to look at a different logical
>>> device.
>>> And please also post the output of 'lspci -vv -nn' and the full output
>>> of 'sensors-detect'.
>>>
>>> ...juerg
>> Here is all the listings!
>> Best
>> Werner
>>
>>
>> sudo isadump -k 0x55 0x2e 0x2f 0x8
>> [sudo] password for werner:
>> 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]
>>       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 00 00
>> 20: 83 0f 38 00 04 00 2e 00 00 00 00 00 10 00 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 00 00 00 00 00 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 ff ff ff ff ff ff
>> 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 00 00 00 00 00 00 00 00
> 
> 
> No IO space configured.
> 
> 
>>   sudo isadump -k 0x55 0x2e 0x2f 0x9
>> WARNING! Running this program can cause system crashes, data loss
>> and worse!
>> I will probe address register 0x2e and data register 0x2f.
>> Probing bank 9 using bank register 0x07.
>> Continue? [Y/n]
>>       0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>> 00: 00 00 00 00 00 00 00 09 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: 83 0f 38 00 04 00 2e 00 00 00 00 00 10 00 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 00 00 00 00 00 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 ff ff ff ff ff ff
>> 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 00 00 00 00 00 00 00 00
> 
> No IO space configured either. So it looks like the SCH5514 doesn't
> have any HW monitoring capabilities, unless it uses a different
> logical device which is unlikely given that all the other SMSC
> Super-IOs use one of 8, 9, or 0xa.
> 
> 
>>
>>
>> sudo lspci -vv -nn
>> 00:00.0 Host bridge [0600]: Intel Corporation 82Q963/Q965 Memory
>> Controller Hub [8086:2990] (rev 02)
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>>          Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSELúst
>>  >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
>>          Latency: 0
>>          Capabilities: [e0] Vendor Specific Information
>>
>> 00:02.0 VGA compatible controller [0300]: Intel Corporation
>> 82Q963/Q965 Integrated Graphics Controller [8086:2992] (rev 02)
>> (prog-if 00 [VGA])
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>          Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSELúst
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Interrupt: pin A routed to IRQ 16
>>          Region 0: Memory at dfe00000 (32-bit, non-prefetchable)
>> [size=1M]
>>          Region 2: Memory at c0000000 (64-bit, prefetchable)
>> [size%6M]
>>          Region 4: I/O ports at ecb8 [size=8]
>>          Capabilities: [90] Message Signalled Interrupts: Mask-
>> 64bit- Queue=0/0 Enable-
>>                  Address: 00000000  Data: 0000
>>          Capabilities: [d0] Power Management version 2
>>                  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
>> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>>
>> 00:02.1 Display controller [0380]: Intel Corporation 82Q963/Q965
>> Integrated Graphics Controller [8086:2993] (rev 02)
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>          Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSELúst
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Region 0: Memory at dff00000 (32-bit, non-prefetchable)
>> [size=1M]
>>          Capabilities: [d0] Power Management version 2
>>                  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
>> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>>
>> 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8
>> Family) USB UHCI Contoller #4 [8086:2834] (rev 02) (prog-if 00
>> [UHCI])
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>          Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Interrupt: pin A routed to IRQ 16
>>          Region 4: I/O ports at ff20 [size2]
>>
>> 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8
>> Family) USB UHCI Controller #5 [8086:2835] (rev 02) (prog-if 00
>> [UHCI])
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>          Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Interrupt: pin B routed to IRQ 17
>>          Region 4: I/O ports at ff00 [size2]
>>
>> 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8
>> Family) USB2 EHCI Controller #2 [8086:283a] (rev 02) (prog-if 20
>> [EHCI])
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>>          Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Interrupt: pin C routed to IRQ 20
>>          Region 0: Memory at dfdfbc00 (32-bit, non-prefetchable)
>> [size=1K]
>>          Capabilities: [50] Power Management version 2
>>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent75mA
>> PME(D0+,D1-,D2-,D3hot+,D3cold+)
>>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>>          Capabilities: [58] Debug port
>>
>> 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8
>> Family) HD Audio Controller [8086:284b] (rev 02)
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>>          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0, Cache Line Size: 64 bytes
>>          Interrupt: pin A routed to IRQ 16
>>          Region 0: Memory at dfdfc000 (64-bit, non-prefetchable)
>> [size\x16K]
>>          Capabilities: [50] Power Management version 2
>>                  Flags: PMEClk- DSI- D1- D2- AuxCurrentUmA
>> PME(D0+,D1-,D2-,D3hot+,D3cold+)
>>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>>          Capabilities: [60] Message Signalled Interrupts: Mask-
>> 64bit+ Queue=0/0 Enable-
>>                  Address: 0000000000000000  Data: 0000
>>          Capabilities: [70] Express Unknown type IRQ 0
>>                  Device: Supported: MaxPayload 128 bytes,
>> PhantFunc 0, ExtTag-
>>                  Device: Latency L0s <64ns, L1 <1us
>>                  Device: Errors: Correctable- Non-Fatal- Fatal-
>> Unsupported-
>>                  Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
>>                  Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
>>                  Link: Supported Speed unknown, Width x0, ASPM
>> unknown, Port 0
>>                  Link: Latency L0s <64ns, L1 <1us
>>                  Link: ASPM Disabled CommClk- ExtSynch-
>>                  Link: Speed unknown, Width x0
>>
>> 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family)
>> PCI Express Port 1 [8086:283f] (rev 02) (prog-if 00 [Normal decode])
>>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>>          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0, Cache Line Size: 64 bytes
>>          Bus: primary\0, secondary\x01, subordinate\x01, sec-latency=0
>>          Memory behind bridge: dfc00000-dfcfffff
>>          Secondary status: 66MHz- FastB2B- ParErr- DEVSELúst
>>  >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
>>          BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset-
>> FastB2B-
>>          Capabilities: [40] Express Root Port (Slot+) IRQ 0
>>                  Device: Supported: MaxPayload 128 bytes,
>> PhantFunc 0, ExtTag-
>>                  Device: Latency L0s unlimited, L1 unlimited
>>                  Device: Errors: Correctable+ Non-Fatal+ Fatal+
>> Unsupported+
>>                  Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
>>                  Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
>>                  Link: Supported Speed 2.5Gb/s, Width x1, ASPM
>> L0s, Port 1
>>                  Link: Latency L0s <256ns, L1 <4us
>>                  Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
>>                  Link: Speed 2.5Gb/s, Width x0
>>                  Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd-
>> HotPlug+ Surpise+
>>                  Slot: Number 4, PowerLimit 10.000000
>>                  Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet-
>> CmdCplt- HPIrq-
>>                  Slot: AttnInd Unknown, PwrInd Unknown, Power-
>>                  Root: Correctable- Non-Fatal- Fatal- PME-
>>          Capabilities: [80] Message Signalled Interrupts: Mask-
>> 64bit- Queue=0/0 Enable-
>>                  Address: 00000000  Data: 0000
>>          Capabilities: [90] Subsystem: Dell Unknown device
>> [1028:01da]
>>          Capabilities: [a0] Power Management version 2
>>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
>> PME(D0+,D1-,D2-,D3hot+,D3cold+)
>>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>>
>> 00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family)
>> PCI Express Port 5 [8086:2847] (rev 02) (prog-if 00 [Normal decode])
>>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>>          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0, Cache Line Size: 64 bytes
>>          Bus: primary\0, secondary\x02, subordinate\x02, sec-latency=0
>>          Memory behind bridge: dfb00000-dfbfffff
>>          Secondary status: 66MHz- FastB2B- ParErr- DEVSELúst
>>  >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
>>          BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset-
>> FastB2B-
>>          Capabilities: [40] Express Root Port (Slot+) IRQ 0
>>                  Device: Supported: MaxPayload 128 bytes,
>> PhantFunc 0, ExtTag-
>>                  Device: Latency L0s unlimited, L1 unlimited
>>                  Device: Errors: Correctable+ Non-Fatal+ Fatal+
>> Unsupported+
>>                  Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
>>                  Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
>>                  Link: Supported Speed 2.5Gb/s, Width x1, ASPM
>> L0s, Port 5
>>                  Link: Latency L0s <256ns, L1 <4us
>>                  Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
>>                  Link: Speed 2.5Gb/s, Width x1
>>                  Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd-
>> HotPlug+ Surpise+
>>                  Slot: Number 0, PowerLimit 10.000000
>>                  Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet-
>> CmdCplt- HPIrq-
>>                  Slot: AttnInd Unknown, PwrInd Unknown, Power-
>>                  Root: Correctable- Non-Fatal- Fatal- PME-
>>          Capabilities: [80] Message Signalled Interrupts: Mask-
>> 64bit- Queue=0/0 Enable-
>>                  Address: 00000000  Data: 0000
>>          Capabilities: [90] Subsystem: Dell Unknown device
>> [1028:01da]
>>          Capabilities: [a0] Power Management version 2
>>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
>> PME(D0+,D1-,D2-,D3hot+,D3cold+)
>>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>>
>> 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8
>> Family) USB UHCI Controller #1 [8086:2830] (rev 02) (prog-if 00
>> [UHCI])
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>          Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Interrupt: pin A routed to IRQ 18
>>          Region 4: I/O ports at ff80 [size2]
>>
>> 00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8
>> Family) USB UHCI Controller #2 [8086:2831] (rev 02) (prog-if 00
>> [UHCI])
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>          Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Interrupt: pin B routed to IRQ 17
>>          Region 4: I/O ports at ff60 [size2]
>>
>> 00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8
>> Family) USB UHCI Controller #3 [8086:2832] (rev 02) (prog-if 00
>> [UHCI])
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>          Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Interrupt: pin C routed to IRQ 19
>>          Region 4: I/O ports at ff40 [size2]
>>
>> 00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8
>> Family) USB2 EHCI Controller #1 [8086:2836] (rev 02) (prog-if 20
>> [EHCI])
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>>          Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Interrupt: pin A routed to IRQ 18
>>          Region 0: Memory at ff980800 (32-bit, non-prefetchable)
>> [size=1K]
>>          Capabilities: [50] Power Management version 2
>>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent75mA
>> PME(D0+,D1-,D2-,D3hot+,D3cold+)
>>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>>          Capabilities: [58] Debug port
>>
>> 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge
>> [8086:244e] (rev f2) (prog-if 01 [Subtractive decode])
>>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>>          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Bus: primary\0, secondary\x03, subordinate\x03,
>> sec-latency2
>>          Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium
>>  >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
>>          BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset-
>> FastB2B-
>>          Capabilities: [50] Subsystem: Dell Unknown device
>> [1028:01da]
>>
>> 00:1f.0 ISA bridge [0601]: Intel Corporation 82801HB/HR (ICH8/R)
>> LPC Interface Controller [8086:2810] (rev 02)
>>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>>          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Capabilities: [e0] Vendor Specific Information
>>
>> 00:1f.2 IDE interface [0101]: Intel Corporation 82801H (ICH8
>> Family) 4 port SATA IDE Controller [8086:2820] (rev 02) (prog-if
>> 8f [Master SecP SecO PriP PriO])
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>          Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Interrupt: pin C routed to IRQ 21
>>          Region 0: I/O ports at fe00 [size=8]
>>          Region 1: I/O ports at fe10 [size=4]
>>          Region 2: I/O ports at fe20 [size=8]
>>          Region 3: I/O ports at fe30 [size=4]
>>          Region 4: I/O ports at fec0 [size\x16]
>>          Region 5: I/O ports at ecc0 [size\x16]
>>          Capabilities: [70] Power Management version 3
>>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
>> PME(D0-,D1-,D2-,D3hot+,D3cold-)
>>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>>
>> 00:1f.3 SMBus [0c05]: Intel Corporation 82801H (ICH8 Family)
>> SMBus Controller [8086:283e] (rev 02)
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>>          Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Interrupt: pin C routed to IRQ 21
>>          Region 0: Memory at dfdfbb00 (32-bit, non-prefetchable)
>> [size%6]
>>          Region 4: I/O ports at ece0 [size2]
> 
> 
> The ICH8 SMBus is visible. That was one of my other concerns. On some
> machines, the ICH8 SMBus is hidden and sensors-detect won't find HW
> monitor devices attached to it. That's not the case for your system
> though.
> 
> 
>> 00:1f.5 IDE interface [0101]: Intel Corporation 82801H (ICH8
>> Family) 2 port SATA IDE Controller [8086:2825] (rev 02) (prog-if
>> 85 [Master SecO PriO])
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>          Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Interrupt: pin C routed to IRQ 21
>>          Region 0: I/O ports at fe40 [size=8]
>>          Region 1: I/O ports at fe50 [size=4]
>>          Region 2: I/O ports at fe60 [size=8]
>>          Region 3: I/O ports at fe70 [size=4]
>>          Region 4: I/O ports at fed0 [size\x16]
>>          Region 5: I/O ports at ecd0 [size\x16]
>>          Capabilities: [70] Power Management version 3
>>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
>> PME(D0-,D1-,D2-,D3hot+,D3cold-)
>>                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>>
>> 02:00.0 Ethernet controller [0200]: Broadcom Corporation
>> NetXtreme BCM5754 Gigabit Ethernet PCI Express [14e4:167a] (rev 02)
>>          Subsystem: Dell Unknown device [1028:01da]
>>          Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
>> VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELúst
>>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0, Cache Line Size: 64 bytes
>>          Interrupt: pin A routed to IRQ 16
>>          Region 0: Memory at dfbf0000 (64-bit, non-prefetchable)
>> [sizedK]
>>          Capabilities: [48] Power Management version 3
>>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
>> PME(D0-,D1-,D2-,D3hot+,D3cold+)
>>                  Status: D0 PME-Enable- DSel=0 DScale=1 PME-
>>          Capabilities: [50] Vital Product Data
>>          Capabilities: [58] Vendor Specific Information
>>          Capabilities: [e8] Message Signalled Interrupts: Mask-
>> 64bit+ Queue=0/0 Enable-
>>                  Address: 270010008484420c  Data: 087e
>>          Capabilities: [d0] Express Endpoint IRQ 0
>>                  Device: Supported: MaxPayload 128 bytes,
>> PhantFunc 0, ExtTag+
>>                  Device: Latency L0s <4us, L1 unlimited
>>                  Device: AtnBtn- AtnInd- PwrInd-
>>                  Device: Errors: Correctable- Non-Fatal- Fatal-
>> Unsupported-
>>                  Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
>>                  Device: MaxPayload 128 bytes, MaxReadReq 4096 bytes
>>                  Link: Supported Speed 2.5Gb/s, Width x1, ASPM
>> L0s, Port 0
>>                  Link: Latency L0s <4us, L1 <64us
>>                  Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
>>                  Link: Speed 2.5Gb/s, Width x1
>>
>>
>>
>>
>>
>> sudo sensors-detect
>> # sensors-detect revision 4609 (2007-07-14 09:28:39 -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 82801H ICH8
>>
>> We will now try to load each adapter module in turn.
>> Module `i2c-i801' already loaded.
>> If you have undetectable or unsupported adapters, you can have them
>> scanned by manually loading the modules before running this script.
>>
>> To continue, we need module `i2c-dev' to be loaded.
>> Do you want to load `i2c-dev' now? (YES/no):
>> Module loaded successfully.
>>
>> 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 ece0 (i2c-0)
>> Do you want to scan it? (YES/no/selectively):
>> Client found at address 0x44
>> Probing for `Maxim MAX6633/MAX6634/MAX6635'...              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 `Silicon Integrated Systems SIS5595'...         No
>> Probing for `VIA VT82C686 Integrated Sensors'...            No
>> Probing for `VIA VT8231 Integrated Sensors'...              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 unknown chip with ID 0x830f
>> 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
> 
> The SCH5514 really seems to be the only device. It's possible that
> your system uses the ICH8 built-in HW monitoring features instead of
> relying on a dedicated chip. We don't support that (yet) due to lack
> of technical information. The only other suggestion I can make is to
> run Speedfan under Windows to see if it can find something but I doubt
> it. You can also load the acpi drivers (thermal and fan) and check if
> you get some info from them via /proc/acpi/.
> 
> Sorry looks like you're out of luck.
> ...juerg

I see. I will try the thermal and fan option and let you know 
what I find. I don't have Windows on that machine, but it would 
be worth a try...

Thanks, in any case, for all your help!

Werner



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