From owner-freebsd-stable Thu Mar 8 15: 5:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from level3.dynacom.net (level3.dynacom.net [206.107.213.213]) by hub.freebsd.org (Postfix) with SMTP id 491FE37B719 for ; Thu, 8 Mar 2001 15:05:26 -0800 (PST) (envelope-from kstewart@urx.com) Received: (qmail 1495 invoked by uid 0); 8 Mar 2001 23:05:24 -0000 Received: from unknown (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 8 Mar 2001 23:05:24 -0000 Message-ID: <3AA81034.B73A84CF@urx.com> Date: Thu, 08 Mar 2001 15:05:24 -0800 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Bert Driehuis Cc: stable@FreeBSD.ORG Subject: Re: ABIT KT7 and temp monitoring References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bert Driehuis wrote: > > On Thu, 8 Mar 2001, Lyndon Nerenberg wrote: > > > > healthd works fine on systems that use supported monitoring chips. > > > Unfortunately the number of chips that healthd supports is pretty small > > > compared to monitoring tools on other platforms, e.g. Motherboard Monitor on > > > Windows or LM Sensors on Linux. > > > > Which says to me that the interface should be abstracted out. > > Something like a device driver that presents a /dev device that > > you can read or ioctl to get the information in a somewhat chip- > > independent fashion. > > I've toyed with this idea (actually, I've implemented it for BSD/OS 4.x > using the sysctl interface). However, there are two problems with it > that made me drop the project for the time being. > > First of all, putting it in the kernel means a rigid interface, not to > mention the associated bloat and near-constant kernel updates as new > chips get glued to motherboards (and wired in new an innovative ways). > > Second, the user needs to define what sensor means what anyway, because > of the ease of miswiring, and because a broken fan is indistinguisable > from a nonexistant fan, which means a config file must be used anyway. > > Finally, none of the monitoring chips I've seen can be detected > reliably. The ones attached to the ISA bus can be checked for sanity > with some confidence (the W83781D has a one byte id), but scanning the > I2C bus can easily lock a motherboard (I think that that's what's > causing my Intel board to act up when the ichsmb driver gets added to > the kernel). I also have a KT7. When you talked about the system hanging on the Temp and Fans message, I tried building a new release with the smbus stuff included. I don't see a hang but I also don't see any smb devices in the dmesg. Kent > > Cheers, > > -- Bert > -- > Bert Driehuis -- driehuis@playbeing.org -- +31-20-3116119 > If the only tool you've got is an axe, every problem looks like fun! > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message