lm-sensors AMD

sensors<Tab>

sensors-detect запускали опосля установки? и на все вопросы отвечайте «Yes»

Возможно надо модуль k10temp собрать (хотя проц поколения k8 вроде) - в ядро его еще не включили. Исходники и инструкция: http://blog.morrigan.ch/?p=9

eugeneblack-- сделал как по ссылке ни фига ((( не находит сенсоров

в ядре есть поддержка?
zgrep CORETEMP /proc/config.gz
CONFIG_SENSORS_CORETEMP=y

zgrep CORETEMP /proc/config.gz gzip: /proc/config.gz: No such file or directory

дык посмотри в конфиге ядра

как-нибудь так
grep CONFIG_SENSORS_CORETEMP /usr/src/linux-$(uname -r)/.config

CONFIG_SENSORS_CORETEMP=m стоит

а этот самый модуль подгружен? где ньть в lsmod смотри

root@avolon-linux:/usr/src/linux-headers-2.6.31-17-generic# lsmod |grep core
soundcore 9088 1 snd
edac_core 48876 1 amd64_edac_mod
root@avolon-linux:/usr/src/linux-headers-2.6.31-17-generic# modprobe coretemp
FATAL: Error inserting coretemp (/lib/modules/2.6.31-17-generic/kernel/drivers/hwmon/coretemp.ko): No such device

ой - тебе нужен
grep CONFIG_SENSORS_K8TEMP /usr/src/linux-$(uname -r)/.config

или для 10-ки собирать, если этот не поймёт

CONFIG_SENSORS_K8TEMP=m стоит

собрал модуль k10temp эфект 0

Модуль собрал, а в /lib/modules/(и далее где находятся k8temp.ko) закинул его? А подгрузить не забыл?

все собрано и установлено

root@avolon-linux:/var/log# root@avolon-linux:/lib/modules/2.6.31-17-generic/kernel/drivers/hwmon# lsmod |grep k10 k10temp 3712 0 root@avolon-linux:/lib/modules/2.6.31-17-generic/kernel/drivers/hwmon# lsmod |grep k8 k8temp 5504 0 root@avolon-linux:/lib/modules/2.6.31-17-generic/kernel/drivers/hwmon#

вот k10temp из 2.6.33 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=drivers/hwmon/k10temp.c;hb=6102c315d896fb020550fb2481613485872978f6

да кстати, а что выводит sensors?

вот лог если поможет

[code]


oot@avolon-linux:/var/log# cat messages |grep conflict
Jan 18 09:31:31 avolon-linux kernel: [ 22.621290] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SMBI [0xb00-0xb0f]
Jan 18 09:31:31 avolon-linux kernel: [ 22.621290] ACPI: This conflict may cause random problems and system instability
Jan 18 11:09:08 avolon-linux kernel: [ 27.420041] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SMBI [0xb00-0xb0f]
Jan 18 11:09:08 avolon-linux kernel: [ 27.420041] ACPI: This conflict may cause random problems and system instability
Jan 18 17:52:25 avolon-linux kernel: [ 7.796153] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SMBI [0xb00-0xb0f]
Jan 18 17:52:25 avolon-linux kernel: [ 7.796161] ACPI: This conflict may cause random problems and system instability
Jan 18 17:59:41 avolon-linux kernel: [ 15.421297] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SMBI [0xb00-0xb0f]
Jan 18 17:59:41 avolon-linux kernel: [ 15.421297] ACPI: This conflict may cause random problems and system instability
Jan 18 18:03:06 avolon-linux kernel: [ 14.828656] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SMBI [0xb00-0xb0f]
Jan 18 18:03:06 avolon-linux kernel: [ 14.828656] ACPI: This conflict may cause random problems and system instability
Jan 18 18:53:32 avolon-linux kernel: [ 15.670046] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SMBI [0xb00-0xb0f]
Jan 18 18:53:32 avolon-linux kernel: [ 15.670046] ACPI: This conflict may cause random problems and system instability
Jan 18 22:44:19 avolon-linux kernel: [ 7.445671] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SMBI [0xb00-0xb0f]
Jan 18 22:44:19 avolon-linux kernel: [ 7.445678] ACPI: This conflict may cause random problems and system instability
Jan 18 23:49:38 avolon-linux kernel: [ 6.821337] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SMBI [0xb00-0xb0f]
Jan 18 23:49:38 avolon-linux kernel: [ 6.821344] ACPI: This conflict may cause random problems and system instability
Jan 18 23:51:41 avolon-linux kernel: [ 12.251293] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SMBI [0xb00-0xb0f]
Jan 18 23:51:41 avolon-linux kernel: [ 12.251293] ACPI: This conflict may cause random problems and system instability
Jan 19 07:35:50 avolon-linux kernel: [ 12.525271] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SMBI [0xb00-0xb0f]
Jan 19 07:35:50 avolon-linux kernel: [ 12.525271] ACPI: This conflict may cause random problems and system instability
Jan 19 16:46:45 avolon-linux kernel: [ 7.259815] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SMBI [0xb00-0xb0f]
Jan 19 16:46:45 avolon-linux kernel: [ 7.259823] ACPI: This conflict may cause random problems and system instability
Jan 19 20:29:17 avolon-linux kernel: [ 20.481304] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SMBI [0xb00-0xb0f]
Jan 19 20:29:17 avolon-linux kernel: [ 20.481304] ACPI: This conflict may cause random problems and system instability
Jan 20 07:18:27 avolon-linux kernel: [ 20.231293] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SMBI [0xb00-0xb0f]
Jan 20 07:18:27 avolon-linux kernel: [ 20.231293] ACPI: This conflict may cause random problems and system instability

[/code]

ну можно попробовать еще acpi_enforce_resources=no добавить к опциям загрузки ядра.

добавил эфекто 0

Исходя из этого http://lwn.net/Articles/363117/, все же нужен k10temp, но он не на всех ревизиях процессорного работать может, как оказалось. На флуд в логе про smbus можно не обращать внимания.

Ну так sensors, что показывает?! А то у меня вот Phenom II X3 с разблоченным 4м ядром, так модуль подгружается, а в sensors вывод показывает только один температурный датчик в ядре и на нем 0 градусов.

Вот k10temp подружен ((

root@avolon-linux:/home/avolon# sensors-detect
# sensors-detect revision 5729 (2009-06-02 15:51:29 +0200)
# System: Hewlett-Packard HP Pavilion dv5 Notebook PC (laptop)
# Board: HP 3622

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
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal and voltage sensors... 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'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... 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-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600 SMBus

Next adapter: SMBus PIIX4 adapter at 0b00 (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'... 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)

Sorry, no sensors were detected.
This is relatively common on laptops, where thermal management is
handled by ACPI rather than the OS

Что выводит sensors, а не sensors-detect?

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

1.

AMD K10 thermal sensors... No

Sorry, no sensors were detected.
This is relatively common on laptops, where thermal management is
handled by ACPI rather than the OS 

ММММ!! А как через аспи смотреть вот что я нарыл

/proc/acpi/thermal_zone/THRM/temperature ноо нет такого

acpi -t нечего не показывает(( CNFIG_ACPI_THERMAL=y

Мда не укого нет мыслей??