From owner-freebsd-net@FreeBSD.ORG Tue Mar 15 00:31:35 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E55216A4CE for ; Tue, 15 Mar 2005 00:31:35 +0000 (GMT) Received: from sb.santaba.com (sb.santaba.com [207.154.84.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23CFA43D41 for ; Tue, 15 Mar 2005 00:31:35 +0000 (GMT) (envelope-from anon1@santaba.com) Received: from [192.168.3.100] (unknown [205.180.85.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sb.santaba.com (Postfix) with ESMTP id 0131A28483; Mon, 14 Mar 2005 16:31:34 -0800 (PST) Message-ID: <42362D37.6010202@santaba.com> Date: Mon, 14 Mar 2005 16:32:55 -0800 From: Jeff User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jung-uk Kim References: <4235E6CC.7040909@santaba.com> <200503141747.57487.jkim@niksun.com> In-Reply-To: <200503141747.57487.jkim@niksun.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: IPMI doesn't work... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 00:31:35 -0000 Jung-uk Kim wrote: >On Monday 14 March 2005 02:32 pm, Jeff wrote: > > >>>it worth posting to -net> >> >>on a 5.3 amd64 system. anyone have any luck or know anything about >>this? i can query variables right up until the point where the >>kernel loads, then nothing. ibm is saying this can be caused by >>the actual nic driver (the Baseboard Management Controller (BMC) >>shares the network interface); the system uses a Broadcom BCM5704C >>Dual gig adapter: >> >>bge0: >>mem 0xfe000000-0xfe00ffff,0xfe010000-0xfe01ffff irq 24 at device >>1.0 on pci2 >> >> > >Does 'in-band' mode work for you? Try FreeIPMI to check: > >http://www.gnu.org/software/freeipmi/ >http://www.freshports.org/sysutils/freeipmi/ > > > I'm not sure what you mean by in band. The IP address of the BMC is assigned via the bios and is different from what the OS later assigns. With imiptool we can turn on/powercycle/monitor via the BMC assigned address up until the point where the kernel loads. Once it does, the BMC no longer responds. This doesn't happen with the two linux distros we've tried it on. Wtih both, including SuSE, we can still query/control via the BMC using ipmitool. It seems to be some sort of driver issue to me. I find it confusing that the NIC is shared between the BMC and the OS, but I guess that's just how it's done. Perhaps the bsd broadcomm driver is simply blocking this somehow... jeff