Date: Wed, 12 Nov 2014 01:20:25 +0100 From: Andreas Nilsson <andrnils@gmail.com> To: Dmitry Morozovsky <marck@rinet.ru> Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: SuperMicro IPMI/SOL and ipmitool troubles Message-ID: <CAPS9%2BSu970ukYwbYcfzrrC=hMnT61CQzYRd-6RaoLiW42BK4Dw@mail.gmail.com> In-Reply-To: <CAPS9%2BSv4kNjR=69kWEf8zhAXGBpRYmULZm8AnFxSscBiw2wwiw@mail.gmail.com> References: <alpine.BSF.2.00.1411112022500.25949@woozle.rinet.ru> <3C955A8F-9D1A-463B-BB9A-256C36BF0D4C@gromit.dlib.vt.edu> <alpine.BSF.2.00.1411112226450.25949@woozle.rinet.ru> <CAPS9%2BSuvWq1vtBw8K3J5NRs30272MV7EgkFMT57A=FspeZvCbQ@mail.gmail.com> <CAPS9%2BSv4kNjR=69kWEf8zhAXGBpRYmULZm8AnFxSscBiw2wwiw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 12, 2014 at 1:10 AM, Andreas Nilsson <andrnils@gmail.com> wrote: > > On Tue, Nov 11, 2014 at 8:45 PM, Andreas Nilsson <andrnils@gmail.com> > wrote: > >> >> >> On Tue, Nov 11, 2014 at 8:29 PM, Dmitry Morozovsky <marck@rinet.ru> >> wrote: >> >>> Paul, >>> >>> >>> On Tue, 11 Nov 2014, Paul Mather wrote: >>> >>> > > I'm trying to set up sol console for supermicro servers, reading >>> some documents >>> > >>> > Aye, and there's the rub: I've found that the COM port that SOL uses >>> > varies across different Supermicro server models, and the BIOS support >>> > for assigning or determining the COM port differs (or is sometimes >>> > nonexistent) between those servers. :-( >>> > >>> > I recently spent quite a bit of time trying to figure out why SOL was >>> > not working on a particular Supermicro server and it turned out to be >>> > that the COM port differed to those I'd used in previous setups. >>> >>> Yes, at least on X8SIE your hint works, swithing to com3 with >>> >>> # SOL console >>> boot_multicons="yes" >>> boot_serial="YES" >>> console="comconsole vidconsole" >>> # com3 is ipmi/sol console >>> comconsole_port="0x3E8" >>> comconsole_speed="115200" >>> >>> works, thanks a lot! >>> >>> Still fighting microcloud blades... >>> >>> Next thing will be consolidation all these into conserver-com for both >>> logging >>> and centralized management... >>> >>> >>> -- >>> Sincerely, >>> D.Marck [DM5020, MCK-RIPE, DM3-RIPN] >>> [ FreeBSD committer: marck@FreeBSD.org ] >>> ------------------------------------------------------------------------ >>> *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** >>> ------------------------------------------------------------------------ >>> >>> >> Well, >> >> I just performed my upgrade from 9.2 to 9.3 and now serial does not work >> anymore, so something funky is going on. >> >> I made sure to copy both the loader.conf and ttys file just to be sure. I >> see the loader loading modules, but as soon as kernel takes over serial >> console goes quiet :/ >> >> Best Regards >> Andreas >> > > Some more data points: > The difference between working and non-working serial console are one > single line in loader.conf: > hw.uart.console=1234 > > loader.conf looks like: > > zfs_load="YES" > > geom_mirror_load="YES" > > ipfw_load="YES" > > ipmi_load="YES" > > coretemp_load="YES" > > beastie_disable="YES" > > boot_serial="YES" > > boot_multicons="YES" > > console="comconsole,vidconsole" > > > hint.uart.0.port="0x3E8" > > hint.uart.0.irq="10" > > hw.uart.console="1234" > > hint.acpi_throttle.0.disbled=1 > > net.inet.ip.fw.default_to_accept=1 > > Best regards > Andreas > Oh, setting hw.uart.console=1234 renders me with a working serial console over iLO on the HP machine as well ( HP dl360 g5 ilo2-2.22 ) Best regards Andreas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPS9%2BSu970ukYwbYcfzrrC=hMnT61CQzYRd-6RaoLiW42BK4Dw>