Форум русскоязычного сообщества Ubuntu


Увидели сообщение с непонятной ссылкой, спам, непристойность или оскорбление?
Воспользуйтесь ссылкой «Сообщить модератору» рядом с сообщением!

Автор Тема: Не удается посмотреть температуру процессора  (Прочитано 902 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн damix

  • Автор темы
  • Новичок
  • *
  • Сообщений: 27
    • Просмотр профиля
Не могу проверить температуру процессора и другого оборудования, у которого есть соответствующие датчики. Это новый компьютер, я только установил на него линукс. На старом компьютере температуру смотрел так
sensorsСейчас эта команда выдает
$ sensors
amdgpu-pci-3800
Adapter: PCI adapter
fan1:             N/A
temp1:         +0.0°C  (crit =  +0.0°C, hyst =  +0.0°C)
Программа была установлена так
sudo apt install lm-sensors
sudo sensors-detect
На все вопросы ответил enter'ом.
Вывод второй команды
$ sudo sensors-detect
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: Micro-Star International Co., Ltd. MS-7A34 [2.0]
# Board: Micro-Star International Co., Ltd. B350 PC MATE (MS-7A34)
# Kernel: 4.15.0-22-generic x86_64
# Processor: AMD Ryzen 3 2200G with Radeon Vega Graphics (23/17/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):
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 16h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 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'...               Yes
Found unknown chip with ID 0xd352

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):
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):
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):
Found unknown SMBus adapter 1022:790b at 0000:00:14.0.
Sorry, no supported PCI bus adapters found.

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x1c
Probing for `Texas Instruments TMP421'...                   No
Probing for `Texas Instruments TMP441'...                   No
Probing for `SMSC EMC1072'...                               No
Probing for `SMSC EMC1073'...                               No
Probing for `SMSC EMC1074'...                               No
Probing for `ST STTS424'...                                 No
Probing for `ST STTS424E'...                                No
Probing for `ST STTS2002'...                                No
Probing for `ST STTS3000'...                                No
Probing for `NXP SE97/SE97B'...                             No
Probing for `NXP SE98'...                                   No
Probing for `Analog Devices ADT7408'...                     No
Probing for `IDT TS3000/TSE2002'...                         No
Probing for `IDT TSE2004'...                                No
Probing for `IDT TS3001'...                                 No
Probing for `Maxim MAX6604'...                              No
Probing for `Microchip MCP9804'...                          No
Probing for `Microchip MCP98242'...                         No
Probing for `Microchip MCP98243'...                         No
Probing for `Microchip MCP98244'...                         No
Probing for `Microchip MCP9843'...                          No
Probing for `ON CAT6095/CAT34TS02'...                       No
Probing for `Atmel AT30TS00'...                             No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No

Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1)
Do you want to scan it? (YES/no/selectively):

Next adapter: SMBus PIIX4 adapter port 3 at 0b00 (i2c-2)
Do you want to scan it? (YES/no/selectively):

Next adapter: SMBus PIIX4 adapter port 4 at 0b00 (i2c-3)
Do you want to scan it? (YES/no/selectively):

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-4)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-5)
Do you want to scan it? (yes/NO/selectively):

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

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-7)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM i2c hw bus 3 (i2c-8)
Do you want to scan it? (yes/NO/selectively):

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.

Процессор: AMD Ryzen 3 2200G
ОС: Kubuntu 18.04 LTS
$ inxi -Fxz
System:    Host: ryzen Kernel: 4.15.0-22-generic x86_64 bits: 64 gcc: 7.3.0
           Desktop: KDE Plasma 5.12.5 (Qt 5.9.5) Distro: Ubuntu 18.04 LTS                                                           
Machine:   Device: desktop Mobo: Micro-Star model: B350 PC MATE (MS-7A34) v: 2.0 serial: N/A                                         
           UEFI: American Megatrends v: A.D0 date: 03/16/2018                                                                       
CPU:       Quad core AMD Ryzen 3 2200G with Radeon Vega Graphics (-MCP-) arch: Zen rev.0 cache: 2048 KB                             
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 28001                                                   
           clock speeds: max: 2221 MHz 1: 1455 MHz 2: 1475 MHz 3: 2221 MHz 4: 1447 MHz                                               
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Vega [Radeon Vega 8 Mobile] bus-ID: 38:00.0                                       
           Display Server: x11 (X.Org 1.19.6 ) drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon)                         
           Resolution: 1920x1080@60.00hz                                                                                             
           OpenGL: renderer: AMD RAVEN (DRM 3.23.0 / 4.15.0-22-generic, LLVM 6.0.0)                                                 
           version: 4.5 Mesa 18.0.0-rc5 Direct Render: Yes                                                                           
Audio:     Card-1 Advanced Micro Devices [AMD] Device 15e3 driver: snd_hda_intel bus-ID: 38:00.6                                     
           Card-2 Advanced Micro Devices [AMD/ATI] Device 15de driver: snd_hda_intel bus-ID: 38:00.1                                 
           Sound: Advanced Linux Sound Architecture v: k4.15.0-22-generic                                                           
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller                                                   
           driver: r8169 v: 2.3LK-NAPI port: f000 bus-ID: 1e:00.0                                                                   
           IF: enp30s0 state: up speed: 100 Mbps duplex: full mac: <filter>                                                         
Drives:    HDD Total Size: 480.1GB (18.9% used)                                                                                     
           ID-1: /dev/sda model: KINGSTON_SA400S3 size: 480.1GB temp: 31C                                                           
Partition: ID-1: / size: 94G used: 7.1G (8%) fs: ext4 dev: /dev/sda2                                                                 
           ID-2: /home size: 338G used: 70G (22%) fs: ext4 dev: /dev/sda4                                                           
           ID-3: swap-1 size: 8.19GB used: 0.00GB (0%) fs: swap dev: /dev/sda3                                                       
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present                                                               
Sensors:   System Temperatures: cpu: No active sensors found. Have you configured your sensors yet? mobo: N/A gpu: 0.0               
Info:      Processes: 190 Uptime: 1:40 Memory: 2164.3/3698.8MB Init: systemd runlevel: 5 Gcc sys: N/A                               
           Client: Shell (bash 4.4.191) inxi: 2.3.56

Сейчас удается узнать только температуру жесткого диска командой hddtemp /dev/sda.
Пытался посмотреть в /sys/devices/platform/coretemp.0/, но такой папки нет.
$ ls /sys/devices/platform/
alarmtimer/        Fixed MDIO bus.0/  PNP0103:00/        PNP0C14:01/        serial8250/       
AMDI0030:00/       microcode/         PNP0C0C:00/        power/             uevent             
efi-framebuffer.0/ pcspkr/

Как настроить lm-sensors или воспользоваться другой программой, которая может показать температуру устройств? Как вариант, через виртуальный файловые системы линукса, вроде /sys/.

Оффлайн Morisson

  • Модератор раздела
  • Старожил
  • *
  • Сообщений: 3185
    • Просмотр профиля
На все вопросы ответил enter'ом.
Надо Yes отвечать, а не Ентером.
Если не помогает- добавьте к параметрам ядра:
acpi_enforce_resources=laxи повторите поиск датчиков
Acer E5-571G; Intel Corei5; GPU: IntelHD 4400 + Nvidia 820M; SSD 250 Гб + HDD 500 Гб; RAM 12 Гб, UEFI без загрузчика.
Arch Linux; WM: Xmonad ;ядро: linux-zen

Оффлайн damix

  • Автор темы
  • Новичок
  • *
  • Сообщений: 27
    • Просмотр профиля
Ответил YES, результат тот же.

Если не помогает- добавьте к параметрам ядра:

acpi_enforce_resources=lax

и повторите поиск датчиков

Сделал так
$ cat /etc/default/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_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=2
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_enforce_resources=lax"
GRUB_CMDLINE_LINUX=""

# 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"
$ sudo update-grub
Перезагрузился.
Затем
$ sudo sensors-detect
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: Micro-Star International Co., Ltd. MS-7A34 [2.0]
# Board: Micro-Star International Co., Ltd. B350 PC MATE (MS-7A34)
# Kernel: 4.15.0-22-generic x86_64
# Processor: AMD Ryzen 3 2200G with Radeon Vega Graphics (23/17/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): YES
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 16h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 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): YES
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 unknown chip with ID 0xd352

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): YES
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): YES
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): YES
Found unknown SMBus adapter 1022:790b at 0000:00:14.0.
Sorry, no supported PCI bus adapters found.

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively): YES
Убито
Вывод sensors тот же.

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=33755908-51bd-4ef7-bbfe-4e34313e8022 ro quiet splash acpi_enforce_resources=lax vt.handoff=1

Пользователь добавил сообщение 06 Июнь 2018, 23:17:42:
Странно. Чем могла быть убита программа? Я такого сигнала не посылал.

$ sensors -v
sensors version 3.4.0 with libsensors version 3.4.0

При этом BIOS показывает в своем меню следующие значения:
CPU 31 | System 36 | MOS 38 | PCH 24
все в градусах Цельсия.
PCH - это, как я понял датчик температуры южного моста. А MOS - это что такое?
« Последнее редактирование: 06 Июнь 2018, 23:22:01 от damix »

Оффлайн damix

  • Автор темы
  • Новичок
  • *
  • Сообщений: 27
    • Просмотр профиля
Температурные датчики на Ryzen в принципе не работают из коробки.  Пришлось собрать из исходников и установить модуль ядра nct6775.
https://github.com/groeck/nct6775
git clone https://github.com/groeck/nct6775.git
cd nct6775/
make -j5
sudo make install
Пересобрал из исходников lm-sensors
cd ..
git clone https://github.com/groeck/lm-sensors.git
cd lm-sensors/
make -j5 all
sudo make install
sudo ldconfig
Подгружаем модуль ядра
sudo modprobe nct6775И теперь
$ sudo sensors-detect
# sensors-detect revision $Revision$
# System: Micro-Star International Co., Ltd. MS-7A34 [2.0]
# Board: Micro-Star International Co., Ltd. B350 PC MATE (MS-7A34)
# Kernel: 4.17.0-041700-generic x86_64
# Processor: AMD Ryzen 3 2200G with Radeon Vega Graphics (23/17/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):
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 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           Success!
    (driver `k10temp')
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 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'...               Yes
Found `Nuvoton NCT6795D Super IO Sensors'                   Success!
    (address 0xa20, driver `nct6775')

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):
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):

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-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
Do you want to scan it? (yes/NO/selectively):

Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1)
Do you want to scan it? (yes/NO/selectively):

Next adapter: SMBus PIIX4 adapter port 3 at 0b00 (i2c-2)
Do you want to scan it? (yes/NO/selectively):

Next adapter: SMBus PIIX4 adapter port 4 at 0b00 (i2c-3)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-4)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-5)
Do you want to scan it? (yes/NO/selectively):

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

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-7)
Do you want to scan it? (yes/NO/selectively):

Next adapter: AMDGPU DM i2c hw bus 3 (i2c-8)
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 `k10temp' (autoloaded):
  * Chip `AMD Family 17h thermal sensors' (confidence: 9)

Driver `nct6775':
  * ISA bus, address 0xa20
    Chip `Nuvoton NCT6795D Super IO Sensors' (confidence: 9)

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO):
To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----
# Chip drivers
modprobe nct6775
/usr/bin/sensors -s
#----cut here----

You really should try these commands right now to make sure everything
is working properly. Monitoring programs won't work until the needed
modules are loaded.

Unloading cpuid... OK

$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +30.8°C  (high = +70.0°C)

nct6795-isa-0a20
Adapter: ISA adapter
in0:                    +0.85 V  (min =  +0.00 V, max =  +1.74 V)
in1:                    +1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:                    +3.46 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:                    +3.38 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:                    +1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                    +0.15 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                    +0.74 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:                    +3.44 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:                    +3.36 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:                    +1.85 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                   +0.90 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                   +1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                   +0.92 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                   +0.60 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                   +1.53 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                   361 RPM  (min =    0 RPM)
fan2:                   929 RPM  (min =    0 RPM)
fan3:                     0 RPM  (min =    0 RPM)
fan4:                     0 RPM  (min =    0 RPM)
fan5:                     0 RPM  (min =    0 RPM)
fan6:                     0 RPM  (min =    0 RPM)
SYSTIN:                 +39.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = CPU diode
CPUTIN:                 +32.0°C  (high = +115.0°C, hyst = +90.0°C)  sensor = thermistor
AUXTIN0:                +40.0°C  (high = +115.0°C, hyst = +90.0°C)  sensor = thermistor
AUXTIN1:                +31.0°C    sensor = thermistor
AUXTIN2:                +25.0°C    sensor = thermistor
AUXTIN3:                 -2.0°C    sensor = thermistor
SMBUSMASTER 0:          +30.5°C 
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C 
PCH_CHIP_TEMP:           +0.0°C 
PCH_CPU_TEMP:            +0.0°C 
intrusion0:            ALARM
intrusion1:            ALARM
beep_enable:           disabled

Пользователь добавил сообщение 13 Июнь 2018, 13:54:52:
И теперь чтобы посмотреть температуру
sudo modprobe nct6775
sensors
« Последнее редактирование: 13 Июнь 2018, 13:54:52 от damix »

 

Страница сгенерирована за 0.063 секунд. Запросов: 24.