* [lm-sensors] it8716 under 2.6
@ 2006-08-25 6:42 Jean Delvare
2006-08-25 19:45 ` Juergen Kilb
` (7 more replies)
0 siblings, 8 replies; 9+ messages in thread
From: Jean Delvare @ 2006-08-25 6:42 UTC (permalink / raw)
To: lm-sensors
Hi J?rgen,
> i am using a backported version of your patch with kernel 2.6.16.21 Suse 10.1
> on an ASUS M2N-SLI Deluxe.
>
> It seem's to work... in some way ;-)
Great :)
> Inside the BIOS...
>
> VCORE => 1,31V
> 3,3V => 3,41V
> 5V => 5,13V
> 12V => 12,3V
> CPU Temp 26?C
> MB 28?C
> CPU_FAN 2096 => seems to be fan1
> CHA_FAN1 1256 => seems to be fan2
> CHA_FAN2 1427
> CHA_FAN3 1908
> CHA_FAN4 1978
> PWR_FAN 903=> seems to be fan3
>
> Output from "sensors -c /dev/null" is
> ======> it8716-isa-0290
> Adapter: ISA adapter
> in0: +1.01 V (min = +4.08 V, max = +4.08 V) ALARM
> in1: +3.22 V (min = +4.08 V, max = +4.08 V) ALARM
> in2: +0.00 V (min = +4.08 V, max = +4.08 V) ALARM
> in3: +2.85 V (min = +4.08 V, max = +4.08 V) ALARM
> in4: +2.86 V (min = +4.08 V, max = +4.08 V) ALARM
> in5: +0.00 V (min = +4.08 V, max = +4.08 V) ALARM
> in6: +0.00 V (min = +4.08 V, max = +4.08 V) ALARM
> in7: +2.85 V (min = +4.08 V, max = +4.08 V) ALARM
> in8: +2.93 V
> fan1: 4166 RPM (min = 0 RPM)
> fan2: 2481 RPM (min = 0 RPM)
> fan3: 1844 RPM (min = 0 RPM)
> temp1: +22?C (low = -1?C, high = -1?C) sensor = diode
> temp2: +30?C (low = -1?C, high = -1?C) sensor = thermistor
> temp3: -5?C (low = -1?C, high = -1?C) sensor = thermistor
> ALARM
> vid: +0.30 V
> =======
You have the same problem as was reported to me by someone else, i.e.
fan speed readings are twice as much as what the BIOS says. Now, the
values reported by the BIOS are quite low... Do you know what is the
expected speed for these three fans? If you have the opportunity to
test one of them in another machine and compare what the two BIOSes
say, I'd appreciate.
Do the voltages match what the BIOS says if you use the default
configuration file?
> Output of /var/log/messages:
> =======
> Aug 24 22:27:19 deepthought2 kernel: it87: Found IT8716F chip at 0x290,
> revision 0
So this is an IT7616F and not IT8718F contrary to what your original
subject line said... Fixed.
> Aug 24 22:27:19 deepthought2 kernel: it87: in3 is VCC (+5V)
> Aug 24 22:27:19 deepthought2 kernel: it87: in7 is VCCH (+5V)
> Aug 24 22:27:19 deepthought2 kernel: it87: fan4 is enabled
> Aug 24 22:27:19 deepthought2 kernel: it87: fan5 is enabled
> ======>
> What do you think ? How can the BIOS tell me soemthing about 6 FANS..
> I thought the ITE8716 has only 5 tachometer inputs....
Very good question, I don't really know. I even had a report of a board
with 7 fans using this chip (Asus M2N32-SLI). Could either be a second
chip on the board, or multiplexed fan lines (would be bad.) Can you
please provide the complete output of sensors-detect for this system?
Thanks,
--
Jean Delvare
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] it8716 under 2.6
2006-08-25 6:42 [lm-sensors] it8716 under 2.6 Jean Delvare
@ 2006-08-25 19:45 ` Juergen Kilb
2006-08-25 20:24 ` Rudolf Marek
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: Juergen Kilb @ 2006-08-25 19:45 UTC (permalink / raw)
To: lm-sensors
Am Freitag, 25. August 2006 08:42 schrieb Jean Delvare:
Hi Jean,
>
> You have the same problem as was reported to me by someone else, i.e.
> fan speed readings are twice as much as what the BIOS says. Now, the
> values reported by the BIOS are quite low... Do you know what is the
> expected speed for these three fans? If you have the opportunity to
> test one of them in another machine and compare what the two BIOSes
> say, I'd appreciate.
>
I gues the expected speed for the fans are:
CPU-Fan:
Arctic Cooling Alpine 64 :
expected speed :2000 RPM
according to sensors output :4179 RPM
Bios output :2096 RPM
CHA_FAN 1 is an
Revoltec AirGuard 120mm, 23.94 dBA
expected speed :1200 RPM
according to sensors output :2494 RPM
Bios output :1256 RPM
PWR_FAN:
Enermax Liberty EL500AWT 120mm Fan
expected speed :??? RPM
according to sensors output :903 RPM /
Bios output :1256 RPM
i would beleive the BIOS values....
> Do the voltages match what the BIOS says if you use the default
> configuration file?
>
Voltages:
Bios Sensors with default config
Vcore 1,31V 1,01V (maybe the BIOS value is so high after power up)
3,3V 3,41V 3,22V (i think it is the voltage called VDDR)
5V 5,13V 4,78V
12V 12,3V 11,46V
CPU-Temp 26? 24?
MB-Temp 28? 31?
I think, it doesn't look too bad. Should it be better ?
> > Output of /var/log/messages:
> > =======
> > Aug 24 22:27:19 deepthought2 kernel: it87: Found IT8716F chip at 0x290,
> > revision 0
>
> So this is an IT7616F and not IT8718F contrary to what your original
> subject line said... Fixed.
>
Oops my fault ;-)
> > Aug 24 22:27:19 deepthought2 kernel: it87: in3 is VCC (+5V)
> > Aug 24 22:27:19 deepthought2 kernel: it87: in7 is VCCH (+5V)
> > Aug 24 22:27:19 deepthought2 kernel: it87: fan4 is enabled
> > Aug 24 22:27:19 deepthought2 kernel: it87: fan5 is enabled
> > ======> >
> > What do you think ? How can the BIOS tell me soemthing about 6 FANS..
> > I thought the ITE8716 has only 5 tachometer inputs....
>
> Very good question, I don't really know. I even had a report of a board
> with 7 fans using this chip (Asus M2N32-SLI). Could either be a second
> chip on the board, or multiplexed fan lines (would be bad.) Can you
> please provide the complete output of sensors-detect for this system?
>
> Thanks,
Sure here is the complete output of "sensors detect"
====================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): yes
Probing for PCI bus adapters...
Sorry, no PCI bus adapters found.
We will now try to load each adapter module in turn.
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).
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): yes
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... Success!
(confidence 8, driver `it87')
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): yes
Probing for `ITE 8702F Super IO Sensors'
Failed! (0x8716)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0x8716)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0x8716)
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)
Do you want to scan for secondary Super I/O sensors? (YES/no): yes
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)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `it87' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `ITE IT8712F' (confidence: 8)
I will now generate the commands needed to load the I2C modules.
To make the sensors modules behave correctly, add these lines to
/etc/modprobe.conf:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe it87
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----
=============
btw, i have also an
vendor_id : AuthenticAMD
cpu family : 15
model : 75
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
65Watt Type....
==
Juergen
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] it8716 under 2.6
2006-08-25 6:42 [lm-sensors] it8716 under 2.6 Jean Delvare
2006-08-25 19:45 ` Juergen Kilb
@ 2006-08-25 20:24 ` Rudolf Marek
2006-08-25 21:34 ` Jean Delvare
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: Rudolf Marek @ 2006-08-25 20:24 UTC (permalink / raw)
To: lm-sensors
Hi Juergen
Please send me in private the dsdt table.
cat /proc/acpi/dsdt >/tmp/dsdt.bin
In private is neccessary because mailing list eats the binary attachment.
Thanks,
Regards
Rudolf
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] it8716 under 2.6
2006-08-25 6:42 [lm-sensors] it8716 under 2.6 Jean Delvare
2006-08-25 19:45 ` Juergen Kilb
2006-08-25 20:24 ` Rudolf Marek
@ 2006-08-25 21:34 ` Jean Delvare
2006-08-26 10:13 ` Juergen Kilb
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: Jean Delvare @ 2006-08-25 21:34 UTC (permalink / raw)
To: lm-sensors
Hallo J?rgen,
> I gues the expected speed for the fans are:
> CPU-Fan:
> Arctic Cooling Alpine 64 :
> expected speed :2000 RPM
> according to sensors output :4179 RPM
> Bios output :2096 RPM
>
> CHA_FAN 1 is an
> Revoltec AirGuard 120mm, 23.94 dBA
> expected speed :1200 RPM
> according to sensors output :2494 RPM
> Bios output :1256 RPM
>
> PWR_FAN:
> Enermax Liberty EL500AWT 120mm Fan
> expected speed :??? RPM
> according to sensors output :903 RPM /
> Bios output :1256 RPM
Copy-n-paste typo for this last value?
> i would beleive the BIOS values....
Yep everyone seems to agree - I've updated my patch:
http://jdelvare.pck.nerim.net/sensors/hwmon-it8716f-it8718f-v3-2.6.18.patch
Fan readings for fan1 and fan2 should be OK now - not sure about fan3.
Can you test and report?
> > Do the voltages match what the BIOS says if you use the default
> > configuration file?
> >
> Voltages:
> Bios Sensors with default config
> Vcore 1,31V 1,01V (maybe the BIOS value is so high after power up)
Yes, your CPU can change its Vcore depending on frequency.
> 3,3V 3,41V 3,22V (i think it is the voltage called VDDR)
Then just change the label to "+3.3V" in sensors.conf.
> 5V 5,13V 4,78V
> 12V 12,3V 11,46V
> CPU-Temp 26? 24?
> MB-Temp 28? 31?
>
> I think, it doesn't look too bad. Should it be better ?
Hmm, all your voltages are lower in sensors than in the BIOS. We just
had a similar report, however I also had reports where the voltages
match so I think the driver works. I just can't explain this difference
on some Asus boards.
For temperatures it is OK, BIOS is usually in a busy loop so slightly
hotter than Linux at idle.
> Sure here is the complete output of "sensors detect"
> ====================> 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): yes
> Probing for PCI bus adapters...
> Sorry, no PCI bus adapters found.
Ah, hardware is too recent for lm_sensors 2.10.0's sensors-detect. Can
you please pick SVN's version and try again?
http://www.lm-sensors.org/browser/lm-sensors/trunk/prog/detect/sensors-detect?format=txt
Thanks,
--
Jean Delvare
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] it8716 under 2.6
2006-08-25 6:42 [lm-sensors] it8716 under 2.6 Jean Delvare
` (2 preceding siblings ...)
2006-08-25 21:34 ` Jean Delvare
@ 2006-08-26 10:13 ` Juergen Kilb
2006-08-26 21:17 ` Jean Delvare
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: Juergen Kilb @ 2006-08-26 10:13 UTC (permalink / raw)
To: lm-sensors
Hi Jean,
> > according to sensors output :903 RPM /
> > Bios output :1256 RPM
>
> Copy-n-paste typo for this last value?
you are right. Maybe it was to late.
>
> > i would beleive the BIOS values....
>
> Yep everyone seems to agree - I've updated my patch:
> http://jdelvare.pck.nerim.net/sensors/hwmon-it8716f-it8718f-v3-2.6.18.patch
> Fan readings for fan1 and fan2 should be OK now - not sure about fan3.
> Can you test and report?
>
Now it looks like:
snip =======
sensors
it8716-isa-0290
Adapter: ISA adapter
VCore: +1.01 V (min = +0.00 V, max = +4.08 V)
VDDR: +3.22 V (min = +0.00 V, max = +4.08 V)
+3.3V: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
+5V: +4.81 V (min = +0.00 V, max = +6.85 V)
+12V: +11.46 V (min = +0.00 V, max = +16.32 V)
-12V: -16.97 V (min = -16.97 V, max = +4.01 V) ALARM
-5V: -8.78 V (min = -8.78 V, max = +4.05 V) ALARM
5VSB: +4.78 V (min = +0.00 V, max = +6.85 V)
VBat: +2.93 V
CPU_Fan: 2096 RPM (min = 0 RPM)
CHA_Fan1: 1264 RPM (min = 0 RPM)
PWR_Fan: 920 RPM (min = 0 RPM)
CPU Temp: +22?C (low = -1?C, high = +127?C) sensor = diode
MB Temp: +29?C (low = -1?C, high = +127?C) sensor = thermistor
temp3: -5?C (low = -1?C, high = +127?C) sensor = thermistor
vid: +0.30 V
k8temp-pci-00c3
Adapter: PCI adapter
temp1: +30?C
temp3: +22?C
snap======
The all fan speeds are now correct. Great work !
>
> Ah, hardware is too recent for lm_sensors 2.10.0's sensors-detect. Can
> you please pick SVN's version and try again?
>
> http://www.lm-sensors.org/browser/lm-sensors/trunk/prog/detect/sensors-dete
>ct?format=txt
OK, i have tried again with SVN version of "sensors-detect" and here is the
output..
snip========prog/detect/sensors-detect
# sensors-detect revision 4112 (2006-08-25 21:59:29 +0200 (Fr, 25 Aug 2006))
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): yes
Probing for PCI bus adapters...
Use driver `i2c-nforce2' for device 00:01.1: nVidia Corporation nForce4 SMBus
(MCP55)
Probe successfully concluded.
We will now try to load each adapter module in turn.
Module `i2c-nforce2' 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).
Some chips are also accessible through the ISA I/O ports. 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.
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): yes
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 `Winbond W83627DHG'
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 `AMD K8 thermal sensors'
Trying general detect... Success!
(confidence 9, driver `k8temp')
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): yes
Probing for `ITE 8702F Super IO Sensors'
Failed! (0x8716)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0x8716)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0x8716)
Probing for `ITE IT8716F Super IO Sensors'
Success... found at address 0x0290
Probing for `ITE IT8718F Super IO Sensors'
Failed! (0x8716)
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)
Do you want to scan for secondary Super I/O sensors? (YES/no): yes
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)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `k8temp' (should be inserted):
Detects correctly:
* ISA bus, undetermined address (Busdriver `i2c-isa')
Hint: Try forcing the chip address. Consult the documentation
of particular chip for details and address value.
Chip `AMD K8 thermal sensors' (confidence: 9)
Driver `it87' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `ITE IT8716F Super IO Sensors' (confidence: 9)
I will now generate the commands needed to load the required modules.
To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# Chip drivers
# Warning: the required module k8temp is not currently installed on your
system.
# For status of 2.6 kernel ports see
http://www.lm-sensors.org/wiki/SupportedDevices
# If driver is built-in to the kernel, or unavailable, comment out the
following line.
modprobe k8temp
modprobe it87
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----
WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.
Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): n
snap ======
Btw.. do you have any idea, why "i2cdetect" doesnt detect anything.. like the
EEPROMS at the memory modules...
Regards
Juergen
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] it8716 under 2.6
2006-08-25 6:42 [lm-sensors] it8716 under 2.6 Jean Delvare
` (3 preceding siblings ...)
2006-08-26 10:13 ` Juergen Kilb
@ 2006-08-26 21:17 ` Jean Delvare
2006-08-27 14:45 ` Juergen Kilb
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: Jean Delvare @ 2006-08-26 21:17 UTC (permalink / raw)
To: lm-sensors
Hi J?rgen,
> Now it looks like:
>
> snip =======
>
> sensors
> it8716-isa-0290
> Adapter: ISA adapter
> VCore: +1.01 V (min = +0.00 V, max = +4.08 V)
> VDDR: +3.22 V (min = +0.00 V, max = +4.08 V)
> +3.3V: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
> +5V: +4.81 V (min = +0.00 V, max = +6.85 V)
> +12V: +11.46 V (min = +0.00 V, max = +16.32 V)
> -12V: -16.97 V (min = -16.97 V, max = +4.01 V) ALARM
> -5V: -8.78 V (min = -8.78 V, max = +4.05 V) ALARM
> 5VSB: +4.78 V (min = +0.00 V, max = +6.85 V)
> VBat: +2.93 V
> CPU_Fan: 2096 RPM (min = 0 RPM)
> CHA_Fan1: 1264 RPM (min = 0 RPM)
> PWR_Fan: 920 RPM (min = 0 RPM)
> CPU Temp: +22?C (low = -1?C, high = +127?C) sensor = diode
> MB Temp: +29?C (low = -1?C, high = +127?C) sensor = thermistor
> temp3: -5?C (low = -1?C, high = +127?C) sensor = thermistor
> vid: +0.30 V
Voltages look good. in2, in5 and in6 are obviously not wired so you can
add the following lines to your configuration file:
ignore in2
ignore in5
ignore in6
And you can set the proper label for in1:
label in1 "+3.3V"
It also looks like temp3 isn't wired so you can add:
ignore temp3
Lastly, the vid reading is really strange, the value isn't even
possible for your CPU model. I think you are using a slightly older
kernel which lacks this fix:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h\x177d165d7c2ec424007d6241a93d0cb83d953c51
If you can apply this patch, it should fix your vid reading.
> The all fan speeds are now correct. Great work !
Thanks :)
> prog/detect/sensors-detect
> # sensors-detect revision 4112 (2006-08-25 21:59:29 +0200 (Fr, 25 Aug 2006))
>
> 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): yes
> Probing for PCI bus adapters...
> Use driver `i2c-nforce2' for device 00:01.1: nVidia Corporation nForce4 SMBus
> (MCP55)
> Probe successfully concluded.
OK, that's your SMBus.
> We will now try to load each adapter module in turn.
> Module `i2c-nforce2' already loaded.
And the driver is loaded, but...
> 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).
... it doesn't seem to work, else sensors-detect would scan it. Support
for this SMBus master was only added recently, so maybe you need to
apply this patch as well:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h\7ae65899a4c5b05b6277f856018d1eeeb98907
> Btw.. do you have any idea, why "i2cdetect" doesnt detect anything.. like the
> EEPROMS at the memory modules...
Because these are behind the SMBus, and it doesn't work for you yet. If
you can get it to work using the patch above, run sensors-detect gain
and it should find your EEPROMs - and maybe the additional hardware
monitoring chip I suspect you have for the additional fans.
--
Jean Delvare
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] it8716 under 2.6
2006-08-25 6:42 [lm-sensors] it8716 under 2.6 Jean Delvare
` (4 preceding siblings ...)
2006-08-26 21:17 ` Jean Delvare
@ 2006-08-27 14:45 ` Juergen Kilb
2006-08-27 20:06 ` Jean Delvare
2006-08-27 20:33 ` Juergen Kilb
7 siblings, 0 replies; 9+ messages in thread
From: Juergen Kilb @ 2006-08-27 14:45 UTC (permalink / raw)
To: lm-sensors
Hi Jean,
i have now applied the patches you told me.
"sensors" shows now:
snip ==========
it8716-isa-0290
Adapter: ISA adapter
VCore: +1.01 V (min = +0.00 V, max = +4.08 V)
+3.3V: +3.22 V (min = +0.00 V, max = +4.08 V)
+5V: +4.81 V (min = +0.00 V, max = +6.85 V)
+12V: +11.46 V (min = +0.00 V, max = +16.32 V)
5VSB: +4.78 V (min = +0.00 V, max = +6.85 V)
VBat: +2.93 V
CPU_Fan: 2102 RPM (min = 0 RPM)
CHA_Fan1: 1254 RPM (min = 0 RPM)
PWR_Fan: 920 RPM (min = 0 RPM)
CPU Temp: +22?C (low = -1?C, high = +127?C) sensor = diode
MB Temp: +29?C (low = -1?C, high = +127?C) sensor = thermistor
vid: +1.10 V
k8temp-pci-00c3
Adapter: PCI adapter
temp1: +30?C
temp3: +21?C
snap==========
Vid looks now better.
>
> ... it doesn't seem to work, else sensors-detect would scan it. Support
> for this SMBus master was only added recently, so maybe you need to
> apply this patch as well:
>
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=comm
>it;h\7ae65899a4c5b05b6277f856018d1eeeb98907
>
> > Btw.. do you have any idea, why "i2cdetect" doesnt detect anything.. like
> > the EEPROMS at the memory modules...
>
> Because these are behind the SMBus, and it doesn't work for you yet. If
> you can get it to work using the patch above, run sensors-detect gain
> and it should find your EEPROMs - and maybe the additional hardware
> monitoring chip I suspect you have for the additional fans.
Ok now with the patches, two EEPROMS and some other devices were found...
What devices are at address 0x08, 0x0c, 0x22, 0x2e, 0x30, 0x31 and 0x50 ??
Is there an device for the other fan's ?
snip-==========
sensors-detect
# sensors-detect revision 4112 (2006-08-25 21:59:29 +0200 (Fr, 25 Aug 2006))
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): yes
Probing for PCI bus adapters...
Use driver `i2c-nforce2' for device 00:01.1: nVidia Corporation nForce4 SMBus
(MCP55)
Probe successfully concluded.
We will now try to load each adapter module in turn.
Module `i2c-nforce2' 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 nForce2 adapter at 1c40
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x08
Client found at address 0x0c
Client found at address 0x22
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83627HF'... Failed!
Client found at address 0x2e
Probing for `Myson MTP008'... Failed!
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `National Semiconductor LM85 or LM96000'... Failed!
Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... Failed!
Probing for `SMSC EMC6D100, EMC6D101 or EMC6D102'... Failed!
Probing for `Analog Devices ADT7467 or ADT7468'... Failed!
Probing for `Analog Devices ADT7476'... Failed!
Probing for `National Semiconductor LM87'... Failed!
Probing for `National Semiconductor LM93'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83792D'... Failed!
Probing for `Winbond W83793R/G'... Failed!
Probing for `Winbond W83791SD'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Winbond W83627EHF'... Failed!
Probing for `Winbond W83627DHG'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Winbond W83L785TS-S'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1026'... Failed!
Probing for `Analog Devices ADM1025'... Failed!
Probing for `Analog Devices ADM1024'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `Analog Devices ADM1030'... Failed!
Probing for `Analog Devices ADM1031'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `Analog Devices ADM1028'... Failed!
Probing for `ITE IT8712F'... Failed!
Probing for `Fintek F75373S/SG'... Failed!
Probing for `Fintek F75375S/SP'... Failed!
Probing for `Fintek F75387SG/RG'... Failed!
Probing for `Winbond W83791D'... Failed!
Next adapter: SMBus nForce2 adapter at 1c00
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x08
Client found at address 0x30
Client found at address 0x31
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `EDID EEPROM'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Some chips are also accessible through the ISA I/O ports. 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.
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): yes
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 `Winbond W83627DHG'
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 `AMD K8 thermal sensors'
Trying general detect... Success!
(confidence 9, driver `k8temp')
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): yes
Probing for `ITE 8702F Super IO Sensors'
Failed! (0x8716)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0x8716)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0x8716)
Probing for `ITE IT8716F Super IO Sensors'
Success... found at address 0x0290
Probing for `ITE IT8718F Super IO Sensors'
Failed! (0x8716)
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)
Do you want to scan for secondary Super I/O sensors? (YES/no): yes
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)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus nForce2 adapter at 1c00'
Busdriver `i2c-nforce2', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus nForce2 adapter at 1c00'
Busdriver `i2c-nforce2', I2C address 0x51
Chip `SPD EEPROM' (confidence: 8)
EEPROMs are *NOT* sensors! They are data storage chips commonly
found on memory modules (SPD), in monitors (EDID), or in some
laptops, for example.
Driver `k8temp' (should be inserted):
Detects correctly:
* ISA bus, undetermined address (Busdriver `i2c-isa')
Hint: Try forcing the chip address. Consult the documentation
of particular chip for details and address value.
Chip `AMD K8 thermal sensors' (confidence: 9)
Driver `it87' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `ITE IT8716F Super IO Sensors' (confidence: 9)
I will now generate the commands needed to load the required modules.
To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-nforce2
modprobe i2c-isa
# Chip drivers
modprobe eeprom
# Warning: the required module k8temp is not currently installed on your
system.
# For status of 2.6 kernel ports see
http://www.lm-sensors.org/wiki/SupportedDevices
# If driver is built-in to the kernel, or unavailable, comment out the
following line.
modprobe k8temp
modprobe it87
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----
WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.
Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): no
snap =========
==
Juergen
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] it8716 under 2.6
2006-08-25 6:42 [lm-sensors] it8716 under 2.6 Jean Delvare
` (5 preceding siblings ...)
2006-08-27 14:45 ` Juergen Kilb
@ 2006-08-27 20:06 ` Jean Delvare
2006-08-27 20:33 ` Juergen Kilb
7 siblings, 0 replies; 9+ messages in thread
From: Jean Delvare @ 2006-08-27 20:06 UTC (permalink / raw)
To: lm-sensors
Hi J?rgen,
> Hi Jean,
> i have now applied the patches you told me.
>
> "sensors" shows now:
>
> snip ==========
> it8716-isa-0290
> Adapter: ISA adapter
> VCore: +1.01 V (min = +0.00 V, max = +4.08 V)
> +3.3V: +3.22 V (min = +0.00 V, max = +4.08 V)
> +5V: +4.81 V (min = +0.00 V, max = +6.85 V)
> +12V: +11.46 V (min = +0.00 V, max = +16.32 V)
> 5VSB: +4.78 V (min = +0.00 V, max = +6.85 V)
> VBat: +2.93 V
> CPU_Fan: 2102 RPM (min = 0 RPM)
> CHA_Fan1: 1254 RPM (min = 0 RPM)
> PWR_Fan: 920 RPM (min = 0 RPM)
> CPU Temp: +22?C (low = -1?C, high = +127?C) sensor = diode
> MB Temp: +29?C (low = -1?C, high = +127?C) sensor = thermistor
> vid: +1.10 V
>
> k8temp-pci-00c3
> Adapter: PCI adapter
> temp1: +30?C
> temp3: +21?C
> snap==========
>
> Vid looks now better.
Yep, looks alright to me now :) You're lucky, out of 4 boards with the
IT8716F chip, this is the only one with valid VID readings...
> Ok now with the patches, two EEPROMS and some other devices were found...
> What devices are at address 0x08, 0x0c, 0x22, 0x2e, 0x30, 0x31 and 0x50 ??
> Is there an device for the other fan's ?
The chip at 0x2e is most certainly a second hardware monitoring chip. I
just found out that the Asus M2N32-SLI has an Analog Devices ADT7475
for the additional fans, I would suspect that your board are the same
or a very similar chip.
I added detection of a bunch of new Analog Devices chips to
sensors-detect a few minutes ago, can you please fetch it, give it a
try and report?
> # Warning: the required module k8temp is not currently installed on your system.
> # For status of 2.6 kernel ports see http://www.lm-sensors.org/wiki/SupportedDevices
> # If driver is built-in to the kernel, or unavailable, comment out the following line.
> modprobe k8temp
For this one you can pick these patches:
http://khali.linux-fr.org/devel/i2c/linux-2.6/hwmon-k8temp-new-driver.patch
http://khali.linux-fr.org/devel/i2c/linux-2.6/hwmon-k8temp-autoload.patch
Thanks,
--
Jean Delvare
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] it8716 under 2.6
2006-08-25 6:42 [lm-sensors] it8716 under 2.6 Jean Delvare
` (6 preceding siblings ...)
2006-08-27 20:06 ` Jean Delvare
@ 2006-08-27 20:33 ` Juergen Kilb
7 siblings, 0 replies; 9+ messages in thread
From: Juergen Kilb @ 2006-08-27 20:33 UTC (permalink / raw)
To: lm-sensors
Hi Jean,
here it is...
It seems that you are right. The script founds a ADT7475!!
====
prog/detect/sensors-detect
# sensors-detect revision 4116 (2006-08-27 21:51:38 +0200 (So, 27 Aug 2006))
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): yes
Probing for PCI bus adapters...
Use driver `i2c-nforce2' for device 00:01.1: nVidia Corporation nForce4 SMBus
(MCP55)
Probe successfully concluded.
We will now try to load each adapter module in turn.
Module `i2c-nforce2' 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 nForce2 adapter at 1c40
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x08
Client found at address 0x0c
Client found at address 0x22
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83627HF'... Failed!
Client found at address 0x2e
Probing for `Myson MTP008'... Failed!
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `National Semiconductor LM85 or LM96000'... Failed!
Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... Failed!
Probing for `SMSC EMC6D100, EMC6D101 or EMC6D102'... Failed!
Probing for `Analog Devices ADT7462'... Failed!
Probing for `Analog Devices ADT7467 or ADT7468'... Failed!
Probing for `Analog Devices ADT7470'... Failed!
Probing for `Analog Devices ADT7473'... Failed!
Probing for `Analog Devices ADT7475'... Success!
(confidence 5, driver `to-be-written')
Probing for `Analog Devices ADT7476'... Failed!
Probing for `National Semiconductor LM87'... Failed!
Probing for `National Semiconductor LM93'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83792D'... Failed!
Probing for `Winbond W83793R/G'... Failed!
Probing for `Winbond W83791SD'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Winbond W83627EHF'... Failed!
Probing for `Winbond W83627DHG'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Winbond W83L785TS-S'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1026'... Failed!
Probing for `Analog Devices ADM1025'... Failed!
Probing for `Analog Devices ADM1024'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `Analog Devices ADM1030'... Failed!
Probing for `Analog Devices ADM1031'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `Analog Devices ADM1028'... Failed!
Probing for `ITE IT8712F'... Failed!
Probing for `Fintek F75373S/SG'... Failed!
Probing for `Fintek F75375S/SP'... Failed!
Probing for `Fintek F75387SG/RG'... Failed!
Probing for `Winbond W83791D'... Failed!
Next adapter: SMBus nForce2 adapter at 1c00
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x08
Client found at address 0x30
Client found at address 0x31
Client found at address 0x50
Probing for `Analog Devices ADM1033'... Failed!
Probing for `Analog Devices ADM1034'... Failed!
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `EDID EEPROM'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x51
Probing for `Analog Devices ADM1033'... Failed!
Probing for `Analog Devices ADM1034'... Failed!
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Some chips are also accessible through the ISA I/O ports. 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.
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): yes
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 `Winbond W83627DHG'
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 `AMD K8 thermal sensors'
Trying general detect... Success!
(confidence 9, driver `k8temp')
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): yes
Probing for `ITE 8702F Super IO Sensors'
Failed! (0x8716)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0x8716)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0x8716)
Probing for `ITE IT8716F Super IO Sensors'
Success... found at address 0x0290
Probing for `ITE IT8718F Super IO Sensors'
Failed! (0x8716)
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)
Do you want to scan for secondary Super I/O sensors? (YES/no): yes
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)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `to-be-written' (should be inserted):
Detects correctly:
* Bus `SMBus nForce2 adapter at 1c40'
Busdriver `i2c-nforce2', I2C address 0x2e
Chip `Analog Devices ADT7475' (confidence: 5)
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus nForce2 adapter at 1c00'
Busdriver `i2c-nforce2', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus nForce2 adapter at 1c00'
Busdriver `i2c-nforce2', I2C address 0x51
Chip `SPD EEPROM' (confidence: 8)
EEPROMs are *NOT* sensors! They are data storage chips commonly
found on memory modules (SPD), in monitors (EDID), or in some
laptops, for example.
Driver `k8temp' (should be inserted):
Detects correctly:
* ISA bus, undetermined address (Busdriver `i2c-isa')
Hint: Try forcing the chip address. Consult the documentation
of particular chip for details and address value.
Chip `AMD K8 thermal sensors' (confidence: 9)
Driver `it87' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `ITE IT8716F Super IO Sensors' (confidence: 9)
I will now generate the commands needed to load the required modules.
To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-nforce2
modprobe i2c-isa
# Chip drivers
# no driver for Analog Devices ADT7475 yet
modprobe eeprom
# Warning: the required module k8temp is not currently installed on your
system.
# For status of 2.6 kernel ports see
http://www.lm-sensors.org/wiki/SupportedDevices
# If driver is built-in to the kernel, or unavailable, comment out the
following line.
modprobe k8temp
modprobe it87
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----
WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.
Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): n
===> > # Warning: the required module k8temp is not currently installed on your
> > system. # For status of 2.6 kernel ports see
> > http://www.lm-sensors.org/wiki/SupportedDevices # If driver is built-in
> > to the kernel, or unavailable, comment out the following line. modprobe
> > k8temp
>
> For this one you can pick these patches:
> http://khali.linux-fr.org/devel/i2c/linux-2.6/hwmon-k8temp-new-driver.patch
> http://khali.linux-fr.org/devel/i2c/linux-2.6/hwmon-k8temp-autoload.patch
>
> Thanks,
I will try these patches tomorrow.
good night...
Juergen
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2006-08-27 20:33 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-25 6:42 [lm-sensors] it8716 under 2.6 Jean Delvare
2006-08-25 19:45 ` Juergen Kilb
2006-08-25 20:24 ` Rudolf Marek
2006-08-25 21:34 ` Jean Delvare
2006-08-26 10:13 ` Juergen Kilb
2006-08-26 21:17 ` Jean Delvare
2006-08-27 14:45 ` Juergen Kilb
2006-08-27 20:06 ` Jean Delvare
2006-08-27 20:33 ` Juergen Kilb
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.