Re: cannot start lm_sensors daemon on Fedora 14 on AMD CPU

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

 



Just forgot to mention that adding
HWMON_MODULES="k10temp"
to the /etc/sysconfig/lm_sensors solved the problem,
but I should not edit configuration files manually.

~Daniil.

On Sun, Feb 6, 2011 at 7:35 PM, Daniil Ivanov <daniil.ivanov@xxxxxxxxx> wrote:
> Hi!
>
> I'm using Fedora 14 and having an issue with lm_sensors deamon.
> Attempt to start it fails.x: lm-sensors <at> lm-sensors <dot> org.
> /etc/init.d/lm_sensors start
> Starting lm_sensors: not configured, run sensors-detect    [WARNING]
>
> Then I use sensors-detect:
>
> #  sensors-detect
> # sensors-detect revision 5861 (2010-09-21 17:21:05 +0200)
> # System: Hewlett-Packard HP Pavilion dv6 Notebook PC (laptop)
> # Board: Hewlett-Packard 1440
>
> 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):
> 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...                           Success!
>    (driver `k10temp')
> AMD Family 11h thermal sensors...                           No
> Intel Core family thermal sensor...                         No
> Intel Atom 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'...                   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'...                   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):
> 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):
> 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 VGA (i2c-0)
> Do you want to scan it? (YES/no/selectively):
>
> Next adapter: Radeon i2c bit bus LVDS (i2c-1)
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x4f
> Probing for `National Semiconductor LM75'...                No
> Probing for `Dallas Semiconductor DS75'...                  No
> Probing for `Dallas Semiconductor DS1621/DS1631'...         No
> Probing for `Texas Instruments TMP421'...                   No
> Probing for `Texas Instruments TMP422'...                   No
> Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
> 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 LVDS (i2c-2)
> Do you want to scan it? (YES/no/selectively):
>
> Next adapter: Radeon i2c bit bus HDMI (i2c-3)
> Do you want to scan it? (YES/no/selectively):
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
>
> Driver `k10temp' (autoloaded):
>  * Chip `AMD Family 10h thermal sensors' (confidence: 9)
>
> No modules to load, skipping modules configuration.
>
> Unloading i2c-dev... OK
>
> k10temp is autoloaded module, so my /etc/sysconfig/lm_sensors is empty
> # cat /etc/sysconfig/lm_sensors
> #    /etc/sysconfig/sensors - Defines modules loaded by
> /etc/rc.d/init.d/lm_sensors
> # Run sensors-detect to generate this config file
>
> However, lm_sensors.init checks, if there is an occurrence of
> HWMON_MODULES in /etc/sysconfig/lm_sensors
> http://www.lm-sensors.org/browser/lm-sensors/trunk/prog/init/lm_sensors.init#L48
> resulting in impossibility to start daemon.
>
> Thanks, Daniil.
>

_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors



[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux