From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 21 19:52:55 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A62C16A4C8 for ; Thu, 21 Sep 2006 19:52:55 +0000 (UTC) (envelope-from ohartman@uni-mainz.de) Received: from mailgate01.zdv.uni-mainz.de (mailgate01.zdv.Uni-Mainz.DE [134.93.178.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21B7E43D68 for ; Thu, 21 Sep 2006 19:52:43 +0000 (GMT) (envelope-from ohartman@uni-mainz.de) Received: from exfront02.zdv.uni-mainz.de ([134.93.176.56]) by mailgate01.zdv.uni-mainz.de with ESMTP; 21 Sep 2006 21:52:41 +0200 Received: from mail.uni-mainz.de ([134.93.176.49]) by exfront02.zdv.Uni-Mainz.DE with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Sep 2006 21:52:41 +0200 Received: from [192.168.1.128] ([85.178.26.45] RDNS failed) by mail.uni-mainz.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Sep 2006 21:52:40 +0200 Message-ID: <4512ED7F.1030400@mail.uni-mainz.de> Date: Thu, 21 Sep 2006 21:52:31 +0200 From: "O. Hartmann" User-Agent: Thunderbird 1.5.0.7 (X11/20060917) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 Sep 2006 19:52:40.0883 (UTC) FILETIME=[7F29B030:01C6DDB7] Subject: FBSD 6.2-PRE/AMD64: two times SMBUS on ASUS A8N32-SLI? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2006 19:52:55 -0000 Running FreeBSD 6.2-PRE/AMD64 on an ASUS A8N32-SLI shows up two smbus- interfaces as you can see in the short dmesg-excerpt. In kernel config there is only nfsmb mentioned, so I do not expect more than one smb-bus on that kind of motherboard. Can anyone explain this odd behaviour? Temperature- and fanspeed monitoring is still not possible, neither through ACPI, nor mbmon utility found in ports. Regards, Oliver -- nfsmb0: port 0xcc00-0xcc1f,0x600-0x63f,0x700-0x73f irq 20 at device 10.1 on pci 0 smbus0: on nfsmb0 smb0: on smbus0 nfsmb1: on nfsmb0 smbus1: on nfsmb1 smb1: on smbus1