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

[hypersash]

Всем доброго времени суток! Имею Ubuntu сервер 14.04.3 на Пентиум 4 и матери MSI 845E MAX (MS-6566Ever2).

Крайне необходимо мониторить температуру, так как сервер стоит дома и напряжения на кулер снижены, дабы было меньше шума.
Установил lm-sensors, прошел конфигурацию, ребут и sensors - No sensors found!
Как только не мучился, все без толку 

(Нажмите, чтобы показать/скрыть)

root@Server:/home/alex# sensors-detect
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# System: Micro-Star Inc. MS-6566E [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...                                   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...                             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'...               Yes
Found `Winbond W83627HF/F/HG/G Super IO Sensors'            Success!
    (address 0x290, driver `w83627hf')
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-i801' for device 0000:00:1f.3: Intel 82801DB ICH4
Module i2c-i801 loaded successfully.

Next adapter: nouveau-0000:01:00.0-0 (i2c-0)
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/ADT7420'...             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

Next adapter: nouveau-0000:01:00.0-1 (i2c-1)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: nouveau-0000:01:00.0-2 (i2c-2)
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 `w83627hf':
  * ISA bus, address 0x290
    Chip `Winbond W83627HF/F/HG/G Super IO Sensors' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
w83627hf
#----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 'service kmod start'
to load them.

Unloading i2c-i801... OK
Unloading cpuid... OK

Код: [Выделить]

root@Server:/home/alex# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

Содержание /etc/modules

Код: [Выделить]

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

lp

# Generated by sensors-detect on Tue Dec 02 23:00:40 2015
# Chip drivers
w83627hf

[Peter_I]

А sensors-detect как root запускали?

[hypersash]

А sensors-detect как root запускали?

Да, конечно, там под спойлером видно как он отработал...

(Нажмите, чтобы показать/скрыть)

root@Server:/home/alex# sensors-detect
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# System: Micro-Star Inc. MS-6566E [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...                                   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...                             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'...               Yes
Found `Winbond W83627HF/F/HG/G Super IO Sensors'            Success!
    (address 0x290, driver `w83627hf')
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-i801' for device 0000:00:1f.3: Intel 82801DB ICH4
Module i2c-i801 loaded successfully.

Next adapter: nouveau-0000:01:00.0-0 (i2c-0)
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/ADT7420'...             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

Next adapter: nouveau-0000:01:00.0-1 (i2c-1)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: nouveau-0000:01:00.0-2 (i2c-2)
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 `w83627hf':
  * ISA bus, address 0x290
    Chip `Winbond W83627HF/F/HG/G Super IO Sensors' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
w83627hf
#----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 'service kmod start'
to load them.

Unloading i2c-i801... OK
Unloading cpuid... OK

Пользователь решил продолжить мысль 07 Декабря 2015, 01:48:28:Все почти получилось!   

Нужно было добавить

GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax"

в файл /etc/default/grub

затем выполнить sudo update-grub и ребутнуться.

Теперь sensors все показывает, но перед этим надо ввести modprobe w83627hf, иначе не работает!

Итоговый вопрос - куда добавить этот modprobe что-бы он загружался при запуске системы?

[| toZen |]

/etc/modules
Только имя модуля.

[hypersash]

Там он уже прописан 

[| toZen |]

Код: [Выделить]

cat /etc/modules??

[hypersash]

Код: [Выделить]

cat /etc/modules??

Код: [Выделить]

root@Server:~# cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

lp

# Generated by sensors-detect on Tue Dec 02 23:00:40 2015
# Chip drivers
w83627hf

[| toZen |]

hypersash, эммм..., может в блэклист по ошибке прописали?

[hypersash]

hypersash, эммм..., может в блэклист по ошибке прописали?

Прописалось автоматом при sensors-detect, но все-же скажите где блэклист лежит, гляну.

Думаеться мне что можно обойтись и костылем в виде скрипта, который будет делать при старте

Код: [Выделить]

sudo modprobe w83627hf, но так далеко я еще не заходил в освоении Linuxа =)

[| toZen |]

hypersash, не, мне тоже интересна причина такого поведения, давайте ещё покрутим без всяких костылей.

Код: [Выделить]

cat /etc/modprobe.d/blacklist.confКстати, а что это за модуль?

[hypersash]

hypersash, не, мне тоже интересна причина такого поведения, давайте ещё покрутим без всяких костылей.

Код: [Выделить]

cat /etc/modprobe.d/blacklist.conf

Давайте! 

Код: [Выделить]

root@Server:~# cat /etc/modprobe.d/blacklist.conf
# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.

# evbug is a debug tool that should be loaded explicitly
blacklist evbug

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

# replaced by e100
blacklist eepro100

# replaced by tulip
blacklist de4x5

# causes no end of confusion by creating unexpected network interfaces
blacklist eth1394

# snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support much
# hardware on its own (Ubuntu bug #2011, #6810)
blacklist snd_intel8x0m

# Conflicts with dvb driver (which is better for handling this device)
blacklist snd_aw2

# causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306)
blacklist i2c_i801

# replaced by p54pci
blacklist prism54

# replaced by b43 and ssb.
blacklist bcm43xx

# most apps now use garmin usb driver directly (Ubuntu: #114565)
blacklist garmin_gps

# replaced by asus-laptop (Ubuntu: #184721)
blacklist asus_acpi

# low-quality, just noise when being used for sound playback, causes
# hangs at desktop session start (Ubuntu: #246969)
blacklist snd_pcsp

# ugly and loud noise, getting on everyone's nerves; this should be done by a
# nice pulseaudio bing (Ubuntu: #77010)
blacklist pcspkr

# EDAC driver for amd76x clashes with the agp driver preventing the aperture
# from being initialised (Ubuntu: #297750). Blacklist so that the driver
# continues to build and is installable for the few cases where its
# really needed.
blacklist amd76x_edac


Кстати, а что это за модуль?

Видимо что-то типо Winbond'овского драйвера для датчиков, в самом первом посте под спойлером есть вывод sensors-detect, может он вам прояснит ситуацию =)

[| toZen |]

Давайте тогда обновим initial disk:

Код: [Выделить]

sudo update-initramfs -u

Код: [Выделить]

sudo rebootЕсли не сработает и так, то можно подсунуть строку <modprobe w83627hf> в /etc/rc.local прямо перед <exit 0> и опять ребутнуться, но это не по фэн-шую.

[hypersash]

Давайте тогда обновим initial disk:

Код: [Выделить]

sudo update-initramfs -u

Код: [Выделить]

sudo reboot

Выполнил, не помогло 

Если не сработает и так, то можно подсунуть строку <modprobe w83627hf> в /etc/rc.local прямо перед <exit 0> и опять ребутнуться, но это не по фэн-шую.

А вот так заработало, супер, спасибо большое за ваше время!  И ничего что костыль, зато сервер наконец-то в кладовку поедет 

[| toZen |]

hypersash, ладно, работает и хорошо. На здоровье. Удачи.

### UPD ###
Поставьте пометку [Решено] - правый нижний угол.

### UPD FOR UPD ###
Подумалось на досуге. Проверьте/покажите содержимое /usr/lib/modules.d/
Возможно, что там прописан блеклистинг. Ну, это в том случае, если есть ещё желание понадожимать проблему по правилам.
И кстати, у Вас udev или systemd?

[fisher74]

Банальнейший вопрос по теме: а в /etc/modules после w83627hf перевод строки есть?
и да

Код: [Выделить]

grep 8327 /etc/modprobe.d/*