Date: Fri, 22 Feb 2013 08:37:00 -0500 From: Paul Mather <paul@gromit.dlib.vt.edu> To: Jeremy Chadwick <jdc@koitsu.org> Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-stable@freebsd.org, John Baldwin <jhb@freebsd.org>, Navdeep Parhar <nparhar@gmail.com> Subject: Re: IPMI serial console Message-ID: <B761E1EF-0DF4-43A5-A952-467B5C129BED@gromit.dlib.vt.edu> In-Reply-To: <20130222042907.GA75261@icarus.home.lan> References: <E44ABF7A-3795-471B-B241-7103ECE2119E@gsoft.com.au> <51269ABD.2040308@gmail.com> <2AF6F8E4-A45E-4D4C-9232-FF09AD4A3641@gsoft.com.au> <5126A3A1.1030208@gmail.com> <64293C7A-038A-4EA1-B394-9E80CFCBC14F@gsoft.com.au> <20130221230001.GF2598@kib.kiev.ua> <20130221232929.GA91708@icarus.home.lan> <3FE71C9F-29B2-48F5-9A51-D312B1803E14@gsoft.com.au> <20130222013258.GA93350@icarus.home.lan> <9F6E4B36-0C89-4409-91FB-08CC90848D23@gsoft.com.au> <20130222042907.GA75261@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 21, 2013, at 11:29 PM, Jeremy Chadwick <jdc@koitsu.org> wrote: > On Fri, Feb 22, 2013 at 02:22:52PM +1030, Daniel O'Connor wrote: >> On 22/02/2013, at 12:02, Jeremy Chadwick <jdc@koitsu.org> wrote: >>>> Hmm I tried putting '-S 115200' in /boot.config and it broke - the = boot process didn't run the loader (or kernel). >>>=20 >>> I'll talk a bit about this -- again, sorry for the verbosity. I'll >>> explain what I've historically used/done, then speculate a bit about >>> your IPMI stuff: >>>=20 >>> For me, on systems without IPMI, all I had to do was this (and = nothing >>> else): >>>=20 >>> * Put the following in /boot.config: >>>=20 >>> -S115200 -Dh >>=20 >> This breaks the boot for me, boot.config has to contain more than = just >> flags it seems. In any case I believe setting boot_multicons and >> boot_serial is the same as -Dh. Not sure about the baud rate though. >=20 > Then someone broke something (parser or something else). This has > always, *always* worked (just flags). The last time I verified it was > with the release of 9.0-RELEASE. I do have a system I could test this > on, but I'd need to find a null modem cable first. >=20 > I have seen some MFCs that touch those bits in the bootloader, but = from > my memory it didn't touch anything other than supporting /boot/config = as > an alternate location to the classic /boot.config file. I would be = very > surprised if this broke it. >=20 > I can assure you that those were the only flags that were needed, and = in > exactly that syntax. Even the Handbook has this in it, as well as > boot(8). >=20 > I believe your explanation of boot_multicons and boot_serial are = correct > and do correlate with -D and -h. I could look at the bootstrap code = to > verify. The options are described in loader(8) but not = loader.conf(5). I think something did break back at the start of the year that caused = /boot.config contents to render the system completely unbootable. At = least that is what happened to me on RELENG_8: = http://lists.freebsd.org/pipermail/freebsd-stable/2013-January/071579.html= Bruce A. Mah reports later in the same thread that his happened to him = on 8.3-RELEASE. I don't know if this was fixed. Cheers, Paul.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B761E1EF-0DF4-43A5-A952-467B5C129BED>