sensors не видит датчики

genghaev · #1

Всем привет.
Сменил себе материнку на ASUS TUF B360-PLUS GAMING + i3 8100 (благодаря nethello, спасибо!)

System: Host: genghaev-System-Product-Name Kernel: 5.0.0-29-generic x86_64 bits: 64 gcc: 7.4.0
Desktop: KDE Plasma 5.16.5 (Qt 5.12.3) Distro: KDE neon User Edition 5.16
Machine: Device: desktop Mobo: ASUSTeK model: TUF B360-PLUS GAMING v: Rev 1.xx serial: N/A
UEFI: American Megatrends v: 1502 date: 06/26/2019
Battery hidpp__0: charge: N/A condition: NA/NA Wh model: Logitech Wireless Mouse status: Discharging
hidpp__1: charge: N/A condition: NA/NA Wh model: Logitech K520 status: Discharging
CPU: Quad core Intel Core i3-8100 (-MCP-) arch: Skylake rev.11 cache: 6144 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28800
clock speeds: max: 3600 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz 4: 800 MHz
Graphics: Card: NVIDIA GK106 [GeForce GTX 650 Ti] bus-ID: 01:00.0
Display Server: x11 (X.Org 1.19.6 ) drivers: nvidia (unloaded: modesetting,fbdev,vesa,nouveau)
Resolution: 1920x1080@60.00hz
OpenGL: renderer: GeForce GTX 650 Ti/PCIe/SSE2 version: 4.6.0 NVIDIA 430.26 Direct Render: Yes
Audio: Card-1 NVIDIA GK106 HDMI Audio Controller driver: snd_hda_intel bus-ID: 01:00.1
Card-2 Intel Cannon Lake PCH cAVS driver: snd_hda_intel bus-ID: 00:1f.3
Card-3 KYE Systems (Mouse Systems) Genius iSlim 2000AF V2 driver: USB Audio usb-ID: 001-002
Sound: Advanced Linux Sound Architecture v: k5.0.0-29-generic
Network: Card: Intel Ethernet Connection (7) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 7385.5GB (76.2% used)
ID-1: /dev/nvme0n1 model: INTEL_SSDPEKKW256G8 size: 256.1GB temp: 36C
ID-2: /dev/sda model: WDC_WD20EARX size: 2000.4GB temp: 35C
ID-3: /dev/sdb model: WDC_WD20EZRX size: 2000.4GB temp: 36C
ID-4: /dev/sdc model: WDC_WD30EZRX size: 3000.6GB temp: 36C
ID-5: /dev/sdd model: INTEL_SSDSC2KW12 size: 128.0GB temp: 29C
Partition: ID-1: / size: 115G used: 32G (30%) fs: ext4 dev: /dev/nvme0n1p5
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 35.0C mobo: N/A gpu: 0.0:37C
Fan Speeds (in rpm): cpu: 0
Info: Processes: 221 Uptime: 1:34 Memory: 2465.3/15957.2MB Init: systemd runlevel: 5 Gcc sys: 7.4.0
Client: Shell (fish) inxi: 2.3.56

Neon KDE x64, lm-sensors не видит датчиков, sudo sensors-detect делал, вот выхдоп sensors:

asus-isa-0000
Adapter: ISA adapter
cpu_fan: 0 RPM

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

хотелось бы узнать как на новой матери со старом sensors увидеть вентиляторы?

#2

На моей материнке тоже вентиляторы не отображаются. Полагаю это как-то связано с тем что политика работы с кулерами настраивается в самом биосе мамки...

genghaev · #3

zuzabrik писал(а): ↑
04 окт 2019, 17:56
Полагаю это как-то связано с тем что политика работы с кулерами настраивается в самом биосе мамки...

я весь биос перешерстил, сдается мне что надо вносить изменения в лм сенсорс (или еще куда то), так же как и для новых ссд вносили изменения в etc/hddtemp

#4

genghaev писал(а): ↑
04 окт 2019, 17:42
lm-sensors не видит датчиков, sudo sensors-detect делал,

Такая же проблема на ASUS B360 G-GAMING. Сильно не копался (настроил обороты в биосе и забыл), но, судя по всему, на наших материнках используется чип Nuvoton NCT6796D, для которого нужно:
1. Ядро 4.17+ (с этим проблем в минте нет)
2. lm-sensors 3.5. В Минте используется старая версия 3.4 от 2015 года. Я уже пробовал подсунуть пакеты от новой убунты - не ставятся из-за конфликта версий, т.к. цепляются зависимостями за общие системные либы. В каком-либо ppa новой версии тоже нет. (теоретически, можно собрать из исходников, но...

)
Во ссылка на багрепорт: https://github.com/lm-sensors/lm-sensors/issues/111

Покажите вывод команды sudo sensors-detect, весь не нужен, просто первые две секции (как тут):

tt@tt-one:~$ sudo sensors-detect
[sudo] пароль для tt:
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# Board: ASUSTeK COMPUTER INC. ROG STRIX B360-G GAMING
# Kernel: 4.15.0-65-generic x86_64
# Processor: Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz (6/158/11)

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... Success!
(driver `coretemp')
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'... Yes
Found unknown chip with ID 0xd423
(logical device B has address 0x290, could be sensors)
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 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

genghaev · #5

Ара Магеддон писал(а): ↑
04 окт 2019, 18:59
Покажите вывод команды sudo sensors-detect,

# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# Board: ASUSTeK COMPUTER INC. TUF B360-PLUS GAMING
# Kernel: 5.0.0-29-generic x86_64
# Processor: Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz (6/158/11)

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... Success!
(driver `coretemp')
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'... Yes
Found unknown chip with ID 0xd423
(logical device B has address 0x290, could be sensors)
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 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 8086:a323 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.

#6

genghaev писал(а): ↑
04 окт 2019, 19:02
Found unknown chip with ID 0xd423
(logical device B has address 0x290, could be sensors)

Да, такая же штука. Я давно собирался убунту 19.04 поставить на тестовую ссдшку, поиграться. Там уже версия 3.5 - тогда отпишусь, заработало или нет

genghaev · #7

Ара Магеддон писал(а): ↑
04 окт 2019, 19:05
заработало или нет

Завтра попытаюсь все таки вычислить в чем проблема, на свежую голову так сказать )

#8

Народ, у меня близкая к вашим материнка ASUS PRIME B360-PLUS, и стоит manjaro где пакет sensors сейчас 3.5. Так оно тоже обороты вентияторов не видит, по крайней мере с простой автонастройкой через sensors-detect. Это так, для информации.

#9

В общем, вот готовое решение:

1. Поставить ядро 5.0 через Менеджер обновлений > Вид > Ядра Linux

2. sudo nano /etc/default/grub, привести строчку GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" к виду GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_enforce_resources=lax"

3. sudo update-grub

4. sudo nano /etc/modules, добавить строки:

coretemp
nct6775
blacklist thermal
blacklist asus_wmi

Дубликаты можно удалить. Две первые строчки добавляют загрузку нужных модулей, две вторые - запрещают загрузку модулей, перехватывающих информацию от чипа.

5. Перезагрузиться

Вывод команды sensors в моём случае:

Нашел тут: https://bbs.archlinux.org/viewtopic.php?id=223967

genghaev · #10

Ара Магеддон писал(а): ↑
04 окт 2019, 23:29
В общем, вот готовое решение:

Спасибо! Все заработало.

#11

genghaev писал(а): ↑
05 окт 2019, 12:33
Спасибо! Все заработало.

Всегда пожалуйста!

Stiven · #12

Дабы не плодить однотипных тем.
Ситуация та-же, только не даёт температуру CPU, видео и hdd пожалуйста. Железяка старая, собрана под несложные задачи, но с загрузкой процессора, нужно контролировать температуру - помещение пыльное. lm-sensors, psensor и hddtemp установлены, система обновлена, sensors-detect выполнен.

System:
Host: stiven-btc Kernel: 5.0.0-32-generic x86_64 bits: 64
Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia
Machine:
Type: Desktop System: MSI product: MS-7255 v: 2.0 serial: <root required>
Mobo: Micro-Star model: MS-7255 V2.0 v: 2.0 serial: <root required>
BIOS: American Megatrends v: 5.4 date: 07/12/2007
CPU:
Topology: Dual Core model: Intel Pentium D bits: 64 type: MCP
L2 cache: 2048 KiB
Speed: 3200 MHz min/max: N/A Core speeds (MHz): 1: 3200 2: 3200
Graphics:
Device-1: NVIDIA G71 [GeForce 7900 GS] driver: nouveau v: kernel
Display: x11 server: X.Org 1.20.5 driver: nouveau
unloaded: fbdev,modesetting,vesa resolution: 1280x1024~60Hz
OpenGL: renderer: NV49 v: 2.1 Mesa 19.0.8
Audio:
Device-1: VIA VT8237A/VT8251 HDA driver: snd_hda_intel
Sound Server: ALSA v: k5.0.0-32-generic
Network:
Device-1: VIA VT6102/VT6103 [Rhine-II] driver: via-rhine
IF: enp0s18 state: unknown speed: 100 Mbps duplex: full
mac: 00:19:db:d6:32:71
Drives:
Local Storage: total: 614.81 GiB used: 437.77 GiB (71.2%)
ID-1: /dev/sda vendor: Seagate model: ST3160815AS size: 149.05 GiB
ID-2: /dev/sdb vendor: Seagate model: ST9500423AS size: 465.76 GiB
Partition:
ID-1: / size: 136.32 GiB used: 7.24 GiB (5.3%) fs: ext4 dev: /dev/sda3
ID-2: /boot size: 1.85 GiB used: 87.5 MiB (4.6%) fs: ext4 dev: /dev/sda1
ID-3: /home size: 457.45 GiB used: 430.28 GiB (94.1%) fs: ext4
dev: /dev/sdb1
ID-4: swap-1 size: 7.63 GiB used: 171.2 MiB (2.2%) fs: swap dev: /dev/sda2
Sensors:
Message: No sensors data was found. Is sensors configured?
Info:
Processes: 165 Uptime: 21h 28m Memory: 1.94 GiB used: 527.9 MiB (26.6%)
Shell: bash inxi: 3.0.32

Вот фсё что согласен отображать:

Заранее спасибо)))

#13

Stiven, а из под винды температуру процессора видел?

Stiven · #14

rogoznik писал(а): ↑
06 фев 2020, 17:11
Stiven, а из под винды температуру процессора видел?

А в душЕ не знаю))) Не было там форточек. Мать долго валялась без дела, решил её напрячь, а тут и всяких железок на системник собралось. Точно знаю что в bios температуры процессора отображаются, настраивал там.

#15

Stiven, попробуй какой-нибудь liveCD виндовый запустить, а в нем аиду или еще какую приблуду для наблюдения за температурой - будет показывать температуру проца или нет

Stiven · #16

rogoznik писал(а): ↑
06 фев 2020, 17:22
Stiven, попробуй какой-нибудь liveCD виндовый запустить, а в нем аиду или еще какую приблуду для наблюдения за температурой - будет показывать температуру проца или нет

Ок, попробую cpu-z. Но часика через 2-3, сейчас задача запущена, 20 часов работы железки терять не хочется.

symon2014 · #17

Stiven, sudo sensors-detect . Enter - ответ на все вопросы.

Stiven · #18

symon2014 писал(а): ↑
06 фев 2020, 17:34
Stiven, sudo sensors-detect . Enter - ответ на все вопросы.

Возможно. Но есть нюанс), я уже понимаю что модулей lm-sensors не хватает. Сейчас буду пробовать выкосить lm-sensors и обратно установить.

stiven@stiven-btc:~$ sudo sensors-detect
[sudo] пароль для stiven:
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: MSI MS-7255 [2.0]
# Board: Micro-Star MS-7255 V2.0
# Kernel: 5.0.0-32-generic x86_64
# Processor: Intel(R) Pentium(R) D CPU 3.20GHz (15/6/5)

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... 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): 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'... Yes
Found `Winbond W83627DHG Super IO Sensors' Success!
(address 0x290, driver `w83627ehf')
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 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-viapro' for device 0000:00:11.0: VIA Technologies VT8237A South Bridge

Next adapter: SMBus Via Pro adapter at 0400 (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x2f
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 `TI / National Semiconductor ADC128D818'... No
Probing for `Analog Devices ADT7470'... No
Probing for `Winbond W83781D'... No
Probing for `Winbond W83782D'... No
Probing for `Winbond W83791D'... No
Probing for `Winbond W83792D'... No
Probing for `Winbond W83793R/G'... No
Probing for `Nuvoton W83795G/ADG'... No
Probing for `Nuvoton NCT7802Y'... 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 `Winbond W83L786NR/NG/R/G'... No
Probing for `Analog Devices ADM9240'... No
Probing for `Dallas Semiconductor DS1780'... No
Probing for `National Semiconductor LM81'... No
Probing for `Maxim MAX6639'... No
Probing for `Analog Devices ADM1029'... No
Probing for `ITE IT8712F'... No
Probing for `SMSC EMC2104'... No
Probing for `Fintek custom power control IC'... No
Probing for `Winbond W83791SD'... 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: nvkm-0000:02:00.0-bus-0000 (i2c-1)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: nvkm-0000:02:00.0-bus-0001 (i2c-2)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: nvkm-0000:02:00.0-bus-0002 (i2c-3)
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 `w83627ehf':
* ISA bus, address 0x290
Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
w83627ehf
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)y
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/kmod start'
to load them.

Unloading cpuid... OK

Хотя на запрос /etc/init.d/kmod start всё ок проходит

stiven@stiven-btc:~$ /etc/init.d/kmod start
[ ok ] Starting kmod (via systemctl): kmod.service.

Так что я в сомнениях каких-то.

Stiven · #19

symon2014 писал(а): ↑
06 фев 2020, 17:34
Stiven, sudo sensors-detect . Enter - ответ на все вопросы.

Согласен, решило но далеко не сразу разобрался, опыта очень мало с *nix системами, да и периодические они.
33 ха, решено. И как ни странно, ответ был в отсутствующем драйвере w83627ehf, о чем, собственно, писал sensors-detect. Информацию подробную про него подчерпнул тут. А там столько всего расписано, что аж слюнки потекли, и не зря, выглядит теперь все очень красиво

stiven@stiven-btc:~$ sensors
nouveau-pci-0200
Adapter: PCI adapter
GPU core: +1.20 V (min = +1.20 V, max = +1.20 V)
temp1: +49.0°C (high = +95.0°C, hyst = +3.0°C)
(crit = +130.0°C, hyst = +10.0°C)
(emerg = +135.0°C, hyst = +5.0°C)

w83627ehf-isa-0290
Adapter: ISA adapter
Vcore: +1.20 V (min = +0.00 V, max = +1.74 V)
in1: +1.59 V (min = +1.87 V, max = +0.00 V) ALARM
AVCC: +3.31 V (min = +2.85 V, max = +1.36 V) ALARM
+3.3V: +3.31 V (min = +1.23 V, max = +3.95 V)
in4: +1.83 V (min = +0.26 V, max = +1.62 V) ALARM
in5: +0.12 V (min = +0.01 V, max = +1.81 V)
in6: +0.12 V (min = +1.34 V, max = +0.66 V) ALARM
3VSB: +3.31 V (min = +0.10 V, max = +0.88 V) ALARM
Vbat: +3.20 V (min = +0.99 V, max = +2.94 V) ALARM
in9: +0.10 V (min = +1.39 V, max = +1.06 V) ALARM
fan1: 0 RPM (min = 888 RPM, div = 16) ALARM
fan2: 2250 RPM (min = 831 RPM, div = 8)
fan3: 0 RPM (min = 888 RPM, div = 16) ALARM
fan4: 0 RPM (min = 760 RPM, div = 16) ALARM
fan5: 0 RPM (min = 811 RPM, div = 16) ALARM
temp1: +34.0°C (high = +14.0°C, hyst = +111.0°C) sensor = thermistor
temp2: +40.5°C (high = -111.5°C, hyst = -112.0°C) ALARM sensor = CPU diode
temp3: +48.0°C (high = -111.5°C, hyst = -112.0°C) ALARM sensor = thermistor
cpu0_vid: +0.000 V
intrusion0: ALARM

Хотя, видимо, или данные не верны или надо как-то калибровать датчики, ПО, может ещё чего не хватает, но мой английский не столь хорош(((. Не видит второй кулер, с напругами тоже непонятно, по замерам всё норм.
Устанавливать просто sudo modprobe w83627ehf force_id=0x8860

symon2014 · #20

Stiven, ну раз драйвер датчика появился , посмотри на psensor , это гуилка для датчиков.

Кто сейчас на конференции