From owner-freebsd-questions@FreeBSD.ORG Mon Dec 6 23:09:31 2010 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87AAC106566C; Mon, 6 Dec 2010 23:09:31 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from vms173007pub.verizon.net (vms173007pub.verizon.net [206.46.173.7]) by mx1.freebsd.org (Postfix) with ESMTP id 665F78FC0A; Mon, 6 Dec 2010 23:09:30 +0000 (UTC) Received: from [192.168.1.8] ([unknown] [173.70.194.135]) by vms173007.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LD100M844BJPC62@vms173007.mailsrvcs.net>; Mon, 06 Dec 2010 17:09:20 -0600 (CST) Message-id: <4CFD6D2F.6090304@aldan.algebra.com> Date: Mon, 06 Dec 2010 18:09:35 -0500 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; uk-UA; rv:1.9.2.12) Gecko/20101114 Thunderbird/3.1.6 MIME-version: 1.0 To: Andriy Gapon References: <4CFC910A.5090806@aldan.algebra.com> <4CFD3EC0.1060600@fuckner.net> <4CFD5006.7010303@aldan.algebra.com> <4CFD6BA3.7070505@freebsd.org> In-reply-to: <4CFD6BA3.7070505@freebsd.org> Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-Mailman-Approved-At: Mon, 06 Dec 2010 23:30:33 +0000 Cc: questions@freebsd.org, hardware@freebsd.org Subject: Re: monitoring hardware temperatures X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2010 23:09:31 -0000 On 06.12.2010 18:02, Andriy Gapon wrote: > BTW, you could probably write a simple script employing smbmsg(1) to query the > DIMMs based on logic in the sdtemp driver. From OpenBSD's sdtemp man-page, it would seem, the driver uses the iic framework (if that's the right word, khmm...) And on this server I can't get /dev/iic* (nor smb*) to appear despite loading everything I could think of (even the viapm): 3 1 0xffffffff80c23000 d22 iic.ko 4 4 0xffffffff80c24000 10e7 iicbus.ko 5 1 0xffffffff80c26000 f16 iicsmb.ko 6 5 0xffffffff80c27000 819 smbus.ko 7 1 0xffffffff80c28000 c02 smb.ko 8 3 0xffffffff80c29000 114f iicbb.ko 9 1 0xffffffff80c2b000 1df3 ichsmb.ko 10 1 0xffffffff80c2d000 1aed intpm.ko 11 1 0xffffffff80c2f000 e38 pcf.ko 12 1 0xffffffff80c30000 b83 lpbb.ko 13 1 0xffffffff80c31000 368b ppbus.ko 14 1 0xffffffff80c35000 262a viapm.ko Could it be, that the motherboard simply does not have the iic-circuitry and that some other method has to be used? Thanks! Yours, -mi