В насройке нет ни одного датчика.
Как исправить?
sshooter wrote:
> Как исправить?
В терминале, отroot, запустить команду sensors.
Вот что выдает:
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
sshooter wrote:
> Try sensors-detect to find out which these are.
И что не понятно?
Я не понимаю смысла этой фразы.
sshooter wrote:
> Я не понимаю смысла этой фразы.
sshooter, я не понимаю вашего увлечения openSUSE.
То, что написано ниже, требуетмодерации и, уничтожения после прочтения.
По-моему, вам уже предлагалось вернуться в Windows-систему.
запусти sensors-detect
Запустил, ничего он не обнаружил.
На все его вопросы ответом было - yes или no?
Отвечал yes
В биосе все штучки типа acpi включены?
Да, не все пользователи линукса достаточно хорошо знают английский язык. Поэтому, господа модераторы и господа линукс-гуру, будьте великодушны!
В Yast - Системные службы надо включить lm_sensors.
Похожая ситуация
выполняю sensors-detect, на все вопросы отвечаю yes
получаю следующее
# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
# Board: ASUSTeK Computer INC. P5GPL-X
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
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 W83627EHF/EF/EHG/EG 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-i801' for device 0000:00:1f.3: Intel 82801FB ICH6
Module i2c-dev loaded successfully.
Next adapter: NVIDIA i2c adapter 0 at 3:00.0 (i2c-0)
Do you want to scan it? (YES/no/selectively): y
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 3:00.0 (i2c-1)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter 2 at 3:00.0 (i2c-2)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter 5 at 3:00.0 (i2c-3)
Do you want to scan it? (YES/no/selectively): y
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'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Now follows a summary of the probes I have just done.
Just press ENTER to continue: y
Driver `w83627ehf':
* ISA bus, address 0x290
Chip `Winbond W83627EHF/EF/EHG/EG 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 # эта строчка мне не совсем ясна (у меня нет каталога prog/init)
and run 'systemctl enable lm_sensors.service'
for initialization at boot time.
# соответственно получаю -** lm_sensors.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig lm_sensors on**
Unloading i2c-dev... OK
Unloading cpuid... OK
попытка запуска lm_sensors в yast возвращает неизвестную ошибку
service lm_sensors status показывает:
lm_sensors.service - LSB: Load and configure hardware monitoring drivers
Loaded: loaded (/etc/init.d/lm_sensors)
Active: failed (Result: exit-code) since Thu, 28 Feb 2013 00:37:04 +0200; 10min ago
Process: 565 ExecStart=/etc/init.d/lm_sensors start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/lm_sensors.service
Feb 28 00:37:12 linux-home lm_sensors[565]: Starting up sensors: ..failed
выполнение **sensors **показывает
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
Вопрос:
Где взять **prog/init/lm_sensors.service, **чтобы скопировать в **/lib/systemd/system? **я подозреваю, что затык в этом..или нет?
Команды вида** /etc/init.d/lm_sensors status и service lm_sensors status**- это одно и то же, или же есть различия?
P.S Если загрузиться в винды и воспользоваться aida - показывает множество температурных датчиков, включая те, что на видеокарте.
Где взять prog/init/lm_sensors.service, чтобы скопировать в /lib/systemd/system?
В данном случае при запуске службы sensors происходит перенаправление (redirecting to systemctl). Никакой службы в директории* /lib/systemd/system* быть не должно, поскольку используется скрипт из* /etc/init.d. *В качестве доказательства работоспособности службы:
dhcppc0:/etc/init.d # ./lm_sensors start
redirecting to systemctl
Starting up sensors: done
dhcppc0:/etc/init.d # systemctl status lm_sensors.service
lm_sensors.service - LSB: Load and configure hardware monitoring drivers
Loaded: loaded (/etc/init.d/lm_sensors)
Active: active (exited) since Thu, 28 Feb 2013 07:32:42 +0300; 9min ago
Process: 5042 ExecStop=/etc/init.d/lm_sensors stop (code=exited, status=0/SUCCESS)
Process: 5093 ExecStart=/etc/init.d/lm_sensors start (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/lm_sensors.service
Feb 28 07:32:42 dhcppc0 lm_sensors[5093]: Starting up sensors: ..done
Проблема явно в чем-то другом.
Покажите:
cd /etc/init.d/lm_sensors
sh -x lm_sensors start
показываю:
cd /etc/init.d/lm_sensors
bash: cd: /etc/init.d/lm_sensors: Это не каталог
/etc/init.d # ./lm_sensors start
redirecting to systemctl
Starting up sensors: failed
sh -x lm_sensors start
+ CONFIG=/etc/sysconfig/lm_sensors
+ LOCK=/var/run/lm_sensors.lock
+ PSENSORS=/usr/bin/sensors
+ FANCONFIG=/etc/fancontrol
+ PFAN=/usr/sbin/fancontrol
+ . /etc/rc.status
++ test -z ''
++ /bin/mountpoint -q /sys/fs/cgroup/systemd
++ test 2977 -ne 1 -a 1 -eq 1
++ _rc_base=
++ case "$0" in
++ case "$1" in
++ echo 'redirecting to systemctl'
redirecting to systemctl
++ test -n '' -a -x /bin/systemctl
++ unset _rc_base
++ test -z /dev/tty7 -a -x /sbin/showconsole
++ LC_ALL=POSIX
++ export LC_ALL
++ trap rc_lc SIGWINCH
++ test -n 80 -a -n 24
++ export LINES COLUMNS
++ case ":$PATH:" in
++ test -t 1 -a xterm '!=' raw -a xterm '!=' dumb
+++ echo -en '\033'
++ esc=$'\E'
++ extd=''
++ warn=''
++ done=''
++ attn=''
+++ echo -en '\017'
++ norm=''
+++ echo -en '\015 '
++ stat=' '
++ rc_done=' done'
++ rc_running=' running'
++ rc_failed=' failed'
++ rc_missed=' missing'
++ rc_skipped=' skipped'
++ rc_dead=' dead'
++ rc_unused=' unused'
++ rc_unknown=' failed''
++ rc_reset=''p='
++ rc_save=''
++ rc_restor'='
++ _rc_service=lm_sensors
++ _rc_status=0
++ _rc_status_all=0
++ _rc_todo=start
++ test start = status
++ test -n start
++ cmdline=
+ rc_reset
+ _rc_status=0
+ _rc_status_all=0
+ rc_check
+ _rc_status_ret=0
+ test 0 -eq 0
+ test 0 -eq 0
+ return 0
+ return 0
+ case "$1" in
+ start
+ echo -n 'Starting up sensors'
Starting up sensors+ unset
+ test -r /etc/sysconfig/lm_sensors
+ . /etc/sysconfig/lm_sensors
++ HWMON_MODULES=w83627ehf
++ MODULE_0=w83627ehf
+ for i in '${!MODULE_*}'
+ eval 'module=$MODULE_0'
++ module=w83627ehf
+ /sbin/modprobe w83627ehf
+ rc_status
+ rc_check
+ _rc_status_ret=1
+ test 1 -eq 0
+ _rc_status=1
+ test 1 -eq 0
+ _rc_status_all=1
+ return 1
+ test 1 -gt 7
+ _rc_status_ret=1
+ case "$_rc_todo" in
+ local i
+ return 1
+ rc_status
+ rc_check
+ _rc_status_ret=1
+ test 1 -eq 0
+ _rc_status=1
+ test 1 -eq 0
+ _rc_status_all=1
+ return 1
+ test 1 -gt 7
+ _rc_status_ret=1
+ case "$_rc_todo" in
+ local i
+ return 1
+ /usr/bin/sensors -s
+ rc_status
+ rc_check
+ _rc_status_ret=1
+ test 1 -eq 0
+ _rc_status=1
+ test 1 -eq 0
+ _rc_status_all=1
+ return 1
+ test 1 -gt 7
+ _rc_status_ret=1
+ case "$_rc_todo" in
+ local i
+ return 1
+ test -s /etc/fancontrol -a -x /usr/sbin/fancontrol
+ echo -n ': '
: + rc_status -v
+ rc_check
+ _rc_status_ret=0
+ test 0 -eq 0
+ test 1 -eq 0
+ _rc_status_all=1
+ return 0
+ test 1 -gt 7
+ _rc_status_ret=1
+ case "$_rc_todo" in
+ local i
+ for i in '"$@"'
+ case "$i" in
+ local vrt=
+ local out=1
+ local opt=en
+ test -n ''
+ opt=e
+ case "$_rc_status" in
+ vrt=' failed'
+ out=2
+ echo -e '' failed
failed
+ _rc_status=0
+ return 1
+ rc_exit
+ exit 1
Никакой службы в директории* /lib/systemd/system быть не должно*
а что означает вот это:
Copy prog/init/lm_sensors.service to /lib/systemd/system and run 'systemctl enable lm_sensors.service' for initialization at boot time.
?
У вас не загружается модуль:
...
+ /sbin/modprobe w83627ehf
+ rc_status
+ rc_check
+ _rc_status_ret=1
+ test 1 -eq 0
+ _rc_status=1
+ test 1 -eq 0
+ _rc_status_all=1
+ return 1
...
Попробуйте подгрузить модуль вручную.