From owner-freebsd-current@FreeBSD.ORG Mon Dec 19 20:30:55 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 095C716A42D; Mon, 19 Dec 2005 20:30:55 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF84143D60; Mon, 19 Dec 2005 20:30:46 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1EoRed-0000tk-00; Mon, 19 Dec 2005 21:30:43 +0100 Date: Mon, 19 Dec 2005 21:30:43 +0100 To: Ruslan Ermilov Message-ID: <20051219203043.GA26388@poupinou.org> References: <20051218173028.GV41326@ip.net.ua> <69674F40-30B2-4025-B5A5-AC3DE44C00A4@nevada.net.nz> <20051219163049.GA84996@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051219163049.GA84996@ip.net.ua> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-current@FreeBSD.org Subject: Re: New nfpm.c driver available for testing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2005 20:30:56 -0000 On Mon, Dec 19, 2005 at 06:30:50PM +0200, Ruslan Ermilov wrote: > On Mon, Dec 19, 2005 at 10:59:43AM +1300, Philip Murray wrote: > > This is on a Dual Dual-Core Opteron 275 on a Tyan S2882-D motherboard > > w/ 4GB of RAM running -amd64 > > > I have the same motherboard. > > > root@stratos# dmesg | grep nf > > nfpm0: port 0xcc00-0xcc1f irq 19 at > > device 7.2 on pci0 > > smbus0: on nfpm0 > > > I figured that AMD-8111 uses an EC-based SMBus register access, so > I've split the drivers into two: amdsmb(4) supports AMD-8111 SMBus > 2.0 controller which uses EC to read/write SMBus registers, and > nfsmb(4) supports NVIDIA nForce-2/3/4 MCP twin SMBus 2.0 controller > that appears to use an I/O based access to SMBus registers. > > http://people.freebsd.org/~patches/amdsmb-nfsmb.patch > > 1. > Recompile everything in /sys/modules/i2c/ (create two directories, > controllers/amdsmb and controllers/nfsmb before applying a patch). > > 2. > Check with smbtest: > > a) on nForce: > smbtest /dev/smb0 > smbtest /dev/smb1 > b) on AMD-8111: > smbtest > > All smbtest commands should include "slave 8" device which is > the SMBus Host device. If it didn't find any more devices, it > means that you now have a working SMBus bus, which it otherwise > useless on your system. It if detects some other devices, > chances are that some of them are xmbmon recognizeable sensors. > > 3. > Make sure you compile the latest sysutils/xmbmon port which has > smb(4) support ("mbmon" should have the -s option (lowercase ell)). > > 4. > Substitute your PCI ID in xmbmon's pci_pm.h (see my original > post that explains this in more detail). > > 5. > On nForce2/3/4, run mbmon -S -s0 -d and mbmon -S -s1 -d. > On AMD-8111, run mbmon -S -d. > > You may also want to s/-d/-D/ to verify it finds devices > attached to SMBus, it's similar to smbtest. If it finds any > known sensors (my systems don't have them), you can run > mbmon -S -s[01] -c8 1 to display eight probes with a one > second interval. > > P.S. I don't know how useful all of this is, since my systems > don't seem to have any sensors attached to SMBus 2.0 busses. > I think those tyan motherboards use IPMI. Maybe sysutils/freeipmi will work? -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care.