Hello,
For production environment, You may give a try to mosquitto package and
to industrial modules which support mqtt 3.1 or 3.1.1. As far as i
remember there's some which support standard rtd sensor like pt100/pt1000
and publish their data over wifi or ethernet. (Try adam 6015 series for
exampl
On Fri, Nov 14, 2014 at 06:27:10PM +, Etienne wrote:
> [...]
> ("93C" is just a typical value, I've seen any between 92 and 98). I
> usually have just the time to log in before the system logs me out and
> shuts down. This laptop normally runs at around 80??C, and I think the
> temperature read
On 2014-11-14 19:59, patrick keshishian wrote:
As I say, I never have had this issue with x120e, which I've
been using for over 3 years with OpenBSD, mainly following
snapshots.
Thanks for the info. Clearly, I need to open the beast for inspection.
Cheers!
--
Étienne
On 11/14/14, Mike Larkin wrote:
> On Fri, Nov 14, 2014 at 11:59:26AM -0800, patrick keshishian wrote:
>> Hi,
>>
>> On 11/14/14, Etienne wrote:
>> > Hello list,
>> >
>> > I seem to have a little hardware related problem. I have been using a
>> > Lenovo x120e for some time, and OpenBSD ran nicely o
On Fri, Nov 14, 2014 at 11:59:26AM -0800, patrick keshishian wrote:
> Hi,
>
> On 11/14/14, Etienne wrote:
> > Hello list,
> >
> > I seem to have a little hardware related problem. I have been using a
> > Lenovo x120e for some time, and OpenBSD ran nicely on it until April. As
> > soon as I upgrad
Hi,
On 11/14/14, Etienne wrote:
> Hello list,
>
> I seem to have a little hardware related problem. I have been using a
> Lenovo x120e for some time, and OpenBSD ran nicely on it until April. As
> soon as I upgraded to 5.5, and from quite early after kernel loading,
> the console started showing
On 2014-11-14 18:56, Gregor Best wrote:
("93C" is just a typical value, I've seen any between 92 and 98). I
usually have just the time to log in before the system logs me out and
shuts down. This laptop normally runs at around 80??C, and I think the
temperature reading in OpenBSD is correct, bec
Did a fan die? Or are you blocking the vent somehow?
I killed a laptop like that once by putting it on my lap. Turned out the
fan vent was on the bottom and the laptop needed to be on a flat surface.
Usually called a desk. So I don't know why it was classified as a laptop.
:)
Tim.
On 2014-11-14 18:27, Etienne wrote:
Hello list,
Sorry for answering to myself, that was my first post and I didn't
expect the attachements to be concatenated after my message. Please let
me reformat:
x100e# dmesg
OpenBSD 5.6 (GENERIC.MP) #333: Fri Aug 8 00:20:21 MDT 2014
dera...@amd64
Etienne wrote:
> Hello list,
>
> I seem to have a little hardware related problem. I have been using a
> Lenovo x120e for some time, and OpenBSD ran nicely on it until April. As
> soon as I upgraded to 5.5, and from quite early after kernel loading,
> the console started showing and repeating at
On 11/14/14 13:27, Etienne wrote:
Hello list,
I seem to have a little hardware related problem. I have been using a
Lenovo x120e for some time, and OpenBSD ran nicely on it until April. As
soon as I upgraded to 5.5, and from quite early after kernel loading,
the console started showing and repea
On 2006/01/16 22:27, Ricardo Lucas wrote:
> Look at this, it's look a kind of weird:
You forgot the complete dmesg. In any case, unless you're running
recent -current, reports of sensors problems are probably not very
useful at the moment.
On 2006/01/16 22:45, Ricardo Lucas wrote:
> And when I tr
Here is my dmesg:
OpenBSD 3.8 (GENERIC) #138: Sat Sep 10 15:41:37 MDT 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD-K6(tm) 3D processor ("AuthenticAMD" 586-class) 494 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX
real mem = 200908800 (196200K)
avail mem = 17644748
On Mon, 16 Jan 2006, Ricardo Lucas wrote:
> Any ideias?
we can't help you without a dmesg.
-d
And when I try atactl:
# atactl wd0c readattr
Attributes table revision: 4
ID Attribute name Threshold Value Raw
1 Raw Read Error Rate 102253
0x
2 Throughput Performance 127253
0x
3
Look at this, it's look a kind of weird:
hw.sensors.0=lm0, IN0, volts_dc, 2.26 V
hw.sensors.1=lm0, IN1, volts_dc, 3.94 V
hw.sensors.2=lm0, IN2, volts_dc, 2.93 V
hw.sensors.3=lm0, IN3, volts_dc, 4.67 V
hw.sensors.4=lm0, IN4, volts_dc, 0.00 V
hw.sensors.5=lm0, IN5, volts_dc, 0.00 V
hw.sensors.6=lm0
Hi,
I put together a script last week, for now i run it every hour in cron to see
how/if temperature vaies over time. I don't have any usable sensors on my mobo.
DISKS="0 1 2 3"
S=`date +"%b %e %H:%M:%S "`
for d in $DISKS; do
TEMP=`atactl wd$d readattr |grep Temp |cut -f 4`
S="$
On Sun, 15 Jan 2006, Ricardo Lucas wrote:
> Hello misc,
> anyone knows a program that monitoring the cpu temperature and hard disk
> temperature and rotation?!
There has been a lot of hardware monitoring work that has been happening
in -current recently. Grab a snapshot and try it out - the resul
On 1/15/06, Pete Vickers <[EMAIL PROTECTED]> wrote:
> While we're on this subject, what about adding something like "
> sysctl -w | grep hw.sensor" to /etc/daily ? I'd consider the output
> of such to be as useful as the status of disk space etc.
If you're concerned about temperature readings and
Hi,
While we're on this subject, what about adding something like "
sysctl -w | grep hw.sensor" to /etc/daily ? I'd consider the output
of such to be as useful as the status of disk space etc.
/Pete
On 15. jan. 2006, at 16.25, Stuart Henderson wrote:
On 2006/01/15 13:05, Ricardo Lucas w
On 2006/01/15 13:05, Ricardo Lucas wrote:
> anyone knows a program that monitoring the cpu temperature
> and hard disk temperature
sysctl(8) (hw.sensors tree) is the natural place for this information,
you can be alerted if it exceeds parameters with sensorsd(8). Sensors
for many motherboards and
21 matches
Mail list logo
