sensors-detect не определяет ASUST A88XM-A

[Juriy]

Заменил mb плату в домашнем медиа-сервере на ASUST A88XM-A.
Вроде все прошло нормально, грузиться, работает.
Только sensors отказывается работать.

Код Выделить Развернуть

uname -a
Linux mynas 3.2.0-4-amd64 #1 SMP Debian 3.2.89-2 x86_64 GNU/Linux
CPU: AMD A4-7300 APU with Radeon HD Graphics @ 3.8GHz
MBoard: ASUSTeK COMPUTER INC. A88XM-A

sensors-detect

Код Выделить Развернуть

root@mynas:~# sensors-detect
# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
# Board: ASUSTeK COMPUTER INC. A88XM-A

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 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'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8603
    (logical device 4 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): 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-piix4' for device 0000:00:14.0: AMD Hudson-2 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
Handled by driver `eeprom' (already loaded), chip type `eeprom'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver `eeprom' (already loaded), chip type `eeprom'
    (note: this is probably NOT a sensor chip!)

Next adapter: Radeon i2c bit bus 0x90 (i2c-1)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x91 (i2c-2)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x92 (i2c-3)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x93 (i2c-4)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x94 (i2c-5)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x95 (i2c-6)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon aux bus DP-auxch (i2c-7)
Do you want to scan it? (yes/NO/selectively): y

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.

[свернуть]

lspci

Код Выделить Развернуть

root@mynas:~# lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Root Complex
00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Device 9996
00:01.1 Audio device: Advanced Micro Devices [AMD] nee ATI Trinity HDMI Audio Controller
00:10.0 USB controller: Advanced Micro Devices [AMD] FCH USB XHCI Controller (rev 09)
00:10.1 USB controller: Advanced Micro Devices [AMD] FCH USB XHCI Controller (rev 09)
00:11.0 SATA controller: Advanced Micro Devices [AMD] FCH SATA Controller [AHCI mode] (rev 40)
00:14.0 SMBus: Advanced Micro Devices [AMD] FCH SMBus Controller (rev 16)
00:14.3 ISA bridge: Advanced Micro Devices [AMD] FCH LPC Bridge (rev 11)
00:14.4 PCI bridge: Advanced Micro Devices [AMD] FCH PCI Bridge (rev 40)
00:15.0 PCI bridge: Advanced Micro Devices [AMD] Hudson PCI to PCI bridge (PCIE port 0)
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 0
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 5
01:05.0 Ethernet controller: D-Link System Inc DGE-528T Gigabit Ethernet Adapter (rev 10)

[свернуть]

lsmod

Код Выделить Развернуть

root@mynas:~# lsmod
Module                  Size  Used by
eeprom                 12537  0
i2c_dev                13109  0
cpuid                  12708  0
cpufreq_conservative    13147  2
cpufreq_userspace      12576  0
cpufreq_stats          12866  0
cpufreq_powersave      12454  0
softdog                12666  2
quota_v2               12959  10
quota_tree             12906  1 quota_v2
nfsd                  216052  2
nfs                   308353  0
nfs_acl                12511  2 nfs,nfsd
auth_rpcgss            37185  2 nfs,nfsd
fscache                36739  1 nfs
lockd                  67306  2 nfs,nfsd
sunrpc                173736  6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd
k10temp                12611  0
hwmon_vid              12430  0
loop                   22634  0
snd_hda_codec_hdmi     30824  0
snd_hda_intel          26259  0
snd_hda_codec          78031  2 snd_hda_intel,snd_hda_codec_hdmi
snd_hwdep              13186  1 snd_hda_codec
snd_pcm                68083  3 snd_hda_codec,snd_hda_intel,snd_hda_codec_hdmi
snd_page_alloc         13003  2 snd_pcm,snd_hda_intel
snd_timer              22970  1 snd_pcm
snd                    52893  6 snd_hda_codec,snd_timer,snd_pcm,snd_hwdep,snd_hda_intel,snd_hda_codec_hdmi
powernow_k8            17618  0
mperf                  12453  1 powernow_k8
crc32c_intel           12747  0
radeon                722295  1
aesni_intel            50667  0
eeepc_wmi              12564  0
asus_wmi               18726  1 eeepc_wmi
sparse_keymap          12760  1 asus_wmi
ttm                    53664  1 radeon
drm_kms_helper         31370  1 radeon
drm                   183920  3 drm_kms_helper,ttm,radeon
aes_x86_64             16843  1 aesni_intel
soundcore              13065  1 snd
power_supply           13475  1 radeon
aes_generic            33026  2 aes_x86_64,aesni_intel
pcspkr                 12579  0
rfkill                 19005  1 asus_wmi
cryptd                 14517  1 aesni_intel
i2c_algo_bit           12841  1 radeon
evdev                  17562  5
i2c_piix4              12536  0
i2c_core               23876  7 i2c_piix4,i2c_algo_bit,drm,drm_kms_helper,radeon,i2c_dev,eeprom
video                  17683  0
processor              28149  3 powernow_k8
wmi                    13243  1 asus_wmi
thermal_sys            18040  2 processor,video
button                 12937  0
ext4                  355097  6
crc16                  12343  1 ext4
jbd2                   62412  1 ext4
mbcache                13082  1 ext4
dm_mod                 63682  0
md_mod                 87721  0
microcode              30230  0
sg                     25874  0
sd_mod                 36187  11
crc_t10dif             12348  1 sd_mod
ahci                   29136  6
libahci                22941  1 ahci
xhci_hcd               73411  0
r8169                  47008  0
mii                    12675  1 r8169
libata                140721  2 libahci,ahci
scsi_mod              162321  3 libata,sd_mod,sg
usbcore               128741  2 xhci_hcd
usb_common             12354  1 usbcore

[свернуть]

[yoric]

Судя по ядру, у Вас debian 7, то есть устаревший. Оно же пишет, найден неизвестный ITE, модуля для него нет. Вывод - надо обновиться, через 8 на 9 debian.

[Juriy]

Дело в том что на debian 7 стоит openmediavault 2 версии
Обновляться пробовал:
1) Если только обновить Debian, напрочь отваливается omv2.
2) Если обновить omv2 вместе с Debian до omv3, установленные плагины со всеми настройками отваливаются.
Думал может проще один sensors заставить работать, чем ради него заново пере устанавливать и настраивать omv.

[yoric]

Проще идти в струе))