Date: Tue, 26 Apr 2005 10:08:15 +0300 From: Danny Braniss <danny@cs.huji.ac.il> To: Jeff Behl <jbehl@fastclick.com> Cc: current@freebsd.org Subject: Re: serial/ether console & ramblings Message-ID: <E1DQKB5-0006Qi-HC@cs1.cs.huji.ac.il> In-Reply-To: Message from Jeff Behl <jbehl@fastclick.com> of "Mon, 25 Apr 2005 23:02:13 PDT." <426DD965.4010106@fastclick.com>
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... just look at the amount of magic needed to run IPMI! ... BIOS+NIC+BMC+linux-emulation+cli+proxy ... Can we get back on track? this is becoming a IPMI bashing, and we are no where nearer in finding a decent repalcement for that good-old-serial-console. danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1DQKB5-0006Qi-HC>