Date: Mon, 19 Dec 2005 18:30:50 +0200 From: Ruslan Ermilov <ru@FreeBSD.org> To: freebsd-current@FreeBSD.org Subject: Re: New nfpm.c driver available for testing Message-ID: <20051219163049.GA84996@ip.net.ua> In-Reply-To: <69674F40-30B2-4025-B5A5-AC3DE44C00A4@nevada.net.nz> References: <20051218173028.GV41326@ip.net.ua> <69674F40-30B2-4025-B5A5-AC3DE44C00A4@nevada.net.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
--cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 =20 > w/ 4GB of RAM running -amd64 >=20 I have the same motherboard. > root@stratos# dmesg | grep nf > nfpm0: <AMD-8111 SMBus 2.0 Controller> port 0xcc00-0xcc1f irq 19 at =20 > device 7.2 on pci0 > smbus0: <System Management Bus> on nfpm0 >=20 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. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --cNdxnHkX5QqsyA0e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDpuA5qRfpzJluFF4RAoBYAJ9Cm3YN+E09iRKaV7GFok6OLtCyAgCfdtKF 9NsYhLLITs9KdPJaVGF5eHY= =45W5 -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051219163049.GA84996>