From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 11:51:00 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 E091C16A41F for ; Fri, 9 Dec 2005 11:51:00 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Received: from stalker.bmc.brk.ru (stalker.bmc.brk.ru [217.150.59.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AA1343D7D for ; Fri, 9 Dec 2005 11:50:58 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Date: Fri, 9 Dec 2005 14:50:53 +0300 From: Artemiev Igor To: "Jeremy Messenger" Message-Id: <20051209145053.1cf47b3e.ai@bmc.brk.ru> In-Reply-To: References: <20051206093020.691e1483.ai@bmc.brk.ru> <20051207095818.0b307c89.ai@bmc.brk.ru> <20051208091422.4d1a3ee0.ai@bmc.brk.ru> <20051208125359.17d7f47a.ai@bmc.brk.ru> Organization: Bryansk Medical Center X-Mailer: Sylpheed version 2.0.0beta4 (GTK+ 2.6.8; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] nForce2 SMBus support - nForce3/4 support added. Not tested yet 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: Fri, 09 Dec 2005 11:51:01 -0000 On Thu, 08 Dec 2005 13:15:57 -0600 "Jeremy Messenger" wrote: > I can see /dev/smb* now, but I still can't use -S in mbmon. > # mbmon -S > No SMBus HWM available!! > InitMBInfo: Unknown error: 0 Try invoke mbmon with -p . Mbmon doesn`t know your monitor chip. > Have you tried to do the kldunload amdpm yet? It will get FreeBSD > crash and forced me to reboot. I don't have any debug in my kernel, > so I can't provide the backtraces. Does amdpm needs the iic* stuff? I > remember that one of my dead motherboard that use viapm required the > iic* stuff. It`s strange. kldunload is working in my case. Could your provide kernel backtrace? -- iprefetch ai