subject:"sensors"

On Monday 18 January 2021 14:47:03 0...@caiway.net wrote:

> On Sun, 17 Jan 2021 23:47:48 -0500
>
> Gene Heskett  wrote:
> > Greetings all;
> >
> > Cheers, Gene Heskett
>
> cpu=$( temperature: $((cpu/100)) Celsius"   | sed 's/\B[0-9]\{1\}\>/,&/'
>
> This oneliner works on pi3 and pi4
>
>
> I use this oneliner for some color:
> cpu=$( temperature: \e[31m  $((cpu/100)) Celsius \e[0m"   | sed
> 's/\B[0-9]\{1\}\>/,&/'
>
> Or in a script:
>
> #!/bin/bash
> cpu=$( echo -e "CPU temperatuur: \e[31m  $((cpu/100)) Celsius \e[0m" | sed 
> 's/\B[0-9]\{1\}\>/,&/'
> #eof
>
> hope this helps

it does, thanks.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page

Re: What is the command to access the temp sensors in a rpi4?

2021-01-18 Thread 0...@caiway.net

On Sun, 17 Jan 2021 23:47:48 -0500
Gene Heskett  wrote:

> Greetings all;

> Cheers, Gene Heskett

cpu=$(/,&/'

This oneliner works on pi3 and pi4


I use this oneliner for some color:
cpu=$(/,&/'

Or in a script:

#!/bin/bash
cpu=$(/,&/' 
#eof

hope this helps

Re: What is the command to access the temp sensors in a rpi4?

On Monday 18 January 2021 13:55:44 Eduardo M KALINOWSKI wrote:

> On 18/01/2021 15:35, Gene Heskett wrote:
> > On Monday 18 January 2021 12:15:00 Stefan Monnier wrote:
> >>> ISTR there is a "vcg*" sort of thing to read that stuff, but have
> >>> lost it in the fog of time.
> >>
> >> If the kernel is sane, then I think that the following command
> >> should give you this info:
> >>
> >>  sensors
> >
> > This kernel isn't "sane": 4.19.71-rt24-v7l+ #1 SMP PREEMPT RT
> >
> >> it comes from the `lm-sensors` package.
> >
> > Returns a null.
>
> In my RPI4, running stock Debian from https://raspi.debian.net/,
> sensors works:
>
> $ sensors
> cpu_thermal-virtual-0
> Adapter: Virtual device
> temp1:+43.8°C  (crit = +90.0°C)

After running sensors-detect, I get:

rpi_volt-isa-
Adapter: ISA adapter
in0:  N/A

So I assume that module wasn't built. I built that kernel.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

Re: What is the command to access the temp sensors in a rpi4?

2021-01-18 Thread Miguel A. Vallejo

Do not forget for sensors to work you must first run sensors-detect

Greetings

El lun, 18 ene 2021 a las 20:11, Eduardo M KALINOWSKI
() escribió:
>
> On 18/01/2021 15:35, Gene Heskett wrote:
> > On Monday 18 January 2021 12:15:00 Stefan Monnier wrote:
> >
> >>> ISTR there is a "vcg*" sort of thing to read that stuff, but have
> >>> lost it in the fog of time.
> >>
> >> If the kernel is sane, then I think that the following command should
> >> give you this info:
> >>
> >>  sensors
> > This kernel isn't "sane": 4.19.71-rt24-v7l+ #1 SMP PREEMPT RT
> >
> >> it comes from the `lm-sensors` package.
> > Returns a null.
> >>
> >>
>
> In my RPI4, running stock Debian from https://raspi.debian.net/, sensors
> works:
>
> $ sensors
> cpu_thermal-virtual-0
> Adapter: Virtual device
> temp1:+43.8°C  (crit = +90.0°C)
>
>
>
> --
> Linux é user-friendly e não idiota friendly. Se você não entende isso,
> use o Windows!
>
> Eduardo M KALINOWSKI
> edua...@kalinowski.com.br
>

Re: What is the command to access the temp sensors in a rpi4?

2021-01-18 Thread Eduardo M KALINOWSKI


On 18/01/2021 15:35, Gene Heskett wrote:

On Monday 18 January 2021 12:15:00 Stefan Monnier wrote:


ISTR there is a "vcg*" sort of thing to read that stuff, but have
lost it in the fog of time.


If the kernel is sane, then I think that the following command should
give you this info:

     sensors

This kernel isn't "sane": 4.19.71-rt24-v7l+ #1 SMP PREEMPT RT


it comes from the `lm-sensors` package.

Returns a null.





In my RPI4, running stock Debian from https://raspi.debian.net/, sensors 
works:


$ sensors
cpu_thermal-virtual-0
Adapter: Virtual device
temp1:+43.8°C  (crit = +90.0°C)



--
Linux é user-friendly e não idiota friendly. Se você não entende isso, 
use o Windows!


Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: What is the command to access the temp sensors in a rpi4?

On Monday 18 January 2021 13:39:36 Stefan Monnier wrote:

> >> > ISTR there is a "vcg*" sort of thing to read that stuff, but have
> >> > lost it in the fog of time.
> >>
> >> If the kernel is sane, then I think that the following command
> >> should give you this info:
> >> sensors
> >
> > This kernel isn't "sane": 4.19.71-rt24-v7l+ #1 SMP PREEMPT RT
>
> This doesn't say whether it's sane or not.  The question is whether
> the driver for the temp sensor is using the standard kernel
> infrastructure or whether it reinvented the wheel.
>
Its armhf Stefan, not wintel. lm_sensors is built for it, and its 
installled by buster but apparently the kernel abi is different.
sensors-detect does not detect it.

> Stefan


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

Re: What is the command to access the temp sensors in a rpi4?

2021-01-18 Thread Stefan Monnier

>> > ISTR there is a "vcg*" sort of thing to read that stuff, but have
>> > lost it in the fog of time.
>> If the kernel is sane, then I think that the following command should
>> give you this info:
>> sensors
> This kernel isn't "sane": 4.19.71-rt24-v7l+ #1 SMP PREEMPT RT

This doesn't say whether it's sane or not.  The question is whether the
driver for the temp sensor is using the standard kernel infrastructure
or whether it reinvented the wheel.


Stefan

Re: What is the command to access the temp sensors in a rpi4?

On Monday 18 January 2021 12:15:00 Stefan Monnier wrote:

> > ISTR there is a "vcg*" sort of thing to read that stuff, but have
> > lost it in the fog of time.
>
> If the kernel is sane, then I think that the following command should
> give you this info:
>
> sensors
This kernel isn't "sane": 4.19.71-rt24-v7l+ #1 SMP PREEMPT RT

> it comes from the `lm-sensors` package.
Returns a null.
>
>
Thank you, Stefan


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

Re: What is the command to access the temp sensors in a rpi4?

2021-01-18 Thread Stefan Monnier

> ISTR there is a "vcg*" sort of thing to read that stuff, but have lost it 
> in the fog of time.

If the kernel is sane, then I think that the following command should
give you this info:

sensors

it comes from the `lm-sensors` package.


Stefan

Re: What is the command to access the temp sensors in a rpi4?

2021-01-18 Thread Anssi Saari

Gene Heskett  writes:

> Greetings all;
>
> ISTR there is a "vcg*" sort of thing to read that stuff, but have lost it 
> in the fog of time.

vcgencmd measure_temp

Or has that changed? I don't have a Pi 4, just a 3B and 3B+.

Re: What is the command to access the temp sensors in a rpi4?

2021-01-18 Thread deloptes

Gene Heskett wrote:

>> vcgencmd get_throttled
> 0x0

means no trottle occured (see below)

>> https://www.raspberrypi.org/forums/viewtopic.php?t=190584
> 
> That "forum" is NOT a list. And I've changed browsers, losing all my
> passwds. So while I can read it, I can't post.
> 

I mean the raspberry pi forum hosted on comp.sys - sorry for misleading you

> And I am wondering where the man page for vcgencmd might be?
> 

from what I see it is not exactly documented

> Searching for that, I found a page that describes it, then found a blog
> by Jeff Geerling on make a pi4 boot from an ssd, which killed a good
> sized tree, but might get me going there.
> 
yes, the usual open source & free software stuff


https://www.8086.net/tools/decode-get_throttled?d=0x0

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
| | | | | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | | | └ Under-voltage detected
| | | | | | | | | | | | | | | | | | └ Arm frequency capped
| | | | | | | | | | | | | | | | | └ Currently throttled
| | | | | | | | | | | | | | | | └ Soft temperature limit active
| | | | | | | | | | | | | | | └ 
| | | | | | | | | | | | | | └ 
| | | | | | | | | | | | | └ 
| | | | | | | | | | | | └ 
| | | | | | | | | | | └ 
| | | | | | | | | | └ 
| | | | | | | | | └ 
| | | | | | | | └ 
| | | | | | | └ 
| | | | | | └ 
| | | | | └ 
| | | | └ 
| | | └ Under-voltage has occurred
| | └ Arm frequency capped has occurred
| └ Throttling has occurred
└ Soft temperature limit has occurred

Re: What is the command to access the temp sensors in a rpi4?

On Monday 18 January 2021 03:11:56 deloptes wrote:

> Gene Heskett wrote:
> > ISTR there is a "vcg*" sort of thing to read that stuff, but have
> > lost it in the fog of time.
> >
> > Cheers, Gene Heskett
>
> Hi Gene,
> why not ask on the RPI list - I think you are subscribed there.
> Actually at the moment there is a discussion around this topic going
> on.
>
> vcgencmd get_throttled
0x0
> https://www.raspberrypi.org/forums/viewtopic.php?t=190584

That "forum" is NOT a list. And I've changed browsers, losing all my 
passwds. So while I can read it, I can't post.

And I am wondering where the man page for vcgencmd might be?

Searching for that, I found a page that describes it, then found a blog 
by Jeff Geerling on make a pi4 boot from an ssd, which killed a good 
sized tree, but might get me going there.

But first, back to bed, swearing at an electric blanket with a flaky 
stat. I'm having trouble with a perl module that amanda uses, and was up 
to see if the backup actually worked.  It did. Did I mention I hate 
trying to run down an intermittent that takes a notion to work, and 
spits out missleading errors when it doesn't? Gonna need a longer wall 
someday.

Thanks deloptes

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page

Re: What is the command to access the temp sensors in a rpi4?

2021-01-18 Thread deloptes

Gene Heskett wrote:

> ISTR there is a "vcg*" sort of thing to read that stuff, but have lost it
> in the fog of time.
> 
> Cheers, Gene Heskett

Hi Gene,
why not ask on the RPI list - I think you are subscribed there. Actually at
the moment there is a discussion around this topic going on.

vcgencmd get_throttled

https://www.raspberrypi.org/forums/viewtopic.php?t=190584

What is the command to access the temp sensors in a rpi4?

2021-01-17 Thread Gene Heskett

Greetings all;

ISTR there is a "vcg*" sort of thing to read that stuff, but have lost it 
in the fog of time.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page

Re: sensors

2020-07-20 Thread Reco

Hi.

On Mon, Jul 20, 2020 at 07:27:03PM +0200, Pòl Hallen wrote:
> Hi folks :-)
> 
> I bought  a new cpu: xeon E3-1243 v3
> 
> sensors show me the follow data (normal use):
> 
> Physical id 0:  +46.0�C  (high = +80.0�C, crit = +100.0�C)
> Core 0: +46.0�C  (high = +80.0�C, crit = +100.0�C)
> Core 1: +42.0�C  (high = +80.0�C, crit = +100.0�C)
> Core 2: +42.0�C  (high = +80.0�C, crit = +100.0�C)
> Core 3: +42.0�C  (high = +80.0�C, crit = +100.0�C)
> 
> someone can tell me if these data are "normal"? or should better change 
> heatsink?

Somewhat higher than it could be, but hardly a cause for an alarm.
For instance, 

# lscpu  | grep Model
Model:   44
Model name:  Intel(R) Xeon(R) CPU   X5675  @ 3.07GHz

# sensors
coretemp-isa-0001
Adapter: ISA adapter
Core 0:   +35.0°C  (high = +80.0°C, crit = +96.0°C)
Core 1:   +32.0°C  (high = +80.0°C, crit = +96.0°C)
Core 2:   +36.0°C  (high = +80.0°C, crit = +96.0°C)
Core 8:   +37.0°C  (high = +80.0°C, crit = +96.0°C)
Core 9:   +37.0°C  (high = +80.0°C, crit = +96.0°C)
Core 10:  +40.0°C  (high = +80.0°C, crit = +96.0°C)

intel5500-pci-00a3
Adapter: PCI adapter
temp1:+58.0°C  (high = +100.0°C, hyst = +90.0°C)
   (crit = +109.5°C)

coretemp-isa-
Adapter: ISA adapter
Core 0:   +35.0°C  (high = +80.0°C, crit = +96.0°C)
Core 1:   +34.0°C  (high = +80.0°C, crit = +96.0°C)
Core 2:   +35.0°C  (high = +80.0°C, crit = +96.0°C)
Core 8:   +37.0°C  (high = +80.0°C, crit = +96.0°C)
Core 9:   +34.0°C  (high = +80.0°C, crit = +96.0°C)
Core 10:  +36.0°C  (high = +80.0°C, crit = +96.0°C)

Reco

Re: sensors

2020-07-20 Thread David Christensen

On 2020-07-20 10:27, Pòl Hallen wrote:

Hi folks :-)

I bought a new cpu: xeon E3-1243 v3

sensors show me the follow data (normal use):

Physical id 0: +46.0�C (high = +80.0�C, crit = +100.0�C)
Core 0: +46.0�C (high = +80.0�C, crit = +100.0�C)
Core 1: +42.0�C (high = +80.0�C, crit = +100.0�C)
Core 2: +42.0�C (high = +80.0�C, crit = +100.0�C)
Core 3: +42.0�C (high = +80.0�C, crit = +100.0�C)

someone can tell me if these data are "normal"? or should better change
heatsink?

thanks for help :)

Pol

I do not see that model processor on the Intel specifications web site.
I see E3-1240, -1241, -1245, and -1246, for version v3:

https://ark.intel.com/content/www/us/en/ark/products/75055/intel-xeon-processor-e3-1240-v3-8m-cache-3-40-ghz.html

That particular page does not show a temperature rating, but 42 C should
be acceptable. Your listing above shows a high limit of 80 C and a
critical limit of 100 C.

I use Xcfe and the Sensor plug-in to monitor whatever temperatures
and/or voltages are supported on a particular machine. When I put my
Intel processors under load, I have seen temperatures above 70 C. I
would be concerned if any temperature reached 80 C.

Your computer may have an accumulation of dust in the heat sinks, fans,
and/or air ports/ filters. Power down the computer. Disconnect the
electrical cables for all fans. Clean all fans, heat sinks, filters,
grills, etc., with a vacuum cleaner. (The fans will spin, may act as
generators, and could damage your motherboard. This is why I disconnect
them.) Reconnect the fans. Boot the computer. Test.

Another possibility is that the heat sink compound may have dried out.
Power down the computer, remove the processor heat sink and fan
assembly, clean the fan and heat sink with a vacuum cleaner, clean the
heat sink compound off of the CPU and off of the heat sink (a plastic
gift card or credit card works well), clean the mating surfaces again
with rubbing alcohol, apply silver heat sink compound, install heat and
fan, boot, and test.

David

Re: sensors

2020-07-20 Thread Linux-Fan


Pòl Hallen writes:


Hi folks :-)

I bought  a new cpu: xeon E3-1243 v3


Is it really an E3-1243 v3? ark.intel.com does not seem to know about it,  
although judging from xeon it should be Intel, right? v3 may hint that  
it is not exactly a “new cpu”, despite still performing wéll...



sensors show me the follow data (normal use):

Physical id 0:  +46.0�C  (high = +80.0�C, crit = +100.0�C)
Core 0: +46.0�C  (high = +80.0�C, crit = +100.0�C)
Core 1: +42.0�C  (high = +80.0�C, crit = +100.0�C)
Core 2: +42.0�C  (high = +80.0�C, crit = +100.0�C)
Core 3: +42.0�C  (high = +80.0�C, crit = +100.0�C)

someone can tell me if these data are "normal"? or should better change  
heatsink?


What system is it running in? Is the system under load or idle?

My Xeon E3-1231 v3 has the following:

$ sensors
[...]
coretemp-isa-
Adapter: ISA adapter
Package id 0:  +33.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:+31.0°C  (high = +80.0°C, crit = +100.0°C)
Core 1:+30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 2:+33.0°C  (high = +80.0°C, crit = +100.0°C)
Core 3:+30.0°C  (high = +80.0°C, crit = +100.0°C)

If the system is put under CPU load, temperatures rise:

$ sensors
[...]
coretemp-isa-
Adapter: ISA adapter
Package id 0:  +76.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:+73.0°C  (high = +80.0°C, crit = +100.0°C)
Core 1:+76.0°C  (high = +80.0°C, crit = +100.0°C)
Core 2:+74.0°C  (high = +80.0°C, crit = +100.0°C)
Core 3:+71.0°C  (high = +80.0°C, crit = +100.0°C)

After a while, one can hear the fans speeding up :)

Short summary: Unless your system is idle, 40°C seem to be perferctly fine.

HTH
Linux-Fan


pgpKlaQBsfOxh.pgp
Description: PGP signature

Re: sensors

2020-07-20 Thread Dan Ritter

P??l Hallen wrote: 
> Hi folks :-)
> 
> I bought  a new cpu: xeon E3-1243 v3
> 
> sensors show me the follow data (normal use):
> 
> Physical id 0:  +46.0???C  (high = +80.0???C, crit = +100.0???C)
> Core 0: +46.0???C  (high = +80.0???C, crit = +100.0???C)
> Core 1: +42.0???C  (high = +80.0???C, crit = +100.0???C)
> Core 2: +42.0???C  (high = +80.0???C, crit = +100.0???C)
> Core 3: +42.0???C  (high = +80.0???C, crit = +100.0???C)
> 
> someone can tell me if these data are "normal"? or should better change
> heatsink?
> 

It tells you itself: the current temperature is under the high
mark and far under the critical mark.

I have an E3-1220 v6 here:

coretemp-isa-
Adapter: ISA adapter
Package id 0:  +32.0??C  (high = +80.0??C, crit = +100.0??C)
Core 0:+32.0??C  (high = +80.0??C, crit = +100.0??C)
Core 1:+32.0??C  (high = +80.0??C, crit = +100.0??C)
Core 2:+32.0??C  (high = +80.0??C, crit = +100.0??C)
Core 3:+32.0??C  (high = +80.0??C, crit = +100.0??C)


This machine isn't doing anything interesting right now.

-dsr-

sensors

2020-07-20 Thread Pòl Hallen


Hi folks :-)

I bought  a new cpu: xeon E3-1243 v3

sensors show me the follow data (normal use):

Physical id 0:  +46.0�C  (high = +80.0�C, crit = +100.0�C)
Core 0: +46.0�C  (high = +80.0�C, crit = +100.0�C)
Core 1: +42.0�C  (high = +80.0�C, crit = +100.0�C)
Core 2: +42.0�C  (high = +80.0�C, crit = +100.0�C)
Core 3: +42.0�C  (high = +80.0�C, crit = +100.0�C)

someone can tell me if these data are "normal"? or should better change 
heatsink?


thanks for help :)

Pol

Re: any gui for lm-sensors?

2020-07-09 Thread 0...@caiway.net

On Thu, 9 Jul 2020 02:52:22 + (UTC)
Long Wind  wrote:

> i want a small app that show cpu temperaturewhich package shall i
> install?Thanks!
> 

psensor if you want a graph and/or remote

the packages are:

psensor is 63 kB,
psensor-common is 43 kB and 
psensor-server is 110 kB

Re: any gui for lm-sensors?

2020-07-08 Thread Gene Heskett

On Wednesday 08 July 2020 22:52:22 Long Wind wrote:

> i want a small app that show cpu temperaturewhich package shall i
> install?Thanks!

gkrellm and helpers. Small, still shows everything.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page

Re: any gui for lm-sensors?

2020-07-08 Thread Long Wind

Thank Charles! 
xsensors seems best for me 
On Thursday, July 9, 2020, 12:10:27 AM EDT, Charles Curley 
 wrote:  

 On Thu, 9 Jul 2020 02:52:22 + (UTC)
Long Wind  wrote:

> i want a small app that show cpu temperaturewhich package shall i
> install?Thanks!
> 

Your desktop may have a suitable addon. For XFCE, xfce4-sensors-plugin.
Otherwise, run

apt-cache search sensors

and see if any of that gives you ideas.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: any gui for lm-sensors?

2020-07-08 Thread Tu Can

On [4], 2020-07-09 at 02:52 +, Long Wind wrote:
> i want a small app that show cpu temperature
> which package shall i install?
> Thanks!
> 
conky, as a background of desktop. not only cpu informaiton. Here is my
configuration file[1].

[1]https://github.com/bestucan/conky

Re: any gui for lm-sensors?

2020-07-08 Thread Charles Curley

On Thu, 9 Jul 2020 02:52:22 + (UTC)
Long Wind  wrote:

> i want a small app that show cpu temperaturewhich package shall i
> install?Thanks!
> 

Your desktop may have a suitable addon. For XFCE, xfce4-sensors-plugin.
Otherwise, run

apt-cache search sensors

and see if any of that gives you ideas.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: any gui for lm-sensors?

2020-07-08 Thread David Christensen


On 2020-07-08 19:52, Long Wind wrote:

i want a small app that show cpu temperaturewhich package shall i 
install?Thanks!


I use Xfce with the CPU Frequency Monitor, CPU Graph, and Sensor panel 
plug-ins.



David

Re: any gui for lm-sensors?

2020-07-08 Thread Joe Pfeiffer

Long Wind  writes:

> i want a small app that show cpu temperature
> which package shall i install?
> Thanks!

I've been using gkrellm to show quite a bit of system information
(including temperatures) for years and years now.

Re: Hoe temperatuur informatie van sensors te intepreteren

2018-09-11 Thread Jan Claeys

On Tue, 2018-09-11 at 08:26 +0200, Cecil Westerhof wrote:
> Wanneer ik sensors draai dan krijg ik o.a.:
> CPU_TEMP:   +53.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = 
> thermistor
> 
> Ik heb een grafisch tooltje geschreven dat in een grafiek de
> temperatuur van het afgelopen uur laat zien. Normaal is deze groen,
> maar bij een temperatuur boven warning wordt hij oranje en boven
> critical wordt hij rood. Ik heb nu ingesteld:
> set critical  85
> set warning   75
> 
> of kan ik daar beter van maken:
> set critical  80
> set warning   70

Welke temperaturen kritisch zijn of niet hangt af van wat (CPU, andere
chip, lucht in de kast, ...) & waar (vb. buitenkant vs. binnenkant) er
gemeten wordt, en kan bij elke CPU (etc.) anders zijn...

Voor de meeste CPUs kan je de kritische temperatuur vinden op de
website van de fabrikant bij de CPU-specificaties.

-- 
Jan Claeys

Hoe temperatuur informatie van sensors te intepreteren

2018-09-11 Thread Cecil Westerhof

Wanneer ik sensors draai dan krijg ik o.a.:
CPU_TEMP:   +53.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = 
thermistor

Ik heb een grafisch tooltje geschreven dat in een grafiek de
temperatuur van het afgelopen uur laat zien. Normaal is deze groen,
maar bij een temperatuur boven warning wordt hij oranje en boven
critical wordt hij rood. Ik heb nu ingesteld:
set critical  85
set warning   75

of kan ik daar beter van maken:
set critical  80
set warning   70

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

Re: lm-sensors doesn't see the cpu rpm.....

On 28 December 2017 at 18:14, deloptes  wrote:

> Michael Fothergill wrote:
>
> > I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> > cooler.
>
> I'm just wondering if you used the correct switch for the cpu fan - what is
> your mother board?
>
> also from the gentoo link
>
> $ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
> CONFIG_SENSORS_FAM15H_POWER=m
> grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
> CONFIG_SENSORS_K10TEMP=m
>
> $ lsmod | grep temp
> k10temp16384  0
> $ lsmod | grep fam15
> fam15h_power   16384  0
>
> does this apply to your kernel?
>

I am going to suggest to the asus support folks that I might have
misconnected the cpu fan up to the motherboard.

I already told them that I wasn't sure if I was using a 3 pin instead of a
4 pin lead which might be a limitation here.

The Windows software diagnostics might also give clues to an erroneous mobo
hook up here.

I need to use all the divining rods available on this.

Regards

MF

>
> regards
>
>

Re: lm-sensors doesn't see the cpu rpm.....

On 28 December 2017 at 18:14, deloptes  wrote:

> Michael Fothergill wrote:
>
> > I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> > cooler.
>
> I'm just wondering if you used the correct switch for the cpu fan - what is
> your mother board?
>
> also from the gentoo link
>
> $ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
> CONFIG_SENSORS_FAM15H_POWER=m
> grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
> CONFIG_SENSORS_K10TEMP=m
>
> $ lsmod | grep temp
> k10temp16384  0
> $ lsmod | grep fam15
> fam15h_power   16384  0
>
> does this apply to your kernel?


Here is the output from lsmod on this:



> mikef@bong:~$ lsmod | grep fam15
> fam15h_power   16384  0
> mikef@bong:~$ lsmod | grep temp
> k10temp16384  0
> mikef@bong:~$
>
>
Cheers

MF



>
> regards
>
>

Re: lm-sensors doesn't see the cpu rpm.....

On 28 December 2017 at 18:30, Michael Fothergill <
michael.fotherg...@gmail.com> wrote:

>
>
> On 28 December 2017 at 18:14, deloptes  wrote:
>
>> Michael Fothergill wrote:
>>
>> > I am running stretch on an AMD FX8350 box which uses an Arctic Freezer
>> 13
>> > cooler.
>>
>> I'm just wondering if you used the correct switch for the cpu fan - what
>> is
>> your mother board?
>>
>
> This is an interesting idea.  I built the PC myself.  Maybe I connected
> up the CPU fan lead incorrectly..
>

Wait a minute here...

When I said I build the PC, what I mean is I screwed the motherboard into
the PC and then connected up the 3 case fans to it.

The CPU cooler and FAN were actually attached to the motherboard by the
company I bought the entire motherboard bundle from (ie I purchased the
board, 8GB RAM preinstalled plus the Arctic Freezer
cooler thermal pasted (and baisted - its Christmas remember!) the firm here
in the UK offering it as a job lot.

I can't quite remember if the cpu cooler lead was already attached to the
motherboard at that point - I might have done that bit myself (and maybe
bungled it - you could be on the money here).

So some thought and imagination could be required here.

MF


> The motherboard is an ASUS FX 990 Sabertooth R2.0; the bios version is
> 2501.
>
> Here is some of the info sent to the ASUS support folks:
>
> [Product Information]
> Product Type : Motherboard
> Product Model : SABERTOOTH 990FX R2.0
> Product S/N : EAM0BX019177
> Operation System / Firmware or BIOS version : Debian 9 (Linuc) OS/Bios
> that came with product
>
> [Graphics Card Vendor/model/Chipset/Driver]
> Nvidia engt 430 model
>
> [CPU vendor/processor number]
> AMD FX 8350
>
> [Memory vendor/model/specification]
> Memory Vengeance LP Upgrade: Corsair 8GB 1600Mhz Vengeance LP DDR3
>
>
>>
>> also from the gentoo link
>>
>> $ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
>> CONFIG_SENSORS_FAM15H_POWER=m
>> grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
>> CONFIG_SENSORS_K10TEMP=m
>>
>> $ lsmod | grep temp
>> k10temp16384  0
>> $ lsmod | grep fam15
>> fam15h_power   16384  0
>>
>> does this apply to your kernel?
>>
>
> I will login to the machine, fire up debian and run
>
> lsmod | grep temp
>
> and
>
> lsmod | grep fam 15
>
> and get you the output.
>
> I think fam15 module is installed - check the lsmod output I already
> posted.
>
> Please let me know any other commands/diagnostics you want running here.
>
> Regards and thanks.
>
> Michael Fothergill
>
> 
>
>
>
>
>>
>> regards
>>
>>
>

Re: lm-sensors doesn't see the cpu rpm.....

On 28 December 2017 at 18:14, deloptes  wrote:

> Michael Fothergill wrote:
>
> > I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> > cooler.
>
> I'm just wondering if you used the correct switch for the cpu fan - what is
> your mother board?
>

This is an interesting idea.  I built the PC myself.  Maybe I connected up
the CPU fan lead incorrectly..

The motherboard is an ASUS FX 990 Sabertooth R2.0; the bios version is 2501.

Here is some of the info sent to the ASUS support folks:

[Product Information]
Product Type : Motherboard
Product Model : SABERTOOTH 990FX R2.0
Product S/N : EAM0BX019177
Operation System / Firmware or BIOS version : Debian 9 (Linuc) OS/Bios that
came with product

[Graphics Card Vendor/model/Chipset/Driver]
Nvidia engt 430 model

[CPU vendor/processor number]
AMD FX 8350

[Memory vendor/model/specification]
Memory Vengeance LP Upgrade: Corsair 8GB 1600Mhz Vengeance LP DDR3


>
> also from the gentoo link
>
> $ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
> CONFIG_SENSORS_FAM15H_POWER=m
> grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
> CONFIG_SENSORS_K10TEMP=m
>
> $ lsmod | grep temp
> k10temp16384  0
> $ lsmod | grep fam15
> fam15h_power   16384  0
>
> does this apply to your kernel?
>

I will login to the machine, fire up debian and run

lsmod | grep temp

and

lsmod | grep fam 15

and get you the output.

I think fam15 module is installed - check the lsmod output I already posted.

Please let me know any other commands/diagnostics you want running here.

Regards and thanks.

Michael Fothergill






>
> regards
>
>

Re: lm-sensors doesn't see the cpu rpm.....

2017-12-28 Thread deloptes

Michael Fothergill wrote:

> I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> cooler.

I'm just wondering if you used the correct switch for the cpu fan - what is
your mother board?

also from the gentoo link

$ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
CONFIG_SENSORS_FAM15H_POWER=m
grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
CONFIG_SENSORS_K10TEMP=m

$ lsmod | grep temp
k10temp16384  0
$ lsmod | grep fam15
fam15h_power   16384  0

does this apply to your kernel?

regards

Re: lm-sensors doesn't see the cpu rpm.....

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>

Dear All,

It's sad but I think I need install Windows 10 on this machine to sort out
the fan control and cpu cooler problems.

This machine overheats when I run pov-ray benchmark on it and shuts down.

see here (first page only)

https://forums.gentoo.org/viewtopic-t-1056576-start-0.html

Then I can install the ASUS Fan Xpert and ROG software etc on top of the FX
990 sabertooth motherboard I have...

I think I might need to change the thermal paste compound between the CPU
and Arctic Freezer 13 heatsink to cure the cooling problem.

I am going to use Artic MX-4 paste.

While Debian and Gentoo are OK to work with here, I cannot tolerate the
machine shutting down now and again due to overheating any longer.

I am corresponding with the ASUS technical folks at present.

I need the extra special bloodhound Passau Cathedral Organ factor here to
help check on the temps and the fan activity once I start doing
surgery on the cpu/fan-heatsink thermal interface...

CPUs cost money.

Thanks for the help to date.

Regards

MF

>
> wooledg:~$ /sbin/modinfo coretemp
> filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:GPL
> description:Intel Core temperature monitor
> author: Rudolf Marek 
> alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
> depends:
> intree: Y
> vermagic:   4.9.0-4-amd64 SMP mod_unload modversions
> parm:   tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>
>

Re: lm-sensors doesn't see the cpu rpm.....

On 28 December 2017 at 13:55, Greg Wooledge <wool...@eeg.ccf.org> wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>

If you look here:

https://askubuntu.com/questions/748615/lm-sensors-not-returning-cpu-temp-it87

it says that You need to append acpi_enforce_resources=lax at the end of
> the line GRUB_CMDLINE_LINUX
>
in /etc/default/grub to make e.g. the it87 module work for the FX8350 chip
AFAICT

BUT

If you look at my /etc/default/grub:

root@bong:/etc/default# more grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX="initrd=/install/initrd.gz"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to
Linux
#GRUB_DISABLE_LINUX_UUID=true


# Uncomment to disable generation of recovery mode menu
entries
#GRUB_DISABLE_RECOVERY="true"



# Uncomment to get a beep at grub
start
#GRUB_INIT_TUNE="480 440
1"
root@bong:/etc/default#


I don't have any acpi command in there but lsmod does list it87 as a
module for my install:

root@bong:/etc/default# lsmod | grep it87
it87   57344
0
hwmon_vid  16384  1 it87


Does it need to have a 1 not a zero in there for the it87 to actually be
working even if it is installed?

Cheers

MF









>
> wooledg:~$ /sbin/modinfo coretemp
> filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:GPL
> description:Intel Core temperature monitor
> author: Rudolf Marek <r.ma...@assembler.cz>
> alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
> depends:
> intree: Y
> vermagic:   4.9.0-4-amd64 SMP mod_unload modversions
> parm:   tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>
>

Re: lm-sensors doesn't see the cpu rpm.....

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>
> wooledg:~$ /sbin/modinfo coretemp
> filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:GPL
> description:Intel Core temperature monitor
> author: Rudolf Marek 
> alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
> depends:
> intree: Y
> vermagic:   4.9.0-4-amd64 SMP mod_unload modversions
> parm:   tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>

I now realise that coretemp only works with Intel chips not AMD ones

Ooops!

I will look up module names that work for the FX 8350 and see of I can find
any that are not listed in lsmod and try installing them
with modprobe.

Cheers

MF

Re: lm-sensors doesn't see the cpu rpm.....

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>

The output of lspci is here:
https://pastebin.com/AAXTq8Uh



>
> wooledg:~$ /sbin/modinfo coretemp
> filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:GPL
> description:Intel Core temperature monitor
> author: Rudolf Marek 
> alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
> depends:
> intree: Y
> vermagic:   4.9.0-4-amd64 SMP mod_unload modversions
> parm:   tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>
>

Re: lm-sensors doesn't see the cpu rpm.....

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>

Perhaps you could suggest some other module names I could try to turn on
using
the modprobe command that I do not have turned on at present based on the
lsmod output.

Maybe one or to might work.

Cheers

MF



>
> wooledg:~$ /sbin/modinfo coretemp
> filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:GPL
> description:Intel Core temperature monitor
> author: Rudolf Marek 
> alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
> depends:
> intree: Y
> vermagic:   4.9.0-4-amd64 SMP mod_unload modversions
> parm:   tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>

Re: lm-sensors doesn't see the cpu rpm.....

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>
> wooledg:~$ /sbin/modinfo coretemp
> filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:GPL
> description:Intel Core temperature monitor
> author: Rudolf Marek 
> alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
> depends:
> intree: Y
> vermagic:   4.9.0-4-amd64 SMP mod_unload modversions
> parm:   tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>


> It says "Intel" in the description.  Are you using an Intel CPU?
>

Here is the output of lscpu:


root@bong:/home/mikef# lscpu
Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):8
On-line CPU(s) list:   0-7
Thread(s) per core:2
Core(s) per socket:4
Socket(s): 1
NUMA node(s):  1
Vendor ID: AuthenticAMD
CPU family:21
Model: 2
Model name:AMD FX(tm)-8350 Eight-Core Processor
Stepping:  0
CPU MHz:   4334.834
BogoMIPS:  8669.66
Virtualization:AMD-V
L1d cache: 16K
L1i cache: 64K
L2 cache:  2048K
L3 cache:  8192K
NUMA node0 CPU(s): 0-7
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid
aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2
popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm
sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce
nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate vmmcall bmi1
arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid
decodeassists pausefilter pfthreshold
root@bong:/home/mikef#


It looks like an FX8350 chip to me.

Comments appreciated

Regards

MF

Re: lm-sensors doesn't see the cpu rpm.....

2017-12-28 Thread Greg Wooledge

On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> root@bong:/boot#  sudo modprobe coretemp
> modprobe: ERROR: could not insert 'coretemp': No such device
> 
> 
> This is odd because coretemp is set as a module option in the config file:
> 
> CONFIG_SENSORS_CORETEMP=m
> 
> Comments appreciared

Well, it *should* work with a standard Debian kernel and applicable
hardware.

wooledg:~$ /sbin/modinfo coretemp
filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.ko
license:GPL
description:Intel Core temperature monitor
author: Rudolf Marek 
alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
depends:
intree: Y
vermagic:   4.9.0-4-amd64 SMP mod_unload modversions 
parm:   tjmax:TjMax value in degrees Celsius (int)

Your "No such device" error sounds like it probed for hardware and didn't
find any.  If the module itself were missing from the file system, then
I would have expected "FATAL: Module coretemp not found in directory ...".

It says "Intel" in the description.  Are you using an Intel CPU?

Re: lm-sensors doesn't see the cpu rpm.....

G_SENSORS_ATXP1=m
> CONFIG_SENSORS_DS620=m
> CONFIG_SENSORS_DS1621=m
> CONFIG_SENSORS_DELL_SMM=m
> CONFIG_SENSORS_I5K_AMB=m
> CONFIG_SENSORS_F71805F=m
> CONFIG_SENSORS_F71882FG=m
> CONFIG_SENSORS_F75375S=m
> CONFIG_SENSORS_FSCHMD=m
> CONFIG_SENSORS_FTSTEUTATES=m
> CONFIG_SENSORS_GL518SM=m
> CONFIG_SENSORS_GL520SM=m
> CONFIG_SENSORS_G760A=m
> # CONFIG_SENSORS_G762 is not set
> # CONFIG_SENSORS_GPIO_FAN is not set
> # CONFIG_SENSORS_HIH6130 is not set
> CONFIG_SENSORS_IBMAEM=m
> CONFIG_SENSORS_IBMPEX=m
> # CONFIG_SENSORS_IIO_HWMON is not set
> CONFIG_SENSORS_I5500=m
> CONFIG_SENSORS_CORETEMP=m
> CONFIG_SENSORS_IT87=m
> CONFIG_SENSORS_JC42=m
> # CONFIG_SENSORS_POWR1220 is not set
> CONFIG_SENSORS_LINEAGE=m
> # CONFIG_SENSORS_LTC2945 is not set
> # CONFIG_SENSORS_LTC2990 is not set
> CONFIG_SENSORS_LTC4151=m
> CONFIG_SENSORS_LTC4215=m
> # CONFIG_SENSORS_LTC4222 is not set
> CONFIG_SENSORS_LTC4245=m
> # CONFIG_SENSORS_LTC4260 is not set
> CONFIG_SENSORS_LTC4261=m
> CONFIG_SENSORS_MAX=m
> CONFIG_SENSORS_MAX16065=m
> CONFIG_SENSORS_MAX1619=m
> CONFIG_SENSORS_MAX1668=m
> # CONFIG_SENSORS_MAX197 is not set
> # CONFIG_SENSORS_MAX31722 is not set
> CONFIG_SENSORS_MAX6639=m
> CONFIG_SENSORS_MAX6642=m
> CONFIG_SENSORS_MAX6650=m
> # CONFIG_SENSORS_MAX6697 is not set
> # CONFIG_SENSORS_MAX31790 is not set
> # CONFIG_SENSORS_MCP3021 is not set
> CONFIG_SENSORS_MENF21BMC_HWMON=m
> CONFIG_SENSORS_ADCXX=m
> CONFIG_SENSORS_LM63=m
> CONFIG_SENSORS_LM70=m
> CONFIG_SENSORS_LM73=m
> CONFIG_SENSORS_LM75=m
> CONFIG_SENSORS_LM77=m
> CONFIG_SENSORS_LM78=m
> CONFIG_SENSORS_LM80=m
> CONFIG_SENSORS_LM83=m
> CONFIG_SENSORS_LM85=m
> CONFIG_SENSORS_LM87=m
> CONFIG_SENSORS_LM90=m
> CONFIG_SENSORS_LM92=m
> CONFIG_SENSORS_LM93=m
> # CONFIG_SENSORS_LM95234 is not set
> CONFIG_SENSORS_LM95241=m
> CONFIG_SENSORS_LM95245=m
> CONFIG_SENSORS_PC87360=m
> CONFIG_SENSORS_PC87427=m
> CONFIG_SENSORS_NTC_THERMISTOR=m
> CONFIG_SENSORS_NCT6683=m
> CONFIG_SENSORS_NCT6775=m
> # CONFIG_SENSORS_NCT7802 is not set
> # CONFIG_SENSORS_NCT7904 is not set
> CONFIG_SENSORS_PCF8591=m
> # CONFIG_PMBUS is not set
> # CONFIG_SENSORS_SHT15 is not set
> CONFIG_SENSORS_SHT21=m
> # CONFIG_SENSORS_SHT3x is not set
> # CONFIG_SENSORS_SHTC1 is not set
> CONFIG_SENSORS_SIS5595=m
> CONFIG_SENSORS_DME1737=m
> CONFIG_SENSORS_EMC1403=m
> CONFIG_SENSORS_EMC2103=m
> CONFIG_SENSORS_EMC6W201=m
> CONFIG_SENSORS_SMSC47M1=m
> CONFIG_SENSORS_SMSC47M192=m
> CONFIG_SENSORS_SMSC47B397=m
> CONFIG_SENSORS_SCH56XX_COMMON=m
> CONFIG_SENSORS_SCH5627=m
> CONFIG_SENSORS_SCH5636=m
> CONFIG_SENSORS_SMM665=m
> # CONFIG_SENSORS_ADC128D818 is not set
> CONFIG_SENSORS_ADS1015=m
> CONFIG_SENSORS_ADS7828=m
> CONFIG_SENSORS_ADS7871=m
> CONFIG_SENSORS_AMC6821=m
> # CONFIG_SENSORS_INA209 is not set
> # CONFIG_SENSORS_INA2XX is not set
> # CONFIG_SENSORS_INA3221 is not set
> # CONFIG_SENSORS_TC74 is not set
> CONFIG_SENSORS_THMC50=m
> CONFIG_SENSORS_TMP102=m
> # CONFIG_SENSORS_TMP103 is not set
> CONFIG_SENSORS_TMP401=m
> CONFIG_SENSORS_TMP421=m
> CONFIG_SENSORS_VIA_CPUTEMP=m
> CONFIG_SENSORS_VIA686A=m
> CONFIG_SENSORS_VT1211=m
> CONFIG_SENSORS_VT8231=m
> CONFIG_SENSORS_W83781D=m
> CONFIG_SENSORS_W83791D=m
> CONFIG_SENSORS_W83792D=m
> CONFIG_SENSORS_W83793=m
> CONFIG_SENSORS_W83795=m
> # CONFIG_SENSORS_W83795_FANCTRL is not set
> CONFIG_SENSORS_W83L785TS=m
> CONFIG_SENSORS_W83L786NG=m
> CONFIG_SENSORS_W83627HF=m
> CONFIG_SENSORS_W83627EHF=m
>
> It seems that the kernel is configured with the module m setting
> consistently not the internal y setting so debian does not use the built in
> option by default here it would seem
>
> - see discussion here
>
> https://www.linux.com/learn/intro-to-linux/2017/9/
> advanced-lm-sensors-tips-and-tricks-linux-0
>
> so modifying the /etc/modules file works here.
>
> I notice that
> # CONFIG_SENSORS_W83795_FANCTRL is not set
> has been commented out
>
> and
>
> # CONFIG_SENSORS_GPIO_FAN is not set
>
> is in a similar state
>
> I will continue looking at this in more detail.
>
> Regards
>
> MF
>
>
>
>
>
>
>
>
>
>
>
> On 28 December 2017 at 12:14, Michael Fothergill <
> michael.fotherg...@gmail.com> wrote:
>
>> I have 3 case fans in the box here but lm-sensors only sees two of them
>> apparently as well as not seeing the cpu fan.
>>
>> Funny stuff.
>>
>> Regards
>>
>> MF
>>
>> On 28 December 2017 at 11:50, Michael Fothergill <
>> michael.fotherg...@gmail.com> wrote:
>>
>>> Dear Folks,
>>>
>>> I am runn

Re: lm-sensors doesn't see the cpu rpm.....

Dear All,

I looked at the config-4.9.0-4-amd64 file for the current kernel:

# Native drivers
#
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ABITUGURU3=m
# CONFIG_SENSORS_AD7314 is not set
CONFIG_SENSORS_AD7414=m
CONFIG_SENSORS_AD7418=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
# CONFIG_SENSORS_ADT7310 is not set
# CONFIG_SENSORS_ADT7410 is not set
CONFIG_SENSORS_ADT7411=m
CONFIG_SENSORS_ADT7462=m
CONFIG_SENSORS_ADT7470=m
CONFIG_SENSORS_ADT7475=m
CONFIG_SENSORS_ASC7621=m
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_K10TEMP=m
CONFIG_SENSORS_FAM15H_POWER=m
CONFIG_SENSORS_APPLESMC=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS620=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_DELL_SMM=m
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FSCHMD=m
CONFIG_SENSORS_FTSTEUTATES=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_G760A=m
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_GPIO_FAN is not set
# CONFIG_SENSORS_HIH6130 is not set
CONFIG_SENSORS_IBMAEM=m
CONFIG_SENSORS_IBMPEX=m
# CONFIG_SENSORS_IIO_HWMON is not set
CONFIG_SENSORS_I5500=m
CONFIG_SENSORS_CORETEMP=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_JC42=m
# CONFIG_SENSORS_POWR1220 is not set
CONFIG_SENSORS_LINEAGE=m
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2990 is not set
CONFIG_SENSORS_LTC4151=m
CONFIG_SENSORS_LTC4215=m
# CONFIG_SENSORS_LTC4222 is not set
CONFIG_SENSORS_LTC4245=m
# CONFIG_SENSORS_LTC4260 is not set
CONFIG_SENSORS_LTC4261=m
CONFIG_SENSORS_MAX=m
CONFIG_SENSORS_MAX16065=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX1668=m
# CONFIG_SENSORS_MAX197 is not set
# CONFIG_SENSORS_MAX31722 is not set
CONFIG_SENSORS_MAX6639=m
CONFIG_SENSORS_MAX6642=m
CONFIG_SENSORS_MAX6650=m
# CONFIG_SENSORS_MAX6697 is not set
# CONFIG_SENSORS_MAX31790 is not set
# CONFIG_SENSORS_MCP3021 is not set
CONFIG_SENSORS_MENF21BMC_HWMON=m
CONFIG_SENSORS_ADCXX=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM70=m
CONFIG_SENSORS_LM73=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_LM93=m
# CONFIG_SENSORS_LM95234 is not set
CONFIG_SENSORS_LM95241=m
CONFIG_SENSORS_LM95245=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_NTC_THERMISTOR=m
CONFIG_SENSORS_NCT6683=m
CONFIG_SENSORS_NCT6775=m
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
CONFIG_SENSORS_PCF8591=m
# CONFIG_PMBUS is not set
# CONFIG_SENSORS_SHT15 is not set
CONFIG_SENSORS_SHT21=m
# CONFIG_SENSORS_SHT3x is not set
# CONFIG_SENSORS_SHTC1 is not set
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_DME1737=m
CONFIG_SENSORS_EMC1403=m
CONFIG_SENSORS_EMC2103=m
CONFIG_SENSORS_EMC6W201=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_SCH56XX_COMMON=m
CONFIG_SENSORS_SCH5627=m
CONFIG_SENSORS_SCH5636=m
CONFIG_SENSORS_SMM665=m
# CONFIG_SENSORS_ADC128D818 is not set
CONFIG_SENSORS_ADS1015=m
CONFIG_SENSORS_ADS7828=m
CONFIG_SENSORS_ADS7871=m
CONFIG_SENSORS_AMC6821=m
# CONFIG_SENSORS_INA209 is not set
# CONFIG_SENSORS_INA2XX is not set
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_TC74 is not set
CONFIG_SENSORS_THMC50=m
CONFIG_SENSORS_TMP102=m
# CONFIG_SENSORS_TMP103 is not set
CONFIG_SENSORS_TMP401=m
CONFIG_SENSORS_TMP421=m
CONFIG_SENSORS_VIA_CPUTEMP=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83795=m
# CONFIG_SENSORS_W83795_FANCTRL is not set
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83L786NG=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m

It seems that the kernel is configured with the module m setting
consistently not the internal y setting so debian does not use the built in
option by default here it would seem

- see discussion here

https://www.linux.com/learn/intro-to-linux/2017/9/advanced-lm-sensors-tips-and-tricks-linux-0

so modifying the /etc/modules file works here.

I notice that
# CONFIG_SENSORS_W83795_FANCTRL is not set
has been commented out

and

# CONFIG_SENSORS_GPIO_FAN is not set

is in a similar state

I will continue looking at this in more detail.

Regards

MF











On 28 December 2017 at 12:14, Michael Fothergill <
michael.fotherg...@gmail.com> wrote:

> I have 3 case fans in the box here but lm-sensors only sees two of them
> apparently as well as not seeing the cpu fan.
>
> Funny stuff.
>
> Regards
>
> MF
>
> On 28 December 2017 at 11:50, Michael Fothergill <
> michael.fotherg...@gmail.com> wrote:
>
>> Dear Folks,
>>
>> I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
>> cooler.
>>
>> I inst

Re: lm-sensors doesn't see the cpu rpm.....

I have 3 case fans in the box here but lm-sensors only sees two of them
apparently as well as not seeing the cpu fan.

Funny stuff.

Regards

MF

On 28 December 2017 at 11:50, Michael Fothergill <
michael.fotherg...@gmail.com> wrote:

> Dear Folks,
>
> I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> cooler.
>
> I installed lm-sensors and ran the /etc module update command.
>
> The output looks like this:
>
> root@bong:/home/mikef# sensors
> asus-isa-
> Adapter: ISA adapter
> cpu_fan:0 RPM
>
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1:+21.9°C  (high = +70.0°C)
>(crit = +90.0°C, hyst = +87.0°C)
>
> nouveau-pci-0700
> Adapter: PCI adapter
> GPU core: +0.90 V  (min =  +0.88 V, max =  +1.08 V)
> temp1:+35.0°C  (high = +95.0°C, hyst =  +3.0°C)
>(crit = +105.0°C, hyst =  +5.0°C)
>(emerg = +135.0°C, hyst =  +5.0°C)
>
> fam15h_power-pci-00c4
> Adapter: PCI adapter
> power1:6.75 W  (crit = 125.19 W)
>
>
> it8721-isa-0290
>
> Adapter: ISA adapter
>
> in0:  +2.83 V  (min =  +2.02 V, max =  +2.95
> V)
> in1:  +2.83 V  (min =  +1.68 V, max =  +1.73 V)
> ALARM
> in2:  +0.98 V  (min =  +2.40 V, max =  +1.08 V)
> ALARM
> +3.3V:+3.31 V  (min =  +0.38 V, max =  +0.96 V)
> ALARM
> in4:  +0.25 V  (min =  +0.41 V, max =  +0.20 V)  ALARM
> in5:  +2.51 V  (min =  +0.12 V, max =  +0.00 V)  ALARM
> in6:  +1.98 V  (min =  +1.54 V, max =  +0.59 V)  ALARM
> 3VSB: +3.94 V  (min =  +3.31 V, max =  +0.89 V)  ALARM
> Vbat: +3.29 V
> fan1:1814 RPM  (min =   87 RPM)
> fan2:   0 RPM  (min =   46 RPM)  ALARM
> fan3:1125 RPM  (min =   29 RPM)
> temp1:+37.0°C  (low  = +34.0°C, high = +91.0°C)  sensor =
> thermistor
> temp2:+30.0°C  (low  = +45.0°C, high =  +9.0°C)  ALARM  sensor =
> thermistor
> temp3:   -128.0°C  (low  = -60.0°C, high =  +4.0°C)  sensor = disabled
> intrusion0:  OK
>
> root@bong:/home/mikef#
>
> The cpu fan is running at around 2500 rpm.
>
> If the connector were 3 pin rather than 4 pin could that explain the zero
> here?
>
> Suggestions on a tweak that could awaken the sensor or stimulate
> lm-sensors truffle hound hunting skills here would be appreciated.
>
> Googling around gives quite complex suggestions.
>
> Is there something simple I could try here?
>
> Regards
>
> Michael Fothergill
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

lm-sensors doesn't see the cpu rpm.....

Dear Folks,

I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
cooler.

I installed lm-sensors and ran the /etc module update command.

The output looks like this:

root@bong:/home/mikef# sensors
asus-isa-
Adapter: ISA adapter
cpu_fan:0 RPM

k10temp-pci-00c3
Adapter: PCI adapter
temp1:+21.9°C  (high = +70.0°C)
   (crit = +90.0°C, hyst = +87.0°C)

nouveau-pci-0700
Adapter: PCI adapter
GPU core: +0.90 V  (min =  +0.88 V, max =  +1.08 V)
temp1:+35.0°C  (high = +95.0°C, hyst =  +3.0°C)
   (crit = +105.0°C, hyst =  +5.0°C)
   (emerg = +135.0°C, hyst =  +5.0°C)

fam15h_power-pci-00c4
Adapter: PCI adapter
power1:6.75 W  (crit = 125.19 W)


it8721-isa-0290

Adapter: ISA
adapter

in0:  +2.83 V  (min =  +2.02 V, max =  +2.95
V)
in1:  +2.83 V  (min =  +1.68 V, max =  +1.73 V)
ALARM
in2:  +0.98 V  (min =  +2.40 V, max =  +1.08 V)
ALARM
+3.3V:+3.31 V  (min =  +0.38 V, max =  +0.96 V)
ALARM
in4:  +0.25 V  (min =  +0.41 V, max =  +0.20 V)  ALARM
in5:  +2.51 V  (min =  +0.12 V, max =  +0.00 V)  ALARM
in6:  +1.98 V  (min =  +1.54 V, max =  +0.59 V)  ALARM
3VSB: +3.94 V  (min =  +3.31 V, max =  +0.89 V)  ALARM
Vbat: +3.29 V
fan1:1814 RPM  (min =   87 RPM)
fan2:   0 RPM  (min =   46 RPM)  ALARM
fan3:1125 RPM  (min =   29 RPM)
temp1:+37.0°C  (low  = +34.0°C, high = +91.0°C)  sensor = thermistor
temp2:+30.0°C  (low  = +45.0°C, high =  +9.0°C)  ALARM  sensor =
thermistor
temp3:   -128.0°C  (low  = -60.0°C, high =  +4.0°C)  sensor = disabled
intrusion0:  OK

root@bong:/home/mikef#

The cpu fan is running at around 2500 rpm.

If the connector were 3 pin rather than 4 pin could that explain the zero
here?

Suggestions on a tweak that could awaken the sensor or stimulate lm-sensors
truffle hound hunting skills here would be appreciated.

Googling around gives quite complex suggestions.

Is there something simple I could try here?

Regards

Michael Fothergill

FingerPrint ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader

2014-09-19 Thread Benedito Junior

Hello everybody,

Does anyone here know where can I download the driver for my fingerprint

ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader

I'm using debian wheezy and I didn't find the correct driver for it.

lm-sensors控制风扇，不能加载模块

2014-05-14 Thread gmail

我在x200上面安装了 debian sid，风扇一直在全速运转，想要实现根据温度来调 
节转速。

参考了http://www.linuxidc.com/Linux/2009-02/18270.htm
这篇文章提到lm-sensors，于是到官方网站（http://www.lm- sensors.org/wiki 
/iwizard/Detection）

按照教程设置，最后加载模 块不能成功。
下面是我的操作过程，有知 道的，帮我看看。

PS：1.像这样 的问题应该在哪里的邮件列表去问呢?

2 有哪位朋友也在 thinkpad上面安装了debian之类的linux系统，一起 
交流。怎样实现充放电阈值的控制，以及延长电池使用时间 的方法，以及动态硬 
盘保护


谢 谢！


#+TITLE:
* ref
www.lm-sensors.org/wiki/iwizard/DistroPackageInstall
www.lm-sensors.org/wiki/iwizard/KernelPreparation
www.lm-sensors.org/wiki/iwizard/SensorsOutput

* install
$ apt-get install lm-sensors

* usage

kk@x200:~$  sudo sensors-detect
# sensors-detect revision 6209 (2014-01-14 22:51:58 +0100)
# System: LENOVO 7459X18 [ThinkPad X200] (laptop)

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.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...   No
VIA VT82C686 Integrated Sensors...  No
VIA VT8231 Integrated Sensors...No
AMD K8 thermal sensors...   No
AMD Family 10h thermal sensors...   No
AMD Family 11h thermal sensors...   No
AMD Family 12h and 14h thermal sensors...   No
AMD Family 15h thermal sensors...   No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor...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 for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...   No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'...   No
Trying family `ITE'...  No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...   No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'...   No
Trying family `ITE'...  No

Some hardware monitoring chips are 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 LM79' at 0x290...   No
Probing for `Winbond W83781D' at 0x290...   No
Probing for `Winbond W83782D' at 0x290...   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky 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):
Using driver `i2c-i801' for device :00:1f.3: Intel ICH9
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at 1c60 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x5c
Probing for `Analog Devices ADT7462'... No
Probing for `SMSC EMC1072'...   No
Probing for `SMSC EMC1073'...   No
Probing for `SMSC EMC1074'...   No

Next adapter: i915 gmbus ssc (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus vga (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus panel (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpc (i2c-4)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpb (i2c-5)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpd (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: DPDDC-B (i2c-7)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: DPDDC-C (i2c-8)
Do you want to scan it? (YES/no/selectively):

Next adapter: DPDDC-D (i2c-9)
Do you want to scan it? (YES/no/selectively):


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

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

To load everything that is needed, add

systemd - fancontrol and sensors changed

2014-02-22 Thread Hans-J. Ullrich

Hi folks,

after changing to systemd, I recognized, that fancontrol on my EEEPC did not 
work properly any more. First I noticed nothing, but after some time I 
noticed, the fan did not run at heavy load.

The reason for it, was the changed sensors. According to the debian wiki my 
working configuration looked at this:

 Configuration file generated by pwmconfig, changes will be lost
INTERVAL=5
DEVPATH=hwmon0= hwmon1=devices/platform/eeepc
DEVNAME=hwmon0=acpitz hwmon1=eeepc
FCTEMPS= hwmon1/pwm1=hwmon0/temp1_input
FCFANS= hwmon1/pwm1=
MINTEMP= hwmon1/pwm1=55
MAXTEMP= hwmon1/pwm1=65
MINSTART= hwmon1/pwm1=50
MINSTOP= hwmon1/pwm1=50

This worked very well!

After changing to systemd, this did no more work. I ran pwmconfig again 
(several times, just to make clear, I made no mistake) and now it looks like 
this:

# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=10
DEVPATH=hwmon0= hwmon2=devices/platform/eeepc
DEVNAME=hwmon0=acpitz hwmon2=eeepc
FCTEMPS= hwmon2/pwm1=hwmon0/temp1_input
FCFANS= hwmon2/pwm1=
MINTEMP= hwmon2/pwm1=55
MAXTEMP= hwmon2/pwm1=65
MINSTART= hwmon2/pwm1=150
MINSTOP= hwmon2/pwm1=100 


MINPWM=hwmon2/pwm1=0
MAXPWM=hwmon2/pwm1=255

See the difference? This configuration is working very well.
Don't check the coretemp, this will never start the fan. You must check the 
virtual device. To do so, enter the following into console, like here:

$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:+55.0°C  (crit = +88.0°C)

coretemp-isa-
Adapter: ISA adapter
Core 0:   +35.0°C  (crit = +90.0°C)

eeepc-isa-
Adapter: ISA adapter
fan1:3990 RPM

 
It is not coretemp-isa- the important one (as it would be logical), the 
Virtual device named temp1 is the correct one.

Maybe this should be fixed in the wiki, before someones cpu get overheated.

Just my 2 cents.

Best 

Hans


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/7316965.NdnuKVp7o4@protheus7

Re: lm-sensors sólo detecta 2 cpu de 4 debian wheezy testing

2013-09-16 Thread Camaleón

El Mon, 16 Sep 2013 03:02:26 +0200, Maykel Franco escribió:

 No sé si os habrá pasado alguna vez, pero no consigo que lm_sensors me
 detecte las 4 cpus que tengo. 

Comprueba que tu modelo de micro tenga soporte para 4 cores con cat /
proc/cpuinfo | grep -i name.

Por ejemplo:

sm01@stt008:~$ cat /proc/cpuinfo | grep -i name
model name  : Intel(R) Core(TM)2 Quad CPUQ9550  @ 2.83GHz
model name  : Intel(R) Core(TM)2 Quad CPUQ9550  @ 2.83GHz
model name  : Intel(R) Core(TM)2 Quad CPUQ9550  @ 2.83GHz
model name  : Intel(R) Core(TM)2 Quad CPUQ9550  @ 2.83GHz

Y ese modelo (Q9550) tiene, efectivamente, 4 núcleos (# of Cores   
4):

http://ark.intel.com/products/33924

 Le hice un sensors-detect:
 
 root@debian-netbook:# sensors 
 coretemp-isa- Adapter: ISA adapter
 Core 0:   +59.0°C  (crit = +100.0°C)
 Core 1:   +57.0°C  (crit = +100.0°C)
 
 root@debian-netbook:# cat /proc/cpuinfo | grep -i processor 
 processor   : 0 processor   : 1 processor   : 2
 processor   : 3

(...)

¿Marca y modelo?

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2013.09.16.13.41...@gmail.com

Re: lm-sensors sólo detecta 2 cpu de 4 debian wheezy testing

El día 16 de septiembre de 2013 15:41, Camaleón noela...@gmail.com escribió:
 El Mon, 16 Sep 2013 03:02:26 +0200, Maykel Franco escribió:

 No sé si os habrá pasado alguna vez, pero no consigo que lm_sensors me
 detecte las 4 cpus que tengo.

 Comprueba que tu modelo de micro tenga soporte para 4 cores con cat /
 proc/cpuinfo | grep -i name.

 Por ejemplo:

 sm01@stt008:~$ cat /proc/cpuinfo | grep -i name
 model name  : Intel(R) Core(TM)2 Quad CPUQ9550  @ 2.83GHz
 model name  : Intel(R) Core(TM)2 Quad CPUQ9550  @ 2.83GHz
 model name  : Intel(R) Core(TM)2 Quad CPUQ9550  @ 2.83GHz
 model name  : Intel(R) Core(TM)2 Quad CPUQ9550  @ 2.83GHz

 Y ese modelo (Q9550) tiene, efectivamente, 4 núcleos (# of Cores
 4):

Este también no??

root@debian-netbook:~# cat /proc/cpuinfo | grep -i name
model name  : Intel(R) Atom(TM) CPU N550   @ 1.50GHz
model name  : Intel(R) Atom(TM) CPU N550   @ 1.50GHz
model name  : Intel(R) Atom(TM) CPU N550   @ 1.50GHz
model name  : Intel(R) Atom(TM) CPU N550   @ 1.50GHz


 http://ark.intel.com/products/33924

 Le hice un sensors-detect:

 root@debian-netbook:# sensors
 coretemp-isa- Adapter: ISA adapter
 Core 0:   +59.0°C  (crit = +100.0°C)
 Core 1:   +57.0°C  (crit = +100.0°C)

 root@debian-netbook:# cat /proc/cpuinfo | grep -i processor
 processor   : 0 processor   : 1 processor   : 2
 processor   : 3

 (...)

 ¿Marca y modelo?

El portatil en cuestion es este, TOSHIBA NB520 dejo mas info:

description: Notebook
product: TOSHIBA NB520 (012345678912345678912345678)
vendor: TOSHIBA
version: PLL52E-00E008CE
serial: YA478944K
width: 64 bits
capabilities: smbios-2.5 dmi-2.5 vsyscall32
configuration: boot=oem-specific chassis=notebook
family=ABCDEFGHIJKLMNOPQRSTUVWXYZ sku=012345678912345678912345678
uuid=5D8EED16-EEC5-11DF-A632-1C75086FAA5E
  *-core
   description: Motherboard
   product: PBU00
   vendor: TOSHIBA
   physical id: 0
   version: 1.00
   serial: 0123456789AB
 *-firmware
  description: BIOS
  vendor: TOSHIBA
  physical id: 0
  version: V1.90
  date: 06/02/2011
  size: 100KiB
  capacity: 448KiB
  capabilities: pci pcmcia pnp upgrade shadowing cdboot
bootselect int13floppytoshiba int5printscreen int9keyboard int14serial
int17printer int10video acpi usb agp smartbattery
biosbootspecification
 *-cpu
  description: CPU
  product: Intel(R) Atom(TM) CPU N550   @ 1.50GHz
  vendor: Intel Corp.
  physical id: 4
  bus info: cpu@0
  version: A0
  slot: U2E1
  size: 1500MHz
  capacity: 2048MHz
  width: 64 bits
  clock: 166MHz
  capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr
pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr
sse sse2 ss ht tm pbe syscall nx constant_tsc arch_perfmon pebs bts
rep_good nopl aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16
xtpr pdcm movbe lahf_lm dtherm cpufreq
  configuration: cores=2 enabledcores=2 threads=4
*-cache:0
 description: L1 cache
 physical id: 5
 slot: L1 Cache
 size: 32KiB
 capacity: 32KiB
 capabilities: asynchronous internal write-back
*-cache:1
 description: L2 cache
 physical id: 6
 slot: L2 Cache
 size: 512KiB
 capacity: 512KiB
 capabilities: burst external write-back

Este fué el portatil que al final le he metido debian testing o jessi
y que tuve el problema de managed=true del famoso network manager
jejeje.

Viene con un 1GB de ram y con un hdd 5400 rpm, lo he tuneado un
pelin y le he metido 2 GB de ram(solo tiene un banco de memoria) y le
he quitado el disco duro y le he metido un ssd ocz agility. Le instale
kde 4.10-5 desactivando efectos de escritorio, desactivando nepomuk y
akonadi y la verdad es que va muy muy fino con debian testing. Así
aprovecho para probar debian testing que nunca lo he probado(deseando
que saquen la version 4.11.1 de kde jeje).

Gracias por todo.


 Saludos,

 --
 Camaleón


 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/pan.2013.09.16.13.41...@gmail.com



--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAJ2aOA8qZ3Mr0X-5OXoC6KFGRFQC-2B8eizmMqwVW=-ytyi...@mail.gmail.com

Re: lm-sensors sólo detecta 2 cpu de 4 debian wheezy testing

2013-09-16 Thread Camaleón

El Mon, 16 Sep 2013 16:21:20 +0200, Maykel Franco escribió:

 El día 16 de septiembre de 2013 15:41, Camaleón noela...@gmail.com
 escribió:

(...)

 Comprueba que tu modelo de micro tenga soporte para 4 cores con cat /
 proc/cpuinfo | grep -i name.

 Por ejemplo:

 sm01@stt008:~$ cat /proc/cpuinfo | grep -i name 
 model name  : Intel(R) Core(TM)2 Quad CPUQ9550  @ 2.83GHz

(...)

 Y ese modelo (Q9550) tiene, efectivamente, 4 núcleos (# of Cores 4):
 
 Este también no??
 
 root@debian-netbook:~# cat /proc/cpuinfo | grep -i name 
 model name  : Intel(R) Atom(TM) CPU N550   @ 1.50GHz 

Huy... pues va a ser que no :-P

***
http://ark.intel.com/products/50154/Intel-Atom-Processor-N550-1M-Cache-1_50-GHz?q=N550

# of Cores  2
***

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2013.09.16.14.27...@gmail.com

Re: lm-sensors sólo detecta 2 cpu de 4 debian wheezy testing

El día 16 de septiembre de 2013 17:01, Javier Silva
fjsil...@gmail.com escribió:
 2013/9/16 Maykel Franco maykeldeb...@gmail.com:
 configuration: cores=2 enabledcores=2 threads=4

 Fíjate en la línea anterior, dice 2 núcleos (cores), 2 activos y 4 hilos.

 Algunos procesadores de intel (no todos) tienen lo que se denomina
 hyperthreading, hace que tenga dos hilos 'paralelos' de cada núcleo
 físico. No tiene el rendimiento de tener los núcleos físicos, pero
 bajo determinadas circunstancias se gana algo de velocidad de
 ejecución.

 Accede al enlace que te ha dejado Camaleón hacia la página de Intel,
 donde podrás consultar toda la información sobre las características
 de tu micro.

 Saludos,
 Javier Silva.


 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/caog_h5zmerofdo3+darrdwax+fd6cfp6w7tjssuct4afyel...@mail.gmail.com



Sí lo he visto, muchas gracias. Me he dejado llevar por el comando cat
/proc/cpuinfo jejeje.

Saludos.


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caj2aoa8hlkmwmffmdrd7g9gkhp98xjc4yhlfpi1c4mgbbjn...@mail.gmail.com

Re: lm-sensors sólo detecta 2 cpu de 4 debian wheezy testing

El día 16 de septiembre de 2013 16:49, Maykel Franco
maykeldeb...@gmail.com escribió:
 El día 16 de septiembre de 2013 16:27, Camaleón noela...@gmail.com escribió:
 El Mon, 16 Sep 2013 16:21:20 +0200, Maykel Franco escribió:

 El día 16 de septiembre de 2013 15:41, Camaleón noela...@gmail.com
 escribió:

 (...)

 Comprueba que tu modelo de micro tenga soporte para 4 cores con cat /
 proc/cpuinfo | grep -i name.

 Por ejemplo:

 sm01@stt008:~$ cat /proc/cpuinfo | grep -i name
 model name  : Intel(R) Core(TM)2 Quad CPUQ9550  @ 2.83GHz

 (...)

 Y ese modelo (Q9550) tiene, efectivamente, 4 núcleos (# of Cores 4):

 Este también no??

 root@debian-netbook:~# cat /proc/cpuinfo | grep -i name
 model name  : Intel(R) Atom(TM) CPU N550   @ 1.50GHz

 Huy... pues va a ser que no :-P

 ***
 http://ark.intel.com/products/50154/Intel-Atom-Processor-N550-1M-Cache-1_50-GHz?q=N550

 # of Cores  2

 Pero el comando que me has pasado devuelve 4 no??

 mm ya veo hyperthreading...xDD. Quizá me guiado por comando en vez de
 ver la especificacion del hardware. Ejecuta ambos procesadores(2)
 simultáneamente las instrucciones.

 Gracias a todos chicos.

 Saludos.

 ***

 Saludos,

 --
 Camaleón


 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/pan.2013.09.16.14.27...@gmail.com



Comando también muy útil:

root@debian-netbook:~# lscpu
Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):4
On-line CPU(s) list:   0-3
Thread(s) per core:2
Core(s) per socket:2
Socket(s): 1
NUMA node(s):  1
Vendor ID: GenuineIntel
CPU family:6
Model: 28
Stepping:  10
CPU MHz:   1000.000
BogoMIPS:  2992.31
L1d cache: 24K
L1i cache: 32K
L2 cache:  512K
NUMA node0 CPU(s): 0-3


Concretamente, Thread(s) per core:2 . Yo no lo conocía.

Imagino que en el portatil profesional que uso en casa :

Toshiba Portege Z930-145 i5-3317U


http://www.pccomponentes.com/toshiba_portege_z930_145_i5_3317u_4gb_128gb_ssd_13_3_.html

Pasa exáctamente lo mismo??

linux-x45d:/home/maykel/Downloads # lscpu
Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):4
On-line CPU(s) list:   0-3
Thread(s) per core:2
Core(s) per socket:2
Socket(s): 1
NUMA node(s):  1
Vendor ID: GenuineIntel
CPU family:6
Model: 58
Stepping:  9
CPU MHz:   782.000
BogoMIPS:  3392.35
Virtualization:VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache:  256K
L3 cache:  3072K
NUMA node0 CPU(s): 0-3

Y yo que pensaba que en este sí que tenía 4 procesadores...


Saludos.


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caj2aoa_g1we0jydfuvcbubsyhdmbvo83ot-az-syl1epy2g...@mail.gmail.com

Re: lm-sensors sólo detecta 2 cpu de 4 debian wheezy testing

El día 16 de septiembre de 2013 16:27, Camaleón noela...@gmail.com escribió:
 El Mon, 16 Sep 2013 16:21:20 +0200, Maykel Franco escribió:

 El día 16 de septiembre de 2013 15:41, Camaleón noela...@gmail.com
 escribió:

 (...)

 Comprueba que tu modelo de micro tenga soporte para 4 cores con cat /
 proc/cpuinfo | grep -i name.

 Por ejemplo:

 sm01@stt008:~$ cat /proc/cpuinfo | grep -i name
 model name  : Intel(R) Core(TM)2 Quad CPUQ9550  @ 2.83GHz

 (...)

 Y ese modelo (Q9550) tiene, efectivamente, 4 núcleos (# of Cores 4):

 Este también no??

 root@debian-netbook:~# cat /proc/cpuinfo | grep -i name
 model name  : Intel(R) Atom(TM) CPU N550   @ 1.50GHz

 Huy... pues va a ser que no :-P

 ***
 http://ark.intel.com/products/50154/Intel-Atom-Processor-N550-1M-Cache-1_50-GHz?q=N550

 # of Cores  2

Pero el comando que me has pasado devuelve 4 no??

mm ya veo hyperthreading...xDD. Quizá me guiado por comando en vez de
ver la especificacion del hardware. Ejecuta ambos procesadores(2)
simultáneamente las instrucciones.

Gracias a todos chicos.

Saludos.

 ***

 Saludos,

 --
 Camaleón


 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/pan.2013.09.16.14.27...@gmail.com



--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAJ2aOA88d+Avmwug+Es36DjBqR8QbVxtKOisVqhmfMRA3=m...@mail.gmail.com

Re: lm-sensors sólo detecta 2 cpu de 4 debian wheezy testing

2013-09-16 Thread Javier Silva

2013/9/16 Maykel Franco maykeldeb...@gmail.com:
 configuration: cores=2 enabledcores=2 threads=4

Fíjate en la línea anterior, dice 2 núcleos (cores), 2 activos y 4 hilos.

Algunos procesadores de intel (no todos) tienen lo que se denomina
hyperthreading, hace que tenga dos hilos 'paralelos' de cada núcleo
físico. No tiene el rendimiento de tener los núcleos físicos, pero
bajo determinadas circunstancias se gana algo de velocidad de
ejecución.

Accede al enlace que te ha dejado Camaleón hacia la página de Intel,
donde podrás consultar toda la información sobre las características
de tu micro.

Saludos,
Javier Silva.


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caog_h5zmerofdo3+darrdwax+fd6cfp6w7tjssuct4afyel...@mail.gmail.com

Re: lm-sensors sólo detecta 2 cpu de 4 debian wheezy testing

2013/9/16 Camaleón noela...@gmail.com:
 El Mon, 16 Sep 2013 17:01:19 +0200, Maykel Franco escribió:

 Comando también muy útil:

 root@debian-netbook:~# lscpu
 (...)
 Thread(s) per core:2
 Core(s) per socket:2
 Socket(s): 1
 (...)
 CPU MHz:   1000.000
 (...)
 L2 cache:  512K

 Pues sí, tampoco lo conocía. Interesante:

Como digo muchas veces, siempre se aprende algo.


 sm01@stt008:~$ lscpu
 Architecture:  x86_64
 CPU op-mode(s):32-bit, 64-bit
 Byte Order:Little Endian
 CPU(s):4
 On-line CPU(s) list:   0-3
 Thread(s) per core:1
 Core(s) per socket:4
 Socket(s): 1
 NUMA node(s):  1
 Vendor ID: GenuineIntel
 CPU family:6
 Model: 23
 Stepping:  10
 CPU MHz:   2000.000
 BogoMIPS:  5667.05
 Virtualization:VT-x
 L1d cache: 32K
 L1i cache: 32K
 L2 cache:  6144K
 NUMA node0 CPU(s): 0-3

 En mi caso, el micro que tengo NO dispone de HT.

 Concretamente, Thread(s) per core:2 . Yo no lo conocía.

 Y el valor de caché de segundo nivel, también es un dato importante, al
 menos para los modelos antiguos o los que no disponen de QuickPath.

Interesante:

http://www.intel.la/content/www/xl/es/io/quickpath-technology/quickpath-technology-general.html

Tampoco lo conocía.

Thanks.

 Imagino que en el portatil profesional que uso en casa :

 Toshiba Portege Z930-145 i5-3317U


 http://www.pccomponentes.com/
 toshiba_portege_z930_145_i5_3317u_4gb_128gb_ssd_13_3_.html

 Pasa exáctamente lo mismo??

 linux-x45d:/home/maykel/Downloads # lscpu
 Architecture:  x86_64
 CPU op-mode(s):32-bit, 64-bit
 Byte Order:Little Endian
 CPU(s):4
 On-line CPU(s) list:   0-3
 Thread(s) per core:2
 Core(s) per socket:2
 Socket(s): 1
 NUMA node(s):  1
 Vendor ID: GenuineIntel
 CPU family:6
 Model: 58
 Stepping:  9
 CPU MHz:   782.000
 BogoMIPS:  3392.35
 Virtualization:VT-x
 L1d cache: 32K
 L1i cache: 32K
 L2 cache:  256K
 L3 cache:  3072K
 NUMA node0 CPU(s): 0-3

 Y yo que pensaba que en este sí que tenía 4 procesadores...

 Je, ahora todo pasa por la virtualización y  la paralelización, hasta
 los núcleos del micro ;-)

 Saludos,

 --
 Camaleón


 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/pan.2013.09.16.15.19...@gmail.com



--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caj2aoa8uhtzo6qhaz-pauplkjx8-qq769mky11+gdq2mcar...@mail.gmail.com

Re: lm-sensors sólo detecta 2 cpu de 4 debian wheezy testing

2013-09-16 Thread Camaleón

El Mon, 16 Sep 2013 17:01:19 +0200, Maykel Franco escribió:

 Comando también muy útil:
 
 root@debian-netbook:~# lscpu
(...)
 Thread(s) per core:2
 Core(s) per socket:2
 Socket(s): 1
(...)
 CPU MHz:   1000.000
(...)
 L2 cache:  512K

Pues sí, tampoco lo conocía. Interesante:

sm01@stt008:~$ lscpu
Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):4
On-line CPU(s) list:   0-3
Thread(s) per core:1
Core(s) per socket:4
Socket(s): 1
NUMA node(s):  1
Vendor ID: GenuineIntel
CPU family:6
Model: 23
Stepping:  10
CPU MHz:   2000.000
BogoMIPS:  5667.05
Virtualization:VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache:  6144K
NUMA node0 CPU(s): 0-3

En mi caso, el micro que tengo NO dispone de HT.

 Concretamente, Thread(s) per core:2 . Yo no lo conocía.

Y el valor de caché de segundo nivel, también es un dato importante, al 
menos para los modelos antiguos o los que no disponen de QuickPath.

 Imagino que en el portatil profesional que uso en casa :
 
 Toshiba Portege Z930-145 i5-3317U
 
 
 http://www.pccomponentes.com/
toshiba_portege_z930_145_i5_3317u_4gb_128gb_ssd_13_3_.html
 
 Pasa exáctamente lo mismo??
 
 linux-x45d:/home/maykel/Downloads # lscpu
 Architecture:  x86_64
 CPU op-mode(s):32-bit, 64-bit
 Byte Order:Little Endian
 CPU(s):4
 On-line CPU(s) list:   0-3
 Thread(s) per core:2
 Core(s) per socket:2
 Socket(s): 1
 NUMA node(s):  1
 Vendor ID: GenuineIntel
 CPU family:6
 Model: 58
 Stepping:  9
 CPU MHz:   782.000
 BogoMIPS:  3392.35
 Virtualization:VT-x
 L1d cache: 32K
 L1i cache: 32K
 L2 cache:  256K
 L3 cache:  3072K
 NUMA node0 CPU(s): 0-3
 
 Y yo que pensaba que en este sí que tenía 4 procesadores...

Je, ahora todo pasa por la virtualización y  la paralelización, hasta 
los núcleos del micro ;-)

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2013.09.16.15.19...@gmail.com

Re: lm-sensors sólo detecta 2 cpu de 4 debian wheezy testing