Re: Some voltage readings, off & low when they are not
Gene Heskett <[email protected]>
| Newsgroups | gmane.comp.gnome.apps.gkrellm |
|---|---|
| Organization | Organization? Not detectable |
| Message-ID | <[email protected]> |
On Saturday 26 January 2008, Bill Wilson wrote: >On Sat, 26 Jan 2008 14:51:17 -0500 > >Gene Heskett <[email protected]> wrote: >> I just called and arranged for another psu for this box as the gkrellm is >> saying the +5 volt line is running in the 4.6-4.7 range, and the -5 volts >> is showing at about -3.5. >> >> Sticking a good digital meter in the end of a long chain of drive >> connectors, (this box has a bunch of extra stuff in it, and a 400Watt >> HiPro supply about 3 months old) I'm getting a stable reading of 4.98 >> volts. Getting at the -5 line is difficult, the board connector is on the >> other side of a drive cage with 3 drives in it, so I have NDI what it >> actually is. >> >> The ability to adjust the scales and offsets in the voltage config display >> is greyed out, so how does one go about this? >> >> An lsof says it is using libsensors.so.3.1.4. There are a couple of >> gkrellm files in the sysconfig tree, but test edits of those and a restart >> (why doesn't sending it a SIGHUP work?, it dies instead) doesn't change >> the display at all. >> >> The chipset is nforce2, w-83627hf. > >When libsensors is used the scaling/offset stuff is taken from the > /etc/sensors.conf file and you should find and edit the w83627hf section in > that file. But with libsensors4 I think the config file becomes > /etc/sensors3.conf. The version numbers are confusing and I don't if your > libsensors.so.3.1.4 means you have libsensors3 or libsensor4. > >Anyway for your 5 volt supply edit the w83627hf compute line for "in3" in > /etc/sensors.conf or /etc/sensors3.conf ... or maybe both! > I only have /etc/sensors.conf. I edited that and the response from the sensors command was instant. I restarted lm_sensors, and gkrellm's display went to all zero's for a couple of refresh cycles, then went back to the old, low values. But, a restart on gkrellm seems to have worked. Which set of stuff in the sensors.conf do I edit to set the alarm levels, they are generally pretty fubar: [root@coyote ~]# sensors w83627hf-isa-0290 Adapter: ISA adapter VCore 1: +1.68 V (min = +1.44 V, max = +1.86 V) VCore 2: +1.50 V (min = +1.44 V, max = +1.86 V) +3.3V: +3.31 V (min = +2.82 V, max = +3.79 V) +5V: +5.01 V (min = +2.34 V, max = +3.32 V) ALARM +12V: +12.16 V (min = +0.79 V, max = +6.81 V) ALARM -12V: -12.69 V (min = -14.83 V, max = -14.91 V) ALARM -5V: +4.98 V (min = +1.86 V, max = +3.79 V) ALARM V5SB: +5.64 V (min = +4.41 V, max = +6.59 V) VBat: +3.14 V (min = +0.00 V, max = +0.27 V) ALARM fan1: 1654 RPM (min = 1298 RPM, div = 16) fan2: 2721 RPM (min = 474 RPM, div = 16) fan3: 0 RPM (min = 2636 RPM, div = 16) ALARM temp1: -48°C (high = -126°C, hyst = +47°C) sensor = thermistor temp2: +50.5°C (high = +120°C, hyst = +115°C) sensor = thermistor temp3: +49.5°C (high = +120°C, hyst = +115°C) sensor = thermistor vid: +1.650 V (VRM Version 9.0) alarms: beep_enable: Sound alarm enabled >Yeah, gkrellm doesn't do anything with SIGHUP, something to look at. > >Bill > As is the ups stuff, which I finally had to turn off as the answers were totally bogus, if it gave any at all. With a new F8 install all up to date, I haven't yet installed apcupsd, which worked only moderately well with my Belkin supply, but it would at east make the system do a semi-gracefull shutdown. This time I think I'll try nut & see how well it deals with a Belkin. At least there are rpms for it. Thanks Bill. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) fortune: No such file or directory ______________________________________________ Gkrellm mailing list [email protected] Read archives-join-leave-set RSS feed: http://archive.lists.netservicesgroup.com