On Thu, Nov 21, 2013 at 12:51:02AM -0800, jonathan stewart wrote: > > # sensors-detect revision 6031 (2012-03-07 17:14:01 +0100) > # Board: Micro-Star International Co., Ltd. MS-1761 > > 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... No > AMD Family 15h thermal sensors... No > AMD Family 15h 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): 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-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH) > Module i2c-i801 loaded successfully. > Module i2c-dev loaded successfully. > > Next adapter: NVIDIA i2c adapter 0 at 1:00.0 (i2c-0) > Do you want to scan it? (YES/no/selectively): yes > > Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-1) > 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: NVIDIA i2c adapter 2 at 1:00.0 (i2c-2) > Do you want to scan it? (YES/no/selectively): yes > > Next adapter: NVIDIA i2c adapter 3 at 1:00.0 (i2c-3) > Do you want to scan it? (YES/no/selectively): yes > > Next adapter: NVIDIA i2c adapter 5 at 1:00.0 (i2c-4) > Do you want to scan it? (YES/no/selectively): yes > > Next adapter: NVIDIA i2c adapter 8 at 1:00.0 (i2c-5) > 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 `coretemp': > * Chip `Intel digital thermal sensor' (confidence: 9) > > Module Size Used by > snd_hda_codec_hdmi 36906 4 > coretemp 13355 0 > kvm_intel 132891 0 > kvm 443165 1 kvm_intel > ghash_clmulni_intel 13259 0 > aesni_intel 55399 1 > aes_x86_64 17255 1 aesni_intel > xts 12885 1 aesni_intel > lrw 13257 1 aesni_intel > gf128mul 14951 2 lrw,xts > ablk_helper 13597 1 aesni_intel > cryptd 20373 3 ghash_clmulni_intel,aesni_intel,ablk_helper > nvidia 11309139 43 > arc4 12615 2 > snd_hda_codec_realtek 78399 1 > ath9k 149924 0 > ath9k_common 14055 1 ath9k > snd_hda_intel 39619 5 > ath9k_hw 413629 2 ath9k_common,ath9k > snd_hda_codec 136498 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel > ath 23827 3 ath9k_common,ath9k,ath9k_hw > snd_hwdep 13602 1 snd_hda_codec > snd_pcm 97451 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel > mac80211 606457 1 ath9k > rts5139 352481 0 > snd_page_alloc 18710 2 snd_pcm,snd_hda_intel > snd_seq_midi 13324 0 > snd_seq_midi_event 14899 1 snd_seq_midi > snd_rawmidi 30180 1 snd_seq_midi > microcode 22881 0 > snd_seq 61554 2 snd_seq_midi_event,snd_seq_midi > cfg80211 511019 3 ath,ath9k,mac80211 > joydev 17377 0 > psmouse 95905 0 > serio_raw 13215 0 > snd_seq_device 14497 3 snd_seq,snd_rawmidi,snd_seq_midi > snd_timer 29425 2 snd_pcm,snd_seq > lpc_ich 17061 0 > mei 41158 0 > snd 68876 20 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device > soundcore 12680 1 snd > mxm_wmi 13021 0 > parport_pc 28152 0 > bnep 18036 2 > ppdev 17073 0 > rfcomm 42641 0 > bluetooth 228808 10 bnep,rfcomm > binfmt_misc 17500 1 > dm_multipath 22843 0 > scsi_dh 14843 1 dm_multipath > wmi 19070 1 mxm_wmi > video 19390 0 > mac_hid 13205 0 > lp 17759 0 > parport 46345 3 lp,ppdev,parport_pc > hid_generic 12540 0 > usbhid 47074 0 > hid 101042 2 hid_generic,usbhid > dm_raid45 76725 0 > r8169 67466 0 > ahci 25731 2 > libahci 31364 1 ahci > xor 17116 1 dm_raid45 > dm_mirror 21946 0 > dm_region_hash 20820 1 dm_mirror > dm_log 18529 3 dm_region_hash,dm_mirror,dm_raid45 > > > > it is a laptop, its from xoticpc.com its a force1761 based on the msi gt790dxr it has an i7-2670qm, 4gb patriot ddr3 1600mhz, nvidia gtx570m, corsair performance pro 128gb ssd, 750gb seagate 7200 rpm hdd (? on actual speed but its not the 5k version), and a dvd burner > > it says in synaptic > > > "Lm-sensors is a hardware health monitoring package for Linux. It allows you > to access information from temperature, voltage, and fan speed sensors. It > works with most newer systems. > > This package contains a daemon that calculates fan speeds from temperatures > and sets the corresponding PWM outputs to the computed values." > > > so i am curious on how to adjust the calculations because at them moment my fan does not increase in rpm enough to keep itself cool. if i am playing minecraft on a public server with 200+ people the cpu temps will hit 90C+ and sometimes it crashes my game. i have the same issue with left4dead2 only it begins lagging bad and will start temporarily disconnecting me from steam. if i hit a button above my keyboard it forces the fan to 100% which then cools it down and stops my lagging but also prevents me from using my mic for voip as the fan is loud and sounds like a blow dryer. after i downloaded/installed the fansensors thing from synaptic my minecraft temps dropped to upper 80C's which is better but i would like it to be in the 60's or 70's which i know its capable of if the fan would just turn on so it will stay moderatly cool and not cook itself. > Interesting; based on the information you provided I would have assumed that fan control is not available in your system. Did you run the 'pwmconfig' script ? If so, what did it report ? Also, can you provide output from the 'sensors' command ? Thanks, Guenter > sorry if this still isnt enough information i am good at building pc's and judging their performance but i've just started learning about the software/os side of things > > > > > On Wednesday, November 20, 2013 5:02 PM, Guenter Roeck <linux@xxxxxxxxxxxx> wrote: > > On Wed, Nov 20, 2013 at 01:05:12PM -0800, jonathan stewart wrote: > > > i have downloaded/installed the lm sensors (and related packages) and fancontrol through the synaptic package manager. i was wondering if you could tell me how to adjust the fan speed. i am using ubuntu 13.04 64bit and i only ask because my temps get up to the low 90C's and my fan doesnt spin up much. i have a button that sets fan speed at 100% then temps drop to 50C's but its way to noisy. sorry if this is confusing i'm not entirely sure on how to state my problem. > > _______________________________________________ > > Hi, > > you do not really provide enough information to enable us to help. > Output from "sensors" command might be helpful, as well as > some more information about your hardware. > PC ? Laptop ? CPU type ? Super-IO chip ? fancontrol configuration ? > > Guenter _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
