All of lore.kernel.org
 help / color / mirror / Atom feed
* [lm-sensors] "No sensors found!" on Intel Entry Storage System
@ 2009-08-29  5:24 Tech2009
  2009-08-29  8:30 ` Hubert Kario
                   ` (13 more replies)
  0 siblings, 14 replies; 15+ messages in thread
From: Tech2009 @ 2009-08-29  5:24 UTC (permalink / raw)
  To: lm-sensors

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

I am using an x86 ethernet NAS device with a preloaded custom Linux
distribution.

I replaced the OS with a stock debian kernel from another machine.

Linux debian 2.6.26-2-686 #1 SMP Sun Jul 26 21:25:33 UTC 2009 i686
GNU/Linux.

Everything works minus the temperature sensors and LED control, both
worked using the original proprietary software interface.

The manual indicates the following fan controller is used:
SMSC SCH5027D


sensors-detect apparently finds this chip, and modprobe is able to load
the dme1737 driver. (see attachments). Syslog shows nothing exceptional.

"Probing for `SMSC SCH5027D-NW'...Success!
    (confidence 6, driver `dme1737')"

It's not until "sensors" that I see a problem:
"No sensors found! Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are."

Now my question is, is this user error, or is there an incompatibility
in the sensors program with the dme1737 driver?

I'm not afraid to try and debug the code myself if someone could set me
on the right path.



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

# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no): 
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7

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

We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.

Next adapter: SMBus I801 adapter at 0400 (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x2e
Probing for `Myson MTP008'...                               No
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM78-J'...              No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM85 or LM96000'...     No
Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... No
Probing for `SMSC EMC6D100, EMC6D101 or EMC6D102'...        No
Probing for `Analog Devices ADT7462'...                     No
Probing for `Analog Devices ADT7467 or ADT7468'...          No
Probing for `Analog Devices ADT7470'...                     No
Probing for `Analog Devices ADT7473'...                     No
Probing for `Analog Devices ADT7475'...                     No
Probing for `Analog Devices ADT7476'...                     No
Probing for `Andigilog aSC7611'...                          No
Probing for `Andigilog aSC7621'...                          No
Probing for `National Semiconductor LM87'...                No
Probing for `National Semiconductor LM93'...                No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83792D'...                            No
Probing for `Winbond W83793R/G'...                          No
Probing for `Winbond W83791SD'...                           No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG'...                          No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Winbond W83L786NR/NG/R/G'...                   No
Probing for `Winbond W83L785TS-S'...                        No
Probing for `Analog Devices ADM9240'...                     No
Probing for `Dallas Semiconductor DS1780'...                No
Probing for `National Semiconductor LM81'...                No
Probing for `Analog Devices ADM1026'...                     No
Probing for `Analog Devices ADM1025'...                     No
Probing for `Analog Devices ADM1029'...                     No
Probing for `Analog Devices ADM1030'...                     No
Probing for `Analog Devices ADM1031'...                     No
Probing for `Analog Devices ADM1022'...                     No
Probing for `Texas Instruments THMC50'...                   No
Probing for `Analog Devices ADM1028'...                     No
Probing for `ITE IT8712F'...                                No
Probing for `SMSC DME1737'...                               No
Probing for `SMSC SCH5027D-NW'...                           Success!
    (confidence 6, driver `dme1737')
Probing for `Fintek F75373S/SG'...                          No
Probing for `Fintek F75375S/SP'...                          No
Probing for `Fintek F75387SG/RG'...                         No
Probing for `Analog Devices ADM1024'...                     No
Probing for `Winbond W83791D'...                            No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 
Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no): Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM78-J' at 0x290...     No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     Yes
Found `SMSC SCH5027D-NW Super IO'                           
    (hardware monitoring capabilities accessible via SMBus only)

Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no): 
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD K10 thermal sensors...                                  No
Intel Core family thermal sensor...                         Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No

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

Driver `dme1737' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0400'
    Busdriver `i2c-i801', I2C address 0x2e
    Chip `SMSC SCH5027D-NW' (confidence: 6)

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 load everything that is needed, add this to /etc/modules:

#----cut here----
# I2C adapter drivers
i2c-i801
# Chip drivers
dme1737
coretemp
#----cut here----

Do you want to add these lines automatically? (yes/NO)


[-- Attachment #3: lsmod.txt --]
[-- Type: text/plain, Size: 1923 bytes --]

Module                  Size  Used by
dme1737                29020  0 
hwmon_vid               2720  1 dme1737
i2c_dev                 5256  0 
ipv6                  235364  16 
loop                   12748  0 
evdev                   8000  0 
snd_pcm                62596  0 
snd_timer              17800  1 snd_pcm
snd                    45604  2 snd_pcm,snd_timer
soundcore               6368  1 snd
snd_page_alloc          7816  1 snd_pcm
psmouse                32336  0 
serio_raw               4740  0 
pcspkr                  2432  0 
i2c_i801                7920  0 
i2c_core               19828  3 dme1737,i2c_dev,i2c_i801
rng_core                3940  0 
iTCO_wdt                9508  0 
button                  6096  0 
intel_agp              22556  1 
agpgart                28776  1 intel_agp
ext3                  105512  1 
jbd                    39444  1 ext3
mbcache                 7108  1 ext3
raid10                 18560  0 
raid456               117264  1 
async_xor               3520  1 raid456
async_memcpy            2304  1 raid456
async_tx                6316  3 raid456,async_xor,async_memcpy
xor                    14696  2 raid456,async_xor
raid1                  18016  0 
raid0                   6368  0 
multipath               6112  0 
linear                  4544  0 
md_mod                 67068  6 raid10,raid456,raid1,raid0,multipath,linear
sd_mod                 22200  10 
ahci                   23596  6 
ehci_hcd               28396  0 
sata_sil24             11812  0 
uhci_hcd               18672  0 
usbcore               118224  3 ehci_hcd,uhci_hcd
libata                140416  2 ahci,sata_sil24
scsi_mod              129324  2 sd_mod,libata
dock                    8304  1 libata
e1000e                 84612  0 
thermal                15228  0 
processor              32544  1 thermal
fan                     4164  0 
thermal_sys            10856  3 thermal,processor,fan


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

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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
@ 2009-08-29  8:30 ` Hubert Kario
  2009-08-29 16:03 ` Tech2009
                   ` (12 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Hubert Kario @ 2009-08-29  8:30 UTC (permalink / raw)
  To: lm-sensors

On Saturday 29 August 2009 07:24:13 Tech2009 wrote:
> I am using an x86 ethernet NAS device with a preloaded custom Linux
> distribution.
>
> I replaced the OS with a stock debian kernel from another machine.
>
> Linux debian 2.6.26-2-686 #1 SMP Sun Jul 26 21:25:33 UTC 2009 i686
> GNU/Linux.
>
> Everything works minus the temperature sensors and LED control, both
> worked using the original proprietary software interface.
>
> The manual indicates the following fan controller is used:
> SMSC SCH5027D
>
>
> sensors-detect apparently finds this chip, and modprobe is able to load
> the dme1737 driver. (see attachments). Syslog shows nothing exceptional.

and what shows dmesg?

>
> "Probing for `SMSC SCH5027D-NW'...Success!
>     (confidence 6, driver `dme1737')"
>
> It's not until "sensors" that I see a problem:
> "No sensors found! Make sure you loaded all the kernel drivers you need.
> Try sensors-detect to find out which these are."
>
> Now my question is, is this user error, or is there an incompatibility
> in the sensors program with the dme1737 driver?
>
> I'm not afraid to try and debug the code myself if someone could set me
> on the right path.
-- 
Hubert Kario
QBS - Quality Business Software
02-656 Warszawa, ul. Ksawerów 30/85
tel. +48 (22) 646-61-51, 646-74-24
www.qbs.com.pl

System Zarz±dzania Jako¶ci±
zgodny z norm± ISO 9001:2000

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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
  2009-08-29  8:30 ` Hubert Kario
@ 2009-08-29 16:03 ` Tech2009
  2009-09-01 18:26 ` Hubert Kario
                   ` (11 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Tech2009 @ 2009-08-29 16:03 UTC (permalink / raw)
  To: lm-sensors

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

> Message: 3
> Date: Sat, 29 Aug 2009 10:30:25 +0200
> From: Hubert Kario <hka@qbs.com.pl>
> Subject: Re: [lm-sensors] "No sensors found!" on Intel Entry Storage
> System SS4200
> To: lm-sensors@lm-sensors.org
> Message-ID: <200908291030.25637.hka@qbs.com.pl>
> Content-Type: text/plain;  charset="iso-8859-2"
> 

> 
> and what shows dmesg?


dmesg output after sensors-detect:
[ 1815.988770] i2c /dev entries driver

dmesg output after sensors:
(blank)


The bundled Linux image does not appear to use the dme1737 module or
lmsensors. The web interface loads several closed source libraries, and
I'm not sure how they access the hardware.

Is there something I should try to determine why sensors-detect sees the
chip but sensors does not?



[-- Attachment #2: lsmod orig.txt --]
[-- Type: text/plain, Size: 1634 bytes --]

Module                  Size  Used by    Not tainted
unix                   19988  96 
af_packet              11256  0 
hci_usb                10924  0 
via_rhine              18120  0 
vfat                    9200  0 
fat                    42332  1 vfat
usblp                  10464  0 
usb_storage            30644  0 
usbhid                 31876  0 
uhci_hcd               18248  0 
sr_mod                 11636  0 
sd_mod                 14864  4 
sata_via                6356  0 
sata_sil24             10756  0 
reiserfs              194180  0 
raid456               113168  1 
xor                    13720  1 raid456
raid1                  18080  0 
raid0                   6576  0 
r8169                  21880  0 
pcnet32                27892  0 
ohci_hcd               16212  0 
ntfs                   88172  0 
nasgpio                 7052  2 
mptspi                 11432  0 
mptscsih               17360  1 mptspi
mptbase                41900  2 mptspi,mptscsih
scsi_transport_spi     18448  1 mptspi
md_mod                 62772  4 raid456,raid1,raid0
isofs                  20916  0 
ext3                  106552  1 
jbd                    47736  1 ext3
ehci_hcd               23208  0 
usbcore               104556  8 hci_usb,usblp,usb_storage,usbhid,uhci_hcd,ohci_hcd,ehci_hcd
e1000                 106480  0 
e100                   28136  0 
dm_mod                 43884  14 
ata_piix               11448  0 
ahci                   15924  8 
libata                 83572  4 sata_via,sata_sil24,ata_piix,ahci
scsi_mod               74072  8 usb_storage,sr_mod,sd_mod,mptspi,mptscsih,scsi_transport_spi,ahci,libata


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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
  2009-08-29  8:30 ` Hubert Kario
  2009-08-29 16:03 ` Tech2009
@ 2009-09-01 18:26 ` Hubert Kario
  2009-09-01 21:27 ` Tech2009
                   ` (10 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Hubert Kario @ 2009-09-01 18:26 UTC (permalink / raw)
  To: lm-sensors

On Saturday 29 August 2009 18:03:36 Tech2009 wrote:
> > Message: 3
> > Date: Sat, 29 Aug 2009 10:30:25 +0200
> > From: Hubert Kario <hka@qbs.com.pl>
> > Subject: Re: [lm-sensors] "No sensors found!" on Intel Entry Storage
> > System SS4200
> > To: lm-sensors@lm-sensors.org
> > Message-ID: <200908291030.25637.hka@qbs.com.pl>
> > Content-Type: text/plain;  charset="iso-8859-2"
> >
> >
> >
> > and what shows dmesg?
>
> dmesg output after sensors-detect:
> [ 1815.988770] i2c /dev entries driver
>
> dmesg output after sensors:
> (blank)
So there doesn't appear to be any problem...
>
>
> The bundled Linux image does not appear to use the dme1737 module or
> lmsensors. The web interface loads several closed source libraries, and
> I'm not sure how they access the hardware.
They may access the hardware directly, is the web interface running as root?
Also, you may check /sys file system, look in /sys/bus/platform/drivers/ for 
it, the module may be compiled in in the bundled image
>
> Is there something I should try to determine why sensors-detect sees the
> chip but sensors does not?
you could try one of the parameters aviable for the module, for list of all of 
them, run:
modinfo dme1737


-- 
Hubert Kario
QBS - Quality Business Software
ul. Ksawerów 30/85
02-656 Warszawa
POLAND
tel. +48 (22) 646-61-51, 646-74-24
fax +48 (22) 646-61-50


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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
                   ` (2 preceding siblings ...)
  2009-09-01 18:26 ` Hubert Kario
@ 2009-09-01 21:27 ` Tech2009
  2009-09-02  0:23 ` Hubert Kario
                   ` (9 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Tech2009 @ 2009-09-01 21:27 UTC (permalink / raw)
  To: lm-sensors

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

Thank you for the suggestions.

I looked in sysfs on the factory distro, no sign of dme1737 there (see
attached). However there are other i2c devices not on my debian
install...you could be right about the direct port io, but without
disassembling the library it's hard to tell.

I tried loading dme1737 with force_start, but that made no difference
for me.

I'm going to have to determine whether the problem is with the sensors
program or the dme1737 driver. Is there a way to make the dme1737 module
dump out the debug information present in the source code?

I'm going to see if I can use the dme1737.c module source to read the
information via standard i2c calls in userland (ie i2ctools). If this
does work, I will be at a loss as to why the dme1737 module + sensors
program aren't working, but at least I'll have a viable alternative.

I will let you know if it works.


On Tue, 2009-09-01 at 20:26 +0200, Hubert Kario wrote:
> On Saturday 29 August 2009 18:03:36 Tech2009 wrote:
> > > Message: 3
> > > Date: Sat, 29 Aug 2009 10:30:25 +0200
> > > From: Hubert Kario <hka@qbs.com.pl>
> > > Subject: Re: [lm-sensors] "No sensors found!" on Intel Entry Storage
> > > System SS4200
> > > To: lm-sensors@lm-sensors.org
> > > Message-ID: <200908291030.25637.hka@qbs.com.pl>
> > > Content-Type: text/plain;  charset="iso-8859-2"
> > >
> > >
> > >
> > > and what shows dmesg?
> >
> > dmesg output after sensors-detect:
> > [ 1815.988770] i2c /dev entries driver
> >
> > dmesg output after sensors:
> > (blank)
> So there doesn't appear to be any problem...
> >
> >
> > The bundled Linux image does not appear to use the dme1737 module or
> > lmsensors. The web interface loads several closed source libraries, and
> > I'm not sure how they access the hardware.
> They may access the hardware directly, is the web interface running as root?
> Also, you may check /sys file system, look in /sys/bus/platform/drivers/ for 
> it, the module may be compiled in in the bundled image
> >
> > Is there something I should try to determine why sensors-detect sees the
> > chip but sensors does not?
> you could try one of the parameters aviable for the module, for list of all of 
> them, run:
> modinfo dme1737
> 
> 

[-- Attachment #2: modinfo dme1737.txt --]
[-- Type: text/plain, Size: 827 bytes --]

filename:       /lib/modules/2.6.26-2-686/kernel/drivers/hwmon/dme1737.ko
license:        GPL
description:    DME1737 sensors
author:         Juerg Haefliger <juergh@gmail.com>
depends:        i2c-core,hwmon-vid
vermagic:       2.6.26-2-686 SMP mod_unload modversions 686 
parm:           force_start:Force the chip to start monitoring inputs (bool)
parm:           force_id:Override the detected device ID (ushort)
parm:           force:List of adapter,address pairs to boldly assume to be present (array of short)
parm:           force_dme1737:List of adapter,address pairs which are unquestionably assumed to contain a `dme1737' chip (array of short)
parm:           probe:List of adapter,address pairs to scan additionally (array of short)
parm:           ignore:List of adapter,address pairs not to scan (array of short)


[-- Attachment #3: sys fs bus listing.txt --]
[-- Type: text/plain, Size: 7769 bytes --]

bus/usb
bus/usb/drivers
bus/usb/drivers/hci_usb
bus/usb/drivers/hci_usb/new_id
bus/usb/drivers/hci_usb/bind
bus/usb/drivers/hci_usb/unbind
bus/usb/drivers/hci_usb/module
bus/usb/drivers/usblp
bus/usb/drivers/usblp/new_id
bus/usb/drivers/usblp/bind
bus/usb/drivers/usblp/unbind
bus/usb/drivers/usblp/module
bus/usb/drivers/usb-storage
bus/usb/drivers/usb-storage/new_id
bus/usb/drivers/usb-storage/bind
bus/usb/drivers/usb-storage/unbind
bus/usb/drivers/usb-storage/module
bus/usb/drivers/usbhid
bus/usb/drivers/usbhid/new_id
bus/usb/drivers/usbhid/bind
bus/usb/drivers/usbhid/unbind
bus/usb/drivers/usbhid/module
bus/usb/drivers/hiddev
bus/usb/drivers/hiddev/new_id
bus/usb/drivers/hiddev/bind
bus/usb/drivers/hiddev/unbind
bus/usb/drivers/hiddev/module
bus/usb/drivers/usb
bus/usb/drivers/usb/usb5
bus/usb/drivers/usb/usb4
bus/usb/drivers/usb/usb3
bus/usb/drivers/usb/usb2
bus/usb/drivers/usb/usb1
bus/usb/drivers/usb/bind
bus/usb/drivers/usb/unbind
bus/usb/drivers/usb/module
bus/usb/drivers/hub
bus/usb/drivers/hub/5-0:1.0
bus/usb/drivers/hub/4-0:1.0
bus/usb/drivers/hub/3-0:1.0
bus/usb/drivers/hub/2-0:1.0
bus/usb/drivers/hub/1-0:1.0
bus/usb/drivers/hub/new_id
bus/usb/drivers/hub/bind
bus/usb/drivers/hub/unbind
bus/usb/drivers/hub/module
bus/usb/drivers/usbfs
bus/usb/drivers/usbfs/new_id
bus/usb/drivers/usbfs/bind
bus/usb/drivers/usbfs/unbind
bus/usb/drivers/usbfs/module
bus/usb/devices
bus/usb/devices/5-0:1.0
bus/usb/devices/usb5
bus/usb/devices/4-0:1.0
bus/usb/devices/usb4
bus/usb/devices/3-0:1.0
bus/usb/devices/usb3
bus/usb/devices/2-0:1.0
bus/usb/devices/usb2
bus/usb/devices/1-0:1.0
bus/usb/devices/usb1
bus/scsi
bus/scsi/drivers
bus/scsi/drivers/sr
bus/scsi/drivers/sr/bind
bus/scsi/drivers/sr/unbind
bus/scsi/drivers/sd
bus/scsi/drivers/sd/bind
bus/scsi/drivers/sd/unbind
bus/scsi/drivers/sd/3:0:0:0
bus/scsi/drivers/sd/2:0:0:0
bus/scsi/drivers/sd/1:0:0:0
bus/scsi/drivers/sd/0:0:0:0
bus/scsi/devices
bus/scsi/devices/3:0:0:0
bus/scsi/devices/2:0:0:0
bus/scsi/devices/1:0:0:0
bus/scsi/devices/0:0:0:0
bus/ide
bus/ide/drivers
bus/ide/drivers/ide-cdrom
bus/ide/drivers/ide-cdrom/bind
bus/ide/drivers/ide-cdrom/unbind
bus/ide/drivers/ide-disk
bus/ide/drivers/ide-disk/bind
bus/ide/drivers/ide-disk/unbind
bus/ide/drivers/ide-disk/0.0
bus/ide/devices
bus/ide/devices/0.0
bus/isa
bus/isa/drivers
bus/isa/devices
bus/bluetooth
bus/bluetooth/drivers
bus/bluetooth/devices
bus/i2c
bus/i2c/drivers
bus/i2c/drivers/dev_driver
bus/i2c/drivers/dev_driver/bind
bus/i2c/drivers/dev_driver/unbind
bus/i2c/drivers/i2c_adapter
bus/i2c/drivers/i2c_adapter/bind
bus/i2c/drivers/i2c_adapter/unbind
bus/i2c/devices
bus/serio
bus/serio/drivers
bus/serio/drivers/atkbd
bus/serio/drivers/atkbd/bind
bus/serio/drivers/atkbd/unbind
bus/serio/drivers/atkbd/bind_mode
bus/serio/drivers/atkbd/description
bus/serio/devices
bus/serio/devices/serio1
bus/serio/devices/serio0
bus/pnp
bus/pnp/drivers
bus/pnp/drivers/serial
bus/pnp/drivers/serial/bind
bus/pnp/drivers/serial/unbind
bus/pnp/drivers/serial/00:06
bus/pnp/drivers/system
bus/pnp/drivers/system/bind
bus/pnp/drivers/system/unbind
bus/pnp/drivers/system/00:0d
bus/pnp/drivers/system/00:0c
bus/pnp/drivers/system/00:0b
bus/pnp/drivers/system/00:0a
bus/pnp/drivers/system/00:08
bus/pnp/drivers/system/00:07
bus/pnp/drivers/system/00:01
bus/pnp/devices
bus/pnp/devices/00:0d
bus/pnp/devices/00:0c
bus/pnp/devices/00:0b
bus/pnp/devices/00:0a
bus/pnp/devices/00:09
bus/pnp/devices/00:08
bus/pnp/devices/00:07
bus/pnp/devices/00:06
bus/pnp/devices/00:05
bus/pnp/devices/00:04
bus/pnp/devices/00:03
bus/pnp/devices/00:02
bus/pnp/devices/00:01
bus/pnp/devices/00:00
bus/acpi
bus/acpi/drivers
bus/acpi/devices
bus/acpi/devices/acpi
bus/pci
bus/pci/drivers
bus/pci/drivers/via-rhine
bus/pci/drivers/via-rhine/new_id
bus/pci/drivers/via-rhine/bind
bus/pci/drivers/via-rhine/unbind
bus/pci/drivers/via-rhine/module
bus/pci/drivers/uhci_hcd
bus/pci/drivers/uhci_hcd/new_id
bus/pci/drivers/uhci_hcd/bind
bus/pci/drivers/uhci_hcd/unbind
bus/pci/drivers/uhci_hcd/module
bus/pci/drivers/uhci_hcd/0000:00:1d.3
bus/pci/drivers/uhci_hcd/0000:00:1d.2
bus/pci/drivers/uhci_hcd/0000:00:1d.1
bus/pci/drivers/uhci_hcd/0000:00:1d.0
bus/pci/drivers/sata_via
bus/pci/drivers/sata_via/new_id
bus/pci/drivers/sata_via/bind
bus/pci/drivers/sata_via/unbind
bus/pci/drivers/sata_via/module
bus/pci/drivers/sata_sil24
bus/pci/drivers/sata_sil24/new_id
bus/pci/drivers/sata_sil24/bind
bus/pci/drivers/sata_sil24/unbind
bus/pci/drivers/sata_sil24/module
bus/pci/drivers/sata_sil24/0000:02:00.0
bus/pci/drivers/r8169
bus/pci/drivers/r8169/new_id
bus/pci/drivers/r8169/bind
bus/pci/drivers/r8169/unbind
bus/pci/drivers/r8169/module
bus/pci/drivers/pcnet32
bus/pci/drivers/pcnet32/new_id
bus/pci/drivers/pcnet32/bind
bus/pci/drivers/pcnet32/unbind
bus/pci/drivers/pcnet32/module
bus/pci/drivers/ohci_hcd
bus/pci/drivers/ohci_hcd/new_id
bus/pci/drivers/ohci_hcd/bind
bus/pci/drivers/ohci_hcd/unbind
bus/pci/drivers/ohci_hcd/module
bus/pci/drivers/nasGpio
bus/pci/drivers/nasGpio/new_id
bus/pci/drivers/nasGpio/bind
bus/pci/drivers/nasGpio/unbind
bus/pci/drivers/nasGpio/module
bus/pci/drivers/nasGpio/0000:00:1f.0
bus/pci/drivers/mptspi
bus/pci/drivers/mptspi/new_id
bus/pci/drivers/mptspi/bind
bus/pci/drivers/mptspi/unbind
bus/pci/drivers/mptspi/module
bus/pci/drivers/ehci_hcd
bus/pci/drivers/ehci_hcd/new_id
bus/pci/drivers/ehci_hcd/bind
bus/pci/drivers/ehci_hcd/unbind
bus/pci/drivers/ehci_hcd/module
bus/pci/drivers/ehci_hcd/0000:00:1d.7
bus/pci/drivers/e1000
bus/pci/drivers/e1000/new_id
bus/pci/drivers/e1000/bind
bus/pci/drivers/e1000/unbind
bus/pci/drivers/e1000/module
bus/pci/drivers/e1000/0000:01:00.0
bus/pci/drivers/e100
bus/pci/drivers/e100/new_id
bus/pci/drivers/e100/bind
bus/pci/drivers/e100/unbind
bus/pci/drivers/e100/module
bus/pci/drivers/ata_piix
bus/pci/drivers/ata_piix/new_id
bus/pci/drivers/ata_piix/bind
bus/pci/drivers/ata_piix/unbind
bus/pci/drivers/ata_piix/module
bus/pci/drivers/ahci
bus/pci/drivers/ahci/new_id
bus/pci/drivers/ahci/bind
bus/pci/drivers/ahci/unbind
bus/pci/drivers/ahci/module
bus/pci/drivers/ahci/0000:00:1f.2
bus/pci/drivers/i801_smbus
bus/pci/drivers/i801_smbus/new_id
bus/pci/drivers/i801_smbus/bind
bus/pci/drivers/i801_smbus/unbind
bus/pci/drivers/i801_smbus/0000:00:1f.3
bus/pci/drivers/PCI_IDE
bus/pci/drivers/PCI_IDE/new_id
bus/pci/drivers/PCI_IDE/bind
bus/pci/drivers/PCI_IDE/unbind
bus/pci/drivers/RZ1000_IDE
bus/pci/drivers/RZ1000_IDE/new_id
bus/pci/drivers/RZ1000_IDE/bind
bus/pci/drivers/RZ1000_IDE/unbind
bus/pci/drivers/PIIX_IDE
bus/pci/drivers/PIIX_IDE/new_id
bus/pci/drivers/PIIX_IDE/bind
bus/pci/drivers/PIIX_IDE/unbind
bus/pci/drivers/serial
bus/pci/drivers/serial/new_id
bus/pci/drivers/serial/bind
bus/pci/drivers/serial/unbind
bus/pci/devices
bus/pci/devices/0000:02:00.0
bus/pci/devices/0000:01:00.0
bus/pci/devices/0000:00:1f.3
bus/pci/devices/0000:00:1f.2
bus/pci/devices/0000:00:1f.0
bus/pci/devices/0000:00:1e.0
bus/pci/devices/0000:00:1d.7
bus/pci/devices/0000:00:1d.3
bus/pci/devices/0000:00:1d.2
bus/pci/devices/0000:00:1d.1
bus/pci/devices/0000:00:1d.0
bus/pci/devices/0000:00:1c.2
bus/pci/devices/0000:00:1c.0
bus/pci/devices/0000:00:02.0
bus/pci/devices/0000:00:00.0
bus/platform
bus/platform/drivers
bus/platform/drivers/dcdbas
bus/platform/drivers/dcdbas/dcdbas
bus/platform/drivers/dcdbas/bind
bus/platform/drivers/dcdbas/unbind
bus/platform/drivers/i8042
bus/platform/drivers/i8042/i8042
bus/platform/drivers/i8042/bind
bus/platform/drivers/i8042/unbind
bus/platform/drivers/serial8250
bus/platform/drivers/serial8250/bind
bus/platform/drivers/serial8250/unbind
bus/platform/drivers/serial8250/serial8250
bus/platform/devices
bus/platform/devices/dcdbas
bus/platform/devices/i8042
bus/platform/devices/serial8250
bus/platform/devices/pcspkr
bus/platform/devices/bluetooth


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

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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
                   ` (3 preceding siblings ...)
  2009-09-01 21:27 ` Tech2009
@ 2009-09-02  0:23 ` Hubert Kario
  2009-09-02  2:10 ` Juerg Haefliger
                   ` (8 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Hubert Kario @ 2009-09-02  0:23 UTC (permalink / raw)
  To: lm-sensors

On Tuesday 01 September 2009 23:27:28 Tech2009 wrote:
> Thank you for the suggestions.
>
> I looked in sysfs on the factory distro, no sign of dme1737 there (see
> attached). However there are other i2c devices not on my debian
> install...you could be right about the direct port io, but without
> disassembling the library it's hard to tell.
>
> I tried loading dme1737 with force_start, but that made no difference
> for me.
I was thinking about using the 'force' parameter to givie the address 
explicitly to the module, the device may be on non standard port.
sensors-detect is usually more capable of detecting devices than kernel 
modules
>
> I'm going to have to determine whether the problem is with the sensors
> program or the dme1737 driver. Is there a way to make the dme1737 module
> dump out the debug information present in the source code?
Haven't read the source of this module, but you'll probably have to compile 
kernel (or at least the module) with different .config (one that enables 
debugging messages)
>
> I'm going to see if I can use the dme1737.c module source to read the
> information via standard i2c calls in userland (ie i2ctools). If this
> does work, I will be at a loss as to why the dme1737 module + sensors
> program aren't working, but at least I'll have a viable alternative.
>
> I will let you know if it works.
I'm just a random lm-sensors user, so it's more of the blind leading the blind 
case and educated guess than real inside knowledge about lm-sensors...
Though there are other readers from the list that will benefit from this 
information
>
> On Tue, 2009-09-01 at 20:26 +0200, Hubert Kario wrote:
> > On Saturday 29 August 2009 18:03:36 Tech2009 wrote:
> > > > Message: 3
> > > > Date: Sat, 29 Aug 2009 10:30:25 +0200
> > > > From: Hubert Kario <hka@qbs.com.pl>
> > > > Subject: Re: [lm-sensors] "No sensors found!" on Intel Entry Storage
> > > > System SS4200
> > > > To: lm-sensors@lm-sensors.org
> > > > Message-ID: <200908291030.25637.hka@qbs.com.pl>
> > > > Content-Type: text/plain;  charset="iso-8859-2"
> > > >
> > > >
> > > >
> > > > and what shows dmesg?
> > >
> > > dmesg output after sensors-detect:
> > > [ 1815.988770] i2c /dev entries driver
> > >
> > > dmesg output after sensors:
> > > (blank)
> >
> > So there doesn't appear to be any problem...
> >
> > > The bundled Linux image does not appear to use the dme1737 module or
> > > lmsensors. The web interface loads several closed source libraries, and
> > > I'm not sure how they access the hardware.
> >
> > They may access the hardware directly, is the web interface running as
> > root? Also, you may check /sys file system, look in
> > /sys/bus/platform/drivers/ for it, the module may be compiled in in the
> > bundled image
> >
> > > Is there something I should try to determine why sensors-detect sees
> > > the chip but sensors does not?
> >
> > you could try one of the parameters aviable for the module, for list of
> > all of them, run:
> > modinfo dme1737

-- 
Hubert Kario
QBS - Quality Business Software
ul. Ksawerów 30/85
02-656 Warszawa
POLAND
tel. +48 (22) 646-61-51, 646-74-24
fax +48 (22) 646-61-50


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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
                   ` (4 preceding siblings ...)
  2009-09-02  0:23 ` Hubert Kario
@ 2009-09-02  2:10 ` Juerg Haefliger
  2009-09-02 19:29 ` Jean Delvare
                   ` (7 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Juerg Haefliger @ 2009-09-02  2:10 UTC (permalink / raw)
  To: lm-sensors

Hi

>> and what shows dmesg?
>
>
> dmesg output after sensors-detect:
> [ 1815.988770] i2c /dev entries driver
>
> dmesg output after sensors:
> (blank)


Please send the output of dmesg after you load the dme1737 driver. It
should at least spit out a message like "Found a SCH5027 chip at xyz".

...juerg


>
> The bundled Linux image does not appear to use the dme1737 module or
> lmsensors. The web interface loads several closed source libraries, and
> I'm not sure how they access the hardware.
>
> Is there something I should try to determine why sensors-detect sees the
> chip but sensors does not?
>
>
>
> _______________________________________________
> 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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
                   ` (5 preceding siblings ...)
  2009-09-02  2:10 ` Juerg Haefliger
@ 2009-09-02 19:29 ` Jean Delvare
  2009-09-02 20:02 ` Juerg Haefliger
                   ` (6 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Jean Delvare @ 2009-09-02 19:29 UTC (permalink / raw)
  To: lm-sensors

On Wed, 2 Sep 2009 02:23:52 +0200, Hubert Kario wrote:
> On Tuesday 01 September 2009 23:27:28 Tech2009 wrote:
> > Thank you for the suggestions.
> >
> > I looked in sysfs on the factory distro, no sign of dme1737 there (see
> > attached). However there are other i2c devices not on my debian
> > install...you could be right about the direct port io, but without
> > disassembling the library it's hard to tell.
> >
> > I tried loading dme1737 with force_start, but that made no difference
> > for me.
> I was thinking about using the 'force' parameter to givie the address 
> explicitly to the module, the device may be on non standard port.
> sensors-detect is usually more capable of detecting devices than kernel 
> modules

Good point. The dme1737 driver only recognizes version/stepping value
of 0x69 as the SCH5027. sensors-detect OTOH recognizes all version/
steppings from 0x69 to 0x6f. It would be interesting to see a dump of
the chip (modprobe i2c-dev then run i2cdump), I'd guess you have a
version/stepping value > 0x69.

Then I don't know which of the driver or sensors-detect is correct.
Juerg?

It might help to have a physical look at the chip and read the top
marking, if this is possible.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
                   ` (6 preceding siblings ...)
  2009-09-02 19:29 ` Jean Delvare
@ 2009-09-02 20:02 ` Juerg Haefliger
  2010-01-29 13:46 ` Jean Delvare
                   ` (5 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Juerg Haefliger @ 2009-09-02 20:02 UTC (permalink / raw)
  To: lm-sensors

Hi Jean,

>> > Thank you for the suggestions.
>> >
>> > I looked in sysfs on the factory distro, no sign of dme1737 there (see
>> > attached). However there are other i2c devices not on my debian
>> > install...you could be right about the direct port io, but without
>> > disassembling the library it's hard to tell.
>> >
>> > I tried loading dme1737 with force_start, but that made no difference
>> > for me.
>> I was thinking about using the 'force' parameter to givie the address
>> explicitly to the module, the device may be on non standard port.
>> sensors-detect is usually more capable of detecting devices than kernel
>> modules
>
> Good point. The dme1737 driver only recognizes version/stepping value
> of 0x69 as the SCH5027. sensors-detect OTOH recognizes all version/
> steppings from 0x69 to 0x6f. It would be interesting to see a dump of
> the chip (modprobe i2c-dev then run i2cdump), I'd guess you have a
> version/stepping value > 0x69.
>
> Then I don't know which of the driver or sensors-detect is correct.
> Juerg?

The datasheet that I have specifies 0x69 as the initial
version/stepping value but doesn't specify the range of possible
values.

...juerg



> It might help to have a physical look at the chip and read the top
> marking, if this is possible.
>
> --
> Jean Delvare
> http://khali.linux-fr.org/wishlist.html
>

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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
                   ` (7 preceding siblings ...)
  2009-09-02 20:02 ` Juerg Haefliger
@ 2010-01-29 13:46 ` Jean Delvare
  2010-01-30  0:17 ` Lou Gosselin
                   ` (4 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Jean Delvare @ 2010-01-29 13:46 UTC (permalink / raw)
  To: lm-sensors

On Wed, 2 Sep 2009 21:29:16 +0200, Jean Delvare wrote:
> On Wed, 2 Sep 2009 02:23:52 +0200, Hubert Kario wrote:
> > On Tuesday 01 September 2009 23:27:28 Tech2009 wrote:
> > > Thank you for the suggestions.
> > >
> > > I looked in sysfs on the factory distro, no sign of dme1737 there (see
> > > attached). However there are other i2c devices not on my debian
> > > install...you could be right about the direct port io, but without
> > > disassembling the library it's hard to tell.
> > >
> > > I tried loading dme1737 with force_start, but that made no difference
> > > for me.
> > I was thinking about using the 'force' parameter to givie the address 
> > explicitly to the module, the device may be on non standard port.
> > sensors-detect is usually more capable of detecting devices than kernel 
> > modules
> 
> Good point. The dme1737 driver only recognizes version/stepping value
> of 0x69 as the SCH5027. sensors-detect OTOH recognizes all version/
> steppings from 0x69 to 0x6f. It would be interesting to see a dump of
> the chip (modprobe i2c-dev then run i2cdump), I'd guess you have a
> version/stepping value > 0x69.

Ping. Can we have the output of i2cdump for your chip, please?

> It might help to have a physical look at the chip and read the top
> marking, if this is possible.

This would also be helpful, if possible.

-- 
Jean Delvare

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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
                   ` (8 preceding siblings ...)
  2010-01-29 13:46 ` Jean Delvare
@ 2010-01-30  0:17 ` Lou Gosselin
  2010-01-30  9:33 ` Jean Delvare
                   ` (3 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Lou Gosselin @ 2010-01-30  0:17 UTC (permalink / raw)
  To: lm-sensors

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

Jean Delvare wrote:
> On Wed, 2 Sep 2009 21:29:16 +0200, Jean Delvare wrote:
>   
>> On Wed, 2 Sep 2009 02:23:52 +0200, Hubert Kario wrote:
>>     
>>> On Tuesday 01 September 2009 23:27:28 Tech2009 wrote:
>>>       
>>>> Thank you for the suggestions.
>>>>
>>>> I looked in sysfs on the factory distro, no sign of dme1737 there (see
>>>> attached). However there are other i2c devices not on my debian
>>>> install...you could be right about the direct port io, but without
>>>> disassembling the library it's hard to tell.
>>>>
>>>> I tried loading dme1737 with force_start, but that made no difference
>>>> for me.
>>>>         
>>> I was thinking about using the 'force' parameter to givie the address 
>>> explicitly to the module, the device may be on non standard port.
>>> sensors-detect is usually more capable of detecting devices than kernel 
>>> modules
>>>       
>> Good point. The dme1737 driver only recognizes version/stepping value
>> of 0x69 as the SCH5027. sensors-detect OTOH recognizes all version/
>> steppings from 0x69 to 0x6f. It would be interesting to see a dump of
>> the chip (modprobe i2c-dev then run i2cdump), I'd guess you have a
>> version/stepping value > 0x69.
>>     
>
> Ping. Can we have the output of i2cdump for your chip, please?
>
>   
>> It might help to have a physical look at the chip and read the top
>> marking, if this is possible.
>>     
>
> This would also be helpful, if possible.
>
>   
Wow, it's been a while since then, I'm not on the list any longer.

I've attached two files.
sensors.txt shows the output that I get with sensors-detect and sensors.

i2cbus.txt shows output for i2cdetect and i2cdump.
Let me point out that after running "i2cdump 0 0x6a", lmsensors was no 
longer responsive. Furthermore the machine failed to reboot until I did 
a cold boot.


I'm not sure what chip to look for, but according to this document:
http://download.intel.com/support/motherboards/server/ss4200-e/sb/ss4200e_tps_11.pdf
"Enclosure management is performed by a SMSC SCH5027D part with an 
integrated hardware monitor controller. The SMSC component monitors 
various aspects of the storage enclosure."

If you feel it's helpful I can try to take a picture.

I'll give any suggestions a shot, or if you're willing, I can setup one 
of these machines for you to connect to.


[-- Attachment #2: i2cbus.txt --]
[-- Type: text/plain, Size: 4916 bytes --]

Script started on Fri 29 Jan 2010 06:41:17 PM EST
intel-ss4200:~# i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- 08 -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- 2e -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- 44 -- -- -- -- -- -- -- -- -- -- -- 
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- 69 6a -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
intel-ss4200:~# i2cdump 0 0x69
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 0x69, mode byte
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08    ????????????????
10: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08    ????????????????
20: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08    ????????????????
30: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08    ????????????????
40: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08    ????????????????
50: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08    ????????????????
60: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08    ????????????????
70: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08    ????????????????
80: ff f6 03 00 07 00 1a 05 80 11 00 03 ff ff ff ff    .??.?.????.?....
90: ff 96 01 ff ff ff ff ff ff 96 01 00 ff 15 00 00    .??......??..?..
a0: 08 b4 1b b4 ff ff ff ff ff ff ff ff ff ff ff ff    ????............
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff 01 11    ..............??
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
intel-ss4200:~# i2cdump 0 0x69\b^[[Ka
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 0x6a, mode byte
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06    ????????????????
10: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06    ????????????????
20: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06    ????????????????
30: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06    ????????????????
40: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06    ????????????????
50: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06    ????????????????
60: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06    ????????????????
70: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06    ????????????????
80: 8f ff 00 11 06 06 00 00 00 00 80 00 00 00 00 d5    ?..???....?....?
90: d5 d5 d5 d5 d5 d5 d5 d5 d5 d5 d5 d5 d5 d5 XX XX    ??????????????XX
a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
intel-ss4200:~# sendo\b^[[K\b^[[Ksors-detect
# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no): 
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7

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

We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.

Next adapter: SMBus I801 adapter at 0400 (i2c-0)
Do you want to scan it? (YES/no/selectively): 

^C
intel-ss4200:~# 
intel-ss4200:~# exit

Script done on Fri 29 Jan 2010 06:43:51 PM EST

[-- Attachment #3: sensors.txt --]
[-- Type: text/plain, Size: 9688 bytes --]

Script started on Fri 29 Jan 2010 06:48:54 PM EST
intel-ss4200:~# sn\b^[[Kensors-detect
# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no): 
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7

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

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 0400 (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x2e
Probing for `Myson MTP008'...                               No
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM78-J'...              No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM85 or LM96000'...     No
Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... No
Probing for `SMSC EMC6D100, EMC6D101 or EMC6D102'...        No
Probing for `Analog Devices ADT7462'...                     No
Probing for `Analog Devices ADT7467 or ADT7468'...          No
Probing for `Analog Devices ADT7470'...                     No
Probing for `Analog Devices ADT7473'...                     No
Probing for `Analog Devices ADT7475'...                     No
Probing for `Analog Devices ADT7476'...                     No
Probing for `Andigilog aSC7611'...                          No
Probing for `Andigilog aSC7621'...                          No
Probing for `National Semiconductor LM87'...                No
Probing for `National Semiconductor LM93'...                No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83792D'...                            No
Probing for `Winbond W83793R/G'...                          No
Probing for `Winbond W83791SD'...                           No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG'...                          No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Winbond W83L786NR/NG/R/G'...                   No
Probing for `Winbond W83L785TS-S'...                        No
Probing for `Analog Devices ADM9240'...                     No
Probing for `Dallas Semiconductor DS1780'...                No
Probing for `National Semiconductor LM81'...                No
Probing for `Analog Devices ADM1026'...                     No
Probing for `Analog Devices ADM1025'...                     No
Probing for `Analog Devices ADM1029'...                     No
Probing for `Analog Devices ADM1030'...                     No
Probing for `Analog Devices ADM1031'...                     No
Probing for `Analog Devices ADM1022'...                     No
Probing for `Texas Instruments THMC50'...                   No
Probing for `Analog Devices ADM1028'...                     No
Probing for `ITE IT8712F'...                                No
Probing for `SMSC DME1737'...                               No
Probing for `SMSC SCH5027D-NW'...                           Success!
    (confidence 6, driver `dme1737')
Probing for `Fintek F75373S/SG'...                          No
Probing for `Fintek F75375S/SP'...                          No
Probing for `Fintek F75387SG/RG'...                         No
Probing for `Analog Devices ADM1024'...                     No
Probing for `Winbond W83791D'...                            No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no): 
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM78-J' at 0x290...     No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     Yes
Found `SMSC SCH5027D-NW Super IO'                           
    (hardware monitoring capabilities accessible via SMBus only)

Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no): 
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD K10 thermal sensors...                                  No
Intel Core family thermal sensor...                         Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No

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

Driver `dme1737' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0400'
    Busdriver `i2c-i801', I2C address 0x2e
    Chip `SMSC SCH5027D-NW' (confidence: 6)

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 load everything that is needed, add this to /etc/modules:

#----cut here----
# I2C adapter drivers
i2c-i801
# Chip drivers
dme1737
coretemp
#----cut here----

Do you want to add these lines automatically? (yes/NO)
intel-ss4200:~# modprobe coretemp
intel-ss4200:~# modprobe i2c-i801
intel-ss4200:~# modprobe dme1737
intel-ss4200:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +27.0������C  (high = +86.0������C, crit = +100.0������C)  

intel-ss4200:~# lsmod
Module                  Size  Used by
i2c_dev                10640  0 
ipv6                  288456  16 
xt_tcpudp               7680  1 
iptable_nat             9872  1 
nf_nat                 23192  1 iptable_nat
nf_conntrack_ipv4      19352  3 iptable_nat,nf_nat
nf_conntrack           71440  3 iptable_nat,nf_nat,nf_conntrack_ipv4
ip_tables              21520  1 iptable_nat
x_tables               25224  3 xt_tcpudp,iptable_nat,ip_tables
coretemp               11008  0 
dme1737                43168  0 
hwmon_vid               7296  1 dme1737
loop                   19468  0 
snd_pcm                81800  0 
snd_timer              25744  1 snd_pcm
snd                    63688  2 snd_pcm,snd_timer
soundcore              12064  1 snd
snd_page_alloc         13072  1 snd_pcm
psmouse                42268  0 
pcspkr                  7040  0 
serio_raw               9988  0 
i2c_i801               13596  0 
i2c_core               27936  3 i2c_dev,dme1737,i2c_i801
rng_core                8968  0 
button                 11680  0 
intel_agp              31856  1 
evdev                  14208  0 
ext3                  125072  1 
jbd                    51240  1 ext3
mbcache                12804  1 ext3
sd_mod                 29376  3 
ahci                   33036  2 
ehci_hcd               36108  0 
uhci_hcd               25760  0 
sata_sil24             18180  0 
libata                165600  2 ahci,sata_sil24
scsi_mod              161016  2 sd_mod,libata
dock                   14112  1 libata
e1000e                104872  0 
thermal                22688  0 
processor              42304  1 thermal
fan                     9352  0 
thermal_sys            17728  3 thermal,processor,fan
intel-ss4200:~# exit

Script done on Fri 29 Jan 2010 06:50:08 PM EST

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

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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
                   ` (9 preceding siblings ...)
  2010-01-30  0:17 ` Lou Gosselin
@ 2010-01-30  9:33 ` Jean Delvare
  2010-01-30 20:27 ` Lou Gosselin
                   ` (2 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Jean Delvare @ 2010-01-30  9:33 UTC (permalink / raw)
  To: lm-sensors

Hi Lou,

On Fri, 29 Jan 2010 19:17:06 -0500, Lou Gosselin wrote:
> I've attached two files.
> sensors.txt shows the output that I get with sensors-detect and sensors.
> 
> i2cbus.txt shows output for i2cdetect and i2cdump.
> Let me point out that after running "i2cdump 0 0x6a", lmsensors was no 
> longer responsive. Furthermore the machine failed to reboot until I did 
> a cold boot.

Let me point out that dumping random i2c chips is a very bad idea.
Especially chips in the 0x86-0x6a range, are often clock chips which
don't like being dumped at all...

> (...)
> I'll give any suggestions a shot, or if you're willing, I can setup one 
> of these machines for you to connect to.

The chip I would like to see a dump of is the one at 0x2e. This will
give us the chip ID of your SMSC chip. It's probably only a matter of
adding the right ID to the driver.

-- 
Jean Delvare

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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
                   ` (10 preceding siblings ...)
  2010-01-30  9:33 ` Jean Delvare
@ 2010-01-30 20:27 ` Lou Gosselin
  2010-01-31 13:05 ` Jean Delvare
  2010-01-31 13:26 ` Jean Delvare
  13 siblings, 0 replies; 15+ messages in thread
From: Lou Gosselin @ 2010-01-30 20:27 UTC (permalink / raw)
  To: lm-sensors

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

The email didn't specify the range to dump, but thanks for the advice.
I'm attaching the output for 0x2e.
Let me know if you'd like anything else.


Jean Delvare wrote:
> Hi Lou,
>
> On Fri, 29 Jan 2010 19:17:06 -0500, Lou Gosselin wrote:
>   
>> I've attached two files.
>> sensors.txt shows the output that I get with sensors-detect and sensors.
>>
>> i2cbus.txt shows output for i2cdetect and i2cdump.
>> Let me point out that after running "i2cdump 0 0x6a", lmsensors was no 
>> longer responsive. Furthermore the machine failed to reboot until I did 
>> a cold boot.
>>     
>
> Let me point out that dumping random i2c chips is a very bad idea.
> Especially chips in the 0x86-0x6a range, are often clock chips which
> don't like being dumped at all...
>
>   
>> (...)
>> I'll give any suggestions a shot, or if you're willing, I can setup one 
>> of these machines for you to connect to.
>>     
>
> The chip I would like to see a dump of is the one at 0x2e. This will
> give us the chip ID of your SMSC chip. It's probably only a matter of
> adding the right ID to the driver.
>
>   


[-- Attachment #2: lmsensor.txt --]
[-- Type: text/plain, Size: 1443 bytes --]

intel-ss4200:~# 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]
     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 02 48 00 0f    ............?H.?
20: c0 57 c0 c3 bf fd 15 1a ff ff 40 11 b4 10 ff ff    ?W??????..@???..
30: 6b 6b 6b 30 0b 00 0f 00 40 00 48 f7 0f 00 5c 69    kkk0?.?.@.H??.\i
40: 05 00 00 18 00 ff 00 ff 00 ff 00 ff 00 ff 81 44    ?..?..........?D
50: 81 7f 81 4b ff ff ff ff ff ff ff ff 02 c2 c2 7b    ???K........???{
60: 7b 7b e8 88 6b 6b 6b 33 32 64 40 41 73 22 20 00    {{??kkk32d@As" .
70: 6b 6b 6b 00 00 00 00 00 00 00 30 00 00 00 ec 1c    kkk.......0...??
80: 7e a4 0f 00 00 6c 4c 2e cc 00 33 33 24 24 19 19    ~??..lL.?.33$$??
90: 04 04 04 04 0c 0c 0c 5a f1 c0 b5 00 ff 00 ff 00    ???????Z???.....
a0: 00 00 0c 00 00 ff ff 07 0b fe ff fe ff ff ff ff    ..?....???.?....
b0: ff 00 00 00 00 00 28 28 0e 0e 0f 0f 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    ................

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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
                   ` (11 preceding siblings ...)
  2010-01-30 20:27 ` Lou Gosselin
@ 2010-01-31 13:05 ` Jean Delvare
  2010-01-31 13:26 ` Jean Delvare
  13 siblings, 0 replies; 15+ messages in thread
From: Jean Delvare @ 2010-01-31 13:05 UTC (permalink / raw)
  To: lm-sensors

On Sat, 30 Jan 2010 15:27:21 -0500, Lou Gosselin wrote:
> The email didn't specify the range to dump, but thanks for the advice.
> I'm attaching the output for 0x2e.
> Let me know if you'd like anything else.

I've looked at the dump, and the device ID is 0x69 as expected by the
driver. So this wasn't the problem.

Then I've read the thread again, and I see you're running kernel
2.6.26. Our wiki improperly claims that support for the SCH5027 was
added in kernel 2.6.26, but looking at the code, this isn't true.
Support for your chip was added in kernel 2.6.27. So this is no
surprise that the dme1737 kernel driver on your system did not
recognize your chip: it doesn't support it (yet).

I've fixed the wiki. If you want support for your chip, you'll have to
either upgrade your kernel to >= 2.6.27, or backport the dme1737 driver
to your kernel. The version in kernel 2.6.27 should do just fine on
2.6.26:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=drivers/hwmon/dme1737.c;hbT9edb83327f2a5027a22d65b10603b01dc40175

-- 
Jean Delvare

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

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
  2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
                   ` (12 preceding siblings ...)
  2010-01-31 13:05 ` Jean Delvare
@ 2010-01-31 13:26 ` Jean Delvare
  13 siblings, 0 replies; 15+ messages in thread
From: Jean Delvare @ 2010-01-31 13:26 UTC (permalink / raw)
  To: lm-sensors

Hi Lou,

On Sun, 31 Jan 2010 14:05:24 +0100, Jean Delvare wrote:
> On Sat, 30 Jan 2010 15:27:21 -0500, Lou Gosselin wrote:
> > The email didn't specify the range to dump, but thanks for the advice.
> > I'm attaching the output for 0x2e.
> > Let me know if you'd like anything else.
> 
> I've looked at the dump, and the device ID is 0x69 as expected by the
> driver. So this wasn't the problem.
> 
> Then I've read the thread again, and I see you're running kernel
> 2.6.26. Our wiki improperly claims that support for the SCH5027 was
> added in kernel 2.6.26, but looking at the code, this isn't true.
> Support for your chip was added in kernel 2.6.27. So this is no
> surprise that the dme1737 kernel driver on your system did not
> recognize your chip: it doesn't support it (yet).
> 
> I've fixed the wiki. If you want support for your chip, you'll have to
> either upgrade your kernel to >= 2.6.27, or backport the dme1737 driver
> to your kernel. The version in kernel 2.6.27 should do just fine on
> 2.6.26:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=drivers/hwmon/dme1737.c;hbT9edb83327f2a5027a22d65b10603b01dc40175

And here you go...
http://khali.linux-fr.org/devel/misc/dme1737/

Put the files in a temporary directory, install package linux-headers,
type "make" to build the driver, and then, as root:
# rmmod dme1737
# insmod ./dme1737.ko

That should do it.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

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

^ permalink raw reply	[flat|nested] 15+ messages in thread
end of thread, other threads:[~2010-01-31 13:26 UTC | newest]

Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
2009-08-29  8:30 ` Hubert Kario
2009-08-29 16:03 ` Tech2009
2009-09-01 18:26 ` Hubert Kario
2009-09-01 21:27 ` Tech2009
2009-09-02  0:23 ` Hubert Kario
2009-09-02  2:10 ` Juerg Haefliger
2009-09-02 19:29 ` Jean Delvare
2009-09-02 20:02 ` Juerg Haefliger
2010-01-29 13:46 ` Jean Delvare
2010-01-30  0:17 ` Lou Gosselin
2010-01-30  9:33 ` Jean Delvare
2010-01-30 20:27 ` Lou Gosselin
2010-01-31 13:05 ` Jean Delvare
2010-01-31 13:26 ` Jean Delvare

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.