cpu temp. im terminal

[docNet]

hi

kann mir jemand sagen wie ich mir die cpu temp. über die comandozeile (terminal) anzeigen lassen kann? bin für jeden tipp dankbar:-)
google hat mir nicht wirklich weiter geholfen

thx docNet

[QT]

Das hängt davon ab, mit welchen Treibern Du diese Info bei Dir bekommst. Wenn Du lm-sensors nutzt, dann mit dem Kommando "sensors", wenn Du die Info per ACPI bekommst, dann mit "acpi -t".

[docNet]

hi,
und viellen dank für die antwort aber,
das weiß ich leider nicht genau
aber mit sensors bekomme ich folgendes :

Code: Alles auswählen

linux:/home/docnet # sensors
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs!
For older kernels, make sure you have done 'modprobe i2c-proc'!

im moment läuft auf dem rechner wieder suse91 pro.

[docNet]

okey bei meinen laptop funz. acpi -t
aber bein pc ??
thx...

[brainchild]

Hast Du nach der Installation von lm-sensors auch sensors-detect aufgerufen und die entsprechenden Module in /etc/modules eingetragen?

Dann kannst Du Dir die Temperatur mit folgendem einzeiler anzeigen lassen:

Code: Alles auswählen

sensors | awk '/CPU Temp/ {print $3}'

Grüße Kai

[docNet]

nach auf ruf von sensors-detect:

Code: Alles auswählen

linux:/home/docnet # sensors-detect
 
This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
 
 We can start with probing for (PCI) I2C or SMBus adapters.
 You do not need any special privileges for this.
 Do you want to probe now? (YES/no): yes
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801DB ICH4
Use driver `rivatv' for device 01:00.0: GeForce2 MX
Probe succesfully concluded.
 
 We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no): yes
Module loaded succesfully.
Load `rivatv' (say NO if built into your kernel)? (YES/no): yes
FATAL: Module rivatv not found.
Loading failed... skipping.
** Note: rivatv module is available at http://rivatv.sourceforge.net/
 Do you now want to be prompted for non-detectable adapters? (yes/NO): yes
Load `i2c-elektor' (say NO if built into your kernel)? (YES/no): y
FATAL: Error inserting i2c_elektor (/lib/modules/2.6.5-7.108-default/kernel/drivers/i2c/busses/i2c-elektor.ko): No such device
Loading failed... skipping.
Load `i2c-elv' (say NO if built into your kernel)? (YES/no): y
FATAL: Module i2c_elv not found.
Loading failed... skipping.
Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no): yes
FATAL: Module i2c_philips_par not found.
Loading failed... skipping.
Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): s
FATAL: Module i2c_velleman not found.
Loading failed... skipping.
 To continue, we need module `i2c-dev' to be loaded.
 If it is built-in into your kernel, you can safely skip this.
 i2c-dev is not loaded. Do you want to load it now? (YES/no): y
 Module loaded succesfully.
 
 We are now going to do the adapter probings. Some adapters may hang halfway
 through; we can't really help that. Also, some chips will be double detected;
 we choose the one with the highest confidence value in that case.
 If you found that the adapter hung after probing a certain address, you can
 specify that address to remain unprobed. That often
 includes address 0x69 (clock chip).
 
Next adapter: SMBus I801 adapter at e800 (Algorithm unavailable)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x00
Client found at address 0x08
Client found at address 0x2d
Probing for `Myson MTP008'... Failed!
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `National Semiconductor LM85'... Failed!
Probing for `Analog Devices ADM1027 or ADT7463'... Failed!
Probing for `SMSC EMC6D100 and EMC6D101'... Failed!
Probing for `National Semiconductor LM87'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83783S'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Success!
    (confidence 8, driver `asb100'), other addresses: 0x48 0x49
Probing for `Winbond W83L784R/AR'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x00'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x80'... Failed!
Probing for `Genesys Logic GL520SM'... Failed!
Probing for `Genesys Logic GL525SM'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1026'... Failed!
Probing for `Analog Devices ADM1025'... Failed!
Probing for `Philips NE1619'... Failed!
Probing for `Analog Devices ADM1024'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `Analog Devices ADM1030'... Failed!
Probing for `Analog Devices ADM1031'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'... Failed!
Client found at address 0x30
Client found at address 0x31
Client found at address 0x44
Client found at address 0x48
Probing for `National Semiconductor LM75'... Failed!
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Maxim MAX6650/MAX6651'... Failed!
Client found at address 0x4e
Probing for `National Semiconductor LM75'... Failed!
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Analog Devices ADM1021'... Failed!
Probing for `Analog Devices ADM1021A/ADM1023'... Failed!
Probing for `Maxim MAX1617'... Success!
    (confidence 3, driver `adm1021')
Probing for `Maxim MAX1617A'... Failed!
Probing for `TI THMC10'... Failed!
Probing for `National Semiconductor LM84'... Success!
    (confidence 5, driver `adm1021')
Probing for `Genesys Logic GL523SM'... Failed!
Probing for `Onsemi MC1066'... Failed!
Probing for `National Semiconductor LM82'... Failed!
Probing for `National Semiconductor LM83'... Failed!
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
 
 Some chips are also accessible through the ISA bus. ISA probes are
 typically a bit more dangerous, as we have to write to I/O ports to do
 this.  Do you want to scan the ISA bus? (YES/no): y
Probing for `National Semiconductor LM78'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
  Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
  Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
  Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
  Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
  Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
  Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
  Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
  Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
  Trying address 0x0ca8... Failed!
 
 Some Super I/O chips may also contain sensors. Super I/O probes are
 typically a bit more dangerous, as we have to write to I/O ports to do
 this.  Do you want to scan for Super I/O sensors? (YES/no): y
Probing for `ITE 8712F Super IO Sensors'
  Failed! (0x8708)
Probing for `SMSC 47M10x Super IO Fan Sensors'
  Failed!
Probing for `SMSC 47M14x Super IO Fan Sensors'
  Failed!
Probing for `VT1211 Super IO Sensors'
  Failed! (0x87)
Probing for `Winbond W83627HF Super IO Sensors'
  Failed! (0x87)
Probing for `Winbond W83627THF Super IO Sensors'
  Failed! (0x87)
Probing for `Winbond W83637HF Super IO Sensors'
  Failed! (0x87)
Probing for `Winbond W83697HF Super IO Sensors'
  Failed! (0x87)
Probing for `Winbond W83697UF Super IO PWM'
  Failed! (0x87)
 
 Now follows a summary of the probes I have just done.
 Just press ENTER to continue:
 
Driver `asb100' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at e800' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x2d (and 0x48 0x49)
    Chip `Asus ASB100 Bach' (confidence: 8)
 
Driver `adm1021' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at e800' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x4e
    Chip `National Semiconductor LM84' (confidence: 5)
 
Driver `eeprom' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at e800' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x50
    Chip `SPD EEPROM' (confidence: 8)
  * Bus `SMBus I801 adapter at e800' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x51
    Chip `SPD EEPROM' (confidence: 8)
 
 
 I will now generate the commands needed to load the I2C modules.
 Sometimes, a chip is available both through the ISA bus and an I2C bus.
 ISA bus access is faster, but you need to load an additional driver module
 for it. If you have the choice, do you want to use the ISA bus or the
 I2C/SMBus (ISA/smbus)? ISA
 
To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:
 
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
 
To load everything that is needed, add this to some /etc/rc* file:
 
#----cut here----
# I2C adapter drivers
modprobe i2c-i801
# I2C chip drivers
modprobe asb100
modprobe adm1021
modprobe eeprom
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----
 
WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.
 
Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): y
Copy /usr/share/doc/packages/sensors/prog/init/lm_sensors.init.suse
to /etc/init.d/lm_sensors for initialization at boot time.
linux:/home/docnet # sensors
No sensors found!
linux:/home/docnet #
linux:/home/docnet #

hmm??
was mach ich falsch ?

Hast Du nach der Installation von lm-sensors auch sensors-detect aufgerufen und die entsprechenden Module in /etc/modules eingetragen?

wie müsste die /etc/modules aussehen?

[brainchild]

Hast Du das hier so weitesgehend befolgt?

To load everything that is needed, add this to some /etc/rc* file:

# I2C adapter drivers
modprobe i2c-i801
# I2C chip drivers
modprobe asb100
modprobe adm1021
modprobe eeprom
# sleep 2 # optional
/usr/bin/sensors -s

Alternativ kannst Du die Module ja erste einmal per Hand laden, dann ein sensors -s aufrufen und dann sollte sensors Dir auch sensoren und deren Werte anzeigen.

Grüße Kai

[edit]
schau Dir mal /etc/init.d/lm_sensors. Könnte mir vorstellen das es da schion drinnen steht. Wenn ja dann brauchste es nur noch starten.
[/edit]

[ThoWaBu]

Probier doch mal mbmon ...

[Goth]

wenn ich sensors eingebe bekomm ich folgendes


Philips PAL_BG -i2c-0-61 Adapter: bt878 #0 [sw] MSP3415D-i2c-0-40 Adapter: bt878 #0 [sw]

komisch was??