Date: 12 Jul 2003 21:26:19 -0400 From: "J. Seth Henry" <jshamlet@comcast.net> To: freebsd-hardware@freebsd.org Cc: ruler@darkpact.net Subject: Re: freebsd-hardware Digest, Vol 16, Issue 6 Message-ID: <1058059578.8410.13.camel@alexandria> In-Reply-To: <20030712190105.5092C37B404@hub.freebsd.org> References: <20030712190105.5092C37B404@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I've run into this same problem on my primary app/file server. (I have a dual P3 with the ServerWorks chipset as well) So, I would be interested in getting this to work as well. Although Linux implements this stuff partly in the kernel; in theory, you could write a userland app to read/write the data from the LM78 subsystem - if you knew where it was (which should be easy), what was hooked up, and how it was hooked up. That's the rub on ServerWorks boards. Apparently, they make you sign an NDA before they will give you any details at all. Also, FreeBSD has a lousy track record of supporting LM78 based hardware in general. I have four systems, each with different LM78 monitoring systems, and programs like healthd, etc. can't manage any of them. (they include the file server, a fairly standard Abit P4 system, a VIA EPIA system, and an old K6-2 system) > Hello freebsd-hardware, > > Hi, > > I've been running into a few overheating problems, and finally after > replacing the parts...my system is functional once again. > > Now, I want to be able to monitor CPU/MB/etc temperature, and I > can't really find anything relevant after searching the list, or on > google. Has anyone successfully done this? If so, please share some > info! > > If this is the wrong list, sorry, I was told this is the best place > for this. > > Thank you,
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1058059578.8410.13.camel>