* [lm-sensors] Problems with i2c_i801
@ 2006-03-31 9:19 James Davis
2006-03-31 10:15 ` Jean Delvare
` (5 more replies)
0 siblings, 6 replies; 7+ messages in thread
From: James Davis @ 2006-03-31 9:19 UTC (permalink / raw)
To: lm-sensors
I was about to post a support ticket but saw that I ought to post here
instead whilst the system is down.
I'm running Debian/Etch with a 2.6.15-1-686 kernel. The I think the
system is a Dell Optiplex GX280 which from reading Dell's website gives
me an Intel 915G chipset (if I've correctly identified the system!).
Running sensors detect gave me the following to add to my modules.conf.
#----cut here----
# I2C adapter drivers
i2c-i801
# I2C chip drivers
eeprom
#----cut here----
I've loaded these modules Looking through the output of lsmod I get:
cressida:/home/james# lsmod | grep i2c
i2c_dev 8640 0
i2c_i801 7916 0
i2c_core 19280 3 eeprom,i2c_dev,i2c_i801
sysfs appears to be correctly mounted:
cressida:/home/james# mount | grep sys
sysfs on /sys type sysfs (rw)
But when I run sensors I get the following output:
cressida:/home/james# sensors
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!
cressida:/home/james#
Any idea what I'm doing wrong? :(
Many thanks,
James
^ permalink raw reply [flat|nested] 7+ messages in thread
* [lm-sensors] Problems with i2c_i801
2006-03-31 9:19 [lm-sensors] Problems with i2c_i801 James Davis
@ 2006-03-31 10:15 ` Jean Delvare
2006-03-31 10:28 ` James Davis
` (4 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Jean Delvare @ 2006-03-31 10:15 UTC (permalink / raw)
To: lm-sensors
Hi James,
> I'm running Debian/Etch with a 2.6.15-1-686 kernel. The I think the
> system is a Dell Optiplex GX280 which from reading Dell's website gives
> me an Intel 915G chipset (if I've correctly identified the system!).
> Running sensors detect gave me the following to add to my modules.conf.
>
> #----cut here----
> # I2C adapter drivers
> i2c-i801
> # I2C chip drivers
> eeprom
> #----cut here----
>
> I've loaded these modules Looking through the output of lsmod I get:
>
> cressida:/home/james# lsmod | grep i2c
> i2c_dev 8640 0
> i2c_i801 7916 0
> i2c_core 19280 3 eeprom,i2c_dev,i2c_i801
>
> sysfs appears to be correctly mounted:
>
> cressida:/home/james# mount | grep sys
> sysfs on /sys type sysfs (rw)
>
> But when I run sensors I get the following output:
>
> cressida:/home/james# sensors
> Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and libsensors
> was compiled with sysfs support!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
> cressida:/home/james#
>
> Any idea what I'm doing wrong? :(
Where do the "sensors" program come from? Debian package?
Hand-compiled? Which version ("sensors -v")?
Note that no hardware monitoring chip was detected on your system, so
if that's what you are after, fixing the problem above won't help you
much. Either your system has no hardware monitoring chip, or
sensors-detect failed to detect it for some reason. The complete output
of "sensors-detect" may let us help you in the second case.
--
Jean Delvare
^ permalink raw reply [flat|nested] 7+ messages in thread
* [lm-sensors] Problems with i2c_i801
2006-03-31 9:19 [lm-sensors] Problems with i2c_i801 James Davis
2006-03-31 10:15 ` Jean Delvare
@ 2006-03-31 10:28 ` James Davis
2006-03-31 11:15 ` Jean Delvare
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: James Davis @ 2006-03-31 10:28 UTC (permalink / raw)
To: lm-sensors
On Fri, 2006-03-31 at 12:15 +0200, Jean Delvare wrote:
> Where do the "sensors" program come from? Debian package?
> Hand-compiled? Which version ("sensors -v")?
The Debian package
cressida:/home/james# sensors -v
sensors version 2.10.0 with libsensors version 2.10.0
> Note that no hardware monitoring chip was detected on your system, so
> if that's what you are after, fixing the problem above won't help you
> much. Either your system has no hardware monitoring chip, or
> sensors-detect failed to detect it for some reason. The complete output
> of "sensors-detect" may let us help you in the second case.
cressida:/home/james# sensors-detect
# sensors-detect revision 1.413 (2006/01/19 20:28:00)
This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
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.
You do not need any special privileges for this.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801FB ICH6
Probe succesfully concluded.
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.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.
We are now going to do the adapter probings. Some adapters may hang
halfway
through; we can't really help that. Also, some chips will 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. That often
includes address 0x69 (clock chip).
Next adapter: SMBus I801 adapter at e8a0
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x30
Client found at address 0x32
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client at address 0x50 can not be probed - unload all client drivers
first!
Client at address 0x52 can not be probed - unload all client drivers
first!
Client found at address 0x69
Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan the ISA bus? (YES/no):
Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8712F'
Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for `ITE 8702F Super IO Sensors'
Failed! (0x7601)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0x7601)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0x7601)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (0x76)
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed! (0x76)
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed! (0x76)
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed! (0x76)
Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
Failed! (0x76)
Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
Failed! (0x76)
Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
Failed! (0x76)
Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
Failed! (0x76)
Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
Failed! (0x76)
Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
Failed! (0x76)
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed! (0x76)
Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
Failed! (0x76)
Probing for `Nat. Semi. PC87591 Super IO'
Failed! (0x76)
Probing for `Nat. Semi. PC87371 Super IO'
Failed! (0x76)
Probing for `Nat. Semi. PC97371 Super IO'
Failed! (0x76)
Probing for `Nat. Semi. PC8739x Super IO'
Failed! (0x76)
Probing for `Nat. Semi. PC8741x Super IO'
Failed! (0x76)
Probing for `Nat. Semi. PCPC87427 Super IO'
Failed! (0x76)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (0x76)
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed! (0x76)
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed! (0x76)
Probing for `SMSC 47M15x/192/997 Super IO Fan Sensors'
Failed! (0x76)
Probing for `SMSC 47S42x Super IO Fan Sensors'
Failed! (0x76)
Probing for `SMSC 47S45x Super IO Fan Sensors'
Failed! (0x76)
Probing for `SMSC 47M172 Super IO'
Failed! (0x76)
Probing for `SMSC LPC47B397-NC Super IO'
Failed! (0x76)
Probing for `SMSC SCH5307-NS Super IO'
Failed! (0x76)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
Failed! (skipping family)
Do you want to scan for secondary Super I/O sensors? (YES/no):
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
Failed! (skipping family)
Sorry, no chips were detected.
Either your sensors are not supported, or they are
connected to an I2C bus adapter that we do not support.
See doc/FAQ, doc/lm_sensors-FAQ.html, or
http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/lm_sensors-FAQ.html
(FAQ #4.24.3) for further information.
If you find out what chips are on your board, see
http://secure.netroedge.com/~lm78/newdrivers.html for driver status.
:-( doesn't look hopeful.
James
^ permalink raw reply [flat|nested] 7+ messages in thread
* [lm-sensors] Problems with i2c_i801
2006-03-31 9:19 [lm-sensors] Problems with i2c_i801 James Davis
2006-03-31 10:15 ` Jean Delvare
2006-03-31 10:28 ` James Davis
@ 2006-03-31 11:15 ` Jean Delvare
2006-03-31 12:45 ` James Davis
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Jean Delvare @ 2006-03-31 11:15 UTC (permalink / raw)
To: lm-sensors
Hi James,
> > Where do the "sensors" program come from? Debian package?
> > Hand-compiled? Which version ("sensors -v")?
>
> The Debian package
>
> cressida:/home/james# sensors -v
> sensors version 2.10.0 with libsensors version 2.10.0
OK. Can you make sure that libsensors was compiled with sysfs support?
"ldd /usr/lib/libsensors.so" should have one line for libsysfs.
> Next adapter: SMBus I801 adapter at e8a0
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x08
> Client found at address 0x30
> Client found at address 0x32
> Client found at address 0x44
> Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
> Client at address 0x50 can not be probed - unload all client drivers
> first!
> Client at address 0x52 can not be probed - unload all client drivers
> first!
> Client found at address 0x69
No I2C/SMBus hardware monitoring chip...
> Do you want to scan for Super I/O sensors? (YES/no):
> Probing for `ITE 8702F Super IO Sensors'
> Failed! (0x7601)
> Probing for `ITE 8705F Super IO Sensors'
> Failed! (0x7601)
> Probing for `ITE 8712F Super IO Sensors'
> Failed! (0x7601)
> Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
> Failed! (0x76)
> Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
> Failed! (0x76)
> Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
> Failed! (0x76)
> Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
> Failed! (0x76)
> Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `Nat. Semi. PC87591 Super IO'
> Failed! (0x76)
> Probing for `Nat. Semi. PC87371 Super IO'
> Failed! (0x76)
> Probing for `Nat. Semi. PC97371 Super IO'
> Failed! (0x76)
> Probing for `Nat. Semi. PC8739x Super IO'
> Failed! (0x76)
> Probing for `Nat. Semi. PC8741x Super IO'
> Failed! (0x76)
> Probing for `Nat. Semi. PCPC87427 Super IO'
> Failed! (0x76)
> Probing for `SMSC 47B27x Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `SMSC 47M14x Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `SMSC 47M15x/192/997 Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `SMSC 47S42x Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `SMSC 47S45x Super IO Fan Sensors'
> Failed! (0x76)
> Probing for `SMSC 47M172 Super IO'
> Failed! (0x76)
> Probing for `SMSC LPC47B397-NC Super IO'
> Failed! (0x76)
> Probing for `SMSC SCH5307-NS Super IO'
> Failed! (0x76)
> Probing for `VT1211 Super IO Sensors'
> Failed! (skipping family)
> Probing for `Winbond W83627EHF/EHG Super IO Sensors'
> Failed! (skipping family)
You have a Super-I/O chip (a.k.a. LPC chip) we don't know about. Given
the output above, this could be a chip made by ITE, National
Semiconductor or SMSC. Can you find some documentation about your board
and/or open the case and locate that chip? Typically they are
rectangular, with 128 pins, and measure about 20 mm by 12 mm. Sometimes
these chips have hardware monitoring functionalities.
Does the BIOS of your system display any hardware monitoring
information? Is this system somehow advertise as having hardware
monitoring capabilities?
--
Jean Delvare
^ permalink raw reply [flat|nested] 7+ messages in thread
* [lm-sensors] Problems with i2c_i801
2006-03-31 9:19 [lm-sensors] Problems with i2c_i801 James Davis
` (2 preceding siblings ...)
2006-03-31 11:15 ` Jean Delvare
@ 2006-03-31 12:45 ` James Davis
2006-03-31 13:17 ` Jean Delvare
2006-03-31 15:00 ` James Davis
5 siblings, 0 replies; 7+ messages in thread
From: James Davis @ 2006-03-31 12:45 UTC (permalink / raw)
To: lm-sensors
On Fri, 2006-03-31 at 13:15 +0200, Jean Delvare wrote:
> OK. Can you make sure that libsensors was compiled with sysfs support?
> "ldd /usr/lib/libsensors.so" should have one line for libsysfs.
It's there...
james at cressida:~$ ldd /usr/lib/libsensors.so.3
linux-gate.so.1 => (0xffffe000)
libc.so.6 => /lib/tls/libc.so.6 (0xb7df3000)
libm.so.6 => /lib/tls/libm.so.6 (0xb7dcc000)
libsysfs.so.1 => /lib/libsysfs.so.1 (0xb7dc1000)
/lib/ld-linux.so.2 (0x80000000)
> You have a Super-I/O chip (a.k.a. LPC chip) we don't know about. Given
> the output above, this could be a chip made by ITE, National
> Semiconductor or SMSC. Can you find some documentation about your board
> and/or open the case and locate that chip? Typically they are
> rectangular, with 128 pins, and measure about 20 mm by 12 mm. Sometimes
> these chips have hardware monitoring functionalities.
I found the following SMSC chip:
LPC47M584-NC
B0443-AL1314
8H1190280
Here's a link to a photograph.
http://www.freecharity.org.uk/~james/DSC00300.JPG
> Does the BIOS of your system display any hardware monitoring
> information? Is this system somehow advertise as having hardware
> monitoring capabilities?
Nothing there, I guess that doesn't bode well..
Many thnaks for your help,
James
^ permalink raw reply [flat|nested] 7+ messages in thread
* [lm-sensors] Problems with i2c_i801
2006-03-31 9:19 [lm-sensors] Problems with i2c_i801 James Davis
` (3 preceding siblings ...)
2006-03-31 12:45 ` James Davis
@ 2006-03-31 13:17 ` Jean Delvare
2006-03-31 15:00 ` James Davis
5 siblings, 0 replies; 7+ messages in thread
From: Jean Delvare @ 2006-03-31 13:17 UTC (permalink / raw)
To: lm-sensors
Hi James,
> I found the following SMSC chip:
>
> LPC47M584-NC
> B0443-AL1314
> 8H1190280
>
> Here's a link to a photograph.
>
> http://www.freecharity.org.uk/~james/DSC00300.JPG
Looks like we had a report for that chip already:
http://netroedge.com/~lm78/readticket.cgi?ticket\x1998
Dell system too... SMSC doesn't have anything about that chip on their
site. I guess this is a custom chip they made for Dell.
> > Does the BIOS of your system display any hardware monitoring
> > information? Is this system somehow advertise as having hardware
> > monitoring capabilities?
>
> Nothing there, I guess that doesn't bode well..
Indeed. I've gone as far as I could, but now, without any information
on that SMSC chip, there's nothing left I can do. Unless you can get
information from either Dell or SMSC, this is the end of the road,
sorry.
--
Jean Delvare
^ permalink raw reply [flat|nested] 7+ messages in thread
* [lm-sensors] Problems with i2c_i801
2006-03-31 9:19 [lm-sensors] Problems with i2c_i801 James Davis
` (4 preceding siblings ...)
2006-03-31 13:17 ` Jean Delvare
@ 2006-03-31 15:00 ` James Davis
5 siblings, 0 replies; 7+ messages in thread
From: James Davis @ 2006-03-31 15:00 UTC (permalink / raw)
To: lm-sensors
Jean Delvare wrote:
> Indeed. I've gone as far as I could, but now, without any information
> on that SMSC chip, there's nothing left I can do. Unless you can get
> information from either Dell or SMSC, this is the end of the road,
> sorry.
Thanks for your help, I've written to SMSC but I'm not holding out on a
reply.
Thanks once again,
James
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2006-03-31 15:00 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-31 9:19 [lm-sensors] Problems with i2c_i801 James Davis
2006-03-31 10:15 ` Jean Delvare
2006-03-31 10:28 ` James Davis
2006-03-31 11:15 ` Jean Delvare
2006-03-31 12:45 ` James Davis
2006-03-31 13:17 ` Jean Delvare
2006-03-31 15:00 ` James Davis
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.