Ksensors Issue

[BeepBeep]

Running Jaunty 64 bit on an Intel DG35EC mobo. The install is not an upgrade but a clean full install from CD.

I have run sudo sensors-detect and modprobed the detected sensors. Also auto pasted the details into /etc/modules.

When I run Ksensors info from both sensors that were detected plus the HDD info is displayed correctly.

However, when I reboot the system, Ksensors just shows the default readings and none from the detected sensors. If I run sensors-detect again Ksensors shows the values from the detected sensors.

Am I missing something that would ensure Ksensors functions with the detected sensors each and every time?

[Detonate]

Re: Ksensors Issue

Did you check your /etc/modules file to make sure the info from sensors-detect got posted there?

[BeepBeep]

Re: Ksensors Issue

Did you check your /etc/modules file to make sure the info from sensors-detect got posted there?

Yes the output from sensors-detect run process is written into the /etc/modules file.

[Detonate]

Re: Ksensors Issue

Is lm-sensors listed in the /etc/init.d file?

[BeepBeep]

Re: Ksensors Issue

Is lm-sensors listed in the /etc/init.d file?

Yes, it is listed.

Also running command "sensors" gives following:

jim@home:~$ sensors
w83627dhg-isa-06e0
Adapter: ISA adapter
VCore: +0.81 V (min = +0.00 V, max = +1.74 V)
in1: +9.87 V (min = +3.59 V, max = +0.16 V) ALARM
AVCC: +3.04 V (min = +0.26 V, max = +0.40 V) ALARM
3VCC: +3.04 V (min = +0.40 V, max = +2.18 V) ALARM
in4: +0.94 V (min = +0.58 V, max = +0.51 V) ALARM
in5: +1.34 V (min = +0.01 V, max = +0.06 V) ALARM
in6: +1.28 V (min = +0.20 V, max = +0.82 V) ALARM
VSB: +3.04 V (min = +0.48 V, max = +2.27 V) ALARM
VBAT: +2.96 V (min = +1.95 V, max = +0.56 V) ALARM
Case Fan: 0 RPM (min = 585 RPM, div = 128) ALARM
CPU Fan: 1875 RPM (min = 2636 RPM, div = 16) ALARM
Aux Fan: 0 RPM (min = 351 RPM, div = 128) ALARM
fan4: 0 RPM (min = 2636 RPM, div = 128) ALARM
Sys Temp: +51.0°C (high = +17.0°C, hyst = -44.0°C) ALARM sensor = diode
CPU Temp: +72.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
AUX Temp: -128.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
cpu0_vid: +2.050 V

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +51.0°C (high = +78.0°C, crit = +100.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +51.0°C (high = +78.0°C, crit = +100.0°C)

[Detonate]

Re: Ksensors Issue

Lm-sensors is obviously working, so the problem must be with ksensors. I don't use ksensors, and I don't have kde installed on this desktop, so I'm hoping someone else will jump in now.

[BeepBeep]

Re: Ksensors Issue

Lm-sensors is obviously working, so the problem must be with ksensors. I don't use ksensors, and I don't have kde installed on this desktop, so I'm hoping someone else will jump in now.

Thanks, appreciate the input.

[dibl]

Re: Ksensors Issue

I'm still a bit skeptical ....

@BeepBeep, you say when you boot, sensors appear not to be working. I'd like to see you do a reboot, and as soon as you are logged in, and before doing anything else, run

lsmod

in the Konsole and then open your browser and post the output here. I just want to see whether the modules are really loading at boot time.

[BeepBeep]

Re: Ksensors Issue

I'm still a bit skeptical ....

@BeepBeep, you say when you boot, sensors appear not to be working. I'd like to see you do a reboot, and as soon as you are logged in, and before doing anything else, run

lsmod

in the Konsole and then open your browser and post the output here. I just want to see whether the modules are really loading at boot time.

Module Size Used by
i915 75272 2
drm 123232 3 i915
ppdev 16904 0
bridge 63904 0
stp 11140 1 bridge
bnep 22912 2
vboxnetflt 110316 0
vboxdrv 1704748 1 vboxnetflt
video 29204 0
output 11648 1 video
input_polldev 12688 0
coretemp 15360 0
w83627ehf 32272 0
hwmon_vid 12160 1 w83627ehf
lp 19588 0
parport 49584 2 ppdev,lp
snd_hda_intel 557364 3
snd_pcm_oss 52352 0
snd_mixer_oss 24960 1 snd_pcm_oss
snd_pcm 99336 2 snd_hda_intel,snd_pcm_oss
snd_seq_dummy 11524 0
snd_seq_oss 41984 0
snd_seq_midi 15744 0
snd_rawmidi 33920 1 snd_seq_midi
snd_seq_midi_event 16512 2 snd_seq_oss,snd_seq_midi
gspca_spca501 23680 0
gspca_main 34560 1 gspca_spca501
snd_seq 66272 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
iTCO_wdt 21712 0
snd_timer 34064 2 snd_pcm,snd_seq
snd_seq_device 16276 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
psmouse 64028 0
compat_ioctl32 18304 1 gspca_main
videodev 45184 2 gspca_main,compat_ioctl32
v4l1_compat 23940 1 videodev
iTCO_vendor_support 12420 1 iTCO_wdt
pcspkr 11136 0
serio_raw 14468 0
snd 78792 15 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,sn d_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_de vice
soundcore 16800 1 snd
snd_page_alloc 18704 2 snd_hda_intel,snd_pcm
intel_agp 39408 1
ohci1394 42036 0
ieee1394 108288 1 ohci1394
e1000e 137392 0
fbcon 49792 0
tileblit 11264 1 fbcon
font 17024 1 fbcon
bitblit 14464 1 fbcon
softcursor 10368 1 bitblit
compcache 13808 1
lzo_decompress 11264 1 compcache
lzo_compress 11264 1 compcache
tlsf 15392 1 compcache

[dibl]

Re: Ksensors Issue

coretemp 15360 0
w83627ehf 32272 0
hwmon_vid 12160 1 w83627ehf

OK, now I believe!

Honestly, this looks a lot like a bug in Ksensors. I'd advise posting the information on launchpad -- I'm convinced that the modules are loaded at boot, and Ksensors is not collecting the metrics from them.

You could also google around with those module names and see if there is information about issues with them.

[BeepBeep]

Re: Ksensors Issue

OK, now I believe!

Honestly, this looks a lot like a bug in Ksensors. I'd advise posting the information on launchpad -- I'm convinced that the modules are loaded at boot, and Ksensors is not collecting the metrics from them.

You could also google around with those module names and see if there is information about issues with them.

Would appreciate you pointing me in the direction of "launchpad" so I could post there.

Thanks!

[dibl]

Re: Ksensors Issue

Sure -- start here:

https://launchpad.net/ubuntu

See the "File a Bug" button -- press that. You'll have to review the instructions -- it's been awhile since I filed one. I think you'll have to sign up with your name and e-mail address, so they can let you know how the bug is handled.

[Qqmike]

Re: Ksensors Issue

You might try the ksensors site, see if there's any nuances with your board. I know the lm-sensors site is excellent for reporting such, in FAQ and mail list.
http://ksensors.sourceforge.net/
http://www.lm-sensors.org/

[BeepBeep]

Re: Ksensors Issue

Thanks for the info. I reported it to the developer of the SW.

Shall post if I hear from him.