From owner-freebsd-net@FreeBSD.ORG  Mon Mar 14 19:31:08 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 9FE2816A4CE
	for <freebsd-net@freebsd.org>; Mon, 14 Mar 2005 19:31:08 +0000 (GMT)
Received: from sb.santaba.com (sb.santaba.com [207.154.84.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8139443D1F
	for <freebsd-net@freebsd.org>; Mon, 14 Mar 2005 19:31:08 +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 66D2228433
	for <freebsd-net@freebsd.org>; Mon, 14 Mar 2005 11:31:08 -0800 (PST)
Message-ID: <4235E6CC.7040909@santaba.com>
Date: Mon, 14 Mar 2005 11:32:28 -0800
From: Jeff <anon1@santaba.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-net@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: 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 <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2005 19:31:08 -0000

<posted this to -questions too but thought the nic component made 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: <Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003> mem 
0xfe000000-0xfe00ffff,0xfe010000-0xfe01ffff irq 24 at device 1.0 on pci2

anyone have any idea why this may be the case?  unfortunately for me and 
others here, the inability to remotely manage boxes (console/power 
cycle/detect drive failures/etc) via ipmi will be a deal breaker in our 
push for FBSD in our fleet (couple hundred) of dual proc amd64 IBM e325 
servers.  SuSE here we come (unwillingly)...

thx