paulisdead Guru
Joined: 10 Apr 2002 Posts: 510 Location: Seattle, WA
|
Posted: Wed Mar 23, 2005 7:47 pm Post subject: any way to get right sensors readings w/ neo4 sli? |
|
|
I've got everything working really well with this mobo, except for lm_sensors. I've got the modules loaded Code: | Module Size Used by
snd_seq_midi 9664 0
snd_emu10k1_synth 8256 0
snd_emux_synth 40256 1 snd_emu10k1_synth
snd_seq_virmidi 8576 1 snd_emux_synth
snd_seq_midi_emul 8832 1 snd_emux_synth
snd_ioctl32 28032 0
snd_pcm_oss 56864 0
snd_mixer_oss 20032 1 snd_pcm_oss
snd_seq_oss 36096 0
snd_seq_midi_event 9344 3 snd_seq_midi,snd_seq_virmidi,snd_seq_oss
snd_seq 59008 8 snd_seq_midi,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_oss,snd_seq_midi_event
snd_emu10k1 99428 3 snd_emu10k1_synth
snd_rawmidi 28064 3 snd_seq_midi,snd_seq_virmidi,snd_emu10k1
snd_seq_device 9808 7 snd_seq_midi,snd_emu10k1_synth,snd_emux_synth,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi
snd_ac97_codec 82640 1 snd_emu10k1
snd_pcm 101324 5 snd_ioctl32,snd_pcm_oss,snd_emu10k1,snd_ac97_codec
snd_timer 27272 3 snd_seq,snd_emu10k1,snd_pcm
snd_page_alloc 11080 2 snd_emu10k1,snd_pcm
snd_util_mem 5376 2 snd_emux_synth,snd_emu10k1
snd_hwdep 10976 2 snd_emux_synth,snd_emu10k1
snd 59944 17 snd_emux_synth,snd_seq_virmidi,snd_ioctl32,snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer,snd_hwdep
soundcore 11872 1 snd
it87 28060 0
i2c_nforce2 7744 0
i2c_isa 2688 0
i2c_dev 13056 0
nvidia 4566972 12
eeprom 8848 0
i2c_sensor 3968 2 it87,eeprom
i2c_core 25624 6 it87,i2c_nforce2,i2c_isa,i2c_dev,eeprom,i2c_sensor
usb_storage 36736 0
usbhid 36160 0
ohci_hcd 22600 0
ehci_hcd 33096 0
usbcore 129232 5 usb_storage,usbhid,ohci_hcd,ehci_hcd
sk98lin 195428 1 |
but I get this with sensors Code: | it87-isa-0290
Adapter: ISA adapter
VCore 1: +1.50 V (min = +1.42 V, max = +1.57 V) ALARM
VCore 2: +3.31 V (min = +2.40 V, max = +2.61 V)
+3.3V: +6.24 V (min = +3.14 V, max = +3.46 V)
+5V: +5.03 V (min = +4.76 V, max = +5.24 V)
+12V: +1.86 V (min = +11.39 V, max = +12.61 V)
-12V: -23.56 V (min = -12.63 V, max = -11.41 V)
-5V: -2.35 V (min = -5.26 V, max = -4.77 V)
Stdby: +0.99 V (min = +0.00 V, max = +0.00 V)
VBat: +4.08 V
fan1: 0 RPM (min = 0 RPM, div = 1) ALARM
fan2: 4218 RPM (min = 0 RPM, div = 64) ALARM
fan3: 135000 RPM (min = 2657 RPM, div = 2) ALARM
M/B Temp: -1 C (low = +0 C, high = +40 C) sensor = diode
CPU Temp: +119 C (low = +15 C, high = +0 C) sensor = diode
Temp3: -16 C (low = +15 C, high = +45 C) sensor = diode |
This is clearly very wrong. if fan3 really were spinning at 135000 RPM I could probably make the whole box hover on top of it and fry bacon on my 119C CPU, while keeping my beer cold by resting it on the chipset at -1C
Anyone have any ideas on how to fix this, short of getting something to physically probe the temps and use the offsets in Gkrellm?
*edit* Btw using 2.6.11-gentoo-r4 kernel and lm_sensors 2.9.0. _________________ "we should make it a law that all geeks have dates" - Linus |
|