[Comm] Не могу посмотреть температуру процессора и обороты вентилятора

Chernetsky Andrey andy_ch на open.by
Вт Июн 11 11:30:54 MSK 2013


Система установленный p7
andy на mycomp ~ $ sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
Вывод команды sensors-detect во вложении.
andy на mycomp ~ $ sudo lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] nee ATI RS690 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices [AMD] nee ATI RS690 PCI to PCI Bridge (PCI
Express Graphics Port 0)
00:05.0 PCI bridge: Advanced Micro Devices [AMD] nee ATI RS690 PCI to PCI Bridge (PCI
Express Port 1)
00:11.0 SATA controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA
Controller [IDE mode]
00:12.0 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB
OHCI0 Controller
00:12.1 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0 USB OHCI1
Controller
00:12.2 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB
EHCI Controller
00:13.0 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB
OHCI0 Controller
00:13.1 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0 USB OHCI1
Controller
00:13.2 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB
EHCI Controller
00:14.0 SMBus: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus Controller (rev 3a)
00:14.1 IDE interface: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 IDE
Controller
00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 LPC host
controller
00:14.4 PCI bridge: Advanced Micro Devices [AMD] nee ATI SBx00 PCI to PCI Bridge
00:14.5 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB
OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM
Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous
Control
01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce 9800 GT] (rev a2)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express
Gigabit Ethernet controller (rev 02)
03:03.0 Mass storage controller: Promise Technology, Inc. PDC20262
(FastTrak66/Ultra66) (rev 01)


-- 
С уважением,
Андрей!




----------- следующая часть -----------
andy на mycomp ~ $ sudo sensors-detect
# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
# System: MICRO-STAR INTERNATIONAL CO.,LTD MS-7302 [1.0]

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): y
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   Success!
    (driver `k8temp')
    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
    Intel digital thermal sensor...                             No
    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): y
    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'...               Yes
    Found `Fintek F71882FG/F71883FG Super IO Sensors'           Success!
        (address 0x600, driver `f71882fg')

	Some systems (mainly servers) implement IPMI, a set of common interfaces
	through which system health data may be retrieved, amongst other things.
	We first try to get the information from SMBIOS. If we don't find it
	there, we have to read from arbitrary I/O ports to probe for such
	interfaces. This is normally safe. Do you want to scan for IPMI
	interfaces? (YES/no): y
	Probing for `IPMI BMC KCS' at 0xca0...                      No
	Probing for `IPMI BMC SMIC' at 0xca8...                     No

	Some hardware monitoring chips are accessible through the ISA I/O 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): y
	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): y
	Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus
	Module i2c-dev loaded successfully.

	Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x28
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM96080'...             No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Analog Devices ADM1029'...                     No
Probing for `ITE IT8712F'...                                No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
    Probing for `EDID EEPROM'...                                No
    Client found at address 0x51
    Probing for `Analog Devices ADM1033'...                     No
    Probing for `Analog Devices ADM1034'...                     No
    Probing for `SPD EEPROM'...                                 Yes
        (confidence 8, not a hardware monitoring chip)

	Next adapter: SMBus PIIX4 adapter at 0b20 (i2c-1)
	Do you want to scan it? (yes/NO/selectively): y
	Client found at address 0x4f
	Probing for `National Semiconductor LM75'...                No
	Probing for `National Semiconductor LM75A'...               No
	Probing for `Dallas Semiconductor DS75'...                  No
	Probing for `Dallas Semiconductor DS1621/DS1631'...         No
	Probing for `Maxim MAX6642'...                              No
	Probing for `Texas Instruments TMP421'...                   No
	Probing for `Texas Instruments TMP422'...                   No
	Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
	Probing for `NXP/Philips SA56004'...                        No

	Next adapter: NVIDIA i2c adapter 0 at 1:00.0 (i2c-2)
	Do you want to scan it? (YES/no/selectively): y
	Client found at address 0x49
	Probing for `National Semiconductor LM75'...                No
	Probing for `National Semiconductor LM75A'...               No
	Probing for `Dallas Semiconductor DS75'...                  No
	Probing for `National Semiconductor LM77'...                No
	Probing for `Analog Devices ADT7410'...                     No
	Probing for `Dallas Semiconductor DS1621/DS1631'...         No
	Probing for `Maxim MAX6642'...                              No
	Probing for `National Semiconductor LM73'...                No
	Probing for `National Semiconductor LM92'...                No
	Probing for `National Semiconductor LM76'...                No
	Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
	Probing for `NXP/Philips SA56004'...                        No
	Probing for `SMSC EMC1023'...                               No
	Probing for `SMSC EMC1043'...                               No
	Probing for `SMSC EMC1053'...                               No
	Probing for `SMSC EMC1063'...                               No
	Client found at address 0x50
	Probing for `Analog Devices ADM1033'...                     No
	Probing for `Analog Devices ADM1034'...                     No
	Probing for `SPD EEPROM'...                                 No
	Probing for `EDID EEPROM'...                                Yes
	    (confidence 8, not a hardware monitoring chip)
Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-3)
Do you want to scan it? (YES/no/selectively): y

Next adapter: NVIDIA i2c adapter 2 at 1:00.0 (i2c-4)
Do you want to scan it? (YES/no/selectively): y

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

Driver `k8temp':
  * Chip `AMD K8 thermal sensors' (confidence: 9)

  Driver `f71882fg':
    * ISA bus, address 0x600
        Chip `Fintek F71882FG/F71883FG Super IO Sensors' (confidence: 9)

	Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): y
	Copy prog/init/lm_sensors.service to /lib/systemd/system
	and run 'systemctl enable lm_sensors.service'
	for initialization at boot time.
	Unloading i2c-dev... OK
	Unloading cpuid... OK



Подробная информация о списке рассылки community