Hi.
As request, here is some system information :
But, I beleive the problem is not from theses setting
So, whatever , they are ...
* Motherboard vendor and model :
Gigabyte GA-880GM-UD2H
* Lm_sensors and kernel versions :
LM v 3.3.2 (from the Debian deposite) / Kernel 3.2.0-4-amd64
* The output of sensors :
frederic@X4-955:~$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
AM10 Core: +29.9°C (high = +70.0°C)
(crit = +79.0°C, hyst = +77.0°C)
it8720-isa-0228
Adapter: ISA adapter
Vcore: +1.02 V (min = +0.80 V, max = +1.50 V)
Vram: +1.60 V (min = +1.52 V, max = +1.68 V)
+3.3V: +2.83 V (min = +3.14 V, max = +3.47 V) ALARM
+5V: +5.00 V (min = +4.76 V, max = +5.24 V)
+12V: +12.17 V (min = +11.40 V, max = +12.62 V)
+5V_SNB: +4.82 V (min = +0.00 V, max = +6.68 V)
Vbat: +3.28 V
CPU Fan: 1569 RPM (min = 500 RPM)
SYS Fan: 1445 RPM (min = 700 RPM)
CPU Temp: +27.0°C (low = +20.0°C, high = +70.0°C) sensor =
thermistor
MB Temp: +28.0°C (low = +20.0°C, high = +60.0°C) sensor =
thermal diode
NBr Temp: +27.0°C (low = +20.0°C, high = +60.0°C) sensor =
thermistor
intrusion0: OK
frederic@X4-955:~$
* The dmesg or syslog output if applicable
Nothing about Fancontrol neither LM-sensors
* The output of (as root) sensors-detect
root@X4-955:/home/frederic# sensors-detect
# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
# System: Gigabyte Technology Co., Ltd. GA-880GM-UD2H
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... Success!
(driver `k10temp')
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'... No
Trying family `ITE'... Yes
Found `ITE IT8720F Super IO Sensors' Success!
(address 0x228, driver `it87')
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):
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):
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.
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `it87':
* ISA bus, address 0x228
Chip `ITE IT8720F Super IO Sensors' (confidence: 9)
Driver `k10temp' (autoloaded):
* Chip `AMD Family 10h thermal sensors' (confidence: 9)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
it87
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)
Unloading i2c-dev... OK
Unloading cpuid... OK
root@X4-955:/home/frederic#
* The output of lsmod
root@X4-955:/home/frederic# lsmod
Module Size Used by
fuse 62020 3
parport_pc 22364 0
ppdev 12763 0
bnep 17567 2
lp 17149 0
parport 31858 3 lp,ppdev,parport_pc
rfcomm 33700 0
bluetooth 119455 10 rfcomm,bnep
rfkill 19012 2 bluetooth
pci_stub 12429 1
vboxpci 19103 0
vboxnetadp 25443 0
vboxnetflt 23608 0
vboxdrv 190105 3 vboxnetflt,vboxnetadp,vboxpci
binfmt_misc 12957 1
nfsd 216170 2
nfs 308313 0
nfs_acl 12511 2 nfs,nfsd
auth_rpcgss 37143 2 nfs,nfsd
fscache 36739 1 nfs
lockd 67306 2 nfs,nfsd
sunrpc 173730 6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd
ip6t_LOG 12609 4
xt_hl 12449 6
ip6t_rt 12499 3
nf_conntrack_ipv6 13316 7
nf_defrag_ipv6 12832 1 nf_conntrack_ipv6
ipt_REJECT 12502 1
ipt_LOG 12605 5
xt_multiport 12548 2
xt_limit 12638 12
xt_tcpudp 12570 25
xt_addrtype 12557 4
xt_state 12503 14
ip6table_filter 12540 1
ip6_tables 22175 3 ip6table_filter,ip6t_rt,ip6t_LOG
nf_conntrack_netbios_ns 12445 0
nf_conntrack_broadcast 12365 1 nf_conntrack_netbios_ns
nf_nat_ftp 12460 0
nf_nat 18242 1 nf_nat_ftp
nf_conntrack_ipv4 14078 9 nf_nat
nf_defrag_ipv4 12483 1 nf_conntrack_ipv4
nf_conntrack_ftp 12605 1 nf_nat_ftp
nf_conntrack 52720 8
nf_conntrack_ftp,nf_conntrack_ipv4,nf_nat,nf_nat_ftp,nf_conntrack_broadcast,nf_conntrack_netbios_ns,xt_state,nf_conntrack_ipv6
iptable_filter 12536 1
ip_tables 22042 1 iptable_filter
x_tables 19118 14
ip_tables,iptable_filter,ip6_tables,ip6table_filter,xt_state,xt_addrtype,xt_tcpudp,xt_limit,xt_multiport,ipt_LOG,ipt_REJECT,ip6t_rt,xt_hl,ip6t_LOG
it87 30712 0
hwmon_vid 12430 1 it87
loop 22641 0
snd_hda_codec_hdmi 30824 1
joydev 17266 0
snd_hda_codec_realtek 188858 1
fglrx 7359580 99
snd_hda_intel 26259 3
snd_hda_codec 78031 3
snd_hda_intel,snd_hda_codec_realtek,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_seq 45126 0
snd_seq_device 13176 1 snd_seq
snd_timer 22917 2 snd_seq,snd_pcm
snd 52889 15
snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_realtek,snd_hda_codec_hdmi
evdev 17562 9
powernow_k8 17618 0
edac_mce_amd 17103 0
mperf 12453 1 powernow_k8
edac_core 35258 0
sp5100_tco 12900 0
processor 28157 1 powernow_k8
button 12937 1 fglrx
k10temp 12611 0
i2c_piix4 12536 0
i2c_core 23876 1 i2c_piix4
soundcore 13065 1 snd
pcspkr 12579 0
wmi 13243 0
serio_raw 12931 0
thermal_sys 18040 1 processor
ext4 350763 2
crc16 12343 2 ext4,bluetooth
jbd2 62115 1 ext4
mbcache 13114 1 ext4
microcode 30126 0
hid_logitech_dj 17313 0
usbhid 36418 1 hid_logitech_dj
hid 81328 2 usbhid,hid_logitech_dj
usb_storage 43870 1
sg 25874 0
sr_mod 21899 0
sd_mod 36136 7
crc_t10dif 12348 1 sd_mod
cdrom 35401 1 sr_mod
ata_generic 12479 0
ohci_hcd 26563 0
firewire_ohci 35772 0
firewire_core 48449 1 firewire_ohci
crc_itu_t 12347 1 firewire_core
pata_atiixp 12736 0
ahci 24997 3
libahci 22860 1 ahci
ehci_hcd 40215 0
libata 140630 4 libahci,ahci,pata_atiixp,ata_generic
scsi_mod 162269 5 libata,sd_mod,sr_mod,sg,usb_storage
usbcore 128741 5 ehci_hcd,ohci_hcd,usb_storage,usbhid
r8169 47008 0
usb_common 12354 1 usbcore
mii 12675 1 r8169
root@X4-955:/home/frederic#
* If a PCI chip problem: the output of lspci -nn
None
* If an I2C sensor chip problem: the output of (as root) i2cdetect
X where X = the bus number (run i2cdetect -l to list the buses)
None
* Part numbers of chips on your motherboard you think are the
sensor chips (look at your motherboard)
None
________________________________________________________________________
So, the problem is Fancontrol don't want to load on the boot sequence.
What I done ?
On begining all was running fine. Fancontrol adjust my fans.
I attemps to update lm-sensors, not from the debian deposite,but from
the download area , here.
I follow exactly word by word the process describe in the INSTALL file
include in the tar file.
Also, I install the flex and bison packages.
then, as root, I run :
1. make install
2. make user_install (I don't remember where I found/read this
command,... maybe in the makefile itself)
No error on these commands.
But, fancontrol don't drive fans.
So, I expect if I remove/uninstall this release, everything will be back
fine :( :(
But NO !
I deleted the
/usr/local/lib
/usr/local/bin
/usr/local/sbin
/usr/local/ and all other
Nothing changed after reboot ; fan stay on MAX !
So, I restaure previous directories and run :
1. make user_uninstall
Next reboot, same situation.
So, I run Synaptic (which I always use for install/remove/update
packages) and I remove fancontrol and lm-sensors.
Then reboot and I install back the both packages from Synaptic.
I run sensors-detect, pwmconfig. All run fine without error.
I run fancontrol as root. Fancontrol drive my fans.
But on reboot, fancontrol don't start.
Before all the operation, I never change manualy something for run
fancontrol on boot.
What I have to check/correct ?
Please.
Regards.
_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
