Date: Mon, 25 Apr 2005 23:02:13 -0700 From: Jeff Behl <jbehl@fastclick.com> To: Julian Elischer <julian@elischer.org> Cc: current@freebsd.org Subject: Re: serial/ether console & ramblings Message-ID: <426DD965.4010106@fastclick.com> In-Reply-To: <426D5F94.1000302@elischer.org> References: <E1DQ8ns-000JXj-Is@cs1.cs.huji.ac.il> <426D4179.1020508@fastclick.com> <426D59F5.4070601@elischer.org> <426D5C93.4020802@fastclick.com> <426D5F94.1000302@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: > > > Jeff Behl wrote: > >>>> but my whole point is that nothing in 1) works remotely (out of band) >>>> when the system and the BMC share the same ethernet controller, at >>>> least >>>> with the bge driver. as i mentioned in the thread, i can power cycle >>>> and see the serial console remotely (number 2 from above) all the >>>> way up >>>> to the point where the kernel loads. as soon as it does, the bge >>>> driver >>>> no longer shunts off RMCP packets (what IPMI uses) to the Baseboard >>>> Management Controller, so no IPMI... >>>> >>>> >>>> >>> >>> the intel MBs allow you to share the 10/100 ethernet with the IPMI >>> controller. >>> >>> >> >> >> as do the motherboards with the e325s. we can to everything out of band >> when running linux, but that's because the driver for the broadcom nics >> in linux are aware of the BMC... >> >> > > I run the intels with FreeBSD OOB without any problems. what interface driver is being used? that'd be nifty if the motherboard had first dibs on a packet, but i didn't realize that was the way it could work. the linux bge driver certainly has code in it specifically for RMCP packets...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?426DD965.4010106>