Date: Mon, 14 Mar 2005 14:18:26 -0800 From: Julian Elischer <julian@elischer.org> To: Jeff <anon1@santaba.com> Cc: freebsd-net@freebsd.org Subject: Re: IPMI doesn't work... Message-ID: <42360DB2.5000500@elischer.org> In-Reply-To: <4235E6CC.7040909@santaba.com> References: <4235E6CC.7040909@santaba.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I use IPMI with intel boards using the fxp driver. it seems to work ok.. The only problem I have seen its that is IS possible for the OS to turn off the NIC so that IPMI can't be reached.. Usually during a 'suspend' or similar. On a server you wouldn't do that however. Jeff wrote: > <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 > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42360DB2.5000500>