From owner-freebsd-questions@FreeBSD.ORG Mon Dec 6 23:19:26 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 06B241065696; Mon, 6 Dec 2010 23:19:26 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1E7898FC25; Mon, 6 Dec 2010 23:19:24 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id BAA17088; Tue, 07 Dec 2010 01:19:18 +0200 (EET) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1PPkL0-000Ddd-Aw; Tue, 07 Dec 2010 01:19:18 +0200 Message-ID: <4CFD6F75.10003@freebsd.org> Date: Tue, 07 Dec 2010 01:19:17 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101029 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: "Mikhail T." References: <4CFC910A.5090806@aldan.algebra.com> <4CFD3EC0.1060600@fuckner.net> <4CFD5006.7010303@aldan.algebra.com> <4CFD6BA3.7070505@freebsd.org> <4CFD6D2F.6090304@aldan.algebra.com> In-Reply-To: <4CFD6D2F.6090304@aldan.algebra.com> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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:19:26 -0000 on 07/12/2010 01:09 Mikhail T. said the following: > 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, That's quite possible. Another possibility is that a driver that should be able to handle your hardwre just doesn't know the particular IDs. pciconf -lv output could shed some light. -- Andriy Gapon