Configuration file for the ASUS Z87-K motherboard

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

 



Motherboard: ASUS Z87-K. 
Processor: Intel i5-4570. 
3 coolers: 1 on the processor and 2 in the case (not counting the video card cooler and power supply).

OS: Ubuntu 14.04 LTS (x64).
Kernel versions: 3.13.0-29-generic
Lm-sensors  versions: 1:3.3.4-2ubuntu1

The output of  sensors-detect: 
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# System: ASUS All Series
# Board: ASUSTeK COMPUTER INC. Z87-K
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
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... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
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'... Yes
Found unknown chip with ID 0xc803
(logical device B 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-i801' for device 0000:00:1f.3: Intel Lynx Point (PCH)
Module i2c-i801 loaded successfully.
Module i2c-dev loaded successfully.
Next adapter: saa7133[0] (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x2d
Handled by driver `ir_kbd_i2c' (already loaded), chip type `ir_video'
(note: this is probably NOT a sensor chip!)
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'... No
Next adapter: NVIDIA i2c adapter 0 at 1:00.0 (i2c-1)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-2)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA i2c adapter 2 at 1:00.0 (i2c-3)
Do you want to scan it? (yes/NO/selectively): y
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----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)y
Successful!
Monitoring programs won't work until the needed modules are
loaded. You may want to run 'service kmod start'
to load them.
Unloading i2c-dev... OK
Unloading i2c-i801... OK
Unloading cpuid... OK
sudo modprobe i2c-dev
sudo modprobe i2c-i801
sudo modprobe cpuid
The output of  sensors: 
acpitz-virtual-0
Adapter: Virtual device
temp1: +27.8°C (crit = +105.0°C)
temp2: +29.8°C (crit = +105.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +42.0°C (high = +80.0°C, crit = +100.0°C)
Core 0: +39.0°C (high = +80.0°C, crit = +100.0°C)
Core 1: +40.0°C (high = +80.0°C, crit = +100.0°C)
Core 2: +37.0°C (high = +80.0°C, crit = +100.0°C)
Core 3: +42.0°C (high = +80.0°C, crit = +100.0°C)
As I understand it, this is not correct, because no CPU voltage and fan speed.

The output of  pwmconfig: 
# pwmconfig revision 6166 (2013-05-01)
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.
We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.
/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed
The output of lsmod:
Module Size Used by
pppoe 17873 2 
pppox 13342 1 pppoe
zl10353 17835 0 
saa7134_dvb 34722 0 
videobuf_dvb 14092 1 saa7134_dvb
dvb_core 121659 1 videobuf_dvb
saa7134_alsa 18486 1 
rc_behold 12499 0 
ir_kbd_i2c 13167 0 
rfcomm 69160 0 
bnep 19624 2 
bluetooth 395423 10 bnep,rfcomm
ip6t_REJECT 12939 1 
xt_hl 12521 6 
ip6t_rt 13537 3 
nf_conntrack_ipv6 18894 8 
nf_defrag_ipv6 34768 1 nf_conntrack_ipv6
ipt_REJECT 12541 1 
xt_LOG 17717 10 
xt_limit 12711 13 
xt_tcpudp 12884 18 
xt_addrtype 12635 4 
nf_conntrack_ipv4 15012 8 
nf_defrag_ipv4 12758 1 nf_conntrack_ipv4
xt_conntrack 12760 16 
ip6table_filter 12815 1 
ip6_tables 27025 1 ip6table_filter
nf_conntrack_netbios_ns 12665 0 
nf_conntrack_broadcast 12589 1 nf_conntrack_netbios_ns
nf_nat_ftp 12770 0 
nf_nat 21798 1 nf_nat_ftp
nf_conntrack_ftp 18638 1 nf_nat_ftp
xc5000 22799 1 
nf_conntrack 96976 8 nf_nat_ftp,nf_conntrack_netbios_ns,nf_nat,xt_conntrack,nf_conntrack_broadcast,nf_conntrack_ftp,nf_conntrack_ipv4,nf_conntrack_ipv6
iptable_filter 12810 1 
ip_tables 27239 1 iptable_filter
x_tables 34059 13 ip6table_filter,xt_hl,ip_tables,xt_tcpudp,xt_limit,xt_conntrack,xt_LOG,iptable_filter,ip6t_rt,ipt_REJECT,ip6_tables,xt_addrtype,ip6t_REJECT
tuner 27308 1 
joydev 17381 0 
eeepc_wmi 13151 0 
asus_wmi 24191 1 eeepc_wmi
sparse_keymap 13948 1 asus_wmi
snd_virtuoso 45131 2 
snd_oxygen_lib 41287 1 snd_virtuoso
snd_mpu401_uart 14169 1 snd_oxygen_lib
snd_pcm 102099 2 snd_oxygen_lib,saa7134_alsa
dm_multipath 22873 0 
x86_pkg_temp_thermal 14205 0 
scsi_dh 14882 1 dm_multipath
intel_powerclamp 14705 0 
snd_page_alloc 18710 1 snd_pcm
snd_seq_midi 13324 0 
snd_seq_midi_event 14899 1 snd_seq_midi
kvm_intel 143060 0 
snd_rawmidi 30144 2 snd_mpu401_uart,snd_seq_midi
kvm 451511 1 kvm_intel
crct10dif_pclmul 14289 0 
crc32_pclmul 13113 0 
ghash_clmulni_intel 13216 0 
snd_seq 61560 2 snd_seq_midi_event,snd_seq_midi
aesni_intel 55624 0 
aes_x86_64 17131 1 aesni_intel
lrw 13286 1 aesni_intel
snd_seq_device 14497 3 snd_seq,snd_rawmidi,snd_seq_midi
gf128mul 14951 1 lrw
snd_timer 29482 2 snd_pcm,snd_seq
nvidia 10675249 50 
saa7134 184899 2 saa7134_dvb,saa7134_alsa
glue_helper 13990 1 aesni_intel
ablk_helper 13597 1 aesni_intel
cryptd 20359 3 ghash_clmulni_intel,aesni_intel,ablk_helper
snd 69238 16 snd_timer,snd_pcm,snd_seq,snd_rawmidi,snd_virtuoso,snd_oxygen_lib,snd_mpu401_uart,snd_seq_device,saa7134_alsa,snd_seq_midi
tveeprom 21216 1 saa7134
videobuf_dma_sg 19262 3 saa7134_dvb,saa7134,saa7134_alsa
serio_raw 13462 0 
rc_core 28124 4 saa7134,ir_kbd_i2c,rc_behold
v4l2_common 15681 2 tuner,saa7134
videobuf_core 26023 3 videobuf_dma_sg,saa7134,videobuf_dvb
videodev 134688 3 tuner,saa7134,v4l2_common
drm 302817 2 nvidia
soundcore 12680 1 snd
mei_me 18627 0 
mei 82276 1 mei_me
lpc_ich 21080 0 
video 19476 1 asus_wmi
mac_hid 13205 0 
wmi 19177 1 asus_wmi
parport_pc 32701 0 
ppdev 17671 0 
coretemp 13435 0 
lp 17759 0 
parport 42348 3 lp,ppdev,parport_pc
usb_storage 62209 0 
hid_generic 12548 0 
usbhid 52570 1 
hid 106148 2 hid_generic,usbhid
psmouse 102222 0 
ahci 25819 3 
libahci 32168 1 ahci
r8169 67581 0 
mii 13934 1 r8169
dm_mirror 22135 0 
dm_region_hash 20862 1 dm_mirror
dm_log 18411 2 dm_region_hash,dm_mirror
The output of lspci -nn:
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06)
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 04)
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d4)
00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 [8086:8c14] (rev d4)
00:1c.3 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev d4)
00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 04)
00:1f.0 ISA bridge [0601]: Intel Corporation Z87 Express LPC Controller [8086:8c44] (rev 04)
00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c02] (rev 04)
00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 04)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2)
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 11)
04:00.0 PCI bridge [0604]: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge [1b21:1080] (rev 03)
05:01.0 Multimedia audio controller [0401]: C-Media Electronics Inc CMI8788 [Oxygen HD Audio] [13f6:8788]
05:02.0 Multimedia controller [0480]: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder [1131:7133] (rev d1)
The output of i2cdetect:
Error: No i2c-bus specified!
Usage: i2cdetect [-y] [-a] [-q|-r] I2CBUS [FIRST LAST]
i2cdetect -F I2CBUS
i2cdetect -l
I2CBUS is an integer or an I2C bus name
If provided, FIRST and LAST limit the probing range.
What content should have a file /etc/sensors3.conf for chipset Z87?

PS run with GRUB_CMDLINE_LINUX = "acpi_enforce_resources = lax" and GRUB_CMDLINE_LINUX = "acpi_enforce_resources = auto" tried, unsuccessfully.
_______________________________________________
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