Re: Issues with gkrellm-uguru and gkrellm-hddtemp

Bill,

Wahoo!!!!!!!  Thanks for the pointer on the scaling factor. I now have full
readings for my board! I'd already applied appropriate labels to everything
based on those in the /sys/hwmon/.../*_label files. What I was suggesting in
my last message was that gkrellm use the contents of the label files to
populate the labels it displays. The one downside I can see to this would be
that the labels in those files are not the shortest. In applying them to my
gkrellm I was forced to widen the display.  :-(  I'll have to come up with
usefull contractions of them. Maybe I'll dig into Han's code and apply the
temperature scaling there and feed the resulting code back to the community.

Thanks for all your help in getting this working.

Regards,
Steven

On 8/12/06, Bill WIlson <[email protected]> wrote:
>
> On Sat, 12 Aug 2006 22:01:38 -0600
> "Steven Collins" <[email protected]> wrote:
>
> >  Readings for fans look good, but I have
> > questions about temps and voltages. Gkrellm is reporting the same
> voltages
> > as looking directly at the /sys/class/hwmon files, so most likely any
> > questions I have relating to those readings need to go to Hans. The
> > temperature readings on the other hand do not. I've attached the debug
> from
> > my most recent run and it should show you that gkrellm is reporting 0
> for
> > the temperature readings. At the same time this instance of gkrellm was
> > running, a cat of the temperature input files in the abituguru2 hwmon
> > devices produced:
> >
> > temp1_input: 33
> > temp2_input: 32
> > temp3_input: 36
>
> The raw temperature values are supposed to be scaled by 1000 and
> uguru not doing this makes it different from all other sensor drivers
> I've seen.  You can compensate for now by putting in a 1000 factor
> for your temps in the gkrellm config.  Maybe this will change in a
> future uguru release so it's something to keep an eye on.
> For example, it's typical to get /sys temp files having something like:
>
> temp1_input: 40000
> temp2_input: 40500
> temp3_input: 41000
>
> This should all be taken care of for us once the lm_sensors
> library knows about the device and we won't need to be
> concerned about factors.
>
> And your voltage labels (and values derived from factors/offsets)
> are off because gkrellm (ie me) doesn't know the details of the
> conversion formulas and labels since it's a new driver.  This also
> should be taken care of with an updated lm_sensors lib.
> In the meantime, you'll have to setup voltage labels and I'll
> need to get some default labels setup in gkrellm.  I need to
> look some more at the voltage factor/offset stuff before I'll know
> what values should be right.
>
> So, yeah, it seems it's all working... aside from some fouled up label
> and factor defaults :(
>
> Bill
> _______________________________________________
> Gkrellm mailing list
> [email protected]
> http://lists.jutley.org/cgi-bin/mailman/listinfo/gkrellm
>

_______________________________________________
Gkrellm mailing list
[email protected]
http://lists.jutley.org/cgi-bin/mailman/listinfo/gkrellm