From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mahmood Naderan Date: Wed, 01 Sep 2010 07:30:00 +0000 Subject: Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors Message-Id: <839121.11578.qm@web50006.mail.re2.yahoo.com> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============5905773394260373541==" List-Id: References: <929339.59525.qm@web50002.mail.re2.yahoo.com> In-Reply-To: <929339.59525.qm@web50002.mail.re2.yahoo.com> To: lm-sensors@vger.kernel.org --===============5905773394260373541== Content-Type: multipart/alternative; boundary="0-1350264016-1283326200=:11578" --0-1350264016-1283326200=:11578 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Here is what I did:=0Amahmood@localhost:~$ svn checkout http://lm-sensors.o= rg/svn/lm-sensors/trunk =0Alm-sensors=0A...=0AChecked out revision 5857.=0A= =A0=0Amahmood@localhost:~$ svn update http://lm-sensors.org/svn/lm-sensors/= trunk =0Alm-sensors=0ASkipped 'http://lm-sensors.org/svn/lm-sensors/trunk'= =0AAt revision 5857.=0ASummary of conflicts:=0A=A0 Skipped paths: 1=0A=0AIs= that what you meant?=0A// Naderan *Mahmood;=0A=0A=0A=0A=0A________________= ________________=0AFrom: Nikola Pajkovsky =0ATo: lm-se= nsors@lm-sensors.org=0ASent: Wed, September 1, 2010 11:49:03 AM=0ASubject: = Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors=0A=0AOn 09/01/201= 0 08:38 AM, Mahmood Naderan wrote:=0A> Dear all,=0A>=0A> I ran sensors-dete= ct to detect Core-i7 temperatures but it doesn't show them. =0A>Here is the= output of sensors-detect:=0A>=0A>=0A> mahmood@localhost:~$ sudo sensors-de= tect=0A> # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)=0A> # S= ystem: Gigabyte Technology Co., Ltd. P55-USB3=0A>=0A> This program will hel= p you determine which kernel modules you need=0A> to load to use lm_sensors= most effectively. It is generally safe=0A> and recommended to accept the d= efault answers to all questions,=0A> unless you know what you're doing.=0A>= =0A> Some south bridges, CPUs or memory controllers contain embedded sensor= s.=0A> Do you want to scan for them? This is totally safe. (YES/no): y=0A> = Silicon Integrated Systems SIS5595... No=0A> VIA VT82C686 Integrated Sensor= s... No=0A> VIA VT8231 Integrated Sensors... No=0A> AMD K8 thermal sensors.= .. No=0A> AMD Family 10h thermal sensors... No=0A> AMD Family 11h thermal s= ensors... No=0A> Intel Core family thermal sensor... No=0A> Intel Atom ther= mal sensor... No=0A> Intel AMB FB-DIMM thermal sensor... No=0A> VIA C7 ther= mal sensor... No=0A> VIA Nano thermal sensor... No=0A>=0A> Some Super I/O c= hips contain embedded sensors. We have to write to=0A> standard I/O ports t= o probe them. This is usually safe.=0A> Do you want to scan for Super I/O s= ensors? (YES/no): y=0A> Probing for Super-I/O at 0x2e/0x2f=0A> Trying famil= y `National Semiconductor'... No=0A> Trying family `SMSC'... No=0A> Trying = family `VIA/Winbond/Nuvoton/Fintek'... No=0A> Trying family `ITE'... Yes=0A= > Found `ITE IT8720F Super IO Sensors' Success!=0A> (address 0x290, driver = `it87')=0A> Probing for Super-I/O at 0x4e/0x4f=0A> Trying family `National = Semiconductor'... No=0A> Trying family `SMSC'... No=0A> Trying family `VIA/= Winbond/Nuvoton/Fintek'... No=0A> Trying family `ITE'... No=0A>=0A> Some sy= stems (mainly servers) implement IPMI, a set of common interfaces=0A> throu= gh which system health data may be retrieved, amongst other things.=0A> We = first try to get the information from SMBIOS. If we don't find it=0A> there= , we have to read from arbitrary I/O ports to probe for such=0A> interfaces= . This is normally safe. Do you want to scan for IPMI=0A> interfaces? (YES/= no): y=0A> Probing for `IPMI BMC KCS' at 0xca0... No=0A> Probing for `IPMI = BMC SMIC' at 0xca8... No=0A>=0A> Some hardware monitoring chips are accessi= ble through the ISA I/O ports.=0A> We have to write to arbitrary I/O ports = to probe them. This is usually=0A> safe though. Yes, you do have ISA I/O po= rts even if you do not have any=0A> ISA slots! Do you want to scan the ISA = I/O ports? (yes/NO): y=0A> Probing for `National Semiconductor LM78' at 0x2= 90... No=0A> Probing for `National Semiconductor LM79' at 0x290... No=0A> P= robing for `Winbond W83781D' at 0x290... No=0A> Probing for `Winbond W83782= D' at 0x290... No=0A>=0A> Lastly, we can probe the I2C/SMBus adapters for c= onnected hardware=0A> monitoring devices. This is the most risky part, and = while it works=0A> reasonably well on most systems, it has been reported to= cause trouble=0A> on some systems.=0A> Do you want to probe the I2C/SMBus = adapters now? (YES/no): y=0A> Found unknown SMBus adapter 8086:3b30 at 0000= :00:1f.3.=0A> Sorry, no supported PCI bus adapters found.=0A> Module i2c-de= v loaded successfully.=0A>=0A> Now follows a summary of the probes I have j= ust done.=0A> Just press ENTER to continue:=0A>=0A> Driver `it87':=0A> * IS= A bus, address 0x290=0A> Chip `ITE IT8720F Super IO Sensors' (confidence: 9= )=0A>=0A> To load everything that is needed, add this to /etc/modules:=0A> = #----cut here----=0A> # Chip drivers=0A> it87=0A> #----cut here----=0A> If = you have some drivers built into your kernel, the list above will=0A> conta= in too many modules. Skip the appropriate ones!=0A>=0A> Do you want to add = these lines automatically to /etc/modules? (yes/NO)yes=0A> Successful!=0A>= =0A> Monitoring programs won't work until the needed modules are=0A> loaded= . You may want to run '/etc/init.d/module-init-tools start'=0A> to load the= m.=0A>=0A> Unloading i2c-dev... OK=0A>=0A>=0A> Then I ran sensors:=0A>=0A> = mahmood@localhost:~$ sudo sensors=0A> it8720-isa-0290=0A> Adapter: ISA adap= ter=0A> in0: +0.86 V (min =3D +0.00 V, max =3D +4.08 V)=0A> in1: +1.58 V (m= in =3D +0.00 V, max =3D +4.08 V)=0A> in2: +3.39 V (min =3D +0.00 V, max =3D= +4.08 V)=0A> in3: +3.02 V (min =3D +0.00 V, max =3D +4.08 V)=0A> in4: +0.0= 5 V (min =3D +0.00 V, max =3D +4.08 V) ALARM=0A> in5: +3.12 V (min =3D +0.0= 0 V, max =3D +4.08 V)=0A> in6: +0.02 V (min =3D +0.00 V, max =3D +4.08 V) A= LARM=0A> in7: +2.16 V (min =3D +0.00 V, max =3D +4.08 V)=0A> Vbat: +3.10 V= =0A> fan1: 1679 RPM (min =3D 10 RPM)=0A> fan2: 644 RPM (min =3D 0 RPM)=0A> = fan3: 1278 RPM (min =3D 10 RPM)=0A> fan4: 1205 RPM (min =3D 0 RPM)=0A> temp= 1: +36.0=C2=B0C (low =3D +127.0=C2=B0C, high =3D +127.0=C2=B0C) sensor =3D = thermistor=0A> temp2: +25.0=C2=B0C (low =3D +127.0=C2=B0C, high =3D +127.0= =C2=B0C) sensor =3D thermistor=0A> temp3: +33.0=C2=B0C (low =3D +127.0=C2= =B0C, high =3D +90.0=C2=B0C) sensor =3D thermistor=0A> cpu0_vid: +0.313 V= =0A>=0A>=0A> What can I do then? currently I have kubuntu 10.04=0A>=0A> *//= Naderan *Mahmood;*=0A>=0A>=0A=0APick sensors-detect from svn or file bug a= gainst lm-sensors in ubuntu and =0Amaintainer(if he is nice) update lm-sens= ors.=0A=0A_______________________________________________=0Alm-sensors mail= ing list=0Alm-sensors@lm-sensors.org=0Ahttp://lists.lm-sensors.org/mailman/= listinfo/lm-sensors=0A=0A=0A=0A --0-1350264016-1283326200=:11578 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
=0A
Here is what I did:
=0A
mahmood@localhost:~$ svn checkout http://lm-sensors.org/sv= n/lm-sensors/trunk lm-sensors
=0A
...
Checked out revision = 5857.
 
=0A
mahmoo= d@localhost:~$ svn update http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
Skip= ped 'http://lm-sensors.org/svn/lm-sensors/trunk'
At revision 5857.
Su= mmary of conflicts:
  Skipped paths: 1
=0A
Is that what you meant?=
=0A
=0A
// Naderan *Mah= mood;
=0A

=0A

=0A
=0A
=0AFrom: Nikola Pajkovsky <npajkovs@redhat.co= m>
To: lm-sensors@lm-= sensors.org
Sent: Wed, S= eptember 1, 2010 11:49:03 AM
Subjec= t: Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
=
On 09/01/2010 08:38 AM, Mahmood Naderan wrote:
> Dear all,=
>
> I ran sensors-detect to detect Core-i7 temperatures but it= doesn't show them. Here is the output of sensors-detect:
>
>> mahmood@localhost:~$ sudo sensors-detect
> # sensors-detect re= vision 5818 (2010-01-18 17:22:07 +0100)
> # System: Gigabyte Technolo= gy Co., Ltd. P55-USB3
>
> This program will help you determine = which kernel modules you need
> to load to use lm_sensors most effect= ively. It is generally safe
> and recommended to accept the default answers to all questions,
> unless you know what = you're doing.
>
> Some south bridges, CPUs or memory controller= s contain embedded sensors.
> Do you want to scan for them? This is t= otally safe. (YES/no): y
> Silicon Integrated Systems SIS5595... No> VIA VT82C686 Integrated Sensors... No
> VIA VT8231 Integrated = Sensors... No
> AMD K8 thermal sensors... No
> AMD Family 10h t= hermal sensors... No
> AMD Family 11h thermal sensors... No
> I= ntel Core family thermal sensor... No
> Intel Atom thermal sensor... = No
> Intel AMB FB-DIMM thermal sensor... No
> VIA C7 thermal se= nsor... No
> VIA Nano thermal sensor... No
>
> Some Super= I/O chips contain embedded sensors. We have to write to
> standard I= /O ports to probe them. This is usually safe.
> Do you want to scan f= or Super I/O sensors? (YES/no): y
> Probing for Super-I/O at 0x2e/0x2f
> Trying family `National Semiconductor'... No
> Try= ing family `SMSC'... No
> Trying family `VIA/Winbond/Nuvoton/Fintek'.= .. No
> Trying family `ITE'... Yes
> Found `ITE IT8720F Super I= O Sensors' Success!
> (address 0x290, driver `it87')
> Probing = for Super-I/O at 0x4e/0x4f
> Trying family `National Semiconductor'..= . No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/= Nuvoton/Fintek'... No
> Trying family `ITE'... No
>
> Som= e systems (mainly servers) implement IPMI, a set of common interfaces
&g= t; through which system health data may be retrieved, amongst other things.=
> We first try to get the information from SMBIOS. If we don't find = it
> there, we have to read from arbitrary I/O ports to probe for suc= h
> interfaces. This is normally safe. Do you want to scan for IPMI> interfaces? (YES/no): y
> Probing for `IPMI BMC KCS' at 0xca0... No
> Probing for `IPMI BMC SMIC' at 0xca8... No
>
= > Some hardware monitoring chips are accessible through the ISA I/O port= s.
> We have to write to arbitrary I/O ports to probe them. This is u= sually
> safe though. Yes, you do have ISA I/O ports even if you do n= ot have any
> ISA slots! Do you want to scan the ISA I/O ports? (yes/= NO): y
> Probing for `National Semiconductor LM78' at 0x290... No
= > Probing for `National Semiconductor LM79' at 0x290... No
> Probi= ng for `Winbond W83781D' at 0x290... No
> Probing for `Winbond W83782= D' at 0x290... No
>
> Lastly, we can probe the I2C/SMBus adapte= rs for connected hardware
> monitoring devices. This is the most risk= y part, and while it works
> reasonably well on most systems, it has = been reported to cause trouble
> on some systems.
> Do you want= to probe the I2C/SMBus adapters now? (YES/no): y
> Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
> Sorry, no support= ed PCI bus adapters found.
> Module i2c-dev loaded successfully.
&= gt;
> Now follows a summary of the probes I have just done.
> J= ust press ENTER to continue:
>
> Driver `it87':
> * ISA b= us, address 0x290
> Chip `ITE IT8720F Super IO Sensors' (confidence: = 9)
>
> To load everything that is needed, add this to /etc/modu= les:
> #----cut here----
> # Chip drivers
> it87
> = #----cut here----
> If you have some drivers built into your kernel, = the list above will
> contain too many modules. Skip the appropriate = ones!
>
> Do you want to add these lines automatically to /etc/= modules? (yes/NO)yes
> Successful!
>
> Monitoring program= s won't work until the needed modules are
> loaded. You may want to r= un '/etc/init.d/module-init-tools start'
> to load them.
>
> Unloading i2c-dev... OK
>
>
> Then= I ran sensors:
>
> mahmood@localhost:~$ sudo sensors
> i= t8720-isa-0290
> Adapter: ISA adapter
> in0: +0.86 V (min =3D += 0.00 V, max =3D +4.08 V)
> in1: +1.58 V (min =3D +0.00 V, max =3D +4.= 08 V)
> in2: +3.39 V (min =3D +0.00 V, max =3D +4.08 V)
> in3: = +3.02 V (min =3D +0.00 V, max =3D +4.08 V)
> in4: +0.05 V (min =3D +0= .00 V, max =3D +4.08 V) ALARM
> in5: +3.12 V (min =3D +0.00 V, max = =3D +4.08 V)
> in6: +0.02 V (min =3D +0.00 V, max =3D +4.08 V) ALARM<= BR>> in7: +2.16 V (min =3D +0.00 V, max =3D +4.08 V)
> Vbat: +3.10= V
> fan1: 1679 RPM (min =3D 10 RPM)
> fan2: 644 RPM (min =3D 0= RPM)
> fan3: 1278 RPM (min =3D 10 RPM)
> fan4: 1205 RPM (min = =3D 0 RPM)
> temp1: +36.0=C2=B0C (low =3D +127.0=C2=B0C, high =3D +12= 7.0=C2=B0C) sensor =3D thermistor
> temp2: +25.0=C2=B0C (low =3D +127= .0=C2=B0C, high =3D +127.0=C2=B0C) sensor =3D thermistor
> temp3: +33.0=C2=B0C (low =3D +127.0=C2=B0C, high =3D +9= 0.0=C2=B0C) sensor =3D thermistor
> cpu0_vid: +0.313 V
>
>= ;
> What can I do then? currently I have kubuntu 10.04
>
>= ; *// Naderan *Mahmood;*
>
>

Pick sensors-detect from sv= n or file bug against lm-sensors in ubuntu and maintainer(if he is nice) up= date lm-sensors.

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

=0A=0A=0A=0A=0A=0A=0A=0A --0-1350264016-1283326200=:11578-- --===============5905773394260373541== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lm-sensors mailing list lm-sensors@lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors --===============5905773394260373541==--