http://bugzilla.novell.com/show_bug.cgi?id=612910 http://bugzilla.novell.com/show_bug.cgi?id=612910#c yang xiaoyu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |jdelvare@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612910 http://bugzilla.novell.com/show_bug.cgi?id=612910#c Jean Delvare changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|ASSIGNED |NEEDINFO InfoProvider| |MSchmidt_glz@gmx.de Severity|Major |Minor -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612910 http://bugzilla.novell.com/show_bug.cgi?id=612910#c3 --- Comment #3 from Jean Delvare 2010-06-11 13:45:07 UTC --- Including examples isn't the purpose of sensors.conf.default (which is installed as /etc/sensors3.conf). The upstream wiki has many example configuration files at: http://www.lm-sensors.org/wiki/Configurations These are configuration files for specific motherboards, not monitoring chips. A sample configuration for a given chip only makes sense if the manufacturer provides a recommended application circuit, and we do not have any for the IT8720F, so we can't derive a default configuration for that chip. And even if we had, motherboard vendors are free to diverge from these recommendations. We do not have a configuration file for the Gigabyte 890GPA-UD3H yet, but I can try and help you writing one. For this, I will need some data. First of all, if you also have Windows running on your system, please install Gigabyte's EasyTune software, and report everything it reports. Then, please write down everything related to hardware monitoring displayed in the BIOS setup screens: labels and values, and when values oscillate, all values ever printed for each item. And lastly, the output of "sensors" at the time being. Again, if some values oscillate, this is a valuable piece of information. Also look for messages in the kernel logs when the it87 driver gets loaded. With this information, I should be able to provide the basis of a configuration file for your board. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612910 http://bugzilla.novell.com/show_bug.cgi?id=612910#c4 --- Comment #4 from Michael Schmidt 2010-06-13 09:47:39 UTC --- OK, EasyTune5 says: VCORE = 1,340 +3,3V = 3,34 +12V = 12,230 EasyTune6 says: CPU = 1,344 DRAM = 1,488 +3,3V = 3,344 +12V = 12,175 BIOS: VCORE = 1,344 V DDR3 1,5V = 1,488 V +3,3V = 3,312 V +12V = 12,239 V If I change the setting "System Voltage Control" to manual, I get additional Value (by setting normal for all Values): CPU PLL Voltage Control 2,500 V DRAM Voltage Control 1,500 V DDR VTT Voltage Control 0,750 V NB Voltage Control 1,300 V SidePort Mem Volt Control 1,600 V NB/PCIe/PLL Voltage Control 1,800 V Normal CPU Core 1,3500 V The it87 is loaded. sensors says: k10temp-pci-00c3 Adapter: PCI adapter temp1: +34.9°C (high = +70.0°C, crit = +81.0°C) it8720-isa-0228 Adapter: ISA adapter in0: +1.07 V (min = +0.00 V, max = +4.08 V) in1: +1.49 V (min = +0.00 V, max = +4.08 V) in2: +3.31 V (min = +0.00 V, max = +4.08 V) in3: +2.99 V (min = +0.00 V, max = +4.08 V) in4: +3.09 V (min = +0.00 V, max = +4.08 V) in5: +1.97 V (min = +0.00 V, max = +4.08 V) in6: +4.08 V (min = +0.00 V, max = +4.08 V) in7: +2.16 V (min = +0.00 V, max = +4.08 V) Vbat: +3.23 V fan1: 1776 RPM (min = 10 RPM) fan2: 0 RPM (min = 0 RPM) fan3: 3139 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) temp1: +43.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: +32.0°C (low = +127.0°C, high = +70.0°C) sensor = thermal diode temp3: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor cpu0_vid: +0.413 V -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612910 http://bugzilla.novell.com/show_bug.cgi?id=612910#c6 --- Comment #6 from Jean Delvare 2010-06-14 13:51:40 UTC --- Created an attachment (id=368972) --> (http://bugzilla.novell.com/attachment.cgi?id=368972) libsensors configuration file for Gigabyte 890GPA-UD3H Put this file into /etc/sensors.d and the output of sensors should be much better. It's not perfect though. You didn't provide any comparison points for temperatures and fans, so it's pure guess work at the moment. If you provide the temperature and fan readings of the BIOS and EasyTune, we might improve these sections. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612910 http://bugzilla.novell.com/show_bug.cgi?id=612910#c8 --- Comment #8 from Michael Schmidt 2010-06-20 15:47:07 UTC --- The both isadump-commands gets all ffh back. Here is the new output from sensors: k10temp-pci-00c3 Adapter: PCI adapter temp1: +33.5°C (high = +70.0°C, crit = +81.0°C) it8720-isa-0228 Adapter: ISA adapter Vcore: +1.07 V (min = +0.78 V, max = +1.50 V) Vdram: +1.49 V (min = +1.42 V, max = +1.57 V) +3.3V: +3.33 V (min = +3.14 V, max = +3.47 V) +5V: +5.03 V (min = +4.76 V, max = +5.24 V) +12V: +12.24 V (min = +11.41 V, max = +12.62 V) in5: +1.95 V (min = +0.00 V, max = +4.08 V) in7: +2.16 V (min = +0.00 V, max = +4.08 V) Vbat: +3.22 V CPU Fan: 1626 RPM (min = 1000 RPM) Sys Fan: 2227 RPM (min = 1000 RPM) temp1: +43.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor CPU Temp: +30.0°C (low = +127.0°C, high = +70.0°C) sensor = thermal diode temp3: +35.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor cpu0_vid: +0.413 V But here is new problem: If here is a setting not correct - e.g. the Fan_min to high - an I get a ALARM, I can the sound not turn of with a correct value in sensor3.conf and a sensors -s. I can the sound only turn of with a reboot of the computer. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612910 http://bugzilla.novell.com/show_bug.cgi?id=612910#c10 --- Comment #10 from Michael Schmidt 2010-06-21 10:03:17 UTC ---

and this is done by _reading_ from the chip, not by writing to it. So, after changing the limits in the configuration file, and running "sensors -s", you must run "sensors" again. If the alarm condition is gone, the beeping will stop.

No, it has not stopped. First by the reboot of the computer. Sorry, the isadump take a time. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612910 http://bugzilla.novell.com/show_bug.cgi?id=612910#c12 --- Comment #12 from Jean Delvare 2010-06-22 09:44:28 UTC --- The dump confirms that in3 is +5V (bit 0 of register 0x2c is set). So you should definitely see a message in the logs saying so when you load the it87 driver. Please double check, this is the third time I ask. Surprisingly, in7 isn't mapped to 5VSB internally (bit 1 of register 0x2c isn't set). Given that there is no physical pin on the IT8720F for in7, I don't get the idea. This explains why the value reported as in7 makes no sense. The more surprising is that, according to the datasheet, this bit should be set by default. So either the datasheet is wrong, or the BIOS explicitly disables this feature for a reason I don't grasp. You may try the following command sequence as root to enable 5VSB monitoring internally, and see if you get a better output for in7: # rmmod it87 # isaset -y -f 0x2e 0x87 # isaset -y -f 0x2e 0x01 # isaset -y -f 0x2e 0x55 # isaset -y -f 0x2e 0x55 # isaset -y -f 0x2e 0x07 # isaset -y -f 0x2f 7 # isaset -y -f 0x2e 0x2c # isaset -y -f 0x2f 0x03 # isaset -y -f 0x2e 0x02 # isaset -y -f 0x2f 0x02 # modprobe it87 You must type all commands correctly, otherwise it won't work and you may get into trouble. And please report the log messages after loading the it87 driver. If the above works for you, then I may let the it87 driver do it automatically for the IT8720F on all boards. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612910 http://bugzilla.novell.com/show_bug.cgi?id=612910#c14 --- Comment #14 from Jean Delvare 2010-06-22 19:51:07 UTC --- The messages in /var/log/message are exactly what I expected, thanks. After the isaset commands, in7 looks much better, and you can get the right output with the following settings in your configuration file: label in7 "5VSB" compute in7 @ * (6.8/10+1), @ / (6.8/10+1) I believe that the driver should change the device configuration that way automatically for the IT8720F. I don't understand why it isn't the default, I'll ask my ITE contact about it. All the reports I've seen on the web had the wrong value too, so I have a serious doubt about the claims in the datasheet. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612910 http://bugzilla.novell.com/show_bug.cgi?id=612910#c16 Jean Delvare changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|MSchmidt_glz@gmx.de | --- Comment #16 from Jean Delvare 2010-06-24 08:27:05 UTC --- I think we're almost done here. You can either add the isaset sequence to /etc/init.d/after.local, or build and use the standalone it87 driver from: http://khali.linux-fr.org/devel/misc/it87/ I've posted the in7 fix upstream already, and will get it merged into kernel 2.6.35 (and from there, to 2.6.34-stable.) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612910 http://bugzilla.novell.com/show_bug.cgi?id=612910#c Jean Delvare changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #371411|1 |0 is patch| | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612910 http://bugzilla.novell.com/show_bug.cgi?id=612910#c20 --- Comment #20 from Jean Delvare 2010-06-24 11:48:05 UTC --- No, in8 (Vbat) has no limit settings. This is a hardware limitation of all the IT87xxF chips, nothing the it87 driver can do. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612910 http://bugzilla.novell.com/show_bug.cgi?id=612910#c22 --- Comment #22 from Bernhard Wiedemann --- This is an autogenerated message for OBS integration: This bug (612910) was mentioned in https://build.opensuse.org/request/show/42060 11.3:Test / kernel-source https://build.opensuse.org/request/show/42266 Factory / kernel-source https://build.opensuse.org/request/show/42378 11.3:Test / kernel-source -- You are receiving this mail because: You are on the CC list for the bug.