[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Как загрузить hw-монитор?



Ivan Zavarzin:
> Иван Лох:
>> On Fri, Jul 27, 2012 at 09:04:21PM +0400, Ivan Zavarzin wrote:
>>>
> 
> Под wheezy проблема с управление кулерами остаются, find /sys -name
> "*fan*" ничего не находит.
> Хотя температура ниже градусов на 10 (70 - 75 С).
>>> Да
>>> Как я понимаю, пакет lm-sensors?
>>>>
>>> $ sensors
>>
>> А 
>> eeepc-laptop
>> загружен?
>>
>> Попробуйте
>> sensors-detect
> Вывод сейчас такой:
> ~# sensors-detect
> # sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
> # System: ASUSTeK Computer INC. 1015BXO [x.x] (laptop)
> 
> 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): YES
> 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...                   Success!
>     (driver `k10temp')
> 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): YES
> 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'...                                      No
> 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 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-piix4' for device 0000:00:14.0: ATI Technologies Inc
> SB600/SB700/SB800 SMBus
> Module i2c-dev loaded successfully.
> 
> Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
> Do you want to scan it? (YES/no/selectively): YES
> 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: Radeon i2c bit bus 0x91 (i2c-1)
> Do you want to scan it? (YES/no/selectively): YES
> 
> Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
> Do you want to scan it? (YES/no/selectively): YES
> 
> Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
> Do you want to scan it? (YES/no/selectively): YES
> 
> Next adapter: Radeon i2c bit bus 0x94 (i2c-4)
> Do you want to scan it? (YES/no/selectively): YES
> 
> Next adapter: Radeon i2c bit bus 0x95 (i2c-5)
> Do you want to scan it? (YES/no/selectively): YES
> 
> Next adapter: Radeon i2c bit bus 0x96 (i2c-6)
> Do you want to scan it? (YES/no/selectively): YES
> Y
> Next adapter: Radeon i2c bit bus 0x97 (i2c-7)
> 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 `k10temp' (autoloaded):
>   * Chip `AMD Family 12h and 14h thermal sensors' (confidence: 9)
> 
> No modules to load, skipping modules configuration.
> 
> Unloading i2c-dev... OK
> Unloading cpuid... OK
> 
> По-моему, ничего не изменилось
> 
>> 
>> HW монитор не загружен же...
>>
> 

Соответственно, под wheezy данная проблема автоматически не решилась.
Как устранить эту ошибку?


Reply to: