Stephen Boddy wrote:
On Saturday 09 September 2006 07:08, Basil Chupin wrote:
For the first time since starting to use Linux, I decided that I will go really high tech and start using lm_sensors on SUSE 10.1.
I used the /usr/sbin/sensors- detect command and let it find them and then "do its thing" to create the lm_sensors configuration file. Because it was time for me to go biddie-byes I didn't reboot but shut the system down and went to bed.
This morning I booted-up the system and suddenly I was hit by a very high pitched sound coming from the computer. Ear-splitting it was :-( and to me this is a no-no 'cause I suffer from tinnitus.
Took a while to pinpoint the sound as coming from the rheostat on the (front) panel which controls the speed of the Gigabyte CPU heatsink fan.
There was not a murmur when I booted into the "other" OS so it was something in SUSE. Finally[0] dawned on me that the only thing that changed between "no noise" and "hight-pitched noise" was the creation of the lm_sensors file in /etc/sysconfig. I renamed lm_sensors file, rebooted and the sound vanished.
So, if you configure lm_sensors and suddenly find that there is a very high-pitched sound coming from the innards of your computer case then you now know what you can try and do to get rid of it.
[0] I have another rheostat on another (front) panel which controls the speed of the PSU and case fans which occasionally makes a similar noise if the speed of the case fans drops too low, and just gently tapping the control knob gets rid of the noise. My initial reaction to the above was that it was this that was causing the high-pitched sound.
This may sound like an silly question, but is it possible it's an alarm?
I've always found the lm_sensors stuff a bit hit and miss for detecting and setting things properly, like putting odd values in for alarm conditions.
Not understanding the detail of how it works, it may be seeing something it doesn't like and generating an audible alarm.
[pruned]
As you can see, after a quick detect and init, I've got crazy values in some fields, and alarms up the kazoo. Note also the beep_enable at the end. I guess if that was wired up properly I'd be being annoyed right now by a high pitched noise ;-)
Only problem with this is that lm_sensors application was not actually activated :-) . All I had in place was the lm_sensors file created by /usr/sbin/sensors-detect. Unless of course in SUSE 10.1 the lm_sensors are activated automatically once the lm_sensors file is created in /etc/sysconfig. Dunno. Actually..... I just had a look at the lm_sensors file and I think lm_sensors may be activated should the lm_sensors file exist in /etc/sysconfig which may go against what Joe Morris mentioned in an earlier message. But then I am stating this from a very cursory look at what is shown in lm_sensors file. BTW, here are the parameters which sensors-detect put into the lm_sensors file when it created it: # Generated by sensors-detect on Sat Sep 9 01:07:41 2006 MODULE_0=i2c-nforce2 MODULE_1=i2c-isa MODULE_2=eeprom MODULE_3=it87 Cheers. -- This computer is environment-friendly and is running on OpenSuSE 10.1