1. Sensors; 2. клавиатура в VirtualBox

samson4747	# 9 лет, 3 месяца назад
Темы: 33 Сообщения: 534 Участник с: 23 февраля 2012	1. Решил поставить GNOME Extensions sensors. Установил sensors: $ sudo pacman -Ss sensors extra/lm_sensors 3.3.3-3 [установлен] Collection of user space tools for general SMBus access and hardware monitoring extra/xfce4-sensors-plugin 1.2.5-1 (xfce4-goodies) A lm_sensors plugin for the Xfce panel community/i2c-tools 3.1.0-3 Heterogeneous set of I2C tools for Linux that used to be part of lm-sensors community/python2-sensors 0.0.2-1 Python bindings to libsensors community/sensors-applet 3.0.0-3 Applet for GNOME Panel to display readings from hardware sensors, including CPU temperature, fan speeds and voltage readings community/xsensors 0.70-3 X11 interface to lm_sensors $ Хотел запустить его сервис lm_sensors.service, но безуспешно: $ sudo systemctl start lm_sensors.service Job for lm_sensors.service failed. See 'systemctl status lm_sensors.service' and 'journalctl -xn' for details. $ systemctl status lm_sensors.service lm_sensors.service - Initialize hardware monitoring sensors Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled) Active: failed (Result: exit-code) since Вс 2013-05-19 00:11:40 MSK; 42s ago Process: 5386 ExecStart=/usr/bin/sensors -s (code=exited, status=1/FAILURE) Process: 5382 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=1/FAILURE) $ $ sudo sensors-detect # sensors-detect revision 6085 (2012-10-30 18:18:45 +0100) # Board: ASUSTeK Computer INC. P5GD1 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 # DMI data unavailable, please consider installing dmidecode 2.7 # or later for better results. 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 4:00.0 (i2c-0) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 1 at 4:00.0 (i2c-1) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 2 at 4:00.0 (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 `w83627ehf': * ISA bus, address 0x290 Chip `Winbond W83627EHF/EF/EHG/EG Super IO Sensors' (confidence: 9) Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): Job for lm_sensors.service failed. See 'systemctl status lm_sensors.service' and 'journalctl -xn' for details. Unloading i2c-dev... OK Unloading cpuid... OK $ journalctl -xn Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. Error was encountered while opening journal files: Нет доступных данных -- Logs begin at Сб 2012-10-13 18:21:40 MSK, end at Чт 2013-05-16 14:22:17 MSK. май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Cu май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Go май 16 13:28:14 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Tr май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Cu май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Go май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Cu май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Go май 16 14:22:16 myhost gnome-session[420]: WARNING: Application 'gnome-shell.des май 16 14:22:17 myhost /etc/gdm/Xsession[420]: gnome-session[420]: WARNING: Appl май 16 14:22:17 myhost /etc/gdm/Xsession[420]: Message: applet now removed fr lines 1-11/11 (END)...skipping... -- Logs begin at Сб 2012-10-13 18:21:40 MSK, end at Чт 2013-05-16 14:22:17 MSK. -- май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: CurrentTime used to choose focus window; focus window may not май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Got a request to focus the no_focus_window with a timestamp of май 16 13:28:14 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Treating resize request of legacy application 0x1c002a2 (Windo май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: CurrentTime used to choose focus window; focus window may not май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Got a request to focus 0x200007f (Аудио) with a timestamp of 0 май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: CurrentTime used to choose focus window; focus window may not май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Got a request to focus the no_focus_window with a timestamp of май 16 14:22:16 myhost gnome-session[420]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 май 16 14:22:17 myhost /etc/gdm/Xsession[420]: gnome-session[420]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 май 16 14:22:17 myhost /etc/gdm/Xsession[420]: Message: applet now removed from the notification area ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-11/11 (END) Вот что выдаёт при вызове: $ sudo sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. $ 2. В VirtualBox на ВиндеХП при смене раскладки, клавиатура шалит: щёлкая на клавиши они исполняют другие функции, например некоторые буквы вызывают F1-F12, Ctrl+C делает выделение всего и так далее. Приходится выходить обратно, что-то печатать на основной системе и возвращаться обратно, куда копать для решения этой проблемы? "If you try to hide the complexity of the system, you'll end up with a more complex system". Layers of abstraction that serve to hide internals are never a good thing. Instead, the internals should be designed in a way such that they NEED no hiding. —Aaron Griffin

# 9 лет, 3 месяца назад

Сообщения: 534

Участник с: 23 февраля 2012

1. Решил поставить GNOME Extensions sensors. Установил sensors:

$ sudo pacman -Ss  sensors
extra/lm_sensors 3.3.3-3 [установлен]
    Collection of user space tools for general SMBus access and hardware monitoring
extra/xfce4-sensors-plugin 1.2.5-1 (xfce4-goodies)
    A lm_sensors plugin for the Xfce panel
community/i2c-tools 3.1.0-3
    Heterogeneous set of I2C tools for Linux that used to be part of lm-sensors
community/python2-sensors 0.0.2-1
    Python bindings to libsensors
community/sensors-applet 3.0.0-3
    Applet for GNOME Panel to display readings from hardware sensors, including CPU temperature, fan speeds and voltage readings
community/xsensors 0.70-3
    X11 interface to lm_sensors
$

Хотел запустить его сервис lm_sensors.service, но безуспешно:

$ sudo systemctl start lm_sensors.service
Job for lm_sensors.service failed. See 'systemctl status lm_sensors.service' and 'journalctl -xn' for details.

$ systemctl status lm_sensors.service
lm_sensors.service - Initialize hardware monitoring sensors
   Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled)
   Active: failed (Result: exit-code) since Вс 2013-05-19 00:11:40 MSK; 42s ago
  Process: 5386 ExecStart=/usr/bin/sensors -s (code=exited, status=1/FAILURE)
  Process: 5382 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=1/FAILURE)
$

$ sudo sensors-detect
# sensors-detect revision 6085 (2012-10-30 18:18:45 +0100)
# Board: ASUSTeK Computer INC. P5GD1
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
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
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 4:00.0 (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA i2c adapter 1 at 4:00.0 (i2c-1)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA i2c adapter 2 at 4:00.0 (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 `w83627ehf':
* ISA bus, address 0x290
Chip `Winbond W83627EHF/EF/EHG/EG Super IO Sensors' (confidence: 9)
Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no):
Job for lm_sensors.service failed. See 'systemctl status lm_sensors.service' and 'journalctl -xn' for details.
Unloading i2c-dev... OK
Unloading cpuid... OK

$ journalctl -xn
Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
Error was encountered while opening journal files: Нет доступных данных
-- Logs begin at Сб 2012-10-13 18:21:40 MSK, end at Чт 2013-05-16 14:22:17 MSK.
май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Cu
май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Go
май 16 13:28:14 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Tr
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Cu
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Go
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Cu
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Go
май 16 14:22:16 myhost gnome-session[420]: WARNING: Application 'gnome-shell.des
май 16 14:22:17 myhost /etc/gdm/Xsession[420]: gnome-session[420]: WARNING: Appl
май 16 14:22:17 myhost /etc/gdm/Xsession[420]: ** Message: applet now removed fr
lines 1-11/11 (END)...skipping...
-- Logs begin at Сб 2012-10-13 18:21:40 MSK, end at Чт 2013-05-16 14:22:17 MSK. --
май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: CurrentTime used to choose focus window; focus window may not
май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Got a request to focus the no_focus_window with a timestamp of
май 16 13:28:14 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Treating resize request of legacy application 0x1c002a2 (Windo
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: CurrentTime used to choose focus window; focus window may not
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Got a request to focus 0x200007f (Аудио) with a timestamp of 0
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: CurrentTime used to choose focus window; focus window may not
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Got a request to focus the no_focus_window with a timestamp of
май 16 14:22:16 myhost gnome-session[420]: WARNING: Application 'gnome-shell.desktop' killed by signal 11
май 16 14:22:17 myhost /etc/gdm/Xsession[420]: gnome-session[420]: WARNING: Application 'gnome-shell.desktop' killed by signal 11
май 16 14:22:17 myhost /etc/gdm/Xsession[420]: ** Message: applet now removed from the notification area
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-11/11 (END)

Вот что выдаёт при вызове:

$ sudo sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
$

2. В VirtualBox на ВиндеХП при смене раскладки, клавиатура шалит: щёлкая на клавиши они исполняют другие функции, например некоторые буквы вызывают F1-F12, Ctrl+C делает выделение всего и так далее. Приходится выходить обратно, что-то печатать на основной системе и возвращаться обратно, куда копать для решения этой проблемы?

"If you try to hide the complexity of the system, you'll end up with a more complex system". Layers of abstraction that serve to hide internals are never a good thing. Instead, the internals should be designed in a way such that they NEED no hiding. —Aaron Griffin

samson4747	# 9 лет, 3 месяца назад
Темы: 33 Сообщения: 534 Участник с: 23 февраля 2012	$ sudo systemctl status lm_sensors.service lm_sensors.service - Initialize hardware monitoring sensors Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled) Active: failed (Result: exit-code) since Вс 2013-05-19 00:30:28 MSK; 1min 32s ago Process: 247 ExecStart=/usr/bin/sensors -s (code=exited, status=1/FAILURE) Process: 235 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=1/FAILURE) май 19 00:30:28 myhost systemd[1]: lm_sensors.service: main process exited, code=exited, status=1/FAILURE май 19 00:30:28 myhost systemd[1]: Failed to start Initialize hardware monitoring sensors. май 19 00:30:28 myhost systemd[1]: Unit lm_sensors.service entered failed state. $ "If you try to hide the complexity of the system, you'll end up with a more complex system". Layers of abstraction that serve to hide internals are never a good thing. Instead, the internals should be designed in a way such that they NEED no hiding. —Aaron Griffin

samson4747

# 9 лет, 3 месяца назад

Темы: 33

Сообщения: 534

Участник с: 23 февраля 2012

$ sudo systemctl status lm_sensors.service
lm_sensors.service - Initialize hardware monitoring sensors
   Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled)
   Active: failed (Result: exit-code) since Вс 2013-05-19 00:30:28 MSK; 1min 32s ago
  Process: 247 ExecStart=/usr/bin/sensors -s (code=exited, status=1/FAILURE)
  Process: 235 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=1/FAILURE)
май 19 00:30:28 myhost systemd[1]: lm_sensors.service: main process exited, code=exited, status=1/FAILURE
май 19 00:30:28 myhost systemd[1]: Failed to start Initialize hardware monitoring sensors.
май 19 00:30:28 myhost systemd[1]: Unit lm_sensors.service entered failed state.
$

vasek	# 9 лет, 3 месяца назад
Темы: 48 Сообщения: 11340 Участник с: 17 февраля 2013	Почитай внимательнее Wiki. Может что-то пропустил. Например, не вижу - systemctl enable lm_sensors.service. Повтори sensors-detect и на все вопросы отвечай yes PS....sensors работает и без sudo Ошибки не исчезают с опытом - они просто умнеют

samson4747	# 9 лет, 3 месяца назад
Темы: 33 Сообщения: 534 Участник с: 23 февраля 2012	$ sudo pacman -S lm_sensors предупреждение: lm_sensors-3.3.3-3 не устарел -- переустанавливается разрешение зависимостей... проверка на взаимную несовместимость... Пакеты (1): lm_sensors-3.3.3-3 Будет установлено: 0,46 MiB Изменение размера: 0,00 MiB :: Приступить к установке? [Y/n] (1/1) проверка ключей [######################] 100% (1/1) проверяется целостность пакета [######################] 100% (1/1) загрузка файлов пакета [######################] 100% (1/1) проверка конфликтов файлов [######################] 100% (1/1) проверяется доступное место [######################] 100% (1/1) переустановка lm_sensors [######################] 100% $ sudo sensors-detect # sensors-detect revision 6085 (2012-10-30 18:18:45 +0100) # Board: ASUSTeK Computer INC. P5GD1 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 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): 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): # DMI data unavailable, please consider installing dmidecode 2.7 # or later for better results. 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 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 4:00.0 (i2c-0) Do you want to scan it? (yes/NO/selectively): yes Next adapter: NVIDIA i2c adapter 1 at 4:00.0 (i2c-1) Do you want to scan it? (yes/NO/selectively): yes Next adapter: NVIDIA i2c adapter 2 at 4:00.0 (i2c-2) Do you want to scan it? (yes/NO/selectively): yes Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `w83627ehf': * ISA bus, address 0x290 Chip `Winbond W83627EHF/EF/EHG/EG Super IO Sensors' (confidence: 9) Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): Job for lm_sensors.service failed. See 'systemctl status lm_sensors.service' and 'journalctl -xn' for details. Unloading i2c-dev... OK Unloading cpuid... OK $ sudo systemctl enable lm_sensors.service $ sudo systemctl start lm_sensors Job for lm_sensors.service failed. See 'systemctl status lm_sensors.service' and 'journalctl -xn' for details. $ sudo systemctl status lm_sensors.service lm_sensors.service - Initialize hardware monitoring sensors Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled) Active: failed (Result: exit-code) since Вс 2013-05-19 21:29:20 MSK; 13s ago Process: 1206 ExecStart=/usr/bin/sensors -s (code=exited, status=1/FAILURE) Process: 1202 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=1/FAILURE) май 19 21:29:20 myhost systemd[1]: Starting Initialize hardware monitori..... май 19 21:29:20 myhost systemd[1]: lm_sensors.service: main process exit...RE май 19 21:29:20 myhost systemd[1]: Failed to start Initialize hardware m...s. май 19 21:29:20 myhost systemd[1]: Unit lm_sensors.service entered faile...e. $ sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. $ $ journalctl -xn Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. Error was encountered while opening journal files: Нет доступных данных -- Logs begin at Чт 2012-11-01 15:32:07 MSK, end at Чт 2013-05-16 14:22:17 MSK. май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Cu май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Go май 16 13:28:14 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Tr май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Cu май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Go май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Cu май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Go май 16 14:22:16 myhost gnome-session[420]: WARNING: Application 'gnome-shell.des май 16 14:22:17 myhost /etc/gdm/Xsession[420]: gnome-session[420]: WARNING: Appl май 16 14:22:17 myhost /etc/gdm/Xsession[420]: Message: applet now removed fr lines 1-11/11 (END)...skipping... -- Logs begin at Чт 2012-11-01 15:32:07 MSK, end at Чт 2013-05-16 14:22:17 MSK. -- май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: CurrentTime used to choose focus window; focus window may not май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Got a request to focus the no_focus_window with a timestamp of май 16 13:28:14 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Treating resize request of legacy application 0x1c002a2 (Windo май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: CurrentTime used to choose focus window; focus window may not май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Got a request to focus 0x200007f (Аудио) with a timestamp of 0 май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: CurrentTime used to choose focus window; focus window may not май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Got a request to focus the no_focus_window with a timestamp of май 16 14:22:16 myhost gnome-session[420]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 май 16 14:22:17 myhost /etc/gdm/Xsession[420]: gnome-session[420]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 май 16 14:22:17 myhost /etc/gdm/Xsession[420]: Message: applet now removed from the notification area ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-11/11 (END) "If you try to hide the complexity of the system, you'll end up with a more complex system". Layers of abstraction that serve to hide internals are never a good thing. Instead, the internals should be designed in a way such that they NEED no hiding. —Aaron Griffin

samson4747

# 9 лет, 3 месяца назад

Темы: 33

Сообщения: 534

Участник с: 23 февраля 2012

$ sudo pacman -S lm_sensors
предупреждение: lm_sensors-3.3.3-3 не устарел -- переустанавливается
разрешение зависимостей...
проверка на взаимную несовместимость...
Пакеты (1): lm_sensors-3.3.3-3
Будет установлено: 0,46 MiB
Изменение размера: 0,00 MiB
:: Приступить к установке? [Y/n]
(1/1) проверка ключей                              [######################] 100%
(1/1) проверяется целостность пакета               [######################] 100%
(1/1) загрузка файлов пакета                       [######################] 100%
(1/1) проверка конфликтов файлов                   [######################] 100%
(1/1) проверяется доступное место                  [######################] 100%
(1/1) переустановка lm_sensors                 [######################] 100%

$ sudo sensors-detect
# sensors-detect revision 6085 (2012-10-30 18:18:45 +0100)
# Board: ASUSTeK Computer INC. P5GD1
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 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):
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):
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
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
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 4:00.0 (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: NVIDIA i2c adapter 1 at 4:00.0 (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: NVIDIA i2c adapter 2 at 4:00.0 (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83627ehf':
* ISA bus, address 0x290
Chip `Winbond W83627EHF/EF/EHG/EG Super IO Sensors' (confidence: 9)
Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no):
Job for lm_sensors.service failed. See 'systemctl status lm_sensors.service' and 'journalctl -xn' for details.
Unloading i2c-dev... OK
Unloading cpuid... OK

$ sudo systemctl enable lm_sensors.service

$ sudo systemctl start lm_sensors
Job for lm_sensors.service failed. See 'systemctl status lm_sensors.service' and 'journalctl -xn' for details.

$ sudo systemctl status lm_sensors.service
lm_sensors.service - Initialize hardware monitoring sensors
   Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled)
   Active: failed (Result: exit-code) since Вс 2013-05-19 21:29:20 MSK; 13s ago
  Process: 1206 ExecStart=/usr/bin/sensors -s (code=exited, status=1/FAILURE)
  Process: 1202 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=1/FAILURE)
май 19 21:29:20 myhost systemd[1]: Starting Initialize hardware monitori.....
май 19 21:29:20 myhost systemd[1]: lm_sensors.service: main process exit...RE
май 19 21:29:20 myhost systemd[1]: Failed to start Initialize hardware m...s.
май 19 21:29:20 myhost systemd[1]: Unit lm_sensors.service entered faile...e.

$ sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
$

$ journalctl -xn
Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
Error was encountered while opening journal files: Нет доступных данных
-- Logs begin at Чт 2012-11-01 15:32:07 MSK, end at Чт 2013-05-16 14:22:17 MSK.
май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Cu
май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Go
май 16 13:28:14 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Tr
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Cu
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Go
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Cu
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Go
май 16 14:22:16 myhost gnome-session[420]: WARNING: Application 'gnome-shell.des
май 16 14:22:17 myhost /etc/gdm/Xsession[420]: gnome-session[420]: WARNING: Appl
май 16 14:22:17 myhost /etc/gdm/Xsession[420]: ** Message: applet now removed fr
lines 1-11/11 (END)...skipping...
-- Logs begin at Чт 2012-11-01 15:32:07 MSK, end at Чт 2013-05-16 14:22:17 MSK. --
май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: CurrentTime used to choose focus window; focus window may not
май 16 13:28:13 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Got a request to focus the no_focus_window with a timestamp of
май 16 13:28:14 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Treating resize request of legacy application 0x1c002a2 (Windo
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: CurrentTime used to choose focus window; focus window may not
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Got a request to focus 0x200007f (Аудио) with a timestamp of 0
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: CurrentTime used to choose focus window; focus window may not
май 16 13:29:27 myhost /etc/gdm/Xsession[420]: Предупреждение менеджера окон: Got a request to focus the no_focus_window with a timestamp of
май 16 14:22:16 myhost gnome-session[420]: WARNING: Application 'gnome-shell.desktop' killed by signal 11
май 16 14:22:17 myhost /etc/gdm/Xsession[420]: gnome-session[420]: WARNING: Application 'gnome-shell.desktop' killed by signal 11
май 16 14:22:17 myhost /etc/gdm/Xsession[420]: ** Message: applet now removed from the notification area
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-11/11 (END)

vasek	# 9 лет, 3 месяца назад
Темы: 48 Сообщения: 11340 Участник с: 17 февраля 2013	Sensors-detect завершил работу с ошибкой - естественно ничего не нашел. Job for lm_sensors.service failed. See 'systemctl status lm_sensors.service' and 'journalctl -xn' for details. Дальнейшее ничего можно было и не делать, а нужно смотреть логи журнала. Sensors-detect делал 19.05, а записи журнала ты привел на 16.05. Тебе написали, что ты не можешь видеть все записи. Или добавь себя в группу или запускай с sudo Тебе нужно смотреть логи журнала на дату и время, когда ты запускал sensors-detect Ошибки не исчезают с опытом - они просто умнеют

vasek

# 9 лет, 3 месяца назад

Темы: 48

Сообщения: 11340

Участник с: 17 февраля 2013

Sensors-detect завершил работу с ошибкой - естественно ничего не нашел.
Job for lm_sensors.service failed. See 'systemctl status lm_sensors.service' and 'journalctl -xn' for details.
Дальнейшее ничего можно было и не делать, а нужно смотреть логи журнала.
Sensors-detect делал 19.05, а записи журнала ты привел на 16.05. Тебе написали, что ты не можешь видеть все записи.
Или добавь себя в группу или запускай с sudo
Тебе нужно смотреть логи журнала на дату и время, когда ты запускал sensors-detect

Ошибки не исчезают с опытом - они просто умнеют

samson4747	# 9 лет, 3 месяца назад
Темы: 33 Сообщения: 534 Участник с: 23 февраля 2012	$ sudo journalctl -xn [sudo] password for nnikita: -- Logs begin at Чт 2012-11-01 15:32:07 MSK, end at Вс 2013-05-19 22:04:41 MSK. -- май 19 21:40:34 myhost dbus-daemon[244]: dbus[244]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org май 19 21:40:34 myhost dbus[244]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostn май 19 21:40:34 myhost systemd[1]: Starting Hostname Service... -- Subject: Unit systemd-hostnamed.service has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-hostnamed.service has begun starting up. май 19 21:40:34 myhost dbus-daemon[244]: dbus[244]: [system] Successfully activated service 'org.freedesktop.hostname1' май 19 21:40:34 myhost dbus[244]: [system] Successfully activated service 'org.freedesktop.hostname1' май 19 21:40:34 myhost systemd[1]: Started Hostname Service. -- Subject: Unit systemd-hostnamed.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-hostnamed.service has finished starting up. -- -- The start-up result is done. май 19 21:40:46 myhost /etc/gdm/Xsession[690]: (nautilus:1286): GVFS-WARNING : meta_journal_iterate: found short sized entry, possible jou май 19 21:40:47 myhost /etc/gdm/Xsession[690]: (nautilus:1286): GVFS-WARNING : meta_journal_iterate: found short sized entry, possible jou май 19 22:04:41 myhost sudo[1625]: nnikita : TTY=pts/0 ; PWD=/home/nnikita ; USER=root ; COMMAND=/usr/bin/journalctl -xn май 19 22:04:41 myhost sudo[1625]: pam_unix(sudo:session): session opened for user root by nnikita(uid=0) lines 1-23/23 (END) "If you try to hide the complexity of the system, you'll end up with a more complex system". Layers of abstraction that serve to hide internals are never a good thing. Instead, the internals should be designed in a way such that they NEED no hiding. —Aaron Griffin

samson4747

# 9 лет, 3 месяца назад

Темы: 33

Сообщения: 534

Участник с: 23 февраля 2012

$ sudo journalctl -xn
[sudo] password for nnikita:
-- Logs begin at Чт 2012-11-01 15:32:07 MSK, end at Вс 2013-05-19 22:04:41 MSK. --
май 19 21:40:34 myhost dbus-daemon[244]: dbus[244]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org
май 19 21:40:34 myhost dbus[244]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostn
май 19 21:40:34 myhost systemd[1]: Starting Hostname Service...
-- Subject: Unit systemd-hostnamed.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-hostnamed.service has begun starting up.
май 19 21:40:34 myhost dbus-daemon[244]: dbus[244]: [system] Successfully activated service 'org.freedesktop.hostname1'
май 19 21:40:34 myhost dbus[244]: [system] Successfully activated service 'org.freedesktop.hostname1'
май 19 21:40:34 myhost systemd[1]: Started Hostname Service.
-- Subject: Unit systemd-hostnamed.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-hostnamed.service has finished starting up.
--
-- The start-up result is done.
май 19 21:40:46 myhost /etc/gdm/Xsession[690]: (nautilus:1286): GVFS-WARNING **: meta_journal_iterate: found short sized entry, possible jou
май 19 21:40:47 myhost /etc/gdm/Xsession[690]: (nautilus:1286): GVFS-WARNING **: meta_journal_iterate: found short sized entry, possible jou
май 19 22:04:41 myhost sudo[1625]: nnikita : TTY=pts/0 ; PWD=/home/nnikita ; USER=root ; COMMAND=/usr/bin/journalctl -xn
май 19 22:04:41 myhost sudo[1625]: pam_unix(sudo:session): session opened for user root by nnikita(uid=0)
lines 1-23/23 (END)

vasek	# 9 лет, 3 месяца назад
Темы: 48 Сообщения: 11340 Участник с: 17 февраля 2013	Сделай полный запрос sudo journalctl --all , можешь для начала только ошибки sudo journalctl -a -p 3 и поищи на нужное время (как делать выборочно и другие запросы читай в help) Ошибки не исчезают с опытом - они просто умнеют

samson4747	# 9 лет, 3 месяца назад
Темы: 33 Сообщения: 534 Участник с: 23 февраля 2012	journalctl -b journalctl -b -a -p 3 "If you try to hide the complexity of the system, you'll end up with a more complex system". Layers of abstraction that serve to hide internals are never a good thing. Instead, the internals should be designed in a way such that they NEED no hiding. —Aaron Griffin

vasek	# 9 лет, 3 месяца назад
Темы: 48 Сообщения: 11340 Участник с: 17 февраля 2013	опции:-b - текущая загрузка, -a - все (вместе их употреблять не имеет смысла). Датчиков не найдено. Похоже на твоей материнке есть проблемы со снятием данных с датчиков. Немного погуглил, кое что нашел тут1 и тут2 — особо не читал. Посмотри, можешь еще потом погуглить Извиняюсь за повтор - спешил Ошибки не исчезают с опытом - они просто умнеют

vasek

# 9 лет, 3 месяца назад

Темы: 48

Сообщения: 11340

Участник с: 17 февраля 2013

опции:-b - текущая загрузка, -a - все (вместе их употреблять не имеет смысла).
Датчиков не найдено. Похоже на твоей материнке есть проблемы со снятием данных с датчиков. Немного погуглил, кое что нашел тут1 и тут2 — особо не читал. Посмотри, можешь еще потом погуглить
Извиняюсь за повтор - спешил

Ошибки не исчезают с опытом - они просто умнеют

vasek	# 9 лет, 3 месяца назад
Темы: 48 Сообщения: 11340 Участник с: 17 февраля 2013	опции:-b - текущая загрузка, -a - все (вместе их употреблять не имеет смысла). Датчиков не найдено. Похоже на твоей материнке есть проблемы со снятием данных с датчиков. Немного погуглил, кое что нашел тут1 и тут2 — особо не читал. Посмотри, можешь еще потом погуглить PS............ w83627ehf: Found W83627EHG chip at 0x290 - это из твоего лога. + еще ссылка Ошибки не исчезают с опытом - они просто умнеют

vasek

# 9 лет, 3 месяца назад

Темы: 48

Сообщения: 11340

Участник с: 17 февраля 2013

Ошибки не исчезают с опытом - они просто умнеют