From: Hans de Goede <hdegoede@redhat.com>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Problem with:
Date: Mon, 15 Dec 2008 12:51:13 +0000 [thread overview]
Message-ID: <494652C1.8060506@redhat.com> (raw)
Hi Jean,
I just realised there is an issue with the
hwmon-f71882fg-11-separate-max-crit-alarm-and-beep.patch
patch.
It removes the temp#_alarm attributes (replacing them by temp#_max_alarm),
which is fine for lm_sensors v3, but will cause a problem with lm_sensors v2,
the "sensors" command from lm_sensors v2 will now give failed to read data for
temp# for all 3 temps :(
So it looks like we are sorta stuck with our past mistake of not doing separate
alarms.
We could do separate alarms like this:
temp#_alarm
temp#_crit_alarm
This will work with both libsensors and with "sensors" from both v2 and v3.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next reply other threads:[~2008-12-15 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 12:51 Hans de Goede [this message]
2008-12-15 13:24 ` [lm-sensors] Problem with: Jean Delvare
2008-12-16 10:07 ` Jean Delvare
2008-12-16 13:40 ` Hans de Goede
2008-12-16 14:57 ` Jean Delvare
2008-12-16 15:10 ` Hans de Goede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=494652C1.8060506@redhat.com \
--to=hdegoede@redhat.com \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.