From owner-freebsd-bugs@FreeBSD.ORG Mon Oct 17 21:10:29 2005 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C149D16A46F for ; Mon, 17 Oct 2005 21:10:29 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 344E643D6E for ; Mon, 17 Oct 2005 21:10:26 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j9HLAQJp019751 for ; Mon, 17 Oct 2005 21:10:26 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j9HLAQMe019750; Mon, 17 Oct 2005 21:10:26 GMT (envelope-from gnats) Date: Mon, 17 Oct 2005 21:10:26 GMT Message-Id: <200510172110.j9HLAQMe019750@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Mikhail Teterin Cc: Subject: Re: kern/77365: [patch] amdpm driver has wrong PCI device ID for 8111 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mikhail Teterin List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2005 21:10:30 -0000 The following reply was made to PR kern/77365; it has been noted by GNATS. From: Mikhail Teterin To: "Mark Gooderum" Cc: bug-followup@freebsd.org Subject: Re: kern/77365: [patch] amdpm driver has wrong PCI device ID for 8111 Date: Mon, 17 Oct 2005 17:00:27 -0400 > What motherboard do you have and what slave addresses are you probing? I'm using IWill's DK8X motherboard and am simply trying to use the `chm' program, which is installed by the sysutils/consolehm port: pci0: at device 7.2 (no driver attached) amdpm0: port 0x50e0-0x50ff at device 7.3 on pci0 smbus0: on amdpm0 smb0: on smbus0 The program (mostly) works in the /dev/io-mode (chm -I), but the /dev/smb0 mode is producing 'EINV' errors only. -mi